You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

161 lines
6.5 KiB

v2.2.40
- Added a --restore option to undo all changes made by the script.
v2.2.39
- Now looks for and edits both v7 and non-v7 db files to solve issue #11 for RS '21 models running DSM 6.2.4. This will also ensure the script still works if:
- Synology append different numbers to the db file names in DSM 8 etc.
- The detected NAS model name does not match the .db files' model name.
- Now backs up the .db.new files (as well as the .db files).
- Now shows max memory in GB instead of MB.
- Now shows status of "Support disk compatibility" setting even if it wasn't changed.
- Now shows status of "Support memory compatibility" setting even if it wasn't changed.
v2.1.38
- Improved shell output when editing max memory setting.
- Changed method of checking if drive is a USB drive to prevent ignoring internal drives on RS models.
- Changed to not run "synostgdisk --check-all-disks-compatibility" in DSM 6.2.3 (which has no synostgdisk).
v2.1.37
- Now edits max supported memory to match the amount of memory installed, if installed memory is greater than the current max memory setting.
- Minor improvements.
v2.0.36
- Show the options used.
- Thank you to Gummibando on reddit for their donation.
v2.0.35
- Now allows creating M.2 storage pool and volume all from Storage Manager.
v1.3.34
- Now always shows your drive entries in the host db file if -s or --showedits used instead of only db file was edited during that run.
- Changed to show usage if invalid long option used instead of continuing.
v1.3.33
- Fixed bug inserting firmware version for already existing model.
v1.3.32
- Changed to add drives' firmware version to the db files (to support data deduplication).
- See https://github.com/007revad/Synology_enable_Deduplication
- Changed to be able to edit existing drive entries in the db files to add the firmware version.
- Now supports editing db files that don't currently have any drives listed.
v1.2.31
- Bug fix. The --noupdate option was coded as --nodbupdate. Now either will work.
- Bug fix. Re-enable drive db updates wasn't working in some instances.
v1.2.30
- Fixed "download new version" failing if script was run via symlink or ./<scriptname>
v1.2.29
- Bug fix. v1.2.28 had v1.2.27 in the sh file so it always wanted to update!
v1.2.28
- Fixed bug in getting the M.2 card model.
v1.2.27
- Changed 'latest version check' to download and extract to /tmp then copy only the syno_hdd_db.sh and readme.txt files to the currrently running script's location.
- Minor tweaks to the shell output.
v1.2.25
- Minor bug fix.
v1.2.24
- Bug fix. Ignoring removable drives was ignoring all drives in DSM 7 on a RS2421rp+. Fix issue #23.
v1.2.23
- Changed to show if no M.2 cards were found, if M.2 drives were found.
v1.2.22
- Changed 'latest version check' to download to /tmp and extract files to the script's location to fix issue #27.
v1.2.21
- Reinstated removing brand from start of drive model to fix issue #24.
v1.2.20
- Added a timeouts when checking for newer script version in case github is down or slow to fix issue #25.
- Fixed change log (v1.2.19 and v1.2.18 were listed as v2.2.19 and v2.2.19).
v1.2.19
- Minor change to check new version code.
v1.2.18
- Minor shell output formatting fix.
v1.2.17
- Added disable support memory compatibility option --ram or -r
v1.2.16
- Changed to show the script version, Synology model and DSM version on each run to make it easier to debug any user's issues.
v1.2.15
- Now finds your expansion units' model numbers and adds your drives to their db files.
- Now adds your M.2 drives to your M.2 PCI card's db files (supports M2Dxx and E10M20-T1 and future models with similar model names).
- Improved flags/options checking and added usage help (-h or --help) and version info (-v or --version).
- Can now download the latest script version for you (if you have 'user home service' enabled in DSM).
- Now adds 'support_m2_pool="yes"' line for models that don't have support_m2_pool in synoinfo.conf
- To (hopefully) prevent losing your SSH created M2 volume when running this script on models that DSM 7.2 Beta does not list as supported for creating M2 volumes.
- Added removal of " 00Y" from end of Samsung/Lenovo SSDs to fix issue #13.
- Changed Synology NAS model detection to be more reliable (for models that came in different variations and report extra text after model). issue #2 and issue #10
- Changed checking drive_db_test_url setting to be more durable.
- Fixed bug where removable drives were being added to the drive database.
- Fixed bug where "M.2 volume support already enabled" message appeared when NAS had no M.2 drives.
v1.1.14
- Minor bug fix.
v1.1.13
- Fixed bug in v1.1.12 "check that M.2 volume support is enabled"
v1.1.12
- Added check that M.2 volume support is enabled.
v1.1.11
- Added support for M.2 SATA drives.
- Can now skip processing M.2 drives by running script with the -m2 flag.
- Changed method of getting drive and firmware version so script is faster and easier to maintain. No longer using smartctl or hdparm.
- Changed SAS drive firmware version detection to support SAS drives that hdparm doesn't work with.
- Removed error message and aborting if *.db.new not found (clean DSM installs don't have a *.db.new).
- Fixed script version check introduced in 1.0.7.
v1.1.10
- Now makes DSM recheck disk compatibility so reboot not needed (DSM 7 only).
- Fixed DSM 6 bug when DSM 6 used the old db file format.
v1.1.9
- Added support for SAS drives.
- Now gets HDD/SSD/SAS drive model number with smartctl instead of hdparm.
v1.1.8
- Now prevents DSM auto updating the drive database.
- Disable "support_disk_compatibility" (that was added in v1.0.6) is now optional.
- Run script with -f or -force to disable "support_disk_compatibility".
- If run without -f or -force "support_disk_compatibility" is re-enabled.
v1.0.7
- Added message if newer script version is available.
v1.0.6
- Added 2nd method of disabling disk compatibility to solve issue #1 and #4 for the few people where the original method didn't work.
v1.0.5
- Changed to avoid issue #2
v1.0.4
- Now backs up the database file if there is no backup already.
v1.0.3
Changed to avoid avoid error messages from previous change to search for sda and sata# drives in DSM 6 and DSM 7.
- /dev/sata*: No such file or directory
- /dev/sd*: No such file or directory
v1.0.2
- Improved formatting when listing found drives.
v1.0.1
- Fixed issue where drives weren't detected if:
- NAS had been updated from DSM 6 to DSM 7 and still used sda, sdb etc.
- Models like the DVA3219 that use sata# even in DSM 6.
v1.0.0
- Initial release.