@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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878890
Title:
[Ubuntu Server 20.04 LTS]: Failed Install
(subiquity...install_fail/add_info) during partitioning
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1878890/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
