Re: Chkdsk Reports Nonexistent Errors
- From: "Wesley Vogel" <123WVogel955@xxxxxxxxxxx>
- Date: Tue, 10 Apr 2007 14:12:18 -0600
Keep having fun, Dad! :-)
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In news:Ar6dneqbJLqBn4bbnZ2dnUVZ_tGvnZ2d@xxxxxxxxxxx,
M and D <m.and.d@xxxxxxxxxxxx> hunted and pecked:
Hi again Wesley,
I believe that "0 KB in bad sectors" refers to the surface of the disk,
whereas the reports I am seeing in Event Viewer refer to logical errors.
Nonetheless, I've concluded that I really am seeing nothing more than
Windows XP internal housekeeping, so I'm not going to worry any more.
As for my concern that CHKDSK didn't in the past make my hard disk grind
away for a minute or so during "CHKDSK is verifying indexes"...I haven't
run CHKDSK in a long, long time during which I've installed lots of
updates from Microsoft Update, so perhaps that behavior is typical for
Windows XP nowadays.
Thanks very much for investing so much of your time to help me out. I do
appreciate it. Enjoy your new computer.
M and D
(That's 'Mom and Dad' - I'm Dad.)
"Wesley Vogel" <123WVogel955@xxxxxxxxxxx> wrote in message
news:e%23h22GxeHHA.284@xxxxxxxxxxxxxxxxxxxxxxx
M and D,
Cleaning up 2 unused index entries from index $SII of file 0x9.
Cleaning up 2 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.
]]
Cleaning up 2 unused security descriptors.
[[Chkdsk.exe just reclaims the unused security descriptors as a
housekeeping activity, and it does not actually fix any kind of problem.
]]
Is normal. I think there is much ado about nothing. Meaning I do not
think you have any problem whatsoever.
Here are some chkdsk log samples that I have saved. Notice the 0 KB in
bad sectors. parts
Date: 12/4/2004
Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 unused security descriptors.
9952235 KB total disk space.
6020596 KB in 40720 files.
15248 KB in 2053 indexes.
0 KB in bad sectors.
102811 KB in use by the system.
51824 KB occupied by the log file.
3813580 KB available on disk.
4096 bytes in each allocation unit.
2488058 total allocation units on disk.
953395 allocation units available on disk.
Date: 10/31/2005
Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 10 unused index entries from index $SII of file 0x9.
Cleaning up 10 unused index entries from index $SDH of file 0x9.
Cleaning up 10 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.
9952235 KB total disk space.
8294548 KB in 45987 files.
18368 KB in 2270 indexes.
0 KB in bad sectors.
106159 KB in use by the system.
51824 KB occupied by the log file.
1533160 KB available on disk.
4096 bytes in each allocation unit.
2488058 total allocation units on disk.
383290 allocation units available on disk.
Date: 02/05/2006
Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 8 unused index entries from index $SII of file 0x9.
Cleaning up 8 unused index entries from index $SDH of file 0x9.
Cleaning up 8 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.
9952235 KB total disk space.
7967676 KB in 45429 files.
18224 KB in 2251 indexes.
0 KB in bad sectors.
106179 KB in use by the system.
51824 KB occupied by the log file.
1860156 KB available on disk.
4096 bytes in each allocation unit.
2488058 total allocation units on disk.
465039 allocation units available on disk.
I bought a new machine with a hard drive @ 232 GB not 9.49 GB and this is
from the new machine.
Date: 31/Mar/07
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.
Cleaning up minor inconsistencies on the drive.
Cleaning up 79 unused index entries from index $SII of file 0x9.
Cleaning up 79 unused index entries from index $SDH of file 0x9.
Cleaning up 79 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.
244187968 KB total disk space.
11322912 KB in 53772 files.
20504 KB in 3070 indexes.
0 KB in bad sectors.
134204 KB in use by the system.
65536 KB occupied by the log file.
232710348 KB available on disk.
4096 bytes in each allocation unit.
61046992 total allocation units on disk.
58177587 allocation units available on disk.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In news:4rqdnXy-mZ4QeYfbnZ2dnUVZ_silnZ2d@xxxxxxxxxxx,
M and D <m.and.d@xxxxxxxxxxxx> hunted and pecked:
Thank you sincerely for responding to my posts.
Evidentally we've been reading the same articles in our research.
I understand and accept that CHKDSK in read-only mode can produce
erroneous conclusions. I also understand some - okay, a little bit - of
the housekeeping that Windows performs on the NTFS file system. I'm
almost ready to drop my concerns and go merrily on my way, except for
one thing:
When I've run CHKDSK /f in the past, the second stage ("CHKDSK is
verifying indexes") took only seconds to complete. Now the progress
indicator is stuck at 0% for almost a minute while my disk is grinding
away, and then it progresses swiftly to 100% and CHKDSK goes on
normally. And this now happens everytime I run CHKDSK. /Something/ is
going on during that minute of grinding, and that's what concerns me.
From what I've read on the web, the messages I see in Event
Viewer...here's a typical example:
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.
...are either completely normal /or/ they're a sign that my NTFS file
system is corrupted and my disk is nearing death. That uncertainty and
the minute of disk grinding leave me unsure of what to do.
I'd really appreciate your advice.
M and D
"Wesley Vogel" <123WVogel955@xxxxxxxxxxx> wrote in message
news:urqaDLweHHA.5044@xxxxxxxxxxxxxxxxxxxxxxx
Because ChkDsk makes mistakes when run with the safety catch on, you
should run it with the safety catch off.
Or do not run it at all.
Hey Chris,
You ever heard of The Creaking Door?
I download a lot of old radio programs and burn them to CD. I do not
watch TV. Nobody seems to know much about The Creaking Door. I
listened to a couple of episodes last night and thought that they were
pretty good. The Creaking Door was sponsored by State Express 555
(pronounced State Express Three Fives) cigarettes, which Google tells
me still exists.
''The Creaking Door was an old-time radio series of horror and suspense
shows originating in South Africa.
There are at present anywhere from 34-37 extant episodes in MP3
circulation, yet no currently available program logs for the series
indicate the year of the series' broadcast (though it was likely
sometime in the 1950s, given the generally high audio quality of the
available shows), or the total number of episodes, and only a handful
of them are known by their broadcast order. The stories are thrillers
in the Inner Sanctum vein, and generally thought of favorably by most
fans of Old Time Radio."
"In 1964, South Africa began The Creaking Door, using original scripts
which included stories with a heavy emphasis on the supernatural. The
topics ranged from haunted houses to a woman who turns into a giant
cat, and of course, the typical paranoid murderer so often presented
on the original Inner Sanctum. The host for this series was Peter
Bloomfield.''
Free Old time Radio Shows - The Creaking Door
Click on the Links below to listen for free online:
http://www.radiolovers.com/pages/creakingdoor.htm
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In news:r8cl13901g3fdv0h7oimg7282en8bt90l7@xxxxxxx,
cquirke (MVP Windows shell/user) <cquirkenews@xxxxxxxxxxxxxxx> hunted
and pecked:
On Mon, 9 Apr 2007 12:43:03 -0600, "Wesley Vogel"
Don't even bother running CHKDSK in read-only mode. It is a waste of
time and prone to not accurately reporting information. CHKDSK might
report spurious errors because it cannot lock the drive.
I just love the logic here.
Because ChkDsk makes mistakes when run with the safety catch on, you
should run it with the safety catch off.
What would be more useful (as long as one is forced to live with tool
designs that pre-date MS-DOS 6) is to force ChkDsk to run on boot, as
if it was run with /F, so that it could report more accurately without
irreversibly blowing things up if it gets things wrong.
But it can't, because what runs at boot is not ChkDsk, but the even
more brain-dead AutoChk that can't run without "fixing".
-------------------- ----- ---- --- -- - - - -Hmmm... what was the *other* idea?-------------------- ----- ---- --- -- - - - -
.
- References:
- Chkdsk Reports Nonexistent Errors
- From: M and D
- Re: Chkdsk Reports Nonexistent Errors
- From: M and D
- Re: Chkdsk Reports Nonexistent Errors
- From: Wesley Vogel
- Re: Chkdsk Reports Nonexistent Errors
- From: cquirke (MVP Windows shell/user)
- Re: Chkdsk Reports Nonexistent Errors
- From: Wesley Vogel
- Re: Chkdsk Reports Nonexistent Errors
- From: M and D
- Re: Chkdsk Reports Nonexistent Errors
- From: Wesley Vogel
- Re: Chkdsk Reports Nonexistent Errors
- From: M and D
- Chkdsk Reports Nonexistent Errors
- Prev by Date: Re: cd and dvd gone after clean install of xp
- Next by Date: RE: Error Messages
- Previous by thread: Re: Chkdsk Reports Nonexistent Errors
- Next by thread: Re: Chkdsk Reports Nonexistent Errors
- Index(es):
Relevant Pages
|
|
