March 18, 20251 yr Hello, I didn't want to zombie a older post on the forum but I wanted to know if there were some new steps to this process. I just replaced a parity drive in my array and discovered that after the parity was rebuilt another drive in my array is showing read errors... What I have found so far (in older posts) is to: 1. Place the new drive in the server, and preclear, but leave it unassigned 2. Keep all drives in the server and use the 'New Config' option, making sure to 'preserve current assignments' 3. Unassign the bad drive and replace it with the new precleared drive in the settings? 4. Make sure parity is checked as not valid when starting the array 5. After the array is started, and parity is rebuilt, remount the bad drive (under unassigned devices) and move any files back to the array I'm worried about this process because I don't want to lose data. Is there any example online of this process so that i can see it performed? I also have a cache and several containers running as well, will those be affected with a new config? Thanks!
March 18, 20251 yr Community Expert Forget about New Config in this scenario. Don't do anything without further advice. Attach Diagnostics to your NEXT post in this thread.
March 18, 20251 yr Community Expert Diags are after rebooting, which drive had read errors, and were they during the parity sync or only after the new parity got built?
March 18, 20251 yr Author I had rebooted because the extended smart scan is failing almost instantly after starting. I thought it was a fluke… i have a record of alerts from when the parity check was running and when the drive reported read errors… let me post those…
March 18, 20251 yr Community Expert 1 hour ago, drgambit said: extended smart scan is failing 3 hours ago, JorgeB said: which drive
March 18, 20251 yr Community Expert 1 hour ago, drgambit said: extended smart scan is failing almost instantly after starting. I thought it was a fluke # 1 Extended offline Completed: read failure 10% 34729 7771900672 This is never a fluke Unassigned sde (S#xRTH2) has failed extended self-test so should not be used for anything. But, none of your assigned disks are disabled and all are mounted with plenty of data. So not clear why you think anything needs to be done. Did you already do New Config without sde and rebuild parity? Wish you had asked before doing anything at all. If that disk was part of the array, you probably could have rebuilt to a new disk from parity. But if parity was rebuilt instead, no way to rebuild that disk. Good luck on trying to copy any data from it.
March 19, 20251 yr Author Apologies for not replying until now, to answer your question, I have not performed any steps. My system is in the same state, drive 2 has failed... I replaced my parity drive which was having smart drive errors as well: All the drives heated up overnight: Then, after a while I got this message: But then right after I got this one: So disk 2 in my array is now bad... and that's where I am at now. Like I said before I didn't run any steps or anything else, I guess I made the assumption that my parity is bad because drive 2 reported read errors after the rebuild of the parity drive. If you think (by the diagnostics) that I am OK with parity, then should i go ahead and just replace the drive as normal and rebuild? Thanks for your help with all of this, I really appreciate it!
March 19, 20251 yr Community Expert Were those diagnostics you already posted taken after all those things in these screenshots? If not post new diagnostics
March 19, 20251 yr Author Yes, that's correct. The only thing I did before I created the diagnostics was reboot because I thought the extended smart report was too fast, which now I know not to do that from now on!
March 19, 20251 yr Community Expert Disk2 should be replaced, would prefer to see the diags to confirm, but based on the notifications, looks like there weren't read errors during the parity sync.
March 19, 20251 yr Community Expert Solution 5 hours ago, JorgeB said: Disk2 should be replaced Sorry missed that. It also failed extended test just like the unassigned disk. The procedure you outlined in your first post is wrong. Assuming you intend to replace it with another 4TB disk, here is the correct procedure: https://docs.unraid.net/unraid-os/manual/storage-management/#normal-replacement
March 21, 20251 yr Author Thanks all! I will run the replacement this weekend and let you know how it goes!
April 6, 20251 yr Author Follow-up: Just finished the rebuild with no issues. Thanks again for all your help!
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.