I would just like to confirm that I need to remove (and throwaway) device SDB. 

 

Can someone point me to (or provide) the instructions to remove the disk from the Cache BTRFS array?

 

Thank you.

 

Quote

Nov  4 07:38:27 Tower kernel: ata1.00: status: { DRDY }
Nov  4 07:38:27 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Nov  4 07:38:27 Tower kernel: ata1.00: cmd 60/10:d8:70:f2:0d/00:00:0b:00:00/40 tag 27 ncq dma 8192 in
Nov  4 07:38:27 Tower kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Nov  4 07:38:27 Tower kernel: ata1.00: status: { DRDY }
Nov  4 07:38:27 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Nov  4 07:38:27 Tower kernel: ata1.00: cmd 60/08:e0:38:06:0e/00:00:0b:00:00/40 tag 28 ncq dma 4096 in
Nov  4 07:38:27 Tower kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Nov  4 07:38:27 Tower kernel: ata1.00: status: { DRDY }
Nov  4 07:38:27 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Nov  4 07:38:27 Tower kernel: ata1.00: cmd 60/10:e8:88:f3:0d/00:00:0b:00:00/40 tag 29 ncq dma 8192 in
Nov  4 07:38:27 Tower kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Nov  4 07:38:27 Tower kernel: ata1.00: status: { DRDY }
Nov  4 07:38:27 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Nov  4 07:38:27 Tower kernel: ata1.00: cmd 60/08:f0:c0:f2:0d/00:00:0b:00:00/40 tag 30 ncq dma 4096 in
Nov  4 07:38:27 Tower kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Nov  4 07:38:27 Tower kernel: ata1.00: status: { DRDY }
Nov  4 07:38:27 Tower kernel: ata1.00: failed command: READ FPDMA QUEUED
Nov  4 07:38:27 Tower kernel: ata1.00: cmd 60/48:f8:f8:09:0e/00:00:0b:00:00/40 tag 31 ncq dma 36864 in
Nov  4 07:38:27 Tower kernel:         res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Nov  4 07:38:27 Tower kernel: ata1.00: status: { DRDY }
Nov  4 07:38:27 Tower kernel: ata1: hard resetting link
Nov  4 07:38:27 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov  4 07:38:27 Tower kernel: ata1.00: configured for UDMA/133
Nov  4 07:38:27 Tower kernel: scsi_io_completion_action: 17 callbacks suppressed
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=30s
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#0 Sense Key : 0x5 [current] 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#0 ASC=0x21 ASCQ=0x4 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 0b 0e 0a f8 00 00 18 00
Nov  4 07:38:27 Tower kernel: blk_print_req_error: 17 callbacks suppressed
Nov  4 07:38:27 Tower kernel: I/O error, dev sdb, sector 185469688 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=30s
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#1 Sense Key : 0x5 [current] 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#1 ASC=0x21 ASCQ=0x4 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#1 CDB: opcode=0x28 28 00 02 ad 30 60 00 00 30 00
Nov  4 07:38:27 Tower kernel: I/O error, dev sdb, sector 44904544 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 2
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=30s
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#2 Sense Key : 0x5 [current] 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#2 ASC=0x21 ASCQ=0x4 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#2 CDB: opcode=0x28 28 00 02 ac f0 28 00 00 08 00
Nov  4 07:38:27 Tower kernel: I/O error, dev sdb, sector 44888104 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=30s
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#3 Sense Key : 0x5 [current] 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#3 ASC=0x21 ASCQ=0x4 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#3 CDB: opcode=0x28 28 00 0b 0e 00 28 00 00 08 00
Nov  4 07:38:27 Tower kernel: I/O error, dev sdb, sector 185466920 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=30s
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#4 Sense Key : 0x5 [current] 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#4 ASC=0x21 ASCQ=0x4 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#4 CDB: opcode=0x28 28 00 02 ac f1 18 00 00 08 00
Nov  4 07:38:27 Tower kernel: I/O error, dev sdb, sector 44888344 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=30s
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#5 Sense Key : 0x5 [current] 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#5 ASC=0x21 ASCQ=0x4 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#5 CDB: opcode=0x28 28 00 02 ad 3d 70 00 00 40 00
Nov  4 07:38:27 Tower kernel: I/O error, dev sdb, sector 44907888 op 0x0:(READ) flags 0x80700 phys_seg 8 prio class 2
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=30s
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#6 Sense Key : 0x5 [current] 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#6 ASC=0x21 ASCQ=0x4 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#6 CDB: opcode=0x28 28 00 02 ad 63 b8 00 00 10 00
Nov  4 07:38:27 Tower kernel: I/O error, dev sdb, sector 44917688 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=30s
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#7 Sense Key : 0x5 [current] 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#7 ASC=0x21 ASCQ=0x4 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#7 CDB: opcode=0x28 28 00 02 ad 67 68 00 00 28 00
Nov  4 07:38:27 Tower kernel: I/O error, dev sdb, sector 44918632 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 2
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=30s
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#8 Sense Key : 0x5 [current] 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#8 ASC=0x21 ASCQ=0x4 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#8 CDB: opcode=0x28 28 00 02 ad 69 a0 00 00 08 00
Nov  4 07:38:27 Tower kernel: I/O error, dev sdb, sector 44919200 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=30s
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#9 Sense Key : 0x5 [current] 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#9 ASC=0x21 ASCQ=0x4 
Nov  4 07:38:27 Tower kernel: sd 2:0:0:0: [sdb] tag#9 CDB: opcode=0x28 28 00 02 ad 90 c0 00 00 20 00
Nov  4 07:38:27 Tower kernel: I/O error, dev sdb, sector 44929216 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2
Nov  4 07:38:27 Tower kernel: ata1: EH complete
Nov  4 07:38:27 Tower kernel: repair_io_failure: 108 callbacks suppressed
Nov  4 07:38:27 Tower kernel: BTRFS info (device sdb1): read error corrected: ino 261 off 587280384 (dev /dev/sdb1 sector 185467648)
Nov  4 07:38:27 Tower kernel: BTRFS info (device sdb1): read error corrected: ino 261 off 587231232 (dev /dev/sdb1 sector 185467640)
Nov  4 07:38:27 Tower kernel: BTRFS info (device sdb1): read error corrected: ino 261 off 586911744 (dev /dev/sdb1 sector 44902496)
Nov  4 07:38:27 Tower kernel: BTRFS info (device sdb1): read error corrected: ino 261 off 587284480 (dev /dev/sdb1 sector 185467656)
Nov  4 07:38:27 Tower kernel: BTRFS info (device sdb1): read error corrected: ino 261 off 586915840 (dev /dev/sdb1 sector 44902504)
Nov  4 07:38:27 Tower kernel: BTRFS info (device sdb1): read error corrected: ino 261 off 586919936 (dev /dev/sdb1 sector 44902512)
Nov  4 07:38:27 Tower kernel: BTRFS info (device sdb1): read error corrected: ino 261 off 586924032 (dev /dev/sdb1 sector 44902520)
Nov  4 07:38:27 Tower kernel: BTRFS info (device sdb1): read error corrected: ino 261 off 586928128 (dev /dev/sdb1 sector 44902528)
Nov  4 07:38:27 Tower kernel: BTRFS info (device sdb1): read error corrected: ino 261 off 586932224 (dev /dev/sdb1 sector 44902536)
Nov  4 07:38:27 Tower kernel: BTRFS info (device sdb1): read error corrected: ino 261 off 586539008 (dev /dev/sdb1 sector 44886056)
Nov  4 11:29:57 Tower kernel: md: sync done. time=34196sec
Nov  4 11:29:57 Tower kernel: md: recovery thread: exit status: 0
 

 

tower-diagnostics-20241104-1319.zip

Edited November 4, 20241 yr by jeradc
hit enter too soon and did not complete topic.

That looks more like a power/connection issue, replace both cables and retest.

Interesting. I'm pretty sure I've already tried different sata cables with no change (issue recurs). But I've not tried a different power plug. I'll swap both out and try again. Thanks.

No update yet.

 

I noticed that both SDC and SDB were having issues prior to the SDB1 errors.

Both disks connect to the same controller on the motherboard, and share a common power cord from the PSU.

 

So far I've:

• Upgaded to 6.12.13 from 6.12.11
• Moved one drive to different controller (and different SATA cable).
• On the other drive I swapped the SATA cable, leaving it connected to the same position on the motherboard.

so I think, if it recurs, that leaves power supply / common power cable they share.

 

Thanks.

No recurrence, and the issue had been almost daily prior. Marking as resolved. Thank you.

Edited November 15, 20241 yr by jeradc

Future me reporting in, the issue still recurs, just not as frequently as before. I'll try to get a new power supply for the system when I can. Right now this issue, seems self-correcting for the time being.