Checking & Verifying Disk after hard reboot

[Lfiorese]

I have several IBM machines running Windows 2000 Professional. On the rare instance that a machine is rebooted without going through the shutdown procedure, it goes through a checking and verifying disk program that takes close to 3 hours! I remember in Win98 and earlier this was a much faster process. Is this normal with Win2000?

 

[bcastner]

Are the users doing the hard reboot because of possible problems that could be traced to hard disk problems?

Something is setting the 'dirty' bit, and it is not a hard reboot. There is a hard drive issue. If the drives were fine the chkdsk upoun startup would complete in well less than 3 minutes and not 3 hours.

 

[computerhighguy]

The dirty bit is set if the system does not sucessfully shutdown (or there are disk errors, check the event log). Checkdisk will run at bootup if the dirtybit is set. 3 hours is a LONG LONG LONG time. I would say one of the following is the problem.

IDE Drive: If the system has an IDE drive, then the drive is probably going bad. Even on my systems with multiple 250GB+ drives, checkdisk only take a few minutes.

SCSI Drives: The raid controller or controller cable is going bad.

Page file: The page file could be non-existant. Without a page file, the system could take a long time to boot if it runs check disk.

Checkdisk: Checkdisk and the OS could be hosed. If they all came from the same image and there is no hardware issues, then your image is bad.

Even a boot time directory consolidation from Diskeeper doesn't usually take that long.