subiquity

  1. Bug #1878890
  2. Comment #22

Comment 22 for bug 1878890

Revision history for this message
Kai Harrekilde-Petersen (kaihp) wrote :

@Ryan

I booted the server into the 20.04 installer and copied off the /var/log directory.
/var/log/installer/subiquity-debug.log.3179 ends with:

2020-06-02 21:22:21,793 INFO root:39 start: subiquity/Filesystem: starting UI
2020-06-02 21:22:21,793 DEBUG root:39 start: subiquity/Filesystem/convert_autoinstall_config:
2020-06-02 21:22:21,794 DEBUG subiquitycore.controller.filesystem:170 self.ai_data = {}
2020-06-02 21:22:21,794 DEBUG root:39 finish: subiquity/Filesystem/convert_autoinstall_config: SUCCESS:
2020-06-02 21:22:44,255 DEBUG subiquity.ui.filesystem.filesystem:314 _action DeviceAction.EDIT partition-sda1
2020-06-02 21:23:05,415 DEBUG subiquity.ui.filesystem.filesystem:314 _action DeviceAction.EDIT partition-sda3

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.