A 2025 ZimaOS feature request asked for two related capabilities: encrypting storage from inside ZimaOS and unlocking already encrypted external drives such as LUKS, BitLocker, or VeraCrypt volumes. Zima staff acknowledged the use case and said the request would be discussed, but the thread did not announce a shipping version or confirm that those formats are supported today.
What the Community Thread Actually Confirmed
The original poster could not access a LUKS-encrypted USB HDD in ZimaOS, including after trying the CLI. Later replies asked whether planned encryption work would also cover USB drives and BitLocker volumes. None of the staff replies in that thread documented a finished feature.
That means an old comment such as “encryption is being worked on” should not be converted into a current product claim without a newer official release note.
Why External Drive Encryption Matters
An external backup disk is easy to remove from a server. Encryption protects the data at rest if that disk is lost or stolen, provided the passphrase or recovery material is not stored with the drive.
The upstream Cryptsetup LUKS FAQ describes LUKS as Linux disk encryption built on dm-crypt and emphasizes recovery and header-backup risks. Microsoft's Microsoft BitLocker FAQ defines BitLocker To Go for removable USB drives and external HDDs. These are separate encryption ecosystems, so support for one format does not imply support for another.
What You Can Do with ZimaOS Today
If your workflow depends on removable encrypted media, first verify whether the exact current ZimaOS build can mount that format before committing production backups to it. The external drive mount workflow is useful for understanding current external-drive mount behavior, while ZimaOS cloud integration helps separate local removable storage from other backup and sync paths.
For ordinary unencrypted removable media that must also be shared across the LAN, the NAS file sharing basics explains the current ZimaOS Samba sharing model. Do not reformat an encrypted disk simply because ZimaOS cannot currently unlock it unless you already have a verified copy of the data.
Do Not Infer Encryption from RAID
RAID, filesystem layout, and login authentication are not substitutes for drive encryption. A storage pool can be difficult to reconstruct outside the original system and still not provide cryptographic protection. Treat “hard to read elsewhere” and “encrypted at rest” as different security properties.
Bottom Line
The source thread is a feature request, not evidence that ZimaOS currently supports LUKS, BitLocker, or VeraCrypt external drives. If removable-drive confidentiality is a requirement, validate the exact format and current ZimaOS release before relying on the server for that workflow, and keep recovery material plus an independent backup.
