Chkdsk repair

[Guest]

Norton utilities reports a disk error.

I have tried running chkdsk /r from the Recovery Console several times -
each time get a report that errors were found and fixed.
How can I tell what the errors are? If new errors are being found and fixed,
or if the same problem is reocurring, or what?

I have a Samsung drive and have checked their site for a disk utility but
they do not seem to have one. I tested the drive with a Maxtor utility and
that found no errors with the disk.

I'm using XP Home SP2. Thanks for help with this.

 

[Steve N.]

Norton utilities reports a disk error.

I have tried running chkdsk /r from the Recovery Console several times -
each time get a report that errors were found and fixed.
How can I tell what the errors are? If new errors are being found and fixed,
or if the same problem is reocurring, or what?

I have a Samsung drive and have checked their site for a disk utility but
they do not seem to have one. I tested the drive with a Maxtor utility and
that found no errors with the disk.

I'm using XP Home SP2. Thanks for help with this.

Right click My Computer, Manage, Event Viewer, Application, look at
Winlogon entries.

Steve

 

[Guest]

OK, I checked that and indeed there was a change from the first to the second
run, but not for the 3rd time

Winlog file showed "minor inconsistencies"

14 unused entries from $S11 of file 0x0
14 unused entries from $SDH of file 0x0
14 unused security decriptors

The second CHKDSK has the same minor inconistencies except now there were
only 2.

Thethird CHKDSK had the same result.

Seems like I can't clear those last 2 minor inconsistencies.

Any more suggestions? Thanks for your help.

 

[Steve N.]

OK, I checked that and indeed there was a change from the first to the second
run, but not for the 3rd time

Winlog file showed "minor inconsistencies"

14 unused entries from $S11 of file 0x0
14 unused entries from $SDH of file 0x0
14 unused security decriptors

The second CHKDSK has the same minor inconistencies except now there were
only 2.

Thethird CHKDSK had the same result.

Seems like I can't clear those last 2 minor inconsistencies.

Any more suggestions? Thanks for your help.

You are most welcome David.

Minor inconsistencies are usually nothing to be concened about but I
have seen security descriptor errors effecting security permissions for
limited user accounts accessing some software applications properly. On
some systems I have run CHKDSK /F repeatedly and some minor
inconsistencies and unused security decriptors that show up every time.
The systems operate normally, though.

Also, CHKDSK /R does a surface scan for bad blocks on the disk (as
opposed to CHKDSK /F from cmd prompt or CHKDSK /P from Recovery Console,
which only checks for file system errors), if it does not find any bad
blocks then your disk itself is probably healthy. Why did you feel the
need to run CHKDSK /R in the first place? Are you experiencing specific
problems? If so please post details.

Steve

 

[Guest]

Why did you feel the
need to run CHKDSK /R in the first place? Are you experiencing specific
problems? If so please post details.

Steve

Only because Norton Utilities flagged a disk problem.

Repeated running of DSKCHK does not seem to clear it up.

David E

 

[Steve N.]

:




Only because Norton Utilities flagged a disk problem.

Repeated running of DSKCHK does not seem to clear it up.

David E

(Note: It is CHKDSK, not DSKCHK)

Clear WHAT up? What exactly is NU reporting? What version of NU? What
does it report? Is it fully compatible with the version of NTFS in XP?
NTFS in XP is a bit different than in Win2K and NT4x. Not a lot
different, but enough to possibly make a difference with an older NU
version.

Please post all the gory technical details. Someone can help, I am sure.



Cheers,
Steve

 

[Guest]

Thanks, I'll make a detailed note of the things you've mentioned and try a
new post.

And I have been using CHKDSK, not DSKCHK, though at this point I'm ready to
try anything.

 

[Steve N.]

Thanks, I'll make a detailed note of the things you've mentioned and try a
new post.

Nah, keep it in this thread. Makes it easier to track for everyone.

And I have been using CHKDSK, not DSKCHK, though at this point I'm ready to
try anything.

Ok. Keep us posted.

Steve

 

[Kelly]

Hi David,

Some info:

Disable or Enable CheckDisk Upon Boot (Line 82)
http://www.kellys-korner-xp.com/xp_tweaks.htm

To use the Regedit: Save the REG File to your hard disk. Double click it
and answer yes to the import prompt. REG files can be viewed in Notepad by
right clicking on the file and selecting Edit.

Chkdsk Runs Each Time That You Start Computer
http://support.microsoft.com/support/kb/articles/q316/5/06.asp

Go to Start/Run/Regedit and navigate to this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Highlight the Winlogon file.

In the list look for "SFCScan", this should be set to (0) if it is set to
(1) the scan will happen at every boot.

--
All the Best,
Kelly (MS-MVP)

