Ubuntu 24.04 (Noble Numbat) hangs on installation
https://askubuntu.com/questions/1511927/ubuntu-24-04-noble-numbat-hangs-on-installation
I've been trying to install the new Ubuntu 24.04 (Nomble Numbat) on a PC that's been running 22.04 for a while. Observations:
Upon boot from the USB stick it errors out quickly (IIRC "Oh no something went wrong!" but I don't remember exactly).
It seems the new installer is unhappy with something about my disk partitioning (tri-boot: Windows, Debian, and Ubuntu, with the later two sharing LUKS and LVM volumes). If I unlock the LUKS partitions and restart the installer, I get the first screen to select my language, click "Next", and it just spins.
After a bunch of trial-and-error I discovered if I boot a fresh installer and quickly kill it (presumably before it caches some data that contributes to the error), then unlock the LUKS partitions, the installer makes it further but still ultimately hangs. By poking around I found subiquity-server-info.log, which contains:
2024-04-27 00:59:23,292 INFO subiquity:201 Starting Subiquity server revision 171 of snap /snap/ubuntu-desktop-bootstrap/171 of version 0+git.2d119e1b3
2024-04-27 00:59:23,292 INFO subiquity:205 Arguments passed: ['/snap/ubuntu-desktop-bootstrap/171/bin/subiquity/subiquity/cmd/server.py', '--use-os-prober', '--storage-version=2', '--postinst-hooks-dir=/snap/ubuntu-desktop-bootstrap/171/etc/subiquity/postinst.d']
2024-04-27 00:59:25,292 INFO root:38 start: subiquity/apply_autoinstall_config:
2024-04-27 00:59:25,295 INFO root:38 finish: subiquity/apply_autoinstall_config: SUCCESS:
2024-04-27 00:59:25,559 ERROR root:38 finish: subiquity/Refresh/check_for_update: FAIL: cancelled
2024-04-27 00:59:25,598 INFO root:38 start: subiquity/Meta/status_GET:
2024-04-27 00:59:25,599 INFO root:38 finish: subiquity/Meta/status_GET: SUCCESS: 200 {"state": "WAITING", "confirming_tty": "", "error": null, "nonreportable_erro...
2024-04-27 00:59:25,602 INFO root:38 start: subiquity/Meta/client_variant_POST:
2024-04-27 00:59:25,602 INFO root:38 finish: subiquity/Meta/client_variant_POST: SUCCESS: 200 null
2024-04-27 00:59:25,603 INFO root:38 start: subiquity/Meta/status_GET:
2024-04-27 00:59:25,603 INFO root:38 finish: subiquity/Meta/status_GET: SUCCESS: 200 {"state": "WAITING", "confirming_tty": "", "error": null, "nonreportable_erro...
2024-04-27 00:59:25,604 INFO root:38 start: subiquity/Meta/mark_configured_POST:
2024-04-27 00:59:25,605 INFO root:38 finish: subiquity/Meta/mark_configured_POST: SUCCESS: 200 null
2024-04-27 00:59:25,636 ERROR probert.multipath:38 Failed to run cmd: ['multipathd', 'show', 'maps', 'raw', 'format', '%w,%d,%N']
2024-04-27 00:59:25,636 ERROR probert.multipath:38 Failed to run cmd: ['multipathd', 'show', 'paths', 'raw', 'format', '%d,%z,%m,%N,%n,%R,%r,%a']
2024-04-27 00:59:26,190 INFO probert.lvm:120 b' 9 logical volume(s) in volume group "ubuntu-vg" now active\n'
2024-04-27 00:59:26,266 ERROR probert.lvm:225 Found duplicate volume group: ubuntu-vg
2024-04-27 00:59:26,266 ERROR probert.lvm:225 Found duplicate volume group: ubuntu-vg
2024-04-27 00:59:26,266 ERROR probert.lvm:225 Found duplicate volume group: ubuntu-vg
2024-04-27 00:59:26,267 ERROR probert.lvm:225 Found duplicate volume group: ubuntu-vg
2024-04-27 00:59:26,267 ERROR probert.lvm:225 Found duplicate volume group: ubuntu-vg
2024-04-27 00:59:26,267 ERROR probert.lvm:225 Found duplicate volume group: ubuntu-vg
2024-04-27 00:59:26,268 ERROR probert.lvm:225 Found duplicate volume group: ubuntu-vg
2024-04-27 00:59:26,268 ERROR probert.lvm:225 Found duplicate volume group: ubuntu-vg
2024-04-27 00:59:26,364 INFO root:38 start: subiquity/Meta/status_GET:
2024-04-27 00:59:26,364 INFO root:38 finish: subiquity/Meta/status_GET: SUCCESS: 200 {"state": "WAITING", "confirming_tty": "", "error": null, "nonreportable_erro...
2024-04-27 00:59:26,365 INFO root:38 start: subiquity/Meta/status_GET:
2024-04-27 00:59:26,365 INFO root:38 finish: subiquity/Meta/status_GET: SUCCESS: 200 {"state": "WAITING", "confirming_tty": "", "error": null, "nonreportable_erro...
2024-04-27 00:59:26,366 INFO root:38 start: subiquity/Meta/status_GET:
2024-04-27 00:59:26,366 INFO root:38 start: subiquity/Meta/interactive_sections_GET:
2024-04-27 00:59:26,366 INFO root:38 finish: subiquity/Meta/interactive_sections_GET: SUCCESS: 200 null
Any suggestions about how to debug this further and/or work around? I was going to install it over an existing volume, anyway (e.g., wipe my Debian volume), so if I could, for example, run the installer from my 22.04 volume that would at least speed my debugging cycles and make it easier to get logs and screenshots from the installer into bug reports.