udisks
udisks copied to clipboard
storaged-project
udisksd: error probing device
udisks2 version 2.9.1 linux 5.7.15
When I attach my 1TB Western Digital Elements external hard drives, the following is written to the journal:
udisksd[923]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
0000: 70 00 01 00 00 00 00 0a 00 00 00 00 00 1d 00 00 p...............
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
(g-io-error-quark, 0)
The hard drives still work ok.
This is the same problem as in this bug, but it was closed 2 years ago because it was assumed to have been fixed.
udisks2 version 2.9.4 linux 5.4.224-1-MANJARO
I have a similar log when I plug-in a 20TB Western Digital Elements external HDD:
udisksd[1667]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdh': Unexpected sense data returned:
0000: f0 00 01 00 00 00 00 0a 00 00 00 00 00 1d 00 00 ................
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
(g-io-error-quark, 0)
The hdd seems to be OK though. I can R/W to it fine and SMART self tests (short and long) all pass.
It seems as if upgrading my kernel from 5.15.88 to 6.1.12 resulted in the same type of warning for my WD ‘My Passport for Mac’ 4 TB drive:
kernel: sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
kernel: sd 0:0:0:0: [sda] 7813969920 512-byte logical blocks: (4.00 TB/3.64 TiB)
kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
kernel: sd 0:0:0:0: [sda] Write Protect is off
kernel: sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
kernel: sd 0:0:0:0: [sda] No Caching mode page found
kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
kernel: sda: sda1 sda2
kernel: sd 0:0:0:0: [sda] Attached SCSI disk
udisksd[1310]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
0000: f0 00 01 00 00 00 00 0a 00 00 00 00 00 1d 00 00 ................
0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
(g-io-error-quark, 0)
udisks 2.9.4 linux 6.1.12 (Gentoo)
No actual drive problems encountered yet, though.
Three cases of failures on external WD drives. I guess we can afford silencing any ATA IDENTIFY DEVICE errors on USB-connected drives. There's another known issue with QEMU drives not fully implementing the required ATA commands.
You may ignore similar errors for now as long as it's related to the IDENTIFY DEVICE command.
Hi, FWIW, I just noticed this error appeared on my debian computers with external WD USB drives when the udisks2 debian package version went from 0_2.9.4-3 to 0_2.9.4-3+b1. Unfortunately I did not managed to get the corresponding source tree for those versions in order to make a comparison.
Reporters: could you please post output of udevadm info /dev/sdX for your affected devices? I'm interested in ID_ATA_ attributes.
Reporters: could you please post output of
udevadm info /dev/sdXfor your affected devices? I'm interested inID_ATA_attributes.
P: /devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4:1.0/host0/target0:0:0/0:0:0:0/block/sda
M: sda
U: block
T: disk
D: b 8:0
N: sda
L: 0
S: disk/by-path/pci-0000:07:00.3-usb-0:1.3.4:1.0-scsi-0:0:0:0
S: disk/by-id/wwn-0x50014ee21184ea35
S: disk/by-diskseq/9
S: disk/by-id/ata-WDC_WD40NDZW-11MR8S0_WD-WX41D69CD4K6
S: disk/by-id/usb-WD_My_Passport_2628_575834314436394344344B36-0:0
Q: 9
E: DEVPATH=/devices/pci0000:00/0000:00:08.1/0000:07:00.3/usb5/5-1/5-1.3/5-1.3.4/5-1.3.4:1.0/host0/target0:0:0/0:0:0:0/block/sda
E: DEVNAME=/dev/sda
E: DEVTYPE=disk
E: DISKSEQ=9
E: MAJOR=8
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=139845737487
E: ID_ATA=1
E: ID_TYPE=disk
E: ID_BUS=ata
E: ID_MODEL=WDC_WD40NDZW-11MR8S0
E: ID_MODEL_ENC=WDC\x20WD40NDZW-11MR8S0\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_REVISION=02.01A02
E: ID_SERIAL=WDC_WD40NDZW-11MR8S0_WD-WX41D69CD4K6
E: ID_SERIAL_SHORT=WD-WX41D69CD4K6
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_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=66316
E: ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN=2
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=0x50014ee21184ea35
E: ID_WWN_WITH_EXTENSION=0x50014ee21184ea35
E: ID_USB_MODEL=My_Passport_2628
E: ID_USB_MODEL_ENC=My\x20Passport\x202628
E: ID_USB_MODEL_ID=2628
E: ID_USB_SERIAL=WD_My_Passport_2628_575834314436394344344B36-0:0
E: ID_USB_SERIAL_SHORT=575834314436394344344B36
E: ID_USB_VENDOR=WD
E: ID_USB_VENDOR_ENC=WD\x20\x20\x20\x20\x20\x20
E: ID_USB_VENDOR_ID=1058
E: ID_USB_REVISION=1028
E: ID_USB_TYPE=disk
E: ID_USB_INSTANCE=0:0
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usb-storage
E: ID_PATH=pci-0000:07:00.3-usb-0:1.3.4:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_07_00_3-usb-0_1_3_4_1_0-scsi-0_0_0_0
E: ID_PART_TABLE_UUID=087bb428-9e42-8648-8998-95bbf280a8f4
E: ID_PART_TABLE_TYPE=gpt
E: DEVLINKS=/dev/disk/by-path/pci-0000:07:00.3-usb-0:1.3.4:1.0-scsi-0:0:0:0 /dev/disk/by-id/wwn-0x50014ee21184ea35 /dev/disk/by-diskseq/9 /dev/disk/by-id/ata-WDC_WD40NDZW-11MR8S0_WD-WX41D69CD4K6 /dev/disk/by-id/usb-WD_My_Passport_2628_575834314436394344344B36-0:0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:
Thanks @equaeghe! I think we can avoid sending custom ATA commands from UDisks in case these udev attributes are present. Great to see the passthrough works on USB bridges.