Sometimes ASUS K8V SE Deluxe loses SATA connection...

[ANTant]

Hello,

I have an annoying computer problem with my third additional HDD (a Seagate Barracuda 7200.7 Plus ST3120026A 120
GB with 8 MB cache and 7200 RPM speed). The HDD is connected through VIA SATA Controller and an IDE-to-SATA
adapter. It seems to lose connection once in a while in Windows XP and outside. This has been happening for
almost a year, and still unresolved. I thought it was fixed, but it doesn't seem like it.

I know it is not an OS problem because sometimes BIOS/motherboard boot up doesn't see this drive. Basically, VIA
VT8237 SATA RAID BIOS Setting Utility V4.80 said "Scan Devices,Please wait... HardWare Initiate failed, please
check device!!! The Bios does not be installed. Press <g> to continue!" After I press G to continue, the old Grub
loader (Windows XP Pro. SP2 with all updates and Linux) for OS options (at least I know this part works). When I
go to Windows, I get a black screen and hangs. If I go to safe mode, it gets stuck at agp440.sys part. I did
notice I have to wait about five minutes or so for this part to time out before I see XP's splash screen.
Obviously in Windows, I don't have my Seagate HDD (H: and I: drives).

The motherboard is an ASUS K8V SE Deluxe (VIA K8T800 Socket 754 ATX; VIA VT8237 South Bridge; revision 2; 1007
Firmware; onboard sound disabled; onboard Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
enabled). You can read the rest of the detailed specifications and setup (primary computer) at
http://alpha.zimage.com/~ant/antfarm/about/computers.txt ...

The reason why I have to use the motherboard's VIA SATA controller is because the motherboard's onboard Promise
controller would not boot up Windows XP at all. It just hangs in blackness (never shows the Windows XP splash
screen loader).

I already tried replacing these things:
1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way enough).

I *DID* notice something. If I were to wiggle, unplug, and/or replug the SATA cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS can see this drive again. I don't see
any exact pattern on which one fixes the problem. Sometimes I don't unplug/replug anything and only wiggle one or
more cabls/connectors, and things are back to normal easily. Sometimes I have to do ALL of them to make things
work again. I already tried rearranging the cables, check the contacts (they all looked fine to me), etc.

Another thing I noticed recently on last Sunday evening, but I am not sure if this is related to the problem
(could be clues, you never know) and never had this problem before (happened once so far). I noticed my computer
wouldn't want to read my CD-ROMs, CD-Rs, DVD-ROMs, and movie DVDs properly (new and old medias). I try to eject
my DVD drive with its eject button and via Explorer. Both failed after I see the drive to eject (blinking light).
I also saw this in Windows XP's event viewer:

Event Type: Error
Event Source: Cdrom
Event Category: None
Event ID: 7
Date: 10/29/2006
Time: 6:14:46 PM
User: N/A
Computer: MyBox
Description:
The device, \Device\CdRom0, has a bad block.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 68 00 01 00 b8 00 ..h...?.
0008: 00 00 00 00 07 00 04 c0 .......?
0010: 00 01 00 00 14 00 00 c0 .......?
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 5a 2c a2 00 00 00 00 00 Z,?.....
0030: ff ff ff ff 00 00 00 00 ????....
0038: 40 00 00 c4 02 00 00 00 @..?....
0040: 00 00 06 12 08 00 00 00 ........
0048: 00 00 00 00 14 00 00 00 ........
0050: 00 00 00 00 20 4e 5a 87 .... NZ?
0058: 00 00 00 00 b8 03 d3 88 ....?.??
0060: 01 00 00 00 00 00 00 00 ........
0068: 00 00 00 00 00 00 00 00 ........
0070: 00 00 00 00 00 00 00 00 ........
0078: 70 00 03 00 00 00 00 0a p.......
0080: 00 00 00 00 57 00 00 00 ....W...
0088: 00 00 00 00 00 00 00 00 ........

