[PR #552] [MERGED] Develop #495

New issue

Closed

opened 2026-03-07 19:18:35 +03:00 by kerem · 0 comments

kerem commented

2026-03-07 19:18:35 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/007revad/Synology_HDD_db/pull/552
Author: @007revad
Created: 1/19/2026
Status: ✅ Merged
Merged: 1/19/2026
Merged by: @007revad

Base: main ← Head: develop

📝 Commits (7)

83f9948 Update syno_hdd_db.sh to v3.6.117
f051eda Update CHANGES.txt for v3.6.117
8e8ba93 Add v3.6.118 changes to CHANGES.txt
8ebe2fb Update script to v3.6.118
0f370e7 Merge pull request #551 from 007revad/main
f4052cd Update TRIM instructions for RAID configurations
e3bd37f Update CHANGES.txt for version 3.6.118

📊 Changes

3 files changed (+49 additions, -3 deletions)

View changed files

📝 CHANGES.txt (+5 -0)
📝 README.md (+2 -2)
📝 syno_hdd_db.sh (+42 -1)

📄 Description

v3.6.118

Changed to enable creating M.2 storage pool and volume in Storage Manager after making DSM check disk compatibility. Issue #441
Added SSD TRIM warning of possible data loss if non-Synology SSDs or NVMes are in RAID 5, 6 or SHR with more than 3 drives.
- See https://kb.synology.com/en-global/DSM/tutorial/Why_is_SSD_TRIM_available_only_for_SSDs_in_the_compatibility_list

_{🔄 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/552 **Author:** [@007revad](https://github.com/007revad) **Created:** 1/19/2026 **Status:** ✅ Merged **Merged:** 1/19/2026 **Merged by:** [@007revad](https://github.com/007revad) **Base:** `main` ← **Head:** `develop` --- ### 📝 Commits (7) - [`83f9948`](https://github.com/007revad/Synology_HDD_db/commit/83f9948f0836a19efc0808ca71dc30acce171914) Update syno_hdd_db.sh to v3.6.117 - [`f051eda`](https://github.com/007revad/Synology_HDD_db/commit/f051eda588672b785537bf87c5d6f011b2915bb5) Update CHANGES.txt for v3.6.117 - [`8e8ba93`](https://github.com/007revad/Synology_HDD_db/commit/8e8ba93d8f7eaa8503030067972845399546b86d) Add v3.6.118 changes to CHANGES.txt - [`8ebe2fb`](https://github.com/007revad/Synology_HDD_db/commit/8ebe2fb58a70a931b9c64f3fe139243e13b18534) Update script to v3.6.118 - [`0f370e7`](https://github.com/007revad/Synology_HDD_db/commit/0f370e72805133e752c2686bd800af7e7bccf9e9) Merge pull request #551 from 007revad/main - [`f4052cd`](https://github.com/007revad/Synology_HDD_db/commit/f4052cde0ed86acb06d1b72eaffb878956c892bb) Update TRIM instructions for RAID configurations - [`e3bd37f`](https://github.com/007revad/Synology_HDD_db/commit/e3bd37f7432e4a5fd324c8976c27b59a155cdfc8) Update CHANGES.txt for version 3.6.118 ### 📊 Changes **3 files changed** (+49 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `CHANGES.txt` (+5 -0) 📝 `README.md` (+2 -2) 📝 `syno_hdd_db.sh` (+42 -1) </details> ### 📄 Description v3.6.118 - Changed to enable creating M.2 storage pool and volume in Storage Manager after making DSM check disk compatibility. Issue #441 - Added SSD TRIM warning of possible data loss if non-Synology SSDs or NVMes are in RAID 5, 6 or SHR with more than 3 drives. - See https://kb.synology.com/en-global/DSM/tutorial/Why_is_SSD_TRIM_available_only_for_SSDs_in_the_compatibility_list --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>