Releases: 007revad/Synology_HDD_db
Releases · 007revad/Synology_HDD_db
v3.6.130
05 Jun 20:30
Compare
Sorry, something went wrong.
No results found
Bug fix for Samsung SSDs that have 2.5" in their model name.
Bug fix for not removing leading spaces in drive model names (introduced in v3.6.123).
v3.6.129
03 Jun 06:34
Compare
Sorry, something went wrong.
No results found
Bug fix for backing up expansion unit db files (introduced in v3.6.126).
v3.6.128
03 Jun 04:33
Compare
Sorry, something went wrong.
No results found
Bug fix for trying to backup *_v7.db.version instead of *_v7.version.
v3.6.127
03 Jun 00:50
Compare
Sorry, something went wrong.
No results found
Bug fix for trying to backup *_v7.db.version instead of *_v7.version.
Bug fix for 6 TB drives having "size_gb": 6001 in db files instead of "size_gb": 6000.
Also replaces any existing "size_gb": 6001 in db files with "size_gb": 6000.
v3.6.126
01 Jun 22:44
Compare
Sorry, something went wrong.
No results found
Changed to a more reliable way of getting the NAS model name.
Changed to keep db file backups up to date.
If a DSM update, or the user, has updated the drive databases the old db file backups are replaced with new backups of the unedited db files.
Bug fix for db files with a space in their name, like "rxd1219sas module_v7.db".
Bug fix for restore mode failing to restore E10M20-T1 nic support on NAS models that don't officially support the E10M20-T1.
Bug fix for XPE not showing drive's correct temperature. Issue #585
v3.6.125
19 Apr 12:01
Compare
Sorry, something went wrong.
No results found
Bug fix for lvs and pvs command not found errors for 1 bay NAS (that don't have LVM).
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.