So, I decided to reboot. It didn't eject, via the drive button, when I was at the BIOS bootup. BIOS did show my
DVD drive, so I assume it saw it fine. So, I tried turning off the system and turning back on and I was able to
eject at this point (didn't want to use paperclip and hole method).

However, my BIOS showed VIA SATA can't find my third HDD again! I wonder if the DVD drive problem was related to
this. So, I did the usual pain in the arse thing. Turned machine off with PSU off, checked out the cables, etc.
First thing was to unplug and replug the power connection to the third HDD. Turned machine on, and NO FIX. So, I
repeated again. Unplugged the SATA adapter, move the SATA cable around (didn't unplug and replug), etc. Powered
the machine back on, it worked again.

I have had no problems a few times that lasted for months. Then, the problem returns. I don't think it is
temperature related because I have seen this happen when it is 80+(F) degrees in my room and in the 60s(F). Even
when machine is room temperature (just turned on the machine after working all day) and have been on for days.

Does this motherboard (or others; maybe VIA chipsets?) have a known issue with this type of setup? My computer
builder friend is also puzzled and out of ideas at the moment. Maybe I should toss this and get a new
motherboard, CPU, and RAM to upgrade.

Thank you in advance.
--
"The ants sought personal revenge for my having sprayed them the day before." --Oliver Smith
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

 

[Arno Wagner]

Hello,

I have an annoying computer problem with my third additional HDD (a Seagate Barracuda 7200.7 Plus ST3120026A 120
GB with 8 MB cache and 7200 RPM speed). The HDD is connected through VIA SATA Controller and an IDE-to-SATA
adapter. It seems to lose connection once in a while in Windows XP and outside. This has been happening for
almost a year, and still unresolved. I thought it was fixed, but it doesn't seem like it.

I know it is not an OS problem because sometimes BIOS/motherboard boot up doesn't see this drive. Basically, VIA
VT8237 SATA RAID BIOS Setting Utility V4.80 said "Scan Devices,Please wait... HardWare Initiate failed, please
check device!!! The Bios does not be installed. Press <g> to continue!" After I press G to continue, the old Grub
loader (Windows XP Pro. SP2 with all updates and Linux) for OS options (at least I know this part works). When I
go to Windows, I get a black screen and hangs. If I go to safe mode, it gets stuck at agp440.sys part. I did
notice I have to wait about five minutes or so for this part to time out before I see XP's splash screen.
Obviously in Windows, I don't have my Seagate HDD (H: and I: drives).

The motherboard is an ASUS K8V SE Deluxe (VIA K8T800 Socket 754 ATX; VIA VT8237 South Bridge; revision 2; 1007
Firmware; onboard sound disabled; onboard Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
enabled). You can read the rest of the detailed specifications and setup (primary computer) at
http://alpha.zimage.com/~ant/antfarm/about/computers.txt ...

The reason why I have to use the motherboard's VIA SATA controller is because the motherboard's onboard Promise
controller would not boot up Windows XP at all. It just hangs in blackness (never shows the Windows XP splash
screen loader).

I already tried replacing these things:
1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way enough).

I *DID* notice something. If I were to wiggle, unplug, and/or replug the SATA cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS can see this drive again. I don't see
any exact pattern on which one fixes the problem. Sometimes I don't unplug/replug anything and only wiggle one or
more cabls/connectors, and things are back to normal easily. Sometimes I have to do ALL of them to make things
work again. I already tried rearranging the cables, check the contacts (they all looked fine to me), etc.

Another thing I noticed recently on last Sunday evening, but I am not sure if this is related to the problem
(could be clues, you never know) and never had this problem before (happened once so far). I noticed my computer
wouldn't want to read my CD-ROMs, CD-Rs, DVD-ROMs, and movie DVDs properly (new and old medias). I try to eject
my DVD drive with its eject button and via Explorer. Both failed after I see the drive to eject (blinking light).
I also saw this in Windows XP's event viewer:

Event Type: Error
Event Source: Cdrom
Event Category: None
Event ID: 7
Date: 10/29/2006
Time: 6:14:46 PM
User: N/A
Computer: MyBox
Description:
The device, \Device\CdRom0, has a bad block.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 68 00 01 00 b8 00 ..h...?.
0008: 00 00 00 00 07 00 04 c0 .......?
0010: 00 01 00 00 14 00 00 c0 .......?
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 5a 2c a2 00 00 00 00 00 Z,?.....
0030: ff ff ff ff 00 00 00 00 ????....
0038: 40 00 00 c4 02 00 00 00 @..?....
0040: 00 00 06 12 08 00 00 00 ........
0048: 00 00 00 00 14 00 00 00 ........
0050: 00 00 00 00 20 4e 5a 87 .... NZ?
0058: 00 00 00 00 b8 03 d3 88 ....?.??
0060: 01 00 00 00 00 00 00 00 ........
0068: 00 00 00 00 00 00 00 00 ........
0070: 00 00 00 00 00 00 00 00 ........
0078: 70 00 03 00 00 00 00 0a p.......
0080: 00 00 00 00 57 00 00 00 ....W...
0088: 00 00 00 00 00 00 00 00 ........

So, I decided to reboot. It didn't eject, via the drive button, when I was at the BIOS bootup. BIOS did show my
DVD drive, so I assume it saw it fine. So, I tried turning off the system and turning back on and I was able to
eject at this point (didn't want to use paperclip and hole method).

However, my BIOS showed VIA SATA can't find my third HDD again! I wonder if the DVD drive problem was related to
this. So, I did the usual pain in the arse thing. Turned machine off with PSU off, checked out the cables, etc.
First thing was to unplug and replug the power connection to the third HDD. Turned machine on, and NO FIX. So, I
repeated again. Unplugged the SATA adapter, move the SATA cable around (didn't unplug and replug), etc. Powered
the machine back on, it worked again.

I have had no problems a few times that lasted for months. Then, the problem returns. I don't think it is
temperature related because I have seen this happen when it is 80+(F) degrees in my room and in the 60s(F). Even
when machine is room temperature (just turned on the machine after working all day) and have been on for days.

Does this motherboard (or others; maybe VIA chipsets?) have a known issue with this type of setup? My computer
builder friend is also puzzled and out of ideas at the moment. Maybe I should toss this and get a new
motherboard, CPU, and RAM to upgrade.

Thank you in advance.

So this happens only on start-up and if it is detected the drive runns
fine? Have you looked into teh SMART error log on the drive? Anything
in there? (You may have ti trun logging on, before it loggs errors...)

Arno

 

[ANTant]

Hello,
I have an annoying computer problem with my third additional HDD (a Seagate Barracuda 7200.7 Plus ST3120026A 120
GB with 8 MB cache and 7200 RPM speed). The HDD is connected through VIA SATA Controller and an IDE-to-SATA
adapter. It seems to lose connection once in a while in Windows XP and outside. This has been happening for
almost a year, and still unresolved. I thought it was fixed, but it doesn't seem like it.
I know it is not an OS problem because sometimes BIOS/motherboard boot up doesn't see this drive. Basically, VIA
VT8237 SATA RAID BIOS Setting Utility V4.80 said "Scan Devices,Please wait... HardWare Initiate failed, please
check device!!! The Bios does not be installed. Press <g> to continue!" After I press G to continue, the old Grub
loader (Windows XP Pro. SP2 with all updates and Linux) for OS options (at least I know this part works). When I
go to Windows, I get a black screen and hangs. If I go to safe mode, it gets stuck at agp440.sys part. I did
notice I have to wait about five minutes or so for this part to time out before I see XP's splash screen.
Obviously in Windows, I don't have my Seagate HDD (H: and I: drives).
The motherboard is an ASUS K8V SE Deluxe (VIA K8T800 Socket 754 ATX; VIA VT8237 South Bridge; revision 2; 1007
Firmware; onboard sound disabled; onboard Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
enabled). You can read the rest of the detailed specifications and setup (primary computer) at
http://alpha.zimage.com/~ant/antfarm/about/computers.txt ...
The reason why I have to use the motherboard's VIA SATA controller is because the motherboard's onboard Promise
controller would not boot up Windows XP at all. It just hangs in blackness (never shows the Windows XP splash
screen loader).
I already tried replacing these things:
1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way enough).
I *DID* notice something. If I were to wiggle, unplug, and/or replug the SATA cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS can see this drive again. I don't see
any exact pattern on which one fixes the problem. Sometimes I don't unplug/replug anything and only wiggle one or
more cabls/connectors, and things are back to normal easily. Sometimes I have to do ALL of them to make things
work again. I already tried rearranging the cables, check the contacts (they all looked fine to me), etc.
Another thing I noticed recently on last Sunday evening, but I am not sure if this is related to the problem
(could be clues, you never know) and never had this problem before (happened once so far). I noticed my computer
wouldn't want to read my CD-ROMs, CD-Rs, DVD-ROMs, and movie DVDs properly (new and old medias). I try to eject
my DVD drive with its eject button and via Explorer. Both failed after I see the drive to eject (blinking light).
I also saw this in Windows XP's event viewer:
Event Type: Error
Event Source: Cdrom
Event Category: None
Event ID: 7
Date: 10/29/2006
Time: 6:14:46 PM
User: N/A
Computer: MyBox
Description:
The device, \Device\CdRom0, has a bad block.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 68 00 01 00 b8 00 ..h...?.
0008: 00 00 00 00 07 00 04 c0 .......?
0010: 00 01 00 00 14 00 00 c0 .......?
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 5a 2c a2 00 00 00 00 00 Z,?.....
0030: ff ff ff ff 00 00 00 00 ????....
0038: 40 00 00 c4 02 00 00 00 @..?....
0040: 00 00 06 12 08 00 00 00 ........
0048: 00 00 00 00 14 00 00 00 ........
0050: 00 00 00 00 20 4e 5a 87 .... NZ?
0058: 00 00 00 00 b8 03 d3 88 ....?.??
0060: 01 00 00 00 00 00 00 00 ........
0068: 00 00 00 00 00 00 00 00 ........
0070: 00 00 00 00 00 00 00 00 ........
0078: 70 00 03 00 00 00 00 0a p.......
0080: 00 00 00 00 57 00 00 00 ....W...
0088: 00 00 00 00 00 00 00 00 ........
So, I decided to reboot. It didn't eject, via the drive button, when I was at the BIOS bootup. BIOS did show my
DVD drive, so I assume it saw it fine. So, I tried turning off the system and turning back on and I was able to
eject at this point (didn't want to use paperclip and hole method).
However, my BIOS showed VIA SATA can't find my third HDD again! I wonder if the DVD drive problem was related to
this. So, I did the usual pain in the arse thing. Turned machine off with PSU off, checked out the cables, etc.
First thing was to unplug and replug the power connection to the third HDD. Turned machine on, and NO FIX. So, I
repeated again. Unplugged the SATA adapter, move the SATA cable around (didn't unplug and replug), etc. Powered
the machine back on, it worked again.
I have had no problems a few times that lasted for months. Then, the problem returns. I don't think it is
temperature related because I have seen this happen when it is 80+(F) degrees in my room and in the 60s(F). Even
when machine is room temperature (just turned on the machine after working all day) and have been on for days.
Does this motherboard (or others; maybe VIA chipsets?) have a known issue with this type of setup? My computer
builder friend is also puzzled and out of ideas at the moment. Maybe I should toss this and get a new
motherboard, CPU, and RAM to upgrade.
Thank you in advance.

So this happens only on start-up and if it is detected the drive runns
fine? Have you looked into teh SMART error log on the drive? Anything
in there? (You may have ti trun logging on, before it loggs errors...)

I have seen the third HDD lose its connection in Windows before. Windows XP just freezes
because it can't find the HDD and locks up hard.
--
"The ants sought personal revenge for my having sprayed them the day before." --Oliver Smith
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

 

[ANTant]

I have an annoying computer problem with my third additional HDD (a Seagate Barracuda 7200.7 Plus ST3120026A 120

GB with 8 MB cache and 7200 RPM speed). The HDD is connected through VIA SATA Controller and an IDE-to-SATA
adapter. It seems to lose connection once in a while in Windows XP and outside. This has been happening for
almost a year, and still unresolved. I thought it was fixed, but it doesn't seem like it.
I know it is not an OS problem because sometimes BIOS/motherboard boot up doesn't see this drive. Basically, VIA
VT8237 SATA RAID BIOS Setting Utility V4.80 said "Scan Devices,Please wait... HardWare Initiate failed, please
check device!!! The Bios does not be installed. Press <g> to continue!" After I press G to continue, the old Grub
loader (Windows XP Pro. SP2 with all updates and Linux) for OS options (at least I know this part works). When I
go to Windows, I get a black screen and hangs. If I go to safe mode, it gets stuck at agp440.sys part. I did
notice I have to wait about five minutes or so for this part to time out before I see XP's splash screen.
Obviously in Windows, I don't have my Seagate HDD (H: and I: drives).
The motherboard is an ASUS K8V SE Deluxe (VIA K8T800 Socket 754 ATX; VIA VT8237 South Bridge; revision 2; 1007
Firmware; onboard sound disabled; onboard Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
enabled). You can read the rest of the detailed specifications and setup (primary computer) at
http://alpha.zimage.com/~ant/antfarm/about/computers.txt ...
The reason why I have to use the motherboard's VIA SATA controller is because the motherboard's onboard Promise
controller would not boot up Windows XP at all. It just hangs in blackness (never shows the Windows XP splash
screen loader).
I already tried replacing these things:
1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way enough).
I *DID* notice something. If I were to wiggle, unplug, and/or replug the SATA cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS can see this drive again. I don't see
any exact pattern on which one fixes the problem. Sometimes I don't unplug/replug anything and only wiggle one or
more cabls/connectors, and things are back to normal easily. Sometimes I have to do ALL of them to make things
work again. I already tried rearranging the cables, check the contacts (they all looked fine to me), etc.
Another thing I noticed recently on last Sunday evening, but I am not sure if this is related to the problem
(could be clues, you never know) and never had this problem before (happened once so far). I noticed my computer
wouldn't want to read my CD-ROMs, CD-Rs, DVD-ROMs, and movie DVDs properly (new and old medias). I try to eject
my DVD drive with its eject button and via Explorer. Both failed after I see the drive to eject (blinking light).
I also saw this in Windows XP's event viewer:
Event Type: Error
Event Source: Cdrom
Event Category: None
Event ID: 7
Date: 10/29/2006
Time: 6:14:46 PM
User: N/A
Computer: MyBox
Description:
The device, \Device\CdRom0, has a bad block.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 68 00 01 00 b8 00 ..h...?.
0008: 00 00 00 00 07 00 04 c0 .......?
0010: 00 01 00 00 14 00 00 c0 .......?
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 5a 2c a2 00 00 00 00 00 Z,?.....
0030: ff ff ff ff 00 00 00 00 ????....
0038: 40 00 00 c4 02 00 00 00 @..?....
0040: 00 00 06 12 08 00 00 00 ........
0048: 00 00 00 00 14 00 00 00 ........
0050: 00 00 00 00 20 4e 5a 87 .... NZ?
0058: 00 00 00 00 b8 03 d3 88 ....?.??
0060: 01 00 00 00 00 00 00 00 ........
0068: 00 00 00 00 00 00 00 00 ........
0070: 00 00 00 00 00 00 00 00 ........
0078: 70 00 03 00 00 00 00 0a p.......
0080: 00 00 00 00 57 00 00 00 ....W...
0088: 00 00 00 00 00 00 00 00 ........
So, I decided to reboot. It didn't eject, via the drive button, when I was at the BIOS bootup. BIOS did show my
DVD drive, so I assume it saw it fine. So, I tried turning off the system and turning back on and I was able to
eject at this point (didn't want to use paperclip and hole method).
However, my BIOS showed VIA SATA can't find my third HDD again! I wonder if the DVD drive problem was related to
this. So, I did the usual pain in the arse thing. Turned machine off with PSU off, checked out the cables, etc.
First thing was to unplug and replug the power connection to the third HDD. Turned machine on, and NO FIX. So, I
repeated again. Unplugged the SATA adapter, move the SATA cable around (didn't unplug and replug), etc. Powered
the machine back on, it worked again.
I have had no problems a few times that lasted for months. Then, the problem returns. I don't think it is
temperature related because I have seen this happen when it is 80+(F) degrees in my room and in the 60s(F). Even
when machine is room temperature (just turned on the machine after working all day) and have been on for days.
Does this motherboard (or others; maybe VIA chipsets?) have a known issue with this type of setup? My computer
builder friend is also puzzled and out of ideas at the moment. Maybe I should toss this and get a new
motherboard, CPU, and RAM to upgrade.

So this happens only on start-up and if it is detected the drive runns
fine? Have you looked into teh SMART error log on the drive? Anything
in there? (You may have ti trun logging on, before it loggs errors...)

I have seen the third HDD lose its connection in Windows before. Windows XP just freezes
because it can't find the HDD and locks up hard.

Oops, I forgot to answer the other question about SMART sensor. This is from EVEREST Home Ed.
v2.20...:
ID Attribute Description Threshold Value Worst Data Status
01 Raw Read Error Rate 6 59 55 104132688 OK: Value is normal
03 Spin Up Time 0 97 96 0 OK: Always passing
04 Start/Stop Count 20 100 100 29 OK: Value is normal
05 Reallocated Sector Count 36 100 100 0 OK: Value is normal
07 Seek Error Rate 30 82 60 177184323 OK: Value is normal
09 Power-On Time Count 0 80 80 18307 OK: Always passing
0A Spin Retry Count 97 100 100 0 OK: Value is normal
0C Power Cycle Count 20 99 99 1095 OK: Value is normal
C2 Temperature 0 37 60 37 OK: Always passing
C3 Hardware ECC Recovered 0 59 55 104132688 OK: Always passing
C5 Current Pending Sector Count 0 100 100 0 OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0 OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0 OK: Always passing
C8 Write Error Rate 0 100 253 0 OK: Always passing
CA <vendor-specific> 0 100 253 0 OK: Always passing

Nothing odd, right?
--
"The ants sought personal revenge for my having sprayed them the day before." --Oliver Smith
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

 

[Arno Wagner]

In comp.sys.ibm.pc.hardware.storage (e-mail address removed) wrote:
[...]

Oops, I forgot to answer the other question about SMART sensor. This is from EVEREST Home Ed.
v2.20...:
ID Attribute Description Threshold Value Worst Data Status
01 Raw Read Error Rate 6 59 55 104132688 OK: Value is normal
03 Spin Up Time 0 97 96 0 OK: Always passing
04 Start/Stop Count 20 100 100 29 OK: Value is normal
05 Reallocated Sector Count 36 100 100 0 OK: Value is normal
07 Seek Error Rate 30 82 60 177184323 OK: Value is normal
09 Power-On Time Count 0 80 80 18307 OK: Always passing
0A Spin Retry Count 97 100 100 0 OK: Value is normal
0C Power Cycle Count 20 99 99 1095 OK: Value is normal
C2 Temperature 0 37 60 37 OK: Always passing
C3 Hardware ECC Recovered 0 59 55 104132688 OK: Always passing
C5 Current Pending Sector Count 0 100 100 0 OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0 OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0 OK: Always passing
C8 Write Error Rate 0 100 253 0 OK: Always passing
CA <vendor-specific> 0 100 253 0 OK: Always passing

Nothing odd, right?

The raw read error rate is a bit extreme, and so is the seek error rate.
That could indicate unclean power.

Does this HDD maybe have a faultuy power connector? If it is on a
Y-cable, changing the PSU would not have mattered of the Y-cable
is to blame. It could also be a hairline fracture in a power path
on the PCB, or a defective EM filter or the like. Contact problems
also have this typical pattern of vanishing for a while when they
are subject to mechanical force, such as you reseating the SATA
connector.

Arno

 

[Folkert Rienstra]

I have an annoying computer problem with my third additional HDD (a Seagate Barracuda 7200.7 Plus ST3120026A 120
GB with 8 MB cache and 7200 RPM speed). The HDD is connected through VIA SATA Controller and an IDE-to-SATA
adapter. It seems to lose connection once in a while in Windows XP and outside. This has been happening for
almost a year, and still unresolved. I thought it was fixed, but it doesn't seem like it.
I know it is not an OS problem because sometimes BIOS/motherboard boot up doesn't see this drive. Basically, VIA
VT8237 SATA RAID BIOS Setting Utility V4.80 said "Scan Devices,Please wait... HardWare Initiate failed, please
check device!!! The Bios does not be installed. Press <g> to continue!" After I press G to continue, the old Grub
loader (Windows XP Pro. SP2 with all updates and Linux) for OS options (at least I know this part works). When I
go to Windows, I get a black screen and hangs. If I go to safe mode, it gets stuck at agp440.sys part. I did
notice I have to wait about five minutes or so for this part to time out before I see XP's splash screen.
Obviously in Windows, I don't have my Seagate HDD (H: and I: drives).
The motherboard is an ASUS K8V SE Deluxe (VIA K8T800 Socket 754 ATX; VIA VT8237 South Bridge; revision 2; 1007
Firmware; onboard sound disabled; onboard Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
enabled). You can read the rest of the detailed specifications and setup (primary computer) at
http://alpha.zimage.com/~ant/antfarm/about/computers.txt ...
The reason why I have to use the motherboard's VIA SATA controller is because the motherboard's onboard Promise
controller would not boot up Windows XP at all. It just hangs in blackness (never shows the Windows XP splash
screen loader).
I already tried replacing these things:
1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way enough).
I *DID* notice something. If I were to wiggle, unplug, and/or replug the SATA cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS can see this drive again. I don't see
any exact pattern on which one fixes the problem. Sometimes I don't unplug/replug anything and only wiggle one or
more cabls/connectors, and things are back to normal easily. Sometimes I have to do ALL of them to make things
work again. I already tried rearranging the cables, check the contacts (they all looked fine to me), etc.
Another thing I noticed recently on last Sunday evening, but I am not sure if this is related to the problem
(could be clues, you never know) and never had this problem before (happened once so far). I noticed my computer
wouldn't want to read my CD-ROMs, CD-Rs, DVD-ROMs, and movie DVDs properly (new and old medias). I try to eject
my DVD drive with its eject button and via Explorer. Both failed after I see the drive to eject (blinking light).
I also saw this in Windows XP's event viewer:

[snip]

Oops, I forgot to answer the other question about SMART sensor. This is from EVEREST Home Ed.
v2.20...:
ID Attribute Description Threshold Value Worst Data Status
01 Raw Read Error Rate 6 59 55 104132688 OK: Value is normal
03 Spin Up Time 0 97 96 0 OK: Always passing
04 Start/Stop Count 20 100 100 29 OK: Value is normal
05 Reallocated Sector Count 36 100 100 0 OK: Value is normal
07 Seek Error Rate 30 82 60 177184323 OK: Value is normal
09 Power-On Time Count 0 80 80 18307 OK: Always passing
0A Spin Retry Count 97 100 100 0 OK: Value is normal
0C Power Cycle Count 20 99 99 1095 OK: Value is normal
C2 Temperature 0 37 60 37 OK: Always passing
C3 Hardware ECC Recovered 0 59 55 104132688 OK: Always passing
C5 Current Pending Sector Count 0 100 100 0 OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0 OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0 OK: Always passing
C8 Write Error Rate 0 100 253 0 OK: Always passing
CA <vendor-specific> 0 100 253 0 OK: Always passing

Nothing odd, right?

Yup, all standard alfabet.

104,132,688 Raw read errors, peanuts what.
177,184,323 seek errors, raisins, who cares.

 

[ANTant]

In comp.sys.ibm.pc.hardware.storage (e-mail address removed) wrote:
[...]

Oops, I forgot to answer the other question about SMART sensor. This is from EVEREST Home Ed.
v2.20...:
ID Attribute Description Threshold Value Worst Data Status
01 Raw Read Error Rate 6 59 55 104132688 OK: Value is normal
03 Spin Up Time 0 97 96 0 OK: Always passing
04 Start/Stop Count 20 100 100 29 OK: Value is normal
05 Reallocated Sector Count 36 100 100 0 OK: Value is normal
07 Seek Error Rate 30 82 60 177184323 OK: Value is normal
09 Power-On Time Count 0 80 80 18307 OK: Always passing
0A Spin Retry Count 97 100 100 0 OK: Value is normal
0C Power Cycle Count 20 99 99 1095 OK: Value is normal
C2 Temperature 0 37 60 37 OK: Always passing
C3 Hardware ECC Recovered 0 59 55 104132688 OK: Always passing
C5 Current Pending Sector Count 0 100 100 0 OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0 OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0 OK: Always passing
C8 Write Error Rate 0 100 253 0 OK: Always passing
CA <vendor-specific> 0 100 253 0 OK: Always passing
Nothing odd, right?

The raw read error rate is a bit extreme, and so is the seek error rate.
That could indicate unclean power.

Does this HDD maybe have a faultuy power connector? If it is on a
Y-cable, changing the PSU would not have mattered of the Y-cable
is to blame. It could also be a hairline fracture in a power path

Is the Y-cable the one with colorful wires with white plugs like this one
(http://images.amazon.com/images/P/B0002NXNXG.01-A9B09ZK9BZJQ6.LZZZZZZZ.jpg)?
I don't know the terminologies well in computers.

on the PCB, or a defective EM filter or the like. Contact problems
also have this typical pattern of vanishing for a while when they
are subject to mechanical force, such as you reseating the SATA
connector.

Hmm, I should check that out. The only thing that is puzzling is sometimes
wiggling and/or replugging one thing (e.g., SATA cable, IDE-to-SATA, and
power connector) at a time doesn't fix it always. I just have to mess with
it/them until the problem is resolved. I am going to pass this to my friend
to see if he tried this already.
--
"The ants sought personal revenge for my having sprayed them the day before." --Oliver Smith
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

 

[Mike Tomlinson]

I already tried replacing these things:
1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way enough).

I *DID* notice something. If I were to wiggle, unplug, and/or replug the SATA
cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS can see
this drive again.

Since you state twice that wiggling the SATA adapter and its connections
cures the problem, and that you've replaced the SATA cable and adapter,
Occam's razor suggests that the problem is with the drive. Perhaps
there's a bad connection on one or more of the IDE interface pins of the
hard drive (a pin might have been pushed in or lifted from its solder
pad on the drive PCB.)

Try a different drive for a while to see if the problem still exists.

Also, SATA plugs work out of their sockets really easily, particularly
if there's any sort of strain on the cable (for example, where the
weight of the cable is taken by the plug/socket). The vibrations from
the drive probably don't help. Try and rearrange the SATA cable so that
it's mechanically supported where it plugs into the drive.

Does this motherboard (or others; maybe VIA chipsets?) have a known issue with
this type of setup?

I don't believe so. The VIA 8237(R) chip is well established and if
there were any problems with it, we'd have heard about them by now.

Maybe I should
toss this and get a new
motherboard, CPU, and RAM to upgrade.

I don't think a motherboard change etc. is going to make any difference
to your disappearing drive.

 

[Arno Wagner]

In comp.sys.ibm.pc.hardware.storage (e-mail address removed) wrote:
[...]

So this happens only on start-up and if it is detected the drive runns
fine? Have you looked into teh SMART error log on the drive? Anything
in there? (You may have ti trun logging on, before it loggs errors...)
I have seen the third HDD lose its connection in Windows
before. Windows XP just freezes because it can't find the HDD and
locks up hard.
Oops, I forgot to answer the other question about SMART sensor. This is from EVEREST Home Ed.
v2.20...:
ID Attribute Description Threshold Value Worst Data Status
01 Raw Read Error Rate 6 59 55 104132688 OK: Value is normal
03 Spin Up Time 0 97 96 0 OK: Always passing
04 Start/Stop Count 20 100 100 29 OK: Value is normal
05 Reallocated Sector Count 36 100 100 0 OK: Value is normal
07 Seek Error Rate 30 82 60 177184323 OK: Value is normal
09 Power-On Time Count 0 80 80 18307 OK: Always passing
0A Spin Retry Count 97 100 100 0 OK: Value is normal
0C Power Cycle Count 20 99 99 1095 OK: Value is normal
C2 Temperature 0 37 60 37 OK: Always passing
C3 Hardware ECC Recovered 0 59 55 104132688 OK: Always passing
C5 Current Pending Sector Count 0 100 100 0 OK: Always passing
C6 Off-Line Uncorrectable Sector Count 0 100 100 0 OK: Always passing
C7 Ultra ATA CRC Error Rate 0 200 200 0 OK: Always passing
C8 Write Error Rate 0 100 253 0 OK: Always passing
CA <vendor-specific> 0 100 253 0 OK: Always passing
Nothing odd, right?

The raw read error rate is a bit extreme, and so is the seek error rate.
That could indicate unclean power.
Does this HDD maybe have a faultuy power connector? If it is on a
Y-cable, changing the PSU would not have mattered of the Y-cable
is to blame. It could also be a hairline fracture in a power path

Is the Y-cable the one with colorful wires with white plugs like
this one
(http://images.amazon.com/images/P/B0002NXNXG.01-A9B09ZK9BZJQ6.LZZZZZZZ.jpg)?
I don't know the terminologies well in computers.

Yes, that is the one. It is calles Y-cable, because it splits one
pheripherial connector (cabeling red-black-black-yellow for
+5V - ground - ground +12V) into two. Some, especially cheaper ones
can have loose contacts or get corroded, thus resulting in
bad power to the device. Also they should not be chained,
one side should be to the PSU, the other to a device. (I have
chained two on occasion without problem, but they were good
ones.)

Hmm, I should check that out. The only thing that is puzzling is sometimes
wiggling and/or replugging one thing (e.g., SATA cable, IDE-to-SATA, and
power connector) at a time doesn't fix it always.

Also typical for contact problems. They are perhaps the most randomly
behaving physical faults.

I just have to mess with it/them until the problem is resolved. I am
going to pass this to my friend to see if he tried this already.

One thing that may also help if it is the power connector, is removing
and re-insterting is a few times. If it is on a Y-cable, do the same
for the other end of the Y-cable.

Arno

 

[Arno Wagner]

I already tried replacing these things:
1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way enough).

I *DID* notice something. If I were to wiggle, unplug, and/or replug the SATA
cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS can see
this drive again.

Since you state twice that wiggling the SATA adapter and its connections
cures the problem, and that you've replaced the SATA cable and adapter,
Occam's razor suggests that the problem is with the drive. Perhaps
there's a bad connection on one or more of the IDE interface pins of the
hard drive (a pin might have been pushed in or lifted from its solder
pad on the drive PCB.)

Try a different drive for a while to see if the problem still exists.

Also, SATA plugs work out of their sockets really easily, particularly
if there's any sort of strain on the cable (for example, where the
weight of the cable is taken by the plug/socket).

True, but that would likely show up as CRC errors in the SMART
attributes (interruption while transfer). At least that is what
I expect. There were none for this drive.

Arno

 

[Folkert Rienstra]

1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way enough).

I *DID* notice something. If I were to wiggle, unplug, and/or replug the SATA
cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS can see
this drive again.

Since you state twice that wiggling the SATA adapter and its connections
cures the problem, and that you've replaced the SATA cable and adapter,
Occam's razor suggests that the problem is with the drive. Perhaps
there's a bad connection on one or more of the IDE interface pins of
the hard drive (a pin might have been pushed in or lifted from its solder
pad on the drive PCB.)

Try a different drive for a while to see if the problem still exists.

Also, SATA plugs work out of their sockets really easily, particularly
if there's any sort of strain on the cable (for example, where the
weight of the cable is taken by the plug/socket).

[/QUOTE]

True, but that would likely show up as CRC errors in the SMART attributes

For ingoing transfers, data only and when in UDMA mode.

(interruption while transfer).

Uhuh,
And how exactly is the drive to write (log) that error without power, babblebot?

At least that is what I expect.

Yeah, obviously you didn't think it over.

There were none for this drive.

But it has a relatively high Power Cycle count for a relatively low Power-On Time.

 

[ANTant]

I already tried replacing these things:
1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way enough).

I *DID* notice something. If I were to wiggle, unplug, and/or replug the SATA
cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS can see
this drive again.

Since you state twice that wiggling the SATA adapter and its connections
cures the problem, and that you've replaced the SATA cable and adapter,
Occam's razor suggests that the problem is with the drive. Perhaps
there's a bad connection on one or more of the IDE interface pins of the
hard drive (a pin might have been pushed in or lifted from its solder
pad on the drive PCB.)

Hmm, good thinking. FYI. It happened again this morning while I was scanning with
Ad-Aware SE and showering. I rebooted, SATA BIOS didn't see the HDD. Opened the
case, fiddled with the inside. Did NOT unplug and replug anything. Only wiggled
cables and connectors. This did not fix the problem after two attempts in a row).
So, I unplugged the IDE-to-SATA adapter and replugged it. I think I overdid my
replug in terms of pressure and heard a snap. I didn't see what made that noise.
So, I turned the machine back on, and HDD works again for who knows how long. I
am wondering what the heck the loud snap was. I hope I didn't break anything.

