Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All docker containers do not have write perms after merging 2 Disks [Bug] #1809

Open
Trollol01 opened this issue May 4, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@Trollol01
Copy link

Trollol01 commented May 4, 2024

I have a issue that all containers do not have write perms

All docker containers do not have the perms to write to the 2 merged storage drives (OS Drive-And Empty Drive). I can add file into the media folder and rename all files but seems like that Jellyfin cannot delete any media file, but can see and read. Pi-Hole works but i can't add a blocklist or block a domain adding to database.

To Reproduce

Steps to reproduce the behavior:

  1. Go to Storage Manager
  2. Click on Merge Storages
  3. Select empty storage and then merge to the OS one
  4. Install for example Pi-Hole ore Jellyfin for example
  5. Try to add a domain to block a Pi-Hole database or try to delete a media from Jellyfin
  6. And then you will see the error: Permission to write error

Expected behavior

Access the Pi-Hole database and add a domain to block. In Jellyfin if i right click and click delete the file will be deleted

Screenshots

Screenshot 2024-05-04 135807

Desktop:

 - OS: Windows 11 23H2
 - Browser Brave
 - Version: v1.65.126


**System Time**

               Local time: Sat 2024-05-04 07:55:07 EDT
           Universal time: Sat 2024-05-04 11:55:07 UTC
                 RTC time: Sat 2024-05-04 11:55:07
                Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

**Logs**

> Run following command to collect corresponding logs:

```bash
Jul 16 05:23:34 CasaOS casaos-local-storage[1039]: Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Jul 16 05:23:34 CasaOS casaos-local-storage[1039]: =======> INVALID ARGUMENT TO -n: /dev/mmcblk0
Jul 16 05:23:34 CasaOS casaos-local-storage[1039]: =======> VALID ARGUMENTS ARE: never, sleep[,STATUS], standby[,STATUS], idle[,STATUS] <=======
Jul 16 05:23:34 CasaOS casaos-local-storage[1039]: Use smartctl -h to get a usage summary
Jul 16 05:23:34 CasaOS casaos-local-storage[1039]: 2169-07-16T05:23:34.024-0400        error        failed to exec shell - smartctl exec error        {"func": "service.(*diskService).SmartCTL", "file": "/home/runner/work/CasaOS-LocalStorage/CasaOS-LocalStorage/service/disk.go", "line": 149}


"The other commands worked perfectly exept that one: sudo journalctl -xef -u casaos-local-storage"

Additional context

I'm a ZImaBoard 832 user

@Trollol01 Trollol01 added the bug Something isn't working label May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant