Synology_HDD_db: Release 1.1.9 not working on RS4021xs+
When I execute the script I get a bunch of errors like this:
sda SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 10 00 00 00 00 20 00 00 c0 00 00 00 25 20 00 00 00 00 00 00 00 00 00 00 00 HDIO_GET_IDENTITY failed: Invalid argument
I think these come from the getfirmware function. If I replace hdparm -I with smartctl -i that function does not return any errors and the script runs normally and reports that my drives already exist in the db files (Because I’ve run this a few times now). Unfortunately, Synology still shows the drives as not compatible if I don’t use the -f flag. I want to use the deduplication capability so I don’t want to use the force flag.
What could be wrong here? What tests can I do?
The drives I am trying to add:
HDD/SSD models found: 6 P043S3T8EMC3840,Revision: ESFA P043S7T6EMC7680,Revision: ESV7 PX02SMF040,Revision: MS01 PX02SMF040,Revision: MS02 PX04SMB040,Revision: AM04 PX05SMB040,Revision: 0101
NVMe drive models found: 1 WD_BLACK SN850X 2000GB,620311WD
P043S3T8EMC3840 already exists in rs4021xs+_host_v7.db P043S3T8EMC3840 already exists in rs4021xs+_host_v7.db.new P043S7T6EMC7680 already exists in rs4021xs+_host_v7.db P043S7T6EMC7680 already exists in rs4021xs+_host_v7.db.new PX02SMF040 already exists in rs4021xs+_host_v7.db PX02SMF040 already exists in rs4021xs+_host_v7.db.new PX02SMF040 already exists in rs4021xs+_host_v7.db PX02SMF040 already exists in rs4021xs+_host_v7.db.new PX04SMB040 already exists in rs4021xs+_host_v7.db PX04SMB040 already exists in rs4021xs+_host_v7.db.new PX05SMB040 already exists in rs4021xs+_host_v7.db PX05SMB040 already exists in rs4021xs+_host_v7.db.new WD_BLACK SN850X 2000GB already exists in rs4021xs+_host_v7.db WD_BLACK SN850X 2000GB already exists in rs4021xs+_host_v7.db.new
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 49 (21 by maintainers)
Commits related to this issue
- Update syno_hdd_db.sh Debug issue #6 — committed to 007revad/Synology_HDD_db by 007revad a year ago
Sorry @jayanty. I read your comment 2 weeks ago and immediately released a newer version to fix that wrong version number and forgot to reply to let you know.