A
allancarhart
Hi folks,
I'd like you to give me your opinion on the following chain of events.
This is clearly a success story about the use of the recovery console.
Aside from that, I'm hoping that you might be able to shed some light
onto what might have gone wrong.
I have a PC running at home which I built a few years ago. It's
running Windows 2000 with NTFS on an 80GB drive -- The 80GB drive was
an upgrade, about 6 months ago. The drive is hooked up to an ATA-100
controller, built-in to the motherboard. I have not changed any
hardware lately, and always have updated virus protection installed.
We typically hibernate the machine rather than turning it off. So
typically when we turn it on, it's restoring from a hibernation state.
My wife turned on our PC Saturday morning, and found that it just
showed a black screen. I rebooted it, and found that it gave the
boot-up message indicating it couldn't un-hibernate. With the options:
- Delete restoration data and proceed to system boot menu
- Continue with system restart
I tried to make it use the hibernation data. When that didn't work, I
had it delete restoration data and bootup normally.
At this point, I received a blue screen saying:
"INACCESIBLE_BOOT_DEVICE."
I know the second number is important. That was: 0x82014d30
I have searched the web for this hex number, and found no references to
it.
Because I didn't believe this was a hardware problem, I thought it
might be a driver problem. So I thought upgrading to
Windows XP might re-install the necessary drivers. Failing that, I
thought I'd put XP on a new drive, put in the problem drive as a slave,
and try to recover our data.
I booted from the XP CD, and found that the installer saw my disk as
having an unknown partition. So I rebooted, and chose the recovery
console. I was given a C: prompt, and tried to run "DIR", which gave
an error saying "unable to enumerate directory." As a final last-ditch
effort, I tried running chkdsk /r /p. It seemed to happily do it
check. It gave a few lines of output indicating it was checking the
disk, followed by a percentage complete.
There was no further output, although I did notice that
at about 66%, the percentage dropped to 50%. Eventually, the chkdsk
completed, saying only that it had fixed some errors.
When I tried "DIR" again, I saw all my files listed. HALLELUJAH! I ran
chkdsk a second time just to be sure, and came back with
a clean bill of health. The second time only, chkdsk told me the name
of my volume. One odd thing is, it said the volume had been created
1-1-1980.
I rebooted my system, and W2K came up just fine -- Like nothing had
ever happened. There were no relevant errors in the event log, and no
indication of any further problems.
My question to you folks is basically: What is the most likely
explanation? Corruption at the filesystem level, is my only guess.
How worried should I be about the stability of my system? Other than
the obvious "Perform a backup now!" advice, any thoughts or help you
could offer would be appreciated.
Thank you,
Allan Carhart
(e-mail address removed)
I'd like you to give me your opinion on the following chain of events.
This is clearly a success story about the use of the recovery console.
Aside from that, I'm hoping that you might be able to shed some light
onto what might have gone wrong.
I have a PC running at home which I built a few years ago. It's
running Windows 2000 with NTFS on an 80GB drive -- The 80GB drive was
an upgrade, about 6 months ago. The drive is hooked up to an ATA-100
controller, built-in to the motherboard. I have not changed any
hardware lately, and always have updated virus protection installed.
We typically hibernate the machine rather than turning it off. So
typically when we turn it on, it's restoring from a hibernation state.
My wife turned on our PC Saturday morning, and found that it just
showed a black screen. I rebooted it, and found that it gave the
boot-up message indicating it couldn't un-hibernate. With the options:
- Delete restoration data and proceed to system boot menu
- Continue with system restart
I tried to make it use the hibernation data. When that didn't work, I
had it delete restoration data and bootup normally.
At this point, I received a blue screen saying:
"INACCESIBLE_BOOT_DEVICE."
I know the second number is important. That was: 0x82014d30
I have searched the web for this hex number, and found no references to
it.
Because I didn't believe this was a hardware problem, I thought it
might be a driver problem. So I thought upgrading to
Windows XP might re-install the necessary drivers. Failing that, I
thought I'd put XP on a new drive, put in the problem drive as a slave,
and try to recover our data.
I booted from the XP CD, and found that the installer saw my disk as
having an unknown partition. So I rebooted, and chose the recovery
console. I was given a C: prompt, and tried to run "DIR", which gave
an error saying "unable to enumerate directory." As a final last-ditch
effort, I tried running chkdsk /r /p. It seemed to happily do it
check. It gave a few lines of output indicating it was checking the
disk, followed by a percentage complete.
There was no further output, although I did notice that
at about 66%, the percentage dropped to 50%. Eventually, the chkdsk
completed, saying only that it had fixed some errors.
When I tried "DIR" again, I saw all my files listed. HALLELUJAH! I ran
chkdsk a second time just to be sure, and came back with
a clean bill of health. The second time only, chkdsk told me the name
of my volume. One odd thing is, it said the volume had been created
1-1-1980.
I rebooted my system, and W2K came up just fine -- Like nothing had
ever happened. There were no relevant errors in the event log, and no
indication of any further problems.
My question to you folks is basically: What is the most likely
explanation? Corruption at the filesystem level, is my only guess.
How worried should I be about the stability of my system? Other than
the obvious "Perform a backup now!" advice, any thoughts or help you
could offer would be appreciated.
Thank you,
Allan Carhart
(e-mail address removed)