Ventoy icon indicating copy to clipboard operation
Ventoy copied to clipboard

[issue]: Ubuntu 21.10 Beta - "Failed to start default target"

Open ak-42 opened this issue 3 years ago • 6 comments

Official FAQ

  • [X] I have checked the official FAQ.

Ventoy Version

1.0.53

What about latest release

Yes. I have tried the latest release, but the bug still exist.

BIOS Mode

UEFI Mode

Partition Style

GPT

Disk Capacity

100GB VHD, 500GB USB 3.1 SSD

Disk Manufacturer

Samsung Portable SSD T5

Image file checksum (if applicable)

Yes.

Image file download link (if applicable)

https://releases.ubuntu.com/21.10/ubuntu-21.10-beta-desktop-amd64.iso

What happened?

When I try to boot Ubuntu 21.10 Beta using vtoyboot mode I get into emergency mode with message "Failed to start default target". Looking through some of the boot text, seems like Ubuntu is failing to find the drives it is expecting.

Steps I took:

  • Created VirtualBox machine with UEFI mode and fixed VHD size of 100GB.
  • Booted and installed Ubuntu 21.10 Beta to the VHD. I used LUKS and ZFS.
  • Rebooted into the VM, updated Ubuntu and after ran latest vtoyboot.sh, no errors received.
  • Renamed the .vhd file on Ventoy device to .vhd.vtoy
  • Rebooted (machine is pure UEFI mode, not mixed or legacy BIOS), selected Ventoy device, selected the image and successfully decrypted LUKS and then the splash hangs and eventually displays "Failed to start default target".

I also get the exact same error with PopOS 21.04, but since Pop is based on Ubuntu, I've decided to report this more generalised version of the issue. The same machine and Ventoy device have no problem with booting Fedora 35 Beta or latest Manjaro.

EDIT: The error message itself suggests to check journalctl -xb so here's that output: https://pb.envs.net/?0f2df5a3b9419bc4#TRxfKDonfgMEPbyALY96b7GU81T5b2NgULMWxenup7Q

ak-42 avatar Oct 09 '21 12:10 ak-42

Can it boot ok if you don't use LUKS and ZFS (use the default configuration). Can it boot ok for Ubuntu LTS 20.04?

ventoy avatar Oct 10 '21 01:10 ventoy

Did some further testing (same setup as above): Ubuntu 21.10 Beta ext4, no LUKS (default) - works Ubuntu 21.10 Beta ext4, with LUKS - works Ubuntu 21.10 Beta ZFS, no LUKS - same issue as above

So, it seems that the culprit is ZFS.

My other Manjaro image is with btrfs and LUKS and working fine, so it seems that there's something about ZFS that does not agree with Ventoy.

EDIT: Also tested Pop!_OS 21.04 with LUKS and ext4 (default) and without LUKS and with ext4 and got the same "Failed to start default target" issue on both tests. So, this might just be two different issues with same symptom.

ak-42 avatar Oct 10 '21 11:10 ak-42

Ubuntu 21.10 Release, after Ventoy 1.0.54 and then Ubuntu Grub menu:

zstd-compressed data is corrupt
System halted.

icher avatar Oct 15 '21 06:10 icher

Ubuntu 21.10 Release, after Ventoy 1.0.54 and then Ubuntu Grub menu:

zstd-compressed data is corrupt
System halted.

Did you boot by vdisk or just directly boot the ubuntu 21.10.iso by Ventoy? I download ubuntu-21.10-desktop-amd64.iso and I can boot into its desktop environment OK.

ventoy avatar Oct 15 '21 09:10 ventoy

Ubuntu 21.10 Release, after Ventoy 1.0.54 and then Ubuntu Grub menu:

zstd-compressed data is corrupt
System halted.

Did you boot by vdisk or just directly boot the ubuntu 21.10.iso by Ventoy? I download ubuntu-21.10-desktop-amd64.iso and I can boot into its desktop environment OK.

I'm sorry, my iso is corrupt somehow. All works as it should.

echo "f8d3ab0faeaecb5d26628ae1aa21c9a13e0a242c381aa08157db8624d574b830 *ubuntu-21.10-desktop-amd64.iso" | shasum -a 256 --check
ubuntu-21.10-desktop-amd64.iso: FAILED
shasum: WARNING: 1 computed checksum did NOT match

icher avatar Oct 15 '21 12:10 icher

It works the change the uefi to enable on security boot good bye

Ssr2412 avatar Feb 16 '24 16:02 Ssr2412