mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 21:55:59 +03:00
[GH-ISSUE #536] DS1511+ with DSM 6.2.4-25556 doesn't like ST10000NM0086-2AA101 #192
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#192
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aleksei-z on GitHub (Dec 8, 2025).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/536
That was DS1010+ renamed to DS1511+ to make it upgradable to DSM 6.2.4.
Tried script with different set of options, -n, -f, -i but it doesn't like these HDDs. System health status is Healthy but both hard disks "Not supported by the current DSM version". Both disks worked on that same NAS with DSM 5.2. Is it even possible to make it work?
Scripts is trying to update ds1511+_host_v7.db. Is it supposed to be for DSM 7.* of both?
./syno_hdd_db.sh -n -f -i --showedits
Synology_HDD_db v3.6.112
DS1511+-j x86_64 DSM 6.2.4-25556-8
Using model: ds1511+
ds1511+_host_v7 version 8019
Using options: -n -f -i --showedits
Running from: /opt/Synology_HDD_db-main/syno_hdd_db.sh
HDD/SSD models found: 2
ST10000NM0086-2AA101,SN05,10000 GB
ST3000VN007-2E4166,SC60,3000 GB
No M.2 drives found
No M.2 PCIe cards found
No Expansion Units found
ST10000NM0086-2AA101 already exists in ds1511+_host_v7.db
ST3000VN007-2E4166 already exists in ds1511+_host_v7.db
Support disk compatibility already disabled.
Drive db auto updates already disabled.
ST10000NM0086-2AA101:
{
"SN05": {
"size_gb": 10000,
"compatibility_interval": [
{
"compatibility": "support",
"not_yet_rolling_status": "support",
"fw_dsm_update_status_notify": false,
"barebone_installable": true,
"barebone_installable_v2": "auto",
"smart_test_ignore": false,
"smart_attr_ignore": false
}
]
},
"SN02": {
"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
}
]
},
"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
}
]
}
}
/var.defaults/lib/disk-compatibility contains only v7 db files
/var.defaults/lib/disk-compatibility# ls
ds1511+_e10m20-t1_v7.db dx1211_v7.db dx517_v7.version rx1216sas_v7.db rx2417sas_v7.version
ds1511+_e10m20-t1_v7.release dx1211_v7.version dx5_v7.db rx1216sas_v7.version rx410_v7.db
ds1511+_e10m20-t1_v7.version dx1215ii_v7.db dx5_v7.version rx1217rp_v7.db rx410_v7.version
ds1511+_host_v7.db dx1215ii_v7.version fx2421_v7.db rx1217rp_v7.version rx415_v7.db
ds1511+_host_v7.release dx1215_v7.db fx2421_v7.version rx1217sas_v7.db rx415_v7.version
ds1511+_host_v7.version dx1215_v7.version rx1211rp_v7.db rx1217sas_v7.version rx418_v7.db
ds1511+_m2d17_v7.db dx1222_v7.db rx1211rp_v7.version rx1217_v7.db rx418_v7.version
ds1511+_m2d17_v7.release dx1222_v7.version rx1211_v7.db rx1217_v7.version rx4_v7.db
ds1511+_m2d17_v7.version dx213_v7.db rx1211_v7.version rx1222sas_v7.db rx4_v7.version
ds1511+_m2d18_v7.db dx213_v7.version rx1213sas_v7.db rx1222sas_v7.version rx6022sas_v7.db
ds1511+_m2d18_v7.release dx510_v7.db rx1213sas_v7.version rx1223rp_v7.db rx6022sas_v7.version
ds1511+_m2d18_v7.version dx510_v7.version rx1214rp_v7.db rx1223rp_v7.version rxd1215sas_v7.db
ds1511+_m2d20_v7.db dx513_v7.db rx1214rp_v7.version rx1224rp_v7.db rxd1215sas_v7.version
ds1511+_m2d20_v7.release dx513_v7.version rx1214_v7.db rx1224rp_v7.version rxd1219sas_v7.db
ds1511+_m2d20_v7.version dx517_v7.db rx1214_v7.version rx2417sas_v7.db rxd1219sas_v7.version
@aleksei-z commented on GitHub (Dec 9, 2025):
Problem solved by removing disks from existing raid, reinitializing them, and disabling compatibility check.
By some reason DSM 6.2 thought raid was created in newer DSM version although it was created in 5.2.