Resuming move after SSH session aborted while moving Synology Drive Server pkg w/ 600GB @synologydrive folder

[TorbenSchreiter]

Hi Dave,

thanks a lot for your community efforts particularly wrt Synology_app_mover & Synology_HDD_db! Have just donated.

Regardless of that: I am a bit late to the party to migrate to btrfs, which is the reason why over the years, the @synologydrive folder has grown dramatically to >600GB in size. Unfortunately, while moving the package from /volume1 to /volume2 the SSH session got reset during the last(?) step - while moving that folder. The move was only partially completed.

Both the DSM Package mgr and Synology_app_mover already locate the package at the new location. However there are now @synologydrive folders on both volumes.

I have tried to naively move the remainder portion like this, but it fails:

user123@GLHV3:/volume2$ cd @synologydrive
-sh: cd: @synologydrive: Permission denied
user123@GLHV3:/volume2$ sudo mv "/volume1/@synologydrive" "/volume2/"
Password:
mv: inter-device move failed: '/volume1/@synologydrive' to '/volume2/@synologydrive'; unable to remove target: Directory not empty

There is no backup of the pkg (due to the sheer size of the package).

Could you maybe help out with the best way how to move the remainder. Also not sure whether there are potentially other parts additionally to @synologydrive that also need to be manually moved now.

Thanks!

[007revad]

I saw the donation. Thank you.

In Package Center, stop the Synology Drive Server package.

After moving @synologydrive it would move @SynologyDriveShareSync then edit 3 files and a symlink.

Give me an hour and I'll work out the commands needed to fix @synologydrive and do the remaining steps.

[007revad]

Stop Synology Drive Server then

sudo rm /var/packages/SynologyDrive/etc/repo
sudo ln -s "/volume2/@synologydrive/@sync" /var/packages/SynologyDrive/etc/repo
sudo rsync -aH --progress "/volume1/@synologydrive.old/" "/volume2/@synologydrive"

Then check with

readlink /var/packages/SynologyDrive/etc/repo
sudo du -sh /volume2/@synologydrive

[TorbenSchreiter]

Ok. it's 10pm here, now and it's going to take a while until copying will be done. Will leave Putty open and hope it'll finish alone. Will report back in the am. Thanks!

[TorbenSchreiter]

Good morning. At first it looked ok after the move was complete:

user123@GLHV3:/volume2$ readlink /var/packages/SynologyDrive/etc/repo
/volume2/@synologydrive/@sync
user123@GLHV3:/volume2$ sudo du -sh /volume2/@synologydrive
Password:
619G    /volume2/@synologydrive

I then started up the package, which showed up w/ default settings again. And afterwards 🫣:

user123@GLHV3:/volume1$ readlink /var/packages/SynologyDrive/etc/repo
/volume1/@synologydrive/@sync

[007revad]

I just noticed on my Synology Drive is on volume 1, but "Synology Drive Admin > Settings" shows the database volume is volume 3.

Checking via SSH I see:

1. /var/packages/SynologyDrive/etc/db-path.conf contains db-vol=/volume3 # The script does not edit this file
2. The "/var/packages/SynologyDrive/etc/repo" symlink points to /volume3/@synologydrive/@sync

Maybe the script should not edit the repo symlink and also not move the "@synologydrive" folder, as "Synology Drive Admin > Settings" can move the database.

Try this:

1. Stop Synology Drive Server.
2. Then run these commands:

sudo rm /var/packages/SynologyDrive/etc/repo
sudo ln -s "/volume2/@synologydrive/@sync" /var/packages/SynologyDrive/etc/repo
sudo synosetkeyvalue /var/packages/SynologyDrive/etc/db-path.conf db-vol /volume2

3. Start Synology Drive Server.
4. Check the changes have not reverted back to /volume1

readlink /var/packages/SynologyDrive/etc/repo
synogetkeyvalue /var/packages/SynologyDrive/etc/db-path.conf db-vol

[TorbenSchreiter]

In step 2 I would replace /volume 3 with /volume2 (last line), correct?

[007revad]

Yes.

sudo synosetkeyvalue /var/packages/SynologyDrive/etc/db-path.conf db-vol /volume2

[TorbenSchreiter]

Yes, that might have done the trick! Settings are back and changes have not yet reverted back. Also the UI dropdown in the Drive Admin Console now points to "Volume 2" (without me changing it):

user123@GLHV3:/volume1$ readlink /var/packages/SynologyDrive/etc/repo
/volume2/@synologydrive/@sync
user123@GLHV3:/volume1$ synogetkeyvalue /var/packages/SynologyDrive/etc/db-path.conf db-vol
/volume2

My desktop Drive client seems to have connected and has successfully synced new files that I had created locally in the meantime while the Synology Drive Server was down over the course of the last 2 days. Mobile clients connecting flawlessly as well.

Looks all good to me for now. What issues were you potentially expecting above, when you said migrating the package from ext4 to btrfs might cause problems? Something specific to watch out for from now?

Many thanks again! That was a great help!

[007revad]

Awesome!

I'm going to change the script so it does not move @synologydrive or edit the symlink. That way people can use Synology Drive Admin to move the database.