ZimaOS 1.6.1 was an urgent April 2026 corrective release after users upgrading through 1.6.0 reported USB devices that no longer mounted automatically. IceWhale also fixed a more serious backup behavior where a task could continue writing to the system mount point after its intended destination disappeared.
The announcement is historically important, but it should not be presented as the current ZimaOS release. ZimaOS continued through later 1.6.x and 1.7.x versions after this emergency patch.
What ZimaOS 1.6.1 Officially Fixed
- USB devices not auto-mounting after an upgrade;
- backup tasks continuing to write under the system mount point after the original mount point was lost;
- mod modules not starting services according to policy after reboot;
- mount-point names becoming inconsistent when device names contained spaces.
The release also optimized disk-shelf display when third-party enclosures expose many disks and added missing storage-interface translations.
The same changes are preserved in the versioned 1.6.1 release record.
Some Users Still Saw USB Names Gain an _1 Suffix
Replies immediately after the release reported external drives renamed with an _1 suffix and Samba shares that collided with existing names.
This was not evidence that the original auto-mount fix failed. It was a second migration/mount-name problem exposed by the update path.
IceWhale Added a Rename and Recovery Path
Dina later replied that USB mount-point renaming was supported and posted a step-by-step UI flow. Other team replies explained that some old storage folders from 1.6.0 could be moved into an .obsolete folder on ZimaOS-HD during the rename process so users could merge files back into the correct external storage.
Because moving old contents can require temporary space on ZimaOS-HD, users with large external disks should understand what the rename workflow will do before applying it.
Not Every Post-1.6.1 Symptom Had the Same Cause
One ZimaBlade user said the BIOS boot order changed after the update and restored it with firmware defaults. Another user traced a dashboard/Files rendering problem to uBlock Origin rather than storage corruption. Those are useful reports, but neither should be generalized into a universal 1.6.1 failure mode.
Use Current Release Information for New Systems
The April 2026 announcement describes a specific repair release. For a system being installed or upgraded now, check what has shipped in the current ZimaOS release before applying old rollback or recovery advice.
ZimaOS 1.6.1 FAQ
Did 1.6.1 fix the USB auto-mount bug?
Yes. IceWhale listed that as the first official fix in the release.
Did it also fix backups writing to the wrong place?
Yes. The release specifically corrected backup jobs that continued writing to the system mount point after their intended mount point disappeared.
Why did some drives gain _1 after the update?
The replies document a separate mount-name migration issue. IceWhale later provided a rename and old-folder recovery workflow.
Should a new installation deliberately use 1.6.1?
Not simply because this thread exists. It is a historical maintenance release and has been superseded by later ZimaOS versions.
