13 minutes ago, flambot said:

I'm on the other end. Almost time to go to bed.

Yeah I know :-)

Good night to you and greetings to all the sheep...

If you still want to restore the assignments, copy super.dat and the pools folder (if it exists) from the old config folder.

SUCCESS! 😃

Took my time this morning and copied individual config files across to the working USB and it booted.

I had changed the auto start to no in the cfg before hand, so it the array was stopped.

Everything looked correct - drives all in the correct order, so I started the array.

The started array has been running for 1hour 20mins.

Last Parity Check was Mon 9 Oct 2023 (741 days ago) 😮

Perhaps the server died earlier than I thought??? 🤔

So...should I run a new parity check?

Wanted to let the HDD's run for a bit before stress testing them.

Next up, installing some plugins I think.

Many thanks for the input.
I found this extremely vexing.
There are still many tasks to achieve - one of them updating the filesystem to XFS.

EDIT:

Wanted to ask about this in the indent.cfg file

I saw a dropdown when I set the USB up from scratch again for slots??, but since I've copied all my old files across, I have not seen it. Perhaps it is only available when the array is offline?

This function is to do with? HDD's available in system?
I only have 1x parity 7xdata, with 2x spare bays (10 HDD's total) (but 12x SATA ports) -> so should I change this to 10?

In the dashboard there is a SHARES panel that shows a heap of disks down to Disk22. I think this relates to the above setting.

Also also have this -> dynamix.apcupsd in the plugins folder. Not sure of it is being used or not? Doesn't show in the plugins tab. Can't find it in CApps either.
I do have info showing in the Dashboard about my UPS, but is it coming from this plugin, or is the UPS stuff now handled directly by Unraid?

Edited October 18, 2025Oct 18 by flambot

as usual: don't panic :-)

the 24 disk slots is only telling the gui how many slots it should slow that could possible be populated with (new) disks.

Does not matter at all (unless it forces you to scroll too much), limiting it won't help.

(Luckily my Box just has been restored and I am "back in business", took almost 48hrs...)

5 hours ago, flambot said:

So...should I run a new parity check?

yeah some day. but now it only will cost you more time.

complicated things ahead: changing the file systems...

This will take you days or weeks and it would be wise now to have a spare disk that you can use to transfer your data... There are manuals for this, click on "help" and read carefully.

If you do not have a free disk, you might be forced to kill you parity, use it for swap and after all disks are converted, you can assign the last remaining old one as parity.

Or, maybe more future oriented: assuming the oldness of your box, the disks will not be very big (compared to today's ones) too. So it maybe debatable, to buy 3 large ones, use 2 of them for data, and 1 for parity...

Finally getting rid of the 10 old ones, that suck up much more electrical power...

This is up to you.

1 minute ago, MAM59 said:

complicated things ahead: changing the file systems...

Yeah. I actually started this process several years ago before it died.

I already have a disk cleaned out ready to go.

You are correct -> a lot of my HDD's are old -> still a couple of 2TB ones in there.

I have planned to get some new ones.
Looking at 22Tb Seagate Ironwolf Pro. Unfortunately, they cost just a shade under $1000NZ, so going have to take my time getting them.
2x 22tb data drives is way more space than I have now (currently have 7x data drives for a total of about 30Tb)

Spent the day installing and updating plugins. I also been doing lots of notes to help me in the future.

I no longer use the server like I used to. Easier to turn it on, copy content to a local HDD attached to player, then turn it back of. Gone are the days of leaving it running 12hrs a day.

Really appreciate the help you have put in. Couldn't have done it without it. Many thanks 🙏

10 minutes ago, MAM59 said:

(Luckily my Box just has been restored and I am "back in business", took almost 48hrs...)

What happened to it?

1 minute ago, flambot said:

What happened to it?

no idea what happened, wanted to start the array, suddenly all drives were "unmountable, no file system" :-(

All files gone...

Must have been a very bad day for UNRAID.

(I wanted to add a new disk with ZFS to the array, this did not work very well (slow as a dog), so I have stopped the file move and wanted to restart... no go anymore :-( )

Learned lesson: never interrupt a copy/move how many weeks it wants to take...

You see, everybody makes mistakes and learns the hard way.

But I did not panic (as I always tell to others :-) ), I have a backup server with the exact amount and sizes of drives. Thats usually OFF (an old box sucking a lot of energy) but gets turned on every 12hrs, copys over the changes and then shuts itself off again. But even the fast copy back took 2 days now for 4 drives... You need a lot of patience (and yes: Alcohol is NOT the solution :-) )

Now everything is back, new drives added, parity is rebuilding (1d 1hr, 19mins estimated)... all fine

BTW until this here goes more and more off-topic: you should mark the article that helped you most to fix your problem "as the solution" of this thread so others can easily can click it and do not need to read all trys&errors in between...

Edited October 19, 2025Oct 19 by MAM59

Wow...sounds like an experience I would rather do without.
I'm personally getting past it myself.

Finding tech more and more complicated and the old brain struggles with trying to sort it out.

Not even sure I did the right thing rebuilding my server. In hindsight with what I know now (and all the dramas) I probably wouldn't attempt it again.

Would have been a lot cheaper to just take the HDD's out, mount then under a linux distro and copy them to backup drives.
Oh well...you live and learn. Just got called for dinner, so I'm off.
Thanks very muchly again 👍👍👍

Edited October 19, 2025Oct 19 by flambot