I have a failed disk in my array. I have plenty of free space in my array so I thought just to remove this disk.

 

I followed the instructions at

https://docs.unraid.net/unraid-os/manual/storage-management/

and 

https://docs.unraid.net/unraid-os/manual/storage-management/#reset-the-array-configuration

to set the failed disk as unassigned.

 

The failed disk now shows up in unassigned devices. But I thought this will rebuild the array from parity – but it appears to have done nothing and the missing disk just shows as “Not Installed” with the hint “Device is missing (disabled). Contents emulated”.

 

 

 

To fix this I am planning on doing the following:

 

1.       Move all files off emulated disk onto another disk (using Unbalanced).

2.       Check and double check nothing remains on the emulated disk.

3.       Stop array

4.       Remove unassigned failed disk and move all disks after this “up one” in the array list of disks.

5.       Restart array without parity rebuild

 

Am I correct in thinking this will work?

Edited February 3, 20251 yr by Geoff Bland
Using Unbalanced to move files not Krusader

37 minutes ago, Geoff Bland said:

4.       Remove unassigned failed disk and move all disks after this “up one” in the array list of disks.

5.       Restart array without parity rebuild

You would need to do a new config, before step 4, and parity would need to be rebuilt after array start.

Thanks for the response.

 

So:

1. Move all files off emulated disk onto another disk (using Unbalanced).
2. Check and double check nothing remains on the emulated disk.
3. Stop array
4. Set new config - using Tools | New Config 
5. Remove unassigned failed disk and move all disks after this “up one” in the array list of disks.
6. Restart array ensuring with parity rebuilt

 

Is this correct?

Edited February 4, 20251 yr by Geoff Bland

Yep

OK I tried this and it did not work.

 

On step 5 of the above I am unable to move the disks around.

 

If I move the next disk into the unassigned slot where the failed disk was and move all the following disks up one then I am unable to start the Array - "Invalid Configuration" and all but the next disk shows a red x and complains about "Missing" disk.

 

If I move the last disk into the unassigned slot where the failed disk was leaving the other disks as they are then I am unable to start the Array - "Invalid Configuration" and the last (now empty) slot shows a red x and complains about "Missing" disk.

 

 

 

What am I doing wrong?

Did you actually do New Config?

 

Go to Tools - New Config - Retain all - Apply

 

Then change the disk assignments as needed, making sure you don't assign any data disk to any parity slot.

 

Then Start the array to rebuild parity.

Quote

 

Did you actually do New Config?

Go to Tools - New Config - Retain all - Apply

 

 

Yes - I did this.  Made sure I selected "Retain All" and made doubly sure I pressed Apply and then Done.

Should I be selecting "None" in New Config instead of "Retain all" ?

2 minutes ago, Geoff Bland said:

Made sure I selected "Retain All" and made doubly sure I pressed Apply and then Done.

That is correct.   If correctly done then when you return to the Main tab then all drives should be marked with a blue icon, and you should be able to make changes as required and then start the array.

New config was not correctly done, or all disks icons would turn blue, try again.

Makes me wonder if flash is corrupt/readonly.

 

Attach Diagnostics to your NEXT post in this thread.

Quote

New config was not correctly done, or all disks icons would turn blue, try again.

 

You were correct. I triple checked this time and now all the disks had blue icons and I was able to correctly configure the array.

Started and rebuilding parity now.