Troubleshooting Windows XP
http://www.kellys-korner-xp.com

 

[Guest]

OK, so here's what I've got so far ...

I am using XP Home SP2. My "C" drive is NTFS (or whatever the initials are);
non-partitioned; 120GB Samsung Serial ATA. I use Norton Uitilities 2002. I
normally defrag at 25% fragmented; but cannot do this when there is a disk
error flagged. I checked the Samsung site for a vendor disk scan utility, but
Samsung referred me to a third party site, "Data Advisor" and the description
of that utility said it was for FAT files only. I also have a Maxtor drive,
"F" on my system, and used their PowerMax to scan the Samsung drive. No
problems were reported. (But I'm sure a Maxtor program works properly on a
Samsung drive.)

Norton Disk Doctor report says:

SECURITY DESCRIPTORS STATUS
---------------------------

The 'Fix errors' checkbox was not checked.
Corrective actions indicated below were
not written to the disk.

Correcting errors in the Volume Bitmap.

Norton Disk Doctor found problems with the file system.
Run Norton Disk Doctor and check the Fix Errors option.
-----------------------
I've learned from this forum to use my Windows CD to run the Recovery
Console and from there to use CHKDSK. CHKDSK C: /R takes an average of 90
minutes (which in our househiold is not easy to get).

CHKDSK always indicates that it has found and fixed one or more errors. From
this forum I have also learned about the Event Viewer and WINLOGON files. So
the last time I did a CHKDSK, it reported:

Checking file system on \DosDevices\C:
The type of the file system is NTFS.
Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 unused index entries from index $SDH of file 0x9.
Cleaning up 2 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
----------------

Each time I run CHKDSK I get a similar result, the only change in the
message is the number of "Unused ..." (has varied from 2 to 14). The $SII and
$SDH of file 0x9 is constant.

Having discovered the joys of the event viewer, I aslo notice a warning
which was occurring at each shut down: Userenv, Event 1517. I followed the
link in the Properties description window,
go.microsoft.com/fwlink/events.asp, which led me a fix for this particular
problem, UPHClean. I have installed that and it has fixed the Userenv problem
(which UPHClean attributes to svchost(748) and HKCU(0x278) not releasing
handles - or some such thing - I am out of my depth here.)

I have not had a chance to try CHKDSK since installing UPHClean, so can't
tell if the two issues might be connected in some way.

Thanks for help and interest in this.

David E

 

[Guest]

I have just run CHKDSK 4 consecutive times from recovery console (I did exit
RC each time and logged onto windows; then restarted from the CD again.) The
four Winlog files are:

Why is CHKDSK not repairing the data file once and for all??? And/or what is
corrupting the file structure every time I log onto Windows???


Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 12/6/2004
Time: 5:06:45 PM
User: N/A
Computer: DAVID
Description:
Checking file system on \DosDevices\C:
The type of the file system is NTFS.
Cleaning up minor inconsistencies on the drive.
Cleaning up 6 unused index entries from index $SII of file 0x9.
Cleaning up 6 unused index entries from index $SDH of file 0x9.
Cleaning up 6 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

117234305 KB total disk space.
53705068 KB in 139762 files.
48988 KB in 5328 indexes.
0 KB in bad sectors.
221893 KB in use by the system.
65536 KB occupied by the log file.
63258356 KB available on disk.

4096 bytes in each allocation unit.
29308576 total allocation units on disk.
15814589 allocation units available on disk.

Internal Info:
10 4c 02 00 cc 36 02 00 a5 7a 03 00 00 00 00 00 .L...6...z......
14 08 00 00 00 00 00 00 61 02 00 00 00 00 00 00 ........a.......
bc 27 f9 04 00 00 00 00 cc ba 38 36 00 00 00 00 .'........86....
6e e2 d6 05 00 00 00 00 fe fc b6 61 05 00 00 00 n..........a....
26 ec 4f 49 04 00 00 00 76 74 9b ed 09 00 00 00 &.OI....vt......
99 9e 36 00 00 00 00 00 f2 21 02 00 00 00 00 00 ..6......!......
00 b0 e5 cd 0c 00 00 00 d0 14 00 00 00 00 00 00 ................


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

-----------

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 12/6/2004
Time: 6:24:05 PM
User: N/A
Computer: DAVID
Description:
Checking file system on \DosDevices\C:
The type of the file system is NTFS.
Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

117234305 KB total disk space.
53705256 KB in 139773 files.
48988 KB in 5328 indexes.
0 KB in bad sectors.
221893 KB in use by the system.
65536 KB occupied by the log file.
63258168 KB available on disk.

4096 bytes in each allocation unit.
29308576 total allocation units on disk.
15814542 allocation units available on disk.

