Bugzilla – Bug 1222922
[UDISKS2 BUG] Error getting loopX information after boot
Last modified: 2024-06-19 07:49:56 UTC
Summary: After possibly kernel update to 6.8.4-rc1 and newer (don't know clearly) in logs I found some strange strings about error in finding loop devices. For example: Apr 17 00:19:49 lalala udisksd[1441]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 2) Apr 17 00:19:49 lalala udisksd[1441]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 2) Apr 17 00:19:49 lalala udisksd[1441]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 2) Possible fix: appstream Udisks released version 2.10.1 with fix. Fix is: https://github.com/storaged-project/udisks/pull/1148 It need libblockdev commit, but as I see, libblockdev commit has been included in the code for a long time ago. So, can we update udisks, if its possible?
(In reply to Egor Kuznetsov from comment #0) > Possible fix: appstream Udisks released version 2.10.1 with fix. Fix is: > https://github.com/storaged-project/udisks/pull/1148 > It need libblockdev commit, but as I see, libblockdev commit has been > included in the code for a long time ago. So, can we update udisks, if its > possible? Thanks for the report. An update to udisks version 2.10.1 has been submitted.
closing