Try a different drive for a while to see if the problem still exists.

OK, that could be a possibility. I have had this drive since 9/2003 with my
last system (Athlon XP and a different ASUS motherboard. I do remember having
problems with this drive because my old PSU was not strong enough. The HDD
would lose connection and make funny spin noises (had problems keeping up and
freeze). It didn't help that the new video (ATI Radeon 9800 Pro AIW) wanted
some of that power too. Getting a more powerful PSU (Enlight 250(?) watts to
Antec 400 watts) fixed all of this. I don't recall having anything like
today's problem before.

Also, SATA plugs work out of their sockets really easily, particularly
if there's any sort of strain on the cable (for example, where the
weight of the cable is taken by the plug/socket). The vibrations from
the drive probably don't help. Try and rearrange the SATA cable so that
it's mechanically supported where it plugs into the drive.

Ah. Yeah, I noticed that too. When I go check the connections after my HDD is
not found, it didn't feel losed or disconnected. Just to give you guys some
ideas on what my Antec PS180 (had this disconnection problem in an older
crappy generic 1998 tower ATX case too) case interior is like, see
http://www.silentpcreview.com/files/images/p180/psutunnel3.jpg (my three HDDs
are in the bottom right corner with that little container pulled out and near
the black case fan. The problematic Seagate HDD is located at the very
bottom.

