Backups & Storage

Synology DSM 'Unverified Drive' warning: what it does

Diagnose the Synology 'Unverified drive' warning post-October-2025 reversal: what's still blocked vs warning-only, by model and feature, with the admin path to acknowledge and the legitimate workarounds.

Problem summary

Synology DSM 7.3 (October 2025) partially reversed the 2024-announced third-party drive lockout, but the 'Unverified' warning state still exists. On 2024-and-older Plus models it's purely cosmetic; on 2025-series Plus (DS725+, DS925+, DS1525+, DS1825+, DS425+) it's mostly cosmetic for SATA but blocks specific features (M.2 NVMe cache, deduplication, DSM-driven firmware updates, full Drive Health detail). The fix is knowing what's blocked vs what's not, and acknowledging the warning where the UI allows.

Operator snapshotEvidence first

First proof

Confirm DSM version is 7.3.2-86009 Update 3 (March 2026) or later.

Screen to open

Control Panel > Info Center > General; Control Panel > Update & Restore > DSM Update

Expected signal

Control Panel > Info Center shows DSM 7.3.2-86009 or higher.

Stop boundary

Stop if any update fails — diagnose the update failure first.

Layer path

1DSM 7.3 (October 2025) partially reversed the 2024-announced third-party drive lockout — DSM install and Storage Pool creation on 2025-series Plus are no longer blocked for third-party SATA drives. The 'Unverified' warning state still exists with banner + Notification Center entries.

2Policy state varies by chassis: 2024-and-older Plus = warning-only (legacy HCL behavior); 2025-series Plus = warning + specific feature blocks (M.2 NVMe, dedup, firmware updates); XS / SA / FS / HD series still strictly HCL-only; J / Value have no restriction.

3Independent failure layers: drive verification (this page) is unrelated to drive health. A healthy unverified drive is fine; a failing unverified drive needs replacement regardless of the warning state.

4Safety boundary: do NOT modify `/etc/synoinfo.conf` or run community HCL-patching scripts on a NAS holding critical data without a recent Hyper Backup + tested restore.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Update DSM to 7.3.2-86009 Update 3 or later

Check: Control Panel > Update & Restore > DSM Update > apply available updates.

Expected result: DSM version is current; reboot completes successfully.

If not: Don't proceed with policy diagnostics on older DSM — behavior differs.

Safe stop: Stop if any update fails — diagnose the update failure first.

Identify chassis class and look up drive HCL

Check: Note model from Info Center; cross-reference your drive SKU at synology.com/en-us/compatibility for your specific model.

Expected result: Decision made: drives on HCL = no further action; drives not on HCL = decide between accept-warning vs swap-to-HCL.

If not: If model is unknown / EOL, default to 'treat as 2024-or-older Plus' (warning cosmetic).

Acknowledge per-disk warnings in Storage Manager

Check: Storage Manager > HDD/SSD > each unverified drive > Action > Health Info > Verify drive.

Expected result: Per-disk Status changes from 'Unverified' to acknowledged; Notification Center entries stop re-posting.

If not: If 'Verify drive' option doesn't appear in Drive 4.0 panel, your DSM is older than 7.3 — update first.

Acknowledge pool-level warning

Check: Storage Manager > Storage > pool tile > ⋯ menu > Acknowledge unverified state.

Expected result: Pool-level banner clears from Storage Manager > Overview.

If not: If no such menu option exists, the pool itself is HCL-clean and the banner is from drives elsewhere.

Silence per-boot email alerts

Check: Control Panel > Notification > Rules > uncheck 'Drive status: Unverified'. Leave 'Drive failure' and 'Drive temperature' rules ENABLED.

Expected result: No more boot-time emails for unverified drives; other drive alerts still work.

If not: Verify with Notification > Push Service > Send test message.

Safe stop: Stop before unchecking all drive-status rules — you'll miss real failures.

Decide on features you need that may be blocked

Check: List required features (dedup, M.2 NVMe cache, DSM-driven firmware updates) and check against the feature matrix.

