ZimaOS is a complete operating system, not an application installed on top of Debian. If an Intel NUC boots into ZimaOS only while the USB stick is attached and returns to Debian after reboot, you were running the installer environment or never completed the target-disk installation.
The 2024 thread predates current generic-hardware support. Current documentation now explicitly supports generic x86-64 and clearly instructs users to install from USB onto a target disk, remove the USB, and reboot.
What Went Wrong in the Source Case
The user booted ZimaOS from USB, accessed the UI, removed the USB, and later rebooted into Debian. The internal disk had not become the completed ZimaOS system disk.
ZimaOS Is Not Like CasaOS or YunoHost
CasaOS and similar platforms can sit on top of Linux. ZimaOS is its own bootable NAS operating system.
Current Requirements for a Generic NUC
The current ZimaOS installation guide requires x86-64 hardware, at least 25GB storage, UEFI mode, and Secure Boot disabled.
Step 1: Flash the Installer with Balena Etcher
Download the current image and flash it to USB. The USB is installation media, not the intended permanent system disk.
Step 2: Boot USB and Choose Install ZimaOS
Enter the NUC boot menu, choose USB, then select the actual internal SSD/NVMe as the installation target.
Step 3: Confirm the Correct Disk
This is destructive. Back up Debian/YunoHost first and compare model/capacity carefully before confirming.
Step 4: Wait for the Prompt to Remove USB
Do not pull the stick simply because the web UI is reachable. Wait until installation completes and explicitly tells you to remove USB and restart.
Step 5: Check UEFI Boot Order
If Debian still starts, enter BIOS and move the new ZimaOS UEFI entry ahead of the old Debian bootloader.
Confirm Which Disk Is Running
lsblk
findmnt /Verify the active system is on the intended internal device. The installation troubleshooting guide provides a broader path.
Use the NUC Boot Menu to Verify the New Entry
After installation, open the one-time boot menu and look for the ZimaOS/internal-drive UEFI entry. If it boots correctly once from that menu, then make the same entry first in the permanent BIOS boot order.
Remove Old Debian Boot Entries Only After ZimaOS Works
Do not delete the old EFI bootloader or repartition the Debian disk before confirming the new ZimaOS installation boots independently. Preserve rollback until the new system is proven.
Check Storage Controller Mode
If the installer cannot see the internal SSD, review BIOS storage settings such as AHCI versus RAID/VMD modes. Changing those can also break an existing Debian/Windows install, so record the original setting before experimenting.
Verify Network Hardware After First Boot
Some NUC generations use newer Intel Ethernet or Wi-Fi chipsets. If the OS boots but never appears in ZimaClient, check local console output, DHCP, and NIC detection before assuming installation failed.
Verify the Internal Disk Is Large Enough
Current ZimaOS documentation requires at least 25GB of storage. If the NUC has a small eMMC module plus a larger NVMe SSD, make sure the installer target is the device you actually intend to keep as the system disk.
After successful installation, label or document the system disk so later storage work does not accidentally erase it.
FAQ
Can I install ZimaOS on top of Debian?
No. ZimaOS is a complete OS.
Why did it work until reboot?
You likely booted USB without completing the internal install, or firmware kept booting Debian.
Does current ZimaOS support generic NUC hardware?
Current docs target generic x86-64, though individual controllers still need compatible drivers.
Should the installer USB stay connected forever?
No. Normal installation ends by removing it and booting the internal system disk.
