Menu
I have tried to install three versions of Ubuntu Server (18.04.5, 20.04.2, 21.04) on my Win10 Hyper-V. But all failed at curtin command in-target as the last execution. Can anyone tell me why this happened?
243
An issue with your display driver might cause the Ubiquity to get stuck during the installation prompts. To resolve the issue, you will have to launch Ubuntu in Safe Graphics mode which edits the boot parameters. This has been reported as working by a user who was facing a similar issue.
Overview. Curtin is intended to be a bare bones “installer”. Its goal is to take data from a source, and get it onto disk as quick as possible and then boot it. The key difference from traditional package based installers is that curtin assumes the thing its installing is intelligent and will do the right thing.
Curtin (the curt installer) is a "fast path" installer designed to install Ubuntu quickly. It is blunt, brief, snappish, snippety and unceremonious. In order to closely align with the MAAS product, curtin needs to be periodically updated in order to enable new features.
You can run curtin in-target -- $shell_command (with the version of subiquity released with 20.04 GA you need to specify this as curtin in-target --target=/target -- $shell_command) to run in the target system (similar to how plain in-target can be used in d-i preseed/late_command ). Shell commands to run after the install has failed.
Unlike the installation of Ubuntu Desktop, Ubuntu Server does not include a graphical installation program. Instead, it uses a text menu-based process. If you’d rather install the desktop version, take a look at our Install Ubuntu desktop tutorial. This guide will provide an overview of the installation from either a DVD or a USB flash drive.
This was the first hint at a helpful solution. If you're running Ubuntu server in a VM (Gnome boxes, kvm, libvirt etc) Then remove any attached NIC's before you install the OS. Otherwise install fails with the above error. Not sure why this hasn't been fixed in mainstream.
The issue is caused when multiple network adapters are used. The issue goes away when only one NIC is used. This was the first hint at a helpful solution. If you're running Ubuntu server in a VM (Gnome boxes, kvm, libvirt etc) Then remove any attached NIC's before you install the OS. Otherwise install fails with the above error.
LTS 20.04 In VMWare - disabling network adapter for the installation fixed this issue for me as well. I do not know why as of right now, but it seems to correct the issue. You just have to enable and set up network once it's up and running. If you were trying to access via SSH though, I don't know how you'd get around it.
188
Disable network will solve the problem
2
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
