Wrong port? bad expansion card? other ideas? previous SSD keeps unmounting when I'm transferring `$HOME` from old 2TB (`SN850` via USB-c enclosure) to new internal 4TB SSD

[jon]

@Jason_Username_Taken

If your board started failing overall, then maybe you just got a dud and support will replace it for you (or return and re-buy, if you are still within the window).

Indeed, this finally happened. I have been using the new warranty-replacement board now. Been slowly re-configuring a fresh OS install all day, with almost no hiccups; had on sudden reboot in the middle of typing… IDK. If it happens again I’ll reach out to support.

@Jason_Username_Taken

If I’m not mistaken, you are on Core Ultra, correct? My post @jared_kidd linked above does describe NVMe SSD enclosure issue similar to what you initially experienced, but as far as we (the community) know so far that only affects AMD-based Framework laptops. IIRC we can consistently duplicate that issue on multiple AMD FW13/16 units, and consistently confirm Intel FW passes that test.

Correct on a Ultra 7 165H. I finally got to re-test moving files just now (via that enclosure) and sure enough: disconnected after 1m51s. Here’s all the dmesg output for the full 2min duration:

dmesg output starting from the first rsync call

Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#3 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#3 CDB: Read(10) 28 00 05 ad 65 80 00 03 38 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#28 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#28 CDB: Write(10) 2a 00 00 50 60 18 00 00 08 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#27 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#27 CDB: Write(10) 2a 00 00 50 5f e8 00 00 20 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#11 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#11 CDB: Write(10) 2a 00 00 d0 2f d0 00 00 08 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#10 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#10 CDB: Write(10) 2a 00 00 d0 2f b8 00 00 08 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#9 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#9 CDB: Write(10) 2a 00 00 d0 2f a0 00 00 08 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#8 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#8 CDB: Write(10) 2a 00 00 d0 2f 70 00 00 08 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#7 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#7 CDB: Write(10) 2a 00 00 d0 2f 18 00 00 10 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#6 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#6 CDB: Write(10) 2a 00 00 d0 2e 90 00 00 20 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#5 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#5 CDB: Write(10) 2a 00 00 d0 21 b8 00 00 08 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#4 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#4 CDB: Write(10) 2a 00 00 d0 21 00 00 00 08 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#2 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#2 CDB: Write(10) 2a 00 00 90 46 f0 00 00 08 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#1 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#1 CDB: Write(10) 2a 00 00 50 60 60 00 00 08 00
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#0 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT
Feb 28 22:14:00 myhost kernel: sd 2:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 00 50 60 40 00 00 08 00
Feb 28 22:14:30 myhost kernel: sd 2:0:0:0: [sdc] tag#20 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
Feb 28 22:14:30 myhost kernel: sd 2:0:0:0: [sdc] tag#20 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
Feb 28 22:14:30 myhost kernel: scsi host2: uas_eh_device_reset_handler start
Feb 28 22:14:36 myhost kernel: xhci_hcd 0000:00:0d.0: Timeout while waiting for setup device command
Feb 28 22:14:42 myhost kernel: xhci_hcd 0000:00:0d.0: Timeout while waiting for setup device command
Feb 28 22:14:42 myhost kernel: usb 2-3: device not accepting address 7, error -62
Feb 28 22:14:55 myhost kernel: xhci_hcd 0000:00:0d.0: Timeout while waiting for setup device command
Feb 28 22:14:55 myhost kernel: xhci_hcd 0000:00:0d.0: Timeout while waiting for setup device command
Feb 28 22:14:55 myhost kernel: usb 2-3: device not accepting address 7, error -62
Feb 28 22:14:55 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:14:55 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:14:55 myhost kernel: usb 2-3: device not accepting address 7, error -71
Feb 28 22:14:55 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:14:55 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:14:55 myhost kernel: usb 2-3: device not accepting address 7, error -71
Feb 28 22:14:55 myhost kernel: scsi host2: uas_eh_device_reset_handler FAILED err -19
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: usb 2-3: USB disconnect, device number 7
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 22:14:55 myhost kernel: Buffer I/O error on dev dm-2, logical block 526344, lost async page write
Feb 28 22:14:55 myhost kernel: Buffer I/O error on dev dm-2, logical block 526348, lost async page write
Feb 28 22:14:55 myhost kernel: Buffer I/O error on dev dm-2, logical block 1049822, lost async page write
Feb 28 22:14:55 myhost kernel: Buffer I/O error on dev dm-2, logical block 1572896, lost async page write
Feb 28 22:14:55 myhost kernel: Buffer I/O error on dev dm-2, logical block 1572919, lost async page write
Feb 28 22:14:55 myhost kernel: Buffer I/O error on dev dm-2, logical block 1573330, lost async page write
Feb 28 22:14:55 myhost kernel: Buffer I/O error on dev dm-2, logical block 1573331, lost async page write
Feb 28 22:14:55 myhost kernel: Buffer I/O error on dev dm-2, logical block 1573332, lost async page write
Feb 28 22:14:55 myhost kernel: Buffer I/O error on dev dm-2, logical block 1573333, lost async page write
Feb 28 22:14:55 myhost kernel: Buffer I/O error on dev dm-2, logical block 1573347, lost async page write
Feb 28 22:14:55 myhost kernel: Aborting journal on device dm-2-8.
Feb 28 22:14:55 myhost kernel: JBD2: I/O error when updating journal superblock for dm-2-8.
Feb 28 22:14:55 myhost kernel: EXT4-fs error (device dm-2) in ext4_reserve_inode_write:5801: IO failure
Feb 28 22:14:55 myhost kernel: EXT4-fs (dm-2): I/O error while writing superblock
Feb 28 22:14:55 myhost kernel: EXT4-fs (dm-2): Remounting filesystem read-only
Feb 28 22:14:55 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #116942641: lblock 0: comm rsync: error -5 reading directory block
Feb 28 22:14:55 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #9312954: lblock 0: comm rsync: error -5 reading directory block
Feb 28 22:14:55 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #1051837: lblock 0: comm rsync: error -5 reading directory block
Feb 28 22:14:55 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #9312354: lblock 0: comm rsync: error -5 reading directory block
Feb 28 22:14:55 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #9306113: lblock 0: comm rsync: error -5 reading directory block
Feb 28 22:14:55 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #119545270: lblock 0: comm rsync: error -5 reading directory block
Feb 28 22:14:55 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #116932664: lblock 0: comm rsync: error -5 reading directory block
Feb 28 22:14:55 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #117056219: lblock 0: comm rsync: error -5 reading directory block
Feb 28 22:14:55 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #9312513: lblock 0: comm rsync: error -5 reading directory block
Feb 28 22:14:55 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #1051236: lblock 0: comm rsync: error -5 reading directory block
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache
Feb 28 22:14:55 myhost kernel: sd 2:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Feb 28 22:14:55 myhost kernel: EXT4-fs (dm-2): unmounting filesystem a434d11d-b63f-4a9f-9e93-7d438234c61e.
Feb 28 22:14:55 myhost kernel: EXT4-fs (dm-2): I/O error while writing superblock
Feb 28 22:14:55 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:14:56 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:14:56 myhost kernel: usb 2-3: device not accepting address 8, error -71
Feb 28 22:14:56 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:14:56 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:14:57 myhost kernel: usb 2-3: device not accepting address 9, error -71
Feb 28 22:14:57 myhost kernel: usb usb2-port3: attempt power cycle
Feb 28 22:14:59 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:14:59 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:14:59 myhost kernel: usb 2-3: device not accepting address 10, error -71
Feb 28 22:15:00 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:15:00 myhost kernel: usb 2-3: Device not responding to setup address.
Feb 28 22:15:00 myhost kernel: usb 2-3: device not accepting address 11, error -71
Feb 28 22:15:00 myhost kernel: usb usb2-port3: unable to enumerate USB device

