ZImaOS 1.6.2 Beta 1 Files Errors

Insight & Feedback ZimaOS Open Beta
21

Here are the exact steps:

  1. I open the ZimaOS-HD folder.

  2. I click the Back button (top left) to go to the parent directory.

  3. In previous versions, this took me to a view where I could see all of my storage drives.

  4. In Beta 2, instead of opening that view, the Files app shows “Oops! Something went wrong.”

I’m not trying to access /media directly. I’m simply navigating back from the ZimaOS-HD folder, and this worked correctly before.

I’ve attached a screenshot showing the location before pressing Back.

Aufzeichnung 2026-07-03 073332

22

Aufzeichnung 2026-07-03 075535

23

We will fix this issue in the next version. Thanks for your feedback

24

You can try it first: go to the ZimaOS-HD directory, then reorder the favorites list to see if this happens. I want to understand the specific steps to address this issue

25

I found the exact trigger.

The issue occurs when I try to reorder the Favorites list. As soon as I drag a favorite to a different position, the operation fails with the following error:

“This request was blocked by the security policy.”

Because of this, I cannot reorder my Favorites.

26

Thans for your feedback. We have reproduced this issue because this version has made security optimizations to prevent path traversal, which caused some Favorites lists to fail to sort. We will fix this issue in the next version.

27

Thanks for the explanation and for reproducing the issue. That makes sense. I’m glad the cause has been identified, and I appreciate the quick response. I look forward to the fix in the next version.

28

I tested ZimaOS 1.6.2-beta2 on a ZimaBoard using ZimaBrain CE as a verifier-first diagnostic tool.

The update completed successfully and ZimaBrain CE verified the board was running:

ZimaOS v1.6.2-beta2
Kernel 6.18.9
RAUC: Compatible: zimaos-zimacube
Docker: 5/5 containers running

ZimaBrain CE then detected one confirmed failed systemd unit after reboot:

casaos-every-boot.service loaded failed failed CasaOS every boot

I checked this further from the terminal and found the failing script:

/usr/libexec/every-boot.d/07-targetcli-sync-users

The script contains:

#!/bin/sh

exec /usr/libexec/targetcli-sync-users

But the target helper does not exist:

ls: cannot access '/usr/libexec/targetcli-sync-users': No such file or directory

The service log also shows the same failure:

/usr/libexec/every-boot.d/07-targetcli-sync-users: line 3: /usr/libexec/targetcli-sync-users: No such file or directory

Storage mounts looked clean on this unit:

/DATA              -> /dev/mmcblk0p8
/media             -> /dev/mmcblk0p8[/.media]
/media/nvme0n1     -> /dev/nvme0n1
/media/sda         -> /dev/sda
/media/sdb         -> /dev/sdb

I did not see the old /media/HDD-Storage-/dev/sdX style path, duplicate _1 mount, or -device-name suffix issue on this test board.

So on this unit, the AppData/media mount side looks okay, but casaos-every-boot.service fails because 07-targetcli-sync-users calls a missing /usr/libexec/targetcli-sync-users helper.

I have not applied any local fix. Just reporting the verified beta result.

ZimaBrain CE beta output summary

I am including the ZimaBrain CE beta results below so the test is transparent.

ZimaBrain CE verified the board state from the local report:

Host OS: ZimaOS v1.6.2-beta2
Host Version: v1.6.2-beta2
Kernel: 6.18.9
Uptime: up 27 minutes
RAUC: Compatible: zimaos-zimacube

ZimaBrain CE also verified the failed systemd unit from the same report:

Verification status:
✅ VERIFIED FROM SAME-REPORT EVIDENCE

Failed host unit findings:
🟡 YELLOW: Failed systemd unit detected

Evidence:
● casaos-every-boot.service loaded failed failed CasaOS every boot

ZimaBrain CE verified the Docker/container state:

Verification status:
✅ VERIFIED FROM SAME-REPORT EVIDENCE

Dashboard container count:
5/5 containers running

No exited containers were parsed from the current dashboard evidence.

ZimaBrain CE is also still beta, so I am not treating every exported answer as final proof. The useful part from this test is that it correctly verified the main local state and detected the failed systemd unit.

The final root cause was confirmed separately from terminal evidence. ZimaBrain CE was useful as a verifier-first alert system, then the exact cause was manually verified from the terminal.