Internal Info:
10 4c 02 00 d7 36 02 00 b1 7a 03 00 00 00 00 00 .L...6...z......
14 08 00 00 00 00 00 00 5c 02 00 00 00 00 00 00 ........\.......
d8 75 07 05 00 00 00 00 8e a6 44 36 00 00 00 00 .u........D6....
06 59 cd 05 00 00 00 00 cc 05 a3 62 05 00 00 00 .Y.........b....
ee 7c 64 4a 04 00 00 00 c0 d2 a0 ef 09 00 00 00 .|dJ............
99 9e 36 00 00 00 00 00 fd 21 02 00 00 00 00 00 ..6......!......
00 a0 e8 cd 0c 00 00 00 d0 14 00 00 00 00 00 00 ................


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

----------

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 12/6/2004
Time: 7:41:10 PM
User: N/A
Computer: DAVID
Description:
Checking file system on \DosDevices\C:
The type of the file system is NTFS.
Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

117234305 KB total disk space.
53705404 KB in 139784 files.
48992 KB in 5328 indexes.
0 KB in bad sectors.
221893 KB in use by the system.
65536 KB occupied by the log file.
63258016 KB available on disk.

4096 bytes in each allocation unit.
29308576 total allocation units on disk.
15814504 allocation units available on disk.

Internal Info:
10 4c 02 00 e2 36 02 00 bd 7a 03 00 00 00 00 00 .L...6...z......
14 08 00 00 00 00 00 00 5c 02 00 00 00 00 00 00 ........\.......
54 9e ef 04 00 00 00 00 84 c0 bc 35 00 00 00 00 T..........5....
f8 31 c6 05 00 00 00 00 14 d3 ed 61 05 00 00 00 .1.........a....
56 06 6e 4a 04 00 00 00 e2 6b 55 ee 09 00 00 00 V.nJ.....kU.....
99 9e 36 00 00 00 00 00 08 22 02 00 00 00 00 00 ..6......"......
00 f0 ea cd 0c 00 00 00 d0 14 00 00 00 00 00 00 ................


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

-------------

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 12/6/2004
Time: 9:04:38 PM
User: N/A
Computer: DAVID
Description:
Checking file system on \DosDevices\C:
The type of the file system is NTFS.
Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

117234305 KB total disk space.
53705556 KB in 139795 files.
48996 KB in 5328 indexes.
0 KB in bad sectors.
221893 KB in use by the system.
65536 KB occupied by the log file.
63257860 KB available on disk.

4096 bytes in each allocation unit.
29308576 total allocation units on disk.
15814465 allocation units available on disk.

