CHKDSK log file


Joined
Jul 30, 2016
Messages
7
Reaction score
0
I have a Seagate 2TB drive that is starting to fail. Random programs not respnding for 10-30 seconds. (no crashes) I did a test using the Seagate software an it failed the first test. Software suggested running CHKDSK and to retry. I ran the CHKDSK with f and unfortunately it still failed the Seagate test. I have tried to clone the drive with Seagate and Aomei and neither would complete the cloning. Below is the log file from the CHKDSK - With this untrained eye - I can't tell just how sick it really is. Anyone know the details of reading these logs files ? I belive the scan on 6/15 is when the drive started to show signs of failing. (not sure) Thank you for looking

TimeCreated : 6/23/2020 4:54:38 PM
Message :

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
816128 file records processed.

File verification completed.
22188 large file records processed.

0 bad file records processed.


Stage 2: Examining file name linkage ...
53746 reparse records processed.

1077908 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered to lost and found.

53746 reparse records processed.


Stage 3: Examining security descriptors ...
Cleaning up 8528 unused index entries from index $SII of file 0x9.
Cleaning up 8528 unused index entries from index $SDH of file 0x9.
Cleaning up 8528 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
130891 data files processed.

CHKDSK is verifying Usn Journal...
38572296 USN bytes processed.

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
816112 files processed.

File data verification completed.

Stage 5: Looking for bad, free clusters ...
454125706 free clusters processed.

Free space verification is complete.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

1942207691 KB total disk space.
124367984 KB in 537806 files.
348948 KB in 130894 indexes.
0 KB in bad sectors.
987931 KB in use by the system.
65536 KB occupied by the log file.
1816502828 KB available on disk.

4096 bytes in each allocation unit.
485551922 total allocation units on disk.
454125707 allocation units available on disk.

Internal Info:
00 74 0c 00 ac 33 0a 00 ac 2e 13 00 00 00 00 00 .t...3..........
3c 07 00 00 b6 ca 00 00 00 00 00 00 00 00 00 00 <...............

Windows has finished checking your disk.
Please wait while your computer restarts.


TimeCreated : 6/15/2020 9:21:27 AM
Message :

Checking file system on \\?\Volume{424698e9-45f0-4981-a585-1a14f91d1922}
The type of the file system is NTFS.
Volume label is WINRETOOLS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
256 file records processed.

File verification completed.
4 large file records processed.

0 bad file records processed.


Stage 2: Examining file name linkage ...
The multi-sector header signature for VCN 0x0 of index $SII
in file 0x9 is incorrect.
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? ................
Correcting error in index $SII for file 9.
The index bitmap $SII in file 0x9 is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $SII for file 9.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? ................
Sorting index $SII in file 9.
2 reparse records processed.

314 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered to lost and found.

2 reparse records processed.


Stage 3: Examining security descriptors ...
Inserting an index entry with Id 100 into index $SII of file 9.
Inserting an index entry with Id 101 into index $SII of file 9.
Inserting an index entry with Id 102 into index $SII of file 9.
Inserting an index entry with Id 103 into index $SII of file 9.
Inserting an index entry with Id 104 into index $SII of file 9.
Inserting an index entry with Id 105 into index $SII of file 9.
Inserting an index entry with Id 106 into index $SII of file 9.
Inserting an index entry with Id 107 into index $SII of file 9.
Inserting an index entry with Id 108 into index $SII of file 9.
Inserting an index entry with Id 109 into index $SII of file 9.
Inserting an index entry with Id 10A into index $SII of file 9.
Inserting an index entry with Id 10B into index $SII of file 9.
Inserting an index entry with Id 10C into index $SII of file 9.
Inserting an index entry with Id 10D into index $SII of file 9.
Inserting an index entry with Id 10E into index $SII of file 9.
Inserting an index entry with Id 10F into index $SII of file 9.
Inserting an index entry with Id 110 into index $SII of file 9.
Inserting an index entry with Id 111 into index $SII of file 9.
Inserting an index entry with Id 112 into index $SII of file 9.
Inserting an index entry with Id 113 into index $SII of file 9.
Inserting an index entry with Id 114 into index $SII of file 9.
Inserting an index entry with Id 115 into index $SII of file 9.
Inserting an index entry with Id 116 into index $SII of file 9.
Inserting an index entry with Id 117 into index $SII of file 9.
Inserting an index entry with Id 118 into index $SII of file 9.
Inserting an index entry with Id 119 into index $SII of file 9.
Inserting an index entry with Id 11A into index $SII of file 9.
Inserting an index entry with Id 11B into index $SII of file 9.
Inserting an index entry with Id 11C into index $SII of file 9.
Inserting an index entry with Id 11D into index $SII of file 9.
Inserting an index entry with Id 11E into index $SII of file 9.
Inserting an index entry with Id 11F into index $SII of file 9.
Inserting an index entry with Id 120 into index $SII of file 9.
Inserting an index entry with Id 121 into index $SII of file 9.
Inserting an index entry with Id 122 into index $SII of file 9.
Inserting an index entry with Id 123 into index $SII of file 9.
Inserting an index entry with Id 124 into index $SII of file 9.
Inserting an index entry with Id 125 into index $SII of file 9.
Inserting an index entry with Id 126 into index $SII of file 9.
Inserting an index entry with Id 127 into index $SII of file 9.
Repairing the security file record segment.
Cleaning up 13 unused index entries from index $SII of file 9.
Cleaning up 13 unused index entries from index $SDH of file 9.
Cleaning up 13 unused security descriptors.
Security descriptor verification completed.
30 data files processed.

CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Read failure with status 0xc000009c at offset 0x2a000 for 0xa00 bytes.
The attribute definition table cannot be read.
Correcting errors in the Attribute Definition Table.
Correcting errors in the master file table's (MFT) BITMAP attribute.

Windows has made corrections to the file system.
No further action is required.

2097151 KB total disk space.
770260 KB in 89 files.
112 KB in 31 indexes.
4 KB in bad sectors.
13283 KB in use by the system.
12544 KB occupied by the log file.
1313492 KB available on disk.

4096 bytes in each allocation unit.
524287 total allocation units on disk.
328373 allocation units available on disk.

Internal Info:
00 01 00 00 84 00 00 00 80 00 00 00 00 00 00 00 ................
02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
 
Ad

Advertisements

Joined
Apr 22, 2017
Messages
3,752
Reaction score
477
Hi,

is this an SSD or HDD?, is this a laptop or normal PC?. If it is a PC, is the SSD/HDD connected to SATA0 on the motherboard?. :)
 
Joined
Jul 30, 2016
Messages
7
Reaction score
0
Wolfie- It's a Seagate Barracuda 2TB HDD Dell XPS 8500 desktop. Disk management labels it as Disk 0. I hope that answers your ?
I am not at the box today- it's is my office computer.
 
Last edited:
Joined
Jul 30, 2016
Messages
7
Reaction score
0
CrystalDiskinfo says caution but even worse it lists no file information at all. That can't be good. 49K hours on it. Wow.
 
Joined
Apr 22, 2017
Messages
3,752
Reaction score
477
Disk management labels it as Disk 0. I hope that answers your ?
Hi Snafu34,

if you can open the PC case and take a look at how the SATA cables are connected, it would help, if the HDD is in SATA2 (as an example), it can possibly lead to false readings if another drive (a different HDD/SDD or DVD) is using SATA0. :)
 
Ad

Advertisements

Joined
Oct 2, 2014
Messages
1,392
Reaction score
287
CrystalDiskinfo says caution but even worse it lists no file information at all. That can't be good. 49K hours on it. Wow.
Can you post a screenshot so we can see what's causing it? 50,000 hours isn't unheard of if your drive is running 24/7. I have an old pata drive from 2004 that only has 28,000 hours on it. But it's SMART data is fine.
 
Joined
Jul 30, 2016
Messages
7
Reaction score
0
Wolfie- The Del XPS has 4 SATA ports. The original hard drive is on sata0, dvd is on sata1 and the new drive in on sata2.

Bigfeet- here you are- sure look like the partitions got screwed up on the original hard drive.
 

Attachments

Last edited:
Joined
Apr 22, 2017
Messages
3,752
Reaction score
477
new drive in on sata2
Hi Snafu34,

is the new drive the one that currently runs your OS?. If it is, that would need to be connected to SATA0 and not SATA2!. ;)

Regardless of how many drives you have, the one containing the main OS should always be SATA0. :)
 
Joined
Oct 2, 2014
Messages
1,392
Reaction score
287
Hmmm. No information at all. I don't know why the drive isn't producing any SMART data. A "Caution" under health status doesn't necessarily mean there's imminent danger of the drive failing. I would be sure to backup any important data just in case. Maybe someone else will have more insight in to why it's not showing SMART data, or why it's throwing up a "Caution" under health status.
 
Joined
Jul 30, 2016
Messages
7
Reaction score
0
Hi Snafu34,

is the new drive the one that currently runs your OS?. If it is, that would need to be connected to SATA0 and not SATA2!. ;)

Regardless of how many drives you have, the one containing the main OS should always be SATA0. :)
The new drive, disk1 in disk management, is virtual empty. Windows 10 is on disk0. Crystal report if for disk0. CHKDSK log is for disk0
which I have attempted to clone to disk1
 
Ad

Advertisements

Joined
Apr 22, 2017
Messages
3,752
Reaction score
477
I am talking about the SATA connections on your motherboard, not what is showing in Disk Management!. ;)
 
Joined
Oct 2, 2014
Messages
1,392
Reaction score
287
I've had operating systems on all the sata ports while dual and triple booting without issue. It's ideal for the OS to be 0, but not necessary. On some motherboards like mine, 0 and 1 are faster ports. Anyways if you look at his disk management screenshot, his OS is Disk0.
 
Last edited:
Ad

Advertisements

Joined
Apr 22, 2017
Messages
3,752
Reaction score
477
It depends on whether the SATA ports are colour coded or not, if there is no colour code, it doesn't matter, if SATA0 is a different colour to the other SATA ports, it does. I always recommend using SATA0 for that just in case scenario!. :)
 

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