Hi everyone, woke this morning to found my system with errors "Unable to write to cache" and Unable to write to Docker image"

 

Looking into Fix Common Problems, it gave me two errors. For unable to write to cache it said "Drive mounted read-only or completely full." For unable to write to Docker image it said "Docker Image either full or corrupted."

 

I've had some intermittent issues related to Docker image size and the cache being inaccessible. Hope that somebody could have a look at my diagnostics file and suggest appropriate action?

 

Thanks

bigdaddy-diagnostics-20220506-0954.zip

Edited May 6, 20224 yr by randommonth

Ok I've been able to resolve it by shutting down, adjusting the power & data cables on my cache SSD and rebooting.

 

Is anyone able to identify what the issue might be from the diagnostics?

 

Otherwise I'll just assume the physical connectors on my SSD are dodgy.

Your logs are spammed with BTRFS errors of different type from your ADATA cache drive. And your docker image.

 

May  5 23:02:09 BIGDADDY kernel: blk_update_request: I/O error, dev sdb, sector 14812928 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
May  5 23:02:09 BIGDADDY kernel: BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 192, rd 25463, flush 0, corrupt 0, gen 0
May  5 23:02:09 BIGDADDY kernel: sd 1:0:0:0: [sdb] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s
May  5 23:02:09 BIGDADDY kernel: sd 1:0:0:0: [sdb] tag#13 CDB: opcode=0x28 28 00 00 e2 07 00 00 00 20 00

 

May  5 22:44:35 BIGDADDY kernel: BTRFS warning (device sdb1): direct IO failed ino 720496 rw 0,0 sector 0x5cdc3f8 len 0 err no 10
May  5 22:44:35 BIGDADDY kernel: BTRFS info (device sdb1): no csum found for inode 720496 start 195592192
May  5 22:44:35 BIGDADDY kernel: BTRFS warning (device sdb1): direct IO failed ino 720496 rw 0,0 sector 0x5bf6c98 len 0 err no 10
May  5 22:44:35 BIGDADDY kernel: BTRFS info (device sdb1): no csum found for inode 720496 start 195596288
May  5 22:44:35 BIGDADDY kernel: BTRFS warning (device sdb1): direct IO failed ino 720496 rw 0,0 sector 0x5bf6ca0 len 0 err no 10

 

May  5 22:49:36 BIGDADDY kernel: blk_update_request: I/O error, dev loop2, sector 382016 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 0
May  5 22:49:36 BIGDADDY kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 11, rd 4170, flush 0, corrupt 0, gen 0
May  5 22:49:36 BIGDADDY kernel: sd 1:0:0:0: [sdb] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s
May  5 22:49:36 BIGDADDY kernel: sd 1:0:0:0: [sdb] tag#6 CDB: opcode=0x28 28 00 05 cd c3 e0 00 00 20 00
May  5 22:49:36 BIGDADDY kernel: blk_update_request: I/O error, dev sdb, sector 97371104 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0
May  5 22:49:36 BIGDADDY kernel: BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 192, rd 23339, flush 0, corrupt 0, gen 0
May  5 22:49:36 BIGDADDY kernel: BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 192, rd 23340, flush 0, corrupt 0, gen 0
May  5 22:49:36 BIGDADDY kernel: BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 192, rd 23341, flush 0, corrupt 0, gen 0

 

I am not sure that simply rebooting would fix that, please post new diagnostics after the reboot.

Thanks for having a look @ChatNoir.

 

Latest diagnostics are attached.

bigdaddy-diagnostics-20220506-1608.zip

I do not see any BTRFS issues in the log. It seems OK. Maybe JorgeB could confirm that's good.

 

I would run a scrub on the Pool just to be on the safe side.

Ok thanks - could it be a hardware issue with the SSD? It's currently connected with a 90 degree SATA connector butting up against the case structure which may have physically damaged the SSD case. And I'm having these weird cache related issues about every 30-40 days, that unplugging/reconnecting the connector from the SSD and moterboard sata ports has always resolved.

Cache device dropped offline before:

 

May  5 22:39:19 BIGDADDY kernel: ata1: hard resetting link
May  5 22:39:24 BIGDADDY kernel: ata1: COMRESET failed (errno=-16)
May  5 22:39:24 BIGDADDY kernel: ata1: reset failed, giving up
May  5 22:39:24 BIGDADDY kernel: ata1.00: disabled
May  5 22:39:24 BIGDADDY kernel: ata1: EH complete

 

All the btrfs errors are the result of that, if it happens again replace the cables.