chefmangoo

ya right. i mean i run a script to unlock the encrypted disks before it starts, but this should do no harm as it does not put stuff on the fuse layer. i am still not sure what caused the trouble but i highly assume it has to do with my zfs backup scripts, maybe they created a name collision or smth. so my best idea is to not do that anymore from now on manually. thank you too for your help, highly appreciated

hallelujah, it is working now. big thanks! /usr/libexec/unraid/shfs helped a lot. thx for sharing this command, i did not know how to start fuse manually. the mkdir /mnt/user said "mkdir: cannot create directory ‘/mnt/user’: File exists" but i could see the shares afterwards mounted more or less correctly. it seems that my zfs datasets had to do with it. i experimented with zfs before unraid hat the support and somehow there were conflicts. i did this mainly for backups. solution was to deactivate 1) all my custom zfs dataset based backup scripts 2) clean up the datasets one by one that i do not need anymore and voila, fresh restart, shares mapped correctly 3) i also changed some scripts to not use the fuse layer so much anymore to prevent timing issues. hopefully this will keep it safe in the future thanks everyone for the help, highly appreciated

Rebooted in safe mode without started array, re-enabled user shares. Diag1 created. Array started, Diag2 created. voyager-safemode-usershares-enabled-diagnostics-20260402-1327.zipvoyager-safemode-2-diagnostics-20260402-1328.zip

Hi JorgeB, I started the server in normal mode with stopped array, disabled User Shares, started the array, wanted to stop the array to re-enable user shares, but it said "Array Stopping - Retry unmounting user share(s)" still and forever. Have this behaviour also in Safe Mode even when the Array started with Disabled User Shares, both Diags attached while it trys "Array Stopping•Retry unmounting user share(s)...System running in safe mode" I can only restart the server (which also tries to unmount user shares first but after some time it just does) voyager-diagnostics-20260402-1245.zipvoyager-safemode-diagnostics-20260402-1300.zip

Good question I have another NAS in my local network that could have something to do with it, but it does not actively pushes/syncs something to this machine and has no ssh access to it. There is a user script on the problematic machine that does this by pulling something to backup. It uses rclone and pulls data,but as you said right now it is in safe mode I have no other machine that accesses it, i mean i could ssh into it and do stuff from my personal machine but there is no automation. I maybe have some name duplication, like on different pools using the term backup and doing zfs stuff. Dunno exactly anymore. So far thanks for the hint with "backup". If this share is the problematic one, maybe i can pin point it by deactivating stuff and start the server without network access and so on. I will try it tomorrow and post results here.

Started the array in normal mode. Diagnostics attached. voyager-safemode-diagnostics-20260401-2112.zip

Hi JorgeB, thank you for your help. SafeMode Reboot Diags are attached. voyager-safemode-diagnostics-20260401-2003.zip

Hello everyone, i have a problem with my user shares. They all are zfs pool shares. And Unraid 7.2.4 tells me they are empty? I tried several things but don't know how to proceed. Seems they can not be mapped correctly. Would be great if you can help me. Example (pool "warpcore") /mnt/warpcore/isos works and has files, /mnt/user/isos points to it, but says "empty". ls -la /mnt/warpcore/ drwxrwxrwx 2 nobody users 17 Mar 28 15:28 isos/ df -h /mnt/user/isos Filesystem Size Used Avail Use% Mounted on rootfs 63G 3.8G 60G 7% /mnt In the logs i see something like 2880: Mar 30 18:19:21 Voyager emhttpd: error: malloc_share_locations, 8649: Operation not supported (95): getxattr: /mnt/user/isos voyager-diagnostics-20260330-1845.zip