I was going through the wiki steps to make unraid to trust a drive without rebuilding it. Unfortunately I made a mistake in the following step:

 

If necessary, refresh your unRAID Web Management Main page in your browser. For UnRaid 4.7 ensure you DO NOT refresh the unRAID Web Management Main page in your browser.

 

Since my unraid version is 5.0 rc10 i decided to refresh the web management page (bad decision), now all my drives are unassigned.

 

I'm stuck, my server is still on and i have a backup of my flash drive. What should i do to restore my array?

 

Please.

Avraham

Do you KNOW which drives are cache and which are Parity?  (by serial number or other unique identifier)

For example, do you have a saved screenshot of the prior web interface showing how the serial numbers were assigned?

I would need to open up the case since i sticked a note next to each drive with their serial number, but I do.

 

I don't have a cache drive, only parity. Is it safe to power down the server in this state?, since I would need to open it ?

 

Is there a way to know this information if I have a backup of the flash drive?

 

Thanks for the reply.

Searching a bit more in the forums I read that I could restore the drives assignments with my backup of super.dat ?

I would like some confirmation before messing more things up.

 

Thanks

Be patient...your situation is a rare combination of things...

Better that you wait for an unRAID Wizard to weigh in on solutions...

 

 

Shutdown and restore the super.dat file to the flash. You understand that unRAID disabled the disk because a write to it failed and its contents are very likely incorrect. The procedure that your attempting is almost always the wrong thing to do.

Shutdown and restore the super.dat file to the flash. You understand that unRAID disabled the disk because a write to it failed and its contents are very likely incorrect. The procedure that your attempting is almost always the wrong thing to do.

 

Thanks, I restored the assignments with the super.dat file.

Yes, I understand something went wrong in a writing process, but I am almost sure it was a sata cable issue. Anyway, I'm rebuilding it from parity just to make sure.

 

Thanks for the help to everyone.