This morning, I turned on my computer and, before I knew it, it was doing a
5- minute chkdsk, saying my file system is NTFS and the "volume is dirty".
It deleted three indexes, one of which was in Outlook.exe. I have more
details of index and file #'s if anyone wants them.

I don't recall that chkdsk is something one expects upon booting. Though
everything seems fine, I am curious why this happened. Is this just some
sort of automatic maintenance when XP detects a problem while trying to boot
up?

Thanks!
Dean

On 4/10/2007 9:23 AM On a whim, Dean pounded out on the keyboard

> This morning, I turned on my computer and, before I knew it, it was doing a
> 5- minute chkdsk, saying my file system is NTFS and the "volume is dirty".
> It deleted three indexes, one of which was in Outlook.exe. I have more
> details of index and file #'s if anyone wants them.
>
> I don't recall that chkdsk is something one expects upon booting. Though
> everything seems fine, I am curious why this happened. Is this just some
> sort of automatic maintenance when XP detects a problem while trying to boot
> up?
>
> Thanks!
> Dean
>
>

Hi Dean,

Yes, it is. I would make sure you have a current backup. You could
have an impending hard drive failure.

--
Terry

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

Hi Dean... see this discussion and remedy here at

http://discussions.virtualdr.com/sho...d.php?t=192763


"Dean" <(E-Mail Removed)> wrote in message
news:Xb-(E-Mail Removed)...
> This morning, I turned on my computer and, before I knew it, it was doing
> a 5- minute chkdsk, saying my file system is NTFS and the "volume is
> dirty". It deleted three indexes, one of which was in Outlook.exe. I have
> more details of index and file #'s if anyone wants them.
>
> I don't recall that chkdsk is something one expects upon booting. Though
> everything seems fine, I am curious why this happened. Is this just some
> sort of automatic maintenance when XP detects a problem while trying to
> boot up?
>
> Thanks!
> Dean
>

Check Disk runs on every boot.

Open a command prompt...
Start | Run | Type: cmd | Click OK |
Type or paste the following line:

chkntfs /d

Hit the Enter key.

Chkntfs displays or modifies the checking of disks at boot time.

The /d switch restores the machine to the default behavior; all drives are
checked at boot time and chkdsk is run on those that are dirty.

Autochk.exe is a version of Chkdsk that runs only before Windows XP
starts. Autochk runs in the following situations:

Autochk runs if you try to run Chkdsk on the boot volume.
Autochk runs if Chkdsk cannot gain exclusive use of the volume.
Autochk runs if the volume is flagged as dirty.

This can happen if the drive's dirty bit is set.
When a drive's dirty bit is set, autochk automatically
checks the volume for errors the next time the computer is restarted.

This will report whether the dirty bit is set.

Start | Run | Type: cmd | Click OK |
Type or paste the following line:

fsutil dirty query C:

Hit the Enter key.

Volume C: is not dirty
Volume C: is dirty

<quote>
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.

Every time Windows XP starts, Autochk.exe is called by the Kernel to scan
all volumes to check if the volume dirty bit is set. If the dirty bit is
set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f
verifies file system integrity and attempts to fix any problems with the
volume
<quote>
-----

This will also report whether the dirty bit is set.

Start | Run | Type: cmd | Click OK |
Type or paste the following line:

chkntfs c:

Hit the Enter key.

C: is not dirty.
-----

If this is not the problem.....

Go here:
http://www.kellys-korner-xp.com/xp_tweaks.htm

Read the instructions at the top of the page.
Scroll down to:
82. Disable or Enable Check Disk Upon Boot
Click on Disable.
-----

Additional information...
Chkdsk.exe or Autochk.exe starts when you try to shut down or restart your
computer
http://support.microsoft.com/kb/831426

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:Xb-(E-Mail Removed),
Dean <(E-Mail Removed)> hunted and pecked:
> This morning, I turned on my computer and, before I knew it, it was doing
> a 5- minute chkdsk, saying my file system is NTFS and the "volume is
> dirty". It deleted three indexes, one of which was in Outlook.exe. I
> have more details of index and file #'s if anyone wants them.
>
> I don't recall that chkdsk is something one expects upon booting. Though
> everything seems fine, I am curious why this happened. Is this just some
> sort of automatic maintenance when XP detects a problem while trying to
> boot up?
>
> Thanks!
> Dean

Thanks, Wes.

