New Server - Configuration, some Old HDDS sill working.

[ahab666]

Hello Experts,

 

Some time ago I lost both parity drives and 3 data drives during a severe weather event.”

 

Is there any chance to use the data from the “old” data drives in the new created server ?

All the RMA'ed disks were checked by pre-clear and seem to be okay.

For some reason, the now empty parity discs are not accepted in the old configuration, same as the new data drives. 

 

Any ideas please, I can try to create and send the diagnostic file

 

cheers ahab666

[JorgeB]

You can, but need to do a new config if assigning them to an existing array with parity, or they would be cleared, you can also mount the disks individually with the UD plugin or single device pools.

[ahab666]

Hi,

just to clarify - I create a new empty/blank config. 

Can I just add the existing drives (including the data on them) to the newly created array ?

 

 

cheers

[JorgeB]

Does the new server have an array with parity?

[ahab666]

 

I need to create a new and blank server, because I lost both parities and 3/10 data drives physically.

Then one of the exchanged RMA drives was DOA and the whole slow process of getting that excange restarted ...

 

The old array does not start because I get wrong drives at all 5 of them .....

 

If I use the unassigned drives tool, I am still able to access the data on them.

 

So my idea was to unassign them all, then create a new config with no preserving the array and/or pool slots.

Then start the new server, set a basic config (usernames a.s.o.) and add the new 5 (precleared drives)

 

after that, I'll try to add the old ones one by one .....

 

Any idea if and where I can find the old config data, like user share names and locations, installed plugins and docker apps ?

 

I am adding the latest diagnostic file - maybe you can look into it. 

 

When I am talking server I mean the same hardware - server is synonymous for new unraid installation ...

 

An yes i plan to use at least one parity drive in the new installation.

 

 

cheers

tower-diagnostics-20240628-1910.zip

[itimpi]

You do not want to go down the route you mention and add the ‘good’ drives later.   That is both time consuming and error prone.
 

You want to do a New Config and I would recommend you use the option to retain all current assignments - you can remove the ‘bad drives’ when you return to the Main tab.  You can optionally add any new drives at this time as well  and they do not need to have been precleared as you are going to have to rebuild parity. Then start the array to build new parity based on that new drive set.    Unraid will recognise drives that have previously been used by Unraid and will leave their data intact.

 

if you are using the same flash drive then all settings regarding shares, usernames, plugins, etc will still be there.

 

You will need to format any new data drives - just make sure that only the new drives are listed as you do not want to format one of the drives that should have data on them.

 

You may need to adjust any share settings if they have include/exclude settings for specific drives.

 

i am not saying your approach would not work - just that it seems to be far more effort than I think is required.

 

[ahab666]

Hello thx for the replay, 

 

Just to be on the save side :

 

1. I had to remove the “bad” drives physically mid of May to send them to the manufacturers, one of them was very quick, like after a week I have got those drives back.

   The other one was a bit problematic, one of the 3 swapped drives was DOA. The preclear process it is running right now.

 

2. By keeping all the assignments and remove the old ones before even creating the array might a bit problematic. Mostly because I am not sure if I used the same physical ports         during and after the thunderstorm that ruined the original ones.

 

3. User shares - to minimize the spin down/up cycles, I tried to separate the user shares to as few drives as possible and used the Unbalance tool excessively to accomplish that.

    My Docker image was placed on the cache drive, mostly because of loading speeds.

 

4. How can I make sure, that the formatting process will not be forced or “indefinitely suggested” on the “old”  drives that harbor the data from before.

 

cheers and thx 

Edited July 2 by ahab666
spelling