Synology_HDD_db
Synology_HDD_db copied to clipboard
In DS918+, a problem occurred with the Micron 1100 SSD 2TB, which is included in the compatibility list officially supported by Synology.
There was an inquiry from a user using two products: DS918+ and Micron 1100 SSD 2TB.
https://xpenology.com/forum/topic/70001-main-and-important-918-fake-error-from-ssd-most-likely-synology-compatibility-need-2tb-working-urgently-help-please
My script that references your script is also included in the existing compatibility list. For the Micron 1100 2TB product, the DB information, including the firmware version, has been replaced as follows.
"1100_MTFDDAK2T0TBN": { "default": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true, "smart_test_ignore": false, "smart_attr_ignore": false } ] } },
->
"1100_MTFDDAK2T0TBN": { "M0MU033": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true } ] }, "default": { "compatibility_interval": [ { "compatibility": "support", "not_yet_rolling_status": "support", "fw_dsm_update_status_notify": false, "barebone_installable": true } ] } },
The former is the original content, and the latter is the content that has been replaced and changed.
Due to this changed DB information, the following phenomenon occurred. One of the two is normal, but the other one has a problem with a red message.
So, in my script, I kept the original restore to prevent any merging of models that already exist in the compatibility list.
https://github.com/PeterSuh-Q3/tcrp-addons/blob/main/syno-hdd-db/src/install.sh#L87
As a result, the message below is repeated because there is no firmware version in the original information yet.
How can I supplement the script to re-record firmware information? Don't you have any good opinions?