[17:45] <richd> hi. Trying to install ubuntu 22.04.2, and it errors out while trying to probe for block devices.  In days of old, it was pretty simple to tell the installer which block device to install to, but I don't see any such options now.  The block device I would like to install to is all present and accounted for when I go to the command prompt, but the installer can't seem to find anything
[17:46] <ahasenack> the 23.04 installed has this issue, it won't see /dev/mapper/* devices
[17:46] <ahasenack> is that your case? /dev/mapper/* devices?
[17:48] <richd> i have /dev/mapper/control, that's all.  /dev/sda is there, and 'lsblk' shows sda, but no block devices in /dev/mapper
[17:48] <ahasenack> then it's not what I was thinking, and I haven't seen this before
[17:49] <ahasenack> is /dev/sda a device you added after having started the installer?
[17:49] <ahasenack> iirc /dev/sda is *the* installer media usually
[17:50] <richd> no.../dev/sda is a hardware raid that I can partition with parted, but even after partitioning, rebooting, and restarting the installer, it still fails while probing block devices.
[17:51] <ahasenack> can you partition and access it from a shell within the live installer environment?
[17:51] <richd> (the additional /dev/sda1, sda2, etc... do survive a reboot)
[17:51] <richd> yes
[17:51] <ahasenack> the installer sees /dev/sda1 (example), but not /dev/sda?
[17:52] <ahasenack> what do you mean by "sda1 sda2 survive a reboot"
[17:52] <richd> ...
[17:52] <richd> ok so the installer fails, then offers a command prompt...
[17:53] <richd> I can partition /dev/sda and create partitions
[17:53] <ahasenack> the installer fails before the partitioning step?
[17:53] <richd> those partitions are still there after a reboot
[17:53] <richd> the installer still fails while probing for block devices
[17:53] <ahasenack> ok, so if it's actually a crash/hard error, then the logs would be useful
[17:54] <richd> i don't know how to instruct the installer to install to "/dev/sda1" or whatever
[17:54] <ahasenack> I don't remember from memory, but they should be in /var/log somewhere
[17:54] <richd> they are.
[17:55] <ahasenack> they are even saved to the permanent storage part of the pendrive, so you can insert it into another system and have access to them to file a bug
[17:57] <ahasenack> if you could file a bug here (https://bugs.launchpad.net/subiquity/+filebug) and attach them, that would be useful
[17:57] <richd> The command prompt is functional enough to scp the logs to another machine.  t
[17:57] <ahasenack> that works too
[17:58] <richd>  here's a highlight: probert.multipath:52 Failed to parse multipath maps entry: ok: __new__() missing 2 required p
[17:58] <richd> ositional arguments: 'sysfs' and 'paths'
[17:58] <ahasenack> yeah, that sounds like a bug allright
[17:59] <ahasenack> quick search for "multipath" doesn't show existing bugs
[18:00] <richd> whatever "curtin" is, it seems to be pretty fixated on whether or not block devices are multipath
[18:00] <richd> curtin:73 /dev/sda is multipath device member? False
[18:01] <richd> and on, and on...
[18:03] <ahasenack> curtin is the installer backend
[18:08] <ahasenack> were you prompted for a newer version of the installer at the beginning?
[18:08] <richd> no.
[18:09] <ahasenack> what does "snap info subiquity" give you in a command line inside the installer, if you still have that available?
[18:09] <ahasenack> it should list some versions
[18:09] <ahasenack> you *could* try a different version (even older)
[18:09] <ahasenack> although I don't remember if downgrading is supported. Upgrading definitely is.
[18:09] <richd> checking...
[18:12] <richd> ahasenack: installed:          23.02.1
[18:13] <richd> snap-id:      ba2aj8guta0zSRlT3QM5aJNAUXPlBtf9
[18:13] <richd> tracking:     latest/stable/ubuntu-22.04.2
[18:13] <richd> refresh-date: 59 days ago, at 17:26 UTC
[18:13] <ahasenack> you could try candidate perhaps, did you see that listed?
[18:13] <richd> latest/candidate: 23.04.1                  2023-04-17 (4699) 19MB classic
[18:13] <richd> ?
[18:14] <ahasenack> to try it, run `sudo snap refresh --channel=latest/candidate subiquity`
[18:14] <ahasenack> I think it would be best to run that right after a reboot, when you are at the very first installer page
[18:16] <richd> ok...it will take a while, the boot time is not fast.
[18:16] <ahasenack> bit metal box, fans like propelers?
[18:16] <ahasenack> big*
[18:16] <richd> "contact!"
[18:16] <ahasenack> "prop clear!"
[18:17] <richd> ooooh....I just typed "subiquity" to see what would happen, and I have been presented with "Guided storage configuration"
[18:19] <ahasenack> ymmv
[18:21] <richd> seems to be working.
[18:23] <richd> certainly better than before.
[18:40] <richd> ahasenack: so far, so good.  It installed, rebooted, and [fingers crossed] all seems well.
[18:40] <ahasenack> interesting