DSM, version: 7.2.2-72806

[EDub1492]

Answered in a previous thread

Thanks for the great work !!!

[007revad]

Yes.

[TorbenSchreiter]

After completion of the DSM update to v7.2.2 the system initially booted up without having triggered the script scheduled for bootup. Therefore /volume2 that has both all packages and the Synology Drive shared folders on them, were not there until I had manually run the script and rebooted the box a second time.

Afterwards, everything seems to work, not however Synology Drive. It has reset itself to /volume1 with virgin settings. Would it be safe to change in the UI the location as per the below or would this overwrite my Synology Drive DB already present - but not linked to - on /volume2? Or would I need to update symlinks via SSH?

EDIT: Actually, the above situation seems to have moved the entire package - not just the DB - back to /volume1 from /volume2, where it was previously installed. Same for some other pkgs that definitely have been on /volume2 before the DSM update such as Synology Photos or Advanced Media Extensions. Yet other pkgs however are still on /volume2 (e.g. Cloud Sync & Hyper Backup). Strange.

Thanks for any advice!

[007revad]

Changing the Location in Synology Drive Admin moves @synologydrive to the selected volume (overwriting any existing @synologydrive folder on that volume. I would do the following:

1. Rename /volume2/@synologydrive to /volume2/@synologydrive_bak
2. Change the Location in Synology Drive Admin to volume 2.
3. Stop Synology Drive Server.
4. Rename the new /volume2/@synologydrive to /volume2/@synologydrive_new
5. Rename /volume2/@synologydrive_bak to /volume2/@synologydrive
6. Start Synology Drive Server.

[TorbenSchreiter]

Thanks, confirming this worked for me. What I did:

1. Stop Synology Drive Server
2. sudo mv /volume2/@synologydrive /volume2/@synologydrive_bak
3. Move the pkg using the latest release Synology_app_mover
4. Start Synology Drive Server
5. Change the Location in Synology Drive Admin UI to /volume 2
6. Stop Synology Drive Server
7. sudo mv /volume2/@synologydrive /volume2/@synologydrive_new
8. sudo mv /volume2/@synologydrive_bak /volume2/@synologydrive
9. Start Synology Drive Server

[TorbenSchreiter]

@007revad Post v.7.2.2 DSM update, this is the list of packages across volumes before re-moving any of them (as per the above). All of them were on /volume2 prior to the DSM update.

Is it safe to move them again naively using Synology_app_mover or would this overwrite any pkg settings/DBs that might be on /volume2 already?

[007revad]

Did the first 6 packages need repairing after the DSM update to 7.2.2?

[TorbenSchreiter]

Could you maybe add a Log Center entry

You can check the output of the last run of a scheduled user defined script in "Control Panel > Task Scheduler > select the task > Action > View Result > view details". Or set task scheduler to email you results each time it's run (which is what I have set).

I had set up the emails, but had a faulty email server config, which is now fixed. Therefore nothing for the DSM update occasion, unfortunately.

Still think a log entry would make sense simply to see it at the right spot in the sequence of events in the log, but of course not a must.

[007revad]

It would be handy to see the sequence of events. There would need to be a number of log entries. The downside is if someone's needs Synology Support's help the logs would show evidence they may not want support to see.

It's 10pm here. I'll get back to you tomorrow with steps to move Photos.

[007revad]

What does this command return?

sudo readlink /var/services/photo

If you've moved the shared space folder to volume 2 try this:

1. Go to Synology Photos > Settings > Shared Space.
2. Disable the Shared Space.
3. Then go back in and Enable Shared Space.

[TorbenSchreiter]

What does this command return?

sudo readlink /var/services/photo

user123@GLHV3:~$ sudo readlink /var/services/photo
Password:
/volume1/photo

If you've moved the shared space folder to volume 2 try this:

1. Go to Synology Photos > Settings > Shared Space.
2. Disable the Shared Space.
3. Then go back in and Enable Shared Space.

I have not yet moved the pkg to /volume2 yet, but /photo is on /volume1 (pkg should go to /volume2 though). Please confirm whether I should move the pkg first to /volume2 before playing around w/ the Shared Space setting? This won't delete any contents of /photo, right?

[TorbenSchreiter]

Have moved the Synology Photo pkg to /volume2 now. Magically it now found the photos again. All good. Thanks.