Releases: 007revad/Synology_HDD_db
Releases · 007revad/Synology_HDD_db
v3.6.124
20 Feb 23:46
Compare
Sorry, something went wrong.
No results found
Bug fix for script trying to set write_mostly on SATA M.2 drives. Issue #567
Bug fix for script trying to use nvme command to get SATA M.2 drives' vendor id. Issue #567
v3.6.123
19 Feb 21:09
Compare
Sorry, something went wrong.
No results found
Bug fix for WD Ultrastar drives that have "WDC " before the model name. Issue #559
v3.6.122
14 Feb 07:25
Compare
Sorry, something went wrong.
No results found
Bug fix for drive models with multiple consecutive spaces in model name. Issue #559
Bug fix for nvme drives with multiple consecutive spaces in firmware version.
Bug fix for options not working. Issue #559 and #563
Thanks @MeowPerth and @jjlizz
v3.6.121
12 Feb 04:25
Compare
Sorry, something went wrong.
No results found
Added --reboot option to reboot the NAS after a DSM update where the build number has changed.
Only needed if NVMe volume or PCIe card need a 2nd reboot after DSM update.
Note: This version of the script needs to run once to create the file that tracks the DSM build number.
v3.6.119
20 Jan 08:11
Compare
Sorry, something went wrong.
No results found
Bug fix for "cat: /sys/block//sys/block/sata1/device/vendor: No such file or directory" errors. Issue #554
v3.6.118
19 Jan 05:44
Compare
Sorry, something went wrong.
No results found
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.
v3.6.116
14 Dec 02:32
Compare
Sorry, something went wrong.
No results found
Moved the "Warn if script located on NVMe volume" code to after the "check for new script version code". Issue #540
Bug fix for incorrectly warning that the script is located on an NVMe volume when it is on a SHR HDD volume that has, or had, different HDD sizes. Issue #540
v3.6.115
13 Dec 21:46
Compare
Sorry, something went wrong.
No results found
Added syno_hdd_shutdown.sh to the auto update code.
Now if script is located on an NVMe volume it warns you and exits. Previously it just warned you and continued.
Bug fix for DSM 7.3 not disabling compatible drive database auto update.
Bug fix for script thinking it's on an NVMe volume if the HDD volume it's on has a NVMe cache. Issue #540
v3.6.114
13 Dec 19:20
Compare
Sorry, something went wrong.
No results found
Added syno_hdd_shutdown.sh to the auto update code.
Now if script is located on an NVMe volume it warns you and exits. Previously it just warned you and continued.
Bug fix for DSM 7.3 not disabling compatible drive database auto update.
v3.6.113
10 Dec 23:07
Compare
Sorry, something went wrong.
No results found
Added check that DSM 7.3 db file was successfully compacted.
Added drive's firmware version to messages.
Improved checking if drive and firmware version were successfully added to db file.
Bug fix for adding duplicate drive if 2 or more of the same drive model had different firmware versions.
Also removes duplicate drive entries if they exist (before correctly editing the file).
Bug fix adding size_gb to to drive firmware version entries instead of just the "default" key section.