February 8, 20233 yr 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)
February 8, 20233 yr Author 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
February 8, 20233 yr Community Expert After a reboot the syslog is lost, I can only see that parity looks healthy, so re-sync and if it happens again post new diags, you can also replace/swap cables before to rule that out.
February 8, 20233 yr Author 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!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.