How to Fix Synology Unverified Drive Warnings for SSDs and HDDs

The Problem

If you’re running non-Synology branded drives in your NAS, you’ve probably seen the dreaded “Unverified” status in Storage Manager. Your storage pool shows “At risk,” you get warning notifications, and DSM generally acts like your perfectly good drives are ticking time bombs.

This is Synology’s way of pushing you toward their overpriced branded drives. The drives work fine. Synology just refuses to officially “verify” them.

The real kicker: even if you’ve fixed this before, DSM updates frequently re-enable the compatibility check and bring the warnings back. But I’ll show you how to make this fix persistent. Keep reading…

The Solution

A community script called Synology_HDD_db by 007revad patches the drive compatibility database to recognize your drives. Here’s how to use it.

Step 1: Enable SSH

Go to Control Panel > Terminal & SNMP and check “Enable SSH service” if it’s not already enabled.

Step 2: SSH Into Your NAS

Quick safety note: review the script’s source before running it, since you’re piping a downloaded script straight into bash as root. Disable SSH again when you’re done if you don’t leave it on normally.

Connect via SSH using your admin credentials. On Windows, use PowerShell or PuTTY. On Mac/Linux, use Terminal:

ssh yourusername@your-nas-ip

Step 3: Download and Run the Script

Run these commands:

cd /tmp
curl -O https://raw.githubusercontent.com/007revad/Synology_HDD_db/main/syno_hdd_db.sh
sudo bash syno_hdd_db.sh

The script will detect your drives and add them to the compatibility database. You’ll see output confirming each drive model was added.

Step 4: Verify It Worked

Open Storage Manager in DSM. Your drives should now show “Healthy” instead of “Unverified,” and the “At risk” warning on your storage pool should be gone. If not, reboot the NAS and check again.

Making It Permanent

DSM updates will reset the drive database and bring the warnings back. To prevent this, set up the script to run automatically.

Step 1: Save the Script Permanently

The /tmp directory clears on reboot, so move the script somewhere persistent:

sudo mkdir -p /volume1/scripts
sudo cp /tmp/syno_hdd_db.sh /volume1/scripts/

Step 2: Create a Triggered Task

In DSM, go to Control Panel > Task Scheduler and click Create > Triggered Task > User-defined script.

Configure it as follows:

• Task name: Fix Unverified Drives (Or whatever you want to call it.)
• User: root
• Event: Boot-up
• Enabled: Yes

In the Task Settings tab, enter this as the user-defined script:

bash /volume1/scripts/syno_hdd_db.sh

Click OK to save. Now the script will run automatically after every reboot, including after DSM updates.

Why This Happens

Synology maintains a “compatibility list” of approved drives. Drives not on the list get flagged as unverified, even if they’re reliable, enterprise-grade hardware. This is a business decision, not a technical one. Your Samsung, WD, Seagate, or other brand-name drives are fine.

The 007revad script works by adding your specific drive models to Synology’s internal database, effectively whitelisting them. It’s been widely used in the Synology community for years and is regularly updated to support new DSM versions.