@appstore Disk Migration

[Vodka2014]

Hi,

 

I would like to know how I can move my App Disk from 120GB to 500GB Disk.

 

So what I mean is that i have the @appstore on the 120GB with all packages installed. Now i want to move this to my new 500GB Disk.

 

What is the best method for this please.

 

Thanks

Edited February 8, 2021 by Vodka2014

[billat29]

I did this

https://costigator.com/uncategorised/how-to-move-applications-from-one-volume-to-another-on-synology/

which kind of worked.

[Vodka2014]

Thanks @billat29

 

I will give this a try

[Vodka2014]

This did not work at all for me i got disk full even thou there was tons of space. So i am not sure where to go from here. 

[billat29]

"disk full" when you tried the mv command?

[Vodka2014]

Yes that is what i did. I am moving from an 120GB to 500GB so i am not sure what is going on.

[billat29]

looking at the link. Should be

sudo mv /volume1/@appstore/* /volume2/@appstore/

unless you were root already

[Vodka2014]

I was root. Also done i shutdown my NAS change the Disk and then it should all work correct ? 

 

Any other advice 

 

Thanks

[billat29]

I would like to know at what stage you get "disk full". If it is during the file move, then I am thinking about a permissions problem somewhere.

What I did was the move, changed the symlinks and restarted DSM, I confirmed that the applications seemed to be working before I removed my original disk.

But there was more work to do before removing the disk. I remember that I had to move the user home service from volume1 to volume2

 

Edited February 15, 2021 by billat29
reread earlier post

[Vodka2014]

Thanks. So it might be better if i do an new install on everything and migrate over the files and DB's i need etc....

 

Do you think The Kingston SSD Clone Software will work for this ?

Edited February 15, 2021 by Vodka2014

[billat29]

 

Wait. That's a different question. Is your question really "I want to replace my current disk with a new one and keep all my data and applications settings"?

[Vodka2014]

Yes i want to move everything from the 120GB Disk to the 500GB Disk. This has my @appstore on it. Once done the new 500GB Disk will be there an i will remove the 120GB Disk.

 

This is what i am trying to get done. 

[Vodka2014]

Ok so i found a tool that will allow me to Clone the Disk to Disk but now how do i Extend the Volume of the Unallocated Space ? I do not see it at all in the Disk manager. 

 

Any Advice. 

 

Thanks in advanced 

[flyride]

This seems like the hard way to do it, but you'll need to adapt the procedure outlined here after a clone operation:

https://xpenology.com/forum/topic/14091-esxi-unable-to-expand-syno-volume-even-after-disk-space-increased/

 

[Vodka2014]

Thanks @flyride and the easy way to do this and keep all my data ?

 

I am really having a hard time to get this all to work. 

[billat29]

I found this,

I'm going to try it in a virtual machine BRB

Edited February 15, 2021 by billat29
flyride's on the case

[flyride]

Just now, Vodka2014 said:

Thanks @flyride and the easy way to do this and keep all my data ?

 

I am really having a hard time to get this all to work. 

 

Yeah, this stuff can get complicated and there are a lot of tricks.  The @appstore folder is not a shared folder, but it is part of the data array.  This allows us to use array manipulation to do what we need and not screw up your volume location or put your data at additional risk. Here is what I would try.  You need a spare disk larger than the new 500GB disk that you can use temporarily.

 

The assumption is that you have a RAID0 Basic volume now (/volume1) with your app store on it .  If you built a SHR with it, do not follow this guide immediately and post the results of a df and a cat /proc/mdstat and let's evaluate before you proceed.

1. Convert your RAID0 Basic volume with the 120GB disk into a RAID1, adding the new 500GB disk.  Do not make a SHR.  The result will be a 120GB RAID1
2. Shutdown and remove your 120GB disk. If it was the #1 disk slot on the controller, move the new 500GB disk into it.
3. Add your spare disk, boot and repair the RAID1 array with it (again do not make SHR). The array will be expanded automatically.
4. Once it's done, shutdown, remove the spare disk, reboot and you will have a "broken" RAID1 array (which is a RAID0)
5. Confirm which /dev/md device it is by running cat /proc/mdstat
6. Assuming it's /dev/md2 (substitute whatever you figure out from the mdstat command), issue the following command as root:
   mdadm --grow --raid-devices=1 --force /dev/md2

[flyride]

16 minutes ago, billat29 said:

I'm going to try it in a virtual machine BRB

Edited 1 minute ago by billat29
flyride's on the case

 

Never you mind, we need all the helpers we can get.  You found something basically identical to what I was brain-dumping just then

[Vodka2014]

Thanks both

 

I will go get this tested out and see if this works for me. I only have 1x 500GB so will need to find another SSD.

 

Keep you posted. 

[Vodka2014]

Hi @billat29 How did your testing come on since I need to order and new 500GB SSD.

[billat29]

@Vodka2014 I broke my virtual environment. That was while I was setting up to test this. I didn't get as far as trying it.

Then @flyride came in and they really, really know their stuff. So I edited my post and crossed my offer out.

I have watched flyride sort out the most difficult problems and would have every confidence that if anyone can sort you out, they can.

 

My concern now, having reread all this, is what state is your system in? I don't understand why you need to order another 500GB disk right now.

You started with a 120GB and tried to move @appstore onto the 500GB. That didn't work,

so where is @appstore now? Is it back on the 120GB? Does your system work without the 500GB or are you now spread over the two disks?

And looking at flyrides post are you RAID0 or SHR?

 

[Vodka2014]

So what i did was Clone the 120GB to the 500GB so that worked

 

I will need to do some testing on Sunday but from what i know you need 2x Disks to Expand a Volume this is why i need another 500GB then Remove it for RAID 0 again. 

 

[billat29]

The "one disk" strategy that I linked to appeared to work.

The method is slightly different for 6.2.3. I'll put some screenshots up shortly

 

[billat29]

I started with my virtual machine on 6.2.3 U3. It had one 8GB drive.

I then defined and added a 128GB virtual drive and rebooted the machine:

 

I have two unused drives as the first is the bootloader and I haven't applied the fix for hiding it when running in a VM.

I then went to Storage Manager>Storage Pool>Action and selected "change RAID type".

I selected RAID1 and dragged and dropped my new drive

 

Next it resynchronised.

Then I shut down and removed the old drive before restarting ..

[billat29]

When I restarted, the storage pool had crashed

 

 

I ignored that and connected by SSH and ran the magic command:

sudo mdadm --grow --raid-devices=1 --force /dev/md2

That immediately sorted the crashed storage pool and started an expansion

 

 

When that was done, I went to expand the volume as the link said but found it was already done

 

 

 

and that was it. It seemed to have worked. My packages were still there as was my (limited) data.

 

 

[Vodka2014]

Hi @billat29

 

Q, If my Storage Pool is 2 what will the command be for this please ? 

 

EDIT: So I found that it was MD3 so that worked to fix the Failed Array but the dam thing did not expand

Edited February 21, 2021 by Vodka2014