I don't believe so. The VIA 8237(R) chip is well established and if
there were any problems with it, we'd have heard about them by now.
OK.

I don't think a motherboard change etc. is going to make any difference
to your disappearing drive.

OK.
--
"The ants sought personal revenge for my having sprayed them the day before." --Oliver Smith
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

 

[ANTant]

So this happens only on start-up and if it is detected the drive runns

Yes, that is the one. It is calles Y-cable, because it splits one
pheripherial connector (cabeling red-black-black-yellow for
+5V - ground - ground +12V) into two. Some, especially cheaper ones
can have loose contacts or get corroded, thus resulting in
bad power to the device. Also they should not be chained,
one side should be to the PSU, the other to a device. (I have
chained two on occasion without problem, but they were good
ones.)

OK. It's messy and dark in my case and I don't know a lot about this stuff.
It doesn't seem to be chain. I will ask my friend to look at this to double
check.

Also typical for contact problems. They are perhaps the most randomly
behaving physical faults.

One thing that may also help if it is the power connector, is removing
and re-insterting is a few times. If it is on a Y-cable, do the same
for the other end of the Y-cable.

OK.
--
"The ants sought personal revenge for my having sprayed them the day before." --Oliver Smith
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

 

[Lucian Ion]

I've been having exactly the same problems with an Asus P5GDC-V and Seagate
ST3200826AS drive.
You can check-out:
http://forumz.tomshardware.com/hardware/modules.php?name=Forums&file=viewtopic&t=188194&highlight=

