Flooding the syslog by the error messages due to failure to properly recognize USB devices handled by UAS

[alexkotov74]

On Fedora 42, the udisks2-2.10.90-3.fc42 fails to recognize USB HDD/USB SSD devices handled by the uas driver as an USB devices and tries to send them ATA command(s) which fail. Corresponding errors are flooding the syslog.

Here is the output of the "udevadm info /dev/sda" of Toshiba 2TB 2.5" HDD in the AXAGON EE25-XA6, USB 3.2 Gen 1 - SATA 6G enclosure connected via USB 3.2 Gen 2 cable:

P: /devices/pci0000:00/0000:00:08.3/0000:c6:00.4/usb8/8-1/8-1.4/8-1.4.1/8-1.4.1.3/8-1.4.1.3.3/8-1.4.1.3.3:1.0/host0/target0:0:0/0:0:0:0/block/sda
M: sda
J: b8:0
U: block
T: disk
D: b 8:0
N: sda
L: 0
S: disk/by-id/wwn-0x5000039a1298791a
S: disk/by-path/pci-0000:c6:00.4-usb-0:1.4.1.3.3:1.0-scsi-0:0:0:0
S: disk/by-path/pci-0000:c6:00.4-usbv3-0:1.4.1.3.3:1.0-scsi-0:0:0:0
S: disk/by-id/usb-TOSHIBA_HDWL120_AAAABBBBCCCC0003-0:0
S: disk/by-id/ata-TOSHIBA_HDWL120_60GHP28HT
S: disk/by-diskseq/28
Q: 28
E: DEVPATH=/devices/pci0000:00/0000:00:08.3/0000:c6:00.4/usb8/8-1/8-1.4/8-1.4.1/8-1.4.1.3/8-1.4.1.3.3/8-1.4.1.3.3:1.0/host0/target0:0:0/0:0:0:0/block/sda
E: DEVNAME=/dev/sda
E: DEVTYPE=disk
E: DISKSEQ=28
E: MAJOR=8
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=350170687380
E: ID_ATA=1
E: ID_TYPE=disk
E: ID_BUS=ata
E: ID_MODEL=TOSHIBA_HDWL120
E: ID_MODEL_ENC=TOSHIBA\x20HDWL120\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_REVISION=JT000A
E: ID_SERIAL=TOSHIBA_HDWL120_60GHP28HT
E: ID_SERIAL_SHORT=60GHP28HT
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=1
E: ID_ATA_READ_LOOKAHEAD=1
E: ID_ATA_READ_LOOKAHEAD_ENABLED=1
E: ID_ATA_FEATURE_SET_HPA=1
E: ID_ATA_FEATURE_SET_HPA_ENABLED=1
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=1
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=65932
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=65932
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_FEATURE_SET_PUIS=1
E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0
E: ID_ATA_FEATURE_SET_APM=1
E: ID_ATA_FEATURE_SET_APM_ENABLED=1
E: ID_ATA_FEATURE_SET_APM_CURRENT_VALUE=128
E: ID_ATA_DOWNLOAD_MICROCODE=1
E: ID_ATA_SATA=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1
E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1
E: ID_ATA_ROTATION_RATE_RPM=5400
E: ID_WWN=0x5000039a1298791a
E: ID_WWN_WITH_EXTENSION=0x5000039a1298791a

Technically, this issue is a continue of issues #812 and #1214

[marys1234]

Confirming the problem for Fedora CoreOS 42.

[ermezavx]

Thanks for reporting and reproducing this issue. This problem seems to be a continuation of #812 and #1214, now affecting Fedora 42 and CoreOS as confirmed by others.

• A temporary workaround is to restart the udisks2 service after connecting the USB device, which suppresses the syslog flooding for the current session.
• This race/timing issue seems to be related to UAS driver handling and improper device probe logic (ATA command to UAS USB device).
• For long-term resolution, it would be good to review how udisks2 detects and differentiates UAS-backed USB disks and avoids sending ATA commands in such scenarios.