The source thread is useful because it shows how ZimaOS offline updates worked during the 1.3.x era, but the literal path and package filename are historical. The author downloaded a ZimaCube-specific .raucb bundle into an offline-update directory so the system would discover it and show the update indicator.
Current ZimaOS still supports OTA and offline RAUC updates, but IceWhale's current documentation explicitly says the offline package location changed starting with v1.4.1. Current generic x86 releases also use architecture-oriented package names such as zimaos-x86_64-.... Do not copy the 2024 1.3.0-2 URL or old folder into a 2026 system without checking the current release instructions.
The 2024 Source Downloaded a RAUCB Manually
The source author navigated to the official ZimaOS GitHub releases, copied the then-current ZimaCube .raucb URL, and downloaded it over SSH into the offline-update folder.
They expected ZimaOS to scan the directory and show the red update indicator, sometimes after reboot.
IceWhale Preferred the Normal OTA Prompt When It Arrived
Zima-Giorgio replied that another option was to delete the manually downloaded file and wait for the system to notify the user about the update. That shows the source manual method was an alternative when OTA discovery was not appearing, not the only supported update path.
The Offline Package Path Changed After ZimaOS 1.4.1
Current IceWhale documentation says:
- older releases before 1.4.1 used the older RAUC offline location;
- v1.4.1 and later use the newer
.ota/offlinelocation on ZimaOS-HD.
Use the current ZimaOS offline update workflow instead of assuming the 2024 path is permanent.
Choose the Bundle for the Current Hardware Architecture
A later 2026 thread showed why hard-coded old download URLs fail: a user received a 404 from an old mirror and ultimately downloaded the current x86_64 RAUCB from the official GitHub release.
Always use the asset published for your current ZimaOS release and hardware rather than changing only the version number inside an old URL.
Very Old ZimaOS Releases May Need an Intermediate Upgrade
IceWhale has repeatedly documented cases where systems below 1.2.5 needed to upgrade to 1.2.5 first before moving to a much newer release. This is especially relevant to early ZimaCube units that have not been updated for years.
Do not force a modern RAUCB onto a very old slot if current IceWhale guidance specifies an intermediate version.
Direct rauc install Is an Advanced Path
IceWhale staff have used rauc install <bundle> in official troubleshooting and test-driver workflows. That does not mean every routine update should bypass the UI and package-scanning mechanism.
For normal systems, the current offline-update workflow provides a clearer supported path and visible status.
RAUC Updates Depend on ZimaOS's Dual-Slot Recovery Model
ZimaOS maintains system slots so a failed update can be isolated from user data and, in supported recovery situations, the alternate slot can boot. Do not erase or reformat system partitions just because an update does not appear immediately.
Verify the New Version After Reboot
After the update completes, confirm the displayed ZimaOS version, test Files/Storage, verify important apps, and confirm remote/network access. If the update reports success but the version does not change, collect the update error/status rather than repeatedly reinstalling the same bundle.
ZimaOS Offline Update FAQ
Should current users download the 1.3.0-2 ZimaCube package from the source?
No. That package and URL are historical.
Does current ZimaOS still support offline updates?
Yes. IceWhale maintains a current offline-update workflow using RAUCB packages.
Did the offline package folder change after v1.4.1?
Yes. Current IceWhale documentation explicitly notes a path change beginning with v1.4.1.
