tl;dr: file-copy from previous SSD failing, so hoping for: (1) general tips to do this file transfer, or (2) specific expertise about these kernel dmesg logs (to help pin point the true cause that I might mitigate).
- goal: transfer 1TB of
$HOMEcontent from previous SSD via enclosure - problem:
rsynclasts <5min before said enclosure’s FS mount just disappears- hypothesis: I have a few guesses what might be wrong, but I’m hoping the logs below will give someone with more expertise a better hint:
- a) maybe I’m not mounting correctly (I’m just using Gnome’s new/fancy auto-mount and auto-prompt for the LUKS password, but maybe that’s problematic?)
- b) maybe this brand new enclosure I got is just too-low a quality? using brand new (bought here yesterday; about $30; Inland’s SKU
370569).- maybe this isn’t what enclosures are for, and I need something higher-end (eg: something with separate power supply?)
- c) maybe the previous SSD is failing? (I find this really unbelievable given my laptop was fine before upgrading; in fact I’d bet if I re-install it, I could just happily continue using it as-is).
- hypothesis: I have a few guesses what might be wrong, but I’m hoping the logs below will give someone with more expertise a better hint:
- steps: here’s what I’m doing to try to transfer
- fresh install motherboard and SSD:
- a) installed new motherboard: upgraded from 1st gen 13" motherboard to
Ultra 7 165H - b) installed new 4TB SSD: upgraded from
WD_BLACK SN850to 4TBWD_BLACK SN850X - 2280 - c) fresh install NixOS to new SSD; (then upgrade (rebuild, switch), etc., and reboot)
- a) installed new motherboard: upgraded from 1st gen 13" motherboard to
- trying to transfer
$HOMEover:- a) put previous 2TB SSD into enclosure
- b) plug said enclosure into
- specifically the top-right port: an expansion slot nearest the power button
- using what I think is a sufficient usb-c cable: this 40Gbps Thunderbolt 4 by Maxonar
- c) enter my LUKS password (gnome just auto-prompts me here after plugging in, I don’t take any special steps otherwise)
- d) run rsync against the newly mounted path, to copy out my old
$HOME(about1TBof content)
- fresh install motherboard and SSD:
attempts
Here’s the various attempts I’ve made (I’ll update this post with further attempts if I update this post)…
1st failed attempt: <2min
I don’t have the logs from the first attempt, but my second attempts’ logs are below.
2nd failed attempt: <6m
$ time rsync \
--verbose \
--archive \
--recursive \
--times \
--progress \
--exclude '.local/**' \
--exclude '.cache/**' \
/run/media/myuser/a434d11d-b63f-4a9f-9e93-7d438234c61e/home/myuser/ \
/home/myuser/
real 5m36.818s
user 0m7.366s
sys 0m33.071s
$ echo $?
1
rsync runs successfully for a few minutes before I start seeing a flood of these lines in stderr (which is why 90G transfer stops at just 5min):
rsync: [sender] send_files failed to open "/run/media/myuser/a434d11d-b63f-4a9f-9e93-7d438234c61e/home/myuser/audio/foo/bar.mp3": Input/output error
journalctl output
journalctl --pager-end --catalog --full --follow output at the moment it starts failing:
regular journalctl output
Feb 02 12:51:30 myhost rtkit-daemon[1774]: Successfully made thread 10469 of process 10460 owned by '1000' RT at priority 5.
Feb 02 12:51:30 myhost .xdg-desktop-po[3008]: Realtime error: Could not map tid: Process ids could not be found: 22
Feb 02 12:51:48 myhost rtkit-daemon[1774]: Successfully made thread 10469 of process 10460 owned by '1000' RT at priority 5.
Feb 02 12:51:49 myhost .xdg-desktop-po[3008]: Realtime error: Could not map tid: Process ids could not be found: 24
Feb 02 12:51:53 myhost udisksd[2714]: Cleaning up mount point /run/media/myuser/a434d11d-b63f-4a9f-9e93-7d438234c61e (device 254:3 is about to be cleaned up)
Feb 02 12:51:53 myhost systemd[1]: run-media-myuser-a434d11d\x2db63f\x2d4a9f\x2d9e93\x2d7d438234c61e.mount: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit run-media-myuser-a434d11d\x2db63f\x2d4a9f\x2d9e93\x2d7d438234c61e.mount has successfully entered the 'dead' state.
Feb 02 12:51:53 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-2 (backing device 8:19 no longer exists)
Feb 02 12:51:53 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:51:53 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:51:53 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:51:53 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:51:53 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:51:53 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:51:53 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:51:53 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:51:53 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:51:53 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:51:53 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:51:53 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:51:53 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:51:53 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:51:53 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:51:53 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:52:29 myhost polkitd[1543]: Operator of unix-session:3 successfully authenticated as unix-user:myuser to gain TEMPORARY authorization for action org.freedesktop.udisks2.filesystem-mount-system for system-bus-name::1.85 [/nix/store/al1cy7nrsdk0ngi28z99dn2n3f7hl6sv-gvfs-1.56.1/libexec/gvfs-udisks2-volume-monitor] (owned by unix-user:myuser)
Feb 02 12:52:29 myhost udisksd[2714]: Mounted /dev/dm-3 at /run/media/myuser/a434d11d-b63f-4a9f-9e93-7d438234c61e on behalf of uid 1000
Feb 02 12:52:29 myhost udisksd[2714]: Cleaning up mount point /run/media/myuser/a434d11d-b63f-4a9f-9e93-7d438234c61e (device 254:3 is about to be cleaned up)
Feb 02 12:52:29 myhost systemd[1]: run-media-myuser-a434d11d\x2db63f\x2d4a9f\x2d9e93\x2d7d438234c61e.mount: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit run-media-myuser-a434d11d\x2db63f\x2d4a9f\x2d9e93\x2d7d438234c61e.mount has successfully entered the 'dead' state.
Feb 02 12:52:29 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:52:29 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:52:29 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:52:29 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:52:29 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:52:29 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
Feb 02 12:52:29 myhost udisksd[2714]: Cleaning up LUKS device /dev/dm-3 (backing device 8:18 no longer exists)
Feb 02 12:52:29 myhost udisksd[2714]: Error cleaning up LUKS device /dev/dm-3: Failed to deactivate device: Device or resource busy
dmesg output: showing the drive suddenly “offlined” and some “ucsi_acpi” errors?
journalctl --pager-end --catalog --full --dmesg --follow output at the moment it starts failing:
just to recap the key lines I'm guessing matter from fuller the logs below
sd 1:0:0:0: [sdb] tag#29 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD INscsi host1: uas_eh_device_reset_handler startusb 2-1: reset SuperSpeed Plus Gen 2x1 USB device number 9 using xhci_hcducsi_acpi USBC000:00: unknown error 256ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)xhci_hcd 0000:00:0d.0: Trying to add endpoint 0x83 without dropping it.usb 2-1: failed to restore interface 0 altsetting 1 (error=-110)scsi host1: uas_eh_device_reset_handler FAILED err -19sd 1:0:0:0: Device offlined - not ready after error recoveryusb 2-1: USB disconnect, device number 9scsi_io_completion_action: 36 callbacks suppressedsd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35sI/O error, dev sdb, sector 165658624 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0Buffer I/O error on dev dm-3, logical block 468189831, lost async page writeAborting journal on device dm-3-8.JBD2: I/O error when updating journal superblock for dm-3-8.EXT4-fs error (device dm-3) in ext4_reserve_inode_write:5801: IO failureBuffer I/O error on dev dm-3, logical block 0, lost sync page writeEXT4-fs (dm-3): I/O error while writing superblockEXT4-fs (dm-3): Remounting filesystem read-onlyEXT4-fs warning (device dm-3): htree_dirblock_to_tree:1083: inode #117058494: lblock 0: comm rsync: error -5 reading directory block
dmesg journalctl output
Feb 02 12:45:34 myhost kernel: wlp170s0: associated
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#29 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#29 CDB: Read(10) 28 00 09 df bc 00 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#19 uas_eh_abort_handler 0 uas-tag 25 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#19 CDB: Read(10) 28 00 8f c0 a2 c0 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#18 uas_eh_abort_handler 0 uas-tag 24 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#18 CDB: Read(10) 28 00 8f c0 9e c0 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#15 uas_eh_abort_handler 0 uas-tag 23 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#15 CDB: Read(10) 28 00 8f c0 9a c0 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#14 uas_eh_abort_handler 0 uas-tag 22 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#14 CDB: Read(10) 28 00 8f c0 96 c0 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#13 uas_eh_abort_handler 0 uas-tag 21 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#13 CDB: Read(10) 28 00 8f c0 92 c0 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#12 uas_eh_abort_handler 0 uas-tag 20 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#12 CDB: Read(10) 28 00 8f c0 8e c0 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#11 uas_eh_abort_handler 0 uas-tag 19 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#11 CDB: Read(10) 28 00 8f c0 8a c0 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#10 uas_eh_abort_handler 0 uas-tag 18 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#10 CDB: Read(10) 28 00 8f c0 86 c0 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#9 uas_eh_abort_handler 0 uas-tag 17 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#9 CDB: Read(10) 28 00 8f c0 82 c0 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#8 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#8 CDB: Read(10) 28 00 8f c0 7e c0 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#7 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#7 CDB: Read(10) 28 00 09 df d8 00 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#6 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#6 CDB: Read(10) 28 00 09 df d4 00 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#5 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#5 CDB: Read(10) 28 00 09 df d0 00 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#4 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#4 CDB: Read(10) 28 00 09 df dc 00 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#3 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#3 CDB: Read(10) 28 00 09 df cc 00 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#2 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#2 CDB: Read(10) 28 00 09 df c8 00 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#1 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#1 CDB: Read(10) 28 00 09 df c4 00 00 04 00 00
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD IN
Feb 02 12:51:48 myhost kernel: sd 1:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 09 df c0 00 00 04 00 00
Feb 02 12:51:48 myhost kernel: scsi host1: uas_eh_device_reset_handler start
Feb 02 12:51:48 myhost kernel: usb 2-1: reset SuperSpeed Plus Gen 2x1 USB device number 9 using xhci_hcd
Feb 02 12:51:53 myhost kernel: ucsi_acpi USBC000:00: unknown error 256
Feb 02 12:51:53 myhost kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
Feb 02 12:51:53 myhost kernel: xhci_hcd 0000:00:0d.0: Trying to add endpoint 0x83 without dropping it.
Feb 02 12:51:53 myhost kernel: usb 2-1: failed to restore interface 0 altsetting 1 (error=-110)
Feb 02 12:51:54 myhost kernel: scsi host1: uas_eh_device_reset_handler FAILED err -19
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: Device offlined - not ready after error recovery
Feb 02 12:51:54 myhost kernel: usb 2-1: USB disconnect, device number 9
Feb 02 12:51:54 myhost kernel: scsi_io_completion_action: 36 callbacks suppressed
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 09 df c0 00 00 04 00 00
Feb 02 12:51:54 myhost kernel: blk_print_req_error: 36 callbacks suppressed
Feb 02 12:51:54 myhost kernel: I/O error, dev sdb, sector 165658624 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#1 CDB: Read(10) 28 00 09 df c4 00 00 04 00 00
Feb 02 12:51:54 myhost kernel: I/O error, dev sdb, sector 165659648 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#2 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#2 CDB: Read(10) 28 00 09 df c8 00 00 04 00 00
Feb 02 12:51:54 myhost kernel: I/O error, dev sdb, sector 165660672 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#3 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#3 CDB: Read(10) 28 00 09 df cc 00 00 04 00 00
Feb 02 12:51:54 myhost kernel: I/O error, dev sdb, sector 165661696 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#4 CDB: Read(10) 28 00 09 df dc 00 00 04 00 00
Feb 02 12:51:54 myhost kernel: I/O error, dev sdb, sector 165665792 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#5 CDB: Read(10) 28 00 09 df d0 00 00 04 00 00
Feb 02 12:51:54 myhost kernel: I/O error, dev sdb, sector 165662720 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#6 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#6 CDB: Read(10) 28 00 09 df d4 00 00 04 00 00
Feb 02 12:51:54 myhost kernel: I/O error, dev sdb, sector 165663744 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#7 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#7 CDB: Read(10) 28 00 09 df d8 00 00 04 00 00
Feb 02 12:51:54 myhost kernel: I/O error, dev sdb, sector 165664768 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#8 CDB: Read(10) 28 00 8f c0 7e c0 00 04 00 00
Feb 02 12:51:54 myhost kernel: I/O error, dev sdb, sector 2411757248 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=35s
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] tag#9 CDB: Read(10) 28 00 8f c0 82 c0 00 04 00 00
Feb 02 12:51:54 myhost kernel: I/O error, dev sdb, sector 2411758272 op 0x0:(READ) flags 0x84700 phys_seg 128 prio class 0
Feb 02 12:51:54 myhost kernel: Buffer I/O error on dev dm-3, logical block 468189831, lost async page write
Feb 02 12:51:54 myhost kernel: Buffer I/O error on dev dm-3, logical block 468189832, lost async page write
Feb 02 12:51:54 myhost kernel: Buffer I/O error on dev dm-3, logical block 468189833, lost async page write
Feb 02 12:51:54 myhost kernel: Buffer I/O error on dev dm-3, logical block 468189834, lost async page write
Feb 02 12:51:54 myhost kernel: Buffer I/O error on dev dm-3, logical block 468189835, lost async page write
Feb 02 12:51:54 myhost kernel: Aborting journal on device dm-3-8.
Feb 02 12:51:54 myhost kernel: Buffer I/O error on dev dm-3, logical block 239632384, lost sync page write
Feb 02 12:51:54 myhost kernel: JBD2: I/O error when updating journal superblock for dm-3-8.
Feb 02 12:51:54 myhost kernel: EXT4-fs error (device dm-3) in ext4_reserve_inode_write:5801: IO failure
Feb 02 12:51:54 myhost kernel: Buffer I/O error on dev dm-3, logical block 0, lost sync page write
Feb 02 12:51:54 myhost kernel: EXT4-fs (dm-3): I/O error while writing superblock
Feb 02 12:51:54 myhost kernel: EXT4-fs (dm-3): Remounting filesystem read-only
Feb 02 12:51:54 myhost kernel: EXT4-fs warning (device dm-3): htree_dirblock_to_tree:1083: inode #117058494: lblock 0: comm rsync: error -5 reading directory block
Feb 02 12:51:54 myhost kernel: EXT4-fs warning (device dm-3): htree_dirblock_to_tree:1083: inode #117058516: lblock 0: comm rsync: error -5 reading directory block
Feb 02 12:51:54 myhost kernel: EXT4-fs warning (device dm-3): htree_dirblock_to_tree:1083: inode #117058533: lblock 0: comm rsync: error -5 reading directory block
Feb 02 12:51:54 myhost kernel: EXT4-fs warning (device dm-3): htree_dirblock_to_tree:1083: inode #117058588: lblock 0: comm rsync: error -5 reading directory block
Feb 02 12:51:54 myhost kernel: EXT4-fs warning (device dm-3): htree_dirblock_to_tree:1083: inode #117058600: lblock 0: comm rsync: error -5 reading directory block
Feb 02 12:51:54 myhost kernel: EXT4-fs warning (device dm-3): htree_dirblock_to_tree:1083: inode #117058640: lblock 0: comm rsync: error -5 reading directory block
Feb 02 12:51:54 myhost kernel: EXT4-fs warning (device dm-3): dx_probe:823: inode #117058677: lblock 0: comm rsync: error -5 reading directory block
Feb 02 12:51:54 myhost kernel: EXT4-fs warning (device dm-3): htree_dirblock_to_tree:1083: inode #117058853: lblock 0: comm rsync: error -5 reading directory block
Feb 02 12:51:54 myhost kernel: EXT4-fs warning (device dm-3): htree_dirblock_to_tree:1083: inode #117058897: lblock 0: comm rsync: error -5 reading directory block
Feb 02 12:51:54 myhost kernel: EXT4-fs warning (device dm-3): dx_probe:823: inode #117058917: lblock 0: comm rsync: error -5 reading directory block
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Feb 02 12:51:54 myhost kernel: sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Feb 02 12:52:30 myhost kernel: EXT4-fs (dm-3): unmounting filesystem a434d11d-b63f-4a9f-9e93-7d438234c61e.
Feb 02 12:52:30 myhost kernel: Buffer I/O error on dev dm-3, logical block 0, lost sync page write
Feb 02 12:52:30 myhost kernel: EXT4-fs (dm-3): I/O error while writing superblock
3rd failed attempt: <5 hours
here’s the rsync command I ran this time (just a new --bwlimit flag):
$ rsync \
--verbose \
--bwlimit=500M \
--archive \
--recursive \
--times \
--progress \
--exclude '.local/**' \
--exclude '.cache/**' \
/run/media/myuser/a434d11d-b63f-4a9f-9e93-7d438234c61e/home/myuser/ \
/home/myuser/
# ...stdout snipped..
sent 39,382,833,548 bytes received 107,738 bytes 2,461,972.39 bytes/sec
total size is 99,192,030,805 speedup is 2.52
real 266m36.208s
user 0m10.118s
sys 0m50.479s
journalctl --pager-end --catalog --full --dmesg --follow is what I have logs for below (to avoid single-post character limits for discourse).
forum-template’s debugging details
which OS, BIOS, hardware
Which Linux distro are you using?
NixOS
$ cat /etc/lsb-release
DISTRIB_CODENAME=warbler
DISTRIB_DESCRIPTION="NixOS 25.05 (Warbler)"
DISTRIB_ID=nixos
DISTRIB_RELEASE="25.05"
LSB_VERSION="25.05 (Warbler)"
Which release version?
(if rolling release without a release version, skip this question)
Rolling-ish (nixos with unstable channel).
(If rolling release, last date updated?)
fresh install from a freshly downloaded NixOS Gnome ISO yesterday, and a fresh rebuild.
5461b06cd246337eb05c2c87dca75fa8741767e7107cf5cad5f1f6d6c04feea6 nixos-gnome-24.11.714033.f6687779bf4c-x86_64-linux.iso
Which kernel are you using?
6.12.11
Which BIOS version are you using?
I’ll report back about this; not sure how to check, but guessing it’ll show up somewhere in the BIOS config UI if I boot into that.
Which Framework Laptop 13 model are you using? (AMD Ryzen™ 7040 Series, Intel® Core™ Ultra Series 1, 13th Gen Intel® Core™ , 12th Gen Intel® Core™, 11th Gen Intel® Core™)
Framework 13, Ultra 7 165H (Intel® Core™ Ultra Series 1).
…