Do I need to update the script?

[principalarchivist]

I created a volume on an M.2 drive on my Synology (which is now running DSM 7.2.2-72806 Update 4) using version 3.5.103 of this script almost a year ago, and have had absolutely no problems. It has survived several DSM updates nicely.

I have version 3.5.103 running from Task Manager every time my Synology boots, just in case there's been a DSM update since the last boot. It doesn't seem to hurt anything that most of the time it runs unnecessarily.

I see that there is now a V2 of the script, v2.1.31.

Is there any reason for me to have Task Manager run V2.1.31 at boot instead of 3.5.103? Would doing so erase the contents of the volume on the M.2 drive?

Thanks!

[007revad]

3.5.103 would be Syno_hdd_db (which is up to 3.6.111 https://github.com/007revad/Synology_HDD_db/releases).

Most people only need syno_hdd_db and do not need syno_m2_volume.

[principalarchivist]

Thanks - same question applies, though - is there any point in updating to 3.5.103 and, if I do so, will it reformat or otherwise delete what's on the M.2 drive now? Thanks!

[007revad]

Updating syno_hdd_db won't cause you to lose your NVMe volume.

[principalarchivist]

Excellent, thanks!On Aug 26, 2025, at 4:58 PM, Dave Russell ***@***.***> wrote: Updating syno_hdd_db won't cause you to lose your NVMe volume. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>