edit: dmesg logs for second attempt, this time with a cold-pack on the enclosure, from the start:

second attempt with replacement board

Feb 28 22:57:38 myhost kernel: usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 12 using xhci_hcd
Feb 28 22:57:38 myhost kernel: usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
Feb 28 22:57:38 myhost kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 28 22:57:38 myhost kernel: usb 2-1: Product: RTL9210B-CG
Feb 28 22:57:38 myhost kernel: usb 2-1: Manufacturer: Realtek
Feb 28 22:57:38 myhost kernel: usb 2-1: SerialNumber: 012345678909
Feb 28 22:57:38 myhost kernel: scsi host2: uas
Feb 28 22:57:38 myhost kernel: scsi 2:0:0:0: Direct-Access     WDS200T1 X0E-00AFY0       1.00 PQ: 0 ANSI: 6
Feb 28 22:57:38 myhost kernel: sd 2:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Feb 28 22:57:38 myhost kernel: sd 2:0:0:0: [sdc] Write Protect is off
Feb 28 22:57:38 myhost kernel: sd 2:0:0:0: [sdc] Mode Sense: 37 00 00 08
Feb 28 22:57:38 myhost kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 28 22:57:38 myhost kernel: sd 2:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
Feb 28 22:57:38 myhost kernel: sd 2:0:0:0: [sdc] Optimal transfer size 33553920 bytes
Feb 28 22:57:38 myhost kernel:  sdc: sdc1 sdc2 sdc3
Feb 28 22:57:38 myhost kernel: sd 2:0:0:0: [sdc] Attached SCSI disk
Feb 28 22:57:58 myhost kernel: EXT4-fs (dm-2): recovery complete
Feb 28 22:57:58 myhost kernel: EXT4-fs (dm-2): mounted filesystem a434d11d-b63f-4a9f-9e93-7d438234c61e r/w with ordered data mode. Quota mode: none.
Feb 28 23:04:10 myhost kernel: perf: interrupt took too long (2521 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#19 uas_eh_abort_handler 0 uas-tag 25 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#19 CDB: Read(10) 28 00 a2 8f 04 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#18 uas_eh_abort_handler 0 uas-tag 24 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#18 CDB: Read(10) 28 00 a2 8f 00 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#17 uas_eh_abort_handler 0 uas-tag 23 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#17 CDB: Read(10) 28 00 a2 8e fc 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#15 uas_eh_abort_handler 0 uas-tag 21 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#15 CDB: Read(10) 28 00 a2 8e f4 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#14 uas_eh_abort_handler 0 uas-tag 20 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#14 CDB: Read(10) 28 00 a2 8e f0 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#13 uas_eh_abort_handler 0 uas-tag 19 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#13 CDB: Read(10) 28 00 a2 8e ec 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#12 uas_eh_abort_handler 0 uas-tag 22 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#12 CDB: Read(10) 28 00 a2 8e f8 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#11 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#11 CDB: Read(10) 28 00 a2 8e e8 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#10 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#10 CDB: Read(10) 28 00 a2 8e e4 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#9 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#9 CDB: Read(10) 28 00 a2 8e e0 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#8 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#8 CDB: Read(10) 28 00 a2 8d 1c 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#7 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#7 CDB: Read(10) 28 00 a2 8d 0c 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#6 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#6 CDB: Read(10) 28 00 a2 8d 18 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#5 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#5 CDB: Read(10) 28 00 a2 8d 14 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#4 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#4 CDB: Read(10) 28 00 a2 8d 10 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#3 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#3 CDB: Read(10) 28 00 a2 8d 08 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#2 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#2 CDB: Read(10) 28 00 a2 8d 04 00 00 04 00 00
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#1 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD IN 
Feb 28 23:10:17 myhost kernel: sd 2:0:0:0: [sdc] tag#1 CDB: Read(10) 28 00 a2 8d 00 00 00 04 00 00
Feb 28 23:10:23 myhost kernel: sd 2:0:0:0: [sdc] tag#20 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT 
Feb 28 23:10:23 myhost kernel: sd 2:0:0:0: [sdc] tag#20 CDB: Write(10) 2a 00 00 d0 35 a0 00 00 10 00
Feb 28 23:10:23 myhost kernel: scsi host2: uas_eh_device_reset_handler stmyhost
Feb 28 23:10:23 myhost kernel: usb 2-1: reset SuperSpeed Plus Gen 2x1 USB device number 12 using xhci_hcd
Feb 28 23:10:28 myhost kernel: xhci_hcd 0000:00:0d.0: Trying to add endpoint 0x83 without dropping it.
Feb 28 23:10:28 myhost kernel: usb 2-1: failed to restore interface 0 altsetting 1 (error=-110)
Feb 28 23:10:28 myhost kernel: scsi host2: uas_eh_device_reset_handler FAILED err -19
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: Device offlined - not ready after error recovery
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#20 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#20 CDB: Write(10) 2a 00 00 d0 35 a0 00 00 10 00
Feb 28 23:10:28 myhost kernel: I/O error, dev sdc, sector 13645216 op 0x1:(WRITE) flags 0x103000 phys_seg 2 prio class 0
Feb 28 23:10:28 myhost kernel: usb 2-1: USB disconnect, device number 12
Feb 28 23:10:28 myhost kernel: buffer_io_error: 2433 callbacks suppressed
Feb 28 23:10:28 myhost kernel: Buffer I/O error on dev dm-2, logical block 1573556, lost async page write
Feb 28 23:10:28 myhost kernel: Buffer I/O error on dev dm-2, logical block 1573557, lost async page write
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#1 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#1 CDB: Read(10) 28 00 a2 8d 00 00 00 04 00 00
Feb 28 23:10:28 myhost kernel: I/O error, dev sdc, sector 2727149568 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#2 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#2 CDB: Read(10) 28 00 a2 8d 04 00 00 04 00 00
Feb 28 23:10:28 myhost kernel: I/O error, dev sdc, sector 2727150592 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#3 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#3 CDB: Read(10) 28 00 a2 8d 08 00 00 04 00 00
Feb 28 23:10:28 myhost kernel: I/O error, dev sdc, sector 2727151616 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#4 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#4 CDB: Read(10) 28 00 a2 8d 10 00 00 04 00 00
Feb 28 23:10:28 myhost kernel: I/O error, dev sdc, sector 2727153664 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#5 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#5 CDB: Read(10) 28 00 a2 8d 14 00 00 04 00 00
Feb 28 23:10:28 myhost kernel: I/O error, dev sdc, sector 2727154688 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#6 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#6 CDB: Read(10) 28 00 a2 8d 18 00 00 04 00 00
Feb 28 23:10:28 myhost kernel: I/O error, dev sdc, sector 2727155712 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#7 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#7 CDB: Read(10) 28 00 a2 8d 0c 00 00 04 00 00
Feb 28 23:10:28 myhost kernel: I/O error, dev sdc, sector 2727152640 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#8 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#8 CDB: Read(10) 28 00 a2 8d 1c 00 00 04 00 00
Feb 28 23:10:28 myhost kernel: I/O error, dev sdc, sector 2727156736 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#9 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=41s
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] tag#9 CDB: Read(10) 28 00 a2 8e e0 00 00 04 00 00
Feb 28 23:10:28 myhost kernel: I/O error, dev sdc, sector 2727272448 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache
Feb 28 23:10:28 myhost kernel: sd 2:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Feb 28 23:10:29 myhost kernel: Aborting journal on device dm-2-8.
Feb 28 23:10:29 myhost kernel: Buffer I/O error on dev dm-2, logical block 239632384, lost sync page write
Feb 28 23:10:29 myhost kernel: JBD2: I/O error when updating journal superblock for dm-2-8.
Feb 28 23:10:29 myhost kernel: EXT4-fs error (device dm-2) in ext4_reserve_inode_write:5801: IO failure
Feb 28 23:10:29 myhost kernel: Buffer I/O error on dev dm-2, logical block 0, lost sync page write
Feb 28 23:10:29 myhost kernel: EXT4-fs (dm-2): I/O error while writing superblock
Feb 28 23:10:29 myhost kernel: EXT4-fs (dm-2): Remounting filesystem read-only
Feb 28 23:10:30 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #527964: lblock 0: comm rsync: error -5 reading directory block
Feb 28 23:10:30 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #528095: lblock 0: comm rsync: error -5 reading directory block
Feb 28 23:10:30 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #529082: lblock 0: comm rsync: error -5 reading directory block
Feb 28 23:10:30 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #528399: lblock 0: comm rsync: error -5 reading directory block
Feb 28 23:10:30 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #528505: lblock 0: comm rsync: error -5 reading directory block
Feb 28 23:10:30 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #529121: lblock 0: comm rsync: error -5 reading directory block
Feb 28 23:10:30 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #527960: lblock 0: comm rsync: error -5 reading directory block
Feb 28 23:10:30 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #527994: lblock 0: comm rsync: error -5 reading directory block
Feb 28 23:10:30 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #528336: lblock 0: comm rsync: error -5 reading directory block
Feb 28 23:10:30 myhost kernel: EXT4-fs warning (device dm-2): htree_dirblock_to_tree:1083: inode #528321: lblock 0: comm rsync: error -5 reading directory block
Feb 28 23:10:32 myhost kernel: EXT4-fs (dm-2): unmounting filesystem a434d11d-b63f-4a9f-9e93-7d438234c61e.
Feb 28 23:10:32 myhost kernel: Buffer I/O error on dev dm-2, logical block 0, lost sync page write
Feb 28 23:10:32 myhost kernel: EXT4-fs (dm-2): I/O error while writing superblock

---

@jon

Huh. well I’m going to hijack my own thread I guess because maybe it’s related? new my motherboard[1] (maybe?[2]) just started dying…

So I guess the answer’s: no, unrelated.