Experiences updating from DSM 7.2 (DSM 7.2-64570 Update 4) to DSM 7.3

[ductng]

I was just wondering, if anyone experienced any problems when updating from DSM 7.2 to DSM 7.3.

[007revad]

Not personally but I've seen plenty of comments. You do need to run Synology_HDD_db after a major DSM update. Most people schedule it to run as root at boot.

But usually even with Synology_HDD_db scheduled to run at boot:

1. After a major DSM update the NVMe volume is missing until you reboot again.
2. Because of point 1 any packages installed on the NVMe volume may have been "repaired" during the DSM update.
3. Because of point 2 those packages are referencing their data, settings or databases on the HDD volume.

To fix point 3 (after running Synology_HDD_db and rebooting to get your NVMe volume back) you need to:

1. Uninstall the affected packages (but do not tick the option to delete their data).
2. Reinstall those packages on the NVMe volume.

Some people found they needed to recreate their docker containers from backups.