[GH-ISSUE #490] Strange drive detection issue #166

New issue

Open

opened 2026-03-07 19:16:32 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 19:16:32 +03:00

Owner

Originally created by @tkirkland on GitHub (Jul 8, 2025).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/490

I may be missing something here.

But, in the UI:

(this drive:

)

Is this where one should use the -i option? As you see, the drive is registered in the database unless I'm missing something. Why does it still show as unverified? This is the only drive on which this occurs. Additionally, I have other drives of the same model but different revisions (I assume?) :

(this drive:

)

I traced the script, and if I remember correctly, it had to do with the similarity in the drive strings, though I cannot swear to this due to the elapsed time. There is no impact on usage, though curiosity did get the better of me! :)

It's no big deal; I'm just curious. Also, I scanned known issues, so if I overlooked it, please accept my apologies.

Thank you for creating this script.

Originally created by @tkirkland on GitHub (Jul 8, 2025). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/490 I may be missing something here. <img width="568" height="97" alt="Image" src="https://github.com/user-attachments/assets/1833eacf-fa72-4f39-9521-42e95b1b753e" /> But, in the UI: <img width="634" height="207" alt="Image" src="https://github.com/user-attachments/assets/3d47088b-b3b2-4a0b-98d7-aef774d93fe0" /> <img width="1358" height="29" alt="Image" src="https://github.com/user-attachments/assets/8cfaab73-1cf3-406d-841f-bc4ca6d47ff8" /> (this drive: <img width="227" height="17" alt="Image" src="https://github.com/user-attachments/assets/e9e428b0-0d36-48af-85f6-65cf44e2ed21" />) Is this where one should use the -i option? As you see, the drive is registered in the database unless I'm missing something. Why does it still show as unverified? This is the only drive on which this occurs. Additionally, I have other drives of the same model but different revisions (I assume?) : <img width="1318" height="29" alt="Image" src="https://github.com/user-attachments/assets/8a18d0cd-c7e9-420d-b739-297a5145e712" /> (this drive: <img width="332" height="19" alt="Image" src="https://github.com/user-attachments/assets/f0c5dbe2-5d8b-442e-b666-1783932425dc" />) I traced the script, and if I remember correctly, it had to do with the similarity in the drive strings, though I cannot swear to this due to the elapsed time. There is no impact on usage, though curiosity did get the better of me! :) It's no big deal; I'm just curious. Also, I scanned known issues, so if I overlooked it, please accept my apologies. Thank you for creating this script.

kerem commented

2026-03-07 19:16:32 +03:00

Author

Owner

@007revad commented on GitHub (Jul 11, 2025):

Try running the syno_hdd_db.sh with the -n option, then reboot.

@007revad commented on GitHub (Jul 11, 2025): Try running the syno_hdd_db.sh with the -n option, then reboot.

kerem commented

2026-03-07 19:16:33 +03:00

Author

Owner

@tkirkland commented on GitHub (Jul 11, 2025):

Nope. After reboot:

I was not kidding when I debugged it. That will teach me to be lazy and not make PRs. I'll debug again tomorrow to see if I can isolate the bug.

@tkirkland commented on GitHub (Jul 11, 2025): Nope. After reboot: <img width="176" height="31" alt="Image" src="https://github.com/user-attachments/assets/0b9c9166-11a6-47f4-844e-e8b0f3d82d95" /><br> <img width="347" height="156" alt="Image" src="https://github.com/user-attachments/assets/e48763e7-0a7a-4150-929b-57a49b9596de" /> <img width="562" height="109" alt="Image" src="https://github.com/user-attachments/assets/fc56113e-93dd-4c08-a403-76e59785fec0" /> <img width="628" height="126" alt="Image" src="https://github.com/user-attachments/assets/7ce1189c-02c5-4266-8ba5-5a8e79b3958c" /> I was not kidding when I debugged it. That will teach me to be lazy and not make PRs. I'll debug again tomorrow to see if I can isolate the bug.