Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdc': Unexpected sense data returned: #1153

Open
mbiebl opened this issue Jul 24, 2023 · 4 comments · May be fixed by #1312
Milestone

Comments

@mbiebl
Copy link
Contributor

mbiebl commented Jul 24, 2023

Version: 2.10.0

Plugging in and USB stick (with NTFS formatted), I get:

Jul 24 18:11:38 pluto udisksd[736]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdc': Unexpected sense data returned:
                                    0000: f0 00 01 00  58 00 01 0a  00 00 00 00  00 1d 00 00    ....X...........
                                    0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
                                     (g-io-error-quark, 0)

I don't remember seeing those probe errors with older udisks versions.

@mbiebl mbiebl changed the title rror probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdc': Unexpected sense data returned: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdc': Unexpected sense data returned: Jul 24, 2023
@tbzatek
Copy link
Member

tbzatek commented Jul 25, 2023

This is #965, #808, #799 and #732. We'll likely just silence these messages.

@tbzatek tbzatek added this to the udisks-2.11.0 milestone Jul 25, 2023
@mbiebl
Copy link
Contributor Author

mbiebl commented Jul 25, 2023

oops, sorry for not checking the bug tracker more closely.
Feel free to close as duplicate.

@tbzatek
Copy link
Member

tbzatek commented Aug 12, 2024

For the moment severity of the warnings was lowered: 3c09a20

@tbzatek
Copy link
Member

tbzatek commented Sep 9, 2024

Please test #1311 if it solves your issue.

@tbzatek tbzatek linked a pull request Sep 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants