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.