After successively blaming the drive itself, the cable, the PSU and the
motherboard and after replacing all but the mobo, to no avail, I came to the
conclusion that it must the way I route the data cable. Since both cables
that I used were about half a meter long, and the mobo connector is very
close to the hdd, I was rolling the cable a bit and tying it up in a bunch.
Two days ago I happened to read some more about how sensitive these cables
are and decided to route my cable in one big loop with as smooth curve as
possible. So far so good, the drive hasn't dissapeared (in the recent time,
it was going away in a couple hours every time after turning the computer
on). Still I too have experienced longer periods after which the problem
recurred. If I get the same shit again, I will try a fancier, more expensive
cable like those sold by AC Ryan (currently I use ordinary cables like those
that come with the motherboard).

-hope this helps.

Hello,

I have an annoying computer problem with my third additional HDD (a
Seagate Barracuda 7200.7 Plus ST3120026A 120
GB with 8 MB cache and 7200 RPM speed). The HDD is connected through VIA
SATA Controller and an IDE-to-SATA
adapter. It seems to lose connection once in a while in Windows XP and
outside. This has been happening for
almost a year, and still unresolved. I thought it was fixed, but it
doesn't seem like it.

I know it is not an OS problem because sometimes BIOS/motherboard boot up
doesn't see this drive. Basically, VIA
VT8237 SATA RAID BIOS Setting Utility V4.80 said "Scan Devices,Please
wait... HardWare Initiate failed, please
check device!!! The Bios does not be installed. Press <g> to continue!"
After I press G to continue, the old Grub
loader (Windows XP Pro. SP2 with all updates and Linux) for OS options (at
least I know this part works). When I
go to Windows, I get a black screen and hangs. If I go to safe mode, it
gets stuck at agp440.sys part. I did
notice I have to wait about five minutes or so for this part to time out
before I see XP's splash screen.
Obviously in Windows, I don't have my Seagate HDD (H: and I: drives).

