Kilrah

Might have done the opposite of what's needed. Redis needs to be running first, if it's not already available when paperless starts than consume won't work.

The plugin doesn't control the timeout so you'd still be likely to encounter the same issues outside of the backup scenario (shutdown, reboot, just manually stopping the container). Increase the global container stop timeout in Docker settings.

docker image prune -f -a will only delete really orphan images, not images that are used by a stopped container.

No, that wouldn't help, container being stopped is not enough, it has to be deleted to be able to remove the image. Orphan images will also appear if you change tags.

Sorry it was me, I forgot to delete the broken "latest" image before switching back to it so it reused the local one instead of pulling the new

Latest still broken for me. 2026-02-10 00:12:42.698 CET [106M] INFO: Parsed config file /etc/pihole/pihole.toml successfully 2026-02-10 00:12:42.698 CET [106M] INFO: PID file does not exist or not readable 2026-02-10 00:12:42.698 CET [106M] INFO: No other running FTL process found. 2026-02-10 00:12:42.698 CET [106M] WARNING: Insufficient permissions to set process priority to -10 (CAP_SYS_NICE required), process priority remains at 0 2026-02-10 00:12:42.700 CET [106M] INFO: PID of FTL process: 106 2026-02-10 00:12:42.702 CET [106M] INFO: listening on 0.0.0.0 port 53 2026-02-10 00:12:42.702 CET [106M] INFO: listening on :: port 53 2026-02-10 00:12:42.703 CET [106M] INFO: PID of FTL process: 106 2026-02-10 00:12:42.705 CET [106M] ERROR: SQLite3: recovered 325 frames from WAL file /etc/pihole/pihole-FTL.db-wal (283) 2026-02-10 00:12:42.705 CET [106M] INFO: Database version is 21 2026-02-10 00:12:42.720 CET [106M] INFO: Database successfully initialized 2026-02-10 00:12:43.472 CET [106M] INFO: Imported 54688 queries from the on-disk database (it has 1463656 rows) 2026-02-10 00:12:43.472 CET [106M] INFO: Parsing queries in database 2026-02-10 00:12:43.494 CET [106M] INFO: 10000 queries parsed... 2026-02-10 00:12:43.517 CET [106M] INFO: 20000 queries parsed... 2026-02-10 00:12:43.541 CET [106M] INFO: 30000 queries parsed... 2026-02-10 00:12:43.560 CET [106M] INFO: 40000 queries parsed... 2026-02-10 00:12:43.579 CET [106M] INFO: 50000 queries parsed... 2026-02-10 00:12:43.590 CET [106M] INFO: Imported 54688 queries from the long-term database 2026-02-10 00:12:43.590 CET [106M] INFO: -> Total DNS queries: 54688 2026-02-10 00:12:43.590 CET [106M] INFO: -> Cached DNS queries: 38195 2026-02-10 00:12:43.591 CET [106M] INFO: -> Forwarded DNS queries: 4786 2026-02-10 00:12:43.591 CET [106M] INFO: -> Blocked DNS queries: 10992 2026-02-10 00:12:43.591 CET [106M] INFO: -> Unknown DNS queries: 0 2026-02-10 00:12:43.591 CET [106M] INFO: -> Unique domains: 1621 2026-02-10 00:12:43.591 CET [106M] INFO: -> Unique clients: 19 2026-02-10 00:12:43.591 CET [106M] INFO: -> DNS cache records: 303 2026-02-10 00:12:43.591 CET [106M] INFO: -> Known forward destinations: 1 2026-02-10 00:12:43.699 CET [106M] WARNING: Insufficient permissions to set system time (CAP_SYS_TIME required), NTP client not available 2026-02-10 00:12:43.699 CET [106/T179] INFO: NTP server listening on 0.0.0.0:123 (IPv4) 2026-02-10 00:12:43.699 CET [106/T180] INFO: NTP server listening on :::123 (IPv6) 2026-02-10 00:12:43.699 CET [106M] INFO: FTL is running as user pihole (UID 1000) 2026-02-10 00:12:43.699 CET [106M] INFO: Reading certificate from /etc/pihole/tls.pem ... 2026-02-10 00:12:43.699 CET [106M] INFO: Using SSL/TLS certificate file /etc/pihole/tls.pem 2026-02-10 00:12:43.700 CET [106M] INFO: Web server ports: 2026-02-10 00:12:43.700 CET [106M] INFO: - 0.0.0.0:80 (HTTP, IPv4, optional, OK) 2026-02-10 00:12:43.700 CET [106M] INFO: - 0.0.0.0:443 (HTTPS, IPv4, optional, OK) 2026-02-10 00:12:43.700 CET [106M] INFO: - [::]:80 (HTTP, IPv6, optional, OK) 2026-02-10 00:12:43.700 CET [106M] INFO: - [::]:443 (HTTPS, IPv6, optional, OK) 2026-02-10 00:12:43.700 CET [106M] INFO: Restored 0 API sessions from the database 2026-02-10 00:12:43.704 CET [106M] INFO: Blocking status is enabled 2026-02-10 00:12:43.832 CET [106/T181] INFO: Compiled 0 allow and 2 deny regex for 19 clients in 32.2 msec 2026-02-10 00:12:44.954 CET [232/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:44.954 CET [233/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:44.957 CET [234/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:44.959 CET [235/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:45.615 CET [236/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:45.618 CET [237/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:45.618 CET [238/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:45.619 CET [239/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:45.619 CET [240/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:45.619 CET [241/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:45.623 CET [242/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused) 2026-02-10 00:12:45.626 CET [243/F106] WARNING: Connection error (127.1.1.1#5153): TCP connection failed (Connection refused)

[Template only, I am not the container author/maintainer] Project: https://github.com/arpanghosh8453/open-dronelog A high-performance application for analyzing DJI drone flight logs.

Looks like they changed some things and it's a pain now, try removing the "-u 99:100" in Extra parameters in Advanced view.

Are you by any chance doing 2 docker operations at the same time? That'll do it for me. Possibly a container restarting in a loop in the background? I've had this happen several times but not consistently. Seemed it might be dependent on where I triggered the operation from (dashboard vs Docker page vs CA), some of which have slightly different layouts/behaviors...

Today's update's broken, this may be it: [23:22:02.091486] STUBBY: Stubby version: Stubby 0.4.3 You did not specify any valid additional argument to the cloudflared tunnel command. If you are trying to run a Quick Tunnel then you need to explicitly pass the --url flag. Eg. cloudflared tunnel --url localhost:8080/. Please note that Quick Tunnels are meant to be ephemeral and should only be used for testing purposes. For production usage, we recommend creating Named Tunnels. (https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/tunnel-guide/)Had to revert to previous "2025.11.1-z02" tag.

Well it is not here.

See this plugin

Then it problably already had a partition that should have been deleted before adding to array.

You did NOT add the image extensions to the editor.cfg file, right?

How much RAM do you have? How much free for the root in the output of df -h? The flash backup is created by the system in the rootfs.

That might be browser dependent. Images are fine here on Chrome/win but not video.

Edit /boot/config/go and comment out everything after #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp If that helps you can try putting the rest back from top to bottom... My guess is it's this # Start the Monitor Service cp -r /boot/config/monitor/ /usr/local/sbin/monitor/ chmod 777 /usr/local/sbin/monitor/monitor nohup /usr/local/sbin/monitor/monitor >/dev/null 2>&1 &I.e. they added some kind of monitoring service to check drive status and display it on that pretty little LCD, but without considering the implications / being careful not to wake up drives for it. If you can confirm it's fine with only the first 3 lines of the file then contact Linc and tell them about the problem, it'll be on their side.

No, perfectly normal. There's a lot of legacy protocol encapsulation in most current interfaces.

Which Lincplus system is that? The go file customizations likely come from them. It seems there's a "monitor" thing so maybe it's something they added that's not part of stock Unraid that does it.

AFAIK it's known that the sensor in some WD He drives is unreliable, and there have been people using some with "failing" levels for years more with no problem.

Some ways HDDs fail cause the entire machine to freeze/hang between operations on basically any OS, not much can be done about that. Would try doing that recovery on another machine so you don't bog down anything you're actually using.

Why would you need 2 in the first place?

Doesn't support ZFS native encryption either, right?

And what does that easybackup script do? Read it and figure out since it's likely it'd stop what it backs up, and coincidentally daily scripts run at 4:40 by default.

You have 2 vdevs already.