March 20, 20224 yr Upgraded to 6.10.0 RC4 and now the docker Service dailes to start. i attached the diagnostics file. mahomelab-diagnostics-20220320-0845.zip
March 20, 20224 yr Community Expert Solution According to the syslog the docker image is corrupt: Mar 20 08:40:44 MAHomeLab kernel: BTRFS critical (device loop3): corrupt leaf: root=1 block=47251456 slot=16, invalid root generation, have 882824 expect (0, 882323] Mar 20 08:40:44 MAHomeLab kernel: BTRFS error (device loop3): block=47251456 read time tree block corruption detected Mar 20 08:40:44 MAHomeLab kernel: BTRFS critical (device loop3): corrupt leaf: root=1 block=47251456 slot=16, invalid root generation, have 882824 expect (0, 882323] Mar 20 08:40:44 MAHomeLab kernel: BTRFS error (device loop3): block=47251456 read time tree block corruption detected Mar 20 08:40:44 MAHomeLab kernel: BTRFS: error (device loop3) in btrfs_recover_log_trees:6401: errno=-5 IO failure (Couldn't read tree log root.) Mar 20 08:40:44 MAHomeLab kernel: BTRFS: error (device loop3) in btrfs_replay_log:2423: errno=-5 IO failure (Failed to recover log tree) Mar 20 08:40:45 MAHomeLab kernel: BTRFS error (device loop3): open_ctree failed Mar 20 08:40:45 MAHomeLab root: mount: /var/lib/docker: can't read superblock on /dev/loop3. There are also errors reading from the SSD: Mar 20 08:40:52 MAHomeLab kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 761778012160 wanted 5863377 found 5857159 Mar 20 08:40:52 MAHomeLab kernel: repair_io_failure: 2 callbacks suppressed Mar 20 08:40:52 MAHomeLab kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 761778012160 (dev /dev/nvme1n1p1 sector 2564352) Mar 20 08:40:52 MAHomeLab kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 761778016256 (dev /dev/nvme1n1p1 sector 2564360) Mar 20 08:40:52 MAHomeLab kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 761778020352 (dev /dev/nvme1n1p1 sector 2564368) Mar 20 08:40:52 MAHomeLab kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 761778024448 (dev /dev/nvme1n1p1 sector 2564376)
March 21, 20224 yr Author Thanks @itimpi. Really appreciate. I redefined a new image and reloaded all containers and all in fine now. thnak you!
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.