Expected result: Clear go/no-go list; replace specific drives with HCL-listed SKUs only where blocked features are required.

If not: Don't replace working drives just to silence cosmetic warnings.

Decision tree

If: 2024-or-older Plus (DS923+, DS1522+, DS1821+, DS2422+, etc.) showing Unverified warning.

Then: Cosmetic only; all features work.

Action: Acknowledge per-disk in Storage Manager > HDD/SSD > Action > Health Info > Verify drive. Uncheck the 'Drive status: Unverified' notification rule.

If: 2025-series Plus + need to create a SATA Storage Pool with unverified drives.

Then: DSM 7.3 unblocks this. Pool creation works.

Action: Create the pool normally in Storage Manager > Storage > Create > Storage Pool; accept the unverified-drive prompt. Banner remains but features work.

If: 2025-series Plus + need M.2 NVMe cache or pool with non-HCL NVMe drive.

Then: Hard-blocked even in DSM 7.3. M.2 HCL is much narrower than SATA HCL.

Action: Use Synology SNV3xxx M.2, or buy an M.2 drive from the per-model HCL at kb.synology.com. There is no policy workaround inside official Synology DSM.

If: 2025-series Plus + need volume-wide deduplication.

Then: Disabled for unverified drives — even post-reversal.

Action: Either accept the loss, or replace unverified drives with HCL-listed drives (Synology HAT, or listed WD Red Pro / Seagate IronWolf Pro).

If: Want to silence warnings + restore full features on 2025-series Plus without changing drives.

Then: Community workaround: 007revad/Synology_HDD_db script via SSH + Task Scheduler on boot.

Action: Backup NAS first (Hyper Backup, tested restore). Then SSH + run script + schedule for boot. Use-at-own-risk; may break on future DSM major.

If: Banner persists after acknowledging per-disk in Storage Manager.

Then: Pool-level banner is separate; acknowledge at pool tile > ⋯ menu > Acknowledge unverified state.

Action: Run through Storage Manager > Storage > pool tile > ⋯ menu > Acknowledge unverified state.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
Storage Manager banner: 'One or more pools/caches contain unverified drives.'	Persistent banner across the top of Storage Manager > Overview.	Pool-level unverified state	Acknowledge at pool tile > ⋯ > Acknowledge unverified state. The per-disk warnings on HDD/SSD tab are separate.
Storage Manager > HDD/SSD shows Status: Unverified for specific drives.	Per-drive row in HDD/SSD tab.	Drive not on HCL for this chassis	Action > Health Info > Verify drive (acknowledges per-disk). Or replace with HCL-listed SKU if you need dedup / firmware updates.
Email alert on every boot: 'Drive status: Unverified.'	Inbox getting per-boot per-drive emails.	Notification rule firing on the Unverified state.	Control Panel > Notification > Rules > uncheck the 'Drive status: Unverified' rule.
Volume creation wizard greys out the 'Enable data deduplication' checkbox.	Storage Manager > Volume create > Btrfs options.	Dedup disabled on unverified drives even post-7.3.	Replace unverified drives with HCL-listed drives if dedup matters, or accept its absence.
Drive Health panel shows fewer SMART attributes than expected.	Drive 4.0 panel only shows basic SMART for unverified drives.	Degraded Drive Health detail for unverified.	If full attribute access is critical, run `smartctl -a /dev/sata1` via SSH, or replace with HCL-listed drive.

Reference

Commands and settings paths

Confirm DSM version and update status

Control Panel > Info Center > General; Control Panel > Update & Restore > DSM Update

Where: In DSM web UI.

Expected: Version shows DSM 7.3.2-86009 Update 3 or later. Update & Restore shows 'Your DSM is up to date'.

Failure means: Older DSM has different policy state — the runbook depends on 7.3+ behavior.

Safe next step: Apply available DSM update via Update & Restore > Update.

Identify chassis class and HCL applicability

Control Panel > Info Center > General > Model; cross-reference at kb.synology.com/en-us/DSM/tutorial/Drive_compatibility_policies

Where: In DSM web UI + browser.

Expected: Model name matches one of the documented classes (2025-Plus / 2024-Plus / XS / J / Value); HCL link loads correctly.

Failure means: Unknown / discontinued models have unclear policy state.

Safe next step: Look up the model's compatibility list via `synology.com/en-us/compatibility?search_by=products&model=YOUR_MODEL`.

Verify drive in Storage Manager (acknowledges per-disk)

Storage Manager > HDD/SSD > select unverified drive > Action > Health Info > Verify drive

Where: In DSM web UI.

Expected: Per-disk Unverified banner clears; Notification Center entry no longer re-posts on boot.

Failure means: Pool-level banner is independent; acknowledge separately at pool tile.

Safe next step: Per-disk + per-pool acknowledgement may need to be re-done after a future DSM major update.

Disable per-boot email alerts for Unverified state

Control Panel > Notification > Rules > uncheck 'Drive status: Unverified' (leave other drive-status rules ENABLED)

Where: In DSM web UI.

Expected: Email alerts no longer arrive on each boot. Other drive-health alerts still work.

Failure means: Easy to accidentally disable all drive alerts — only disable the Unverified-specific rule.

Safe next step: Confirm by triggering a test alert via Notification > Push Service > Send test message.

Check actual drive health (independent of verification status)

SSH to NAS as admin; `smartctl -a /dev/sata1` (or sata2, sata3 per drive); look for Reallocated_Sector_Ct, Current_Pending_Sector, UDMA_CRC_Error_Count

Where: Via SSH terminal.

Expected: All three counters show 0 or stable; SMART self-test passes.

Failure means: Drive verification state is independent of drive health — a healthy unverified drive is fine to use.

Safe next step: Replace the drive if SMART shows degradation, regardless of verification state.

Hardware boundary

Hardware and platform boundary

Change only when

Replace unverified drives with Synology HAT or HCL-listed WD Red Pro / Seagate IronWolf Pro only when you specifically need a blocked feature (M.2 NVMe pool, deduplication, full Drive Health detail, DSM-driven firmware updates).

Evidence that matters

Drive SKU + chassis pair on Synology's HCL; M.2 NVMe must be on the chassis-specific M.2 HCL (narrower than SATA HCL); for 2025-series Plus, prefer HCL-listed drives if you plan to use NVMe cache.

Evidence that does not matter

Drive size beyond the chassis's max (most 4-bay can handle 22TB+ even though older docs cite lower); enterprise-class drives where home-NAS drives suffice; aftermarket controllers that bypass the SATA HCL — none of these change the policy state.

Avoid

Buying refurbished/recertified drives from third parties WHILE blaming the 'Unverified' warning for unrelated drive issues; the warning is a label, not a defect indicator.

Related tool/checklist

Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.

NAS storage and backup planner

Last reviewed

2026-05-18 · Reviewed by HomeTechOps. Reviewed against Synology's DSM 7.3 release press release, the kb.synology.com/en-us/DSM/tutorial/Drive_compatibility_policies KB, and community evidence from r/synology, the official Synology community forum, NASCompares, and StorageReview — including the October 2025 reversal coverage and the DSM 7.3.2-86009 Update 3 (March 2026) release notes.

Sources/assumptions

Page state reflects DSM 7.3.2-86009 Update 3 (March 2026). Drive policy is at Synology's discretion to tighten in a future major release.
The 'partial reversal' of October 2025 covered SATA HDD/SSD pool creation and basic features. M.2 NVMe remained HCL-restricted; deduplication and DSM-driven firmware updates remained restricted for unverified drives.
Community workaround references (007revad/Synology_HDD_db) are mentioned for completeness, not endorsed — they require SSH + root and have not been validated against every DSM minor.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Synology: DSM Storage Manager technical specificationsUsed for storage pool, volume, disk-health, file-system, and RAID/SHR operating assumptions.Synology: Snapshot Replication overviewUsed for Btrfs snapshot scheduling, retention math, replication-to-second-NAS planning, and the snapshot-is-not-a-backup boundary on Synology shared folders and LUNs.Synology: SHR (Synology Hybrid RAID) overviewUsed for SHR-1 (one-disk parity) vs SHR-2 (two-disk parity) capacity math and mixed-drive-size planning on DSM.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Avoid unsafe electrical or data-loss steps.
4. Stop when the evidence says the risk moved.

FAQ

I have a 2024 DS923+ and got the 'Unverified' warning on a WD Red Pro — should I do anything?

No, the warning is cosmetic on 2024-and-older Plus models. Pool creation, snapshots, Hyper Backup, Active Backup, encryption, all work normally. Run step 2-5 in the runbook above to silence the per-disk warning and email alerts if you don't want to see them on every boot. Your drive's reliability and your data integrity are unaffected by the warning state.

What about the 2025 DS925+ I just bought — is third-party drive support actually working?

Yes, for SATA HDD/SSD post-DSM 7.3 (October 2025). You can install DSM, create Storage Pools (SHR/RAID/Basic), create Btrfs volumes, run Hyper Backup and Snapshot Replication, and use Active Backup for Business with third-party Seagate/WD/Toshiba SATA drives. Drives show 'Unverified' with banners and Notification Center entries, but the features themselves work. Still restricted on this model: M.2 NVMe cache/pool (HCL-only), volume-wide deduplication (disabled for unverified), DSM-driven drive firmware updates (disabled), full Drive Health detail (degraded — only basic SMART surfaces). The community workaround `007revad/Synology_HDD_db` silences the warnings and restores some features at your own risk.

Will Synology tighten the policy again in a future DSM major?

Possible. Synology framed the October 2025 reversal as 'interim' while their HCL validation framework (HCL 5.0) expands. The DSM 7.3.2 Update 3 release in March 2026 was a pure security patch (telnetd CVE-2026-32746) with no drive-policy changes, and Synology hasn't signaled a re-tightening publicly. But the policy is at their discretion. If you're betting on third-party drives long-term, the safer hedge is buying a 2024-or-older Plus (DS923+, DS1522+, DS1821+, DS2422+) where the warning has always been cosmetic.

How do I tell if a drive is on Synology's HCL for my specific NAS?

Go to `synology.com/en-us/compatibility?search_by=products&model=YOUR_MODEL&category=hdds` (replace YOUR_MODEL with e.g. `DS925%2B` for DS925+). Filter to your specific NAS. Note that the list is per-chassis — a drive on the DS920+ list isn't automatically on the DS923+ list. Synology updates the list on a rolling basis as new drive SKUs are tested. WD Red Plus/Pro (WD40EFPX, WD60EFPX, WD80EFPX, WD101EFBX, WD121KFBX, WD141KFGX, WD181KFGX, WD201KFGX) and Seagate IronWolf/IronWolf Pro (ST4000VN006, ST6000VN001, ST8000VN004, ST10000VN000, ST12000VN0008, ST16000NT001, ST18000NT001, ST20000NT001) are widely listed; Toshiba MG/N300 coverage is uneven.

Problem summary

Layer path

Step-by-step runbook

Update DSM to 7.3.2-86009 Update 3 or later

Identify chassis class and look up drive HCL

Acknowledge per-disk warnings in Storage Manager

Acknowledge pool-level warning

Silence per-boot email alerts

Decide on features you need that may be blocked

Decision tree

Evidence table

Commands and settings paths

Confirm DSM version and update status

Identify chassis class and HCL applicability

Verify drive in Storage Manager (acknowledges per-disk)

Disable per-boot email alerts for Unverified state

Check actual drive health (independent of verification status)

Hardware and platform boundary

Change only when

Evidence that matters

Evidence that does not matter

Avoid

Related tool/checklist

Related problems

Last reviewed

Sources/assumptions

Source-backed checks