drgambit

Follow-up: Just finished the rebuild with no issues. Thanks again for all your help!

Thanks all! I will run the replacement this weekend and let you know how it goes!

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!

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!

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…

Diagnostics attached server-diagnostics-20250317-2307.zip

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!