Internal Info:
10 4c 02 00 ed 36 02 00 c9 7a 03 00 00 00 00 00 .L...6...z......
14 08 00 00 00 00 00 00 5c 02 00 00 00 00 00 00 ........\.......
54 9e ef 04 00 00 00 00 b6 e4 01 36 00 00 00 00 T..........6....
9e cf c3 05 00 00 00 00 9c be 53 60 05 00 00 00 ..........S`....
c6 3e a7 4a 04 00 00 00 a4 2a 30 ed 09 00 00 00 .>.J.....*0.....
99 9e 36 00 00 00 00 00 13 22 02 00 00 00 00 00 ..6......"......
00 50 ed cd 0c 00 00 00 d0 14 00 00 00 00 00 00 .P..............


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

 

[Steve N.]

I have just run CHKDSK 4 consecutive times from recovery console (I did exit
RC each time and logged onto windows; then restarted from the CD again.) The
four Winlog files are:

Why is CHKDSK not repairing the data file once and for all??? And/or what is
corrupting the file structure every time I log onto Windows???

From a cmd prompt enter this command:

fsutil dirty query C:

This will tell you if the file sytem has the dirty bit set or not. If it
responds with:

Volume - c: is NOT DIRTY

Then the dirty bit is not set and it would appear to be a problem with
your version of Norton and XP. Have you searched the KB at Symantec?

Steve

 

[Guest]

Hi Steve,

I just did as you suggested and got NOT dirty as the response.

Since posting my previous message, I did run CHKDSK twice in a row without
exiting and logging into Windows in between. The second CHKDSK reported no
errors. So I conclude that CHKDSK is finding and repairing errors, but the
log in process - or the log off process - is creating a disk file error of
some kind.

I've initiated one of my two no extra charge email services from Microsoft,
and am getting advice to do a clean install. But I'm hoping there is a
simpler solution.

I don't think the problem is a conflict between NU and XP since even CHKDSK
does always find and repair errors whenever NU indicates there are errors.
That is, the problem is not a conflict nor a false report, there really are
errors being created. The question is how and what is causing the errors. OR
is there some other issue I am not aware of? (And to answer your question:
No, I have not searched Symantec's KB. I'm not even sure how I would describe
my problem for a KB search.)

David E.

PS Thanks a lot for your help.

 

[Rock]

Hi Steve,

I just did as you suggested and got NOT dirty as the response.

Since posting my previous message, I did run CHKDSK twice in a row without
exiting and logging into Windows in between. The second CHKDSK reported no
errors. So I conclude that CHKDSK is finding and repairing errors, but the
log in process - or the log off process - is creating a disk file error of
some kind.

I've initiated one of my two no extra charge email services from Microsoft,
and am getting advice to do a clean install. But I'm hoping there is a
simpler solution.

I don't think the problem is a conflict between NU and XP since even CHKDSK
does always find and repair errors whenever NU indicates there are errors.
That is, the problem is not a conflict nor a false report, there really are
errors being created. The question is how and what is causing the errors. OR
is there some other issue I am not aware of? (And to answer your question:
No, I have not searched Symantec's KB. I'm not even sure how I would describe
my problem for a KB search.)

David E.

PS Thanks a lot for your help.

:

The errors you have posted are not significant. I get them regularly
too and it never causes any problems. Running the fsutil dirty query
will report it's not dirty but if chkdsk is run it will show those minor
inconsistencies. The issue is NU 2002. Get rid of it and you won't
have the issue.

 

[Steve N.]

The errors you have posted are not significant. I get them regularly
too and it never causes any problems. Running the fsutil dirty query
will report it's not dirty but if chkdsk is run it will show those minor
inconsistencies. The issue is NU 2002. Get rid of it and you won't
have the issue.

That's what I'm thinking, too, that it's the version of Norton with the
problem. He didn't mention what version it is.

Steve

 

[Guest]

OK, Thanks again. BTW: I am using NU 2002.

That's what I'm thinking, too, that it's the version of Norton with the
problem. He didn't mention what version it is.

Steve

 

[Steve N.]

OK, Thanks again. BTW: I am using NU 2002.

As Rock said, the problem is NU 2002 since it is what is having the
problem, not the OS or the file system; if FSUTIL says the drive is not
dirty then it is not dirty. I'd check with Symantec tech support for a
fix, upgrade to a newer version, or just stop using NU.

Steve

 

[Steve N.]

OK, Thanks again. BTW: I am using NU 2002.

Sorry - I missed that part earlier.

Steve

 

[cquirke (MVP Win9x)]

David E wrote:

My guess isthat NU 2002 is crying wolf, possibly because something
that is legal in post-2002 NTFS wasn't legal when it was written.

As Rock said, the problem is NU 2002 since it is what is having the
problem, not the OS or the file system; if FSUTIL says the drive is not
dirty then it is not dirty.

Don't confuse "not dirty" with "not corrupted".

What "not dirty" means is that the last time the OS shut down (or
basically, stopped running), there were no file operations in
progress. If the interruption of normal file operations was the only
cause of file system corruption, then that would be all you need to
know, especially if ChkDsk really did "fix" corrupted files.

But there are other possible causes of file system corruption, such as
wild writes from deranged software (look up Witty), or corruption of
data while it's in RAM on on the bus on its way to the HD.

If that corruption is within file system structure, or affects the
address on the HD to which anything is written, then you will get file
system corruption. If it's only within the contents of a file's data,
then the file system will remain sane but that file will be bent.

So:
- a non-dirty file system may be corrupted
- a non-corrupted file system may contain corrupted files

The last is very common after ChkDsk has "fixed" the file system.

-------------------- ----- ---- --- -- - - - -

Tip Of The Day:
To disable the 'Tip of the Day' feature...

 

[Steve N.]

My guess isthat NU 2002 is crying wolf, possibly because something
that is legal in post-2002 NTFS wasn't legal when it was written.




Don't confuse "not dirty" with "not corrupted".

What "not dirty" means is that the last time the OS shut down (or
basically, stopped running), there were no file operations in
progress. If the interruption of normal file operations was the only
cause of file system corruption, then that would be all you need to
know, especially if ChkDsk really did "fix" corrupted files.

But there are other possible causes of file system corruption, such as
wild writes from deranged software (look up Witty), or corruption of
data while it's in RAM on on the bus on its way to the HD.

If that corruption is within file system structure, or affects the
address on the HD to which anything is written, then you will get file
system corruption. If it's only within the contents of a file's data,
then the file system will remain sane but that file will be bent.

So:
- a non-dirty file system may be corrupted
- a non-corrupted file system may contain corrupted files

The last is very common after ChkDsk has "fixed" the file system.





Tip Of The Day:
To disable the 'Tip of the Day' feature...

Funny tip

Thanks for additional info and of course you are correct.

Steve