[GH-ISSUE #127] Worm / Immutable snapshot not fully enabled #557

New issue

Closed

opened 2026-03-11 11:56:43 +03:00 by kerem · 1 comment

kerem commented

2026-03-11 11:56:43 +03:00

Owner

Originally created by @HOAP81 on GitHub (Aug 2, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/127

I tried enabling Immutable snapshots with your script but it left the function broken.

RS1219+ runing DSM 7.2 64570u2

After running the script the WORM and immutable snapshot functions appear in the GUI.
I can also set the system as a replication target with immutable snapshot enabled.

But
I cannot create a WORM-share on the system. It gives the error "The operation failed. Please sign in to DSM again and retry" on the confirm settings page (enterprise mode. I have not tried compliance mode).
Marking an existing snapshot as immutable is possible (or creating one using the system as a replication target) but the expiry timer is not counting down. So it appears my snapshot is immutable for ever.

Also setting the support_worm value back to "no" doesn't do anything. But I guess that would be by design.

Originally created by @HOAP81 on GitHub (Aug 2, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/127 I tried enabling Immutable snapshots with your script but it left the function broken. RS1219+ runing DSM 7.2 64570u2 After running the script the WORM and immutable snapshot functions appear in the GUI. I can also set the system as a replication target with immutable snapshot enabled. But I cannot create a WORM-share on the system. It gives the error "The operation failed. Please sign in to DSM again and retry" on the confirm settings page (enterprise mode. I have not tried compliance mode). Marking an existing snapshot as immutable is possible (or creating one using the system as a replication target) but the expiry timer is not counting down. So it appears my snapshot is immutable for ever. Also setting the support_worm value back to "no" doesn't do anything. But I guess that would be by design.

kerem closed this issue

2026-03-11 11:56:48 +03:00

kerem commented

2026-03-11 11:56:54 +03:00

Author

Owner

@007revad commented on GitHub (Aug 2, 2023):

Don't try compliance mode or you'll have to wait 3.5 years to be able to edit or delete the files (or connect the drives a computer and format them).

Thanks for confirming that I need to do more to fully enable Worm on models older than '20 series.

When I added the option to enable Worm I made the following note to myself:

Synology says Immutable Snapshots are only available on '20 series and newer models. But we can enable them on other models that are using DSM 7.2 by running the following command:

sudo synosetkeyvalue /etc.defaults/synoinfo.conf support_worm yes

Will that work on all models using DSM 7.2... I don't know.

@007revad commented on GitHub (Aug 2, 2023): Don't try compliance mode or you'll have to wait 3.5 years to be able to edit or delete the files (or connect the drives a computer and format them). Thanks for confirming that I need to do more to fully enable Worm on models older than '20 series. When I added the option to enable Worm I made the following note to myself: > Synology says Immutable Snapshots are only available on '20 series and newer models. But we can enable them on other models that are using DSM 7.2 by running the following command: > > `sudo synosetkeyvalue /etc.defaults/synoinfo.conf support_worm yes` > > Will that work on all models using DSM 7.2... **I don't know**.

kerem referenced this issue

2026-03-11 13:14:48 +03:00

[GH-ISSUE #557] NVMe cache and crashed volume #703