Ubuntu
udisks2 package

udisks2 daemon fails to start

Bug #2031096 reported by Paul Dooley on 2023-08-11

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	udisks	New	Unknown	auto-github-storaged-project-udisks #1139
	udisks2 (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

udisks2 2.10.0 fails to start in Ubuntu Mantic (23.10)

Error status is:

Aug 11 10:36:37 nodename systemd[1]: Starting udisks2.service - Disk Manager...
Aug 11 10:36:37 nodename udisksd[232247]: udisks daemon version 2.10.0 starting
Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o>
Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o>
Aug 11 10:36:38 nodename udisksd[232247]: *** stack smashing detected ***: terminated
Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT
Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Failed with result 'core-dump'.
Aug 11 10:36:38 nodename systemd[1]: Failed to start udisks2.service - Disk Manager.

This bug seems to refer: https://github.com/storaged-project/udisks/issues/1139

Bug Watch Updater (bug-watch-updater) on 2023-08-11

Changed in udisks:
status:	Unknown → New

Revision history for this message

Launchpad Janitor (janitor) wrote on 2023-09-01:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in udisks2 (Ubuntu):
status:	New → Confirmed

Revision history for this message

Paul Smith (cvpsmith) wrote on 2023-09-01:

Same. This is on a machine with several nvme and sata SSDs. Oddly enough, I upgraded my laptop (which has a single nvme SSD) and have had no problems.

journalctl -xeu udisks2.service output:

Sep 01 03:03:59 case udisksd[6200]: udisks daemon version 2.10.0 starting
Sep 01 03:03:59 case udisksd[6200]: *** stack smashing detected ***: terminated
Sep 01 03:03:59 case systemd[1]: udisks2.service: Main process exited, code=killed, status=6/ABRT
Sep 01 03:03:59 case systemd[1]: udisks2.service: Failed with result 'signal'.
Sep 01 03:03:59 case systemd[1]: Failed to start udisks2.service - Disk Manager.
cvpsmith@case:~$ journalctl -xeu udisks2.service
Sep 01 03:03:59 case udisksd[6200]: *** stack smashing detected ***: terminated
Sep 01 03:03:59 case systemd[1]: udisks2.service: Main process exited, code=killed, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit udisks2.service has exited.
░░
░░ The process' exit code is 'killed' and its exit status is 6.
Sep 01 03:03:59 case systemd[1]: udisks2.service: Failed with result 'signal'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit udisks2.service has entered the 'failed' state with result 'signal'.
Sep 01 03:03:59 case systemd[1]: Failed to start udisks2.service - Disk Manager.
░░ Subject: A start job for unit udisks2.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit udisks2.service has finished with a failure.
░░
░░ The job identifier is 3124 and the job result is failed.

Revision history for this message

David White (cppege-david-9ei9ny) wrote on 2023-10-18:

I'm getting the same stack smashing fault with udiskd on my Dell XPS 15 7590 with an SSD drive. This fault prevents any external storage from mounting which affects my backup HDD and all USB pen drives.