January 14, 20251 yr First, I had 2 drives "fail" about 6 weeks ago. one parity and one array. Thought is was the drive shelf, so replaced the shelf with a Dell 730xd. No issues moving to the new server, other then I replaced both drives, lost no data. Cool. Weird that neither of the "failed" drives showed any SMART errors. They also passed multiple pre-clear tests. Today, on the new server, I had both the exact same slots (same parity slot and same array slot) fail. The drives in those slots were new and somewhat new, pre-clear and tested 3 times before put in to service for the rebuild referenced above. The fact they were different drives then before but in the exact same slots is wildly odd to me. Plus, neither of these newly "failed" drives have any errors on them at all. The odd thing with this failure is all the drives (parity and array) threw errors (Unbalanced was moving some files at the time). Afterwards, all drives were inaccessible. Tried stopping the array. That happened I think after about 3 hours. Not for sure because I just walked away and let it go. I rebooted and got the wonderful (unclean shutdown) notice. So now my question/concern...... I know if I start the array, because of the unclean shutdown, the system will start a parity check. I would assume if that happens I will lose the array drive that the system says will be emulated? Am I correct in that assumption? Diags attached. sol-diagnostics-20250114-1809.zip Edited January 15, 20251 yr by jmbailey2000
January 15, 20251 yr Community Expert Diags are after rebooting, so we can't see what happened, did you save the older ones?
January 15, 20251 yr Author No previous diags unless they get saved automatically. I couldn't do anything on the server related to stored files. No drives could be accessed and most menu choices were unavailable. The only diags I was able to do was after the reboot. Guess my biggest question is related to starting the array. Right now 1 bad parity and 1 bad array drive (being emulated). With an unclean shutdown the parity check will fire up at start and will wipe out the emulated drive I assume? Can the parity check be avoided on array start so I can get the files off the emulated drive?
January 15, 20251 yr Community Expert Start the array and post new diags, to see if the emulated disk is mounting.
January 15, 20251 yr Author Won't parity check start (because of unclean shutdown) which means the emulated disk would go away?
January 15, 20251 yr Community Expert Solution You cancel the parity check if it starts, it won't change the emulated disk.
January 15, 20251 yr Author Weird. Started array and parity check didn't start. Array drive is mounted and I see files. Never had Unraid not start a parity check after an unclean shutdown. Guess I'll move files off and then replace the drives. Bizarre. Attached is the post start diags if needed, but at this point I'm guessing I'm good. sol-diagnostics-20250115-1515.zip
January 16, 20251 yr Community Expert Emulated disk is mounting, assuming contents look correct, you can rebuild on top and resync parity2, it may be worth swapping cables/slots for those two disks to rule that out if it happens again, and if it does grab diags before rebooting: https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself
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.