ati

Members
  • Posts

    44
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ati's Achievements

Rookie

Rookie (2/14)

2

Reputation

  1. This is a great start. Thank you!
  2. I generally don't shutdown or stop the array on my unRAID server. I was doing some electrical work in the house this past week and this was the first time I have shutdown my server in some time. I learned I was susceptible to the "Retry unmounting disk share(s)" issue even though I am running on 6.11.5. I run my server on a UPS and have it set to auto shutdown after a 3 minute outage. I always assumed that it would properly shutdown, but I guess not (crazy me assuming things). So for the past 6+ months I have been basically susceptible to an 'unclean' shutdown. Is there any way to force a clean shutdown? Frankly I have very little interest in updating to 6.12.3. I am slowly losing trust in LimeTech to QA/QC any update. The last time I updated I had to rebuild disks due to the Seagate error. While I understand that wasn't all on LimeTech, issuing a 'stable' release that fails to shutdown is pretty crazy. Furthermore, there are still reports of it not being fixed in 6.12.3. I have no interest in beta testing for development, that is why I generally stay a revision behind.
  3. I am hoping someone can give my some guidance on getting Paperless-NGX to work with Nginx Proxy Manager. It works fine when I assign both Redis and Paperless-NGX a br0 address on my LAN. However, when I used a bridge address it does not work. I get an 502 error. This is for local access only. I run an instance of NPM for all my services where the names are *.local (unraid.local, plex.local) etc. PiHole for DNS resolution to point to the NPM server. I generally prefer to setup custom Docker networks for services like this for the redis link, but I cannot seem to get the proxy to work without having both dockers having their own LAN IP.
  4. I want to have BR0 and BR0.10 going to a single container. Either 2 interfaces each on their own VLAN or a single interface that can support trunking.
  5. I have a user created that uses SSH to copy files to a public share on my server. I was using this as a means to copy pictures from my phone to server automatically every night. After the update this now fails with permission denied on copy. I also tried using the same credentials on my windows machine with WinSCP and got the same error. Seems to work fine when I log in as root. user and group of the folder is nobody:nobody as well.
  6. I would like to move my UniFI AP controller into a docker container on my unRAID server. My unRAID server is already configured for VLANs and has the appropriate VLANs accessible to its BR0 interface. What I am not sure about is how to get a trunk port to my UniFI controller's docker container. Current network setup: VLAN 1: Network management VLAN 10: Servers VLAN 20: Wireless clients VLAN 40: IoT clients While everything is routable, I would prefer to not have to route my AP management traffic (VLAN 1) to my UniFI server (VLAN 10). Makes everything more complicated when adopting new equipment. TL;DR How can I pass multiple VLANs to a docker container?
  7. I recently went the route of adding several VLANs to segment my docker containers into DMZ areas. In the process I noticed that you have to have an IP address set in the network settings for the network (VLAN) to be available to Docker. I guess that makes sense, as that is how they learn a default gateway. However, that poses a security risk in my mind. If one of those containers gets compromised, it can access the unRAID server which now has an IP on that network. Is there anyway I can disable the GUI and SSH access from a specific interface? Because it is on the same network segment, a router firewall rule is useless.
  8. Tried that many times. Tried each port individually even. When I deleted the /config/network.cfg I set it back up as a single interface. After lots of reboots (to remove the USB and get diagnostic files off it) it just worked after no changes. Any idea where there are lots of references in the syslog to virbr0 using an IP address that isn't anywhere on my network or unRAID configuration? Regardless, I am afraid to reboot for fear of having this ordeal happen again. I spent 3 hours rebooting my server in circles for it to miraculously work again using the same configuration I started with 3 hours prior.
  9. I am even more lost now. I shut down, to get the diagnostics off the USB and upon reboot it booted normally and I was able to access it via the network. I logged into the web GUI to startup the array. Hell I even got an email alert that my UPS was unplugged (to get the USB out). About 30 seconds into starting the array I lost network again. I connected back to the server to checkout the syslog and saw this: Mar 7 15:14:38 unRAID root: Starting diskload Mar 7 15:14:38 unRAID emhttpd: Mounting disks... Mar 7 15:14:38 unRAID emhttpd: shcmd (197): /sbin/btrfs device scan Mar 7 15:14:38 unRAID root: Scanning for Btrfs filesystems Mar 7 15:14:38 unRAID emhttpd: shcmd (198): mkdir -p /mnt/disk1 Mar 7 15:14:38 unRAID emhttpd: shcmd (199): mount -t xfs -o noatime,nodiratime /dev/md1 /mnt/disk1 Mar 7 15:14:38 unRAID kernel: SGI XFS with ACLs, security attributes, no debug enabled Mar 7 15:14:38 unRAID kernel: XFS (md1): Mounting V5 Filesystem Mar 7 15:14:38 unRAID kernel: XFS (md1): Ending clean mount Mar 7 15:14:38 unRAID emhttpd: shcmd (200): xfs_growfs /mnt/disk1 Mar 7 15:14:38 unRAID root: meta-data=/dev/md1 isize=512 agcount=8, agsize=244188659 blks Mar 7 15:14:38 unRAID root: = sectsz=512 attr=2, projid32bit=1 Mar 7 15:14:38 unRAID root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 7 15:14:38 unRAID root: = reflink=1 Mar 7 15:14:38 unRAID root: data = bsize=4096 blocks=1953506633, imaxpct=5 Mar 7 15:14:38 unRAID root: = sunit=0 swidth=0 blks Mar 7 15:14:38 unRAID root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 7 15:14:38 unRAID root: log =internal log bsize=4096 blocks=476930, version=2 Mar 7 15:14:38 unRAID root: = sectsz=512 sunit=0 blks, lazy-count=1 Mar 7 15:14:38 unRAID root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 7 15:14:38 unRAID emhttpd: shcmd (201): mkdir -p /mnt/disk2 Mar 7 15:14:38 unRAID emhttpd: shcmd (202): mount -t xfs -o noatime,nodiratime /dev/md2 /mnt/disk2 Mar 7 15:14:38 unRAID kernel: XFS (md2): Mounting V5 Filesystem Mar 7 15:14:38 unRAID kernel: XFS (md2): Ending clean mount Mar 7 15:14:38 unRAID emhttpd: shcmd (203): xfs_growfs /mnt/disk2 Mar 7 15:14:38 unRAID root: meta-data=/dev/md2 isize=512 agcount=8, agsize=244188659 blks Mar 7 15:14:38 unRAID root: = sectsz=512 attr=2, projid32bit=1 Mar 7 15:14:38 unRAID root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 7 15:14:38 unRAID root: = reflink=1 Mar 7 15:14:38 unRAID root: data = bsize=4096 blocks=1953506633, imaxpct=5 Mar 7 15:14:38 unRAID root: = sunit=0 swidth=0 blks Mar 7 15:14:38 unRAID root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 7 15:14:38 unRAID root: log =internal log bsize=4096 blocks=476930, version=2 Mar 7 15:14:38 unRAID root: = sectsz=512 sunit=0 blks, lazy-count=1 Mar 7 15:14:38 unRAID root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 7 15:14:38 unRAID emhttpd: shcmd (204): mkdir -p /mnt/disk3 Mar 7 15:14:38 unRAID emhttpd: shcmd (205): mount -t xfs -o noatime,nodiratime /dev/md3 /mnt/disk3 Mar 7 15:14:38 unRAID kernel: XFS (md3): Mounting V5 Filesystem Mar 7 15:14:39 unRAID kernel: XFS (md3): Ending clean mount Mar 7 15:14:39 unRAID emhttpd: shcmd (206): xfs_growfs /mnt/disk3 Mar 7 15:14:39 unRAID root: meta-data=/dev/md3 isize=512 agcount=6, agsize=268435455 blks Mar 7 15:14:39 unRAID root: = sectsz=512 attr=2, projid32bit=1 Mar 7 15:14:39 unRAID root: = crc=1 finobt=1, sparse=1, rmapbt=0 Mar 7 15:14:39 unRAID root: = reflink=1 Mar 7 15:14:39 unRAID root: data = bsize=4096 blocks=1465122442, imaxpct=5 Mar 7 15:14:39 unRAID root: = sunit=0 swidth=0 blks Mar 7 15:14:39 unRAID root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Mar 7 15:14:39 unRAID root: log =internal log bsize=4096 blocks=521728, version=2 Mar 7 15:14:39 unRAID root: = sectsz=512 sunit=0 blks, lazy-count=1 Mar 7 15:14:39 unRAID root: realtime =none extsz=4096 blocks=0, rtextents=0 Mar 7 15:14:39 unRAID emhttpd: shcmd (207): mkdir -p /mnt/cache Mar 7 15:14:39 unRAID emhttpd: cache uuid: 7cb7e73a-56e0-4226-b453-ed9ec86cc38f Mar 7 15:14:39 unRAID emhttpd: cache TotDevices: 2 Mar 7 15:14:39 unRAID emhttpd: cache NumDevices: 2 Mar 7 15:14:39 unRAID emhttpd: cache NumFound: 2 Mar 7 15:14:39 unRAID emhttpd: cache NumMissing: 0 Mar 7 15:14:39 unRAID emhttpd: cache NumMisplaced: 0 Mar 7 15:14:39 unRAID emhttpd: cache NumExtra: 0 Mar 7 15:14:39 unRAID emhttpd: cache LuksState: 0 Mar 7 15:14:39 unRAID emhttpd: shcmd (208): mount -t btrfs -o noatime,nodiratime -U 7cb7e73a-56e0-4226-b453-ed9ec86cc38f /mnt/cache Mar 7 15:14:39 unRAID kernel: BTRFS info (device sdh1): using free space tree Mar 7 15:14:39 unRAID kernel: BTRFS info (device sdh1): has skinny extents Mar 7 15:14:56 unRAID emhttpd: shcmd (209): /sbin/btrfs filesystem resize 1:max /mnt/cache Mar 7 15:14:56 unRAID root: Resize '/mnt/cache' of '1:max' Mar 7 15:14:56 unRAID kernel: BTRFS info (device sdh1): resizing devid 1 Mar 7 15:14:56 unRAID kernel: BTRFS info (device sdh1): new size for /dev/sdh1 is 3000592928768 Mar 7 15:14:56 unRAID emhttpd: shcmd (210): /sbin/btrfs filesystem resize 2:max /mnt/cache Mar 7 15:14:56 unRAID root: Resize '/mnt/cache' of '2:max' Mar 7 15:14:56 unRAID kernel: BTRFS info (device sdh1): resizing devid 2 Mar 7 15:14:56 unRAID kernel: BTRFS info (device sdh1): new size for /dev/sde1 is 3000592928768 Mar 7 15:14:56 unRAID emhttpd: shcmd (211): sync Mar 7 15:14:56 unRAID emhttpd: shcmd (212): mkdir /mnt/user0 Mar 7 15:14:56 unRAID emhttpd: shcmd (213): /usr/local/sbin/shfs /mnt/user0 -disks 14 -o noatime,allow_other |& logger Mar 7 15:14:56 unRAID shfs: use_ino: 1 Mar 7 15:14:56 unRAID shfs: direct_io: 0 Mar 7 15:14:56 unRAID emhttpd: shcmd (214): mkdir /mnt/user Mar 7 15:14:56 unRAID emhttpd: shcmd (215): /usr/local/sbin/shfs /mnt/user -disks 15 2048000000 -o noatime,allow_other -o remember=0 |& logger Mar 7 15:14:56 unRAID shfs: use_ino: 1 Mar 7 15:14:56 unRAID shfs: direct_io: 0 Mar 7 15:14:57 unRAID emhttpd: shcmd (217): /usr/local/sbin/update_cron Mar 7 15:14:57 unRAID root: Delaying execution of fix common problems scan for 10 minutes Mar 7 15:14:57 unRAID unassigned.devices: Mounting 'Auto Mount' Devices... Mar 7 15:14:57 unRAID emhttpd: Starting services... Mar 7 15:14:57 unRAID emhttpd: shcmd (220): /etc/rc.d/rc.samba restart Mar 7 15:14:59 unRAID root: Starting Samba: /usr/sbin/smbd -D Mar 7 15:15:00 unRAID root: /usr/sbin/nmbd -D Mar 7 15:15:00 unRAID root: /usr/sbin/wsdd Mar 7 15:15:00 unRAID root: /usr/sbin/winbindd -D Mar 7 15:15:00 unRAID emhttpd: shcmd (234): /usr/local/sbin/mount_image '/mnt/cache/system/docker/docker.img' /var/lib/docker 40 Mar 7 15:15:00 unRAID kernel: BTRFS: device fsid 1e042287-9021-48d2-8ad1-772169654339 devid 1 transid 1747553 /dev/loop2 Mar 7 15:15:00 unRAID kernel: BTRFS info (device loop2): using free space tree Mar 7 15:15:00 unRAID kernel: BTRFS info (device loop2): has skinny extents Mar 7 15:15:00 unRAID root: Resize '/var/lib/docker' of 'max' Mar 7 15:15:00 unRAID kernel: BTRFS info (device loop2): new size for /dev/loop2 is 42949672960 Mar 7 15:15:00 unRAID emhttpd: shcmd (236): /etc/rc.d/rc.docker start Mar 7 15:15:00 unRAID root: starting dockerd ... Mar 7 15:15:04 unRAID avahi-daemon[10987]: Joining mDNS multicast group on interface br-4ead1d45ff54.IPv4 with address 172.18.0.1. Mar 7 15:15:04 unRAID avahi-daemon[10987]: New relevant interface br-4ead1d45ff54.IPv4 for mDNS. Mar 7 15:15:04 unRAID avahi-daemon[10987]: Registering new address record for 172.18.0.1 on br-4ead1d45ff54.IPv4. Mar 7 15:15:04 unRAID kernel: IPv6: ADDRCONF(NETDEV_UP): br-4ead1d45ff54: link is not ready Mar 7 15:15:04 unRAID avahi-daemon[10987]: Joining mDNS multicast group on interface br-66b05052a9b2.IPv4 with address 192.168.240.1. Mar 7 15:15:04 unRAID avahi-daemon[10987]: New relevant interface br-66b05052a9b2.IPv4 for mDNS. Mar 7 15:15:04 unRAID avahi-daemon[10987]: Registering new address record for 192.168.240.1 on br-66b05052a9b2.IPv4. Mar 7 15:15:04 unRAID kernel: IPv6: ADDRCONF(NETDEV_UP): br-66b05052a9b2: link is not ready Mar 7 15:15:04 unRAID avahi-daemon[10987]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Mar 7 15:15:04 unRAID avahi-daemon[10987]: New relevant interface docker0.IPv4 for mDNS. Mar 7 15:15:04 unRAID avahi-daemon[10987]: Registering new address record for 172.17.0.1 on docker0.IPv4. Mar 7 15:15:04 unRAID kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready Mar 7 15:15:09 unRAID rc.docker: b1f70fe360063b35c8f89ccb8a5befd5f30feb5c090801074f6f4ddcbd41b28f Mar 7 15:15:11 unRAID emhttpd: shcmd (250): /usr/local/sbin/mount_image '/mnt/cache/system/libvirt/libvirt.img' /etc/libvirt 1 Mar 7 15:15:11 unRAID kernel: BTRFS: device fsid bc304288-554a-4fd8-a63c-b4a0a37f5e68 devid 1 transid 262 /dev/loop3 Mar 7 15:15:11 unRAID kernel: BTRFS info (device loop3): using free space tree Mar 7 15:15:11 unRAID kernel: BTRFS info (device loop3): has skinny extents Mar 7 15:15:11 unRAID root: Resize '/etc/libvirt' of 'max' Mar 7 15:15:11 unRAID kernel: BTRFS info (device loop3): new size for /dev/loop3 is 1073741824 Mar 7 15:15:11 unRAID emhttpd: shcmd (252): /etc/rc.d/rc.libvirt start Mar 7 15:15:11 unRAID root: Starting virtlockd... Mar 7 15:15:11 unRAID root: Starting virtlogd... Mar 7 15:15:11 unRAID root: Starting libvirtd... Mar 7 15:15:11 unRAID kernel: tun: Universal TUN/TAP device driver, 1.6 Mar 7 15:15:11 unRAID kernel: virbr0: port 1(virbr0-nic) entered blocking state Mar 7 15:15:11 unRAID kernel: virbr0: port 1(virbr0-nic) entered disabled state Mar 7 15:15:11 unRAID kernel: device virbr0-nic entered promiscuous mode Mar 7 15:15:11 unRAID emhttpd: nothing to sync Mar 7 15:15:11 unRAID kernel: bond0: link status definitely down for interface eth0, disabling it Mar 7 15:15:11 unRAID kernel: bond0: making interface eth1 the new active one Mar 7 15:15:11 unRAID kernel: device eth0 left promiscuous mode Mar 7 15:15:11 unRAID kernel: device eth1 entered promiscuous mode Mar 7 15:15:11 unRAID avahi-daemon[10987]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Mar 7 15:15:11 unRAID avahi-daemon[10987]: New relevant interface virbr0.IPv4 for mDNS. Mar 7 15:15:11 unRAID avahi-daemon[10987]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Mar 7 15:15:11 unRAID kernel: virbr0: port 1(virbr0-nic) entered blocking state Mar 7 15:15:11 unRAID kernel: virbr0: port 1(virbr0-nic) entered listening state Mar 7 15:15:11 unRAID dnsmasq[14786]: started, version 2.80 cachesize 150 Mar 7 15:15:11 unRAID dnsmasq[14786]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify dumpfile Mar 7 15:15:11 unRAID dnsmasq-dhcp[14786]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Mar 7 15:15:11 unRAID dnsmasq-dhcp[14786]: DHCP, sockets bound exclusively to interface virbr0 Mar 7 15:15:11 unRAID dnsmasq[14786]: reading /etc/resolv.conf Mar 7 15:15:11 unRAID dnsmasq[14786]: using nameserver 8.8.8.8#53 Mar 7 15:15:11 unRAID dnsmasq[14786]: using nameserver 8.8.4.4#53 Mar 7 15:15:11 unRAID dnsmasq[14786]: read /etc/hosts - 2 addresses Mar 7 15:15:11 unRAID dnsmasq[14786]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Mar 7 15:15:11 unRAID dnsmasq-dhcp[14786]: read /var/lib/libvirt/dnsmasq/default.hostsfile Mar 7 15:15:11 unRAID kernel: virbr0: port 1(virbr0-nic) entered disabled state Mar 7 15:15:11 unRAID kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. Mar 7 15:15:12 unRAID tips.and.tweaks: Tweaks Applied Mar 7 15:15:12 unRAID unassigned.devices: Mounting 'Auto Mount' Remote Shares... Mar 7 15:15:12 unRAID sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/bash -c /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 Mar 7 15:15:13 unRAID kernel: br0: port 2(vnet0) entered blocking state Mar 7 15:15:13 unRAID kernel: br0: port 2(vnet0) entered disabled state Mar 7 15:15:13 unRAID kernel: device vnet0 entered promiscuous mode Mar 7 15:15:13 unRAID kernel: br0: port 2(vnet0) entered blocking state Mar 7 15:15:13 unRAID kernel: br0: port 2(vnet0) entered forwarding state Mar 7 15:15:14 unRAID kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Mar 7 15:15:14 unRAID kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex Mar 7 15:15:15 unRAID avahi-daemon[10987]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe00:f65e. Mar 7 15:15:15 unRAID avahi-daemon[10987]: New relevant interface vnet0.IPv6 for mDNS. Mar 7 15:15:15 unRAID avahi-daemon[10987]: Registering new address record for fe80::fc54:ff:fe00:f65e on vnet0.*. Mar 7 15:16:20 unRAID ntpd[1875]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Mar 7 15:17:13 unRAID unassigned.devices: Cannot 'Auto Mount' Remote Shares. Network not available! Mar 7 15:18:16 unRAID login[10849]: ROOT LOGIN on '/dev/tty1' What the heck is happening?
  10. I am working my way towards upgrading from 6.8 to 6.10. As part of that I needed to update a few settings on my Seagate drives, which required a reboot. I made the changes and rebooted, but the server didn't come back right away. I later learned it was because I left a second USB drive plugged in and it messed up the boot order. I removed that USB, rebooted and the server came up as expected. I then verified the changes using the SeaChest tools and rebooted again. This is when it all went sideways. Everything comes up fine, but I have no network access. The /boot/config/network.cfg matches my previously backed up config (the CLI shows the correct address) I checked syslog and didn't see anything glaring. I pulled the link the syslog shows it going down - so the NIC isn't dead. I deleted /boot/config/network.cfg and rebooted, it did not re-create the file I rebooted again into GUI mode and entered in my static IP in the GUI and rebooted again for the settings to apply. No luck. This is the diagnostics for today from the USB from the last reboot. I am going crazy. This is so simple. Really makes my nervous that a simple reboot caused this much of an issue. What am I missing. I am beyond frustrated with something so simple. unraid-diagnostics-20230307-1115.zip unraid-diagnostics-20230307-1406.zip unraid-diagnostics-20230307-1451.zip
  11. ati

    RSYNC woes?

    Yep. Doesn't show anything more than the verbose output. Actually less. It was only a list of files transferred. It just stopped at the file before the one RSYNC hung on. 2023/02/12 22:28:04 [13522] >f..tpog... Phone Pictures/IMG_20200220_055619.jpg 2023/02/12 22:28:04 [13522] >f..tpog... Phone Pictures/IMG_20200221_073231.jpg 2023/02/12 22:28:04 [13522] >f..tpog... Phone Pictures/IMG_20200221_122321.jpg 2023/02/12 22:28:04 [13522] >f..tpog... Phone Pictures/IMG_20200221_124635.jpg 2023/02/12 22:28:04 [13522] >f..tpog... Phone Pictures/IMG_20200222_120952.jpg 2023/02/13 07:38:57 [13522] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(642) [sender=3.1.3]
  12. ati

    RSYNC woes?

    I am backing up one of my folders on my unRAID server to a directly attached drive via the Unassigned Disks plugin. The folder contains a bunch of family documents (PDFs, pictures, family videos, etc.) about 1.2TB in total. In the past I have used RSYNC and it has worked well. This is what I ran this time: rsync -avh --info=progress2 --partial --log-file=rsynclog.log /mnt/user/Documents/ /mnt/disks/external/documents_backup_2023-02-12/ RSYNC was copying just as I expected until it reached a subfolder where I backup my cellphone pictures every few weeks. It hung on a single picture (roughly 5MB). I manually moved that picture and re-ran RSYNC and it hung again on the next picture. At this point I wanted to finish backing up everything else and ran this: rsync -avh --info=progress2 --partial --exclude '/Phone Pictures' /mnt/user/Documents/ /mnt/disks/external/documents_backup_2023-02-12/ That command ran just fine and finished everything else. I then went back and tried to just RSYNC the 'Phone Pictures' directory and it kept hanging. I used logging and verbose mode and didn't get anything useful, just stopped mid transfer for over an hour. If I re-ran it again it would stop on the exact same file too. Until I manually moved it and it would hang on the next file. I eventually gave up and ran this: cp -R /mnt/user/Documents/Phone\ Pictures /mnt/disks/external/documents_backup_2023-02-12/ That ran just fine and I verified the files were all transferred. I have never had issues like this with RSYNC in the past and I am not experienced enough with it to know how to properly troubleshoot. Is there anything I can do to provide more logging? Or any ideas what the cause might be? I was hoping to try and automate this backup to run once every few months. Thanks.
  13. Is there anyway to update Docker without updating unRAID? I after a few attempts at upgrading that produced undesirable issues I have rolled back. If not, what is the latest version of the container I can run?
  14. I am waiting as well, and from what I can tell this issue will not be fixed by LimeTech. I think if we want to move on from 6.8.x to anything newer you'll have to run through the above outlined steps. I am still holding out for something, but again, I'm not holding my breath. What frustrates me the most is this was working in 6.8.xx and not in 6.9 and onwards, so it is something they could potentially address.
  15. Well it is working again. I waited a day and then I was able to connect again. No clue. Regardless, no settings changes, just was a little more patient. Maybe it was a cache issue with my browser or something.