In article <ei6j2icWGHA.1192@TK2MSFTNGP03.phx.gbl>,
"DL" <dl@spoofmail.nothere> wrote:

I ran chkdsk from the recovery console, and it found "one or more"
unrecoverable problems.

I then made a diagnostics disk from the WEstern Digital web site. Ran
the diagnostics and they came up clean.

Restarted computer and after the Windows 2000 splash screen, I got a
screen I'd never seen before, where a three-step chkdsk process ran. At
the conclusion of that, the screen went black and the computer again
rebooted.

This time, it started fine, going right to Windows.

My Norton Antivirus 2004 had run just yesterday, with a definitions file
from yesterday, finding no viruses. I'm doing another scan of the
system right now.

So I *think* I'm okay.

Except this computer has never done that before, and I'm worried about
why I'd get a consistent inaccessible boot device error, that would then
disappear after I ran diagnostics that found no errors.

Any ideas what happened, and what my next step should be for complete
peace of mind?

In news:none-41C5B0.21533506042006@syrcnyrdrs-02-ge0.nyroc.rr.com,
qwerty spewed forth:
Probably. But...

Backup backup backup. VERIFY the backups.

We had a computer at work which had odd intermittent boot errors. Chkdisk
seldom found problems, but the system would run again. (One time we had to
replace ntldr.) We ended up getting the drive replaced, even though the
diagnostics never showed any errors. Guess what? Problem hasn't been back
since.

So BACKUP the data and settings. Just in case...

--
My wife and I divorced over religious differences. She thought she was
God and I didn't.

At this stage I would ensure I had full data backups
Perhaps this is a sign of a bad/dry connection?
Its a while since I used the WD utility, if it has an intensive test option
I would run this.
Presumably your sys clock is not loosing an inordinate amount of time? -
caused by failing battery

"qwerty" <none@none.qwerty> wrote in message
news:none-41C5B0.21533506042006@syrcnyrdrs-02-ge0.nyroc.rr.com...

"qwerty" <none@none.qwerty> wrote in message
news:none-41C5B0.21533506042006@syrcnyrdrs-02-ge0.nyroc.rr.com...
Qwerty

Two machines I've done come to mind:
Both displayed weird boot up symptoms.
Both showed errors when using 'chkdsk/r' from the recovery console.
Both took an inordinate amount of time to chkdsk.
Both drives came up clean with their respective makers low level (hardware)
diagnostic's.
Both drives showed errors in the file structure using the makers file
testing routine even though the hardware test was OK (Seagate)
No virus's/malware were detected on either drive when mounted as a slave in
a testing PC.

In both cases 'after backing up user data' the drives were zero'd out
(makers utility to write 0's to every part of the drive)
Windows was then installed using the standard routines (boot from CD).

Neither machine has played up since, one is now over two years since, the
other 3 weeks.

In my opinion the file structure got so screwed up 'nothing' would have
fixed it.
As to the cause............................................. ....?

Conclusion
Backup your data.
Wipe the drive, test the drive with the makers utility.
If the utility reports it's clear, reinstall.
If the utility reports 'anything' wrong replace the drive. <note the full
stop, there is no other option and it's senseless to try when errors are
reported.

Cheers
Paul.