Current Reality: ZimaOS Supports ZFS, but the Public Workflow Is Still CLI-Oriented
The feature request is partly still relevant. Current ZimaOS storage documentation acknowledges ZFS for snapshots, checksums and advanced data integrity, but the published ZFS setup process remains command-line based. The regular Storage UI focuses on RAID 0, 1, 5, 6 and JBOD.
The ZimaOS ZFS setup shows the current ZFS path, while the ZimaOS RAID levels defines the normal Storage UI choices.
For a 5-Bay NAS, Start With the Recovery Goal
Do not choose ZFS, RAID 5, RAID 6 or exFAT because one is “more advanced.” Decide what failure you need to survive:
- Primary active storage: RAID 5 for efficient capacity and one-disk fault tolerance, or RAID 6 when two-disk fault tolerance matters.
- ZFS active storage: stronger integrity tooling, snapshots and datasets, with more CLI responsibility in current ZimaOS.
- Portable cold copy: exFAT when direct Windows/macOS readability matters more than Linux permissions and snapshot features.
exFAT Is Read/Write Compatible, but That Does Not Mean the Storage UI Can Create It
Current ZimaOS format compatibility lists exFAT as readable/writable for USB and internal disks. The public Storage workflow, however, does not clearly document a GUI action to format an arbitrary disk as exFAT. Those are two separate capabilities.
Use exFAT for portability, not as the primary database/app-data filesystem. It lacks the Unix permission and snapshot semantics expected by many Linux services.
Snapshots Protect Against Different Problems Than RAID
RAID protects availability when disks fail. A ZFS snapshot can help recover earlier file states after accidental changes or deletion. A snapshot on the same pool is still not an off-device backup. OpenZFS documents ZFS snapshots and RAIDZ layouts.
Use Built-In Backup Before Building a Custom rsync Scheduler
The 2026 request proposed a graphical rsync manager. ZimaOS now has a broader 3-2-1 Backup workflow for local, LAN, USB and cloud destinations. If the real goal is scheduled replication to a cold disk, test whether the built-in backup semantics meet the requirement before adding another scheduler.
The ZimaOS backup and ZimaOS data migration cover different parts of that lifecycle.
A Practical 5-Bay Layout
One reasonable design is four disks in RAID 5/6 or a ZFS pool for active data, plus one removable/independent disk for a cold copy. But putting the fifth disk in the same chassis does not make it a disaster-recovery copy if theft, power damage or chassis failure affects all drives together.
The ZimaCube 2 storage provides a current multi-drive hardware reference.
What the Feature Request Is Really Asking For
The missing value is not “ZFS support” in the abstract. It is safe lifecycle management in the UI: create/import pools, show resilver status, schedule snapshots, browse/restore snapshots, export pools, and manage portable filesystems without shell commands. That is a legitimate product-layer distinction.
Do Not Put Every Recovery Mechanism in the Same Pool
A five-bay chassis invites you to use every disk for primary capacity, but resilience improves when one copy has a different failure boundary. A ZFS snapshot inside the main pool, a fifth internal exFAT disk and an external/offsite backup each protect against different failures. For irreplaceable data, at least one copy should survive loss of the NAS chassis itself.
This is also why “portable cold storage” and “high-integrity active storage” should not be forced into the same filesystem choice: portability favors exFAT, while snapshots, checksums and Unix permissions favor ZFS or another native Linux storage design.
FAQ
Does ZimaOS support ZFS now?
Yes. Current public documentation includes ZFS pool and dataset commands, but the workflow remains CLI-oriented.
Can ZimaOS create RAIDZ in the normal Storage UI?
Current public Storage UI documentation focuses on RAID 0, 1, 5, 6 and JBOD. Do not assume RAIDZ creation is exposed in the same UI.
Can ZimaOS read and write exFAT?
Yes, current disk-format compatibility lists exFAT as read/write for USB and internal disks.
Are ZFS snapshots a backup?
No. Snapshots are valuable point-in-time recovery inside the storage system, but they should be paired with an independent copy.
Should I use exFAT for Docker app data?
Usually no. Use a Linux filesystem with proper ownership/permission semantics for application databases and persistent container data.
