[GH-ISSUE #195] In DS918+, a problem occurred with the Micron 1100 SSD 2TB, which is included in the compatibility list officially supported by Synology. #579

New issue

Open

opened 2026-03-11 12:19:10 +03:00 by kerem · 0 comments

kerem commented

2026-03-11 12:19:10 +03:00

Owner

Originally created by @PeterSuh-Q3 on GitHub (Dec 29, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/195

Originally assigned to: @007revad on GitHub.

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?

Originally created by @PeterSuh-Q3 on GitHub (Dec 29, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/195 Originally assigned to: @007revad on GitHub. There was an inquiry from a user using two products: DS918+ and Micron 1100 SSD 2TB. ![스크린샷 2023-12-29 오전 11 19 24](https://github.com/007revad/Synology_HDD_db/assets/85427533/63d996c6-27b6-435a-bdf1-bc7717ff38f1) 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. ![image thumb png 18135b16c531a45fb882a95a162e73ca](https://github.com/007revad/Synology_HDD_db/assets/85427533/065725b7-a0ec-4303-bc53-4e31dc1e7ca6) 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. ![image thumb png d96067bd12e09c5cb4637ea49f92c95b](https://github.com/007revad/Synology_HDD_db/assets/85427533/c80edc3b-616f-498a-a6f8-6e436a0f3596) How can I supplement the script to re-record firmware information? Don't you have any good opinions?