> PS: how can you run asciinema within the installer?
I cheated and used developer tools :)
(`make dryrun` in the source tree if you're interested)
To simulate that with the real installer the easiest thing would be to
SSH into the install and capture the SSHed terminal.
--
You received this bu
Thanks again for the logs Fernan, I now believe I understand what
happened.
About your item #1 ("starting with fresh disks")
It's our expectation that most people will, when faced with a blank disk or one
they are reformatting, will use the "Add Partition" on the "Free Space" area
under a disk t
Hi Dan, thanks for the fast response. No, the disks where clean. I just
started fresh (from zero!) using the VMWAre Vsphere Client.
New VM
-> Add HDD (Create New Virtual Disk, Thick Provision Lazy Zeroed, Store with
the VM, 50 GB
SCSI (0:0) Hard Disk 1)
-> Add HDD (Create New Virtual Di
Thanks for attaching the installer files. Unfortunately the subiquity-
server-debug.log is actually a symlink to the real log file, so all we
got was an empty symlink.
That said, I can reproduce part of what's going on with the probe-data.
Where I'm confused is the initial state - I think maybe t
Of course! Please let me know if you need more files or further
debugging.
** Attachment added: "requested /var/log/installer files"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1969822/+attachment/5582190/+files/var-log-installer-files.tar.gz
--
You received this bug notification
Thanks for the report.
> However there is nothing I can do to select one! (the option to "Use
As Boot Device" is greyed out).
Up through that part sounds correct - there needs to be a little space
to setup for a boot disk and there isn't, so you made the right choice
to go backwards a bit and for
Moreover, if I go to a shell and format the disks, when I go back to the
installer, and hit "Reset" the system recognizes the changes, and shows
the disks as "already formatted as ext4", with "partition 1 existing",
"not mounted", and with a message saying:
"To continue you need to: Mount a filesy
** Also affects: subiquity
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969822
Title:
fa
