[GH-ISSUE #4] Disks not getting verified on a RS2821RP+ #505

Closed
opened 2026-03-11 11:26:27 +03:00 by kerem · 5 comments
Owner

Originally created by @MiranoVerhoef on GitHub (Feb 28, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/4

Hello!,

First and foremost thank you for the effort you've put into making this.

I ran this on my own NAS with the following hardware:

  • RS2821RP+
  • 4 x ST10000NM001G-2MW103

Using your script it does add them, but it keeps saying Not-verified:

afbeelding

Originally created by @MiranoVerhoef on GitHub (Feb 28, 2023). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/4 Hello!, First and foremost thank you for the effort you've put into making this. I ran this on my own NAS with the following hardware: * RS2821RP+ * 4 x ST10000NM001G-2MW103 Using your script it does add them, but it keeps saying Not-verified: ![afbeelding](https://user-images.githubusercontent.com/67699857/221825204-b761eff6-bac1-4472-8acb-cabe6a0270a0.png)
kerem 2026-03-11 11:26:27 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@007revad commented on GitHub (Feb 28, 2023):

Was that the first you ran the script? I notice that it showed your drive model was already in the .db files. If that was the 2nd time you ran the script that would explain why your drive model was found in the .db files the 2nd time.

Can you reboot the NAS and see if it still shows the drives as not supported.

<!-- gh-comment-id:1447968246 --> @007revad commented on GitHub (Feb 28, 2023): Was that the first you ran the script? I notice that it showed your drive model was already in the .db files. If that was the 2nd time you ran the script that would explain why your drive model was found in the .db files the 2nd time. Can you reboot the NAS and see if it still shows the drives as not supported.
Author
Owner

@MiranoVerhoef commented on GitHub (Feb 28, 2023):

it is indeed the 2nd i ran this, i ran it the first time but closed the Putty session. Once its optimized (disks) i'll restart the NAS

<!-- gh-comment-id:1447999724 --> @MiranoVerhoef commented on GitHub (Feb 28, 2023): > it is indeed the 2nd i ran this, i ran it the first time but closed the Putty session. Once its optimized (disks) i'll restart the NAS
Author
Owner

@007revad commented on GitHub (Mar 1, 2023):

If rebooting after the disk optimizing has finished doesn't solve the problem there is an updated version available that will hopefully solve your issue.
https://github.com/007revad/Synology_HDD_db/releases/tag/V1.0.6

<!-- gh-comment-id:1449488481 --> @007revad commented on GitHub (Mar 1, 2023): If rebooting after the disk optimizing has finished doesn't solve the problem there is an updated version available that will hopefully solve your issue. https://github.com/007revad/Synology_HDD_db/releases/tag/V1.0.6
Author
Owner

@MiranoVerhoef commented on GitHub (Mar 1, 2023):

Hey!

The NAS finished syncing this morning so i restarted it and it seems to be working! Is it reccomended to update the script anyway?

Thank you again for all the effort put in!

<!-- gh-comment-id:1449491018 --> @MiranoVerhoef commented on GitHub (Mar 1, 2023): Hey! The NAS finished syncing this morning so i restarted it and it seems to be working! Is it reccomended to update the script anyway? Thank you again for all the effort put in!
Author
Owner

@007revad commented on GitHub (Mar 1, 2023):

Excellent!

If it's working you might as well stick with the script version you have.

<!-- gh-comment-id:1449690455 --> @007revad commented on GitHub (Mar 1, 2023): Excellent! If it's working you might as well stick with the script version you have.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_HDD_db#505
No description provided.