chkdsk after bad shutdown

  • Thread starter Thread starter beatme101
  • Start date Start date
B

beatme101

Is there any way to force Windows 2000 Professional to run chkdsk on
all hard drives unconditionally when starting up after a bad shutdown,
or is this only a feature of Windows 98?
 
This article may help.

CHKNTFS.EXE: What You Can Use It For
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q160963

--

Regards,

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

| Is there any way to force Windows 2000 Professional to run chkdsk on
| all hard drives unconditionally when starting up after a bad shutdown,
| or is this only a feature of Windows 98?
|
 
Thanks, I have just done chkntfs /D, guess since it didn't tell me if
anything was changed I will have to wait until the next bad shutdown
happens to see if there are results.
 
Well, it's been a while, but a power outage finally happenned, and
guess what, it didn't work, chkdsk did not automatically run for EITHER
of the drives (I want it to run for both), I had to start up into
windows (having all my startup programs potentially corrupt their
various files by writing to them early), go to the command prompt, and
put in chkdsk /f on each drive and then restart.

Is an automatic scan really only a feature of Windows 98? Kind of sad
that it has been removed.

Thanks, I have just done chkntfs /D, guess since it didn't tell me if
anything was changed I will have to wait until the next bad shutdown
happens to see if there are results.


Dave said:
This article may help.

CHKNTFS.EXE: What You Can Use It For
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q160963

--

Regards,

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

| Is there any way to force Windows 2000 Professional to run chkdsk on
| all hard drives unconditionally when starting up after a bad shutdown,
| or is this only a feature of Windows 98?
|
Click to expand...
Click to expand...
 
What did you expect chkntfs /D to do? A power outage is not guaranteed to
set the dirty bit.

From a command prompt;

fsutil dirty query C:

to check the state of the dirty bit.

If a volume's dirty bit is set, this indicates that the file system may be
in an inconsistent state. The dirty bit can be set because the volume is
online and has outstanding changes, because changes were made to the volume
and the computer shutdown before the changes were committed to disk, or
because corruption was detected on the volume. If the dirty bit is set when
the computer restarts, chkdsk runs to verify the consistency of the volume.

When Autochk runs against a volume at boot time it records its output to a
file called Bootex.log in the root of the volume being checked. The Winlogon
service then moves the contents of each Bootex.log file to the Application
Event log. One event log message for each volume checked is recorded. So
check the application event log.

--

Regards,

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

| Well, it's been a while, but a power outage finally happenned, and
| guess what, it didn't work, chkdsk did not automatically run for EITHER
| of the drives (I want it to run for both), I had to start up into
| windows (having all my startup programs potentially corrupt their
| various files by writing to them early), go to the command prompt, and
| put in chkdsk /f on each drive and then restart.
|
| Is an automatic scan really only a feature of Windows 98? Kind of sad
| that it has been removed.
 
That's interesting, I thought the dirty bit was set when Windows
started up right up until shut down. Windows 98 seemed to do much
better at this than Windows 2000 is doing.. Kind of sad that I have to
log in and let all my programs corrupt their files before I can tell
chkdsk to do anything.
 
It would seem to make sense wouldn't it? However, I've experienced
occasionally (not a repeated problem) a condition where my system has
hung for some reason with no programs open and nothing in process and
had to use the power switch to get out of it.

Not uncommonly, chkdsk won't run at next boot and if I specifically run
it (from a Bart's Boot) there are no problems with the drive.

Seems Windows is a bit more intelligent when setting the dirty bit.
 
Only when necessary. From a command prompt;

fsutil dirty query C:

to check the state of the dirty bit.


--

Regards,

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

| That's interesting, I thought the dirty bit was set when Windows
| started up right up until shut down. Windows 98 seemed to do much
| better at this than Windows 2000 is doing.. Kind of sad that I have to
| log in and let all my programs corrupt their files before I can tell
| chkdsk to do anything.
 
Back
Top