Re: chkdsk /f errors in Event Log
- From: "Gerry Cornell" <gcjc@xxxxxxxxxxxxxx>
- Date: Fri, 27 Oct 2006 19:31:50 +0100
This problem existed with Windows 2000 and there is a similar KB Article
for that system as Article 831374 mentioned in another post. By the way
these Articles were reviewed yesterday!
It is not unknown for Microsoft to fix a problem and then to unfix it
unintentionally in a later update.
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
"Frankster" <Frank@xxxxxxxxxxxxxx> wrote in message
news:3OudnYMdc7Wxlt_YnZ2dnUVZ_uidnZ2d@xxxxxxxxxxxxxxx
Frank
How are the drives formatted?
NTFS (only one drive in the machine at any one time - same results)
What partitioning tools, if any, have been used?
None. I told XP Pro installation to remove all partitions, then long
format NTFS. Everything went smooth.
Can you copy and paste some typical Event Viewer Reports?
Sure (MS has this - below)
-Frank
------------------------
Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 10/26/2006
Time: 9:55:46 PM
User: N/A
Computer: SLOTS
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.
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.
195350368 KB total disk space.
22622388 KB in 151454 files.
50076 KB in 8744 indexes.
0 KB in bad sectors.
273488 KB in use by the system.
65536 KB occupied by the log file.
172404416 KB available on disk.
4096 bytes in each allocation unit.
48837592 total allocation units on disk.
43101104 allocation units available on disk.
Internal Info:
60 74 02 00 d1 71 02 00 c0 83 03 00 00 00 00 00 `t...q..........
ff 01 00 00 01 00 00 00 0f 03 00 00 00 00 00 00 ................
b8 c7 6f 0b 00 00 00 00 06 5e c0 49 00 00 00 00 ..o......^.I....
2a 80 80 1b 00 00 00 00 00 00 00 00 00 00 00 00 *...............
00 00 00 00 00 00 00 00 18 a1 c4 77 00 00 00 00 ...........w....
99 9e 36 00 00 00 00 00 98 38 07 00 9e 4f 02 00 ..6......8...O..
00 00 00 00 00 d0 c2 64 05 00 00 00 28 22 00 00 .......d....("..
Windows has finished checking your disk.
Please wait while your computer restarts.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
------------------------
--
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
"Frankster" <Frank@xxxxxxxxxxxxxx> wrote in message
news:fZWdnagoQYNDmN_YnZ2dnUVZ_sGdnZ2d@xxxxxxxxxxxxxxx
I've got an open case with MS about the below problem. Just figured I'd
give folks here a chance to comment on it. Case number has been x'd-out
to protect the innocent :) So far, no real help from MS. Here is my
latest (and most descriptive) correspondence. Feel free to read whatever
you like between the lines.
CASE_ID_NUM: SRZxxxxxxxxxxxx
MESSAGE:
For reference: The machine is a brand new hp a1528x Pavilion AMD 64 Dual
Core 2Ghz PC with 2Ghz RAM with an original Samsung 200Gb SATA hard
drive.
This new machine was reloaded from the original XP Media Center OS to XP
Pro (retail) the day after purchase (last month). Repartitioned with
long format. The frequent chkdsk /f "minor" and "unused index" errors
persist. Here is what I have done so far in an attempt to eliminate the
problem. The errors are being reported in the Event log under the
Winlogon source in the Application log.
1) At the time of my original report (with original Samsung 200Gb SATA
7200rpm drive), I could run chkdsk /f (scheduled at reboot) and get
these "fixing minor errors" messages or "unused index" errors 3 out of 4
times. Roughly, every forth time or so, when run repeatedly, boot after
boot, I'd get a "no problems found" report. Then the errors would
commence again. This behavior continues today, even after all the below
actions. I can still get one clean "no problems found" report if I run
it enough times.
2) Ran the manufactures hard disk checking utility numerous times and
got no errors found. (Added note: also ran the BIOS embeded S.M.A.R.T HD
test, no problems found - forgot to metion this in the origianl report
to MS).
3) As you suggested, I booted from the original XP Pro CD and ran chkdsk
from the recovery console. Unfortunately, when using the internal
command chkdsk, when booted with the CD, no "/f" option is available, as
you suggested I use. The only options available are /p and /r. I used
both. This chkdsk version doesn't produce much in the way of error
reports on screen. However, the first time I ran it with /p, I got the
"one or more errors found" message (no indication of what those were
though). I next ran it with /r switch and got no errors reported
(although a "no errors found" report was not shown on screen - simply
nothing was said). I then ran it repeatedly with the /p switch and
continued to get error-free reports on screen. Rebooted to XP Pro on
hard disk, chkdsk /f, rebooted, errors back again.
4) Went to store and purchased brand new hard drive, different brand,
different size, new cable (Western Digital 250Gb SATA 7200rpm). Loaded
fresh copy of XP Pro from my original XP Pro disk (retail, not OEM) with
no other software loaded at all. Ran chkdsk /f. Still seeing same
errors.
5) Installed SP2 onto fresh XP PRO (sp1 embedded) installation. After
SP2 installed, same errors.
The machine continues to operate perfectly all the time. Never any
"actual" problems.
What next?
-Frank
.
- References:
- chkdsk /f errors in Event Log
- From: Frankster
- Re: chkdsk /f errors in Event Log
- From: Gerry Cornell
- Re: chkdsk /f errors in Event Log
- From: Frankster
- chkdsk /f errors in Event Log
- Prev by Date: How to determine if I'm connected to the internet via my cable modem
- Next by Date: Lock Computer?
- Previous by thread: Re: chkdsk /f errors in Event Log
- Next by thread: Re: chkdsk /f errors in Event Log
- Index(es):
Relevant Pages
|
