Bug 1631767 - udisksd reports "Error probing device" on qemu sata cd
Summary: udisksd reports "Error probing device" on qemu sata cd
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: udisks2
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-21 14:00 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2019-02-26 10:42 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed:


Attachments (Terms of Use)

Description Zbigniew Jędrzejewski-Szmek 2018-09-21 14:00:44 UTC
Description of problem:
I'm testing F29-beta5 amd64 silverblue image under qemu.

Version-Release number of selected component (if applicable):
udisks2-2.8.0-2.fc29.x86_64

Steps to Reproduce:
1. boot a machine under libvirt with "SATA CDROM" (disk bus: SATA)
2. look at logs from boot
3.

Actual results:
udisks daemon version 2.8.0 starting
Error probing device: Error sending ATA command IDENTIFY PACKET DEVICE to /dev/sr0: Unexpected sense data returned:
0000: 70 00 05 00  00 00 00 0a  00 58 00 01  21 04 00 00    p........X..!...
0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
 (g-io-error-quark, 0)
Error probing device: Error sending ATA command IDENTIFY PACKET DEVICE to /dev/sr0: Unexpected sense data returned:
0000: 70 00 05 00  00 00 00 0a  00 58 00 01  21 04 00 00    p........X..!...
0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
 (g-io-error-quark, 0)
Acquired the name org.freedesktop.UDisks2 on the system message bus

Expected results:
no errors

Comment 1 Tomáš Bžatek 2019-02-26 10:41:58 UTC
Yeah, seen those. Is this causing a trouble for you or is it just a cosmetic issue? We can always silence such errors (or lower the log priority) but they're there for a reason and hopefully not propagated to user.


Note You need to log in before you can comment on or make changes to this bug.