same year/make/model HDD in different NAS with different results using --showedits

[wu0lss4j]

same year/make/model HDD in different NAS with different results using --showedits

[007revad]

I find it interesting that you ignored the:

./Synology_HDD_db/syno_hdd_db.sh: line 1629: dmidecode: command not found

ERROR Total memory size is not numeric: ''

I hadn't realised that Synology NAS models without memory upgrade slots don't have dmidecode.

Both your NAS obviously had DSM 6 previously because they both have host.db and host_v7.db files.

It's interesting that the --showedits option chose to show the contents of the old ds218j_host.db for DS218j and the new v7 ds218_host_v7.db for the DS218.

The "rec_intvl" is not an error. In the old pre-v7 version of the drive database all drives have that line:

        }, {
            "model": "WD60EFZX-68B3FN0",
            "firmware": "",
            "rec_intvl": [1]
        }, {
            "model": "WD60EFRX-68MYMN1",
            "firmware": "82.00A82",
            "rec_intvl": [1]
        }, {

[wu0lss4j]

I had no idea about the dmiencode connection. Yes, all of my NAS' have had DSM 6, I was very late to the DSM 7 party. Anyway, this situation only caused by 17.02.2024 HDD compat db push by Synology, which reddit thread then recommended this script. I studied the script, made an educated guess that this wouldn't mess the NAS and now I find myself here.

So I guess, what I want to ask is,... is this fine? I don't plan to run the script again until I replace dying HDDs. Am I ok with this?

[007revad]

Yes, it's all okay.

And with a DS218/DS218j you really don't need this script.