This July 2024 IceWhale Community thread is useful because it captured the practical differences users immediately noticed between CasaOS and the early ZimaOS builds: CasaOS felt more open and app-server-oriented, while ZimaOS was moving toward a dedicated NAS experience with integrated storage. Several answers in that thread were explicitly roadmap statements, and some of those features have since shipped.
The biggest changes are easy to verify today: ZimaOS now exposes SSH and a Web Terminal directly through Developer Mode, SMB multi-user accounts and permissions are available in the UI, and RAID remains a first-class ZimaOS storage type. CasaOS still exists as an open-source Docker-focused project, but IceWhale's current product positioning describes ZimaOS as its next-generation NAS direction.
1. How Do You Access the ZimaOS Terminal and SSH?
In July 2024, Zima-Giorgio said SSH configuration still required a monitor and keyboard and that a Developer Mode option would arrive later.
That later feature shipped. Current ZimaOS documentation says:
- Open Settings.
- Open Developer Mode.
- Turn SSH Access on.
- Optionally turn on the built-in Web Terminal.
Current SSH documentation also says ZimaOS user accounts can be used for login, while root-password setup can require local console access depending on the workflow.
2. Why Did RAID Show Fewer Drives Than the Storage Page?
The source author reported two historical tests:
- five SSDs were visible to ZimaOS but only four appeared as RAID candidates;
- three HDDs were visible but only two appeared in the RAID creation flow.
Zima-Giorgio did not diagnose a universal cause from the available information and asked for detailed hardware/controller data. That remains the correct way to represent the source: the thread documented a drive-selection problem but did not establish whether the cause was the onboard SATA controller, an LSI controller, stale metadata, unsupported topology, or an early ZimaOS bug.
Current ZimaOS documentation still classifies storage as USB, Single Disk, and RAID. If a disk appears in the system but not as a RAID candidate, collect lsblk, controller information, filesystem/RAID metadata, and the current ZimaOS version rather than assuming the disk is missing.
3. Does ZimaOS Now Support SMB Usernames and Passwords?
Yes. In 2024, IceWhale said SMB users and passwords were under development. Current ZimaOS now supports Samba member accounts and per-share permissions.
Managers can create members and choose:
- Read;
- Read & Write;
- or Guest access where anonymous sharing is intentional.
4. Did CasaOS Become a RAID-Focused NAS OS?
The 2024 reply said RAID was not planned for CasaOS in the short term and described CasaOS as the more open/playable environment while ZimaOS targeted a more consumer-oriented NAS experience.
That historical direction became more pronounced. The current CasaOS homepage describes CasaOS as a community-based open-source personal cloud focused on the Docker ecosystem and links users toward ZimaOS as the upgraded next-generation NAS OS.
This does not mean CasaOS is unusable for storage or that third-party ZFS/mergerFS stacks cannot be deployed. It means integrated storage management is primarily a ZimaOS product responsibility rather than CasaOS's core UI direction.
5. Are CasaOS and ZimaOS Both Still Relevant?
The source author wanted CasaOS as a lightweight application server and ZimaOS as an all-in-one NAS. IceWhale replied in 2024 that the team's short-term focus had moved to ZimaOS.
Current positioning remains broadly consistent:
- CasaOS: community-driven, open-source Docker/personal-cloud layer that can run on general Linux.
- ZimaOS: dedicated NAS operating system with integrated storage, sharing, remote access, and application management.
The two projects share history and ecosystem ideas, but they are not interchangeable installation models.
6. Why Couldn't the User Edit /etc/fstab Normally in ZimaOS?
The 2024 author booted Linux Mint just to inspect or modify ZimaOS fstab. That difficulty reflects an important architectural difference: modern ZimaOS is not intended to behave like a normal mutable Debian server where persistent system customization starts with editing arbitrary root filesystem files.
Current ZimaOS documentation notes that the root filesystem is read-only under most circumstances. Where manual mounts are required by advanced workflows, ZimaOS documentation tends to use paths under /media rather than treating the root filesystem as a general-purpose mutable Linux installation.
Do not edit ZimaOS system files from another boot environment unless you have a recovery plan and understand how OTA updates and the read-only system image work.
The TechMadeEZ Video Shared in the Thread
The original author later shared a TechMadeEZ video directly in the community thread. It includes a ZimaOS installation, RAID 5 setup, Windows share creation, and Jellyfin installation, so it is preserved here as part of the source material.
The video was published in July 2024, so its ZimaOS interface and RAID workflow should be treated as a historical demonstration rather than an exact current UI walkthrough.
What Changed Since the 2024 Q&A?
| 2024 question/status | Current status |
|---|---|
| SSH required local-console workflow | SSH toggle and Web Terminal are available in Developer Mode |
| SMB users/passwords were under development | Multi-user Samba accounts and permissions are available |
| RAID drive-selection issue unresolved | RAID remains supported; source-specific missing-disk cause was never confirmed |
| CasaOS RAID not a short-term priority | Integrated NAS/storage direction is centered on ZimaOS |
| Editing fstab like ordinary Linux was difficult | ZimaOS now clearly follows a read-only/managed-system model |
ZimaOS vs CasaOS FAQ
Does ZimaOS have a Web Terminal now?
Yes. Current documentation says it can be enabled from Developer Mode alongside SSH.
Can I create separate SMB users in ZimaOS?
Yes. Current Samba management supports member accounts and Read or Read & Write permissions.
Does the source thread prove ZimaOS RAID loses one disk?
No. It records two examples where fewer disks appeared in the RAID workflow, but the hardware/controller details were insufficient to establish a cause.
Should I edit /etc/fstab from a rescue Linux USB?
Not as a normal ZimaOS workflow. The current system uses a managed/read-only architecture, so use supported storage features first and modify system files only with a clear recovery plan.
