-
Docker service failure, forcing RO
I ended up copying over my entire appdata do one of my array drives and reformatting my cache disk to XFS since I had only a single cache drive. This seems to have worked and I have not seen any issue thus far.
-
nurollinsiii41 started following [Support] binhex - DelugeVPN and Docker service failure, forcing RO
-
Docker service failure, forcing RO
Hello, I am dealing with an issue of docker failures that result in forcing my docker image to RO. Attached are my diagnostics and a quick snippit of the error that persists. Feb 17 16:51:16 Tower kernel: docker0: port 12(veth18a0932) entered disabled state Feb 17 16:51:16 Tower kernel: veth18a0932: entered allmulticast mode Feb 17 16:51:16 Tower kernel: veth18a0932: entered promiscuous mode Feb 17 16:51:17 Tower kernel: eth0: renamed from vethc33fd36 Feb 17 16:51:17 Tower kernel: docker0: port 12(veth18a0932) entered blocking state Feb 17 16:51:17 Tower kernel: docker0: port 12(veth18a0932) entered forwarding state Feb 17 16:51:39 Tower kernel: BTRFS warning (device sdi1): checksum verify failed on logical 2769047846912 mirror 1 wanted 0xb6e90821 found 0x8278443c level 0 Feb 17 16:51:39 Tower kernel: BTRFS warning (device sdi1): checksum verify failed on logical 2769047846912 mirror 2 wanted 0xb6e90821 found 0x8278443c level 0 Feb 17 16:51:39 Tower kernel: BTRFS error (device sdi1: state A): Transaction aborted (error -5) Feb 17 16:51:39 Tower kernel: BTRFS: error (device sdi1: state A) in btrfs_finish_one_ordered:3125: errno=-5 IO failure Feb 17 16:51:39 Tower kernel: BTRFS info (device sdi1: state EA): forced readonly Feb 17 16:51:39 Tower kernel: traps: postgres[4000535] general protection fault ip:149cf1c4750f sp:7ffcdadab110 error:0 in libc.so.6[149cf1c47000+155000] Feb 17 16:51:39 Tower kernel: loop: Write error at byte offset 23705706496, length 4096. Feb 17 16:51:39 Tower kernel: I/O error, dev loop2, sector 46300208 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 2 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Feb 17 16:51:39 Tower kernel: loop: Write error at byte offset 20294074368, length 4096. Feb 17 16:51:39 Tower kernel: I/O error, dev loop2, sector 39636864 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Feb 17 16:51:39 Tower kernel: loop: Write error at byte offset 20326412288, length 4096. Feb 17 16:51:39 Tower kernel: I/O error, dev loop2, sector 39700024 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Feb 17 16:51:39 Tower kernel: loop: Write error at byte offset 23705706496, length 4096. Feb 17 16:51:39 Tower kernel: loop: Write error at byte offset 23705706496, length 4096. Feb 17 16:51:39 Tower kernel: I/O error, dev loop2, sector 46300208 op 0x1:(WRITE) flags 0x800 phys_seg 4 prio class 2 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0 Feb 17 16:51:39 Tower kernel: docker0: port 10(veth2bb4785) entered disabled state Feb 17 16:51:39 Tower kernel: veth2f6799a: renamed from eth0 Feb 17 16:51:39 Tower kernel: loop: Write error at byte offset 23705706496, length 4096. Feb 17 16:51:39 Tower kernel: loop: Write error at byte offset 23705706496, length 4096. Feb 17 16:51:39 Tower kernel: I/O error, dev loop2, sector 46300208 op 0x1:(WRITE) flags 0x800 phys_seg 4 prio class 2 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0 Feb 17 16:51:39 Tower kernel: loop: Write error at byte offset 23705706496, length 4096. Feb 17 16:51:39 Tower kernel: loop: Write error at byte offset 23705706496, length 4096. Feb 17 16:51:39 Tower kernel: I/O error, dev loop2, sector 46300208 op 0x1:(WRITE) flags 0x800 phys_seg 4 prio class 2 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 Feb 17 16:51:39 Tower kernel: loop: Write error at byte offset 1435746304, length 4096. Feb 17 16:51:39 Tower kernel: I/O error, dev loop2, sector 2804192 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Feb 17 16:51:39 Tower kernel: I/O error, dev loop2, sector 707040 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0 Feb 17 16:51:39 Tower kernel: I/O error, dev loop2, sector 2804160 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Feb 17 16:51:39 Tower kernel: I/O error, dev loop2, sector 707008 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Feb 17 16:51:39 Tower kernel: BTRFS error (device loop2: state AL): Transaction aborted (error -5) Feb 17 16:51:39 Tower kernel: BTRFS: error (device loop2: state AL) in free_log_tree:3227: errno=-5 IO failure Feb 17 16:51:39 Tower kernel: BTRFS info (device loop2: state EAL): forced readonly Feb 17 16:51:39 Tower kernel: BTRFS warning (device loop2: state EAL): Skipping commit of aborted transaction. Feb 17 16:51:39 Tower kernel: BTRFS: error (device loop2: state EAL) in cleanup_transaction:2002: errno=-5 IO failure Feb 17 16:53:13 Tower kernel: docker0: port 12(veth18a0932) entered disabled state Feb 17 16:53:13 Tower kernel: vethc33fd36: renamed from eth0 Feb 17 16:56:00 Tower ool www[4006948]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply' Feb 17 16:56:00 Tower emhttpd: Starting services... Feb 17 16:56:00 Tower emhttpd: shcmd (168): /etc/rc.d/rc.samba reload Feb 17 16:56:01 Tower emhttpd: shcmd (171): exportfs -ra Feb 17 16:56:01 Tower emhttpd: shcmd (173): /etc/rc.d/rc.avahidaemon reload Feb 17 16:56:01 Tower avahi-daemon[2156]: Got SIGHUP, reloading. Feb 17 16:56:01 Tower emhttpd: shcmd (176): /etc/rc.d/rc.docker stop Feb 17 16:56:01 Tower rc.docker: Stopping containers... tower-diagnostics-20250217-1904.zip
-
Docker and BTRFS problems since update to v7
I am not having this exact error, but one that is similar. I notice that my docker containers stop working after a while, no matter if I try to stop the docker service and restart it, it never works again until I reboot my machine. When I went to check my syslog I saw it filled with the error like the below. Tower kernel: BTRFS error (device loop2: state EA): level verify failed on logical 46560034816 mirror 1 wanted 1 found 0 Pasted are my diagnostics to help troubleshoot. tower-diagnostics-20250114-1907.zip
-
docker.img' is in-use, cannot mount
just tried the uninstall and re-install to no avail. Same logs as mentioned above in my example. I’m on 7.0.0 beta if that makes a difference
-
docker.img' is in-use, cannot mount
I fear I may be having similar issues, and they are progressively getting worse. Issues I see consistently; 1. Appdata not backing up successfully 2. Intermittent Mover issues where the mover doesn't do anything 3. Docker crashing 4. Entire Unraid system unresponsive to pings / webgui, hard reset fixes Mover example: mvlogger: Log Level: 1 mvlogger: *********************************MOVER -SHARE- START******************************* mvlogger: Tue Dec 31 06:18:57 PST 2024 mvlogger: Share supplied TVShows Sharecfg: /boot/config/shares/TVShows.cfg mvlogger: Cache Pool Name: cache mvlogger: Share Path: /mnt/cache/TVShows mvlogger: Complete Mover Command: find "/mnt/cache/TVShows" -depth | /usr/local/sbin/move -d 1 mvlogger: Tue Dec 31 06:18:57 PST 2024 mvlogger: ********************************Mover Finished***************************** tower-diagnostics-20241231-0829.zip
-
[Support] binhex - DelugeVPN
I'm at a loss. I'm not sure where to go. Deluge appears to be up w/ a IP via PIA. But I can't hit the WebUI, nor can I sent a torrent to it, it fails immediately. This happened out of nowhere so I'm not sure what has changed. Any help would be appreciated. **UPDATE** it worked for a few min, i turned off debugging, and it stopped working again. logs.txt
nurollinsiii41
Members
-
Joined
-
Last visited