Help !

I had my array started in maintenance because I wanted to test if I can launch a VM with at least the SSD Cache installed.

Now after replugging everything back, I cannot add my disk's without having 2x4TB erazed..

Why can't I just add those disk's back to the array?

I also don't remember in which order they where assigned.

Edited November 21, 2025Nov 21 by W0nderW0lf

22 minutes ago, W0nderW0lf said:

Help !

I had my array started in maintenance because I wanted to test if I can launch a VM with at least the SSD Cache installed.

Now after replugging everything back, I cannot add my disk's without having 2x4TB erazed..

Why can't I just add those disk's back to the array?

I also don't remember in which order they where assigned.

Shutdown Unraid, invert failing disk SATA cables and boot.
And share your Diagnostic file please.

Edited November 21, 2025Nov 21 by gyto6

Didn't work. Disk's are being detected as normal but it won't start the array in the previous order. I have a flash backup but I dont know if I can just replace certain files on that stick with array info's like the super.dat

Can you share your diagnostic file please?

Here it is:

nasty-diagnostics-20251121-1224.zip

Not used to it, so I'll wait for another advice as I'ld simply "Tools -> New Config" to simply import the array again.

However, I don't see any damage.

Edited November 21, 2025Nov 21 by gyto6

I just checked a flash backup to find the disk order as it was before.

How do I use the "new config"? Do I need to unassign all disk's before I do that?

Since the disks are disabled, they will need to be rebuilt, or you need to do a new config, in this case a new config may be the better option, but I recommend testing to confirm both disks are mounting first. You can do that with UD (in read only mode is preferable), and note that if you don't know which disk is which, there's a 50/50 chance parity2 will no longer be valid after the new config.

If you are not sure how to proceed, please ask first.

I know the correct disk order now.

Both are mountable at least in the "Main" tab.

What is UD?

Could I just replace disk mount information from an older backup like super.dat + whatelse is necessary?

Should I unassign all drives from the array before I do run new config?

Edited November 21, 2025Nov 21 by W0nderW0lf
typo

Just now, W0nderW0lf said:

Both are mountable at least in the "Main" tab.

Not sure what you mean by this, mount means to have the filesystem mounted, with the data accessible.

UD is the Unassigned Devices plugin; with that installed, you should be able to confirm both disks are mounting. They must be unassigned from the array first.

They are both unassigned from the array and I could mount them via UD, but I cannot see an "read only " mode.

edit: found the read only setting.

Do I need to unassign all drives from the array before I trigger "new config"?

Edited November 21, 2025Nov 21 by W0nderW0lf

22 minutes ago, W0nderW0lf said:

Do I need to unassign all drives from the array before I trigger "new config"?

Nope, you can keep all assignments, then just reassign the two missing disks in the correct order, assuming they mounted correctly with UD (and make sure to unmount them), then check "parity is already valid" before array start, if all looks good, run a parity check.

I resolved it myself in the following way:
!This requires you to have an backup of your flash drive without having changed your disk's in any way!

!! This is not recommended if you have experienced a faulty Disk !!

(In my case I unassigned all disk's from the array, but this step is maybe not necessary)

1. Shut down your server

2. unplug your USB drive, and mount it somewhere where u have a backup available

3. backup your current USB drive

4. after that replace your config/super.dat on the USB drive with the one from your flash backup

5. replug into your server and boot.

Everything should now be as it was before.

Edit:

BTW I wanted to thank you guys for your fast reply and help

Edited November 21, 2025Nov 21 by W0nderW0lf