USB external storage failure/mysteries

English Hardware
23

udisks2 chokes on probing the disk. You may try debug:

erlangen:~ # /usr/libexec/udisks2/udisksd -rd
udisks-Message: 14:05:06.398: udisks daemon version 2.10.0 starting
udisks-Message: 14:05:06.872: Acquired the name org.freedesktop.UDisks2 on the system message bus
udisks-Message: 14:05:40.143: Mounted /dev/sdc2 at /media/openSUSE-Tumbleweed-NET-x86_64 on behalf of uid 1000
udisks-Message: 14:06:04.991: Cleaning up mount point /media/openSUSE-Tumbleweed-NET-x86_64 (device 8:34 no longer exists)
^Cudisks-Message: 14:06:11.531: udisks daemon version 2.10.0 exiting
erlangen:~ #
25 
gerry@Unknown-18-c0-4d-6a-ed-f9:~> sudo /usr/libexec/udisks2/udisksd -rd
udisks-Message: 13:11:49.018: udisks daemon version 2.10.0 starting

(udisksd:26890): udisks-CRITICAL **: 13:11:49.030: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
0000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 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-Message: 13:11:49.066: Acquired the name org.freedesktop.UDisks2 on the system message bus
^Cudisks-Message: 13:12:00.270: udisks daemon version 2.10.0 exiting
26

Login as root and replace the running daemon by a new one:

karl@erlangen:~> su -
Passwort: 
erlangen:~ # /usr/libexec/udisks2/udisksd -rd
udisks-Message: 14:12:23.722: udisks daemon version 2.10.0 starting
udisks-Message: 14:12:24.291: Acquired the name org.freedesktop.UDisks2 on the system message bus

Attach drive:

udisks-Message: 14:13:20.457: Mounted /dev/sdc2 at /media/openSUSE-Tumbleweed-NET-x86_64 on behalf of uid 1000

Remove drive:

udisks-Message: 14:13:51.616: Cleaning up mount point /media/openSUSE-Tumbleweed-NET-x86_64 (device 8:34 no longer exists)
27

Unplugging the drive did not seem to create any further output

gerry@Unknown-18-c0-4d-6a-ed-f9:~> sudo /usr/libexec/udisks2/udisksd -rd
udisks-Message: 13:11:49.018: udisks daemon version 2.10.0 starting

(udisksd:26890): udisks-CRITICAL **: 13:11:49.030: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
0000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 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-Message: 13:11:49.066: Acquired the name org.freedesktop.UDisks2 on the system message bus
^Cudisks-Message: 13:12:00.270: udisks daemon version 2.10.0 exiting
gerry@Unknown-18-c0-4d-6a-ed-f9:~> sudo /usr/libexec/udisks2/udisksd -rd
[sudo] password for root: 
udisks-Message: 13:18:40.248: udisks daemon version 2.10.0 starting
udisks-Message: 13:18:40.388: Acquired the name org.freedesktop.UDisks2 on the system message bus

(udisksd:27562): udisks-CRITICAL **: 13:18:58.130: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sda': Unexpected sense data returned:
0000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
0010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................
 (g-io-error-quark, 0)
^Cudisks-Message: 13:19:28.939: udisks daemon version 2.10.0 exiting
gerry@Unknown-18-c0-4d-6a-ed-f9:~>
28

Some reading: udisks - ArchWiki See also man udisksctl.

29

Thank you. However, having read the wiki I do not know what to do further. I did not see any information that looked relevant.

All I have done is update Tumbleweed. The older version of Tumbleweed works as usual.

Does this not point to a problem in udisks?

30

When you have a clear case of such a regression, then a report on Bugzilla should be next step.

31

Ah, I’ll investigate how to do this

32

https://bugzilla.opensuse.org/index.cgi
SAme username/password as here.

Explanation: openSUSE:Submitting bug reports - openSUSE Wiki

33

It could be either udisks or the drive. What is the model:

erlangen:/Crucial # inxi -Dy222
Drives:    Local Storage: total: 9.1 TiB used: 4.05 TiB (44.5%)
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 2TB size: 1.82 TiB
           ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO Plus 2TB size: 1.82 TiB
           ID-3: /dev/sda vendor: Crucial model: CT2000BX500SSD1 size: 1.82 TiB

           ID-4: /dev/sdb vendor: Crucial model: CT4000P3 SSD8 size: 3.64 TiB type: USB !!!!!!!!!!!!!!!!!!!!!!!!!!!

erlangen:/Crucial #
34

When it worked with this hardware in an earlier Tumbleweed, what is more likely the problem: the software or the type of the model of the hardware?

35

To confirm: the drive (a Samsung EVO in a SABRENT caddy) works perfectly in another machine running an earlier version of Tumbleweed

36

Worked some decades as an engineer for a living. Always excluded all possibilities regardless of probabilities. After retiring I stick to what worked in those days.

BTW: ispace meint Ursache für Hakuto-Absturz gefunden zu haben » Go for Launch » SciLogs - Wissenschaftsblogs

Karl Mistelberger, 05/30/2023, 1:44 PM

A robust mission concept should provide at least one complete orbit in the eccentric orbit.

True enough!

“I assume that …” explained me so often the work colleagues after they had fallen on nose and in their perplexity asked me for advice.

The riddle’s solution was always in the assumptions, where else. It seems to have been similar with Hakuto-R M1.

38

Engagement with the bugzilla team produced an updated test case udisks2 and which solved the problem. I assume it will be mainstreamed in due course.

1 Like
39

Good action. Congratulations.

40

Great!

A courtesy to the readers of this thread:

Thomas Blume says at 1216055 – udisk2 is preventing a USB drive

"The error in the logs looks like: Issue with kde plasma and udisks 2.10 · Issue #1139 · storaged-project/udisks · GitHub

It should be fixed by: udiskslinuxfilesystem: Use ID_FS_SIZE for filesystems that are not known to report ID_FS_LASTBLOCK by tbzatek · Pull Request #1162 · storaged-project/udisks · GitHub"

A lengthy discussion upon whether to use FSLASTBLOCK or FSSIZE is attached to the above pull request. Coders still rely on shaky assumptions. In some cases no improvement occurred since decades.

BTW: On infamous host erlangen disks detected by udisk which needn’t show up in the GUI are hidden by a rule such as:

erlangen:~ # cat /etc/udev/rules.d/61-hide-partitions.rules 
SUBSYSTEM=="block", ENV{ID_FS_UUID}=="47e6d9ee-e910-4ea4-8c8f-7ac75f49a4d3", ENV{UDISKS_IGNORE}="1"
erlangen:~ #

You never know all the bugs lurking in udisk.

1 Like