It all began with this topic i created. My USBkey has been compromised and my server won't boot anymore from it. I just could'nt backup anything that was on that stick since PC or MAC "DO" want to format the key (so no browsing through it).

So i did format the key and copy/paste a fresh install unRAID system on it. But before i plug it in my server and start the machine, i'm asking you guys how will I not lose assignements my data disks and parity disk ??

 

To make it harder, I just don't remember what disks were data or parity. I could drill a hole in my brain but i'm not 100% sure of what disk is what. So not to loose anything (i would die ), here is THE question :

 

How do you rebuild the new array with a previous unRAID array after a deadly crash of the USB stick (and not knowing who was the Parity and the data disks)?

 

Ahah (or not  )

If you accept the fact that yoy're going to rebuild parity (I would advise in doing this instead of a 'trust my parity/array' action), you only have to figure out which drive is the parity drive.

 

All data drives will have a reiserfs filesystem while the parity disk will not contain a filesystem (as every bit it the parity data of all data bits)

How do i see that "reiserfs filesystem" ? Sorry, total n00b inside for this stuff

Do I use the steps described here ? ==> Check Disk Filesystems

If yes, when do i check for the filesystem of every disk? When UnRAID is fully booted ? In maintenance mode ? Array stopped and disks not attributed ?

Well, back from the depth of the unknown.

I ran reiserfsck on all my disks as described in the wiki ==> I started the array in maintenance mode with a disk assignement for the memory of my cloudy brain and some deduction. Every disk check returns as "reiser file system not found".

I saw that i was right in assignement since i was able to browse the disks and their data, excepting the parity one for which when assignated to a data disk was refused to be browsed.

I close my eyes, crossed my fingers, put the cat out the room in case of explosion and hit "start the array" for good.

 

Nothing lost, excepting some years to live for me due to stress.

 

The server is purring and syncing parity.

 

Thanks all for the advices and support ;

 

I think that my way to recover a server is not to follow huh.

Well, back from the depth of the unknown.

I ran reiserfsck on all my disks as described in the wiki ==> I started the array in maintenance mode with a disk assignement for the memory of my cloudy brain and some deduction. Every disk check returns as "reiser file system not found".

I saw that i was right in assignement since i was able to browse the disks and their data, excepting the parity one for which when assignated to a data disk was refused to be browsed.

I close my eyes, crossed my fingers, put the cat out the room in case of explosion and hit "start the array" for good.

 

Nothing lost, excepting some years to live for me due to stress.

 

The server is purring and syncing parity.

 

Thanks all for the advices and support ;

 

I think that my way to recover a server is not to follow huh.

 

reiserfsck has to be run on the partition, e.g., /dev/sda1

 

 

The easiest solution is to assign all disks as data and then reassign the one that is shown as unformatted to parity. Then start the array.