Chkdsk output

G

Guest

I found an event ID 7 ("The device, \Device\Harddisk0\D, has a bad block") in
the system event log.

I ran chkdsk (from the GUI, with both disk options selected - "automatically
fix file system errors" and "scan for and attempt recovery of bad sectors")

The Winlogon ouput reports a read error, but doesn't mention which file is
involved or whether it has attempted to reassign the bad block(s). Does that
mean it recovered the data or what?

I guess I need to replace the disc (4 years old), but is there any way I can
tell which files are corrupted? I have backups which I may be able to use to
replace bad files.

I don't want to copy bad data across to a new disc and then incorporate it
into my backups thinking I have good copies.

The full chkdsk output is:

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 24 unused index entries from index $SII of file 0x9.
Cleaning up 24 unused index entries from index $SDH of file 0x9.
Cleaning up 24 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0xb2cf57000 for 0x10000 bytes.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

78075899 KB total disk space.
66565988 KB in 196404 files.
80376 KB in 23193 indexes.
0 KB in bad sectors.
306131 KB in use by the system.
65536 KB occupied by the log file.
11123404 KB available on disk.

4096 bytes in each allocation unit.
19518974 total allocation units on disk.
2780851 allocation units available on disk.

Thanks to anyone who can help.
Regards,
Geoff
 
G

Guest

I was lead to believe that the same utility runs whether I use the GUI
version or the command line version of Chkdsk, in which case this will just
repeat the same process. Is there a particular reason why you feel this is
different? Thanks Andrew.
 
G

Gerry

Geoff

I wouldn't be overconcerned about what happened. I would lust run
chkdsk occasionally to see if further problems occur.

File fragments can be found using Windows Explorer using "*.chk"
without the quotes as the search criteria. They open with Notepad.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
G

Guest

Thanks Gerry.

The only fragments (all 8KB) I found were:

C:\WINDOWS\SYSTEM32\CatRoot2\edb.chk
C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.chk
C:\I386\edb.chk

Does that mean anything to anyone?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top