Installation failed

[InfiniteCod3]

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

[uzernamee]

Same problem.
RTX 3090, Ryzen 5900x on a x570 motherboard.
Fedora 40 installed correctly.

[nicknamenamenick]

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.

[AwkwaBear]

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 diskpart tool to delete the EFI boot entry for fedora on my boot partition instructed in the following post

https://askubuntu.com/questions/429610/uninstall-grub-and-use-windows-bootloader

[Daxiongmao87]

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 diskpart tool to delete the EFI boot entry for fedora on my boot partition instructed in the following post

https://askubuntu.com/questions/429610/uninstall-grub-and-use-windows-bootloader

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.

[liaralabs]

You can switch to another terminal when the install starts and use efibootmgr to help with this. (Ctrl-alt-f2 -- installer is in f6)

List boot entries with

efibootmgr

Then remove the offending entry with

efibootmgr -b <bootnum> -B

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.

[alexeiz]

I have no "offending" entries in the EFI boot list and still get this error.

[shishimaru90]

I have no "offending" entries in the EFI boot list and still get this error.

Same here.

Honestly terrible.

[CossmicMussel]

Hello fellow nerds,

Believe I found out how to fix this issue at least for my scenario, it was an issue with EFI boot stuff, however the command with in installer did not work.

Answer:
My main operating system is windows so I used this app called easyUEFI on windows to completely rebuild my EFI boot, once I did this I was able to install with no issues. I’m sure there’s equivalents to easyUEFI on other OS’s.

[liaralabs]

If you aren't dual booting, you can try wiping the ESP and letting the installer create it. Otherwise, mount the ESP and look for 'fedora' directories and delete them (assuming you aren't trying to dual boot with an existing fedora installation)

[shishimaru90]

If you aren't dual booting, you can try wiping the ESP and letting the installer create it. Otherwise, mount the ESP and look for 'fedora' directories and delete them (assuming you aren't trying to dual boot with an existing fedora installation)

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.

[Saschabrix]

I have the same issue.
With my AYANEO Next device.

Main NVME is populated with an 2TB Nvme.
Installing Bazzite on an external SSD.

I tried twice, it failed twice.

Will wait a couple of moth more and try again.

[jnfDev]

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 diskpart tool to delete the EFI boot entry for fedora on my boot partition instructed in the following post

https://askubuntu.com/questions/429610/uninstall-grub-and-use-windows-bootloader

This worked for me thanks

[shishimaru90]

The new based on 41 failed too.

• I completely deleted the UEFI partition
• I created a new one and set mount point to /boot/efi (is this correct?)
• format'd and set as / another btrfs partition

And still doesn't work.

Any chance to get a proper offline iso? I even tried with wifi 5ghz, with ethernet cable... I don't know what to try anymore to be honest. It's definitely not a safe installation method since it can fail so easily, format your disk, and find yourself without a working system.

[Zeglius]

The new based on 41 failed too.

• I completely deleted the UEFI partition
• I created a new one and set mount point to /boot/efi (is this correct?)
• format'd and set as / another btrfs partition

And still doesn't work.

Any chance to get a proper offline iso? I even tried with wifi 5ghz, with ethernet cable... I don't know what to try anymore to be honest. It's definitely not a safe installation method since it can fail so easily, format your disk, and find yourself without a working system.

The iso is already offline, no internet access is required other than for downloading the iso itself.

The problem is anaconda is not working 100%. I hope the new web based installer works better. 🤞

[marcdraco]

Happened to me on a Lenovo Legion.

Good news is the EFI fix worked for me.

Bad news is that (although Windows was still there) I got into a mess trying to install the MDK do-dads for the Shim (I assume) and now .... NO Microsoft Windows. Presumably this means fixing it elsewhere but that was the most painful install I've done since the SLACKWARE days. This is poor when compared to many (most?) "popular" distros these days.

I'm very surprised at Fedora to be honest but at least we're not paying for it, so there's that.

[terry9336]

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.

[shishimaru90]

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.

[marcdraco]

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 ..

NOTE: blank disk install, no update or duel boot. Flustered, really wanted this to work.

Oh man I felt that. I managed to wipe my Windows install (which isn't necessarily a bad thing) and I've been using Linux for decades now. I guess we're mostly used to fairly robust installers that don't mess around like this thing does. I love the idea of an atomic desktop but Clear Linux seems to do that without this carry on...

In my case it was the EFI partition - not that the installer seems to give us any clue at all. You'll need 2-300 Mb for the EFI rubbish but try doing that manually in Blivet and reserving the remaining disk space for BTRFS. I had to turn off secure boot and got myself

I think Blivet is the name of the partitioner, I'm a Debian12 guy normally - and mean Debian not Ubuntu. I haven't used Fedora much in ... years. And here we are - at least I finally got mine working. I only wanted to run my Steam Deck games without the hassle and... that failed spectacularly so far. Which means I'm having to reinstall stuff until I have time to figure out how to mount the same physical library on multiple machines.

[antonio0831]

Same issue. The EFI fix didn't work for me

[shishimaru90]

This is what worked for me:

• on the same disk, no shared systems (only works if OSs are on different disks)
• this means that it must have its own EFI partition. Don't share it.
• I don't know why, but if I prepare the partitions in advance and/or if I format them and use mount points, the installation fails...
• ...so I resolved like this: erased all the partitions, recreated them in Anaconda AND also added a /boot partition (I used ext2). If I don't create a /boot partition, it just doesn't work, I don't know why.

Now you'd ask why I just didn't use the automatic installation. It's because I have a big partition with data on it and I need it on that partition, so I had to go with the manual setup.

Quick example. I had big data partition, root partition, home partition, efi partition. I booted Bazzite installer, left the first partition alone, deleted all the others, recreated them (and also created /boot), done.

[Blockzilla101]

I'm having the same problem, the suggestions from previous commenters did not work for me. (at least ones I can try without losing data)

For context, I wanted to switch from arch to this and have a dual boot setup. I used manual partitioning & booted the iso using ventoy (incase that has something to do with it).

I configured the partitions to basically what I had previously but only making the installer overwrite my root partition. Didn't work. Tried again with the efi partition nuked & recreated it to 500mb, still didn't work.

• Partition Setup:
  • 2 NTFS partitions (windows + windows data)
  • ext4 /home
  • ext4 /
  • fat32 /boot/efi

I cannot switch to btrfs as the guide suggested as I do not have a spare drive to backup my data. I also didn't know about their partition suggestion until after I gave up.

[drstrider]

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.

It looks like that page has been deleted, does anyone know what it said? I'm blocked by this bug too 😔

[pieterlexis]

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 rw command is run. This outputs the following error:

Unable to find a deployment in sysroot

[LaercioSantana]

I was with the same error here. I found that atomic images need a separated partition for /boot.

So we need adds a minimum of 3 mount points to make it works: /boot/efi, /boot and /

What I did:

/boot ext4 2gb
/boot/efi EFI system 2gb
/ Btrfs 80gb
/home ext4 100gb

For reference:
https://discussion.fedoraproject.org/t/fedora-kinoite-40-install-always-fail-when-installing-bootloader/116688/10

fedora-silverblue/issue-tracker#284 (comment)

[nefarius]

Same issue I ran into. I had the /boot/efi partition on NVME 1 (where Windows was before) and my Linux install on NVME 0, so I migrated the EFI from NVME 1 to NVME 0, completely wiped NVME 1 and put Bazzite on it and then it installed without issues.