The motherboard is an ASUS K8V SE Deluxe (VIA K8T800 Socket 754 ATX; VIA
VT8237 South Bridge; revision 2; 1007
Firmware; onboard sound disabled; onboard Marvell Yukon 88E8001/8003/8010
PCI Gigabit Ethernet Controller
enabled). You can read the rest of the detailed specifications and setup
(primary computer) at
http://alpha.zimage.com/~ant/antfarm/about/computers.txt ...

The reason why I have to use the motherboard's VIA SATA controller is
because the motherboard's onboard Promise
controller would not boot up Windows XP at all. It just hangs in blackness
(never shows the Windows XP splash
screen loader).

I already tried replacing these things:
1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way
enough).

I *DID* notice something. If I were to wiggle, unplug, and/or replug the
SATA cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS
can see this drive again. I don't see
any exact pattern on which one fixes the problem. Sometimes I don't
unplug/replug anything and only wiggle one or
more cabls/connectors, and things are back to normal easily. Sometimes I
have to do ALL of them to make things
work again. I already tried rearranging the cables, check the contacts
(they all looked fine to me), etc.

Another thing I noticed recently on last Sunday evening, but I am not sure
if this is related to the problem
(could be clues, you never know) and never had this problem before
(happened once so far). I noticed my computer
wouldn't want to read my CD-ROMs, CD-Rs, DVD-ROMs, and movie DVDs properly
(new and old medias). I try to eject
my DVD drive with its eject button and via Explorer. Both failed after I
see the drive to eject (blinking light).
I also saw this in Windows XP's event viewer:

Event Type: Error
Event Source: Cdrom
Event Category: None
Event ID: 7
Date: 10/29/2006
Time: 6:14:46 PM
User: N/A
Computer: MyBox
Description:
The device, \Device\CdRom0, has a bad block.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 68 00 01 00 b8 00 ..h...?.
0008: 00 00 00 00 07 00 04 c0 .......?
0010: 00 01 00 00 14 00 00 c0 .......?
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 5a 2c a2 00 00 00 00 00 Z,?.....
0030: ff ff ff ff 00 00 00 00 ????....
0038: 40 00 00 c4 02 00 00 00 @..?....
0040: 00 00 06 12 08 00 00 00 ........
0048: 00 00 00 00 14 00 00 00 ........
0050: 00 00 00 00 20 4e 5a 87 .... NZ?
0058: 00 00 00 00 b8 03 d3 88 ....?.??
0060: 01 00 00 00 00 00 00 00 ........
0068: 00 00 00 00 00 00 00 00 ........
0070: 00 00 00 00 00 00 00 00 ........
0078: 70 00 03 00 00 00 00 0a p.......
0080: 00 00 00 00 57 00 00 00 ....W...
0088: 00 00 00 00 00 00 00 00 ........

So, I decided to reboot. It didn't eject, via the drive button, when I was
at the BIOS bootup. BIOS did show my
DVD drive, so I assume it saw it fine. So, I tried turning off the system
and turning back on and I was able to
eject at this point (didn't want to use paperclip and hole method).

However, my BIOS showed VIA SATA can't find my third HDD again! I wonder
if the DVD drive problem was related to
this. So, I did the usual pain in the arse thing. Turned machine off with
PSU off, checked out the cables, etc.
First thing was to unplug and replug the power connection to the third
HDD. Turned machine on, and NO FIX. So, I
repeated again. Unplugged the SATA adapter, move the SATA cable around
(didn't unplug and replug), etc. Powered
the machine back on, it worked again.

I have had no problems a few times that lasted for months. Then, the
problem returns. I don't think it is
temperature related because I have seen this happen when it is 80+(F)
degrees in my room and in the 60s(F). Even
when machine is room temperature (just turned on the machine after working
all day) and have been on for days.

Does this motherboard (or others; maybe VIA chipsets?) have a known issue
with this type of setup? My computer
builder friend is also puzzled and out of ideas at the moment. Maybe I
should toss this and get a new
motherboard, CPU, and RAM to upgrade.

Thank you in advance.
--
"The ants sought personal revenge for my having sprayed them the day
before." --Oliver Smith
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

 

[ANTant]

Wow, I wonder how common this problem is. So far, I haven't had this
problem after two weeks. We'll see... I think the longest streak without
problems was over a month.

I've been having exactly the same problems with an Asus P5GDC-V and Seagate
ST3200826AS drive.
You can check-out:
http://forumz.tomshardware.com/hardware/modules.php?name=Forums&file=viewtopic&t=188194&highlight=

After successively blaming the drive itself, the cable, the PSU and the
motherboard and after replacing all but the mobo, to no avail, I came to the
conclusion that it must the way I route the data cable. Since both cables
that I used were about half a meter long, and the mobo connector is very
close to the hdd, I was rolling the cable a bit and tying it up in a bunch.
Two days ago I happened to read some more about how sensitive these cables
are and decided to route my cable in one big loop with as smooth curve as
possible. So far so good, the drive hasn't dissapeared (in the recent time,
it was going away in a couple hours every time after turning the computer
on). Still I too have experienced longer periods after which the problem
recurred. If I get the same shit again, I will try a fancier, more expensive
cable like those sold by AC Ryan (currently I use ordinary cables like those
that come with the motherboard).

-hope this helps.

Hello,

I have an annoying computer problem with my third additional HDD (a
Seagate Barracuda 7200.7 Plus ST3120026A 120
GB with 8 MB cache and 7200 RPM speed). The HDD is connected through VIA
SATA Controller and an IDE-to-SATA
adapter. It seems to lose connection once in a while in Windows XP and
outside. This has been happening for
almost a year, and still unresolved. I thought it was fixed, but it
doesn't seem like it.

I know it is not an OS problem because sometimes BIOS/motherboard boot up
doesn't see this drive. Basically, VIA
VT8237 SATA RAID BIOS Setting Utility V4.80 said "Scan Devices,Please
wait... HardWare Initiate failed, please
check device!!! The Bios does not be installed. Press <g> to continue!"
After I press G to continue, the old Grub
loader (Windows XP Pro. SP2 with all updates and Linux) for OS options (at
least I know this part works). When I
go to Windows, I get a black screen and hangs. If I go to safe mode, it
gets stuck at agp440.sys part. I did
notice I have to wait about five minutes or so for this part to time out
before I see XP's splash screen.
Obviously in Windows, I don't have my Seagate HDD (H: and I: drives).

The motherboard is an ASUS K8V SE Deluxe (VIA K8T800 Socket 754 ATX; VIA
VT8237 South Bridge; revision 2; 1007
Firmware; onboard sound disabled; onboard Marvell Yukon 88E8001/8003/8010
PCI Gigabit Ethernet Controller
enabled). You can read the rest of the detailed specifications and setup
(primary computer) at
http://alpha.zimage.com/~ant/antfarm/about/computers.txt ...

The reason why I have to use the motherboard's VIA SATA controller is
because the motherboard's onboard Promise
controller would not boot up Windows XP at all. It just hangs in blackness
(never shows the Windows XP splash
screen loader).

I already tried replacing these things:
1. SATA cable
2. IDE to SATA adapter
3. Changed PSU (same brand but from 500 to 600 watts; think this is way
enough).

I *DID* notice something. If I were to wiggle, unplug, and/or replug the
SATA cable, power connector, and/or IDE
to SATA adapter [turned the system and its PSU off], then sometimes BIOS
can see this drive again. I don't see
any exact pattern on which one fixes the problem. Sometimes I don't
unplug/replug anything and only wiggle one or
more cabls/connectors, and things are back to normal easily. Sometimes I
have to do ALL of them to make things
work again. I already tried rearranging the cables, check the contacts
(they all looked fine to me), etc.

Another thing I noticed recently on last Sunday evening, but I am not sure
if this is related to the problem
(could be clues, you never know) and never had this problem before
(happened once so far). I noticed my computer
wouldn't want to read my CD-ROMs, CD-Rs, DVD-ROMs, and movie DVDs properly
(new and old medias). I try to eject
my DVD drive with its eject button and via Explorer. Both failed after I
see the drive to eject (blinking light).
I also saw this in Windows XP's event viewer:

Event Type: Error
Event Source: Cdrom
Event Category: None
Event ID: 7
Date: 10/29/2006
Time: 6:14:46 PM
User: N/A
Computer: MyBox
Description:
The device, \Device\CdRom0, has a bad block.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 68 00 01 00 b8 00 ..h...?.
0008: 00 00 00 00 07 00 04 c0 .......?
0010: 00 01 00 00 14 00 00 c0 .......?
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 5a 2c a2 00 00 00 00 00 Z,?.....
0030: ff ff ff ff 00 00 00 00 ????....
0038: 40 00 00 c4 02 00 00 00 @..?....
0040: 00 00 06 12 08 00 00 00 ........
0048: 00 00 00 00 14 00 00 00 ........
0050: 00 00 00 00 20 4e 5a 87 .... NZ?
0058: 00 00 00 00 b8 03 d3 88 ....?.??
0060: 01 00 00 00 00 00 00 00 ........
0068: 00 00 00 00 00 00 00 00 ........
0070: 00 00 00 00 00 00 00 00 ........
0078: 70 00 03 00 00 00 00 0a p.......
0080: 00 00 00 00 57 00 00 00 ....W...
0088: 00 00 00 00 00 00 00 00 ........

So, I decided to reboot. It didn't eject, via the drive button, when I was
at the BIOS bootup. BIOS did show my
DVD drive, so I assume it saw it fine. So, I tried turning off the system
and turning back on and I was able to
eject at this point (didn't want to use paperclip and hole method).

However, my BIOS showed VIA SATA can't find my third HDD again! I wonder
if the DVD drive problem was related to
this. So, I did the usual pain in the arse thing. Turned machine off with
PSU off, checked out the cables, etc.
First thing was to unplug and replug the power connection to the third
HDD. Turned machine on, and NO FIX. So, I
repeated again. Unplugged the SATA adapter, move the SATA cable around
(didn't unplug and replug), etc. Powered
the machine back on, it worked again.

I have had no problems a few times that lasted for months. Then, the
problem returns. I don't think it is
temperature related because I have seen this happen when it is 80+(F)
degrees in my room and in the 60s(F). Even
when machine is room temperature (just turned on the machine after working
all day) and have been on for days.

Does this motherboard (or others; maybe VIA chipsets?) have a known issue
with this type of setup? My computer
builder friend is also puzzled and out of ideas at the moment. Maybe I
should toss this and get a new
motherboard, CPU, and RAM to upgrade.

Thank you in advance.

--
"We are anthill men upon an anthill world." --Ray Bradbury
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )