[NOTICE]
The TCRP-mshell "firmware version cannot be recognized" Issue-related improvements
ARPL covers this error with an addon called hdddb. (Probably requires separate selection)
TCRP provides the same coverage with an addon called drivedatabase.
It's from @007revad's Synology_HDD_db scripts.
After installing DSM, you must boot at least once for this message to disappear.
This improved addon was created under the new name syno-hdd-db.
https://github.com/PeterSuh-Q3/tcrp-addons/tree/main/syno-hdd-db
This addon records the firmware version and model in advance in the model management db file (contents are json) upon installation of DSM.
So, “The firmware version is not recognized.” I have improved it so that you cannot see the message at all.
With a structure roughly like this
DB for each model, such as /var/lib/disk-compatibility/ds3622xs+_host_v7.db
It is written to the end of the file.
Covers both disk and NVMe.
If you are curious about the contents inside
You can check the contents by executing this command with the root account.
jq. /var/lib/disk-compatibility/ds3622xs+_host_v7.db
{
"key": "SSDSC2BB080G4", --> Model name
"value": {
"D2010355": { --> Firmware version
"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
}
]
}
}
}
TCRP automatically replaces the existing drivedatabase with syno-hdd-db.
If you have previously applied it well and have no problems, there is no need to build a new loader.
This new addon will be automatically applied to loaders built in the future.