I am using the Framework storage expansion card. However it appears that the contact to the hard drive does not work well. When I am doing some read or write operation on the drive, after a couple of minutes the contact to the drive seems to be lost. I get a notification from my desktop environment that a an external hard drive has been connected and if I would like to mount it.
When plugging it in my OS (Arch, kernel 6.11.5-arch1-1) does not seem to always recognize it, I seem to have to remove it and plug it in again before it works.
This is how the log looks like the moment I get the notification that a hard drive has been connected (which I think means that the connection has been lost):
Nov 02 04:50:47 framework kernel: perf: interrupt took too long (2530 > 2500), lowering kernel.perf_event_max_sample_rate to 78900
Nov 02 04:51:19 framework kernel: usb 2-2: USB disconnect, device number 14
Nov 02 04:51:19 framework kernel: xhci_hcd 0000:00:0d.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Nov 02 04:51:19 framework kernel: usb 2-2: cmd cmplt err -108
Nov 02 04:51:19 framework kernel: sd 1:0:0:0: [sdb] tag#7 uas_zap_pending 0 uas-tag 1 inflight: CMD
Nov 02 04:51:19 framework kernel: sd 1:0:0:0: [sdb] tag#7 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
Nov 02 04:51:19 framework kernel: sd 1:0:0:0: [sdb] tag#7 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=0s
Nov 02 04:51:19 framework kernel: sd 1:0:0:0: [sdb] tag#7 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
Nov 02 04:51:19 framework kernel: blk_print_req_error: 196 callbacks suppressed
Nov 02 04:51:19 framework kernel: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Nov 02 04:51:19 framework kernel: device offline error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Nov 02 04:51:19 framework kernel: device offline error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Nov 02 04:51:19 framework kernel: device offline error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Nov 02 04:51:19 framework kernel: device offline error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Nov 02 04:51:19 framework kernel: device offline error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Nov 02 04:51:19 framework kernel: device offline error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Nov 02 04:51:19 framework kernel: device offline error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Nov 02 04:51:19 framework kernel: device offline error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Nov 02 04:51:19 framework kernel: device offline error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Nov 02 04:51:20 framework kernel: EXT4-fs (sdb1): shut down requested (2)
Nov 02 04:51:20 framework kernel: Aborting journal on device sdb1-8.
Nov 02 04:51:20 framework kernel: Buffer I/O error on dev sdb1, logical block 30441472, lost sync page write
Nov 02 04:51:20 framework kernel: JBD2: I/O error when updating journal superblock for sdb1-8.
Nov 02 04:51:20 framework kernel: EXT4-fs warning (device sdb1): dx_probe:823: inode #13401116: lblock 0: comm rmlint: error -5 reading directory block
Nov 02 04:51:20 framework kernel: EXT4-fs warning (device sdb1): dx_probe:823: inode #13401116: lblock 0: comm rmlint: error -5 reading directory block
Nov 02 04:51:20 framework kernel: EXT4-fs warning (device sdb1): dx_probe:823: inode #13401116: lblock 0: comm rmlint: error -5 reading directory block
Nov 02 04:51:20 framework kernel: EXT4-fs warning (device sdb1): dx_probe:823: inode #13401116: lblock 0: comm rmlint: error -5 reading directory block
Nov 02 04:51:20 framework kernel: EXT4-fs warning (device sdb1): dx_probe:823: inode #13401116: lblock 0: comm rmlint: error -5 reading directory block
Nov 02 04:51:20 framework kernel: EXT4-fs warning (device sdb1): dx_probe:823: inode #13401116: lblock 0: comm rmlint: error -5 reading directory block
Nov 02 04:51:20 framework kernel: EXT4-fs warning (device sdb1): dx_probe:823: inode #13401116: lblock 0: comm rmlint: error -5 reading directory block
Nov 02 04:51:20 framework kernel: EXT4-fs warning (device sdb1): dx_probe:823: inode #13401116: lblock 0: comm rmlint: error -5 reading directory block
Nov 02 04:51:20 framework kernel: EXT4-fs warning (device sdb1): dx_probe:823: inode #13401116: lblock 0: comm rmlint: error -5 reading directory block
Nov 02 04:51:20 framework kernel: EXT4-fs warning (device sdb1): dx_probe:823: inode #13401116: lblock 0: comm rmlint: error -5 reading directory block
Nov 02 04:51:20 framework udisksd[1240]: Cleaning up mount point /run/media/caspar/e886c75f-e07d-411e-b560-af54076baa29 (device 8:17 no longer exists)
Nov 02 04:51:20 framework plasmashell[1324]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:128: TypeError: Cannot read property 'defaultActionIcon' of undefined
Nov 02 04:51:20 framework plasmashell[1324]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:129: TypeError: Cannot read property 'defaultActionText' of undefined
Nov 02 04:51:20 framework systemd[1]: run-media-caspar-e886c75f\x2de07d\x2d411e\x2db560\x2daf54076baa29.mount: Deactivated successfully.
Nov 02 04:51:20 framework kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Nov 02 04:51:20 framework kernel: sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Nov 02 04:51:21 framework kernel: usb 2-2: new SuperSpeed Plus Gen 2x1 USB device number 15 using xhci_hcd
Nov 02 04:51:21 framework kernel: usb 2-2: New USB device found, idVendor=13fe, idProduct=6500, bcdDevice= 1.10
Nov 02 04:51:21 framework kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 02 04:51:21 framework kernel: usb 2-2: Product: USB DISK 3.2
Nov 02 04:51:21 framework kernel: usb 2-2: Manufacturer:
Nov 02 04:51:21 framework kernel: usb 2-2: SerialNumber: 07001AF207A12772
Nov 02 04:51:21 framework kernel: scsi host2: uas
Nov 02 04:51:21 framework kernel: scsi 2:0:0:0: Direct-Access USB DISK 3.2 PMAP PQ: 0 ANSI: 6
Nov 02 04:51:21 framework mtp-probe[37735]: checking bus 2, device 15: "/sys/devices/pci0000:00/0000:00:0d.0/usb2/2-2"
Nov 02 04:51:21 framework mtp-probe[37735]: bus: 2, device: 15 was not an MTP device
Nov 02 04:51:21 framework kernel: sd 2:0:0:0: [sdc] 488397168 512-byte logical blocks: (250 GB/233 GiB)
Nov 02 04:51:21 framework kernel: sd 2:0:0:0: [sdc] Write Protect is off
Nov 02 04:51:21 framework kernel: sd 2:0:0:0: [sdc] Mode Sense: 23 00 00 00
Nov 02 04:51:21 framework kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 02 04:51:21 framework mtp-probe[37747]: checking bus 2, device 15: "/sys/devices/pci0000:00/0000:00:0d.0/usb2/2-2"
Nov 02 04:51:21 framework mtp-probe[37747]: bus: 2, device: 15 was not an MTP device
Nov 02 04:51:21 framework kernel: sd 2:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes
Nov 02 04:51:21 framework kernel: sd 2:0:0:0: [sdc] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Nov 02 04:51:21 framework kernel: sdc: sdc1
Nov 02 04:51:21 framework kernel: sd 2:0:0:0: [sdc] Attached SCSI disk
Nov 02 04:51:21 framework dbus-daemon[688]: [system] Activating service name='org.kde.kded.smart' requested by ':1.35' (uid=1000 pid=1290 comm="/usr/bin/kded6") (using servicehelper)
Nov 02 04:51:21 framework org.kde.kded.smart[37752]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
Nov 02 04:51:21 framework dbus-daemon[688]: [system] Successfully activated service 'org.kde.kded.smart'
The harddrive is still open in the file manager and appears to be there like nothing happend, even though I did not click on the button to mount it. Some interactions still seems to work, like ls and pwd , but ls throws an error ls: cannot access 'borg-backup': Input/output error, where borg-backup is the name of a directory in the harddrive. The command cd . which is supposed to change to the current directory throws an error zsh: Failed to get current directory: path invalid, as does any other cd command. This suggests to me that the connection to the harddrive has really been lost and dolphin and the command line are just in some kind of cached version.
When mounting it again, I get the message
Nov 02 05:05:06 framework kernel: EXT4-fs (sdc1): recovery complete
Nov 02 05:05:06 framework udisksd[1240]: Mounted /dev/sdc1 at /run/media/caspar/e886c75f-e07d-411e-b560-af54076baa29 on behalf of uid 1000
Nov 02 05:05:06 framework kernel: EXT4-fs (sdc1): mounted filesystem e886c75f-e07d-411e-b560-af54076baa29 r/w with ordered data mode. Quota mode: none.
which suggests that the recovery mode has been triggered.
Now the harddrive seems to work again like normal, until the next time this happens.
Is there a way to find out, if this is indeed a hardware failure? What information can I provide to the framework support when reaching out to them?