v3.5.106

• Bug fix for when script is not located on a volume. Issue #397

v3.5.105

• Bug fix for drives that return "HCST " as the model, like HGST drives do. Issue #389

v3.5.104

• Some disks will be blocked in special scenarios. PR #387

v3.5.103

• Bug fix getting size of large drives. Issue #368
  • Run the script once with the --restore option to undue the previous changes then run the script as normal.

v3.5.102

• Changed to use a faster method of detecting if an expansion unit is connected, for models with the syno_slot_mapping command.
• Changed so XPE users using the hdddb addon don't need to reboot.

v3.5.101

• Changed to support "--restore --ssd=restore" to restore write_mostly when restoring all other changes. Issue #340
  • When using --restore you can also use --ssd=restore, -e or --email

v3.5.100-RC

• Changed to support "--restore --ssd=restore" to restore write_mostly when restoring all other changes. Issue #340
  • When using --restore you can also use --ssd=restore, -e or --email

v3.5.98

• Changed to automatically download and install dtc if all of the following 4 conditions are met:
  1. dtc is not already installed.
  2. /bin/dtc or dtc are not in the same folder as the script.
  3. The script needs dtc.
  4. The script is running from task scheduler.
• Bug fix for "Enable write_mostly on slow internal drives so DSM runs from the fast internal drive(s)." Issue #340
• Improved output to make it clear which drive(s) have most_writely set

v3.5.97

• Changed silently skip empty .db.new files with showing an error. Issue #175
• Changed to warn if db file is 0 bytes.

v3.5.96

• Added option to set write_mostly for your internal HDDs so DSM will normally read from your faster internal SSD(s).
  • It can automatically set DSM to read from your internal SSDs.
  • Or you can tell the script which internal drive(s) DSM should read from.

Thanks to Xeroxxx for the writemostly suggestion and their writeup here:
https://www.techspark.de/speed-up-synology-dsm-with-hdd-ssd/