bazzite: Installation failed
Describe the bug
When installing the OS it fails with the command “ostree container image deploy --sysroot=/mnt/sysimage --image=/run/install/repo/bazzite/nvidia-stable --transport=oci --no-signature-verification” exited with the code 1;
What did you expect to happen?
For it to successfully install
Output of rpm-ostree status
No response
Hardware
No response
Extra information or context
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 11
- Comments: 54 (1 by maintainers)
It was a brand new disk, I told the installer to take the whole thing and do what it wants with it…
I’ve never seen a Linux install fail after doing that before.
The maintainers are eager to some day replace the upstream legacy Fedora installer which causes this issue. The solution to that error as it currently stands is often to just try again.
I see a similar problem with the latest iso. I see these errors in the logs:
The error I see happens in the post-install step when the
ostree admin instutil set-kargs rhgb quiet root=UUID=a0e6fbbc-e44c-494c-b1cc-1faacc386b57 rootflags=subvol=@bazzite rwcommand is run. This outputs the following error:I had to create a EFI partition that lives only for Bazzite (or Bluefin or Aurora). Even if there’s already a partition on the disk, I had to create another one. Fedora really hates to see multiboot computers.
My penny’s worth.
Really new to Linux, My Laptop is a bog standard Intel board from China. Everything thus far from the great many Distros have installed on it. I’m installing from an ISO downloaded direct from the website, where I also get …
“ostree container image deploy --sysroot=/mnt/sysimage --image=/run/install/repo/bazzite/nvidia-stable --transport=oci --no-signature-verification” exited with the code 1;
There’s not a lot I can do with the installer, apart from running the system checker option, but even that doesn’t get past this installation error.
NOTE: blank disk install, no update or duel boot. Flustered, really wanted this to work.
i just had this issue as well and it was due to me attempting to reinstall without properly deleting the EFI entries for the previous installation.
I had just installed a dual boot of bazzite with windows but got stuck at a black screen. I was able to access the terminal but unable to login with my username and pw set during the install.
After trying to reinstall i got the exact error shown above.
I was able to fix it by booting into windows and using the
diskparttool to delete the EFI boot entry for fedora on my boot partition instructed in the following posthttps://askubuntu.com/questions/429610/uninstall-grub-and-use-windows-bootloader
I would recommend following the “ISO Workarounds / Alternative Installation Methods” section in the installation guide and try method 1. Use the Fedora Kinoite (KDE Plasma) or Fedora Silverblue (GNOME) ISO and rebase.
This issue has been plaguing us since the creation of the ISOs. We are aware of this issue and are actively working on a replacement effort for the existing install process. This is unfortunately an upstream issue with Anaconda and until we have a replacement ready, there is not a lot we can do.
This is not the OS but the extremely picky Fedora installer. Did you do manual partitioning or something else? The issue seems to be that the installer wants a specific disk layout. Your disk should be set up as GPT and the partition map needed is outlined above somewhere and needs to be like this:
The subvolume mount points are created differently than the other partitions and are part of the btrfs container. A couple of people (including me) had the error because of the EFI partition. It needs to be 300MiB or larger and have the proper mount point. Good luck.
…it just occurred to me that this could be a case of distinguishing between MB and MiB where 300MB is only 286MiB. Not sure which unit the Fedora installer uses but setting the EFI size to 316 (either unit) might solve.
Progress! Glad to hear at least the installation itself worked. Preaching to the choir about it being a pain; I couldn’t count how many times I went through that manual partitioning scheme to map out how to do it.
BIOS update sounds good. I’ll try to remember to keep an eye out for another issue in case it doesn’t work. Worst case, the last thing I can think of right now to try would be making a fully separate second EFI partition for Bazzite. It looks like it shouldn’t work, but it can, and it makes some extra things possible.
I ran into this issue on a disk that had Windows previously.
This is what solved the issue for me:
This doesn’t help. I literally have a brand new UEFI partition on the disk, formatted through Bazzite’s installer.
Actually Fedora Atomic KDE has the same issue, so they might just “hate” my laptop.
You can switch to another terminal when the install starts and use
efibootmgrto help with this. (Ctrl-alt-f2 – installer is in f6)List boot entries with
Then remove the offending entry with
If you are re-using an efi system partition, might be prudent to clear out things related to Fedora as well. Take care when cleaning up. When in doubt, backup/rename instead of delete.
What would be the solution for those who did not dual boot and have wiped our disk of Windows? I tried using fdisk/diskpart to completely wipe my drive, still no dice.