Hi all,

 

My situation is that I have almost on TB of data on 3 disks. 2 disks are data and one is parity. The three disks are all Western Digital and the same size. Only the serial numbers are different.

 

My server hardware bit the dust and now I have a replacement box where I can put the disks and bring the system online. Is some way that I can identify which disk has the parity assignment based on the disk.cfg file or one of the other config files? I don't want to trash my data when I'm putting things back together. Keep in mind, I can't boot the old system to get the data via the web interface.

 

Alternately, will my old .cfg files just "work" with the new hardware if I just move the disks to the new server, and boot off the old Unraid USB stick?

 

Many many many thanks!

Boot the new hardware with the current flash. If your using version 5 it should work automagically.

Gotcha. I am using version 4.7 so this brings two questions to mind.

 

1. Will it work automatically with that version?

 

2. If I upgrade to version 5, can I copy over the old config files to maintain the old configuration under the new version?

 

Thanks again!

Gotcha. I am using version 4.7 so this brings two questions to mind.

 

1. Will it work automatically with that version?

 

2. If I upgrade to version 5, can I copy over the old config files to maintain the old configuration under the new version?

 

Thanks again!

If you have the same flash drive, it may work.. If not, the old device assignments are shown and you can use the devices page to assign the correct drives to their respective slots in the array.

 

In version 4.7 the disk.cfg has a list of the PCI devices that the disks are plugged into, but not the disks themselves.

Your syslog should have a inventory of the disks in it, assuming you saved one.

 

Other than that, assign no parity disk, assign all your disks as data disks.  One will appear to be unformatted.  It is the parity disk. 

If more than one are unformatted, stop, DO NOT FORMAT ANY DISK.  Get guidance.

 

There are upgrade instructions in the release notes to upgrade from 4.7 to 5.0.  Follow them.  Again, do not format ANY disks, and do not add new disks or remove existing disks until the upgrade is complete.

 

 

 

 

Awesome!

 

Thanks so much for the guidance guys!

Just wanted to say "Thanks" again. I updated to the latest RC for version 5 and used my old disk.cfg file. When I assigned the disks as data I was able to identify the parity disk. I then cleared the raid config and assigned the data and parity disks as normal.

 

Everything is working great!

 

Thanks!