mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #506] Synology DS925+ with DSM 7.2.2-72806 and WD4003FR #174
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#174
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 @Prometheus0711 on GitHub (Sep 3, 2025).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/506
Brand new NAS with brand new HDD from Western Digital Gold. Manage to disable compatibility lock through telnet at the very first start of the device with all 4 HDD. Then performed the install of the latest DSM.
Once in DSM, I enabled SSH then ran the script fine from local root storage via SSH in /OPT. No error message all good. Just Synology alerts after the script finished running telling the HDD are not in compatibility list. Then tried to reboot and tried to refresh Storage Manager but all drives are still UNRECOGNIZED.
If anyone can help I am stuck here. I do not want to exchange my great Western Digital HDD with Synology monopoly....
Here is the result of the script 👍
$ sudo -s /opt/syno_hdd_db.sh
Synology_HDD_db v3.6.111
DS925+ x86_64 DSM 7.2.2-72806-4
StorageManager 1.0.0-00565
ds925+_host_v7 version 8007
Running from: /opt/syno_hdd_db.sh
HDD/SSD models found: 1
0 @,MFAOAC10,4000 GB
No M.2 drives found
No M.2 PCIe cards found
No Expansion Units found
0 @ already exists in ds925+_host_v7.db
Support disk compatibility already enabled.
Drive db auto updates already enabled.
DSM successfully checked disk compatibility.
You may need to reboot the Synology to see the changes.
@007revad commented on GitHub (Sep 3, 2025):
Why does your WD Gold HDD model shows as
0 @instead of WD4003FRYZ ?What does the following command return?
@Prometheus0711 commented on GitHub (Sep 3, 2025):
Good question I was wondering the same… I do mot know … ? If the pci motherboard hardware does not recognize the minimum I am stuck .. if no solution I will have no choice but buying synology hdd to avoid anymore workaround… I am using synology more than 15 years and always used western digital now with such restriction I was glad to find your scripts to bypass limitations but now its a level above … really disappointed…. Need to tell customer I was too optimistic… Anything I could further check you think ?On 3 Sep 2025, at 23:24, Dave Russell @.***> wrote:007revad left a comment (007revad/Synology_HDD_db#506)
Why does your WD Gold HDD model shows as 0 @ instead of WD4003FRYZ ?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
@007revad commented on GitHub (Sep 4, 2025):
What does the following command return?
@Prometheus0711 commented on GitHub (Sep 4, 2025):
admin@SYNO:/$ cat "/sys/block/sata1/device/model"
0 @
admin@SYNO:/$
@007revad commented on GitHub (Sep 4, 2025):
Does this command return the model number?
@Prometheus0711 commented on GitHub (Sep 4, 2025):
admin@BIGYANGSING:/$ cat "/sys/block/sata1/device/model"
0 @
admin@BIGYANGSING:/$ sudo smartctl -a /dev/sata1 | grep 'Device Model' | awk '{print $3}'
admin@BIGYANGSING:/$
Nothing happens
@007revad commented on GitHub (Sep 4, 2025):
What about this?
@Prometheus0711 commented on GitHub (Sep 4, 2025):
admin@BIGYANGSING:/$ sudo smartctl -a /dev/sata1 | grep 'Product' | awk '{print $2}'
YZ-01FDCB0
admin@BIGYANGSING:/$
I think I know why now.... it is refurbished HDD not official Western Digital that is why they hide the origin... it is Singapore ordering online... probably refurbished black market ... will try send it back to get other ones if cannot send back will have to buy new... I am in Switzerland I do not face such kind of problem when ordering original brands....
@Prometheus0711 commented on GitHub (Sep 4, 2025):
Do you think we could edit firmware and force vendor ID within the HDD itself ?
@007revad commented on GitHub (Sep 4, 2025):
I would try and send them back for a refund.
What does "Storage Manager > HDD/SSD" show as the brand and model of those drives?
@Prometheus0711 commented on GitHub (Sep 4, 2025):
@007revad commented on GitHub (Sep 4, 2025):
So the Brand is WD4003FR and the model is "0 @" and smartctl returns the last half of the model as YZ-01FDCB0
Looks like whoever refurbished it has corrupted the Vendor and Product fields in the firmware.
I would definitely send them back for a refund, and if that's not possible then I'd use them in a USB dock for backups.
@Prometheus0711 commented on GitHub (Sep 4, 2025):
ok will challenge the vendor who is trying to say those are OEM ... which is trying to distract the real problem...
@Prometheus0711 commented on GitHub (Sep 4, 2025):
I am trying the WD Marvel Pro just to try edit firmware ID what ref should it show ?
Current is this : WD4003FRYZ-01FDCB0 0
What should it show : ?
@007revad commented on GitHub (Sep 4, 2025):
Vendor should be WDC
Product should be WD4003FRYZ-01FDCB0
I'm not sure if the zero at the end of the firmware id
WD4003FRYZ-01FDCB0 0is supposed to be there or not.