Re: CHKDSK at startup / Win2K

What happens if you run;

chkdsk /r
from the recovery console command line. (/r implies /f and /p)

To start the Recovery Console, start the computer from the Windows 2000 Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup floppy disks and your computer cannot start from the Windows 2000 Setup CD, use another Windows 2000-based computer to create the Setup floppy disks. At the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000 installation, and then press C to use the Recovery Console. The Recovery Console then prompts you for the administrator password. If you do not have the correct password, Recovery Console does not allow access to the computer. If an incorrect password is entered three times, the Recovery Console quits and restarts the computer. Note If the registry is corrupted or missing or no valid installations are found, the Recovery Console starts in the root of the startup volume without requiring a password. You cannot access any folders, but you can carry out commands such as chkdsk, fixboot, and fixmbr for limited disk repairs. Once the password has been validated, you have full access to the Recovery Console, but limited access to the hard disk. You can only access the following folders on your computer: drive root, %systemroot% or %windir%


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Riskman" wrote:
I tried to run Error Checking (CHKDSK) on my Win2K Pro, and selected both
options to auto fix file system errors and scan/attempt recovery of bad
sectors. A popup window advised it would require running at startup, so I
OK'd the schedule, then restarted system to allow CHKDSK to scan, fix,
recover. CHKDSK proceeded thru its 5 phases, completed each to 100% with no
apparent issue, but upon completing the last phase the system moved to a blue
screen with the following stop error:

*** STOP: 0x0000000A (0xC0001C8C, 0x00000002, 0x00000000, 0x8043832C)
IRQL_NOT_LESS_OR_EQUAL

*** Address 8043832C base at 80400000, DateStamp 45ec3c8f - ntoskrnl.exe

"If this is the first time you've seen this Stop error screen, restart your
computer. If this screen appears again, follow these steps:

"Check to make sure any new hardware or software is properly installed. If
this is a new installation, ask your hardware or software manufacturer for
any Windows 2000 updates you might need.

"If this problem continues, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing. Check
your hard drive to make sure it is properly configured and terminated. If you
need to use Safe Mode to remove or disable components, restart your computer,
press F8 to select Advanced Startup Options and then select Safe Mode.

"Refer to your Getting Started manual for more information on
troubleshooting Stop errors."

OK, so following this blue screen I did restart, tried to envoke Safe Mode
but then the scheduled CHKDSK started again, during which the keyboard is
completely unresponsive and does not let you opt to bypass the CHKDSK scan.
It goes thru the full scan with precisely the same results each time, each
phase 100% complete then jumps to the same blue screen. The result is an
endless loop of CHKDSK...

How can I get into a command prompt prior to CHKDSK starting so that I can
either rename the CHKDSK file ot the AUTOCHK file so that I can proceed to
booting into Windows? Otherwise, what other alternatives can you suggest?
If you suggest a quick boot disk, please advise specific files I would need
(keep in mind this is Win2K and not the easier WinXP) in order to be able to
see the NTFS files on C:.. A bootable disk I created with an XP machine
would not let me get beyond A: (i.e. I could not redirect to C: on the Win2K
machine), so there must have been some necessary files missing, but I do not
know which ones.


.

Relevant Pages

  • Re: Invalid boot.ini file
    ... Don't know what a command prompt is. ... how would one "use another Windows 2000-based computer to create the ... > If it is missing then you can start the recovery console and from a command ... > Setup CD or the Windows 2000 Setup floppy disks. ...
    (microsoft.public.win2000.general)
  • Re: Win2k wont boot- SYSTEMd F8 file error
    ... If the system hive is corrupt, and assuming you already tried LKG (F8 and ... To start the Recovery Console, start the computer from the Windows 2000 ... Setup CD or the Windows 2000 Setup floppy disks. ... use another Windows 2000-based computer to create the Setup floppy disks. ...
    (microsoft.public.win2000.new_user)
  • Re: Corrupted registry, no floppy drive for regchk
    ... You'll need to reinstall the device drivers for any hardware added since the original OS install. ... To start the Recovery Console, start the computer from the Windows 2000 Setup CD or the Windows 2000 Setup floppy disks. ... If you do not have Setup floppy disks and your computer cannot start from the Windows 2000 Setup CD, use another Windows 2000-based computer to create the Setup floppy disks. ...
    (microsoft.public.win2000.general)
  • Re: finding fail-safe default for XP laptop
    ... To salvage your files you will have to remove the disk from the ... Using the Recovery Console is usually quite safe, ... chkdsk, this is true even if you have no perceived problems with the ... Windows installation. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: PLEASE HELP: 2 ERROR MESSAGES
    ... recognise CHKDSK/F or CHKDSK /F), then I type in FIXBOOT and it asks: ... It seems as though it would not boot from the CD ... Which windows installation would you like to log onto (To cancel, ... into recovery console. ...
    (microsoft.public.windowsxp.general)