sux

I am running minidlna on my unraid 7.01. As i see an earlier post worked fine until very recently. Not made any changes i am aware of. Been running in host mode earlier but tried changing to bridge mode as hinted in an earlier post but still not working again. Anyone that understands what may be wrong? Including my minidlna log. 2025-05-18 12:46:30.834555 [info] Host is running unRAID 2025-05-18 12:46:30.852257 [info] System information: Linux bae8dbca5769 6.6.78-Unraid #2 SMP PREEMPT_DYNAMIC Thu Feb 20 13:33:15 PST 2025 x86_64 GNU/Linux 2025-05-18 12:46:30.869504 [info] Image tags: BASE_RELEASE_TAG=2025012801,IMAGE_RELEASE_TAG=1.3.3-5-01 2025-05-18 12:46:30.890855 [info] PUID defined as '99' 2025-05-18 12:46:30.922372 [info] PGID defined as '100' 2025-05-18 12:46:30.956102 [info] UMASK defined as '000' 2025-05-18 12:46:30.975900 [info] Permissions already set for '/config' 2025-05-18 12:46:31.003553 [info] Deleting files in /tmp (non recursive)... 2025-05-18 12:46:31.027591 [info] SCAN_ON_BOOT defined as 'yes' 2025-05-18 12:46:31.048802 [info] SCHEDULE_SCAN_DAYS defined as '06' 2025-05-18 12:46:31.068947 [info] SCHEDULE_SCAN_HOURS defined as '02' 2025-05-18 12:46:31.098194 [info] SHARED_NETWORK defined as 'no' 2025-05-18 12:46:31.117490 [info] Starting Supervisor... 2025-05-18 12:46:31,351 INFO Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing 2025-05-18 12:46:31,351 INFO Set uid to user 0 succeeded 2025-05-18 12:46:31,353 INFO supervisord started with pid 7 2025-05-18 12:46:32,357 INFO spawned: 'crond' with pid 74 2025-05-18 12:46:32,360 INFO spawned: 'start' with pid 75 2025-05-18 12:46:32,361 INFO reaped unknown pid 8 (exit status 0) 2025-05-18 12:46:33,362 INFO success: crond entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2025-05-18 12:46:33,362 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2025-05-18 12:46:48,415 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22679913647632 for <Subprocess at 22679913645712 with name start in state RUNNING> (stdout)> 2025-05-18 12:46:48,415 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22679915501584 for <Subprocess at 22679913645712 with name start in state RUNNING> (stderr)> 2025-05-18 12:46:48,416 INFO exited: start (exit status 0; expected) 2025-05-18 12:46:48,416 DEBG received SIGCHLD indicating a child quit

I think i found the source of the error at least. Noticed i could create a new folder on the share but not edit the existing ones (mostly created by sabnzbd) Found this thread Tried changing the setting mentioned in sabnzbd to 777 and then i could delete the file downloaded. Not sure if this is a symtom of something i should adress but might atleast be a quick fix for now.

-rw-r--r-- 1 nobody users 8493 Feb 3 08:41 000-alan_walker-walkerworld_2.0.nfo Did i get this right? This is a file i tried to delete but couldnt.

Sorry, one week away from windows. I lost you after the command i could paste 😵‍💫

The shares named data

Seems to be the same, made it public and tried to delete a file. Get the response The operation can’t be completed because you don’t have permission to access some of the items.

Hi! Started from unraid 7, created user shares with a non root user that has read/write on the smb share. From my mac i connect to the share and when i use "get info" my user is stated to have both read/write access. Whenever i try to add or edit anything on the share i still get a permission error. Any ideas? Hard to move forward since i really cant find anything that seems wrong but i still dont get write right on my shares.