Comment 2 for bug 2031096

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.