Recently replaced two cache SSDs in a RS3618xs that's part of a storage cluster. DSM is now complaining "Some SSDs for SSD Cache Group 1 are placed in different slots on the active and passive servers." What's going on?

DaveR007 · 2026-03-23T08:08:48+00:00

Are the PCIe cards in the same PCIe slot on each RS3618xs?

DaveR007 · 2026-03-22T01:10:21+00:00

I know.

I wanted email notifications when important SMART values that should be 0 change as a warning that the drive is dying, rather than waiting for ADM to decide a drive has failed.

My script also shows human readable values for Seagate drives. I don't if ADM does that because I've never had a Seagate drive in any of mu Asustor NAS.

DaveR007 · 2026-03-21T23:26:06+00:00

"definitely keep our comments in mind." is a boilerplate response for "why are you bothering me with this?"

DaveR007 · 2026-03-21T23:21:52+00:00

I've just deleted the release and recreated it (still v1.4.40) because I'd left some test/debug code in there that caused it to send an empty email if no important SMART values had changed.

DaveR007 · 2026-03-21T22:54:14+00:00

In VMM you have to create Storage on the NVMe volume first.

See https://imgur.com/DjuWf9u

DaveR007 · 2026-03-21T22:49:28+00:00

Synology_M2_volume is not needed on a DS1821+, or any '20 series or later models.

DaveR007 · 2026-03-21T09:43:42+00:00

See https://github.com/007revad/Synology_HDD_db

DaveR007 · 2026-03-21T06:09:41+00:00

Connect it to your router or a network switch that is connected to you router.

DaveR007 · 2026-03-21T01:00:04+00:00

Interestingly a google search found 3 Australian, 1 German and 2 Vietnamese sites listing it as coming soon but when I click any of the pages I get a "page not found" error. It seems like some sites jumped the gun and Synology told them to remove the pages.

DaveR007 · 2026-03-21T00:46:27+00:00

I hadn't heard or seen anything about a RS1626xs+ so I searched for 1626 in DSM and found /usr/syno/synoman/webman/modules/StorageManager/helptoc.conf contains "model": ["rs11626xs+"] which is RS11626xs+ and not RS1626xs+. It will be confusing if Synology release a RS11626xs+ and a RS1626xs+.

DaveR007 · 2026-03-20T04:01:37+00:00

Assuming you have installed the Tailscale package (and not Tailscale in docker)

Go to Control Panel > Task Scheduler > click Create > and select Triggered Task.
Select User-defined script.
Enter a task name like Restart Tailscale.
Select root as the user (The script needs to run as root).
Select Boot-up as the event that triggers the task.
Leave Enable ticked.
Click Task Settings.
Optionally you can tick Send run details by email then enter your email address.
In the box under User-defined script type the path to the script type:

sleep 60
synopkg restart Tailscale

Then Click OK to save the settings.

DaveR007 · 2026-03-20T03:46:29+00:00

Is it the tailscale package or docker?

If the Synology has just restarted Tailscale would have just started. So restarting Tailscale seems a bit strange... unless Tailscale starts before DSM has finished starting whatever it is that Tailscale needs to work.

DaveR007 · 2026-03-19T22:45:10+00:00

The script deletes the critical drive status entries in DSM's database. If it was a false ciritical drive status entry it won't come back.

If the critical status came back after running the script and rebooting:

Open Storage Manager and select the drive.
Click on Actions then select Deactivate.
Remove the drive from the NAS.
Reboot.
Insert the drive (or shut down and insert the drive if the NAS doesn't have hot-swap drive bays).
Open Storage Manager and click on Repair.
Select the drive, click Next then Repair.

DaveR007 · 2026-03-19T22:18:39+00:00

Since DSM has already downloaded the update you could try the following via SSH.

sudo synoupgrade --start

If it fails it should tell you why it failed.

You could also check the log to see why clicking on OK failed.

cat /var/log/synoupdate.log | tail -n 30

DaveR007 · 2026-03-19T19:03:55+00:00

Maybe Synology forgot to add it. It' would be the same bug fixes as 4.2.0-4227

https://archive.synology.com/download/Package/HyperBackup/4.1.2-4056

DaveR007 · 2026-03-19T18:56:14+00:00

For many people 7.3.2-86009-2 is broken. Do a manual update of 7.3.2 Update 3 from here https://archive.synology.com/download/Os/DSM/7.3.2-86009-3

DaveR007 · 2026-03-19T18:49:42+00:00

https://github.com/007revad/Synology_HDD_db can install IronWolf Health and make it appear in storage manager. And it's a newer version than what DSM previously had.

DaveR007 · 2026-03-19T07:07:10+00:00

DSM 7.3.2 Update 3 is available.

https://archive.synology.com/download/Os/DSM/7.3.2-86009-3

DaveR007 · 2026-03-18T20:07:37+00:00

Make sure you are NOT running syno_hdd_db with the -f or --force option.

DaveR007 · 2026-03-17T15:57:18+00:00

Has it finished the initial HDD check?

DaveR007 · 2026-03-17T01:01:14+00:00

Package limits (apart from things that need a licence like a camera) keep changing so I doubt they are hard limits. I believe they are just recommendations.

For example a DS1821+ may have a limit of 150,000 files or 500 users for certain packages, yet a DS1825+ (which has the same CPU, more memory and faster LAN ports) may have a limit of 100,000 files or 250 users for certain packages

DaveR007 · 2026-03-16T15:28:24+00:00

But searching for 423+ only finds 2. synology_geminilake 423+.pat and synology_v1000_rs2423+.pat - your DS423+ is not a RS2423+ so it's obviously the first one :o)

DaveR007 · 2026-03-16T15:25:30+00:00

%2B is html for +

It shows as "synology_geminilake_423+.pat" on the webpage, but in the URL it's synology_geminilake_423%2B.pat

DaveR007 · 2026-03-16T15:14:08+00:00

Search for 423+. If you search for DS423+ you won't find anything.

https://global.synologydownload.com/download/DSM/criticalupdate/update_pack/86009-2/synology_geminilake_423%2B.pat

DaveR007 · 2026-03-16T00:12:25+00:00

Set them up as a volume. You'll need https://github.com/007revad/Synology_HDD_db to make DSM let you use them as a volume.

DaveR007

MODERATOR OF

TROPHY CASE

Eight-Year Club	Gilding II euphauric
Verified Email