I tried both of the commands to see if it was still dirty though, from what
I can figure out, chkdsk is supposed to have fixed it, I think.
Unfortunately, with either command, the screen popped up and disappeared
almost instantaneously, with no time to read it at all. Is there a way to
alter the command so that the result stays in the command dos prompt box so
I can read it?

Your info plus all the links sent by others was a little more info than I
could process. I can't really tell from reading them if I should expect I
have any problem now. More generally, I did reboot, after using the
computer for a couple of hours with no problem, and the reboot was fine too.
Is there really any reason to be concerned about the hard disk being almost
dead or anything? Also Outlook seems fine and two of the three deleted
indexes were associated with Outlook The other index deleted was
A0053534.ini, in case that means anything to anyone - a Google search with
that got zero hits.

Thanks so much.

Dean


"Wesley Vogel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Check Disk runs on every boot.
>
> Open a command prompt...
> Start | Run | Type: cmd | Click OK |
> Type or paste the following line:
>
> chkntfs /d
>
> Hit the Enter key.
>
> Chkntfs displays or modifies the checking of disks at boot time.
>
> The /d switch restores the machine to the default behavior; all drives are
> checked at boot time and chkdsk is run on those that are dirty.
>
> Autochk.exe is a version of Chkdsk that runs only before Windows XP
> starts. Autochk runs in the following situations:
>
> Autochk runs if you try to run Chkdsk on the boot volume.
> Autochk runs if Chkdsk cannot gain exclusive use of the volume.
> Autochk runs if the volume is flagged as dirty.
>
> This can happen if the drive's dirty bit is set.
> When a drive's dirty bit is set, autochk automatically
> checks the volume for errors the next time the computer is restarted.
>
> This will report whether the dirty bit is set.
>
> Start | Run | Type: cmd | Click OK |
> Type or paste the following line:
>
> fsutil dirty query C:
>
> Hit the Enter key.
>
> Volume C: is not dirty
> Volume C: is dirty
>
> <quote>
> 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.
>
> Every time Windows XP starts, Autochk.exe is called by the Kernel to scan
> all volumes to check if the volume dirty bit is set. If the dirty bit is
> set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f
> verifies file system integrity and attempts to fix any problems with the
> volume
> <quote>
> -----
>
> This will also report whether the dirty bit is set.
>
> Start | Run | Type: cmd | Click OK |
> Type or paste the following line:
>
> chkntfs c:
>
> Hit the Enter key.
>
> C: is not dirty.
> -----
>
> If this is not the problem.....
>
> Go here:
> http://www.kellys-korner-xp.com/xp_tweaks.htm
>
> Read the instructions at the top of the page.
> Scroll down to:
> 82. Disable or Enable Check Disk Upon Boot
> Click on Disable.
> -----
>
> Additional information...
> Chkdsk.exe or Autochk.exe starts when you try to shut down or restart your
> computer
> http://support.microsoft.com/kb/831426
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news:Xb-(E-Mail Removed),
> Dean <(E-Mail Removed)> hunted and pecked:
>> This morning, I turned on my computer and, before I knew it, it was doing
>> a 5- minute chkdsk, saying my file system is NTFS and the "volume is
>> dirty". It deleted three indexes, one of which was in Outlook.exe. I
>> have more details of index and file #'s if anyone wants them.
>>
>> I don't recall that chkdsk is something one expects upon booting. Though
>> everything seems fine, I am curious why this happened. Is this just some
>> sort of automatic maintenance when XP detects a problem while trying to
>> boot up?
>>
>> Thanks!
>> Dean
>

Thanks CJ. I did not get a BSOD or anything like that, as suggested in the
thread sent to me. It seems to suggest that chkdsk should fix things, but
that is not completely clear. Terry seems to suggest I could be in for an
impending hard disk crash.

D

"C J." <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Dean... see this discussion and remedy here at
>
> http://discussions.virtualdr.com/sho...d.php?t=192763
>
>
> "Dean" <(E-Mail Removed)> wrote in message
> news:Xb-(E-Mail Removed)...
>> This morning, I turned on my computer and, before I knew it, it was doing
>> a 5- minute chkdsk, saying my file system is NTFS and the "volume is
>> dirty". It deleted three indexes, one of which was in Outlook.exe. I
>> have more details of index and file #'s if anyone wants them.
>>
>> I don't recall that chkdsk is something one expects upon booting. Though
>> everything seems fine, I am curious why this happened. Is this just some
>> sort of automatic maintenance when XP detects a problem while trying to
>> boot up?
>>
>> Thanks!
>> Dean
>>
>
>

