isaw Posted February 15, 2020 Author Share Posted February 15, 2020 7 minutes ago, trurl said: I was talking about using one of these same disks. I pulled 3*8tbs from my old server to replace the 1tb's. the 8tb's were my old raid 5 array which i copied the data from in the first place. Quote Link to comment
trurl Posted February 16, 2020 Share Posted February 16, 2020 Here is a recent thread with the invalidslot situation: https://forums.unraid.net/topic/77771-multiple-errors/?do=findComment&comment=720061 Quote Link to comment
trurl Posted February 16, 2020 Share Posted February 16, 2020 Hold on I am looking for a better example Quote Link to comment
trurl Posted February 16, 2020 Share Posted February 16, 2020 Here is another https://forums.unraid.net/topic/84039-one-drive-failed-while-rebuilding-with-a-new-drive-a-second-drive-failed/?do=findComment&comment=778735 but none of these are exactly where you are now. I recommend patience and see what @johnnie.black recommends. Quote Link to comment
isaw Posted February 16, 2020 Author Share Posted February 16, 2020 (edited) 1 hour ago, trurl said: Here is another https://forums.unraid.net/topic/84039-one-drive-failed-while-rebuilding-with-a-new-drive-a-second-drive-failed/?do=findComment&comment=778735 but none of these are exactly where you are now. I recommend patience and see what @johnnie.black recommends. ok thanks. will read all and see where i end up. hopefully johnnie isnt too far away! Edited February 16, 2020 by isaw Quote Link to comment
JorgeB Posted February 16, 2020 Share Posted February 16, 2020 So, I think you have now re-assigned all disks as they were before this (parity should still be valid) and you want to rebuild disk2, also you started the array in maintenance mode and luckily for you since a few releases Unraid doesn't automatically start a sync/rebuild in maintenance mode, so no harm done. I didn't re-read the entire thread so if I'm missing something please advise, assuming the above is correct: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed -Important - After checking the assignments leave the browser on that page, the "Main" page. -Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters): mdcmd set invalidslot 2 29 -Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk2 will start rebuilding, disk should mount immediately (probably not in this case) but if it's unmountable don't format, wait for the rebuild to finish and then run a filesystem check Quote Link to comment
isaw Posted February 16, 2020 Author Share Posted February 16, 2020 started this off now. @johnnie.black you mention a file system check, can you specify the commands for that please? Quote Link to comment
JorgeB Posted February 16, 2020 Share Posted February 16, 2020 If the emulated disk2 is unmountable post current diags, or just the syslog. The command to run after the rebuild finishes (and starting in maintenance mode) is: xfs_repair -v /dev/md2 Also, if it asks for -L use it. Quote Link to comment
isaw Posted February 17, 2020 Author Share Posted February 17, 2020 xfs repair has finished, there are a number of files (read basically everything) in the lost+found folder, but the folder structure is all gone. I think its going to be easier to try and run up my old raid5 array and copy off it.... Quote Link to comment
JorgeB Posted February 17, 2020 Share Posted February 17, 2020 That's a shame, and it suggests parity wasn't 100% valid, though we already new it wouldn't be 100% because of the disks being mounted read/write outside parity, still xfs_repair can usually mostly recover form that. Quote Link to comment
trurl Posted February 17, 2020 Share Posted February 17, 2020 1 hour ago, johnnie.black said: suggests parity wasn't 100% valid Possibly there were some details about what happened that weren't fully explained or understood. 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.