SlimReaper Posted March 16, 2023 Share Posted March 16, 2023 Server was off when I woke up, booting it back up and now nothing will mount when I start the array, I tried to do a health check on the parity drive and it says disc read failed. Any advice would be much appreciated. reaper-diagnostics-20230316-0911.zip Quote Link to comment
JorgeB Posted March 16, 2023 Share Posted March 16, 2023 Diags only show the array stopped after the boot, auto-start is disabled, did you start the array? Also make sure you are not using Firefox. Quote Link to comment
SlimReaper Posted March 16, 2023 Author Share Posted March 16, 2023 Ok, I'm using Chrome and just attempted to start the array. Thank you for the reply. reaper-diagnostics-20230316-1005.zip Quote Link to comment
JorgeB Posted March 16, 2023 Share Posted March 16, 2023 Disk3 is disabled and parity appears to be failing so you're in a bad spot, is disk3 new and if yes do you still have the old one? Quote Link to comment
SlimReaper Posted March 16, 2023 Author Share Posted March 16, 2023 Disk3 is not new Quote Link to comment
JorgeB Posted March 16, 2023 Share Posted March 16, 2023 Best bet is possibly to clone disk3 with ddrescue to a new disk (same size), then use that clone together with the remaining data disks and a new parity and rebuild the array. Quote Link to comment
SlimReaper Posted March 16, 2023 Author Share Posted March 16, 2023 Ok, I will go buy a drive and try. I appreciate you taking time to help me. Thanks again. 1 Quote Link to comment
SlimReaper Posted March 17, 2023 Author Share Posted March 17, 2023 (edited) Ok, I did ddresucre, I'm a bit confused because it finished instantly.. Was this drive empty? Edited March 17, 2023 by SlimReaper Quote Link to comment
JorgeB Posted March 17, 2023 Share Posted March 17, 2023 ddrescue does a sector by sector copy, does not matter if there's data or not, strange part is the recued amount.. never seen that before. Quote Link to comment
SlimReaper Posted March 17, 2023 Author Share Posted March 17, 2023 (edited) Uh oh. Any ideas? Maybe I'll try to start the array without Disk3 Yea that didn't work. lol Edited March 17, 2023 by SlimReaper Quote Link to comment
SlimReaper Posted March 17, 2023 Author Share Posted March 17, 2023 Are we able to do a Short self test on the parity drive? Every time I try it says "Completed: read failure" Do you think this drive could be the culprit? Can you do ddrescue on the parity drive? I just don't want to erase everything or do something I cannot undo. Quote Link to comment
JorgeB Posted March 17, 2023 Share Posted March 17, 2023 The array was stopped when you did that right? Quote Link to comment
SlimReaper Posted March 17, 2023 Author Share Posted March 17, 2023 It was in Maintenance Mode. Quote Link to comment
JorgeB Posted March 17, 2023 Share Posted March 17, 2023 Array should be stopped, reboot and try again. Quote Link to comment
SlimReaper Posted March 17, 2023 Author Share Posted March 17, 2023 (edited) Ok, stopped, rebooted, and ran check again. same message "Completed: read failure" I attached the Diagnostics, not sure if it will help. reaper-diagnostics-20230317-1207.zip Edited March 17, 2023 by SlimReaper Quote Link to comment
JorgeB Posted March 17, 2023 Share Posted March 17, 2023 I meant run ddrescue again. Quote Link to comment
SlimReaper Posted March 17, 2023 Author Share Posted March 17, 2023 (edited) Oh, I did ddrescure with the array stopped. My apologies for the mix up. Should I try it on the parity drive? Edited March 17, 2023 by SlimReaper Quote Link to comment
JorgeB Posted March 17, 2023 Share Posted March 17, 2023 OK, I think I know what happened, you used an existing log file, ddrescue will resume if you use an existing log file, so if that was from a complete rescue it won't do anything, use a different log file or delete the existing one. Quote Link to comment
SlimReaper Posted March 17, 2023 Author Share Posted March 17, 2023 oh snap! I think we are getting somewhere! Quote Link to comment
JorgeB Posted March 17, 2023 Share Posted March 17, 2023 Not a great sign that the mount option is disabled, run xfs_repair on the cloned disk once it done, don't forget the partition, e.g.: xfs_repair -v /dev/sdX1 Quote Link to comment
SlimReaper Posted March 17, 2023 Author Share Posted March 17, 2023 Ok, will do! Thank you! Quote Link to comment
SlimReaper Posted March 19, 2023 Author Share Posted March 19, 2023 (edited) Ok, finally got all the files transferred and did the repair. Server still stuck at mounting on disk2 when trying to start the array with the new cloned HD in the disk3 spot. Am I missing a step? I let it try to mount all night. reaper-diagnostics-20230319-0837.zip Edited March 19, 2023 by SlimReaper Quote Link to comment
JorgeB Posted March 20, 2023 Share Posted March 20, 2023 Diags show disk3 as invalid, did you do a new config with the cloned disk3? Quote Link to comment
SlimReaper Posted March 20, 2023 Author Share Posted March 20, 2023 (edited) Good morning Jorge, So the server would never rebuild and just say mounting forever. So I was just playing around and put a new disk in the parity2 spot. Once I did this everything started rebuilding. It finished this morning and now my main screen looks like this. Looks like Disk 3 still has some issues, and I think there is something wrong with my main parity disk as it is showing 299 errors and the self test fails to read. Also I'm not 100% sure how to do a new config with disk3. Edited March 20, 2023 by SlimReaper Quote Link to comment
Solution JorgeB Posted March 20, 2023 Solution Share Posted March 20, 2023 28 minutes ago, SlimReaper said: So the server would never rebuild and just say mounting forever. You should not rebuild, you should do a new config (Tools -> New config) with the cloned disk3 installed in place of the old one. Quote Link to comment
Recommended Posts
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.