[GH-ISSUE #364] HP NVME SSD Tip: Unable to recognize firmware version #629

Open
opened 2026-03-11 12:44:52 +03:00 by kerem · 10 comments
Owner

Originally created by @Mrch08 on GitHub (Oct 12, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/364

hi 007revad. I'm not sure why I added the supplier ID in syno_hdd_vendor_ids as per the prompt. The "Unknown" now shows normal "HP", but the firmware version still indicates it cannot be recognized!
The original 920+system was migrated to SA6400, with system version DSM7.2.1。
1
image

Originally created by @Mrch08 on GitHub (Oct 12, 2024). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/364 hi 007revad. I'm not sure why I added the supplier ID in syno_hdd_vendor_ids as per the prompt. The "Unknown" now shows normal "HP", but the firmware version still indicates it cannot be recognized! The original 920+system was migrated to SA6400, with system version DSM7.2.1。 ![1](https://github.com/user-attachments/assets/e0cc6672-165b-48ba-93ee-537eb7752e69) ![image](https://github.com/user-attachments/assets/2bbafdba-9d45-4991-8cea-79ed29638d6e)
Author
Owner

@noobs69 commented on GitHub (Oct 14, 2024):

{5ED6D4FE-2B9D-4167-90FD-E4962DE0E099}
hi 007revad , please add support to my drive too thanks you

<!-- gh-comment-id:2410378412 --> @noobs69 commented on GitHub (Oct 14, 2024): ![{5ED6D4FE-2B9D-4167-90FD-E4962DE0E099}](https://github.com/user-attachments/assets/2ffd8a22-0af6-4260-93e3-c67abe93d5d4) hi 007revad , please add support to my drive too thanks you
Author
Owner

@007revad commented on GitHub (Oct 15, 2024):

@Mrch08 @noobs69

Are they a real Synology SA6400 or XPE?

<!-- gh-comment-id:2415179086 --> @007revad commented on GitHub (Oct 15, 2024): @Mrch08 @noobs69 Are they a real Synology SA6400 or XPE?
Author
Owner

@noobs69 commented on GitHub (Oct 15, 2024):

@007revad XPE sir

<!-- gh-comment-id:2415189902 --> @noobs69 commented on GitHub (Oct 15, 2024): @007revad XPE sir
Author
Owner

@Mrch08 commented on GitHub (Oct 17, 2024):

@007revad sir Not the real Synology SA6400, it's XPE.

<!-- gh-comment-id:2418952609 --> @Mrch08 commented on GitHub (Oct 17, 2024): @007revad sir Not the real Synology SA6400, it's XPE.
Author
Owner

@Neobond commented on GitHub (Oct 17, 2024):

I have the same thing. I did not run the script yet and I have Synology SA6400 (it's XPE)

2024-10-17_182344

Mine are TEAMGROUP MP44Q 4TB SSDs.

When I ran the script the first time (ensuring it was on Volume 2 HDDs) DSM would no longer boot, indicating that the volume was removed. I had it setup as a boot task with

volume2/scripts/syno_hdd_db.sh --autoupdate=7 trigger

<!-- gh-comment-id:2419998131 --> @Neobond commented on GitHub (Oct 17, 2024): I have the same thing. I did not run the script yet and I have Synology SA6400 (it's XPE) ![2024-10-17_182344](https://github.com/user-attachments/assets/613c7b65-72a0-4d52-95d4-12e4df37d4a1) Mine are TEAMGROUP MP44Q 4TB SSDs. When I ran the script the first time (ensuring it was on Volume 2 HDDs) DSM would no longer boot, indicating that the volume was removed. I had it setup as a boot task with `volume2/scripts/syno_hdd_db.sh --autoupdate=7` trigger
Author
Owner

@007revad commented on GitHub (Oct 19, 2024):

Can you try the following:

  1. Run syno_hdd_db with the --restore option.
  2. Update to https://github.com/007revad/Synology_HDD_db/releases/tag/v3.5.103 and run it.
<!-- gh-comment-id:2424296441 --> @007revad commented on GitHub (Oct 19, 2024): Can you try the following: 1. Run syno_hdd_db with the --restore option. 2. Update to https://github.com/007revad/Synology_HDD_db/releases/tag/v3.5.103 and run it.
Author
Owner

@Mrch08 commented on GitHub (Oct 20, 2024):

sir,I followed the instructions and the problem still persists.
image

<!-- gh-comment-id:2424660003 --> @Mrch08 commented on GitHub (Oct 20, 2024): sir,I followed the instructions and the problem still persists. ![image](https://github.com/user-attachments/assets/a9c019c5-9d1b-4b35-970f-2ea80a0fc927)
Author
Owner

@noobs69 commented on GitHub (Oct 22, 2024):

restored and updated script still same before.

<!-- gh-comment-id:2427956023 --> @noobs69 commented on GitHub (Oct 22, 2024): restored and updated script still same before.
Author
Owner

@noobs69 commented on GitHub (Nov 6, 2024):

@Mrch08 @Neobond update to newest RR version. it's fixed guys . thanks you so much for your time Mr.Russell @007revad

<!-- gh-comment-id:2458752363 --> @noobs69 commented on GitHub (Nov 6, 2024): @Mrch08 @Neobond update to newest RR version. it's fixed guys . thanks you so much for your time Mr.Russell @007revad
Author
Owner

@m0tt commented on GitHub (Nov 21, 2024):

image

For me it's still not working. I run syno_hdd_db with --restore option and then syno_hdd_db but no success. V3.5.103. Any what elase may I try to fix it?

<!-- gh-comment-id:2491414966 --> @m0tt commented on GitHub (Nov 21, 2024): <img width="682" alt="image" src="https://github.com/user-attachments/assets/a04ac370-fd95-4b05-96eb-e6365995aa61"> For me it's still not working. I run syno_hdd_db with --restore option and then syno_hdd_db but no success. V3.5.103. Any what elase may I try to fix it?
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#629
No description provided.