BlackLion

I'm going through the same process I did this weekend and the parity data-rebuild should be done in 12-15 hours. I'm assuming it won't take long before I start to see read errors again and the first thing I'll do is grab the diagnostics data. Thanks!

I did reboot last night after the issue reappeared (not realizing I should have run the diagnostics before the reboot) so hopefully this can still provide the information. The parity disk is still disabled, but I'm not seeing any new read errors. unraid-diagnostics-20230208-1050.zip

This happened a few days ago and I followed another suggestion of stopping the array, removed the parity disk from the array, started the array, shut it back down, reassigned the parity drive, and let it rebuild/verify the data. The rebuild finished on Sunday morning. Tonight I got the alert from my server that the errors are back. What's the best way to start troubleshooting these issue? Event: Unraid Parity disk error Subject: Alert [UNRAID] - Parity disk in error state (disk dsbl)

I won't worry about clearing the drive then. I've got 3 data drives. When the replacement drive comes in I will just add it as another data drive. Thanks for the info!

15 AUG - got the first notification "reported uncorrect is 1" 3 NOV - "reported uncorrect is 95" - had been periodically increasing 4 NOV - during parity check the disk was disabled once the "reported uncorrect" hit 429 I reached out to Seagate support and gave them the details and the SMART report info...about 5 minutes after I uploaded the info they said they were starting the RMA process.

My parity drive is failing, but with the RMA process it could be another couple of weeks before I get the replacement. I'm going to pick a new drive from a local store. My plan is to stop the array, swap the parity drive with the new drive, put the failing drive into another bay, and then start the array. My question is should I let the parity rebuild complete before I try to clear the failing drive? Or do I need to change my plan at all?