Motherboard killing my Hard Drives

Over the last several days I lost the ability to boot from three hard drives. When one went down I plugged in another only to have it follow suit.

The following is the screen I get when I power on the PC.

http://i290.photobucket.com/albums/l...ps181ee5ed.jpg

Obviously there is an issue with the motherboard because one can only give coincidence so much credit.

Each time it's happened was on "power up" after a previously successful "power off". So it wasn't as if the PC crashed beforehand or exhibited any unusual behavior to signify that the next boot up attempt would fail.

Can anyone tell me what the possible problems is and a solution so this system doesn't do the same to the fourth drive I just plugged in?

Thanks.

Darren Harris
Staten Island, New York.

On Tue, 23 Apr 2013 15:07:47 -0700 (PDT),
wrote:

Over the last several days I lost the ability to boot from three hard drives. When one went down I plugged in another only to have it follow suit.

The following is the screen I get when I power on the PC.

http://i290.photobucket.com/albums/l...ps181ee5ed.jpg

Obviously there is an issue with the motherboard because one can only give coincidence so much credit.

Each time it's happened was on "power up" after a previously successful "power off". So it wasn't as if the PC crashed beforehand or exhibited any unusual behavior to signify that the next boot up attempt would fail.

Can anyone tell me what the possible problems is and a solution so this system doesn't do the same to the fourth drive I just plugged in?

Simple--don't plug a fourth drive in!

Obviously the port on the motherboard is doing something evil to the
drives. I've had a laptop die that way, it only took frying one more
drive to get the point across.

wrote:
Over the last several days I lost the ability to boot from three hard drives. When one went down I plugged in another only to have it follow suit.

The following is the screen I get when I power on the PC.

http://i290.photobucket.com/albums/l...ps181ee5ed.jpg

Obviously there is an issue with the motherboard because one can only give coincidence so much credit.

Each time it's happened was on "power up" after a previously successful "power off". So it wasn't as if the PC crashed beforehand or exhibited any unusual behavior to signify that the next boot up attempt would fail.

Can anyone tell me what the possible problems is and a solution so this system doesn't do the same to the fourth drive I just plugged in?

Thanks.

Darren Harris
Staten Island, New York.

Well, don't run any more drives on that system,
until you figure it out :-)

*******

I would take the dead drive, to a computer known not to be
killing drives, and test it there.

To protect that computer against damage, I might insert
a PCI IDE card in it, install a driver for the PCI IDE
card, then connect the suspect drive to the PCI IDE card.
If the PCI IDE card is ruined, the motherboard is protected
and only the PCI IDE card needs to be changed out. So that's
a relatively conservative approach, to protecting the
known-good computer. I have several Promise TX2 cards for that.

Once the test computer is booted, you can use TestDisk to
examine the suspect drive as a data drive, and look for data on it.
Maybe it's just the MBR got deleted, and the partitions
are still present.

First, on the known-good test computer, you check at BIOS
level, whether the dead drive can be detected. Enter the BIOS,
look in the disk interface section, and see if the model
number of the drive is listed. That's a basic I/O test,
proving the drive is running internally, and it is able to
send an identity string on demand.

If there is no sign of the drive at all, either an I/O interface
went overvoltage, or +5V/+12V went overvoltage. Something
a bit more physical, low level, and catastrophic.

If the drive is detected, but no sane data can be detected.
perhaps the bad computer has malware which is deleting the MBR
or the partitions.

(I've used this one. It's not a beginner level tool, as the
interface requires interpretation. *Do not* immediately
say yes, to any attempts to write the disk. Press
control-C if you need to exit at any time. This tool can list
files in a partition, for a limited set of file systems.)

http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step

Partition Find and Mount: Download
(I haven't used this one, just bookmarked it.
I don't know anything about it.)

http://findandmount.com/download/

Those are examples of tools you can try, on your
known-good computer.

*******

If all you owned, was the bad computer, you could:

1) Install a new IDE PCI card. Connect unbroken drive to that.
This covers an I/O voltage problem. It would not
solve potential driver problems though. Or an out-of-spec
ATX supply.
2) Check ATX power supply voltages with a multimeter.
If no multimeter is available, go to the BIOS
hardware monitor ("Health") page, and examine
the measured voltages there. 3.3V, 5V, 12V should
be mentioned, and standards say there is a +/-5% tolerance
on voltage. If you need help with that, post the
voltages you see in the Health page, and I can
quote sections of the formfactors.org docs that cover
those rails.
3) To examine the disk drive controller board for damage,
it helps if the components are facing the outside.
For a few years now, they've rotated the controller board,
such that the components are hidden. On the older
drives, you can look for burned transient suppressors
near the power input point, as proof the power supply
has been "burning" the drives. Now that the controller
boards are upside-down, you have to take the controller
board off to do such a check, which sucks. Because of
this development, it's probably easier now to use your
multimeter, and just check the suspect power supply directly
with the meter. Before, you also had the option of
inspecting for burn marks on the hard drive controller
board.

HTH,
Paul

En el artículo ,
escribió:

Can anyone tell me what the possible problems is

It's the power supply. Motherboards don't kill hard drives.

--
(\_/)
(='.'=)
(")_(")

On 4/24/2013 2:07 AM, Mike Tomlinson wrote:
En el artículo ,
escribió:

Can anyone tell me what the possible problems is

It's the power supply. Motherboards don't kill hard drives.


I second this. It's happened to me. Paul told you why in his post.

