What Does “Failed to Load dm Table: Invalid Argument” Mean in This Case?
In April 2025, a new ZimaCube owner reported that an update to ZimaOS 1.4 failed with Failed mounting bundle: Failed to load dm table: Invalid argument. The same failure occurred from the automatically offered update and after downloading the release image manually.
The key detail was the starting version. An IceWhale team member said they had recently encountered the issue and asked whether the installed version was below 1.2.5.
What Fix Did the IceWhale Team Recommend?
The team recommendation was version-specific: if the system was below ZimaOS 1.2.5, first perform an offline update to 1.2.5 and only then upgrade to 1.4.0. This was a staged upgrade path for early releases, not a universal fix for every current update error.
The original poster started on ZimaOS 1.2.1 and later reported that an offline upgrade to 1.3.3 succeeded, after which the normal upgrade to 1.4.0 worked.
How Does the Current Offline Update Process Work?
The current ZimaOS offline update guide instructs users to download the appropriate RAUCB installation package, place it in the offline-update directory, wait for ZimaOS to detect it, and then run the update from the interface.
| ZimaOS version | Offline package directory |
|---|---|
| Before 1.4.1 | /ZimaOS-HD/rauc/offline/ |
| 1.4.1 and later | /ZimaOS-HD/.ota/offline/ |
This directory change matters because the 2025 community reply linked an older offline-update workflow. Do not automatically use the old path on a current release.
What Should You Do If You See the Same Error Today?
- Record the exact installed ZimaOS version.
- Record the target version and full error message.
- If upgrading from an early 1.2.x release toward 1.4.0, the staged-upgrade solution from this thread is directly relevant.
- For newer releases, follow the current ZimaOS offline-update documentation.
- Use the RAUCB package intended for the target release and the directory appropriate for your current version.
- Back up important data before recovery or multi-step version changes.
Frequently Asked Questions
Was the ZimaCube hardware defective?
The thread does not establish a hardware fault. The problem was resolved by changing the software upgrade path.
Should every ZimaOS user update to 1.2.5 first?
No. That advice was specifically given to systems below 1.2.5 that were trying to reach ZimaOS 1.4.0.
Where should I place an offline update package now?
Current documentation uses /ZimaOS-HD/.ota/offline/ for version 1.4.1 and later, while older versions use /ZimaOS-HD/rauc/offline/.
