I'm on 7.0.0 and did a parity drive swap.  Before the swap I had a zero error parity check and all drives healthy.  Now, as the parity-sync started, I have an array drive showing read errors.  Can I stop the parity sync and revert back to my original parity drive? Then I could replace the array drive. Do I just let it run?

  

Please post the diagnostics.
 

unraid-diagnostics-20250208-1007.zip

 

My largest array drive is 8tb an my parity drive was 14tb.  I was swapping the 14tb drive with an 8tb drive as I had lots of wasted space and planned to use the 14tb as a USB backup.  

Also, as I have space on other drives, is another option to move the data from the errored drive to another healthy drive on the array?

Update: Parity - sync completed - 98 errors - One disk has SMART error

Edited February 8, 20251 yr by HutchG

Disk1 has a pending sector, you can try to see if it can still be correctly emulated with the old parity, but keep the old disk1 intact for now.

 

This will only work if parity is still valid with the old disk:

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments and assign any missing disk(s) if needed, including the new disk1, replacement disk should be same size or larger than the old one
-IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked)
-Stop array
-Unassign disk1
-Start array (in normal mode now), and post new diagnostics

I don't have a replacement disk for disk 1 yet, the only "extra" disc I have is the original 14tb parity.  It sounds like, following your instructions, I could return the original parity drive to the parity slot, check the two boxes, use the new parity drive as the drive 1 replacement.

Am I understanding that correctly?  Then I stop the array, unassign disk1 and restart the array in normal mode?  Won't it then give me an error disk1 is missing?

 

Thanks for the help. 

You can use current disk1 for the instructions, data won't be touched, unless you then tried to rebuild.

Okay, I have followed instructions, original parity disk returned and errored disk shows unassigned.  It shows parity is valid.  Here is my new diagnostics.

unraid-diagnostics-20250210-1610.zip

Edited February 10, 20251 yr by HutchG

Check filesystem on the emulated disk1, it's mounting but there are still issues.

Do I press the FIX button?

Yep

Okay, now I'm here.  Not sure exactly what this is this is telling me.  Can I just mount, somehow run the log, then unmount using Unassigned devices or do I need to stop the array, re-add disk1, run the log, then remove again? 
 

Click Zero log, usually that's fine.

Okay, it says no corruption detected now, here is the latest diagnostics.

unraid-diagnostics-20250212-1142.zip

Restart in normal mode and the drive should now mount OK.

Okay now it appears I am back to square one, no errors and all drives show healthy. This is great so far.  I ran a short SMART test on disk1, the previously errored drive, and it completed without error.  I have the extended SMART test running and hope it runs fine.  

Where do you recommend I go from here?  Remember, my original plan was to swap my 14tb parity drive with an 8tb drive as it was overkill for my array and I could use the 14tb as a USB backup device.  If I retry that I might end up with errors again and be where I started this thread.  Should I now prioritize replacing the possibly dying drive1 first or could I move the drive1 data and eliminate it as I have empty space in the rest of the array?  

 

Please advise

You should replace disk1 first, or move the data from the emulated disk1 to other disks, if there's enough space, then do a new config without it.

I think the easiest will be to replace the disk.  I will do that and start a new thread if I need more help.

Thank you @JorgeB for all your patience and help, beer money sent.

 

Thanks!