fnOS (fnNAS) Hard Drive Compatibility: No Whitelist, No Locks — What Actually Matters
Compatibility data on this site last refreshed 2026-11-03 · reading time ~3 min
fnOS (also written fnNAS, from Fnnas, 广州铁刃智造) takes a different approach to drive policy from Synology. It is a Debian-based operating system you install on your own x86 (and Arm) hardware — and Fnnas also sells its own NAS appliances on top of it (see our official hardware guide). Either way, there is no appliance-side drive whitelist and no firmware lock: any drive your board can see is usable for storage pools. There is no official compatibility list to check — which is exactly why this guide exists.
What fnOS does not do
- No drive whitelist: fnOS never blocks a drive for not being on a list. There is no incompatibility-list concept at all.
- No branded-drive requirement: retail WD Red/IronWolf/Exos/MG drives work the same as any other SATA drive.
- No per-model HCL: compatibility is a property of your motherboard, controller and cables — not of fnOS.
What actually matters when buying drives for fnOS
Because fnOS does not test or restrict drives, the buying logic collapses back to the vendor's own ratings: NAS-class or enterprise-class drives with CMR recording and a stated yearly workload. Those are the same drives the Synology, QNAP, Asustor and TerraMaster lists favor — which is why the drive rankings on this site are a reasonable proxy for what to put in an fnOS box. If you buy a Fnnas appliance, Fnnas sells official HDD bundles (Toshiba/Seagate 4–64 TB) — those are the vendor-blessed choices. CMR vs SMR matters even more on a software NAS: a rebuild that stalls on SMR has no vendor support line to call.
System disk: a separate, small SSD
fnOS installs its system onto a single drive. The minimum is 8 GB, and the official installer recommends a 64 GB system partition when the disk has room; swap is auto-sized from RAM. Keep the system on its own SSD — even a small, cheap SATA/NVMe SSD — and pool the HDDs separately. A failed system disk otherwise takes the boot of the whole box with it.
File systems: ext4, Btrfs, ZFS
fnOS supports all three mainstream file systems. For single-disk or basic pooling, ext4 is the safe default. Btrfs adds checksumming and snapshot-style features with lighter resource use. ZFS is the choice for ECC-equipped builds and larger arrays, at the cost of RAM. Drive brand does not change this decision — capacity mix and RAM do.
Community-reported quirks worth knowing
- U.2 NVMe drives were not specially adapted as of late 2025: some U.2 enterprise SSDs were reported invisible under fnOS 1.0 while working in the same machine under other systems; Fnnas staff acknowledged the gap and logged it (club.fnnas.com, December 2025).
- A 2.5-inch HGST drive pair triggered identical smart-error reporting on an N100 box in January 2025; Fnnas confirmed the issue and said the detection tooling would be improved. The drives themselves were fine under Synology.
- Both cases share one lesson: fnOS's disk detection layer is young. If a drive misbehaves only under fnOS, test it in another system before blaming the hardware — and prefer mainstream NAS drives with large install bases.
How fnOS compares with the four vendors we track
Synology's 2025-era policy restricts which drives can create pools on newer Plus models (see our DSM 7.3 policy guide), and its enterprise lines still require listed drives. QNAP, Asustor and TerraMaster publish advisory lists without enforcement. fnOS sits at the far open end: no list at all. The practical consequence is that drive choice for fnOS is a pure hardware-quality decision — capacity, CMR, workload rating — not a policy compliance decision. Use the ranked drives and series pages on this site to pick on quality, then verify against your motherboard's controller.
Quick answers
Does fnOS have an official hard drive compatibility list?
No. fnOS is an operating system that runs on your own hardware (and on Fnnas's own NAS appliances), so there is no appliance-side HCL and no drive whitelist. Any drive your board detects can be used for storage pools.
Can I use any hard drive with fnOS?
Functionally yes — fnOS does not block drives. The recommendation is still to use NAS-class or enterprise-class CMR drives with a rated yearly workload, because software NAS has no vendor support line to fall back on during a rebuild.
What is the minimum disk size to install fnOS?
fnOS installs onto a single drive. The minimum is 8 GB; the official installer recommends a 64 GB system partition when the disk allows. Keep the system disk separate from your HDD pool — a small SSD is the safe choice.
Is fnOS compatible with U.2 NVMe drives?
Not reliably as of late 2025: U.2 enterprise SSDs have been reported invisible under fnOS 1.0 while working under other operating systems, and Fnnas staff have acknowledged that U.2 is not yet specially adapted. Treat U.2 as experimental on fnOS.
Check your exact model
Compatibility is per machine and per part number. Pick your model for its full official drive list: