David

If you've synced, then recovery using snapraid is gone. Verifying after running fix to make sure all of the recovered files are there. Snapraid is idempotent so running it multiple times to ensure all files have been recovered is recommended. I know this doesn't help much now, but always verify after recovery whenever using any tool while recovery is still an option.

Didn't you verify the files were restored on the new drive?

Grok says Vendor,Tool,How to mark bad block Seagate,SeaTools for DOS/Windows,"""Advanced Tests → Set Bad Sector""" WD,Data Lifeguard Diagnostics,"""Write Zeros to Sector"" → forces remap" Samsung,Magician,"""Diagnostic Scan"" → manual sector test" Intel/HGST,Drive Feature Tool,DFT -bad command And Open elevated PowerShell $sector = 12345678 $drive = 0 # \.\PhysicalDrive0 $fs = [IO.File]::Open("\.\PhysicalDrive$drive", 'Open', 'ReadWrite', 'None') $fs.Seek($sector * 512, 'Begin') $bad = [byte[]]@(0xDE,0xAD,0xBE,0xEF)...

Can you use a tool to manually mark the block as bad?

Thanks. Another donation sent.

Ah, ok. Depends on how full the drives were which dictates how parity was calculated.

I don't understand what you mean.

More than likely not. You can try, but you only had a single parity drive.