v3.6.137
- Bug fix for the wrong E10M20-T1, M2D20, M2D18 and M2D17 db files getting processed if the main drives were migrated from a different Synology model.
- Bug fix for not updating db files with each drive's firmware version if drives were previously added to the db files without firmware version from an older script version. Issue #598
- Bug fix for restore mode not re-enabling drive database updates in DSM 7.3 and later.
- Bug fix for sometimes not detecting script was running from scheduled task.
- Bug fix for errors showing in all red instead of just ERROR being in red.
- 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
Added a new option to reboot the NAS after DSM updates if the build number has changed, specifically for NVMe volumes or PCIe cards requiring a second reboot.
v3.6.114
- 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
- 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.
v3.6.109
- Added -I, --ihm option to update IronWolf Health Management to 2.5.1 to support recent model IronWolf and IronWolf Pro drives.
- For NAS with x86_64 CPUs only.
Dave Russell
tkirkland
Ing