Do no harm...



Hi all

I've been running a robust and problem-free W2K installation with all updates installed for over a year. Ignoring the old adage, "if ain't broke, don't fix it," I thought I'd be proactive and run a chkdsk to catch any potential problems before they bite me.

To accomplish this task I went to the the Disk Management screen, selected tools from the properties menu and invoked the check disk routine. I checked off both boxes: automatically fix errors and scan for and attempt recovery of bad sectors.

The computer rebooted as expected and began its scan. Here, I noticed the first anomaly. I could not see a progress window. Since I have disabled the gui boot all I see on bootup is a list of drivers. This list remained on the screen while the scan was proceeding instead of being replaced by the usual chkdsk progress display. Did this happen because I disabled the gui boot, or was there something more sinister going on?

The drive light flashed for about 5-10 minutes and then stopped, with the static list of loaded drivers still visible on the screen. Was there supposed to be some kind of prompt or instructions that I was not seeing? After about 15 minutes I tired of waiting and rebooted. The scan ran again upon reboot and the same thing happened. This time I let it sit there for a much longer time.

I left the room for a few minutes and when I returned, it had booted to a blue screen warning me that no bootable device was to be found. Further testing and investigation with the Recovery Console revealed that the Windows installation on the disk was no longer recognized. No NTFS file system, no drive letter, no disk name, nothing.

The disk is a SATA drive that appears to be in good shape. I was able to restore the system with Ghost from a mirror drive I had updated a few weeks ago and it's running just fine.

So what happened? Like doctors whose first rule is to do no harm, one would expect diagnostic software to follow the same credo. Even if it runs into problems, it should not make them worse. I'm afraid to ever run chkdsk again!

Your insights would be much appreciated.

Casian
.



Relevant Pages

  • Re: Why most run Microsoft, not RedHat
    ... How would you repair an XP installation that continuously reboots after installing a USB keyboard and SATA drivers? ... I did check for minidumps from the ultimate Microsoft OS (always in automatic reboot mode) after installing W2k in the same partition. ... I could not remove the SATA drive since the installation was on that disk. ... "tech support" and finally got the disk and did a clean install to get ...
    (Fedora)
  • RE: Exchange 2000 ms02-025 hotfix Q320436 caused SA to hang on re start[Scanned]
    ... you need to do two things to fix it. ... Delete it and reboot your machine... ... Exchange 2000 ms02-025 hotfix Q320436 caused SA to hang on ... * After hotfix installation, the installer starts up Exchange services. ...
    (Focus-Microsoft)
  • Re: Why most run Microsoft, not RedHat
    ... How would you repair an XP installation that continuously reboots ... minidumps from the ultimate Microsoft OS (always in automatic reboot ... drive since the installation was on that disk. ... You can get out of the chkdsk by pressing esc, ...
    (Fedora)
  • Re: Windows Logs Out Without Logging In
    ... then reboot? ... but doesn't correct the registry damage. ... another installation ... >that includes only a Restore CD, or no disk at all. ...
    (microsoft.public.windowsxp.general)
  • Re: Lite-On CD-RW disappeared from Windows
    ... See Alex Nichol's fix at: ... no it is not listed in disk manager. ... > mins. I've been asked to reboot. ... Still Error Code 19 - my registry might be ...
    (microsoft.public.win2000.hardware)