xxxliqu1dxxx

I did save my diagnostics from when it was buggy/slow, at 1124am and after fresh reboot, 1130am. do you still want them?

Yes it was. completely new install and I saw some slow down after couple of hours. I tried the governor settings, tried to remove any c states from bios, etc. I ended up "deciding" it was hardware related so I completely changed the hardware and it's night and day. I moved from a desktop i5-2500k with 16gb ddr3 ram, to a laptop i7-11850H and 64gb ram - no more slowdown.

Same here. with 7.2.4. No Connect Plugin that I can see. Happens in safe mode as well. I can see the delay in developer mode as well where it's seconds instead of ms. I do not know of a workaround other than downgrading to 6.7.2 or in the surroundings.

I got it to work I think... with 0000, not 000. Did 6.9.2 change something and makes it not interpret the UMASK properly?

Done - changed to 000, restarted docker, Ran docker safe new permissions, then did another full image backup... and still no permissions given.

Hi all - since 6.9.2, my backups are created using wrong/no permissions and I have to rely on the "Docker Safe New permissions" thing in Tools to fix it. The permissions the urBackup docker for the folders are set as: d--------- 1 nobody users and the files within: ---------- 1 nobody users I tried changing the UMASK from 000 to 777 and no changes. Other than the update to 6.9.2, and routine docker updates, there were no changes in configuration or anything else (that I am aware of)... Would one of you know what to do in this scenario? Thanks in advance!

Do not expose your NAS to the Internet... first rule... in fact, read the Security section of this forum for more information. And this:

Did you add 6000 to ADDITIONAL_PORTS as well as adding it the "old way"?

I did the same and resulting in same image... did you find a resolution to your issue? Thanks!

