The 2024 source thread reflects a very different storage workflow from current ZimaOS. A new ZimaBlade owner bought two drives and asked how to mount, format, and choose a filesystem. Community replies recommended creating GPT partitions, usually formatting ext4, finding UUIDs with blkid, editing /etc/fstab, and following Debian's software-RAID instructions for RAID 1.
That advice made sense in the CasaOS/Debian context of the thread, but it should not be the default for a current ZimaOS installation. ZimaOS now detects new disks and guides the user through storage creation, RAID, JBOD, and single-disk setup from Settings > Storage.
What the 2024 Community Workflow Was Doing
The responder suggested preparing the disks on another PC, using a GPT partition table, creating ext4 partitions, then mounting them persistently by UUID through /etc/fstab. For a two-drive mirror, they pointed the user to Debian software RAID.
Those were community Linux instructions, not IceWhale-authored ZimaOS storage steps.
Current ZimaOS Detects New Disks Automatically
Current IceWhale guidance says that when a new disk is connected, ZimaOS prompts the user to set it up. The normal workflow is:
- open Settings > Storage;
- click Combine;
- choose the intended storage configuration;
- select the drives;
- name the storage space and confirm.
Use the current ZimaOS storage setup workflow instead of editing /etc/fstab for ordinary managed disks.
Two Drives Can Be Used as RAID 1
If the goal is a mirrored two-disk array, RAID 1 remains the straightforward choice. Both disks hold the same data, so usable capacity is roughly the size of one member drive while one disk can fail without immediately losing access to the dataset.
RAID 1 protects against one disk failure. It does not protect against accidental deletion, malware, controller failure, theft, or destruction of the whole server.
Do You Need to Choose ext4 Manually?
In the old thread, ext4 was suggested because the system was being administered like a conventional Debian host. Current ZimaOS storage setup manages the filesystem and array creation as part of the storage workflow.
If you have a special reason to use ext4, Btrfs, ZFS, or another supported filesystem, make that decision based on the current ZimaOS storage feature you are using rather than blindly reproducing a 2024 CasaOS partition recipe.
USB Drives Are Now First-Class Storage Too
Current ZimaOS documentation explicitly says USB drives follow the same storage logic as internal HDDs and SSDs. They can be used as single storage, added to an array, or used to expand existing space.
This is another reason older CasaOS-era mount instructions should not define the current experience.
When UUID and fstab Still Matter
UUID-based mounts remain standard Linux technology and can still be useful in advanced custom configurations. But manually editing host mount rules creates a second storage-management layer that ZimaOS may not understand or present correctly in its UI.
Use manual mounts only when the built-in Storage model cannot represent the requirement and you are prepared to own the mount lifecycle yourself.
Formatting Destroys Existing Data
Any workflow that creates a new filesystem or RAID array can erase the selected drives. Confirm the physical disks, back up anything important, and do not assume a drive label such as sda or sdb remains stable between boots.
New Drive Setup FAQ
Should a current ZimaOS user edit /etc/fstab to add a normal new drive?
Usually no. Use the managed Storage interface first.
Can two drives be configured as a mirror?
Yes. RAID 1 is the normal two-drive mirrored configuration.
Is the 2024 Debian SoftwareRAID procedure official ZimaOS guidance?
No. It was community advice from the CasaOS/ZimaBlade era.
