Hello,

Seeking some help, trying not to panic.

I recently decided to upgrade a lot of my disks, I had 8 (smallish) data disks and a parity.

I upgraded the parity to a 20TB drive and rebuilt, all went well.

I then proceeded to try and swap a data disk, and since unassigning the disk (3), i've lost another disk (7), I think the disk itself has mechnically stopped working.

Which leaves me in this situation, 2 failed disks, but the array is up & running (image), files accessible etc, however, if I stop it, I can't seem to replace the broken disks.

I've also attached the diagnostics file.

Thanks (hugely) in advance, for any guidance whatsoever. n.b. i still have the 2tb disk i unassigned but have the 14tb disk plugged into the system.

sap1ent-diagnostics-20260225-1854.zip

Attached smart report for broken drive

sap1ent-smart-20260225-1905.zip

All files can't be accessible since 2 drives are unmountable. You just haven't noticed the missing files yet.

I don't understand how you can have 2 disabled disk with single parity though.

See if you can get disk7 to pass extended self-test.

39 minutes ago, Sap1ent said:

still have the 2tb disk i unassigned

Keep that one safe. It may be needed to rebuild disk7

Go to Settings and disable both Docker and VM Manager.

And don't write anything to any disks until everything is working well again.

Marvell controllers have been NOT recommended for a long time.

While we're waiting, remove this plugin

statistics.sender.plg - 2017.09.22  (Unknown to Community Applications)

That one hasn't been used in a very long time. It had something to do with a very old version of preclear I think.

I'll just put this here for future reference:

thanks very much for the responses @trurl

Re: the raid controller - i'm a bit of a hardware noob, this server has been kicking around a while, so I used what I had to hand back in the day and have gradually increased the storage, funnily enough, once I'd upgraded the storage (now i'm the age where I have a litle cash kicking around) I was going to upgrade all of the hardware, i was just trying to do it in a logical way, which has backfired a little

2 hours ago, trurl said:

While we're waiting, remove this plugin

statistics.sender.plg - 2017.09.22  (Unknown to Community Applications)

That one hasn't been used in a very long time. It had something to do with a very old version of preclear I think.

done!

3 hours ago, trurl said:

So to Settings and disable both Docker and VM Manager.

And don't write anything to any disks until everything is working well again.

done & done

3 hours ago, trurl said:

All files can't be accessible since 2 drives are unmountable. You just haven't noticed the missing files yet.

I don't understand how you can have 2 disabled disk with single parity though.

See if you can get disk7 to pass extended self-test.

running the extended test now

12 hours ago, trurl said:

I don't understand how you can have 2 disabled disk with single parity though.

That's a bug; it was fixed some time ago, but the user is on a very old release.

Best bet here is doing a new config to force enable one of the disks and then try to rebuild the other one.

The extended smart test came back fine on disk 7!

57 minutes ago, JorgeB said:

That's a bug; it was fixed some time ago, but the user is on a very old release.

Best bet here is doing a new config to force enable one of the disks and then try to rebuild the other one.

My plan was also to update everything following the hardware upgrade

So, disk7 was the 2nd one to get disabled, it passed the SMART test, and you still have old disk3 intact, correct?

Yes that's correct @JorgeB - one point of note though, disk 3 was unassigned from the array before disk 7 failed (it was being emulated, ready to add the new 14TB drive).

Thank you for all your help.

Edited February 26Feb 26 by Sap1ent

OK, you can try to re-enable disk7to then rebuild disk3, but if the results are not good, you can always revert to the old disk and resync parity instead.

Try this first:

-Tools -> New Config -> Retain current configuration: All -> Apply

-Check all assignments and assign any missing disk(s) if needed, including the new disk3, replacement disk should be same size or larger than the old one

-IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked)

-Stop array

-Unassign disk3

-Start array (in normal mode now), and post new diagnostics

Thanks again @JorgeB

Just about to do so, but just wanted to double check Preserve current assignments and 'retain current configuration' mean the same thing?

Appreciate they are very close and wording may have changed in a later build, but i'm extremely risk averse at this stage!

21 minutes ago, Sap1ent said:

but just wanted to double check Preserve current assignments and 'retain current configuration' mean the same thing?

Yep

that seems to have gotten me a step further!



sap1ent-diagnostics-20260226-1140.zip

Emulated disk3 is mounting, and shows about 1.8TiB of data, which I guess is about right, if that's the case, you can rebuild to the new disk, just stop the array, reassign the new disk3, and start the array to begin the rebuild.

Thanks @JorgeB - this seems to be working now.

I've got to wait a day and a bit to know for sure, but it's started!

FYI, i think this process is where disk 7 fell over last time, so that might have been why it was in such a strange state.

I assume, immediately after this rebuild (and confirmation that everything is working), i should then replace disk 7? (I have another drive sat ready and waiting to go).

Since disk7 passed the SMART test it should be OK for now, and after the rebuild finishes, I recommend updating Unraid first before doing anything else. You could even have updated before rebuilding now, but I forgot to mention that.

Understood, thank you so much for your help @JorgeB - hugely appreciated.