May 29, 20224 yr Can someone tell me what this could be related to? All of my docker containers quit working. Is it a problem with my cache drive or docker itself? May 28 11:46:58 uNAS kernel: sd 2:0:0:0: [sdd] tag#2 CDB: opcode=0x28 28 00 0b cf 82 10 00 00 08 00 May 28 11:46:58 uNAS kernel: blk_update_request: I/O error, dev sdd, sector 198148624 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 May 28 11:46:58 uNAS kernel: BTRFS error (device sdd1): bdev /dev/sdd1 errs: wr 21, rd 135800, flush 1, corrupt 0, gen 0 May 28 11:46:58 uNAS kernel: BTRFS warning (device sdd1): direct IO failed ino 70670 rw 0,0 sector 0xbcf8218 len 0 err no 10 May 28 11:46:58 uNAS kernel: blk_update_request: I/O error, dev loop2, sector 15651344 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 May 28 11:46:58 uNAS kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 73982, flush 1, corrupt 0, gen 0
May 29, 20224 yr 1 hour ago, haley said: Can someone tell me what this could be related to? All of my docker containers quit working. Is it a problem with my cache drive or docker itself? May 28 11:46:58 uNAS kernel: sd 2:0:0:0: [sdd] tag#2 CDB: opcode=0x28 28 00 0b cf 82 10 00 00 08 00 May 28 11:46:58 uNAS kernel: blk_update_request: I/O error, dev sdd, sector 198148624 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 May 28 11:46:58 uNAS kernel: BTRFS error (device sdd1): bdev /dev/sdd1 errs: wr 21, rd 135800, flush 1, corrupt 0, gen 0 May 28 11:46:58 uNAS kernel: BTRFS warning (device sdd1): direct IO failed ino 70670 rw 0,0 sector 0xbcf8218 len 0 err no 10 May 28 11:46:58 uNAS kernel: blk_update_request: I/O error, dev loop2, sector 15651344 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 May 28 11:46:58 uNAS kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 73982, flush 1, corrupt 0, gen 0 /dev/sdd1 is a physical drive (probably your cache drive), while /dev/loop2 is the docker.img file so it is not surprising docker is not working. The diagnostics will provide more information to give you better feedback
May 29, 20224 yr Author Here’s the diagnostics file… unas-diagnostics-20220529-0511.zip Edited May 29, 20224 yr by haley Typo
May 29, 20224 yr Cache device dropped offline: May 28 03:35:21 uNAS kernel: ata1: hard resetting link May 28 03:35:27 uNAS kernel: ata1: link is slow to respond, please be patient (ready=0) May 28 03:35:56 uNAS kernel: ata1: COMRESET failed (errno=-16) May 28 03:35:56 uNAS kernel: ata1: limiting SATA link speed to 3.0 Gbps May 28 03:35:56 uNAS kernel: ata1: hard resetting link May 28 03:36:01 uNAS kernel: ata1: COMRESET failed (errno=-16) May 28 03:36:01 uNAS kernel: ata1: reset failed, giving up May 28 03:36:01 uNAS kernel: ata1.00: disabled May 28 03:36:01 uNAS kernel: ata1: EH complete Check/replace cables.
May 29, 20224 yr Author Thanks! I was worried this may be a hardware issue. I’ll open it up and see whats going on.
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.