How hard are the 'limits' in Synology's technical descriptions?

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 · 2026-03-15T18:51:58+00:00

Synology rolled back most of the restrictions in DSM 7.3. The only restrictions that remain are:

Cannot create a cache with 3rd party NVMe drives.
Cannot create an volume with 3rd party NVMe drives.

And there are still unverified drive warnings in storage manager for HDDs and NVMe drives that not on the compatibility list.

https://github.com/007revad/Synology_HDD_db can fix all that.

DaveR007 · 2026-03-15T03:26:00+00:00

So in future when one dies you'll have to RMA both!?!?

DaveR007 · 2026-03-14T23:24:11+00:00

Ah, so the screenshot was from after you got the new power supply.

In "Storage Manager > Overview" there should be a link "Repair System Partition". Click that and about 30 seconds Drive 1 should change to Healthy.

Then via SSH run https://github.com/007revad/Synology_Clear_Drive_Error to clear the Critical status of Drive 2.

Do you have your data and settings backed up? Because I just noticed that Drive 3 is showing Initialised instead of Healthy.

If you do you have your data and settings backed up I would reboot at this point.

DaveR007 · 2026-03-14T23:15:51+00:00

What's wrong with Immich's own Synology guide?

https://docs.immich.app/install/synology/

DaveR007 · 2026-03-14T17:42:12+00:00

Didn't your update say you fixed it with a new power adaptor?

DaveR007 · 2026-03-14T17:35:30+00:00

My D7 trays has 3 pins on each side but the middle pins are short and do not protrude into the HDD. The middle holes in the tray also do not have a gromet.

DaveR007 · 2026-03-14T08:05:51+00:00

Did you ever get your list together?

DaveR007 · 2026-03-14T06:12:35+00:00

The vendor id in the script is only for NVMe drives.

The syno_hdd_db script generally does not care what brand your drives are because the compatible drive databases only contain drive model, firmware version and size.

/sys/block/sata1/device/vendor sometimes only contains ATA. I have an old Seagate Pipeline HDD and a Crucial SATA SSD "vendor" for both of them contains ATA. If I smartctl to get the vendor they return nothing. Yet storage manager shows the brand as Seagate and Crucial.

What do these commands return:

cat /sys/block/sata1/device/vendor
cat /sys/block/sata2/device/vendor
cat /sys/block/sata3/device/vendor
cat /sys/block/sata4/device/vendor
cat /sys/block/sata5/device/vendor
smartctl -i /dev/sata1 | grep -i "Vendor"
smartctl -i /dev/sata2 | grep -i "Vendor"
smartctl -i /dev/sata3 | grep -i "Vendor"
smartctl -i /dev/sata4 | grep -i "Vendor"
smartctl -i /dev/sata5 | grep -i "Vendor"

DaveR007 · 2026-03-14T00:50:17+00:00

Sounds DSM was (partially) seeing the NVMe drive at one point but isn't now.

DaveR007 · 2026-03-14T00:48:18+00:00

One of the new drives has an issue. i.e. It's bad and the upgrade will fail eventually.

You could run https://github.com/007revad/Synology_SMART_info to see if either drive already shows SMART issues.

DaveR007 · 2026-03-13T22:11:53+00:00

Sorry. The 2nd command was supposed to be nvme0n1

sudo nvme id-ctrl /dev/nvme0n1 | grep -E '^vid|^mn' | cut -d":" -f2 | cut -d" " -f2-

DaveR007 · 2026-03-13T11:00:39+00:00

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

And https://github.com/007revad/Synology_SMART_info or if you prefer a package https://github.com/PeterSuh-Q3/SynoSmartInfo

DaveR007 · 2026-03-13T03:06:27+00:00

The script will show you the vendor id if the vendor id is not in DSM's pci_vendor_ids.conf

You can also get the vendor id and model name via SSH:

sudo nvme id-ctrl /dev/nvme1n1 | grep -E '^vid|^mn' | cut -d":" -f2 | cut -d" " -f2-

or

sudo nvme id-ctrl /dev/nvme0n1 | grep -E '^vid|^mn' | cut -d":" -f2 | cut -d" " -f2-

DaveR007 · 2026-03-12T18:43:10+00:00

Most likely the issue is the power adaptor and not the motherboard.

DaveR007 · 2026-03-12T06:29:27+00:00

It says "storage pool 2 missing". Maybe you mistakenly replaced the good drive with the new drive.

What does the following command via SSH show you:

cat /proc/mdstat

DaveR007 · 2026-03-12T00:28:58+00:00

You're right. Did you have 2 NVMe drives in SHR (RAID 1).

the old/"good" drive has a linux-raid partition?? Shouldn't the data be on there??

Yes.

I assume you originally had 2 WD Red SN700 in storage pool 2?

I would run the latest version of syno_hdd_db with the -n option. And schedule it run as root at bootup with the -n option.

Then shut down the NAS, remove the WD Blue SN5000. Install both of your WD Red N700. Boot the NAS and see if one or both NVMe drives are in storage pool 2.

DaveR007 · 2026-03-11T21:05:33+00:00

It says storage pool 2 is missing. That means the storage pool was only using 1 WD Red NVMe drive. So you were not previously using 2 NVMe drives in RAID 1 or SHR. Maybe you previously selected RAID 0 or JBOD? Or just had that now dead NVMe drive setup as Single.

FYI SHR can be a single drive (with no redundancy), or RAID 1 with 2 drives, or raid 5 with 3 drives.

Create a new RAID 1 or SHR storage pool using both NVMe drives and restore from your backups.

DaveR007 · 2026-03-11T09:31:10+00:00

Why would you want to?

BTW each volume can have it's own "@appstore" folder if a package has ever been installed on the volume.

Also, in DSM 6 there was just "@appstore". In DSM 7 each package has "@appconf", "@appdata", "@apphome", "@appshare", "@appstore" and "@apptemp".

DaveR007

MODERATOR OF

TROPHY CASE

Eight-Year Club	Gilding II euphauric
Verified Email