Hello eveyone, I need some help please.

 

Yesterday I updated from 7.1.1 to 7.1.2 and ever since my dockers don't start. When I go to Docker's tab I get the following message "Docker Service failed to start"

 

Ive tried to downgrade back to 7.1.1 but didn't resouve the issue and now I've returned to 7.1.2 version.

 

This is something that I'm not sure but going to Setting>Docker> The option "Docker vDisk location: /mnt/user/system/docker/docker.img"  which I think this is correct. I did a google search and someone said that it could been changed during the update but for my case I think its correct. However I noticed the option "Docker data-root: btfrs vDisk". I have 6 drives, 5 are set to xfs and cache to zfs. I tried to change that option " Docker data-root: " to " Directory" but didn't help... Ive returned to btfrs Vdisk.

 

Appreciate any help.

 

 

See the log I get

May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3486168 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709588, rd 0, flush 0, corrupt 0, gen 0
May 17 14:37:35 Tower kernel: loop: Write error at byte offset 1784922112, length 4096.
May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3486168 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709589, rd 0, flush 0, corrupt 0, gen 0
May 17 14:37:35 Tower kernel: loop: Write error at byte offset 1784922112, length 4096.
May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3486168 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709590, rd 0, flush 0, corrupt 0, gen 0
May 17 14:37:35 Tower kernel: loop: Write error at byte offset 1785462784, length 4096.
May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3487232 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709591, rd 0, flush 0, corrupt 0, gen 0
May 17 14:37:35 Tower kernel: loop: Write error at byte offset 1784922112, length 4096.
May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3486168 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709592, rd 0, flush 0, corrupt 0, gen 0
May 17 14:37:35 Tower kernel: loop: Write error at byte offset 1785479168, length 4096.
May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3487264 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709593, rd 0, flush 0, corrupt 0, gen 0
May 17 14:37:35 Tower kernel: Initializing XFRM netlink socket
May 17 14:38:10 Tower rc.docker: Docker daemon...  Failed.
May 17 14:38:10 Tower rc.docker: Starting network...
May 17 14:38:10 Tower rc.docker: Starting containers...
May 17 14:38:11 Tower emhttpd: shcmd (130): umount /var/lib/docker
May 17 14:38:11 Tower kernel: BTRFS info (device loop3): last unmount of filesystem 9b7a0bbc-ea2a-41d2-ad03-9577969188bc
May 17 14:41:14 Tower ool www[19022]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply'
May 17 14:41:14 Tower emhttpd: Starting services...
May 17 14:41:14 Tower emhttpd: shcmd (135): /etc/rc.d/rc.samba reload
May 17 14:41:15 Tower emhttpd: shcmd (139): /etc/rc.d/rc.avahidaemon reload
May 17 14:41:15 Tower avahi-daemon[11986]: Got SIGHUP, reloading.
May 17 14:41:15 Tower unassigned.devices: Updating share settings...
May 17 14:41:15 Tower unassigned.devices: Share settings updated.
May 17 14:41:37 Tower ool www[22621]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply'
May 17 14:41:37 Tower emhttpd: Starting services...
May 17 14:41:37 Tower emhttpd: shcmd (146): /etc/rc.d/rc.samba reload
May 17 14:41:37 Tower emhttpd: shcmd (150): /etc/rc.d/rc.avahidaemon reload
May 17 14:41:38 Tower avahi-daemon[11986]: Got SIGHUP, reloading.
May 17 14:41:38 Tower unassigned.devices: Updating share settings...
May 17 14:41:38 Tower unassigned.devices: Share settings updated.
May 17 14:41:38 Tower emhttpd: shcmd (160): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20
May 17 14:41:38 Tower kernel: loop3: detected capacity change from 0 to 41943040
May 17 14:41:38 Tower kernel: BTRFS: device fsid 9b7a0bbc-ea2a-41d2-ad03-9577969188bc devid 1 transid 1754631 /dev/loop3 (7:3) scanned by mount (22778)
May 17 14:41:38 Tower kernel: BTRFS info (device loop3): first mount of filesystem 9b7a0bbc-ea2a-41d2-ad03-9577969188bc
May 17 14:41:38 Tower kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm
May 17 14:41:38 Tower kernel: BTRFS info (device loop3): using free-space-tree
May 17 14:41:38 Tower kernel: BTRFS info (device loop3): bdev /dev/loop3 errs: wr 709737, rd 0, flush 0, corrupt 0, gen 0
May 17 14:41:38 Tower root: Resize device id 1 (/dev/loop3) from 20.00GiB to max
May 17 14:41:38 Tower emhttpd: shcmd (162): /etc/rc.d/rc.docker start
May 17 14:41:38 Tower rc.docker: Starting Docker daemon...
May 17 14:41:39 Tower kernel: lo_write_bvec: 144 callbacks suppressed
May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785466880, length 4096.
May 17 14:41:39 Tower kernel: blk_print_req_error: 42 callbacks suppressed
May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487232 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:41:39 Tower kernel: btrfs_dev_stat_inc_and_print: 144 callbacks suppressed
May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709738, rd 0, flush 0, corrupt 0, gen 0
May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785479168, length 4096.
May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487264 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709739, rd 0, flush 0, corrupt 0, gen 0
May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785470976, length 4096.
May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487248 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709740, rd 0, flush 0, corrupt 0, gen 0
May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785487360, length 4096.
May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487280 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709741, rd 0, flush 0, corrupt 0, gen 0
May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785466880, length 4096.
May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487232 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709742, rd 0, flush 0, corrupt 0, gen 0
May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785470976, length 4096.
May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487248 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709743, rd 0, flush 0, corrupt 0, gen 0
May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785466880, length 4096.
May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487232 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709744, rd 0, flush 0, corrupt 0, gen 0
May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785479168, length 4096.
May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487264 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709745, rd 0, flush 0, corrupt 0, gen 0
May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785487360, length 4096.
May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487280 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709746, rd 0, flush 0, corrupt 0, gen 0
May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785466880, length 4096.
May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487232 op 0x1:(WRITE) flags 0x800 phys_seg 3 prio class 0
May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709747, rd 0, flush 0, corrupt 0, gen 0
May 17 14:42:14 Tower rc.docker: Docker daemon...  Failed.
May 17 14:42:14 Tower rc.docker: Starting network...
May 17 14:42:14 Tower rc.docker: Starting containers...
May 17 14:42:15 Tower emhttpd: shcmd (164): umount /var/lib/docker
May 17 14:42:15 Tower kernel: BTRFS info (device loop3): last unmount of filesystem 9b7a0bbc-ea2a-41d2-ad03-9577969188bc
May 17 14:52:18 Tower emhttpd: spinning down /dev/sdd
May 17 14:52:18 Tower emhttpd: spinning down /dev/sde
May 17 14:52:18 Tower emhttpd: spinning down /dev/sdb
May 17 14:52:18 Tower emhttpd: spinning down /dev/sdc
May 17 14:56:49 Tower emhttpd: read SMART /dev/sdd

 

Also attached my Diagnostics

tower-diagnostics-20250517-1507.zip

Edited May 17, 20251 yr by Kavian
Added diagnostics file

 --- Solved ---

 

Update 1- Disk1 was completely full with 20kbs of free space. I deleted a couple of files and restarted. 

Now need to figure out why unraid is not writing elsewhere... I have 1tb+ of free space share in other disks.

 

Update 2- I freed 1gb as pointed out earlier and now unraid is balancing itself.  Now, disk1 is showing about 250gbs of free space.

 

 

Anyway thanks.

I notice that the ‘data’ share has files on the ‘cache’ pool, and that share is not configured to move them to the array so mover will ignore them and they will remain there.   Is this intentional?

I'm having the same issue, but my cache is not full, and none of my disk drives are full.

Attach Diagnostics ZIP to your NEXT post in this thread.

@Carlyj303 As well as diagnostics it could be worth giving the name of a share you think is misbehaving.

Figured it out. i needed to increase my Docker VM size.

On 8/17/2025 at 4:37 AM, Carlyj303 said:

Figured it out. i needed to increase my Docker VM size.

Probably you needed to figure out what was filling your docker.img instead of increasing its size. If you don't, it will probably fill again.