Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Docker failed to start after Upgrade to 6.12.6 - restart fixes problem temporarily

Featured Replies

Hi looking for some help.

I recently upgraded to 6.12.6 my Docker service stops running and I get the Docker Service failed to start. error.

"No Docker containers installed".

When I restart the problem goes away. 

Only thing I've done recently is upgraded to 6.12.6 and installed Deluge Docker.

I've noticed CPU errors in the logs but not sure what they mean.

I saw another thread for the same error but didn't want to take take over the post.

equippedserver-diagnostics-20231221-1611.zip

There are 4 topics with this same problem now.

 

The common thread is we all jist upgraded.

 

Im on my phone otherwise I'd link, just have a quick browse.

  • Author

I did look through the others, I didn't really see anything similar. But maybe I missed something.

  • Community Expert
Dec 21 12:09:55 equippedSERVER kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Dec 21 12:09:55 equippedSERVER kernel: ? _raw_spin_unlock+0x14/0x29
Dec 21 12:09:55 equippedSERVER kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

First, macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

 

Second, pool is going read only due to "write time tree block corruption detected":

 

Dec 21 12:40:26 equippedSERVER kernel: BTRFS error (device nvme1n1p1): block=5003613274112 write time tree block corruption detected
Dec 21 12:40:26 equippedSERVER kernel: BTRFS: error (device nvme1n1p1) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction)
Dec 21 12:40:26 equippedSERVER kernel: BTRFS info (device nvme1n1p1: state E): forced readonly

 

This error usually means a hardware issue, most often bad RAM, but with the current kernel there have been some possible false positives, so I would recommend running memtest and if nothing is found try to recreate the pool or use zfs instead.

  • Author

So far memtest all passed. Maybe it's my NVME drive. I will try ZFS next.

  • Author

Now Unraid is full crashing with a Kernel error

"Kernel panic not syncing" I will take a photo next crash. Right now i'm trying to get a new flash drive to try while I wait for new RAM.

  • Author

unraid.thumb.jpg.7acc51b9bfe084546e860fb3bbe56167.jpg

  • Author

I got if fixed, I changed my cache drive but also changed them to ZFS. I saw another comment on Reddit where someone changed their cache to ZFS from BTFRS for something similar. It seems I was getting a bunch of data errors.
For it to happen only after upgrading to 6.12.6 is a bit concerning. 
 

Quote

