How to move current configuration volume to new Raid set

[Digitair]

Hi, I need some advice for the following upgrade I'm planning.

 

I've got a HP N54L with synology working perfectly. 2x 2TB disks in Raid 1 and one 250GB disk where I installed the packages/configuration on. Since the 2TB disks are almost full, I want to add 2x 4TB disks, also RAID 1, but want the volume of the 250GB disk as a volume on the new Raid set. This 250 GB will not be used in the N54L anymore then.

I'm not sure what the best way is to achieve this. I tried to copy the partition with partitioning software to one of the new disks but that didn't work.

 

My new plan is to boot the N54L with all disks de-attached except for 1 of the new 4TB disk and then start a new installation. After this I'll restore the configuration from the backup/restore package from synology itself. Then add the 2nd disk and create a Raid 1 set. The configuration should now be available on both of the disks.

As a last step I'll add the 2 2TB disks and add this as another Raid 1 set. The data on it will not be touched this way?

 

Should this work the way I think of?

When I'm booting the Synology with only one of the new disks, it tels me that an installation has been found and that I can migrate or install a new configuration. What should I choose then?

 

Thanks!

[Digitair]

Not much replies , this is what I did. In case someone has a similar question.

 

The new configuration is slighty different but it's far more easy to do it this way. There is no need to backup and restore data to volumes manually.

 

At first I wanted to create 2 new volumes on the 4TB disks (RAID 1). 1 for the packages (called it config in my previous post) and 1 large volume to store data.

Now I have 1 large volume on the 2 discs without having to backup/restoring everything.

 

Initial setup:

Disc 1 (200GB) - Packages installed and some shares with small size data

Disc 3 (3TB) and Disc 4 (3TB) - RAID 1 - One large volume with data

 

I placed Disc 2 (4TB) and created a SHR raid disc with Disc 1. Once the data was copied, I removed Disc 1 (after shutdown). The 4 TB disc holds the data and only has 200 GB of space to be used, but this will be solved. 

Replaced Disc 1 with a new, empy 4 TB one and booted. Then repaired the SHR volume with Disc 1. Now a large 4 TB volume is available with all packages installed.

 

New setup:

Disc 1 (4 TB) and Disc 2 (4 TB) - SHR raid - One large volume

Disc 3 (3TB) and Disc 4 (3TB) - RAID 1 - One large volume

Edited August 5, 2017 by Digitair
addional info added

[IG-88]

16 hours ago, Digitair said:

Not much replies , this is what I did. In case someone has a similar question.

 

The new configuration is slighty different but it's far more easy to do it this way. There is no need to backup and restore data to volumes manually.

 

At first I wanted to create 2 new volumes on the 4TB disks (RAID 1). 1 for the packages (called it config in my previous post) and 1 large volume to store data.

Now I have 1 large volume on the 2 discs without having to backup/restoring everything.

 

Initial setup:

Disc 1 (200GB) - Packages installed and some shares with small size data

Disc 3 (3TB) and Disc 4 (3TB) - RAID 1 - One large volume with data

 

I placed Disc 2 (4TB) and created a SHR raid disc with Disc 1. Once the data was copied, I removed Disc 1 (after shutdown). The 4 TB disc holds the data and only has 200 GB of space to be used, but this will be solved. 

Replaced Disc 1 with a new, empy 4 TB one and booted. Then repaired the SHR volume with Disc 1. Now a large 4 TB volume is available with all packages installed.

 

New setup:

Disc 1 (4 TB) and Disc 2 (4 TB) - SHR raid - One large volume

Disc 3 (3TB) and Disc 4 (3TB) - RAID 1 - One large volume

 

with that kind if disk configuration you loose some space

synology  dsm can do more with SHR

a shr raid over all disk would create a 4x3TB raid5 and a 2x1TB raid1 volume on the "unused" 1TB parts of the 4TB disks and fusing the 9TB and 1TB usuable space as one volume you can use (dsm is unsing mdadm and LVM for this, but that what happens in background, you just see a SHR1 config with 10TB, the 1 behind the shr means 1 disk redundancy)

so 7TB (raid1 + raid1)  now against 10TB (shr1) when maxed out

 

the problem is that you already created the shr volume on 2x4TB disks and that means 4TB raid1 and i dont think dsm can/will shrink this back to 3TB for creating a 4x3TB raid5 volume, but i'm not certain about it, never tryed it that way, but usualy shrinking file system, lvm and mdadm raid one ater onother is lots of work and there a lots of thing that can go wrong in the process, maybe its not implemented for shr

if you can completly offload your date (called backup) the you can set back all, create the shr1 10tb volume in one step with all disks and restore from backup