Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to move MailPlus Server to another volume #20

Closed
meigetsu opened this issue Jan 31, 2024 · 6 comments
Closed

Failed to move MailPlus Server to another volume #20

meigetsu opened this issue Jan 31, 2024 · 6 comments

Comments

@meigetsu
Copy link

Hello @007revad,

First of all, I discovered your script a few days ago and I am so glad you did it !
Having an hard drive issue on my main volume 1 (with HDD), I wanted to migrate everything to my completely new SSD Volume (DSM refusing me to mix HDD and SSD which would have been a smoother transition...).
It's also completely crazy that Synology offers no simple way to migrate everything to another volume in purpose of removing the old volume...

Anyways, I used your script to move all my installed applications (around 20) without losing any data.
Unfortunately, I had issues with two migrations using the latest available version at the time : 2.0.6.

First of all, docker migration had issues removing some data in @docker/btrfs folder at the end of the migration. Not so much of an issue but there seems to be a attributes/flag problem on th efolders. I cannot remove them manually either.
Container manager seemed to behave correctly for most existing containers except when I started to remove/recreate some of them. Then it started to fail, refusing me to delete them fort strange reasons (btrfs driver issue ?). Maybe linked to the folders not removed properly ?
I also had an issue with a projetc/container created through WebStation and that was referencing the old volume1 and refusing to startup. Unfortunately, this reference to volume 1 was hidden somewhere and I couldn't find where (neither in compose.yml nor each containers configuration).
Finally it was not such an issue to me because I wanted to redo everything properly anyways so that's ok. But so you know that there is still some isuues there

But the biggest issue to me here is migrating MailPlus Server, I had quite a peek of adrenaline while migrating it ! 😄
Migration wen't well, without any issue in the script execution but. I already had moved the MailPlus shared folder to the new volume before running your script to migrate the sever (it may be important?).
Unfortunatly, when the MailPlusServer restarted, it seemd to hve restarted from a fresh installation. I couldn't connect anymore to my previously configured accounts. When oening the administration tool, it invited me to create my first account as if it was freshly installed.
At that moment, I juste praided that moving the app back to volume 1 would fix it and it was the case ! So everything is ok as for now. But I am still stuck with that last app on volume 1.

I am also deeply linked to the directory server for my accounts, and especially for MailPlus Server, maybe this has something to do with it ? It seems like if there was a folder/config missing when moving from one volume to another.

Hope you can manage to identify the problem, it would really help ! 😃

@007revad
Copy link
Owner

I'm actually looking at Container Manager right now. The next version of the script will include backup and restore modes and while testing the restore mode Container Manager I'm getting an error that /volume1/@appdata/ContainerManager' is not empty. I also can't delete the /volume1/@appdata/ContainerManager' folder via SSH, but I can delete it in WinSCP. I've had the same issue with removing some data in @docker/btrfs folder.

The files in /volume1/@appdata/ContainerManager' seem to not get moved when moving Container Manager so it appears there's some docker process still running when I stop the Container Manager package and this process has locked the files.

I'll have a look at Web Station.

I originally had the same "create your first account" issue after moving MailPlusServer but thought I'd solved it. Maybe there's something extra I need to do if directory server is installed.

@holocronology
Copy link

an error that /volume1/@appdata/ContainerManager' is not empty

Appears to be occuring during a move operation as well:
image

@007revad
Copy link
Owner

Answering @holocronology questions in #34 (comment)

@007revad
Copy link
Owner

@meigetsu

Sorry, I forgot about this issue. I've spent 7 hours today searching for the cause but I've finally found what was missing. I'll have a new version on GitHub shortly.

007revad added a commit that referenced this issue Mar 19, 2024
v3.0.41
- Bug fix for moving Hyper Backup. issue #35
- Bug fix for moving Synology MailPlus Server. issue #20
- Bug fix for backing up extra @Folders (@docker, @downloads etc.).
- Improved instructions for moving shared folders.
- To do: Fix moving Container Manaager. issue #34
@007revad
Copy link
Owner

Moving MailPlus Server is now working. https://github.com/007revad/Synology_app_mover/releases/tag/v3.0.41

@meigetsu
Copy link
Author

@meigetsu

Sorry, I forgot about this issue. I've spent 7 hours today searching for the cause but I've finally found what was missing. I'll have a new version on GitHub shortly.

No worries! Thank you for the patch, I'll give it a try as soon as possible !

@007revad 007revad closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants