Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Hard Drive Problem

Apr 5, 2005 3:44AM PDT

I have been using a Western Digital WD1200JB 120 Gb hard drive as the boot drive on a system running Win98SE. The mobo is an ABIT VH7T. Recently the drive has been behaving oddly. If I perform a warm reboot using "restart", the BIOS fails to detect the drive and I get a "Failed Boot" error. If I restart and open the BIOS and highlight the drive location, "Auto" does find the Drive and I save the BIOS configuration and the system successfully reboots. The BIOS never fails to detect the drive if the PC is restarted from a cold boot when the system has been powered off and then restarted.
There is an additional drive (IBM 49Gb)attached to the same IDE port as a slave and it has never given any problem at all.
Neither Norton Disk Doctor nor the Western Digital Diagnostic tools detect any problem with the device.

I would appreciate any ideas anyone can provide on troubleshooting this issue.

Thanks,

Jim

Discussion is locked

- Collapse -
Not sure if this will help for a warm boot.
Apr 5, 2005 4:27AM PDT

If you have not enabled floppy seek in the BIOS, enable it.

What you need to do is "stall" for time during the reboot for the drive to come up to speed to be detected. Any delay in the boot sequence that you can add, that runs before it tries to find the drive could help.

Although, I must admit that the problem usually happens during a cold rather than a warm boot if this is the cause.

- Collapse -
Hard Drive Problem
Apr 5, 2005 5:10AM PDT

Thanks for the advice Ray, I'll give it a try and let you know if it helps.

Jim

- Collapse -
Not sure if this will help for a warm boot.
Apr 5, 2005 5:18AM PDT

I enabled Floppy seek on boot in the BIOS and it did not resolve the problem. Thanks for the suggestion, I'll keep pecking a way at it.

Jim

- Collapse -
Dual HDs (heat)
Apr 5, 2005 5:43AM PDT

Try reseating the IDE cable and power cable. The system can get "stale" either from hot/cold cycling. Try another IDE cable set as well if possible the cost is very low. Also, understand high density HDs when mounted too close together get the areal spacing whacked due to the heat build-up, its an after-effect from running a long time(usage). The Seagate HD could be heading to a failure so bck-up more often as a safety measure. Be prepared to use your warranty if under 3-5yrs(I forget).

tada Happy -----Willy

- Collapse -
What boot sequence art you using??
Apr 5, 2005 5:43AM PDT

Can you make it CD, then A, then C. This, of course is assuming that the problem is that the drive is not up to spped when it gets looked for.

Are you using AUTO in the BIOS as the detection method? That means that it gets searched for at each boot, but possibly if you have the parameters set, they are not exactly correct. I could never get any drive to detect showing the parameters that the vendors sheet gave. One parameter was always different than given by the mfr. Not the same parameter for each drive type.

I must admit that I can't understand, why a drive that had been running would be slow to come up again. Do you have a reset switch?? Try that to see if it makes a difference.

- Collapse -
What boot sequence are you using??
Apr 5, 2005 6:39AM PDT

My boot sequence is A then C the CD. I'll try changing it.

I did find that if I perform the detection in Auto, it accurately detects the parameters. I then switched to manually locking in the detected parameters. So far that seems to work.

Thanks,

Jim

- Collapse -
Problem found and fixed!
Apr 22, 2005 7:49AM PDT

I finally found and corrected the problem.

It seems there was an intermittently defective IDE cable.

I replaced the IDE cable and everything works perfectly now. The drives are autodetected normally in BIOS and no more problems.

Simply replacing the old cable with a new one did the trick.

Thanks for all the responses and suggestions.

Jim