mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 21:55:59 +03:00
[GH-ISSUE #528] DSM 6.2.4-25556 Update 8. Overview shows red blocks #186
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#186
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 @nsoriano2 on GitHub (Nov 20, 2025).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/528
Hi,
I had to run your script on a RS3621 (DSM 6, last version) after having added a RX1217rp extension filled with WD RED drives.
It actually works, but now in Storage Manager/Overview all disks are shown as red blocks (including the 12 first synology drives) and the banner says "DANGER. One or more pools caches contain unverified drives..."
That's very annoying... "DANGER"
Is there a workaround ?
Thanks
@007revad commented on GitHub (Nov 20, 2025):
Do you run syno_hdd_db with -n option?
@nsoriano2 commented on GitHub (Nov 20, 2025):
I used instructions from https://nascompares.com/guide/how-to-use-unverified-hdds-and-ssds-on-a-synology-2025-nas-complete-guide/
That's where I've found this script, and there is no -n option.
I'm giving a try with -n...
root@NanoServer:/opt# ./syno_hdd_db.sh -n
Synology_HDD_db v3.6.111
RS3621rpxs x86_64 DSM 6.2.4-25556-8
rs3621rpxs_host_v7 version 8043
rs3621rpxs_host version 4006
Using options: -n
Running from: /opt/syno_hdd_db.sh
HDD/SSD models found: 3
HAT5300-12T,1401,12000 GB
HDWG62AUZSVA,0104,20000 GB
WD202KFGX-68CKWN0,83.00A83,20000 GB
No M.2 drives found
No M.2 PCIe cards found
Expansion Unit models found: 1
RX1217rp
HAT5300-12T already exists in rs3621rpxs_host.db
Updated HAT5300-12T in rs3621rpxs_host_v7.db
Updated HAT5300-12T in rs3621rpxs_host_v7.db.new
Updated HAT5300-12T in rx1217rp_v7.db
HAT5300-12T already exists in rx1217rp.db
Updated HAT5300-12T in rx1217rp_v7.db.new
HDWG62AUZSVA already exists in rs3621rpxs_host.db
HDWG62AUZSVA already exists in rs3621rpxs_host_v7.db
HDWG62AUZSVA already exists in rs3621rpxs_host_v7.db.new
HDWG62AUZSVA already exists in rx1217rp_v7.db
HDWG62AUZSVA already exists in rx1217rp.db
HDWG62AUZSVA already exists in rx1217rp_v7.db.new
WD202KFGX-68CKWN0 already exists in rs3621rpxs_host.db
WD202KFGX-68CKWN0 already exists in rs3621rpxs_host_v7.db
WD202KFGX-68CKWN0 already exists in rs3621rpxs_host_v7.db.new
WD202KFGX-68CKWN0 already exists in rx1217rp_v7.db
WD202KFGX-68CKWN0 already exists in rx1217rp.db
WD202KFGX-68CKWN0 already exists in rx1217rp_v7.db.new
Re-enabled support disk compatibility.
Support memory compatibility already enabled.
Disabled drive db auto updates.
You may need to reboot the Synology to see the changes.
After reboot, the Banner now says : "HEALTHY System is healthy"
Thank you !