darthjonathan12 Posted December 13, 2018 Share Posted December 13, 2018 I have a drive (disk 2) that has refused to spin up, I've tested it on a few different systems and it still won't spin up. So the array restarted and now It says that all the data on the parity will be overwritten. it also thinks that the parity and disk 1 are new drives when they are not. How do I start up the array with the disk missing so I can access the data until the new replacement drive shows up? If I can't start up without a new drive How do I start it up without losing any data? Quote Link to comment
trurl Posted December 13, 2018 Share Posted December 13, 2018 How exactly did you get to this state? Since parity and disk1 are in fact ALL of your disks then you must have either done a New Config yourself, or else it couldn't read your disk assignments from flash. Did you New Config? Don't do anything else without further advice. Go to Tools - Diagnostics and attach the complete diagnostics zip to your next post. Quote Link to comment
darthjonathan12 Posted December 13, 2018 Author Share Posted December 13, 2018 Here it is. tower-diagnostics-20181213-1720.zip Quote Link to comment
darthjonathan12 Posted December 13, 2018 Author Share Posted December 13, 2018 a few days ago I accidentally bumped the power cable on the drive and unraid refused to run off of it. So I ran a new config so It would read off the disk again and it rebuilt parity and was fine, Today I tried to add some ssd's and bumped it again, so I ran the new config but this time the drive won't spin up at all. Quote Link to comment
trurl Posted December 13, 2018 Share Posted December 13, 2018 Well you might just try checking all your connections again. You must always double check all connections any time you are mucking about in the case. New Config was not the right way to fix your problem either time. New Config tells Unraid to reset your disk assignments and optionally rebuild parity. So after a New Config you can't rebuild a failed disk without some trickery. I am going to suggest that you shut down your server and leave it down until you are ready to replace that disk. Then we can discuss the trickery required to rebuild it. If you don't follow this advice then there will probably be no way to recover that data. Quote Link to comment
darthjonathan12 Posted December 13, 2018 Author Share Posted December 13, 2018 Ok I'll comment again when my new drive arrives Quote Link to comment
darthjonathan12 Posted December 13, 2018 Author Share Posted December 13, 2018 Ok I decided that my time was more important than money and caved and bought an 8tb from Best Buy just now so I wouldn't have to wait for shipping, I am ready to get this server back up and running. Quote Link to comment
trurl Posted December 13, 2018 Share Posted December 13, 2018 I have to leave for a few hours. I will tag @johnnie.black to see if he can help you. I suspect he will want you to do the invalidslot command. Quote Link to comment
darthjonathan12 Posted December 13, 2018 Author Share Posted December 13, 2018 ok, I won't touch it until you or Johnnie are back. Quote Link to comment
JorgeB Posted December 13, 2018 Share Posted December 13, 2018 If parity is valid, and the by way you describe what happened it should be, this should work to rebuild disk2: -Assign the new disk2 -Important - After that leave the browser on that page, the "Main" page. -Open an SSH session/use the console and type: 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, disk2 will start rebuilding, disk should mount immediately but if it's unmountable don't format, wait for the rebuild to finish and then run a filesystem check 1 1 Quote Link to comment
darthjonathan12 Posted December 14, 2018 Author Share Posted December 14, 2018 ok as a newbie you mean I should just paste that line directly into the terminal without anything in front of it? Quote Link to comment
darthjonathan12 Posted December 14, 2018 Author Share Posted December 14, 2018 Ok its rebuilding disk 2!!!!!!!!!!!!!!!! Everything is great!!!!! I'll run a parity check once the disk is rebuilt and hopefully I can get a refund on the 2 month old drive that failed on me. Thank you so much trurl and johnnie.black!!!!!!!!!!!! Quote Link to comment
tuxfania Posted December 14, 2018 Share Posted December 14, 2018 18 hours ago, johnnie.black said: If parity is valid, and the by way you describe what happened it should be, this should work to rebuild disk2: -Assign the new disk2 -Important - After that leave the browser on that page, the "Main" page. -Open an SSH session/use the console and type: 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, disk2 will start rebuilding, disk should mount immediately but if it's unmountable don't format, wait for the rebuild to finish and then run a filesystem check Johnnie, Can you break down what the mdcmd command does...specifically the "29"? Thanks! Quote Link to comment
JorgeB Posted December 14, 2018 Share Posted December 14, 2018 31 minutes ago, tuxfania said: Johnnie, Can you break down what the mdcmd command does...specifically the "29"? Thanks! Sets the specified slots as invalid after a new config, 29 is for parity2 since the OP doesn't have one. 1 Quote Link to comment
tuxfania Posted December 14, 2018 Share Posted December 14, 2018 1 hour ago, johnnie.black said: Sets the specified slots as invalid after a new config, 29 is for parity2 since the OP doesn't have one. Thanks...that makes sense... 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.