You are not logged in.
I have a couple of powered USB -> SATA adapters which I use to connect 4Tb Seagate Barracuda HDDs (with 12V/2A power adapter connected to the adapter). From time to time I see error messages like the following ones in system's logs:
kernel: sd 4:0:0:0: [sdb] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 4:0:0:0: [sdb] tag#24 Sense Key : Aborted Command [current]
kernel: sd 4:0:0:0: [sdb] tag#24 Add. Sense: Data phase CRC error detected
kernel: sd 4:0:0:0: [sdb] tag#24 CDB: Read(16) 88 00 00 00 00 01 c0 95 33 80 00 00 02 00 00 00
kernel: I/O error, dev sdb, sector 7525970816 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 2
...
kernel: sd 4:0:0:0: [sdb] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 4:0:0:0: [sdb] tag#2 Sense Key : Aborted Command [current]
kernel: sd 4:0:0:0: [sdb] tag#2 Add. Sense: Data phase CRC error detected
kernel: sd 4:0:0:0: [sdb] tag#2 CDB: Read(16) 88 00 00 00 00 01 cb 92 85 80 00 00 02 00 00 00
kernel: I/O error, dev sdb, sector 7710344576 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 2
...
kernel: sd 3:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 3:0:0:0: [sda] tag#5 Sense Key : Aborted Command [current]
kernel: sd 3:0:0:0: [sda] tag#5 Add. Sense: Data phase CRC error detected
kernel: sd 3:0:0:0: [sda] tag#5 CDB: Read(16) 88 00 00 00 00 00 4b 75 e1 80 00 00 02 00 00 00
kernel: I/O error, dev sda, sector 1266016640 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 2
...
kernel: sd 3:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
kernel: sd 3:0:0:0: [sda] tag#26 Sense Key : Aborted Command [current]
kernel: sd 3:0:0:0: [sda] tag#26 Add. Sense: Data phase CRC error detected
kernel: sd 3:0:0:0: [sda] tag#26 CDB: Read(16) 88 00 00 00 00 00 97 28 d7 80 00 00 02 00 00 00
kernel: I/O error, dev sda, sector 2536036224 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 2
It doesn't seem that there is a real problem with HDDs (which are fairly new: smartctl reports 100-200 power-on hours): long SMART test on those drives passes without errors, disks are fully readable and there is no data loss (everything in HDDs is 'md5sum'ed and integrity checks pass successfully). When I try to re-read sectors reported in the logs with hdparm - read succeeds without additional error messages. For example:
hdparm --read-sector 7525970816 /dev/sdb
/dev/sdb:
reading sector 7525970816: succeeded
c8e9 d9ca d67b abe8 ea29 c2d9 4eeb bca5
...
Also, sometimes when I connect a HDD, logs are filled up with this kind of messages: when disk is in use, such message appears approximately every second. Disconnecting/reconnecting the adapter solves this problem (and causes those errors to appear only once in a while).
The USB->SATA adapters are identified as:
Bus 002 Device 014: ID 7825:a2a4 Other World Computing External SATA Hard Drive Adapter cable PA023U3
Bus 002 Device 015: ID 7825:a2a4 Other World Computing External SATA Hard Drive Adapter cable PA023U3
What can be a cause for those messages, and how they can be eliminated completely?
Offline
https://wiki.archlinux.org/title/Power_ … utosuspend ?
nb. that eg. https://wiki.archlinux.org/title/TLP#USB_autosuspend or https://wiki.archlinux.org/title/Laptop … utosuspend will override this at runtime.
Offline