[PR #63] [MERGED] Develop #913

New issue

Closed

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

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/007revad/Synology_HDD_db/pull/63
Author: @007revad
Created: 4/23/2023
Status: ✅ Merged
Merged: 4/23/2023
Merged by: @007revad

Base: main ← Head: develop

📝 Commits (10+)

bdb682b Update syno_hdd_db.sh
6d35581 Update CHANGES.txt
99e513c Update syno_hdd_db.sh
57d877b Update CHANGES.txt
a57124c Update CHANGES.txt
0eaec15 Update syno_hdd_db.sh
9574120 Update CHANGES.txt
af55b3d Update syno_hdd_db.sh
bee39ea Update CHANGES.txt
19a9172 Update CHANGES.txt

📊 Changes

2 files changed (+190 additions, -104 deletions)

View changed files

📝 CHANGES.txt (+11 -0)
📝 syno_hdd_db.sh (+179 -104)

📄 Description

Fixed bug where expansion units ending in RP or II were not detected.
Added a --restore option to undo all changes made by the script.
Now looks for and edits both v7 and non-v7 db files to solve issue #11 for RS '21 models running DSM 6.2.4. This will also ensure the script still works if:
- Synology append different numbers to the db file names in DSM 8 etc.
- The detected NAS model name does not match the .db files' model name.
Now backs up the .db.new files (as well as the .db files).
Now shows max memory in GB instead of MB.
Now shows status of "Support disk compatibility" setting even if it wasn't changed.
Now shows status of "Support memory compatibility" setting even if it wasn't changed.

_{🔄 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/63 **Author:** [@007revad](https://github.com/007revad) **Created:** 4/23/2023 **Status:** ✅ Merged **Merged:** 4/23/2023 **Merged by:** [@007revad](https://github.com/007revad) **Base:** `main` ← **Head:** `develop` --- ### 📝 Commits (10+) - [`bdb682b`](https://github.com/007revad/Synology_HDD_db/commit/bdb682b4889b237ee72280f8db9d365d5e3ed7be) Update syno_hdd_db.sh - [`6d35581`](https://github.com/007revad/Synology_HDD_db/commit/6d35581453f32967c68de9feaaf1028826c4b1e1) Update CHANGES.txt - [`99e513c`](https://github.com/007revad/Synology_HDD_db/commit/99e513c621cf34502ce0c22996be994498a13df6) Update syno_hdd_db.sh - [`57d877b`](https://github.com/007revad/Synology_HDD_db/commit/57d877be8d2a4b7983e09d8d99f00d0f3fae8082) Update CHANGES.txt - [`a57124c`](https://github.com/007revad/Synology_HDD_db/commit/a57124c8a13a44ea15b6e85321b1fecd60d426da) Update CHANGES.txt - [`0eaec15`](https://github.com/007revad/Synology_HDD_db/commit/0eaec15c123df1e9edf015bcb7301d1c30ef61e2) Update syno_hdd_db.sh - [`9574120`](https://github.com/007revad/Synology_HDD_db/commit/9574120c2b23bd5466dd59011e09850c01e91af3) Update CHANGES.txt - [`af55b3d`](https://github.com/007revad/Synology_HDD_db/commit/af55b3dab3be2b53ec37fd6b81f013dbd1adb53e) Update syno_hdd_db.sh - [`bee39ea`](https://github.com/007revad/Synology_HDD_db/commit/bee39eaf264c5f375abbe67314938667a2d1ef6e) Update CHANGES.txt - [`19a9172`](https://github.com/007revad/Synology_HDD_db/commit/19a9172ce05a31a9f078620efb568b47f5f3c127) Update CHANGES.txt ### 📊 Changes **2 files changed** (+190 additions, -104 deletions) <details> <summary>View changed files</summary> 📝 `CHANGES.txt` (+11 -0) 📝 `syno_hdd_db.sh` (+179 -104) </details> ### 📄 Description - Fixed bug where expansion units ending in RP or II were not detected. - Added a --restore option to undo all changes made by the script. - Now looks for and edits both v7 and non-v7 db files to solve issue #11 for RS '21 models running DSM 6.2.4. This will also ensure the script still works if: - Synology append different numbers to the db file names in DSM 8 etc. - The detected NAS model name does not match the .db files' model name. - Now backs up the .db.new files (as well as the .db files). - Now shows max memory in GB instead of MB. - Now shows status of "Support disk compatibility" setting even if it wasn't changed. - Now shows status of "Support memory compatibility" setting even if it wasn't changed. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>