ZimaOS 1.6.2 Beta 2: Changed /media permissions (possible regression or new storage policy)

Insight & Feedback
1

After updating to ZimaOS 1.6.2 Beta 2, I noticed a change in how permissions are handled for mounted disks under /media.

Current behavior:

  • All newly mounted Btrfs volumes are owned by:

    • root:root

    • permissions: 755

  • A non-root user cannot write directly to the root of mounted disks

Example:



touch /media/Save/test.txt → Permission denied
sudo touch /media/Save/test.txt → works

System check:

  • Filesystems: Btrfs

  • Mount options include:

    • rw

    • noacl

  • Mount is handled by zimaos-local-storage.service

Example:



/dev/sdd on /media/Save type btrfs (rw,relatime,noacl,...)

Directory permissions:



drwxr-xr-x root root /media/Save

Observation:

  • Older mount points (created before the update) may still have more permissive access (e.g. 777)

  • Newly created or remounted volumes follow the new restrictive model

  • Internal folders (e.g. Nextcloud data) still use their own service users (e.g. www-data)

Possible cause:

It looks like changes in the zimaos-local-storage layer in 1.6.x introduced a stricter ownership model:

  • storage volumes are now treated as system-managed resources

  • root owns mount points by default

  • user-level write access is expected to go through services, shares, or application layers rather than direct filesystem access

Issue:

This breaks the expected NAS usage pattern:

  • users cannot copy files directly into disk roots via SSH or file manager

  • behavior is inconsistent between old and newly mounted disks

  • there is no clear mention of this change in the 1.6.2 beta changelog

Question:

Is this:

  1. an intentional redesign of the storage permission model in ZimaOS 1.6.x

    or

  2. an unintended regression introduced in zimaos-local-storage.service in Beta 2?