[GH-ISSUE #301] Need compatibility with Storage Cluster #608

New issue

Closed

opened 2026-03-11 12:32:59 +03:00 by kerem · 1 comment

kerem commented

2026-03-11 12:32:59 +03:00

Owner

Originally created by @tmunsch on GitHub (May 28, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/301

Originally assigned to: @007revad on GitHub.

I've ran your script on a single NAS and it works beautifully. However when I run it on a High Availability Cluster it only seems to affect the Active Server. I could just make the passive server active and run the script again but it's a production environment. Any thoughts on this? I'm happy to test things after hours etc and thank you so much for writing this you're amazing!

Originally created by @tmunsch on GitHub (May 28, 2024). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/301 Originally assigned to: @007revad on GitHub. I've ran your script on a single NAS and it works beautifully. However when I run it on a High Availability Cluster it only seems to affect the Active Server. I could just make the passive server active and run the script again but it's a production environment. Any thoughts on this? I'm happy to test things after hours etc and thank you so much for writing this you're amazing! ![Synology HA error](https://github.com/007revad/Synology_HDD_db/assets/27962004/322b710f-4a83-4628-ae0b-e83dda45ec99)

kerem closed this issue

2026-03-11 12:33:04 +03:00

kerem commented

2026-03-11 12:33:10 +03:00

Author

Owner

@007revad commented on GitHub (May 28, 2024):

If I understand this Synology page correctly there's no network access to the passive server (until it becomes the active server).

It's a pity you can't temporarily connect another cable to the passive server to SSH in and run the script.

I think the safest option would be to wait until after hours and make the passive server active and run the script again.

Make sure you run the script with the -n option to prevent DSM updating the compatible drive database.

I would normally suggest scheduling the script to run at boot in case DSM updates itself... but I suspect in a production environment you'd have DSM set to not auto update.

@007revad commented on GitHub (May 28, 2024): If I understand [this Synology page](https://kb.synology.com/en-global/WP/Synology_High_Availability_Introduction/3) correctly there's no network access to the passive server (until it becomes the active server). It's a pity you can't temporarily connect another cable to the passive server to SSH in and run the script. I think the safest option would be to wait until after hours and make the passive server active and run the script again. Make sure you run the script with the `-n` option to prevent DSM updating the compatible drive database. I would normally suggest scheduling the script to run at boot in case DSM updates itself... but I suspect in a production environment you'd have DSM set to not auto update.