The subiquity-info.log file just reports that it has started the filesystem stuff:
2020-06-02 21:22:21,793 INFO root:39 start: subiquity/Filesystem: starting UI
Maybe I should point out that I cannot select /dev/sda1 at all as /boot, but I can select sda3, but just not as root directory.
If you have some kind of emulation environment to test out disk layout scenarios, then now is the time to pull it out.
@Ryan
I booted the server into the 20.04 installer and copied off the /var/log directory. installer/ subiquity- debug.log. 3179 ends with:
/var/log/
2020-06-02 21:22:21,793 INFO root:39 start: subiquity/ Filesystem: starting UI Filesystem/ convert_ autoinstall_ config: controller. filesystem: 170 self.ai_data = {} Filesystem/ convert_ autoinstall_ config: SUCCESS: ui.filesystem. filesystem: 314 _action DeviceAction.EDIT partition-sda1 ui.filesystem. filesystem: 314 _action DeviceAction.EDIT partition-sda3
2020-06-02 21:22:21,793 DEBUG root:39 start: subiquity/
2020-06-02 21:22:21,794 DEBUG subiquitycore.
2020-06-02 21:22:21,794 DEBUG root:39 finish: subiquity/
2020-06-02 21:22:44,255 DEBUG subiquity.
2020-06-02 21:23:05,415 DEBUG subiquity.
The subiquity-info.log file just reports that it has started the filesystem stuff: Filesystem: starting UI
2020-06-02 21:22:21,793 INFO root:39 start: subiquity/
Maybe I should point out that I cannot select /dev/sda1 at all as /boot, but I can select sda3, but just not as root directory.
If you have some kind of emulation environment to test out disk layout scenarios, then now is the time to pull it out.