tabbse

I upgraded from 6.9.2 to 7.0.1 but now znapzend is not running on startup anymore. I already read the posts and i figured, that if it is not starting by itself I will just write the "znapzenz --daemonize" command in my go file. Then I logged the output away and after a reboot this was the output: /var/tmp/go: line 7: znapzen: command not found When I start it again manually in the console everything starts and works fine. I read the Unraid documentation about when and what is startet at boot and plugins should be loaded before the go file. Does anyone know what the problem is here?

Thank you very much @BasWeg and @testdasi for your solution! All working as expected now. Just out of curiosity, do you know why this problem only appeared with version 6.9?

Hello, I'm new here. first of all i would like to thank @steini84 for his great plugin! I am not sure whether my question is correct here, as it is actually a Samba (SMB) problem, which only occurs in connection with ZFS. To access a ZFS device via SMB, you have to edit the Samba extras. Mine looks like this: [Media] path = /mnt/HDD/Media comment = browseable = yes public = no valid users = tabbse writeable = yes vfs objects = I updated from 6.8.3 to 6.9.0 and since then I get the same error message in the system log as soon as I access an SMB share. Mar 2 09:28:21 UNRAID smbd[14859]: ../../source3/lib/sysquotas.c:565(sys_get_quota) Mar 2 09:28:21 UNRAID smbd[14859]: sys_path_to_bdev() failed for path [.]! I can access the share, but it's very annoying as hundreds of lines of the same error message were generated during normal operation (e.g. browsing directories). I've already researched and the only thing I've found is that there is a problem with ZFS because SMB expects a mountpoint entry in /etc/fstab. A guy also came up with a workaround. I quote: "The workaround is pretty simple: add the ZFS subvolume you're using as a share to /etc/fstab. If your share is not a ZFS subvolume, but your share directory is located beneath an auto-mounted ZFS subvolume (not listed in /etc/fstab), add that subvolume to /etc/fstab and the error will go away. No hacky scripts involved." I have no idea how to do it or if it will cause any problems. I can give you the link to the site where I got this information but I didn't know if it is against forum rules. Does anyone else have the same problem or know how to solve it? Thank you very much in advance and if I am wrong here please tell me where else I can ask the question.