Does this mean my Cache drive is failing?

[wonderbread24]

Quote

May 12 20:36:42 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 12862088 off 0 csum 0x8941f998 expected csum 0x0aa50e9a mirror 1
May 12 20:36:42 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 99, gen 0
May 12 20:36:42 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 19091 off 0 csum 0x8941f998 expected csum 0xeba93014 mirror 1
May 12 20:36:42 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 100, gen 0
May 12 20:36:45 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 12862088 off 0 csum 0x8941f998 expected csum 0x0aa50e9a mirror 1
May 12 20:36:45 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 101, gen 0
May 12 20:36:45 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 19091 off 0 csum 0x8941f998 expected csum 0xeba93014 mirror 1
May 12 20:36:45 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 102, gen 0
May 12 20:36:49 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:36:49 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 103, gen 0
May 12 20:36:49 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:36:49 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 104, gen 0
May 12 20:37:00 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:37:00 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 105, gen 0
May 12 20:37:00 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:37:00 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 106, gen 0
May 12 20:37:10 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:37:10 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 107, gen 0
May 12 20:37:10 Unraid kernel: BTRFS warning (device loop2): csum failed root 5 ino 272 off 20480 csum 0x8941f998 expected csum 0x3b588bdd mirror 1
May 12 20:37:10 Unraid kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 108, gen 0

 

unraid-diagnostics-20210512-2038.zip

[JorgeB]

It means the docker image is corrupt, delete and recreate.

[wonderbread24]

Thanks @JorgeB

 

I figured out what it was.

There is a bug with 6.9.2 where it ignores the shutdown time-out in disk settings during a graceful shutdown. This was causing the parity check when powered back on. Simply updating the time-out fixes the bug from what I've read.

 

The errors, like you said, were coming from the docker.img. Turns out it was not located on my cache drive like I thought. It somehow ended up on disk4 in the array. Since Unraid was failing to shutdown properly it was causing the docker.img to become corrupt after each shutdown.

 

I've changed my cache drive just in case, relocated the docker.img location to the cache drive and increased the shutdown time-out to make sure everything powers down properly.

When I manually run the script to power down everything comes back happy. We'll see if does so automatically later today.