Dec 26 23:09:59 equippedSERVER kernel: BTRFS: error (device nvme1n1p1: state A) in __btrfs_free_extent:3072: errno=-2 No such entry
Dec 26 23:09:59 equippedSERVER kernel: BTRFS info (device nvme1n1p1: state EA): forced readonly
Dec 26 23:09:59 equippedSERVER kernel: BTRFS error (device nvme1n1p1: state EA): failed to run delayed ref for logical 252857671680 num_bytes 57344 type 178 action 2 ref_mod 1: -2
Dec 26 23:09:59 equippedSERVER kernel: BTRFS: error (device nvme1n1p1: state EA) in btrfs_run_delayed_refs:2149: errno=-2 No such entry
Dec 26 23:10:01 equippedSERVER kernel: loop: Write error at byte offset 1212248064, length 4096.
Dec 26 23:10:01 equippedSERVER kernel: loop: Write error at byte offset 1215893504, length 4096.
Dec 26 23:10:01 equippedSERVER kernel: I/O error, dev loop2, sector 2367672 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
Dec 26 23:10:01 equippedSERVER kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:01 equippedSERVER kernel: I/O error, dev loop2, sector 2374792 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
Dec 26 23:10:01 equippedSERVER kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:02 equippedSERVER kernel: loop: Write error at byte offset 20915568640, length 4096.
Dec 26 23:10:02 equippedSERVER kernel: loop: Write error at byte offset 20647133184, length 4096.
Dec 26 23:10:02 equippedSERVER kernel: loop: Write error at byte offset 20915552256, length 4096.
Dec 26 23:10:02 equippedSERVER kernel: loop: Write error at byte offset 20647116800, length 4096.
Dec 26 23:10:02 equippedSERVER kernel: I/O error, dev loop2, sector 40850720 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2
Dec 26 23:10:02 equippedSERVER kernel: I/O error, dev loop2, sector 40326432 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2
Dec 26 23:10:02 equippedSERVER kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:02 equippedSERVER kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:02 equippedSERVER kernel: I/O error, dev loop2, sector 40850688 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2
Dec 26 23:10:02 equippedSERVER kernel: I/O error, dev loop2, sector 40326400 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2
Dec 26 23:10:02 equippedSERVER kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:02 equippedSERVER kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:02 equippedSERVER kernel: loop: Write error at byte offset 20646100992, length 4096.
Dec 26 23:10:02 equippedSERVER kernel: loop: Write error at byte offset 20914536448, length 4096.
Dec 26 23:10:02 equippedSERVER kernel: loop: Write error at byte offset 20646264832, length 4096.
Dec 26 23:10:02 equippedSERVER kernel: loop: Write error at byte offset 20914700288, length 4096.
Dec 26 23:10:02 equippedSERVER kernel: I/O error, dev loop2, sector 40324416 op 0x1:(WRITE) flags 0x1800 phys_seg 15 prio class 2
Dec 26 23:10:02 equippedSERVER kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:02 equippedSERVER kernel: I/O error, dev loop2, sector 40848704 op 0x1:(WRITE) flags 0x1800 phys_seg 15 prio class 2
Dec 26 23:10:02 equippedSERVER kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:02 equippedSERVER kernel: I/O error, dev loop2, sector 40324736 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2
Dec 26 23:10:02 equippedSERVER kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:02 equippedSERVER kernel: I/O error, dev loop2, sector 40849024 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2
Dec 26 23:10:02 equippedSERVER kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:02 equippedSERVER kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction)
Dec 26 23:10:02 equippedSERVER kernel: BTRFS info (device loop2: state E): forced readonly
Dec 26 23:10:02 equippedSERVER kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction.
Dec 26 23:10:02 equippedSERVER kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1992: errno=-5 IO failure
Dec 26 23:10:25 equippedSERVER kernel: lo_write_bvec: 22 callbacks suppressed
Dec 26 23:10:25 equippedSERVER kernel: loop: Write error at byte offset 1247408128, length 4096.
Dec 26 23:10:25 equippedSERVER kernel: blk_print_req_error: 22 callbacks suppressed
Dec 26 23:10:25 equippedSERVER kernel: I/O error, dev loop2, sector 2436344 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
Dec 26 23:10:25 equippedSERVER kernel: btrfs_dev_stat_inc_and_print: 22 callbacks suppressed
Dec 26 23:10:25 equippedSERVER kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 33, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:32 equippedSERVER kernel: loop: Write error at byte offset 1212248064, length 4096.
Dec 26 23:10:32 equippedSERVER kernel: I/O error, dev loop2, sector 2367672 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
Dec 26 23:10:32 equippedSERVER kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 34, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:35 equippedSERVER kernel: loop: Write error at byte offset 2992574464, length 4096.
Dec 26 23:10:35 equippedSERVER kernel: I/O error, dev loop2, sector 5844872 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2
Dec 26 23:10:35 equippedSERVER kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 35, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:35 equippedSERVER kernel: loop: Write error at byte offset 2991587328, length 4096.
Dec 26 23:10:35 equippedSERVER kernel: I/O error, dev loop2, sector 5842944 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
Dec 26 23:10:35 equippedSERVER kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 36, rd 0, flush 0, corrupt 0, gen 0
Dec 26 23:10:35 equippedSERVER kernel: loop: Write error at byte offset 655400960, length 4096.
Dec 26 23:10:35 equippedSERVER kernel: I/O error, dev loop2, sector 1280080 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2
Dec 26 23:10:35 equippedSERVER kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 37, rd 0, flush 0, corrupt 0, gen 0takah

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.