greenflash24

Hi, i am trying to run a Post-backup script (from the User-Scripts plugin), but the backup failed, because the script does not exists, which is not true, see: [01.01.2024 03:29:34][❌][Main] /boot/config/plugins/user.scripts/scripts/my-script2/script is not existing! Skipping! root@server:~# file /boot/config/plugins/user.scripts/scripts/my-script2/script /boot/config/plugins/user.scripts/scripts/my-script2/script: Bourne-Again shell script, ASCII text executable root@Home-Server:~# ls -la /boot/config/plugins/user.scripts/scripts/my-script2/script -rw------- 1 root root 229 Dec 30 18:32 /boot/config/plugins/user.scripts/scripts/my-script2/script Am I doing anything wrong with my configuration?

That's very unfortunate.

Is there currently any way for using an existing zfs pool with native zfs encryption as an Unraid pool, or does it have to be formatted? If not, is Unraid planning to add support for native zfs encryption?

For me the Send Notifications On Update? option is still not respected in the latest version. I have set this option to NO, as a don't want to receive notifications on each container update, but i still get these notifications.

I can confirm that I am also experiencing this issue with 6.12.1.

What exactly is the issue with your Fritzbox in your case? As far as I know there should be nothing on the router side which would prevent the use of ipvlan on the Unraid side. I also use Fritzboxes (7490 and in the last year 6690) with ipvlan since the feature was released since almost 2 years now without any problems.

Thanks for your reply! Now I wonder, how it is encrypted... 🤔 With the password of the Unraid root account? Or with the main array password? Hopefully not with some sort of a universal master password...

@dlandon If I set the password for my LUKS encrypted device in the unassigned devices settings page, will the password itself be stored unencrypted on the flash drive (where the other unassigned devices config resides) or is it stored on the encrypted main Unraid array? How does this mechanism function? In short: Is it safe to set the password through the unassigned devices settings page? I could not find an answer in this thread already, nor documentation.

I do currently already have a 6 drive raidz1 pool which i have created in truenas scale. Will I be able to import this pool into Unraid, if this pool is encrypted via the native zfs encryption?

My Seagate Exos X16 has also such a high Command_Timeout number, see: The Unraid Dashboard shows this as an Error: I am not sure how I have to interpret this data? Should I replace this drive, or is this an false error message?

I am getting the following error since a while now, I have reported it already but it wasn't fixed yet. Has anybody looked into this yet? It only appears when using this plugin, if I uninstall it, this warning message goes away. (See screenshot below) Also It is only shown when the array is stopped (and thus the Docker Service is also stopped). Then I see the following warning message at the bottom edege of the Unraid Dashboard: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [2] No such file or directory Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 898 After the array is started the warining message goes away. Do i have to worry about this warning? I would think this is a false positive, as the docker service is not started yet, as the array is also not started at this moment. So can i ignore it? I have first noticed this warning in 6.9.2 (with the original Docker-Folders-Plugin), but it is still persistent in 6.11.5 with latest Docker-Folders-Plugin. See also:

Can we get the zfs built-in encryption for zfs-only pools, or will these disks still be encrypted via LUKS? As far as I know the currently available btrfs-pools are using LUKS. But the zfs built-in encryption would allow for different encryption settings for each dataset.

This could be potentially related to the issue i have described in the following post: (maybe this thread is related to your issue.)

I have noticed, that the following issue is still present in the latest version of the new Docker-Folders-Plugin: May I ask for a fix for this issue please ⬆️?

Hey @Squid, Just one quick question: As i noticed the following issue was caused by the OLD DockerFolders-Plugin: May you or somebody else with the NEW DockerFolders-Plugin installed test if you are also getting the same warning message before the array is started with the new version. If this issue is still present in the new version, may I ask for a fix?