Hard drive crapitude

imported_Zeke

Senior member
Sep 18, 2004
956
0
0
I've got a western digital 160gb (wd1600) connected as the slave to my main hard drive, and it has worked fine for several months, but now if I start windows wiht the drive connected, right after the bios(which recognizes the hard drive fine) I get a couple minutes of black screen and when windows finally boots I cant acess the drive, and diagnostic programs cant seem to read anything off it. Its installed in the device manager, which says its working, but windows xp still calls it "unreadable." It not my Ide cable, I checked that and I've swtiched power leads, as well as trying to start computer with only the WD, windiows wont even install to the drive. If I start the computer without the WD attached it boots fine with no problems. I'm getting no click of death and its seems to be spinning fine. Any ideas?
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
I know that when a WD is on a cable by itself, you want it jumpered for Single Drive. Why it's misbehaving when it's in a Slave role, with the other drive as Master (right?), I don't know, aside from the obvious: the hard drive might be dead or dying.
 

imported_Zeke

Senior member
Sep 18, 2004
956
0
0
well its less that a year old, and I'm not hearing any failure, but thats possible I guess. I have even tried rewriting the mbr and installing a new partiton table, nothing seems to work
 

Souka

Diamond Member
Sep 25, 2000
4,728
1
76
Hmm... I would download a diag-tool from Westerndigital...run it.... see what it turn up.

Best tool will be from WD, but IBM makes the Drive Fitness tool, Segate has a bootable and an on-line diag (Seatools)...... so give them a try if u can't find WD's.

Let us know what you find....

 

imported_Zeke

Senior member
Sep 18, 2004
956
0
0
yeah like I said already used data lifeguard which is WD's tool, CS dosent really like to work on my Asus board but I did try it no luck