Thanks for the PSA. I had several error messages myself when there were DB issues, and ended up deleting everything and starting fresh, but never had to simulate a catastrophic failure. I only backup small datasets in comparison to your use case, but still this is worrysome, as the stable version of Duplicati is not even recommended anymore... so there are not lots of alternative in this Duplicati world. Do you know of alternatives of tools that are: 1. free 2. can deduplicate 3. can store to cloud as encrypted, splitted files 4. not beta, and that can actually restore without taking weeks 5. not command line only, i.e. needs a free GUI (Duplicacy is close alternative, but with CLI version being only version that's free, this is not intuitive to use and especially restore via command line)

Thanks @steini84 for pointing to the culprit - a docker which still had some configuration in it: (i.e. binhex-urbackup.xml) root@Tower:/# grep -r ssd500gb /boot /boot/config/plugins/dockerMan/templates-user/my-MacinaBox.xml: <HostDir>/mnt/disks/ssd500gb/domains/</HostDir> /boot/config/plugins/dockerMan/templates-user/my-MacinaBox.xml: <Config Name="VM Images location" Target="/image" Default="" Mode="rw" Description="normally /mnt/users/domains" Type="Path" Display="always" Required="false" Mask="false">/mnt/disks/ssd500gb/domains/</Config> /boot/config/plugins/dockerMan/templates-user/my-binhex-urbackup.xml: <HostDir>/mnt/ssd500gb/Backups/</HostDir> /boot/config/plugins/dockerMan/templates-user/my-binhex-urbackup.xml: <Config Name="Host Path 2" Target="/media" Default="/mnt/user" Mode="rw,slave" Description="Container Path: /media" Type="Path" Display="always" Required="true" Mask="false">/mnt/ssd500gb/Backups/</Config> /boot/config/plugins/dockerMan/templates-user/my-duplicati.xml: <HostDir>/mnt/ssd500gb/tmp/</HostDir> /boot/config/plugins/dockerMan/templates-user/my-duplicati.xml: <Config Name="Host Path 2" Target="/tmp" Default="" Mode="rw,slave" Description="Container Path: /tmp" Type="Path" Display="always" Required="true" Mask="false">/mnt/ssd500gb/tmp/</Config> /boot/config/plugins/dockerMan/templates-user/my-diskover.xml: <HostDir>/mnt/disks/ssd500gb/appdata/diskover</HostDir> /boot/config/plugins/dockerMan/templates-user/my-diskover.xml: <Config Name="appdata" Target="/config" Default="/mnt/user/appdata/diskover" Mode="rw" Description="Specify the exact disk. DO NOT USE /mnt/user/appdata either use /mnt/cache/appdata/ or /mnt/disk$/appdata/ " Type="Path" Display="always" Required="true" Mask="false">/mnt/disks/ssd500gb/appdata/diskover</Config> /boot/config/plugins/fix.common.problems/ignoreList.json: "Invalid folder ssd500gb contained within /mnt": "true" Clearing that fixed the issue!!! Thanks again for everyone involved.

If someone else has an idea... I am kind of still stuck. Here's what I attempted doing since last post: 1. recreating zpool 2. recreating dataset with same name 3. created snapshot 4. deleted snapshot 5. deleted dataset (destroyed) 6. delete zpool (destroyed) 7. rebooted and folder was still mounted/present. 8. Currently trying pre-clearing the disk, as this wipes MBR and "starts fresh" from my understanding... Somehow I think there's still something creating this folder, preparing to mount the zvol and/or dataset and/or something else at boot time... Would the plugin creator and/or someone else be able to point to some zfs config file that may still be present despite removing plugin, which would do a mount command and/or a mkdir command at boot time? I mean how can zfs try to do something if the plugin is removed & if the drive is zero wiped?

I can remove it with rm -rf and it comes back after reboot, as shown previously. It gets "recreated" every reboot, even the timestamp changes. there's no "disk usage" with it, just two folders... /mnt/ssd500gb/Backups ... that's it...

root@Tower:/mnt# zfs set mountpoint=none ssd500gb/Backups cannot open 'ssd500gb/Backups': dataset does not exist root@Tower:/mnt# root@Tower:~# zfs destroy ssd500gb/Backups cannot open 'ssd500gb/Backups': dataset does not exist I just cannot see what's recreating it if it's not ZFS... it's gotta be somewhere... it's not in /etc/fstab... what else does the ZFS plugin do upon boot which may have not been cleaned when uninstall occurred?

root@Tower:/# umount /mnt/ssd500gb umount: /mnt/ssd500gb: not mounted. root@Tower:/# df -h Filesystem Size Used Avail Use% Mounted on rootfs 3.9G 796M 3.1G 21% / tmpfs 32M 472K 32M 2% /run devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 196K 128M 1% /var/log /dev/sda1 15G 470M 15G 4% /boot /dev/loop1 7.3M 7.3M 0 100% /lib/firmware tmpfs 1.0M 0 1.0M 0% /mnt/disks /dev/md1 932G 462G 470G 50% /mnt/disk1 /dev/md2 932G 487G 446G 53% /mnt/disk2 /dev/md3 932G 732G 200G 79% /mnt/disk3 /dev/md4 1.9T 906G 957G 49% /mnt/disk4 shfs 4.6T 2.6T 2.1T 56% /mnt/user /dev/sdd1 466G 113G 354G 25% /mnt/disks/ssd500gb /dev/loop2 20G 6.0G 14G 31% /var/lib/docker /dev/loop3 1.0G 17M 905M 2% /etc/libvirt root@Tower:/# root@Tower:/mnt# ls -al total 0 drwxr-xr-x 9 root root 180 Apr 22 14:56 ./ drwxr-xr-x 20 root root 440 Apr 22 14:58 ../ drwxrwxrwx 7 nobody users 76 Apr 22 15:06 disk1/ drwxrwxrwx 5 nobody users 47 Apr 22 15:06 disk2/ drwxrwxrwx 6 nobody users 64 Apr 22 15:06 disk3/ drwxrwxrwx 7 nobody users 75 Apr 22 15:06 disk4/ drwxrwxrwt 3 root root 60 Apr 22 14:56 disks/ drwxr-xr-x 3 root root 60 Apr 22 14:56 ssd500gb/ drwxrwxrwx 1 nobody users 76 Apr 22 15:06 user/ root@Tower:/mnt# rm -r ssd500gb/ root@Tower:/mnt# ls -al total 0 drwxr-xr-x 8 root root 160 Apr 22 15:08 ./ drwxr-xr-x 20 root root 440 Apr 22 14:58 ../ drwxrwxrwx 7 nobody users 76 Apr 22 15:06 disk1/ drwxrwxrwx 5 nobody users 47 Apr 22 15:06 disk2/ drwxrwxrwx 6 nobody users 64 Apr 22 15:06 disk3/ drwxrwxrwx 7 nobody users 75 Apr 22 15:06 disk4/ drwxrwxrwt 3 root root 60 Apr 22 14:56 disks/ drwxrwxrwx 1 nobody users 76 Apr 22 15:06 user/ At this stage it's technically not in /mnt anymore... rebooting server just now. After reboot: root@Tower:~# cd /mnt root@Tower:/mnt# ls -al total 0 drwxr-xr-x 9 root root 180 Apr 22 15:11 ./ drwxr-xr-x 20 root root 440 Apr 22 15:11 ../ drwxrwxrwx 7 nobody users 76 Apr 22 15:06 disk1/ drwxrwxrwx 5 nobody users 47 Apr 22 15:06 disk2/ drwxrwxrwx 6 nobody users 64 Apr 22 15:06 disk3/ drwxrwxrwx 7 nobody users 75 Apr 22 15:06 disk4/ drwxrwxrwt 3 root root 60 Apr 22 15:11 disks/ drwxr-xr-x 3 root root 60 Apr 22 15:11 ssd500gb/ drwxrwxrwx 1 nobody users 76 Apr 22 15:06 user/ root@Tower:/mnt# It's back... The contents of /mnt/ssd500gb is only /mnt/ssd500gb/Backups, which is the name of one of the file systems I had created... so I had a zpool of ssd500gb. Then I created three file systems (I think that's what they are called?) /mnt/ssd500gb/Docker, /mnt/ssd500gb/VMs and /mnt/ssd500gb/Backups... why would Docker and VMs be gone but Backups still be there? and Empty?...

root@Tower:~# zpool status no pools available root@Tower:~# zpool import -a no pools available to import I cannot seem to find what is recreating that folder... drwxr-xr-x 3 root root 60 Apr 22 14:56 ssd500gb/ rebooted a couple of minutes ago and you can see root is recreating it and unlike the other standard Unraid folders, this one is not 777... any other ideas?

Hi - long story short, installed ZFS plugin, worked well, but did not need it in the end, so destroyed pool, removed ZFS plugin, rebooted and I am left with some traces and somehow still have stuff mounting and/or created under /mnt. How do I get rid of this automatic creation of a folder in /mnt? Full story: I originally had an XFS Unassigned Device for backup purposes which was working ok. It was mounted under /mnt/disks/ssd500gb. Thinking I had lots of duplicate files and/or blocks on it, since I am backing up several clients to it, I installed the ZFS plugin, moved all my data elsewhere, created my pool and mounted under /mnt/ssd500gb. This worked well for a while, until I decided to not use ZFS anymore and move back to ZFS Unassigned Device (dedup ratio was 1.05% so was not worth it in the end). I therefore destroyed the pool ssd500gb, then removed partitions on the Unassigned Device, recreated a XFS ssd500gb partition, and marked it as auto mounted from the Unraid UI. The problem I have now is that I see both: /mnt/ssd500gb (seems to be from old ZFS pool) /mnt/disks/ssd500gb (seems to be the new XFS partition and mounted) I am pretty sure the first one is from the ZFS stuff as mentioned, but I cannot seem to get rid of it... deleting with rm -rf does not persist and upon reboot it comes back. I seem to be able to copy files back to /mnt/disks/ssd500gb so I think the XFS UD is working again. Would you know what is remounting and/or recreating something in /mnt and how to make it stop? Thanks!