I was in the middle of replacing a drive..powered down the server,  disconnected the smaller one, connected the larger one.. Powered up the system.. only to find that I now have two unformatted drives. Seems wiht the power cycle I one of my drives whent to unformatted status. I checked before the power down and it was fine. I have since tried to power cycle and it still comes up unformatted.

 

Any way to put it back into normal status, so I can rebuild my array?

Running Unraid 4.4

I was in the middle of replacing a drive..powered down the server,  disconnected the smaller one, connected the larger one.. Powered up the system.. only to find that I now have two unformatted drives. Seems wiht the power cycle I one of my drives whent to unformatted status. I checked before the power down and it was fine. I have since tried to power cycle and it still comes up unformatted.

 

Any way to put it back into normal status, so I can rebuild my array?

Running Unraid 4.4

unformatted simply means "not mounted"

 

Post a copy of your syslog so we can figure out what is happening.  (if the prior shutdown was not clean it could take a bit of time for the file-system to mount, as it re-plays transaction first )

thank you for your reply.

I unhooked the new drive, rebooted cracefully, and the new drive showed up as missing (as you would expect since it was not connected).. but the other drive that had been showing up as unformatted was just fine.. So I powered down and re-connected the new drive.. sure enough the drive came back up and and both drives are once again unformatted.

 

I will let it sit for a few hours and see if unraid just fixes everything for me.

 

working on getting the logs.

So I Put the original drive back. I got three drives colored some other color (I am color blind - I really wish Unraid would use a square, triangle, and circle icon to help us).  See attached screen cap.

Here is as much of the syslog as I can get..I did the CP method recomended in the link but the file never showed up on my share...

 

Regardless I did a telnet and cat of the syslog and gave you what I could

 

 

In regards to the raid array. I THINK I must tell it to re-store the array, now that I have all the drives back and online. The data has not changed since I started this debacle so I am not worried about losing changed data.. but I don't want to lose the data.

New_Text_Document_3.zip

So given that all my drives are back to the way they were, and given the information in the screen capture... is this one of the few instances where I should select "yes I am sure" and tell it to restore the array?

 

The overall plan is to put the original drive back in (which I have done), get the array working perfectly once again, then upgrade to the latest stable version, THEN try to replace that drive that had been giving me problems.

 

sound good???

You can do that if you are sure all the drives are healthy. That will invalidate parity and start a parity build.

ok that got me back to where all the drives are found as they should be... A parity check is running but I STILL have one unformatted drive...

 

Can I upgrade to a newer version in this state? I read the newer versions don' thave as much of a problem with the unformatted drive issue.

 

Can I force the drive to mount? then restart the parity check?

 

I need to get this back up soon. Please.

 

bump

You have a bunch of errors showing on that drive. Something is wrong with it. A syslog might help diagnose the issue. You could also try shutting down, swapping the power and SATA cables and booting again.

 

 

attached is my new log. you are right, drive 8 has mucho errors. I tried changing the cables but no luck. It is interesting that the drive shows as unmounted and not just dead...

 

assuming drive 8 is dead.. I have one dead drive and an invalid parity drive. What are my options... I thought of letting the parity sync finish.. not sure that is a good idea... not sure it will even finish.

 

 

So what do I do next? I assume I lost data.. but what do I do next to get back to some type of normal.

 

 

on second thought.. the log file is too large.

anyone? what is the best way to minimize the damage from this catastrophy?

zip the log.

zipped it is 5 megs, and it said it was too large to upload. I can prune it a bit and re-try.

You could also split the zip into small segments and upload each segment on a different post.  PITA but should work.