aethl

Emulated disk still mounted and data was good. Re-assigned the disk and started rebuild again. Thank you for the help and quick responses!! Much appreciated.

Ah this makes sense. Thank you!!

So I pulled all my drives. Double checked all connections and restarted. Got the notification that array turned good. However, I do not see an option to resume my disk rebuild. Do I just hit this option to check? The disk just has an x next to it.

Got it. Will be doing that now. Thanks for the reply.

Hi. I was in the middle of replacing a disk in my array. Old disk had some errors pop up so I decided to just replace it. Just followed these steps to replace and rebuild from parity (https://wiki.unraid.net/Replacing_a_Data_Drive). Everything seemed to be going fine. Woke up this morning to a bunch of emails of errors with the array and the rebuild paused. I am thinking I just shutdown the server. Verify all the connections to the hard drives and restart it, but I wanted to post here first just to confirm there isnt something else going on. Any help is appreciated. Parity disk - WDC_WD80EFAX-68LHPN0_7SGH7J5C (sdi) (errors 273) Disk 1 - ST4000DM000-2AE166_WDH17F9N (sdm) (errors 272) Disk 2 - WDC_WD80EMAZ-00WJTA0_JEHBJ13N (sde) (errors 273) Disk 3 - ST4000DM005-2DP166_ZGY0278T (sdl) (errors 272) Disk 4 - WDC_WD80EFAX-68LHPN0_7SGH8J6C (sdh) (errors 273) Disk 5 - WDC_WD80EZAZ-11TDBA0_2YJL29UD (sdk) (errors 273) Disk 6 - ST8000VN004-2M2101_WSD80EY2 (sdg) (errors 273) Disk 7 - WDC_WD80EMAZ-00WJTA0_1EHKMAJZ (sdc) (errors 273) Disk 8 - WDC_WD80EMZZ-11B4FB0_WD-CA06ABKK (sdd) (errors 273) Disk 9 - WDC_WD80EMZZ-11B4FB0_WD-CA06A16K (sdf) (errors 273) Disk 10 - ST8000VN004-2M2101_WSD9DMGQ (sdj) (errors 1024) * **Unable to write to disk1** * **Unable to write to disk2** * **Unable to write to disk3** * **Unable to write to disk4** * **Unable to write to disk5** * **Unable to write to disk6** * **Unable to write to disk7** * **Unable to write to disk8** * **Unable to write to disk9** unraid-diagnostics-20230123-0712.zip

Got it. Thank you!

Is there anything in the diagnostics that is worrying? From what I have seen all my data looks good and SMART for all the drives is also good.

I have a Dell C6100 server, which has 4 compute nodes. I fully reseated the node Unraid is running on and confirmed all the drives are seated as well as all the HBA connections. I did not check the power supply connections but I will do that once the parity sync finishes. It has redundant power supplies but I just dont want to mess with it right now.

Update: I found another post of someone with the same problem where the issue was a loosely seated HBA card. I shut down the server again and double checked that and confirmed it was seated properly.

Hi All, Received a random alert this evening stating that my parity drive is in an error state (Parity disk in error state (disk dsbl)). Then received another message saying the entire drive has errors. Parity disk - (sdj) (errors 3847670) Disk 1 - (sdm) (errors 844) Disk 2 - (sde) (errors 256) Disk 3 - (sdl) (errors 76) Disk 4 - (sdh) (errors 256) Disk 5 - (sdk) (errors 256) Disk 6 - (sdi) (errors 92) Disk 7 - (sdc) (errors 256) Disk 8 - (sdd) (errors 653479) Disk 9 - (sdf) (errors 256) Once I received that email notification I was unable to access the GUI and most of my docker containers seemed to have crashed. I was able to console in and run diagnostics via CLI, attached as postcrash. I powered everything down and pulled power cables as well. Started bringing things back up slowly, I confirmed that all my drives are being read by the server, they can all be seen in the bios and by Unraid. Once Unraid came back up fully it gave me an error stating the parity drive was disabled. I had Array auto-start enabled so the array was half started at this point. I then stopped the array, pulled another diagnostics (postreboot) and ran a short SMART test of the parity drive (shows no errors). Would appreciate some assistance on how to proceed with this. Thanks! unraid-diagnostics-20220530-2139-postreboot.zip unraid-diagnostics-20220530-2031-postcrash.zip

Ah ok cool. So I think steps 1-5 are sort of already done here since when I power-cycled the server the disk was showing as missing at the HBA level so unraid already marked it as missing/unassigned. Thanks!

Got it, SMART tests dont show any errors. I have the array in a stopped state right now, when the array was started all the data looked good and nothing was missing.

Ok I was wrong, its not dead. Moved it to another slot and it picked back up again. Now its showing as a new disk. From what I understand, unraid would have dropped the disk from the array once the errors were detected. If I add it back to the array as a new disk, the parity should just rebuild it and I should be good to go right?

Yeah I will try moving to a different slot, but I think its dead. I really appreciate the help, thank you!

Sorry I should have been more specific, I did a full shutdown on the server (pulled power cables) and then powered on.