fatal error on D drive rebooted and Fixing D: stage 1 going very slow

I had a D drive disk fatal error. The D is my data with start up systems (windows 10) on an SSD C drive. the attempted to restart had Preparing to Fix stuck for about 30 minutes. The second attempt to start was with shift key and it went into check disk. It progressed quickly to D: 50% then began clicking through files slowly (about 400 over the last 1:30). At this point I'm at 311700 in 613100) with the "Total; 17%; ETA; 6.30.00 and the time keeps crept up

... I am a newbie at systems work like this and I don't know exactly what the system notice is saying (above) or it's doing
here in stage 1 or what to expect in time (if this is just the damaged sector bogging and the rest should go quicker?)
... what to expect in the next stages ? ... similar ?
... any thought on whether to grind this out or is there a better way to go about this ? .
... any help would be appreciated

The disk drive file system is typically NTFS.

When there is corruption of the drive file system Windows may flag the drive as dirty.

The next boot triggers a chkdsk scan.

Chkdsk has multiple stages and typically displays an ETA that may change significantly during the stages

It accomplishes little to interrupt the scan and is best to allow it to run overnight and if necessary the next day.

The speed depends upon many factors some of which include:
a) the switches selected
b) the problems found during the scan
c) the size of the drive
d) the size of files on the drive
e) the free space on the drive
etc.

This drive has significant problems.
It is 750 GB.
It took over 4 hours and there were no major problems on this scan.
The prior scan also took over 4 hours but had many problems.
At sometime the ETA had displayed over 10 hours on an earlier run.

Code:

  Log Name: Application
  Source: Chkdsk
  Date: 2021-01-23T00:10:49.540
  Event ID: 26226
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-K2CP43S
  Description: 
Chkdsk was executed in scan mode on a volume snapshot.  

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

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

File verification completed.
  8906 large file records processed.                                   

  0 bad file records processed.                                     


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

  805396 index entries processed.                                                       

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered to lost and found.                    

  421 reparse records processed.                                      


Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  82315 data files processed.                                           

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

Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 722633727 KB total disk space.
 149122892 KB in 323718 files.
    209364 KB in 82316 indexes.
         0 KB in bad sectors.
    769379 KB in use by the system.
     65536 KB occupied by the log file.
 572532092 KB available on disk.

      4096 bytes in each allocation unit.
 180658431 total allocation units on disk.
 143133023 allocation units available on disk.

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


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...

Code:

TimeCreated : 1/19/2021 1:08:51 AM
Message     : 
              
              Checking file system on C:
              The type of the file system is NTFS.
              Windows will now check the disk.                         
              Volume label is Windows.
              
              Examining 25 corruption records ...
              
              Record 1 of 25: Corruption in index "$I30" of directory 
              "\Windows\Temp\_97E96BED-BE0D-4390-8FDA-DD4BC7CA6BEF 
              <0x16,0x1ffd0>" ... The multi-sector header signature for VCN 0x4 
              of index $I30
              in file 0x1ffd0 is incorrect.
              e4 07 0b 00 00 00 0f 00 ?? ?? ?? ?? ?? ?? ?? ??  ................
              unexpected corruption found.
              
              25 corruption records processed in 0.1 seconds.
              
              Windows could not fix all issues with this drive.
              Please run chkdsk /f to find and fix all problems with this drive.

Code:

TimeCreated : 1/20/2021 12:25:22 AM
Message     : Chkdsk was executed in verify mode on a volume snapshot.  
              
              Checking file system on \Device\HarddiskVolume2
              Volume label is Windows.
              
              Examining 64 corruption records ...
              
              Record 1 of 64: Corrupt File "<0x9,0x733a4>" ... no corruption 
              found.
              
              Record 2 of 64: Corrupt File "<0x9,0x733a5>" ... no corruption 
              found.
              
              Record 3 of 64: Corrupt File "<0x9,0x733a6>" ... no corruption 
              found.
              
              Record 4 of 64: Corrupt File "<0x9,0x733a7>" ... no corruption 
              found.
              
              Record 5 of 64: Corrupt File "<0x9,0x733a8>" ... no corruption 
              found.
              
              Record 6 of 64: Corrupt File "<0x9,0x733aa>" ... no corruption 
              found.
              
              Record 7 of 64: Corrupt File "<0x9,0x733ab>" ... no corruption 
              found.
              
              Record 8 of 64: Corrupt File "<0x9,0x733ac>" ... no corruption 
              found.
              
              Record 9 of 64: Corrupt File "<0xd,0x733ad>" ... no corruption 
              found.
              
              Record 10 of 64: Corrupt File "<0xc,0x733af>" ... no corruption 
              found.
              
              Record 11 of 64: Corrupt File "<0xc,0x733b0>" ... no corruption 
              found.
              
              Record 12 of 64: Corrupt File "<0xc,0x733b1>" ... no corruption 
              found.
              
              Record 13 of 64: Corrupt File "<0xa,0x733b4>" ... no corruption 
              found.
              
              Record 14 of 64: Corrupt File "<0xa,0x733b5>" ... no corruption 
              found.
              
              Record 15 of 64: Corrupt File "<0xb,0x733b6>" ... no corruption 
              found.
              
              Record 16 of 64: Corrupt File "<0x9,0x733b7>" ... no corruption 
              found.
              
              Record 17 of 64: Corrupt File "<0x9,0x733b8>" ... no corruption 
              found.
              
              Record 18 of 64: Corrupt File "<0x9,0x733b9>" ... no corruption 
              found.
              
              Record 19 of 64: Corrupt File "<0x9,0x733ba>" ... no corruption 
              found.
              
              Record 20 of 64: Corrupt File "<0xd,0x733bb>" ... no corruption 
              found.
              
              Record 21 of 64: Corrupt File "<0x9,0x733bc>" ... no corruption 
              found.
              
              Record 22 of 64: Corrupt File "<0x9,0x733bd>" ... no corruption 
              found.
              
              Record 23 of 64: Corrupt File "<0x9,0x733be>" ... no corruption 
              found.
              
              Record 24 of 64: Corrupt File "<0x9,0x733bf>" ... no corruption 
              found.
              
              Record 25 of 64: Corrupt File "<0x9,0x733c0>" ... no corruption 
              found.
              
              Record 26 of 64: Corrupt File "<0x9,0x733c1>" ... no corruption 
              found.
              
              Record 27 of 64: Corrupt File "<0x9,0x733c2>" ... no corruption 
              found.
              
              Record 28 of 64: Corrupt File "<0x9,0x733c4>" ... no corruption 
              found.
              
              Record 29 of 64: Corrupt File "<0x9,0x733c5>" ... no corruption 
              found.
              
              Record 30 of 64: Corrupt File "<0x9,0x733cb>" ... no corruption 
              found.
              
              Record 31 of 64: Corrupt File "<0x9,0x733cc>" ... no corruption 
              found.
              
              Record 32 of 64: Corrupt File "<0x9,0x733cd>" ... no corruption 
              found.
              
              Record 33 of 64: Corrupt File "<0x9,0x733ce>" ... no corruption 
              found.
              
              Record 34 of 64: Corrupt File "<0x9,0x733d0>" ... no corruption 
              found.
              
              Record 35 of 64: Corrupt File "<0x9,0x733d1>" ... no corruption 
              found.
              
              Record 36 of 64: Corrupt File "<0x9,0x733d3>" ... no corruption 
              found.
              
              Record 37 of 64: Corrupt File "<0x9,0x733d4>" ... no corruption 
              found.
              
              Record 38 of 64: Corrupt File "<0x9,0x733d5>" ... no corruption 
              found.
              
              Record 39 of 64: Corrupt File "<0x9,0x733d6>" ... no corruption 
              found.
              
              Record 40 of 64: Corrupt File "<0x9,0x733d7>" ... no corruption 
              found.
              
              Record 41 of 64: Corrupt File "<0x9,0x733d8>" ... no corruption 
              found.
              
              Record 42 of 64: Corrupt File "<0x9,0x733dc>" ... no corruption 
              found.
              
              Record 43 of 64: Corrupt File "<0x9,0x733dd>" ... no corruption 
              found.
              
              Record 44 of 64: Corrupt File "<0x9,0x733de>" ... no corruption 
              found.
              
              Record 45 of 64: Corrupt File "<0x9,0x733e0>" ... no corruption 
              found.
              
              Record 46 of 64: Corrupt File "<0x9,0x733e1>" ... no corruption 
              found.
              
              Record 47 of 64: Corrupt File "<0x9,0x733e4>" ... no corruption 
              found.
              
              Record 48 of 64: Corrupt File "<0x7,0x733e5>" ... no corruption 
              found.
              
              Record 49 of 64: Corrupt File "<0x7,0x733e7>" ... no corruption 
              found.
              
              Record 50 of 64: Corrupt File "<0x7,0x733e8>" ... no corruption 
              found.
              
              Record 51 of 64: Corrupt File "<0x9,0x733e9>" ... no corruption 
              found.
              
              Record 52 of 64: Corrupt File "<0x9,0x733ea>" ... no corruption 
              found.
              
              Record 53 of 64: Corrupt File "<0x9,0x733fc>" ... no corruption 
              found.
              
              Record 54 of 64: Corrupt File "<0x9,0x733fe>" ... no corruption 
              found.
              
              Record 55 of 64: Corrupt File "<0x9,0x733ff>" ... no corruption 
              found.
              
              Record 56 of 64: Corrupt File "<0x9,0x73400>" ... no corruption 
              found.
              
              Record 57 of 64: Corrupt File "<0x9,0x73401>" ... no corruption 
              found.
              
              Record 58 of 64: Corrupt File "<0x9,0x73402>" ... no corruption 
              found.
              
              Record 59 of 64: Corrupt File "<0x7,0x73403>" ... no corruption 
              found.
              
              Record 60 of 64: Corrupt File "<0x7,0x73404>" ... no corruption 
              found.
              
              Record 61 of 64: Corrupt File "<0x8,0x73406>" ... no corruption 
              found.
              
              Record 62 of 64: Corrupt File "<0x9,0x73408>" ... no corruption 
              found.
              
              Record 63 of 64: Corrupt File "<0x9,0x73409>" ... no corruption 
              found.
              
              Record 64 of 64: Corrupt File "<0x9,0x7340b>" ... no corruption 
              found.
              
              64 corruption records processed in 0.1 seconds.
              
              Windows has examined the list of previously identified potential 
              issues and found no problems.
              No further action is required.

I am not sure what the process is here as CHKDSK never appeared. The attachment is what comes up on screen with a shift/start up
... I am not sure if this is a R repair process which I have read is not good for usable data ... I have unfortunately found a recent back up to be corrupt/problematic as well (separate external drive) so there is a priority to try to get this dat off intact.

There is also the matter of the C drive, which was operational till I shut down for a restart, naively thinking that might resolve the error. if I remove the D drive and restart, can I get the C drive up and running to regain my station and the programs residing on it ?

Attachment 315767

Mipa said:

I am not sure what the process is here as CHKDSK never appeared. The attachment is what comes up on screen with a shift/start up
... I am not sure if this is a R repair process which I have read is not good for usable data ... I have unfortunately found a recent back up to be corrupt/problematic as well (separate external drive) so there is a priority to try to get this dat off intact.

There is also the matter of the C drive, which was operational till I shut down for a restart, naively thinking that might resolve the error. if I remove the D drive and restart, can I get the C drive up and running to regain my station and the programs residing on it ?

Attachment 315767

The attachment displayed:
Message
Invalid Attachment specified. If you followed a valid link, please notify the administrator

Zbook ... I uploaded a screen picture ... the image shows on my link ... newbie user error is this chkdsk or R repairing at this stage ?

That was stage 1: Examining basic file system structure
Can you allow it to run without interruption?

Thank you for your help, I very much appreciate it. I can let it run if it is just examining with no harm
... will I be prompted for the next stage when complete ?

When the tool is running it typically does not stop.

https://docs.microsoft.com/en-us/win...ommands/chkdsk


ChkDsk Process on NTFS Volumes - Windows 7 Tutorial


https://www.dell.com/support/kbdoc/e...ng-dell-server