re: Failed (non-boot) Hard drive halts windows bootup!?
Friday, September 30, 2005 at 10:11 am
Windows 2000 Annoyances Discussion Forum
Posted by C K
(6910 messages posted)
HDs fail in a number of ways. It sounds like yours has failed due to the platters
not spinning up and will give you the error you see because the media in the drive
can't be read. Doesn't matter why. This can happen either during BIOS POST, or
when Windows starts. In this case, it sounds like the drive shows in the BIOS but
the platters are not spinning up. The hive and key question has no bearing here
as Win 9X is the only system that supports a hardware change and re-detects hardware
on every boot up. Win NT/2k/XP doesn't. That's why NT systems won't start when
motherboards are changed (different IDE controllers) or HD's are moved to a new system.
You see that complaint here all the time. Drives are checked at boot if the dirty
bit has been set on the drive from previos problems or a bad shutdown. Otherwise,
Windows only reports or mounts (tries to mount) all drives reported by the BIOS.
If it can't, up pops the errors. Nothing you can do in the registry to stop that
except to remove the bad drive. All operating systems work this way for data safe
guarding and other reaons (such as stability etc).. It's not up to the operating
system to try and diagnose a drive to see if it can be used or not. That is way to
complicated and specialized. Some errors are non fatal and can just be a problem
for data integraty or, as in your case, this error is fatal and stops everything.
Sorry..
On Friday, September 30, 2005 at 5:35 am, nick wrote:
>
>here's an update to what i've been trying, i put both drives in the old PC to try
>that, same thing the 2nd drive won't spin up, dead as a doornail....in the meantime
>i re-installed another version of win2k on another drive and can boot the new pc
>off of that one, i put the /sos flag on that bootup and exactly where the other
one
>crashes the new one says 'checking drive c: for errors, drive d: for errors' etc.
>so the drive that's failing is failing at the point where it goes thru the drives
>in the system. the error message from the bad boot says 'inacessible boot device'
>and the address is 0x0000007B. i read somewhere that the system configuration hive
>is volatile and re-created every time at bootup, why does it try to find an inaccessible
>boot device then?? can anybody point me to a hive and key where i could manually
>go in and remove the pointer to the missing drive??
|
All messages in this thread [show all]
 | | |  | re: Failed (non-boot) Hard drive halts windows bootup!? (C K: Fri, Sep 30, 2005, 10:11 am) |
| |
| |
| |
Return to the Windows 2000 Discussion Forum
|
|
