New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[issue]: Ubuntu 21.10 Beta - "Failed to start default target" #1131
Comments
Can it boot ok if you don't use LUKS and ZFS (use the default configuration). |
Did some further testing (same setup 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. |
Ubuntu 21.10 Release, after Ventoy 1.0.54 and then Ubuntu Grub menu:
|
Did you boot by vdisk or just directly boot the ubuntu 21.10.iso by Ventoy? |
I'm sorry, my iso is corrupt somehow. All works as it should.
|
It works the change the uefi to enable on security boot good bye |
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:
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
The text was updated successfully, but these errors were encountered: