Fatal error installation aborted - exited with code 1
Hello! Trying to install Bazzite (dual boot) on my legion go. I already have a partion on the ssd with windows running and attempting to install bazzite using this guide: https://www.youtube.com/watch?v=OjqihbOrErM&t=720s
I get the error in the picture when attempting to install.
I followed his steps (except TDP settings) and disabled safe boot + his partitioning segment.
Deck Wizard
YouTube
SteamOS Legion GO Dual Boot - Bazzite & Windows 11 | Steam Deck OS
How To Dual Boot Lenovo Legion GO With SteamOS Bazzite & Windows 11 - 2025 Guide
❤️ Subscribe - https://www.youtube.com/@DeckWizard
00:00 - Introduction
00:56 - What We Need
01:27 - Download Required Files
02:23 - Create Bazzite USB
03:14 - Partition Drive
04:57 - Update Legion GO BIOS to 35WW
05:51 - 2x BIOS Menu Important Changes
07:09 - Ba...
8 Replies
I have also flashed another USB with the Bazzite ISO, to see if it was because of the USB itself.
Trying to follow the troubleshooting guide found on the official site, but i am even stuck here.
Nothing seems to be mounted inside the /mnt/efi
So I currently cant find other suggestion for troubleshooting
Currently attempting to use automatic partioning instead of manual
It still fails with the same error…
Did you resolve the issue? I've attempted to install four different versions of Bazzite along with Fedora on both my desktop and laptop and I always get an exit code 1.
Mike's Tech Tips
YouTube
Getting around the "Code 1" error in Bazzite and other Atomic Deskt...
In this guide we'll be removing the invalid fedora entry in the efi partition to get Bazzite and other atomic desktops to install after attempting to reinstall them. (fixed the audio)
Edit: Note that you might also get this error if you previously installed Fedora workstation or Nobara and you have kept your existing efi partition on the disk.
...
this should help
@Rin It did not, I get an error
mount: /mnt/efi= fsconfig system call failed: /dev/sda1= Can't open blockdev. dmesg(1) may have more information after failed mount system call.I'm seeing the same exact thing. I was previously using the drive for a Debian install. Tried a few different USB drives and tried a secure erase through the MSI startup but that didn't help. Maybe I'm missing something obvious.