[PR #90] [MERGED] Develop #925

New issue

Closed

opened 2026-03-12 17:41:38 +03:00 by kerem · 0 comments

kerem commented

2026-03-12 17:41:38 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/007revad/Synology_HDD_db/pull/90
Author: @007revad
Created: 6/20/2023
Status: ✅ Merged
Merged: 6/20/2023
Merged by: @007revad

Base: main ← Head: develop

📝 Commits (10+)

138fc73 Update CHANGES.txt
a33689a Update syno_hdd_db.sh
2b63ff2 Update CHANGES.txt
11bd2b0 Update CHANGES.txt
ddedd6e Update syno_hdd_db.sh
8d26e2b Update syno_hdd_db.sh
fdbcc53 Update CHANGES.txt
3938527 Update CHANGES.txt
1435664 Update syno_hdd_db.sh
836a150 Update CHANGES.txt

📊 Changes

2 files changed (+341 additions, -97 deletions)

View changed files

📝 CHANGES.txt (+21 -0)
📝 syno_hdd_db.sh (+320 -97)

📄 Description

v3.0.55

Now enables any installed Synology M.2 PCIe cards for models that don't officially support them.
- You can use a M2D20, M2D18, M2D17 or E10M20-T1 on any model with a PCIe slot (not Mini PCIe).
Now the script reloads itself after updating.
Added -i, --immutable option to enable immutable snapshots on models older than '20 series running DSM 7.2.
Added -w, --wdda option to disable WDDA (to prevent warnings when WD drives have been running more than 3 years).
Added "You may need to reboot" message when NVMe drives were detected.
Added --autoupdate=[age] option to auto update synology_hdd_db x days after new version released.
- Autoupdate logs update success or errors to DSM system log.
Changed help to show -r, --ram also sets max memory to the amount of installed memory.
Changed the "No M.2 cards found" to "No M.2 PCIe cards found" to make it clearer.
Changed to skip checking the amount of installed memory in DSM 6 (because it was never working in DSM 6).
Fixed HDD/SSD firmware versions always being 4 characters long (for DSM 7.2 and 6.2.4 Update 7).
Fixed detecting amount of installed memory (for DSM 7.2 which now reports GB instead of MB).
Fixed USB drives sometimes being detected as internal drives (for DSM 7.2).
Fixed error if /run/synostorage/disks/nvme0n1/m2_pool_support doesn't exist yet (for DSM 7.2).
Fixed drive db update still being disabled in /etc/synoinfo.conf after script run without -n or --noupdate option.
Fixed drive db update still being disabled in /etc/synoinfo.conf after script run with --restore option.
Fixed permissions on restored files being incorrect after script run with --restore option.
Fixed permissions on backup files.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/007revad/Synology_HDD_db/pull/90 **Author:** [@007revad](https://github.com/007revad) **Created:** 6/20/2023 **Status:** ✅ Merged **Merged:** 6/20/2023 **Merged by:** [@007revad](https://github.com/007revad) **Base:** `main` ← **Head:** `develop` --- ### 📝 Commits (10+) - [`138fc73`](https://github.com/007revad/Synology_HDD_db/commit/138fc73a434cab6c3bb76731981a9eb9f41f9be4) Update CHANGES.txt - [`a33689a`](https://github.com/007revad/Synology_HDD_db/commit/a33689af0539059f07d82944ad598f75555b0428) Update syno_hdd_db.sh - [`2b63ff2`](https://github.com/007revad/Synology_HDD_db/commit/2b63ff2eaacc071571816dc7a4a48e42c95f290f) Update CHANGES.txt - [`11bd2b0`](https://github.com/007revad/Synology_HDD_db/commit/11bd2b03f740a272095adb61e74848847d779b28) Update CHANGES.txt - [`ddedd6e`](https://github.com/007revad/Synology_HDD_db/commit/ddedd6e72ba9b75ec626c2cde265cddb6f3e771e) Update syno_hdd_db.sh - [`8d26e2b`](https://github.com/007revad/Synology_HDD_db/commit/8d26e2b2cf40fc04f120fe8c11452fe2ebb8a9a9) Update syno_hdd_db.sh - [`fdbcc53`](https://github.com/007revad/Synology_HDD_db/commit/fdbcc53b106aa87afdb2f5b5da50ec626662a840) Update CHANGES.txt - [`3938527`](https://github.com/007revad/Synology_HDD_db/commit/3938527dd0dcd5205615f9e717100dd3be577b9f) Update CHANGES.txt - [`1435664`](https://github.com/007revad/Synology_HDD_db/commit/14356645da06a88eb109cf8d0e49912c46377909) Update syno_hdd_db.sh - [`836a150`](https://github.com/007revad/Synology_HDD_db/commit/836a150c16c3b7912de5b92d35e9e70304ab4215) Update CHANGES.txt ### 📊 Changes **2 files changed** (+341 additions, -97 deletions) <details> <summary>View changed files</summary> 📝 `CHANGES.txt` (+21 -0) 📝 `syno_hdd_db.sh` (+320 -97) </details> ### 📄 Description v3.0.55 - Now enables any installed Synology M.2 PCIe cards for models that don't officially support them. - You can use a M2D20, M2D18, M2D17 or E10M20-T1 on any model with a PCIe slot (not Mini PCIe). - Now the script reloads itself after updating. - Added -i, --immutable option to enable immutable snapshots on models older than '20 series running DSM 7.2. - Added -w, --wdda option to disable WDDA (to prevent warnings when WD drives have been running more than 3 years). - Added "You may need to reboot" message when NVMe drives were detected. - Added --autoupdate=[age] option to auto update synology_hdd_db x days after new version released. - Autoupdate logs update success or errors to DSM system log. - Changed help to show -r, --ram also sets max memory to the amount of installed memory. - Changed the "No M.2 cards found" to "No M.2 PCIe cards found" to make it clearer. - Changed to skip checking the amount of installed memory in DSM 6 (because it was never working in DSM 6). - Fixed HDD/SSD firmware versions always being 4 characters long (for DSM 7.2 and 6.2.4 Update 7). - Fixed detecting amount of installed memory (for DSM 7.2 which now reports GB instead of MB). - Fixed USB drives sometimes being detected as internal drives (for DSM 7.2). - Fixed error if /run/synostorage/disks/nvme0n1/m2_pool_support doesn't exist yet (for DSM 7.2). - Fixed drive db update still being disabled in /etc/synoinfo.conf after script run without -n or --noupdate option. - Fixed drive db update still being disabled in /etc/synoinfo.conf after script run with --restore option. - Fixed permissions on restored files being incorrect after script run with --restore option. - Fixed permissions on backup files. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>