Hench wrote:
On 4/24/2013 2:07 AM, Mike Tomlinson wrote:
En el artículo ,
escribió:

Can anyone tell me what the possible problems is

It's the power supply. Motherboards don't kill hard drives.


I second this. It's happened to me. Paul told you why in his post.

It's easier to understand the power supply case. But I wouldn't
discount a problem on I/O. It's just a question of making up a
plausible theory, that fits the interface type. I'm too lazy to
spend the day, making up some theories for it :-)

Paul

"Paul" wrote in message
...
wrote:
Over the last several days I lost the ability to boot from three hard
drives. When one went down I plugged in another only to have it follow
suit.

The following is the screen I get when I power on the PC.

http://i290.photobucket.com/albums/l...ps181ee5ed.jpg

Obviously there is an issue with the motherboard because one can only
give coincidence so much credit.

Each time it's happened was on "power up" after a previously successful
"power off". So it wasn't as if the PC crashed beforehand or exhibited
any unusual behavior to signify that the next boot up attempt would fail.

Can anyone tell me what the possible problems is and a solution so this
system doesn't do the same to the fourth drive I just plugged in?

Thanks.

Darren Harris
Staten Island, New York.

Well, don't run any more drives on that system,
until you figure it out :-)

*******

I would take the dead drive, to a computer known not to be
killing drives, and test it there.

To protect that computer against damage, I might insert
a PCI IDE card in it, install a driver for the PCI IDE
card, then connect the suspect drive to the PCI IDE card.


Not all IDE interfaces are the same - especially plug in ones.

I recently added an IDE expansion to a MOBO that didn't have any IDE
headers, it wouldn't recognise the drives I'd taken from the previous MOBO
without a re-format.

Pretty lucky I'd backed them up!

"Mike Tomlinson" wrote in message
...
En el artículo ,
escribió:

Can anyone tell me what the possible problems is

It's the power supply. Motherboards don't kill hard drives.


Making such a sweeping generalisation isn't too smart.

I've had actual experience of a ESD damaged MOBO trashing a CD-RW drive & a
HDD on the same header.

OTOH - I've recovered (and still using) a drive from a MOBO that had bulged
electrolytic capacitors caused by the PSU.

Ian Field wrote:


"Paul" wrote in message
...
wrote:
Over the last several days I lost the ability to boot from three hard
drives. When one went down I plugged in another only to have it
follow suit.

The following is the screen I get when I power on the PC.

http://i290.photobucket.com/albums/l...ps181ee5ed.jpg


Obviously there is an issue with the motherboard because one can only
give coincidence so much credit.

Each time it's happened was on "power up" after a previously
successful "power off". So it wasn't as if the PC crashed beforehand
or exhibited any unusual behavior to signify that the next boot up
attempt would fail.

Can anyone tell me what the possible problems is and a solution so
this system doesn't do the same to the fourth drive I just plugged in?

Thanks.

Darren Harris
Staten Island, New York.

Well, don't run any more drives on that system,
until you figure it out :-)

*******

I would take the dead drive, to a computer known not to be
killing drives, and test it there.

To protect that computer against damage, I might insert
a PCI IDE card in it, install a driver for the PCI IDE
card, then connect the suspect drive to the PCI IDE card.


Not all IDE interfaces are the same - especially plug in ones.

I recently added an IDE expansion to a MOBO that didn't have any IDE
headers, it wouldn't recognise the drives I'd taken from the previous
MOBO without a re-format.

Pretty lucky I'd backed them up!

If the original controller was RAID capable, and the driver
writes metadata to suit itself, that can affect interoperability.

RAID controllers have three choices, for a JBOD disk.

1) Use no metadata for JBOD, only add metadata when the
user builds an array.
2) Put metadata up near the end of the disk, then trim down
the declared size of the disk, so the metadata cannot get
overwritten (for as long as the drive resides on the RAID
controller port at least).
3) Put metadata up near the beginning. [Insert your own recipe
as to how this is possible - offset all accesses by 64KB etc.]

I moved an IDE drive, from a Promise controller (378???) to
the Southbridge, and the first partition would disappear. I
suspect this had something to do with metadata, but at the time,
didn't investigate the details. The partition would reappear,
when the drive was put back on the original controller.

I have investigated on another RAID capable setup, and on that
one, about 5MB of space is reserved down near the end, and 64KB of
metadata is written somewhere in the middle of it. I zeroed
the entire drive beforehand, so I could find that 64KB chunk.
And inside the 64KB chunk, was sufficient room to describe
up to 16 RAID arrays. (Data pattern repeated every 4KB, suggesting
each 4KB block described one array.)

So RAID metadata might have had something to do with it.

Paul

wrote:
Over the last several days I lost the ability to boot from three hard
drives. When one went down I plugged in another only to have it
follow suit.

The following is the screen I get when I power on the PC.

http://i290.photobucket.com/albums/l...ps181ee5ed.jpg


I had the PXE-thingy (on T22) like so, I solved it (and never saw it again)
by doing a fresh install of XP, rather than the Backups i'd been using.

Obviously there is an issue with the motherboard because one can only
give coincidence so much credit.

Each time it's happened was on "power up" after a previously
successful "power off". So it wasn't as if the PC crashed beforehand
or exhibited any unusual behavior to signify that the next boot up
attempt would fail.

I didn't get exactly above but found that it would boot if it went via
Hirens-boot-CD.


Can anyone tell me what the possible problems is and a solution so
this system doesn't do the same to the fourth drive I just plugged
in?

Thanks.

Darren Harris
Staten Island, New York.