Windows 10: Got a huge amount of "correcting sparse file record segment" during chkdsk of a RAID...

[COLOR=rgba34, 34, 34, 1]Windows 10 System[/COLOR]

[COLOR=rgba34, 34, 34, 1]Google has given me nothing, nearly all the results are from people who were posting a log and it had other errors that were flat-out read failures of a dying drive...... or they were results about MYSQL, which I don't use at least not manually.[/COLOR]

[COLOR=rgba34, 34, 34, 1]I had just re-assembled a RAID5 array from a dead system, and performed a clone of the drives as a backup. I ran a chkdsk on the backup and got hundreds of "correcting sparse file record segment" messages, though other than cleaning up two or three security entries and index descriptors those were the only errors I got.[/COLOR]

[COLOR=rgba34, 34, 34, 1]Can anyone explain what this is? Is it something to be worried about? Again, this was cloned off a RAID5 disk to a single external drive, is it something to do with the RAID5 metadata itself? I noticed after the fact in the logs that the raid said it was performing a "Patrol Read" at the time of the backup, could that have something to do with it?[/COLOR]

:)

 

Attribute record (80, "") corrupt file segments

Keep getting a message that I need to restart to repair something. I restart and the drive is scanned and repair initiated but doesn't fix whatever needs fixing. I run CHKDSK from command prompt and get the following 10 files (see below) showing
as corrupt. I run /f, and /r and restart but the problem persists. I don't have a backup disc. Computer is about 10 years old AMD Phenom II X6 1100T Processor but I replaced the hard drive about 4 years ago. Any advice is appreciated!

Microsoft Windows [Version 10.0.17763.1098]

(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>chkdsk

The type of the file system is NTFS.

Volume label is New Volume.

WARNING! /F parameter not specified.

Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...

Attribute record (80, "") from file record segment 64E5

is corrupt.

Attribute record (80, "") from file record segment 12E9D

is corrupt.

Attribute record (80, "") from file record segment 132C8

is corrupt.

Attribute record (A0, $I30) from file record segment ****

is corrupt.

Attribute record (80, "") from file record segment 299AE

is corrupt.

Attribute record (80, "") from file record segment 32825

is corrupt.

Attribute record (80, "") from file record segment 43C23

is corrupt.

Attribute record (80, "") from file record segment 4F10D

is corrupt.

Attribute record (80, "") from file record segment 63E23

is corrupt.

Attribute record (80, "") from file record segment 99280

is corrupt.

825856 file records processed.

File verification completed.

41989 large file records processed.

Errors found. CHKDSK cannot continue in read-only mode.

C:\WINDOWS\system32>

 

Identify file name(s) associated with chkdsk corrupt file record segments

I have a Dell XPS15, 32 GB RAM, 1 TB SSD, Windows 10.

The following are the results from CHKDSK read-only:

Since it cannot continue, does that imply that there may be additional existing errors?

My understanding is that CHKDSK /R will recover 'READABLE' information.
So, before I run chkdsk /r, is there any way to identify the filename(s) associated with:

• file 7ADAE
  
• file record segment 1003F
  
• file record segment 21D8F
  
• file record segment 74337
  
• file record segment 74CF5
  

Once I identify the filenames I plan on restoring them from a recent backup after running
`chkdsk /r.

 

Recurring portable drive error: 'The sparse flag in standard information attribute in file _______ is not set.'

I have a portable drive that often slows Windows 10 boot. When performing an error check on this drive as recommended after booting (Properties->Tools->Error checking), it will say errors were found on the drive. The Event Viewer Chkdsk summary mentions something like:

The problem is that this error is never fixed but keeps repeating, with a different file identified each time. Does anyone have an idea how to fix this error for good since it slows the boot process?