I have about 8-10 brand new WD1600AAJB-00J3A0 (Caviar Blue) IDE drives that I am using to load Windows 7 32 bit on for a variety of older IBM computers (ThinkCentre A30 8198-66U). The drives work fine except each time the computer is rebooted, there is a 1 in 10 chance that the hard drive (or the boot partition) appears to NOT BE RECOGNIZED by the BIOS, resulting in the error message “NO OS Found”.
To resolve the condition, the computer must be powered OFF, then powered on, and it will boot
fine. But once again, if someone tries to reboot it, 1 time out of 10 times it will report no OS found.
I have tried just about all the jumper configurations possible, along with
updating the computer BIOS, changing BIOS settings, changing IDE cables, etc. I have
adjusted power settings in Windows 7 so that the power settings are such that the HD does not get shut off.
I have even cloned (Acronis) a 200GB maxtor drive from the WD1600AAJB-00J3A0, and it
works perfectly unlike the WD1600AAJB-00J3A0. I also cloned 2 other random
drives, 1 of which was a 40GB WD drive (Caviar WD400BB-23DEA0), and the other a 40GB Maxtor (4D040H2) from this WD drive and they also work fine. One of these drives I had placed in the computer and set what I call an “infinite restart routine”. I ran that for 3 days over labor day weekend, and when I came in on Tuesday morning, the computer had not jammed up in the No OS found screen. With this, I know for a fact that the problem has to do with the WD1600AAJB model.
I had thought that high heat was possibly a factor so I placed the hard drive in front of a high velocity fan in cold AC, but that too made no difference.
Every single one of my WD1600AAJB-00J3A0 behave this way. I had settled on trusted WD and this
model hard drive to replaced the old worn stock drives, but now I am considering moving away from WD altogether.
It seems like the drive is shutting itself off and then the BIOS does not see
it until power is reset to the drive.
I have not noticed this happening on a Win XP installation, but I will start an infinite restart loop on one tonight to see if it too has a problem.
I am a system admin of 16 years. I thought I could say that I’ve seen it all, but now this.
I’ve scoured the Internet looking for clues, and have found nothing seeminly relevant. I am very determined to find out what the problem is.
Is anyone else experiencing this? What could be happening here?