Hi Dean,

If chkdsk ran and the volume is no longer dirty then there is no problem.

Did you type or paste fsutil dirty query C: into a command prompt or
into the Run command? I think you typed it into the Run command. Start |
Run is the Run command.

Paste the following line into Start | Run and click OK...

cmd /K fsutil dirty query C:

Did a command prompt open and stay open? Look a the very first line;
Volume - C: is....

To open a command prompt, click Start, click Run, type: cmd into the
Open box and click OK.

Then type: fsutil dirty query C: and hit your Enter key.
------------

In the chkdsk log if you see something similar to this...

Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.

[[Chkdsk.exe just reclaims the unused security descriptors as a housekeeping
activity, and it does not actually fix any kind of problem. ]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news4adnWEa6-(E-Mail Removed),
Dean <(E-Mail Removed)> hunted and pecked:
> Thanks, Wes.
>
> I tried both of the commands to see if it was still dirty though, from
> what I can figure out, chkdsk is supposed to have fixed it, I think.
> Unfortunately, with either command, the screen popped up and disappeared
> almost instantaneously, with no time to read it at all. Is there a way to
> alter the command so that the result stays in the command dos prompt box
> so I can read it?
>
> Your info plus all the links sent by others was a little more info than I
> could process. I can't really tell from reading them if I should expect I
> have any problem now. More generally, I did reboot, after using the
> computer for a couple of hours with no problem, and the reboot was fine
> too. Is there really any reason to be concerned about the hard disk being
> almost dead or anything? Also Outlook seems fine and two of the three
> deleted indexes were associated with Outlook The other index deleted was
> A0053534.ini, in case that means anything to anyone - a Google search with
> that got zero hits.
>
> Thanks so much.
>
> Dean
>
>
> "Wesley Vogel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Check Disk runs on every boot.
>>
>> Open a command prompt...
>> Start | Run | Type: cmd | Click OK |
>> Type or paste the following line:
>>
>> chkntfs /d
>>
>> Hit the Enter key.
>>
>> Chkntfs displays or modifies the checking of disks at boot time.
>>
>> The /d switch restores the machine to the default behavior; all drives
>> are checked at boot time and chkdsk is run on those that are dirty.
>>
>> Autochk.exe is a version of Chkdsk that runs only before Windows XP
>> starts. Autochk runs in the following situations:
>>
>> Autochk runs if you try to run Chkdsk on the boot volume.
>> Autochk runs if Chkdsk cannot gain exclusive use of the volume.
>> Autochk runs if the volume is flagged as dirty.
>>
>> This can happen if the drive's dirty bit is set.
>> When a drive's dirty bit is set, autochk automatically
>> checks the volume for errors the next time the computer is restarted.
>>
>> This will report whether the dirty bit is set.
>>
>> Start | Run | Type: cmd | Click OK |
>> Type or paste the following line:
>>
>> fsutil dirty query C:
>>
>> Hit the Enter key.
>>
>> Volume C: is not dirty
>> Volume C: is dirty
>>
>> <quote>
>> 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.
>>
>> Every time Windows XP starts, Autochk.exe is called by the Kernel to scan
>> all volumes to check if the volume dirty bit is set. If the dirty bit is
>> set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f
>> verifies file system integrity and attempts to fix any problems with the
>> volume
>> <quote>
>> -----
>>
>> This will also report whether the dirty bit is set.
>>
>> Start | Run | Type: cmd | Click OK |
>> Type or paste the following line:
>>
>> chkntfs c:
>>
>> Hit the Enter key.
>>
>> C: is not dirty.
>> -----
>>
>> If this is not the problem.....
>>
>> Go here:
>> http://www.kellys-korner-xp.com/xp_tweaks.htm
>>
>> Read the instructions at the top of the page.
>> Scroll down to:
>> 82. Disable or Enable Check Disk Upon Boot
>> Click on Disable.
>> -----
>>
>> Additional information...
>> Chkdsk.exe or Autochk.exe starts when you try to shut down or restart
>> your computer
>> http://support.microsoft.com/kb/831426
>>
>> --
>> Hope this helps. Let us know.
>>
>> Wes
>> MS-MVP Windows Shell/User
>>
>> In news:Xb-(E-Mail Removed),
>> Dean <(E-Mail Removed)> hunted and pecked:
>>> This morning, I turned on my computer and, before I knew it, it was
>>> doing a 5- minute chkdsk, saying my file system is NTFS and the "volume
>>> is dirty". It deleted three indexes, one of which was in Outlook.exe. I
>>> have more details of index and file #'s if anyone wants them.
>>>
>>> I don't recall that chkdsk is something one expects upon booting. Though
>>> everything seems fine, I am curious why this happened. Is this
>>> just some sort of automatic maintenance when XP detects a problem while
>>> trying to boot up?
>>>
>>> Thanks!
>>> Dean

I don't know where to find the chkdsk log, but I did copy down the 3 things
that showed up as being deleted - all 3 were indexes and two were outlook,
as I mentioned before.

Yes, you were right. I was typing it into the run box. When I do it right
it says Volume C is NOT dirty. So, I am fine now? I think you are also
saying chkdsk does not fix these errors (though I thought I read otherwise
in one of the links one of the other posters supplied). If so, I assume
that something fixed the errors, assuming these 3 deleted indexes were
"errors".

Thanks, Wes!
Dean


"Wesley Vogel" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Dean,
>
> If chkdsk ran and the volume is no longer dirty then there is no problem.
>
> Did you type or paste fsutil dirty query C: into a command prompt or
> into the Run command? I think you typed it into the Run command. Start |
> Run is the Run command.
>
> Paste the following line into Start | Run and click OK...
>
> cmd /K fsutil dirty query C:
>
> Did a command prompt open and stay open? Look a the very first line;
> Volume - C: is....
>
> To open a command prompt, click Start, click Run, type: cmd into the
> Open box and click OK.
>
> Then type: fsutil dirty query C: and hit your Enter key.
> ------------
>
> In the chkdsk log if you see something similar to this...
>
> Cleaning up 10 unused index entries from index $SII of file 0x9.
> Cleaning up 10 unused index entries from index $SDH of file 0x9.
>
> [[Chkdsk.exe just reclaims the unused security descriptors as a
> housekeeping
> activity, and it does not actually fix any kind of problem. ]]
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news4adnWEa6-(E-Mail Removed),
> Dean <(E-Mail Removed)> hunted and pecked:
>> Thanks, Wes.
>>
>> I tried both of the commands to see if it was still dirty though, from
>> what I can figure out, chkdsk is supposed to have fixed it, I think.
>> Unfortunately, with either command, the screen popped up and disappeared
>> almost instantaneously, with no time to read it at all. Is there a way
>> to
>> alter the command so that the result stays in the command dos prompt box
>> so I can read it?
>>
>> Your info plus all the links sent by others was a little more info than I
>> could process. I can't really tell from reading them if I should expect
>> I
>> have any problem now. More generally, I did reboot, after using the
>> computer for a couple of hours with no problem, and the reboot was fine
>> too. Is there really any reason to be concerned about the hard disk being
>> almost dead or anything? Also Outlook seems fine and two of the three
>> deleted indexes were associated with Outlook The other index deleted was
>> A0053534.ini, in case that means anything to anyone - a Google search
>> with
>> that got zero hits.
>>
>> Thanks so much.
>>
>> Dean
>>
>>
>> "Wesley Vogel" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Check Disk runs on every boot.
>>>
>>> Open a command prompt...
>>> Start | Run | Type: cmd | Click OK |
>>> Type or paste the following line:
>>>
>>> chkntfs /d
>>>
>>> Hit the Enter key.
>>>
>>> Chkntfs displays or modifies the checking of disks at boot time.
>>>
>>> The /d switch restores the machine to the default behavior; all drives
>>> are checked at boot time and chkdsk is run on those that are dirty.
>>>
>>> Autochk.exe is a version of Chkdsk that runs only before Windows XP
>>> starts. Autochk runs in the following situations:
>>>
>>> Autochk runs if you try to run Chkdsk on the boot volume.
>>> Autochk runs if Chkdsk cannot gain exclusive use of the volume.
>>> Autochk runs if the volume is flagged as dirty.
>>>
>>> This can happen if the drive's dirty bit is set.
>>> When a drive's dirty bit is set, autochk automatically
>>> checks the volume for errors the next time the computer is restarted.
>>>
>>> This will report whether the dirty bit is set.
>>>
>>> Start | Run | Type: cmd | Click OK |
>>> Type or paste the following line:
>>>
>>> fsutil dirty query C:
>>>
>>> Hit the Enter key.
>>>
>>> Volume C: is not dirty
>>> Volume C: is dirty
>>>
>>> <quote>
>>> 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.
>>>
>>> Every time Windows XP starts, Autochk.exe is called by the Kernel to
>>> scan
>>> all volumes to check if the volume dirty bit is set. If the dirty bit is
>>> set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f
>>> verifies file system integrity and attempts to fix any problems with the
>>> volume
>>> <quote>
>>> -----
>>>
>>> This will also report whether the dirty bit is set.
>>>
>>> Start | Run | Type: cmd | Click OK |
>>> Type or paste the following line:
>>>
>>> chkntfs c:
>>>
>>> Hit the Enter key.
>>>
>>> C: is not dirty.
>>> -----
>>>
>>> If this is not the problem.....
>>>
>>> Go here:
>>> http://www.kellys-korner-xp.com/xp_tweaks.htm
>>>
>>> Read the instructions at the top of the page.
>>> Scroll down to:
>>> 82. Disable or Enable Check Disk Upon Boot
>>> Click on Disable.
>>> -----
>>>
>>> Additional information...
>>> Chkdsk.exe or Autochk.exe starts when you try to shut down or restart
>>> your computer
>>> http://support.microsoft.com/kb/831426
>>>
>>> --
>>> Hope this helps. Let us know.
>>>
>>> Wes
>>> MS-MVP Windows Shell/User
>>>
>>> In news:Xb-(E-Mail Removed),
>>> Dean <(E-Mail Removed)> hunted and pecked:
>>>> This morning, I turned on my computer and, before I knew it, it was
>>>> doing a 5- minute chkdsk, saying my file system is NTFS and the "volume
>>>> is dirty". It deleted three indexes, one of which was in Outlook.exe.
>>>> I
>>>> have more details of index and file #'s if anyone wants them.
>>>>
>>>> I don't recall that chkdsk is something one expects upon booting.
>>>> Though everything seems fine, I am curious why this happened. Is this
>>>> just some sort of automatic maintenance when XP detects a problem while
>>>> trying to boot up?
>>>>
>>>> Thanks!
>>>> Dean
>

On 4/10/2007 2:37 PM On a whim, Dean pounded out on the keyboard

> I don't know where to find the chkdsk log, but I did copy down the 3 things
> that showed up as being deleted - all 3 were indexes and two were outlook,
> as I mentioned before.
>
> Yes, you were right. I was typing it into the run box. When I do it right
> it says Volume C is NOT dirty. So, I am fine now? I think you are also
> saying chkdsk does not fix these errors (though I thought I read otherwise
> in one of the links one of the other posters supplied). If so, I assume
> that something fixed the errors, assuming these 3 deleted indexes were
> "errors".
>
> Thanks, Wes!
> Dean
>
>
> "Wesley Vogel" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi Dean,
>>
>> If chkdsk ran and the volume is no longer dirty then there is no problem.
>>
>> Did you type or paste fsutil dirty query C: into a command prompt or
>> into the Run command? I think you typed it into the Run command. Start |
>> Run is the Run command.
>>
>> Paste the following line into Start | Run and click OK...
>>
>> cmd /K fsutil dirty query C:
>>
>> Did a command prompt open and stay open? Look a the very first line;
>> Volume - C: is....
>>
>> To open a command prompt, click Start, click Run, type: cmd into the
>> Open box and click OK.
>>
>> Then type: fsutil dirty query C: and hit your Enter key.
>> ------------
>>
>> In the chkdsk log if you see something similar to this...
>>
>> Cleaning up 10 unused index entries from index $SII of file 0x9.
>> Cleaning up 10 unused index entries from index $SDH of file 0x9.
>>
>> [[Chkdsk.exe just reclaims the unused security descriptors as a
>> housekeeping
>> activity, and it does not actually fix any kind of problem. ]]
>>
>> --
>> Hope this helps. Let us know.
>>
>> Wes
>> MS-MVP Windows Shell/User
>>
>> In news4adnWEa6-(E-Mail Removed),
>> Dean <(E-Mail Removed)> hunted and pecked:
>>> Thanks, Wes.
>>>
>>> I tried both of the commands to see if it was still dirty though, from
>>> what I can figure out, chkdsk is supposed to have fixed it, I think.
>>> Unfortunately, with either command, the screen popped up and disappeared
>>> almost instantaneously, with no time to read it at all. Is there a way
>>> to
>>> alter the command so that the result stays in the command dos prompt box
>>> so I can read it?
>>>
>>> Your info plus all the links sent by others was a little more info than I
>>> could process. I can't really tell from reading them if I should expect
>>> I
>>> have any problem now. More generally, I did reboot, after using the
>>> computer for a couple of hours with no problem, and the reboot was fine
>>> too. Is there really any reason to be concerned about the hard disk being
>>> almost dead or anything? Also Outlook seems fine and two of the three
>>> deleted indexes were associated with Outlook The other index deleted was
>>> A0053534.ini, in case that means anything to anyone - a Google search
>>> with
>>> that got zero hits.
>>>
>>> Thanks so much.
>>>
>>> Dean
>>>
>>>
>>> "Wesley Vogel" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>> Check Disk runs on every boot.
>>>>
>>>> Open a command prompt...
>>>> Start | Run | Type: cmd | Click OK |
>>>> Type or paste the following line:
>>>>
>>>> chkntfs /d
>>>>
>>>> Hit the Enter key.
>>>>
>>>> Chkntfs displays or modifies the checking of disks at boot time.
>>>>
>>>> The /d switch restores the machine to the default behavior; all drives
>>>> are checked at boot time and chkdsk is run on those that are dirty.
>>>>
>>>> Autochk.exe is a version of Chkdsk that runs only before Windows XP
>>>> starts. Autochk runs in the following situations:
>>>>
>>>> Autochk runs if you try to run Chkdsk on the boot volume.
>>>> Autochk runs if Chkdsk cannot gain exclusive use of the volume.
>>>> Autochk runs if the volume is flagged as dirty.
>>>>
>>>> This can happen if the drive's dirty bit is set.
>>>> When a drive's dirty bit is set, autochk automatically
>>>> checks the volume for errors the next time the computer is restarted.
>>>>
>>>> This will report whether the dirty bit is set.
>>>>
>>>> Start | Run | Type: cmd | Click OK |
>>>> Type or paste the following line:
>>>>
>>>> fsutil dirty query C:
>>>>
>>>> Hit the Enter key.
>>>>
>>>> Volume C: is not dirty
>>>> Volume C: is dirty
>>>>
>>>> <quote>
>>>> 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.
>>>>
>>>> Every time Windows XP starts, Autochk.exe is called by the Kernel to
>>>> scan
>>>> all volumes to check if the volume dirty bit is set. If the dirty bit is
>>>> set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f
>>>> verifies file system integrity and attempts to fix any problems with the
>>>> volume
>>>> <quote>
>>>> -----
>>>>
>>>> This will also report whether the dirty bit is set.
>>>>
>>>> Start | Run | Type: cmd | Click OK |
>>>> Type or paste the following line:
>>>>
>>>> chkntfs c:
>>>>
>>>> Hit the Enter key.
>>>>
>>>> C: is not dirty.
>>>> -----
>>>>
>>>> If this is not the problem.....
>>>>
>>>> Go here:
>>>> http://www.kellys-korner-xp.com/xp_tweaks.htm
>>>>
>>>> Read the instructions at the top of the page.
>>>> Scroll down to:
>>>> 82. Disable or Enable Check Disk Upon Boot
>>>> Click on Disable.
>>>> -----
>>>>
>>>> Additional information...
>>>> Chkdsk.exe or Autochk.exe starts when you try to shut down or restart
>>>> your computer
>>>> http://support.microsoft.com/kb/831426
>>>>
>>>> --
>>>> Hope this helps. Let us know.
>>>>
>>>> Wes
>>>> MS-MVP Windows Shell/User
>>>>
>>>> In news:Xb-(E-Mail Removed),
>>>> Dean <(E-Mail Removed)> hunted and pecked:
>>>>> This morning, I turned on my computer and, before I knew it, it was
>>>>> doing a 5- minute chkdsk, saying my file system is NTFS and the "volume
>>>>> is dirty". It deleted three indexes, one of which was in Outlook.exe.
>>>>> I
>>>>> have more details of index and file #'s if anyone wants them.
>>>>>
>>>>> I don't recall that chkdsk is something one expects upon booting.
>>>>> Though everything seems fine, I am curious why this happened. Is this
>>>>> just some sort of automatic maintenance when XP detects a problem while
>>>>> trying to boot up?
>>>>>
>>>>> Thanks!
>>>>> Dean
>
>

Dean,

I would still make sure you have a good backup. I didn't say the hard
drive "was" failing, I said it "could" be failing. You don't want to
take a chance losing your data.

I have been fortunate enough that all but one of the five drives I've
had fail in the last couple years gave me a warning, and it started just
like this.

--
Terry

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

Are you saying that you've had five drives fail in two years? You must be
some heavy user, or are you a network admin for a company? And the warning
in four of those cases was an automated chkdsk running upon startup?

Terry, I will do as you say and backup tonight. Though I know the party
line is always backup, all the time, is there any amount of time, relative
to this problem, where I'm probably home free? In other words, if it is Ok
for a week, can I stop being paranoid and backing up daily?

Thanks!
Dean

"Terry" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> On 4/10/2007 2:37 PM On a whim, Dean pounded out on the keyboard
>
>> I don't know where to find the chkdsk log, but I did copy down the 3
>> things that showed up as being deleted - all 3 were indexes and two were
>> outlook, as I mentioned before.
>>
>> Yes, you were right. I was typing it into the run box. When I do it
>> right it says Volume C is NOT dirty. So, I am fine now? I think you are
>> also saying chkdsk does not fix these errors (though I thought I read
>> otherwise in one of the links one of the other posters supplied). If so,
>> I assume that something fixed the errors, assuming these 3 deleted
>> indexes were "errors".
>>
>> Thanks, Wes!
>> Dean
>>
>>
>> "Wesley Vogel" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Hi Dean,
>>>
>>> If chkdsk ran and the volume is no longer dirty then there is no
>>> problem.
>>>
>>> Did you type or paste fsutil dirty query C: into a command prompt or
>>> into the Run command? I think you typed it into the Run command. Start
>>> | Run is the Run command.
>>>
>>> Paste the following line into Start | Run and click OK...
>>>
>>> cmd /K fsutil dirty query C:
>>>
>>> Did a command prompt open and stay open? Look a the very first line;
>>> Volume - C: is....
>>>
>>> To open a command prompt, click Start, click Run, type: cmd into the
>>> Open box and click OK.
>>>
>>> Then type: fsutil dirty query C: and hit your Enter key.
>>> ------------
>>>
>>> In the chkdsk log if you see something similar to this...
>>>
>>> Cleaning up 10 unused index entries from index $SII of file 0x9.
>>> Cleaning up 10 unused index entries from index $SDH of file 0x9.
>>>
>>> [[Chkdsk.exe just reclaims the unused security descriptors as a
>>> housekeeping
>>> activity, and it does not actually fix any kind of problem. ]]
>>>
>>> --
>>> Hope this helps. Let us know.
>>>
>>> Wes
>>> MS-MVP Windows Shell/User
>>>
>>> In news4adnWEa6-(E-Mail Removed),
>>> Dean <(E-Mail Removed)> hunted and pecked:
>>>> Thanks, Wes.
>>>>
>>>> I tried both of the commands to see if it was still dirty though, from
>>>> what I can figure out, chkdsk is supposed to have fixed it, I think.
>>>> Unfortunately, with either command, the screen popped up and
>>>> disappeared
>>>> almost instantaneously, with no time to read it at all. Is there a way
>>>> to
>>>> alter the command so that the result stays in the command dos prompt
>>>> box
>>>> so I can read it?
>>>>
>>>> Your info plus all the links sent by others was a little more info than
>>>> I
>>>> could process. I can't really tell from reading them if I should
>>>> expect I
>>>> have any problem now. More generally, I did reboot, after using the
>>>> computer for a couple of hours with no problem, and the reboot was fine
>>>> too. Is there really any reason to be concerned about the hard disk
>>>> being
>>>> almost dead or anything? Also Outlook seems fine and two of the three
>>>> deleted indexes were associated with Outlook The other index deleted
>>>> was
>>>> A0053534.ini, in case that means anything to anyone - a Google search
>>>> with
>>>> that got zero hits.
>>>>
>>>> Thanks so much.
>>>>
>>>> Dean
>>>>
>>>>
>>>> "Wesley Vogel" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>> Check Disk runs on every boot.
>>>>>
>>>>> Open a command prompt...
>>>>> Start | Run | Type: cmd | Click OK |
>>>>> Type or paste the following line:
>>>>>
>>>>> chkntfs /d
>>>>>
>>>>> Hit the Enter key.
>>>>>
>>>>> Chkntfs displays or modifies the checking of disks at boot time.
>>>>>
>>>>> The /d switch restores the machine to the default behavior; all drives
>>>>> are checked at boot time and chkdsk is run on those that are dirty.
>>>>>
>>>>> Autochk.exe is a version of Chkdsk that runs only before Windows XP
>>>>> starts. Autochk runs in the following situations:
>>>>>
>>>>> Autochk runs if you try to run Chkdsk on the boot volume.
>>>>> Autochk runs if Chkdsk cannot gain exclusive use of the volume.
>>>>> Autochk runs if the volume is flagged as dirty.
>>>>>
>>>>> This can happen if the drive's dirty bit is set.
>>>>> When a drive's dirty bit is set, autochk automatically
>>>>> checks the volume for errors the next time the computer is restarted.
>>>>>
>>>>> This will report whether the dirty bit is set.
>>>>>
>>>>> Start | Run | Type: cmd | Click OK |
>>>>> Type or paste the following line:
>>>>>
>>>>> fsutil dirty query C:
>>>>>
>>>>> Hit the Enter key.
>>>>>
>>>>> Volume C: is not dirty
>>>>> Volume C: is dirty
>>>>>
>>>>> <quote>
>>>>> 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.
>>>>>
>>>>> Every time Windows XP starts, Autochk.exe is called by the Kernel to
>>>>> scan
>>>>> all volumes to check if the volume dirty bit is set. If the dirty bit
>>>>> is
>>>>> set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f
>>>>> verifies file system integrity and attempts to fix any problems with
>>>>> the
>>>>> volume
>>>>> <quote>
>>>>> -----
>>>>>
>>>>> This will also report whether the dirty bit is set.
>>>>>
>>>>> Start | Run | Type: cmd | Click OK |
>>>>> Type or paste the following line:
>>>>>
>>>>> chkntfs c:
>>>>>
>>>>> Hit the Enter key.
>>>>>
>>>>> C: is not dirty.
>>>>> -----
>>>>>
>>>>> If this is not the problem.....
>>>>>
>>>>> Go here:
>>>>> http://www.kellys-korner-xp.com/xp_tweaks.htm
>>>>>
>>>>> Read the instructions at the top of the page.
>>>>> Scroll down to:
>>>>> 82. Disable or Enable Check Disk Upon Boot
>>>>> Click on Disable.
>>>>> -----
>>>>>
>>>>> Additional information...
>>>>> Chkdsk.exe or Autochk.exe starts when you try to shut down or restart
>>>>> your computer
>>>>> http://support.microsoft.com/kb/831426
>>>>>
>>>>> --
>>>>> Hope this helps. Let us know.
>>>>>
>>>>> Wes
>>>>> MS-MVP Windows Shell/User
>>>>>
>>>>> In news:Xb-(E-Mail Removed),
>>>>> Dean <(E-Mail Removed)> hunted and pecked:
>>>>>> This morning, I turned on my computer and, before I knew it, it was
>>>>>> doing a 5- minute chkdsk, saying my file system is NTFS and the
>>>>>> "volume
>>>>>> is dirty". It deleted three indexes, one of which was in Outlook.exe.
>>>>>> I
>>>>>> have more details of index and file #'s if anyone wants them.
>>>>>>
>>>>>> I don't recall that chkdsk is something one expects upon booting.
>>>>>> Though everything seems fine, I am curious why this happened. Is
>>>>>> this
>>>>>> just some sort of automatic maintenance when XP detects a problem
>>>>>> while
>>>>>> trying to boot up?
>>>>>>
>>>>>> Thanks!
>>>>>> Dean
>>
>>
>
> Dean,
>
> I would still make sure you have a good backup. I didn't say the hard
> drive "was" failing, I said it "could" be failing. You don't want to take
> a chance losing your data.
>
> I have been fortunate enough that all but one of the five drives I've had
> fail in the last couple years gave me a warning, and it started just like
> this.
>
> --
> Terry
>
> ***Reply Note***
> Anti-spam measures are included in my email address.
> Delete NOSPAM from the email address after clicking Reply.