New slave Sata HDD leads to system not booting anymore

May 10, 2015
2
0
4,510
0
Hello everyone,

I've got the following problem:
I am in desperate need for additional disk space, but a little low on budget. Luckily a colleague could get me a seemingly broken hdd from WD with 1 TB. Problem was: it did not boot anymore in its original system. So there should be some Data on the drive and even a bootable OS.

After plugging it in, it gets correctly identified as a slave to my master SDD at the BIOS, but after the "Loading Operating System..." prompt (win7) I only get more and more random colored pixels in the top few lines of my screen.

So I went into diagnosis using Ultimate Boot Disk and some of its tools, especially the WD Lifeguard Diagnostics Tool for DOS. When doing so, the Tool immediately freezes upon starting a quick test, leaving a reset the only option. When I use boot management tools, it IS possible to read out the master boot sector (though, this does not help me very much, as I am unable to read it...).

So until now, I am unable to bring the HDD back to life. If someone here has any ideas what the issue could be or how to remedy it, I would be extremely grateful!

Thanks a lot in advance!
Matthias
 

Phillip Corcoran

Titan
Moderator
My guess is the drive is faulty if it causes SeaTools to freeze, in which case it's no longer usable.

Incidentally, there's no such thing as a "slave" SATA drive. The term "slave" applies only to an IDE drive which shares the same data cable as the "master" IDE drive, whereas SATA drives are always connected to separate data cables.

 
May 10, 2015
2
0
4,510
0


Thanks for the quick reply and the information on SATA drives (I noticed that jumpers are no longer used due to single cables and such...).
It wasn't SeaTools, I used the WD Diagnosis Tool for DOS, but anyway, result is the same I suppose...

So, you suppose there are no chances to revive it by rewriting master boot sectors or something of the kind?
 

ASK THE COMMUNITY

TRENDING THREADS