Have lost ability to run chkdsk /f on reboot. From cmd in Windows, indicates
errors are present, chkdsk /f will run on next reboot - but it DOESN'T...
help?

Try fsutil dirty

http://technet2.microsoft.com/window....mspx?mfr=true

"davdun75" wrote:

> Have lost ability to run chkdsk /f on reboot. From cmd in Windows, indicates
> errors are present, chkdsk /f will run on next reboot - but it DOESN'T...
> help?

Hi

I am using Xp Pro with NTFS file format. When ever there is unexpected power
failure or unexpected shut down then my system is not performing automatic
disc check for errors(saying system will perform error check....press any
key to cancel) which XP generally performs under such situations but opens
normally.Any idea why its not performing automatic disc check??

dheeraj jatwani wrote:
> I am using Xp Pro with NTFS file format. When ever there is
> unexpected power failure or unexpected shut down then my system is
> not performing automatic disc check for errors(saying system will
> perform error check....press any key to cancel) which XP generally
> performs under such situations but opens normally.Any idea why its
> not performing automatic disc check??

What makes you think that everytime there is some unexpected occurance, it
should perform a CHKDSK?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

"dheeraj jatwani" <(E-Mail Removed)> wrote in
message news:1F39C192-CD3E-4044-9877-(E-Mail Removed)...
> Hi
>
> I am using Xp Pro with NTFS file format. When ever there is unexpected
> power
> failure or unexpected shut down then my system is not performing automatic
> disc check for errors(saying system will perform error check....press any
> key to cancel) which XP generally performs under such situations but opens
> normally.Any idea why its not performing automatic disc check??

Although you cannot see it, a DLL loads at boot and does a preliminary check
of your disk. It checks to see if further disk checking / repair is
necessary! I frequently have power go off while the OS is up and upon start
everything is fine, no chkdsk is necessary.

Agreed'
NTFS is a lot more stable than FAT32
It doesn't automatically Need to be fixed...

I've seen it fix it self when it spotted an issue.
(I've never seen FAT32 do this )

Here is something that might help
http://www.theeldergeek.com/ntfs_or_...ile_system.htm

Russ

--
Russell Grover - SBITS.Biz [SBS-MVP]
Microsoft Gold Certified Partner
Microsoft Certified Small Business Specialist
24hr SBS Remote Support - www.SBITS.Biz
Question or Second Opinion $25.00 - www.PersonalITConsultant.com
Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com


"Shenan Stanley" <(E-Mail Removed)> wrote in message
news:OiAzB$(E-Mail Removed)...
> dheeraj jatwani wrote:
>> I am using Xp Pro with NTFS file format. When ever there is
>> unexpected power failure or unexpected shut down then my system is
>> not performing automatic disc check for errors(saying system will
>> perform error check....press any key to cancel) which XP generally
>> performs under such situations but opens normally.Any idea why its
>> not performing automatic disc check??
>
> What makes you think that everytime there is some unexpected occurance, it
> should perform a CHKDSK?
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>

On Feb 7, 12:52*pm, dheeraj jatwani
<dheerajjatw...@discussions.microsoft.com> wrote:
> Hi
>
> I am using Xp Pro with NTFS file format. When ever there is unexpected power
> failure or unexpected shut down then my system is not performing automatic
> disc *check for errors(saying system will perform error check....press any
> key to cancel) which XP generally performs under such situations but opens
> normally.Any idea why its not performing automatic disc check??

A power interruption will sometimes result in the dirty bit being set
for a volume. A power interruption may not result in the dirty bit
being set. Since a power interruption is an unnatural way (not
graceful) to shutdown the system, it is a good thing to let chkdsk run
when XP thinks it is necessary. XP is doing what it is supposed to do
to try to make sure things are okay after being insulted.

Normally, each volume will be checked by autochk when XP starts to
load. If the dirty bit is set on a volume, chkdsk will run. If the
dirty bit is not set, chkdsk will not run - but the volume will be
checked.

If chkdsk completes successfully, the dirty bit will be cleared and
chkdsk will not run again on the next reboot (unless the volume is
dirty again).

When chkdsk runs automatically on a reboot, the results are shown in
the Event Viewer Application log sourced by Winlogon:

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Description:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

39070048 KB total disk space.
25151976 KB in 78653 files.
48256 KB in 10264 indexes.
0 KB in bad sectors.
237080 KB in use by the system.
65536 KB occupied by the log file.
13632736 KB available on disk.

4096 bytes in each allocation unit.
9767512 total allocation units on disk.
3408184 allocation units available on disk.

Windows has finished checking your disk.
Please wait while your computer restarts.

"Trying" fsutil dirty will not tell you anything - it is not even a
complete command, but you can certainly try it.

Using fsutil you can set or query the dirty bit on a volume, but you
cannot clear the dirty bit with fsutil.

Assuming the drive is C, open a command window by clicking Start, Run
and in the box enter:

cmd

Clcik OK to open a command window.

To query the dirty bit, execute the following command:

fsutil dirty query c:

To set the dirty bit, execute the following command:

fsutil dirty set C:

If you set the dirty bit and reboot, expect chkdsk to run on the next
reboot.

NTFS volumes are designed to reduce the likelihood of errors and
fragmentation, but they are not immune to either.

Designed to prevent it, but not immune to either.