DSM 7.3 Neue Version 7.3.2 – 86009

[Benie]

Sieht so aus ! Das automatische Update der Laufwerksdatenbank ist heute Nachmittag gelaufen. Manuell habe ich die eh noch nie Upgedatet.

Edit: auf der DS 920+ Hatte ich bisher diesbezüglich noch nie Probleme.

 

[DaveR]

DSM used to check for Drive Database updates at midnight, or when a new drive was inserted. DSM 7.3 seems to also check at random times (which may only occur on '25+ models).

@Benie It sounds like you are using a version of syno_hdd_db from before 3.6.115

• Bug fix for DSM 7.3 not disabling compatible drive database auto update.

 

[Benie]

That's right, it was probably the version Synology_HDD_db-3.6.112 or Synology_HDD_db-3.6.113. I think I used the version from my DS920+without thinking, hence the slightly older version. I will use the newer version so that this doesn't happen to me again. Thanks for your tips on this.

 

[Benie]

Dear @DaveR

What happens with this Script File wich was also in the Zip Synology_HDD_db-3.6.118

"syno_hdd_shutdown.sh"

 

[DaveR]

It's for people whose 3rd party NVMe volume does not appear until after a 2nd reboot, after a DSM update.

synopkg in DSM 7.3 seems to have changed to automatically "repair" packages whose volume is missing by installing them on the first available volume (usually a HDD volume). But I noticed that packages that are stopped before the DSM update don't get started after boot-up so they don't get automatically repaired.

syno_hdd_shutdown.sh is for scheduling to run as root at shutdown to prevent DSM updates from "repairing" missing NVMe packages (by installing on them on the HDD volume). It's only needed if you have packages, or shared folders that packages depend on, installed on a 3rd party NVMe volume.

syno_hdd_shutdown.sh is not finished yet, but the first test version accidentally got copied from dev to main.

When finished syno_hdd_shutdown.sh will:

1. Check for packages installed on a 3rd party NVMe volume.
2. Check for other packages that depend on the packages installed on a 3rd party NVMe volume.
3. Check for packages that depend on a shared folder that is on a 3rd party NVMe volume.
4. Stop those packages and create a log of the packages it stopped and the NVMe volume number(s).

Then I need to update syno_hdd_db.sh so it:

1. Checks if there is a log of stopped packages.
2. Checks if the NVMe volumes those packages need is writable.
3. If 2 is okay then start the packages listed in the log and delete the log.

 

[Benie]

Thank you for your explanations.

I think I remember that you have already described this problem here in the forum and can now assign it.
Today, when I looked in my DS920+ which version I had saved there (always save the currently used zip file) I remember that I had also this problem with the app installations on a different volume on my DS920+ during the first or second update with 7.3.x. I think this was already fixed with a newer script version (....312, .....313)

The description of the shut_down_script sounds good. Here in Germany we say when we hear something like this: "You're already a clever fox" (Foxes are said to be particularly clever and sophisticated)