We help IT Professionals succeed at work.
Private
Troubleshooting Question

Running CHKDSK correctly and able to view a log after the run

jana
jana asked
on
92 Views
Last Modified: 2020-09-07
Hi Experts!

I have run in a computer the command:
chkdsk /f /r
 
I get the message:
Chkdsk cannot run because the volume is in use by another
process.  Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Which I answer yes (which in turn gives the below message)
This volume will be checked the next time the system restarts

I shut down completely the computer and turn it back on.

and it seem it started the process (see below):


I want to make sure I am doing the correct thing.

So 2 questions:
  1. Please advice if I am missing steps to do a correct chkdsk
  2. also, how do I see the after-effect or results of the chkdsk?
Comment
Watch Question

Hypercat (Deb)President
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Hi Hypercat,

Good to know I am doing the rights steps.
However using Optimizing my SSD is not recommended; I have used it before, never seen a results result data after a chkdsk.

Hi CompProbSolv,

Thanx for the link.  I do remember just last week I did use Event Viewer but nothing was found related to a chkdsk I did.  Right it's running a chkdsk, so when it finish will trye event viewer.

Event viewer is the only way to see chkdsk resluts?
CERTIFIED EXPERT

Commented:
If you look at the link I shared you'll see that you can get to the same info with PowerShell.

Author

Commented:
Yes.  I will proceed as soon as it finish (it's still going)
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
i wonder why it takes such steps to see a simple chkdsk result; and why did they hide the old summmary after running it?  that was easy, and is enough for most uses.

Author

Commented:
Chkdsk used to show the result after running but no more.

Just woke up and noticed that the computer is in the “Automatic Repair” screen.

  • Is that normal? 
  • Or the computer restarted after the chkdsk? 
  • What should I do?


Author

Commented:
Went into Event Viewer and can't determine anything on the chkdsk, if it was process completely or interrupted.

Googled for possible help and found that look for ID 26226 ot ID 1001 or look for winnit in source column.

So I am stuck here.

How can I see an actual result of the chkdsk?
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
what disk model is it?  and how long took the dskchk ?
in event viewer did you check the chkdsk and wininit items for filtering??
CERTIFIED EXPERT

Commented:
"Went into Event Viewer and can't determine anything on the chkdsk "
Where did you look in Event Viewer?

Author

Commented:
Application

Author

Commented:
Where should I look and what should look for?
(help please)
CERTIFIED EXPERT

Commented:
Yes... Windows Logs... Application should be the place to find it

Author

Commented:
What should I look for in Windows Logs >> Application ?
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Thank u very much!!!! I have read it but quite did not get it until u just made it clear!

Here is the log.  I noticed the bad sectors and the read failure, but can u give your input in plain English as possible?

Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          8/28/2020 6:00:57 AM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      acpc
Description:


Checking file system on \\?\Volume{e734c126-f34c-41a1-99c4-3d1a31d625c4}
The type of the file system is NTFS.


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.
 Phase duration (File record verification): 60.33 milliseconds.
  0 large file records processed.                                    

 Phase duration (Orphan file record recovery): 2.01 milliseconds.
  0 bad file records processed.                                      

 Phase duration (Bad file record checking): 1.93 milliseconds.

Stage 2: Examining file name linkage ...
  286 index entries processed.                                                        

Index verification completed.
 Phase duration (Index verification): 37.49 milliseconds.
  0 unindexed files scanned.                                         

 Phase duration (Orphan reconnection): 2.00 milliseconds.
  0 unindexed files recovered to lost and found.                     

 Phase duration (Orphan recovery to lost and found): 2.30 milliseconds.
  0 reparse records processed.                                       

  0 reparse records processed.                                       

 Phase duration (Reparse point and Object ID verification): 3.98 milliseconds.

Stage 3: Examining security descriptors ...
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.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 24.31 milliseconds.
  16 data files processed.                                            

 Phase duration (Data attribute verification): 2.06 milliseconds.
CHKDSK is verifying Usn Journal...
  224336 USN bytes processed.                                                            

Usn Journal verification completed.
 Phase duration (USN journal verification): 13.29 milliseconds.
Read failure with status 0xc000009c at offset 0x11ed7000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x11ee1000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x11ee2000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x11ee2000 for 0x1000 bytes.
Replacing bad clusters in logfile.
Adding 2 bad clusters to the Bad Clusters File.

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

    909311 KB total disk space.
    580192 KB in 13 files.
        76 KB in 17 indexes.
         8 KB in bad sectors.
      5687 KB in use by the system.
      4736 KB occupied by the log file.
    323348 KB available on disk.

      4096 bytes in each allocation unit.
    227327 total allocation units on disk.
     80837 allocation units available on disk.
Total duration: 162.01 milliseconds (162 ms).

Internal Info:
00 01 00 00 2a 00 00 00 26 00 00 00 00 00 00 00  ....*...&.......
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-08-28T12:00:57.3311574Z" />
    <EventRecordID>18784</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>acpc</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on \\?\Volume{e734c126-f34c-41a1-99c4-3d1a31d625c4}
The type of the file system is NTFS.


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.
 Phase duration (File record verification): 60.33 milliseconds.
  0 large file records processed.                                    

 Phase duration (Orphan file record recovery): 2.01 milliseconds.
  0 bad file records processed.                                      

 Phase duration (Bad file record checking): 1.93 milliseconds.

Stage 2: Examining file name linkage ...
  286 index entries processed.                                                        

Index verification completed.
 Phase duration (Index verification): 37.49 milliseconds.
  0 unindexed files scanned.                                         

 Phase duration (Orphan reconnection): 2.00 milliseconds.
  0 unindexed files recovered to lost and found.                     

 Phase duration (Orphan recovery to lost and found): 2.30 milliseconds.
  0 reparse records processed.                                       

  0 reparse records processed.                                       

 Phase duration (Reparse point and Object ID verification): 3.98 milliseconds.

Stage 3: Examining security descriptors ...
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.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 24.31 milliseconds.
  16 data files processed.                                            

 Phase duration (Data attribute verification): 2.06 milliseconds.
CHKDSK is verifying Usn Journal...
  224336 USN bytes processed.                                                            

Usn Journal verification completed.
 Phase duration (USN journal verification): 13.29 milliseconds.
Read failure with status 0xc000009c at offset 0x11ed7000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x11ee1000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x11ee2000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x11ee2000 for 0x1000 bytes.
Replacing bad clusters in logfile.
Adding 2 bad clusters to the Bad Clusters File.

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

    909311 KB total disk space.
    580192 KB in 13 files.
        76 KB in 17 indexes.
         8 KB in bad sectors.
      5687 KB in use by the system.
      4736 KB occupied by the log file.
    323348 KB available on disk.

      4096 bytes in each allocation unit.
    227327 total allocation units on disk.
     80837 allocation units available on disk.
Total duration: 162.01 milliseconds (162 ms).

Internal Info:
00 01 00 00 2a 00 00 00 26 00 00 00 00 00 00 00  ....*...&amp;.......
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
</Data>
  </EventData>
</Event>


also found another one more recently:
Log Name:      Application
Source:        Chkdsk
Date:          8/28/2020 6:13:23 AM
Event ID:      26228
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      acpc
Description:
Chkdsk was executed in verify mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume4
Volume label is Toshiba.

Examining 4 corruption records ...

Record 1 of 4: Corrupt File "<0x13,0x759f8>" ... The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x25.
no corruption found.

Record 2 of 4: Corrupt File "<0x11,0x759fa>" ... The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
no corruption found.

Record 3 of 4: Corrupt File "<0x10,0x759fb>" ... The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
no corruption found.

Record 4 of 4: Corrupt File "<0x10,0x75a04>" ... The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
no corruption found.

4 corruption records processed in 18.4 seconds.

Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Chkdsk" />
    <EventID Qualifiers="0">26228</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-08-28T12:13:23.3217918Z" />
    <EventRecordID>18821</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>acpc</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on \Device\HarddiskVolume4
Volume label is Toshiba.

Examining 4 corruption records ...

Record 1 of 4: Corrupt File "&lt;0x13,0x759f8&gt;" ... The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x25.
no corruption found.

Record 2 of 4: Corrupt File "&lt;0x11,0x759fa&gt;" ... The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
no corruption found.

Record 3 of 4: Corrupt File "&lt;0x10,0x759fb&gt;" ... The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
no corruption found.

Record 4 of 4: Corrupt File "&lt;0x10,0x75a04&gt;" ... The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
no corruption found.

4 corruption records processed in 18.4 seconds.

Windows has examined the list of previously identified potential issues and found no problems.
No further action is required.
</Data>
  </EventData>
</Event>


CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
it says Toshiba 2nd log
i use the HDDregenerator (not free) to correct that  http://www.dposoft.net/hdd.html   
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Hi CompProbSolv,

It's 1 TB drive, only 1 drive (I think it has a small d: drive for recovery)

Hi nobus,

Thanx for the info but for now, nit thinking of spening.  Is there any free apps?

Hi CompProbSolv,

 I wouldn't use a drive for anything important (other than copying files from it) after repairing it.  I just don't trust it.
will take in consideration.

Author

Commented:
FYI guys, I ran chkdsk again just in case... it's almost done (just to see the results)
andyalderretired saggar maker
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Could be, but not aware.  The computer is connected to a ups.  Nevertheless, it's possible.

Author

Commented:
Hi all,

I just saw the chkdsk process continue and return messages on both sources CHKDSK and WININIT as follows:

CHKDSK:
Log Name:      Application
Source:        Chkdsk
Date:          8/29/2020 2:39:48 AM
Event ID:      26226
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      acpc
Description:
Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on \Device\HarddiskVolume4
Volume label is Toshiba.

Stage 1: Examining basic file system structure ...
    Found 0x3 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4470" marked as free
        ... repaired online.
    Found 0x19d clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4473" marked as free
        ... repaired online.
    Found 0x5 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4611" marked as free
        ... repaired online.
    Found 0x8 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4617" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4620" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4622" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4625" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4628" marked as free
        ... repaired online.
    Found 0x7 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x462b" marked as free
        ... repaired online.
    Found 0x5 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4633" marked as free
        ... repaired online.
    Found 0xf clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4639" marked as free
        ... repaired online.
    Found 0x4 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4649" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4650" marked as free
        ... repaired online.
    Found 0xef clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4657" marked as free
        ... repaired online.
    Found 0x6 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x47ae" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x47b5" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x47b8" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x47bb" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x47be" marked as free
        ... repaired online.
    Found 0x6 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x47c0" marked as free
        ... repaired online.
    Found 0xa0 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x47c7" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4869" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x486d" marked as free
        ... repaired online.
    Found 0x5 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4870" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4879" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x487b" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4882" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4885" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4887" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4921" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4939" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4948" marked as free
        ... repaired online.
    Found 0x3 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x494a" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x494f" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4951" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4952" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4956" marked as free
        ... repaired online.
    Found 0x6 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x495a" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4961" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4963" marked as free
        ... repaired online.
    Found 0x5 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4966" marked as free
        ... repaired online.
    Found 0x14 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x496c" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4981" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4983" marked as free
        ... repaired online.
    Found 0x3 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4987" marked as free
        ... repaired online.
    Found 0x4 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x498b" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} <0xdc,0xc7a9>" at offset "0x4aaa" marked as free
        ... repaired online.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x37.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2c.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd3.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x25.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x77, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x23.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3e.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x43, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x26.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\210eae12-dfba-4cd8-8670-ffb49e734f62 <0x7a,0xa08fc>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\25be3602-512d-47c4-8ed9-744d4df1727a <0x51,0xa08fd>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\2f6bfb44-5ebb-40c9-aac2-3d2ddf77d2f8 <0x6f,0xa08fe>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\32d60460-2f39-45bf-b4e6-6dfbd471d404 <0xb7,0xa0900>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\3a93d549-2c6d-471b-bd4a-487595e254e4 <0x3f,0xa0902>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\63718848-e6fd-4036-800b-c3942bf9ab7d <0x82,0xa0903>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\676708e5-0a14-4332-a8d1-e5a2eea1f526 <0x59,0xa0904>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\684625bd-496c-43f1-838e-7043b6da0c43 <0x28,0xa0905>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\68e962f5-3f52-49b3-9f28-6bd6f9a63c2e <0x5e,0xa0906>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\7e8530e5-56e5-4f04-918e-979b9bc6e0f0 <0x4c,0xa0907>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\96a54fc7-ba92-4019-8abb-259d981214d4 <0x3d,0xa0908>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\999476c0-76fe-476f-9db6-ce1150abfbc9 <0x12a,0xa0909>"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\a1f0ad11-86e6-4bcf-9014-c54b0c50f6fa <0x2b,0xa090b>"
        ... repaired online.
  722944 file records processed.                                                        

File verification completed.
 Phase duration (File record verification): 9.20 minutes.
  24197 large file records processed.                                   

    Found unused file metadata marked as used

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


Stage 1: Examining basic file system structure ...
The segment number 0x8dcbc in file 0xa08fc is incorrect.
Fixing incorrect information in file record segment A08FC.
The segment number 0x8dcbd in file 0xa08fd is incorrect.
Fixing incorrect information in file record segment A08FD.
The segment number 0x8dcbe in file 0xa08fe is incorrect.
Fixing incorrect information in file record segment A08FE.
The segment number 0x8dcc0 in file 0xa0900 is incorrect.
Fixing incorrect information in file record segment A0900.
The segment number 0x8dcc2 in file 0xa0902 is incorrect.
Fixing incorrect information in file record segment A0902.
The segment number 0x8dcc3 in file 0xa0903 is incorrect.
Fixing incorrect information in file record segment A0903.
The segment number 0x8dcc4 in file 0xa0904 is incorrect.
Fixing incorrect information in fi
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Chkdsk" />
    <EventID Qualifiers="0">26226</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-08-29T08:39:48.5638895Z" />
    <EventRecordID>19559</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>acpc</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on \Device\HarddiskVolume4
Volume label is Toshiba.

Stage 1: Examining basic file system structure ...
    Found 0x3 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4470" marked as free
        ... repaired online.
    Found 0x19d clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4473" marked as free
        ... repaired online.
    Found 0x5 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4611" marked as free
        ... repaired online.
    Found 0x8 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4617" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4620" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4622" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4625" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4628" marked as free
        ... repaired online.
    Found 0x7 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x462b" marked as free
        ... repaired online.
    Found 0x5 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4633" marked as free
        ... repaired online.
    Found 0xf clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4639" marked as free
        ... repaired online.
    Found 0x4 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4649" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4650" marked as free
        ... repaired online.
    Found 0xef clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4657" marked as free
        ... repaired online.
    Found 0x6 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x47ae" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x47b5" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x47b8" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x47bb" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x47be" marked as free
        ... repaired online.
    Found 0x6 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x47c0" marked as free
        ... repaired online.
    Found 0xa0 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x47c7" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4869" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x486d" marked as free
        ... repaired online.
    Found 0x5 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4870" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4879" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x487b" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4882" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4885" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4887" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4921" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4939" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4948" marked as free
        ... repaired online.
    Found 0x3 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x494a" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x494f" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4951" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4952" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4956" marked as free
        ... repaired online.
    Found 0x6 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x495a" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4961" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4963" marked as free
        ... repaired online.
    Found 0x5 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4966" marked as free
        ... repaired online.
    Found 0x14 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x496c" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4981" marked as free
        ... repaired online.
    Found 0x2 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4983" marked as free
        ... repaired online.
    Found 0x3 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4987" marked as free
        ... repaired online.
    Found 0x4 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x498b" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\System Volume Information\{557e55a9-e929-11ea-80e2-008cfa238a0d}{3808876b-c176-4e48-b7ae-04046e6cc752} &lt;0xdc,0xc7a9&gt;" at offset "0x4aaa" marked as free
        ... repaired online.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x37.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2c.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd3.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x25.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x77, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x23.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3e.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x43, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x26.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\210eae12-dfba-4cd8-8670-ffb49e734f62 &lt;0x7a,0xa08fc&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\25be3602-512d-47c4-8ed9-744d4df1727a &lt;0x51,0xa08fd&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\2f6bfb44-5ebb-40c9-aac2-3d2ddf77d2f8 &lt;0x6f,0xa08fe&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\32d60460-2f39-45bf-b4e6-6dfbd471d404 &lt;0xb7,0xa0900&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\3a93d549-2c6d-471b-bd4a-487595e254e4 &lt;0x3f,0xa0902&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\63718848-e6fd-4036-800b-c3942bf9ab7d &lt;0x82,0xa0903&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\676708e5-0a14-4332-a8d1-e5a2eea1f526 &lt;0x59,0xa0904&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\684625bd-496c-43f1-838e-7043b6da0c43 &lt;0x28,0xa0905&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\68e962f5-3f52-49b3-9f28-6bd6f9a63c2e &lt;0x5e,0xa0906&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\7e8530e5-56e5-4f04-918e-979b9bc6e0f0 &lt;0x4c,0xa0907&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\96a54fc7-ba92-4019-8abb-259d981214d4 &lt;0x3d,0xa0908&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\999476c0-76fe-476f-9db6-ce1150abfbc9 &lt;0x12a,0xa0909&gt;"
        ... repaired online.
    Found corrupt basic file structure for "\Windows\System32\Microsoft\Protect\S-1-5-18\User\a1f0ad11-86e6-4bcf-9014-c54b0c50f6fa &lt;0x2b,0xa090b&gt;"
        ... repaired online.
  722944 file records processed.                                                        

File verification completed.
 Phase duration (File record verification): 9.20 minutes.
  24197 large file records processed.                                   

    Found unused file metadata marked as used

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


Stage 1: Examining basic file system structure ...
The segment number 0x8dcbc in file 0xa08fc is incorrect.
Fixing incorrect information in file record segment A08FC.
The segment number 0x8dcbd in file 0xa08fd is incorrect.
Fixing incorrect information in file record segment A08FD.
The segment number 0x8dcbe in file 0xa08fe is incorrect.
Fixing incorrect information in file record segment A08FE.
The segment number 0x8dcc0 in file 0xa0900 is incorrect.
Fixing incorrect information in file record segment A0900.
The segment number 0x8dcc2 in file 0xa0902 is incorrect.
Fixing incorrect information in file record segment A0902.
The segment number 0x8dcc3 in file 0xa0903 is incorrect.
Fixing incorrect information in file record segment A0903.
The segment number 0x8dcc4 in file 0xa0904 is incorrect.
Fixing incorrect information in fi</Data>
    <Binary>00080B00C5C40600AD940C0000000000290B000084CD00000000000000000000</Binary>
  </EventData>
</Event>

WININIT:
Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          8/29/2020 4:32:52 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      acpc
Description:


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


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 ...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x37.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2c.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd3.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x25.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x77, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x23.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3e.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x43, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x26.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
  722944 file records processed.                                                        


File verification completed.
 Phase duration (File record verification): 8.16 minutes.
  24194 large file records processed.                                   


 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                     


 Phase duration (Bad file record checking): 1.05 milliseconds.

Stage 2: Examining file name linkage ...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x37.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2c.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd3.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x25.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x77, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x23.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3e.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x43, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x26.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
  55485 reparse records processed.                                      


  904704 index entries processed.                                                       


Index verification completed.
 Phase duration (Index verification): 13.74 minutes.
  0 unindexed files scanned.                                        


 Phase duration (Orphan reconnection): 1.20 seconds.
  0 unindexed files recovered to lost and found.                    


 Phase duration (Orphan recovery to lost and found): 17.76 milliseconds.
  55485 reparse records processed.                                      


 Phase duration (Reparse point and Object ID verification): 135.74 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 7 unused index entries from index $SII of file 0x9.
Cleaning up 7 unused index entries from index $SDH of file 0x9.
Cleaning up 7 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 368.57 milliseconds.
  90881 data files processed.                                           


 Phase duration (Data attribute verification): 1.18 milliseconds.
CHKDSK is verifying Usn Journal...
  5301640 USN bytes processed.                                                           


Usn Journal verification completed.
 Phase duration (USN journal verification): 177.07 milliseconds.
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.

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

 965183100 KB total disk space.
 865658000 KB in 352843 files.
    234300 KB in 90882 indexes.
        52 KB in bad sectors.
    847972 KB in use by the system.
     65536 KB occupied by the log file.
  98442776 KB available on disk.

      4096 bytes in each allocation unit.
 241295775 total allocation units on disk.
  24610694 allocation units available on disk.
Total duration: 21.94 minutes (1316834 ms).

Internal Info:
00 08 0b 00 c1 c4 06 00 a4 94 0c 00 00 00 00 00  ................
29 0b 00 00 94 cd 00 00 00 00 00 00 00 00 00 00  )...............

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-08-29T22:32:52.9697716Z" />
    <EventRecordID>19588</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>acpc</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

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


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 ...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x37.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2c.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd3.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x25.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x77, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x23.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3e.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x43, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x26.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
  722944 file records processed.                                                        


File verification completed.
 Phase duration (File record verification): 8.16 minutes.
  24194 large file records processed.                                   


 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                     


 Phase duration (Bad file record checking): 1.05 milliseconds.

Stage 2: Examining file name linkage ...
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x37.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd2.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x2c.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0xd3.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x28.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x25.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x27.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x77, at block 0x1 is incorrect.
The expected value is 0x41.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x23.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x1f.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3e.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x43, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x3a.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x26.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
The USA check value, 0x0, at block 0x1 is incorrect.
The expected value is 0x22.
  55485 reparse records processed.                                      


  904704 index entries processed.                                                       


Index verification completed.
 Phase duration (Index verification): 13.74 minutes.
  0 unindexed files scanned.                                        


 Phase duration (Orphan reconnection): 1.20 seconds.
  0 unindexed files recovered to lost and found.                    


 Phase duration (Orphan recovery to lost and found): 17.76 milliseconds.
  55485 reparse records processed.                                      


 Phase duration (Reparse point and Object ID verification): 135.74 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 7 unused index entries from index $SII of file 0x9.
Cleaning up 7 unused index entries from index $SDH of file 0x9.
Cleaning up 7 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 368.57 milliseconds.
  90881 data files processed.                                           


 Phase duration (Data attribute verification): 1.18 milliseconds.
CHKDSK is verifying Usn Journal...
  5301640 USN bytes processed.                                                           


Usn Journal verification completed.
 Phase duration (USN journal verification): 177.07 milliseconds.
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.

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

 965183100 KB total disk space.
 865658000 KB in 352843 files.
    234300 KB in 90882 indexes.
        52 KB in bad sectors.
    847972 KB in use by the system.
     65536 KB occupied by the log file.
  98442776 KB available on disk.

      4096 bytes in each allocation unit.
 241295775 total allocation units on disk.
  24610694 allocation units available on disk.
Total duration: 21.94 minutes (1316834 ms).

Internal Info:
00 08 0b 00 c1 c4 06 00 a4 94 0c 00 00 00 00 00  ................
29 0b 00 00 94 cd 00 00 00 00 00 00 00 00 00 00  )...............

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
  </EventData>
</Event>
x
Prior closing the question, can u guys give me a glance of these second messages from chkdsk and should I worry about it?
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Understood.

So I can have at hand, based on what u have seen in the results-text, what should I look for to know it is a damaged disk?
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
The computer's drive is a Toshiba MQ01ABD100 SATA interface; is Hitachi Drive Fitness Test able to test Toshiba drive?

Also the site says "(However, Drive Fitness Test is bundled with some restoration utilities that will overwrite data)", does it mean at the test it will write to the drive?


CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
not if you do not run these

Author

Commented:
Thanx.

How about the apps, is Hitachi Drive Fitness Test compatible the Toshiba MQ01ABD100 (the drive is SATA interface) ?
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
jana - why don't you just try it??

Author

Commented:
because if its not compatible with Toshiba MQ01ABD10 i am afraid of further damage

So I just want to know if  Hitachi Drive Fitness Test compatible the Toshiba MQ01ABD100 
CERTIFIED EXPERT

Commented:
"i am afraid of further damage "
I've never seen a HD test that claims to be non-destructive cause any damage other than unrelated damage occurring because a drive is already failing.

Author

Commented:
Just asking to make sure (simple apps like SFC has damage other or my computers, so I need to be careful)


CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
Hi nobus, never cross my mind u would recommend a tool that would damage my pc; and u have helped me super support previously! so, please excuse me if I made u think that.

u have helped me more than enough in this question.  I will be running the tool in a couple of days and if anything out of the ordinary happens, I will post a new question.

Thank u very much!



Author

Commented:
Hi this is what I meant: the tool is not for Toshiba drives as per your link   https://ibm-hitachi-drive-fitness-test.en.softonic.com/ 

 
Is there another tool similar I can use for my Toshiba drive?
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
DFT wa s previously owned by IBM, and their disk section for hdd was taken over byHitachi
Jana, i had a toshiba dribe and tested the dft on it to be sure - guess what : it did not work
so i want to apologise to you, i was mistaken by mixing up hgst driver and toshiba
right now - i have sent a mail asking what software they suggest to use for diagnosis
Please undo you accepted answer -  since it is faulty
i will post the answer from Toshiba when i get one

Author

Commented:
Thank u!
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
there was an error in above post, first sentence should be : "taken over by Hitachi"
i corrected that

Author

Commented:
I just noticed that u didn't include a space before "hitachi" in your entry

Please let me know  about your entry on "i have sent a mail asking what software they suggest to use for diagnosis"

(u have a good suggestion, so I am looking for a compatible similar software for my Toshiba  hard drive)
CERTIFIED EXPERT

Commented:
Keep in mind that if the drive is failing, the longer you run it, the more likely it will fail further.  I'd seriously consider imaging it to a new drive unless you have a complete backup already.

Author

Commented:
Yes, thank u.  I just want to find something similar to the tool nobus recommended but for the Toshiba drive.
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
here the answer from Toshiba :
Dear Mr.nobus
thank you for contacting the Toshiba Storage Products Division.

For specific drives we offer the Toshiba Storage Dianostic Tool.
(Please take a look if your drives are supported in the attached manual to this e-mail)

https://www.toshiba-storage.com/wp-content/uploads/2020/06/ToshibaStorageDiagnosticTool_1.30.8920.zip

Alternatetively we recommed CrystalDiskInfo  for Windows.
A free version can be  downloaded under the following adress:
https://crystalmark.info/en/software/crystaldiskinfo/
 
Best regards
 
Jan Redenius
Support Specialist
Storage Product Business Marketing

Toshiba Electronics Europe GmbH
Hansaallee 181
40549 Duesseldorf
Germany
Tel. 00800-84685463
spdinfo@tee.toshiba.de
www.toshiba.semicon-storage.com, www.toshiba-storage.com

Author

Commented:
Nobus, U-D-BEST!!!!!! Thanx lots!!!!!
(I have been searching for this for the longest - really really EE are the TOPS!)
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
it makes me always happy when i can help someone

Author

Commented:
:)
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
in the meantime i've learned that toshiba differs from hitachi... lol

Author

Commented:
Thanx!
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
well the tshtool did not work for the drive i have here, and CRyDInfo only gives info - - that's ok, but still no diagnostic

Author

Commented:
On the Toshiba Diag Tool I did a 2 min test:

On the Crystal tool,

where i place the mouse over cauation, it display:

What u think?

CERTIFIED EXPERT

Commented:
The information continues to drive me to the conclusion that the drive should be replaced before it fails more seriously.  The longer you wait, the less likely you can image the drive successfully.  It could get bad enough that simple recovery of data files is problematic.

Author

Commented:
I understand, but based on what u have seen u think running these tools to fix, won't do?
CERTIFIED EXPERT

Commented:
There are two types of repairs that these programs will do.  The more common is to identify bad sectors on the disk, copy the data elsewhere, mark the sectors as bad, and redirect pointers to the new sectors.  That will fix the immediate problem, but if the drive has been having this number of problems, I get uneasy with expecting it not to get more.

The other repair (HD Regenerator, Spinrite, etc.) tries to read the drive over and over and "fix" the bad sectors if it can.  Nobus has had better success with this than I have.  If I can make a drive readable with these programs, my next step is to copy it to a new drive.  I'd much rather do that now than have to piece together the data later.  If the drive gets too bad it means installing Windows on a new drive, installing applications, copying data, etc.  I'm much more interested in trying to get the drive imaged as it is now rather than rebuilding later.

It's all a matter of cost vs. time/effort/recovery.  If you don't want to replace the drive, then make very sure that you keep backups of data you don't want to lose and installers (with whatever license codes you'll need) available if you have to rebuild.  You should have the latter (backups and installers) in any case, but I find that clients often have a difficult time locating such things.

Author

Commented:
understood. Thanx!
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
well it reports bad seactors, and reallocated ones.
in such cases, i run HDDRegenerator, and nearly everytime it returns me a working drive - and none came back with problems.
but it's up to you if you want to run it -  because it's not free; but on the other hand, you have the tool for all HDD drives ( not for SSD)

Author

Commented:
I would prefer the purchase of a new drive to be the last option.

What do you mean by "you have the tool for all HDD drives ( not for SSD)"?
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
ih you have HDDReg, you can use it on all your drives, now and in the future
it's not like office where you pay each month...

Author

Commented:
 you have the tool for all HDD drives ( not for SSD) 

But what u meant by "not SSD"?
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
SSD's have their own diags, since it is build of RAM chips, not a rotating drive

Author

Commented:
Hi nobus, thank u very much for such great info, but I don't thinks it's fair for u since this question is closed.  I do have more questions regarding this topic, so I will place a question about it.

Again, thank u!
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.