Jaybau

How do I prevent czkawka from flagging radarr/sonarr/*arr files as duplicates when do the hash check method? I also have a problem with duplicate *arr hardlinks on multiple drives, caused by Unbalanced (which moves file via drive, not share).

The script is able to tell me the duplicate files at the share level, but can the script tell me which drives? I need to know the drives I can delete the duplicated files from. Thanks.

I ran into a problem where Unbalanced didn't delete/remove the source file/folders. Since I don't know anything else to do, I naturally retried moving the folders again, multiple time. Now I'm left with duplicates scattered among a lot of drives. I didn't start to notice this problem until I noticed my drives filling up faster than I before I started. Is there an easy and programmatic method to cleanup the scattered duplicates?

Same problem. In the Unraid notification settings, why isn't there an option for "OAuth2" authentication method?

Is the SeaFile template correct? I didn't see a volume/path to store user data versus the configuration path.

Is the Backrest template missing "MY-BACKUP-DATA:/userdata"? Where do I specify the source data path?

Should the container's console be accessbile via Unraid? When I click "console" from the menu, the console window popsup, then closes immediately. Within the split second, I do not see any text or potential message. Nothing shows up in the Unraid syslog either.

I'm getting the error message: COPY failed: file not found in build context or excluded by .dockerignore: stat test.txt: file does not exist Step 1/2 : FROM alpine:latest ---> 91ef0af61f39 Step 2/2 : COPY test.txt /tmp COPY failed: file not found in build context or excluded by .dockerignore: stat test.txt: file does not exist The file "test.txt" is added to the build context: What are some troubleshooting steps? How can I verify the file was uploaded? Thank you.

Gathered a log for the current "hang"... I cannot access Unraid WebUI. Cannot access via SSH. Cannot access any dockers. The problem occurs around Oct 16 17:38:12. <6>Oct 16 17:27:18 Tower kernel: docker0: port 5(veth34567ba) entered disabled state <6>Oct 16 17:27:18 Tower kernel: device veth34567ba entered promiscuous mode <6>Oct 16 17:27:25 Tower kernel: eth0: renamed from veth9e3327d <6>Oct 16 17:27:25 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth34567ba: link becomes ready <6>Oct 16 17:27:25 Tower kernel: docker0: port 5(veth34567ba) entered blocking state <6>Oct 16 17:27:25 Tower kernel: docker0: port 5(veth34567ba) entered forwarding state <6>Oct 16 17:27:27 Tower kernel: docker0: port 5(veth34567ba) entered disabled state <6>Oct 16 17:27:27 Tower kernel: veth9e3327d: renamed from eth0 <6>Oct 16 17:27:27 Tower kernel: docker0: port 5(veth34567ba) entered disabled state <6>Oct 16 17:27:27 Tower kernel: device veth34567ba left promiscuous mode <6>Oct 16 17:27:27 Tower kernel: docker0: port 5(veth34567ba) entered disabled state <6>Oct 16 17:28:28 Tower kernel: docker0: port 5(vethaaffec7) entered blocking state <6>Oct 16 17:28:28 Tower kernel: docker0: port 5(vethaaffec7) entered disabled state <6>Oct 16 17:28:28 Tower kernel: device vethaaffec7 entered promiscuous mode <6>Oct 16 17:28:36 Tower kernel: eth0: renamed from vethb77cf64 <6>Oct 16 17:28:36 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethaaffec7: link becomes ready <6>Oct 16 17:28:36 Tower kernel: docker0: port 5(vethaaffec7) entered blocking state <6>Oct 16 17:28:36 Tower kernel: docker0: port 5(vethaaffec7) entered forwarding state <6>Oct 16 17:28:38 Tower kernel: vethb77cf64: renamed from eth0 <6>Oct 16 17:28:38 Tower kernel: docker0: port 5(vethaaffec7) entered disabled state <6>Oct 16 17:28:38 Tower kernel: docker0: port 5(vethaaffec7) entered disabled state <6>Oct 16 17:28:38 Tower kernel: device vethaaffec7 left promiscuous mode <6>Oct 16 17:28:38 Tower kernel: docker0: port 5(vethaaffec7) entered disabled state <4>Oct 16 17:38:12 Tower kernel: md: sync done. time=89664sec <4>Oct 16 17:38:17 Tower kernel: md: recovery thread: exit status: 0 <35>Oct 16 19:22:10 Tower sshd[11363]: error: beginning MaxStartups throttling There does appear to be activity in the log, so the server is not dead. During this time, parity is being validated (because of a previous hang which resulted in an unclean shutdown), but I cannot see messages. I also have BTRFS activity for moving data off one of my drives (I need to free-up a drive bay to replace with a larger drive). This is not the unraid array, but a separate BTRFS pool of old drives). The current hanging problem happened before, so I don't think this is causing a problem. I can still see BTRFS move messages in the syslog, so that's how I know Unraid is partially working. This event appears to be the only thing working right now. --- just as I was writing this, the BTRFS activity completed (good news), and I can see it has completed in the original SSH console that I issued the command However, the SSH console is not responsive to my keyboard input, so I cannot do anything else. Unfortunately WebUI doesn't work, nor does SSH. The console allows me to type in the username login, but then timeouts with a timeout message, and I can't type a password or login through the console. So again, there's some sort of activity going on, but something appears to be not allowing logins or the server to make connections. I'm curious if one of my docker containers is taking down the OS. I don't know if that can happen, or figure out which container. syslog.txt

What is the easiest method to determine which docker container is frequently restarting?

In Unraid I configured the syslog to output to a remote syslog server listening for syslog messages. I'm not receiving syslog messages on the remote syslog server/listener. Is there a command to send test messages from Unraid to the remote syslog server? Other options to test/debug the communication from Unraid to the remote syslog server? Thank you. Notes: SOLUTION: logger -n 192.168.1.5 -P 514 test2 ALTERNATIVE: Needed to install NerdTools Need to install netcat from NerdTools. Use command: echo "Test message." | netcat -w1 -u 192.168.1.5 514

I am experiencing multiple Unraid hanging, no response, unresponsive. No error messages printed to console. Cannot log into console either. I have attached three logs. I have since rebooted and attached the diagnostic logs. Thank you. tower-diagnostics-20241015-1640.zip tower-diagnostics-20241013-2009.zip tower-diagnostics-20241012-2056.zip

On machines within Tailscale, I can resolve hostnames. On a machine outside of Tailscale, I cannot resolve hostnames. I setup subnet using the IP address range of my local LAN (without Tailscale): My goal is to get the machine outside of Tailscale to resolve the hosname "tower" to 192.168.1.7. Something similar to what SMB was doing for me before I disabled SMB.

What about for machines where I do not have (cannot) Tailscale installed?

How do I access Unraid via hostname on my LAN? Since I installed Tailscale, and Tailscale didn't like SMB, I disabled SMB. I can no longer reach "http://tower" (because SMB is disabled). I can reach "http://192.168.1.7". Thank you.

I'm concerned about a security vulnerability because Vaultwarden requires HTTPS, and the instructions tell me to use a reverse proxy. Using a reverse proxy opens up my password vault to everyone on the internet. Is there something I can do/use to limit my security risk? I want to use a selfhosted password storage solution to store/access my passwords from my phone, laptop, desktop devices. Thank you.

Correct, docker service is disabled.

When running Mover, Mover stops working, hangs, no response, when trying to move: prw-r--r-- 1 nobody users 0 Apr 18 19:04 /mnt/cache/system/docker/volumes/0142d8f9badc153130ee66735cb5c7fb3f96ae665fc5bdf5e34b790b95a75c06/_data/services/nginx/supervise/control| Information: I have my docker folder configured to be located: /mnt/cache/system/docker I am moving files from cache to array in order to replace my cache drive. The file being moved, "control", appears to be a "FIFO" file, which might be the cause. Cannot stop the Mover. Cannot stop the Array. Requires a reboot. Hanging occurred on multiple "control" "FIFO" files, after rebooting and restarting the Mover. Diagnostics attached. Workaround: Manually deleted the "control" files, but hope that doesn't create problems for those docker containers. tower-diagnostics-20240817-0643.zip

Thank you! I think that's the problem. My cache started to fill up (probably because I wasn't running the mover frequently enough or too large of a file), so then the mover decided to move my System share to the array to try and make more room. And my System share is huge! And now that the mover moved all the files it should have moved, the mover is now moving the System share from the array back to the cache. Thank you for pointing me in the right direction.

Is "mover" supposed to be moving everything from my /mnt/cache/system folder off the cache onto the /mnt/user0/? Aug 15 13:00:00 Tower move: Moving "/mnt/cache/./system/docker/zfs/graph/4dd15260460199225bd2c1cb40588f4dddaa75e32cf4bde7772e996091a87004/opt/venv/lib/python3.12/site-packages/future/moves/collections.py" to /mnt/user0/ I also have a lot of files under zfs and containers. I also don't understand why /mnt/cache/./system/docker/zfs/graph is so lage. Thank you.

Would be better if it was on the "Docker Container" bar, next to "Basic View" or "Advanced View". Where it is at now is where I think of the Unraid system bar.

I had SWAG previously working, but something changed, and now I get an error message about "Permissions could not be set. This is probably because your volume mounts are remote or read-only." chown: cannot dereference '/config/keys/letsencrypt': No such file or directory find: /var/lib/letsencrypt: No such file or directory find: /var/log/letsencrypt: No such file or directory /etc/s6-overlay/s6-rc.d/init-certbot-config/run: line 372: 361 Illegal instruction certbot certonly --non-interactive --renew-by-default chown: cannot dereference '/config/keys/letsencrypt': No such file or directory find: /var/lib/letsencrypt: No such file or directory find: /var/log/letsencrypt: No such file or directory /etc/s6-overlay/s6-rc.d/init-certbot-config/run: line 372: 364 Illegal instruction certbot certonly --non-interactive --renew-by-default using keys found in /config/keys **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** **** The app may not work properly and we will not provide support for it. **** Variables set: PUID=99 PGID=100 TZ=America/Los_Angeles URL=<redacted> SUBDOMAINS= EXTRA_DOMAINS= ONLY_SUBDOMAINS=true VALIDATION=http CERTPROVIDER= DNSPLUGIN=duckdns [email protected] STAGING=false **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** **** The app may not work properly and we will not provide support for it. **** Using Let's Encrypt as the cert provider SUBDOMAINS entered, processing Sub-domains processed are: <redacted> E-mail address entered: [email protected] http validation is selected Generating new certificate ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container [migrations] started [migrations] 01-nginx-site-confs-default: skipped [migrations] done usermod: no changes ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support the app dev(s) visit: Certbot: https://supporters.eff.org/donate/support-work-on-certbot To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 99 User GID: 100 ─────────────────────────────────────── using keys found in /config/keys **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** **** The app may not work properly and we will not provide support for it. **** Variables set: PUID=99 PGID=100 TZ=America/Los_Angeles URL=<redacted> SUBDOMAINS= EXTRA_DOMAINS= ONLY_SUBDOMAINS=true VALIDATION=http CERTPROVIDER= DNSPLUGIN=duckdns [email protected] STAGING=false **** Permissions could not be set. This is probably because your volume mounts are remote or read-only. **** **** The app may not work properly and we will not provide support for it. **** Using Let's Encrypt as the cert provider SUBDOMAINS entered, processing Sub-domains processed are: <redacted> E-mail address entered: [email protected] http validation is selected Generating new certificate ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container Docker Config: docker run -d --name='swag' --net='proxynet' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="swag" -e 'URL'='<redacte>' -e 'VALIDATION'='http' -e 'SUBDOMAINS'='<redacted>' -e 'CERTPROVIDER'='' -e 'DNSPLUGIN'='duckdns' -e 'PROPAGATION'='' -e 'EMAIL'='[email protected]' -e 'ONLY_SUBDOMAINS'='true' -e 'EXTRA_DOMAINS'='' -e 'STAGING'='false' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver-ls-logo.png' -p '1443:443/tcp' -p '180:80/tcp' -v '/mnt/user/appdata/swag':'/config':'rw' --cap-add=NET_ADMIN 'lscr.io/linuxserver/swag' I also have my router ports forwarding 443 to 1443 and 80 to 180. Ideas of where to look for the problem?

Just went through the process (replacing smaller parity drive with larger parity drive, and then moving the old parity drive to data), and it was confusing and didn't go the way I wanted. I wanted the safest and easiest option. What I have right now is a full/clean parity sync, while the old parity is sitting unassigned. However, my array is online, so the old parity is obsolete. This doesn't sound like the safest, nor the easiest option. I thought I could do a parity copy. I thought Unraid would have something built-in to copy the parity bits from the smaller drive to the larger drive. If parity copy is not possible, then Unraid could do both Parity 1 and Parity 2. Then when Parity 2 is complete, remove Parity 1 and move drive to data; Parity 2 drive now becomes the Parity 1 drive. In the future I hope Unraid has scenario buttons that walk the user through the process for common different scenarios.

Should the FloodUI docker use PUID 99 and PGID 100 for safer security practice?

Finally got the mover to work. I'm using moving tuning plugin. To get this to work, I configured the "Mover Tuning - Share Settings". Mover Tuning Config (global): moverDisabled="no" moverNice="0" moverIO="-c 2 -n 0" threshold="0" age="no" sizef="no" sparsnessf="no" filelistf="yes" filetypesf="yes" filetypesv="*.duplicate,*parts,*.bak,*.qb!,*.tmp, .Recycle.Bin, /mnt/cache/media/.Recycle.Bin" parity="no" enableTurbo="no" logging="yes" force="no" ignoreHidden="no" beforeScript="" afterScript="" omovercfg="no" movenow="yes" testmode="no" filelistv="" Mover Tuning - Share Settings moverOverride="yes" age="no" sizef="no" sparsnessf="no" filelistf="no" filetypesf="no" ignoreHidden="no" omovercfg="no"