Hello!
I tried Atomic Workstation but I aways have problems with the end process of the installation. In the machines I tested it always have problems with grub. Never installs it, in any version I’ve tried.
1 Like
Could you provide any kind of error output or logs from a failed install?
2 Likes
Hi!
Trying to run the installation again and now it didn’t even finish. Error that I think I had with 28 either:
My language is Portuguese (Brazil):
The following error ocurred during the installation. This is fatal and the installation will be aborted.
ostree [‘admin’, ‘-sysroot=/mnt/sysimage’,‘deploy’,‘–os=fedora-workstation’, ‘fedora-workstation:fedora/29/x86_64/silverblue’’ exited with code -6
In Fedora Atomic Workstation 28 I also had the no grub problem.
1 Like
Are you using the manual partition setup or automatic? BTRFS or LVM? If you hit Ctrl+Alt+F1 and then Ctrl+b followed by 5, take you post what you see? Any errors?
1 Like
Hi!
@miabbott tested today on may very old machine (atom processor, 2GB RAM) without UEFI/EFI and it passed.
@refi64 I used automatic partitioning with ext4. I will try what you suggested.
Hello, i have the following message when anaconda tries to install the bootloader:
Dec 03 08:37:32 noname anaconda[1881]: anaconda: progress: Installing boot loader
Dec 03 08:37:32 noname anaconda[1881]: anaconda: installation: Task started: Install bootloader (17/18)
Dec 03 08:37:32 noname anaconda[1881]: anaconda: bootloader: boot loader stage1 target device is sdc
Dec 03 08:37:32 noname anaconda[1881]: anaconda: bootloader: boot loader stage2 target device is sdc4
Dec 03 08:37:32 noname anaconda[1881]: anaconda: bootloader: bootloader.py: used boot args: resume=UUID=3b6b2883-64b9-4561-af0a-8df250737997 rhgb quiet
Dec 03 08:37:32 noname anaconda[1881]: program: Running in chroot '/mnt/sysimage/ostree/deploy/fedora-workstation/deploy/e4ffb947091f5f9e85cd6a3adfc24583d3d8b25d0590b2d8058c4bb48a14c287.0'... grub2-mkconfig -o /boot/grub2/grub.cfg
Dec 03 08:37:36 noname anaconda[1881]: program: /usr/bin/grub2-editenv: error: cannot open `/boot/grub2/grubenv.new': No such file or directory.
Dec 03 08:37:36 noname anaconda[1881]: program: /sbin/grub2-mkconfig: line 268: /boot/grub2/grub.cfg.new: No such file or directory
Dec 03 08:37:36 noname anaconda[1881]: program: Return code: 1
Dec 03 08:37:36 noname anaconda[1881]: anaconda: bootloader: bootloader.write failed: failed to write boot loader configuration
Screenshots and journalctl there → https://workupload.com/archive/UtzBdAP
How can i get it to work?
1 Like
Manual or automatic partitioning?
1 Like
Manual without home, / is on /dev/sdc4. GRUB on sdc + bios_grub sdc1. But whatever i try, it is not working with a separate /home on /dev/sdc6 either.
1 Like
Are you remembering to create /boot? Have you tried going to manual partitioning, select the option to auto-create partitions, and then manually adjusting them to how you want?
1 Like
Been getting the same error for the past couple days:
Dec 03 08:37:36 noname anaconda[1881]: program: /sbin/grub2-mkconfig: line 268: /boot/grub2/grub.cfg.new: No such file or directory
In addition, the installer is creating nested directories: /boot/efi/EFI/EFI...
I have tried with automatic partitioning as well as with manual partitioning - same error.
Screenshots
3 Likes
Are you dual booting? If not, can you try deleting the ESP and installing again? If you are, can you try selecting manual partitioning → hit the button to create the partitions → remove the /boot/efi mount point and re-create it as a new partition?
1 Like
Well, in my case, i got it to work on /dev/sda with default options. But that SSD was due for a secure erase, so … yeah. I dont want Silverblue on /dev/sda. I will happily wait another two years until the Silverblue team got their anaconda sorted out, so i can finally install it on /dev/sdc4 with multiboot.
1 Like
Every time I try to install Silverblue on a drive with pre-existing EFI partition (dual booting), I get the message “failed to write boot loader configuration”. The installation log is showing the same above messages, and I confirm the nested directories /boot/efi/EFI/EFI... too. Is this a known bug for Anaconda?
If anyone is interested, this worked for me:
Run this from the shell when the error dialog box comes up, and then ignore the error and continue the installation (replace <deploy_id>.0 with the existing folder):
chroot /mnt/sysimage/ostree/deploy/fedora-workstation/deploy/<deploy_id>.0 /bin/sh
mv /boot/efi/EFI/EFI/* /boot/efi/EFI
rm -r /boot/efi/EFI/EFI
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
exit
4 Likes
It might be this one: https://bugzilla.redhat.com/show_bug.cgi?id=1168118
I ran into it trying to install Fedora Workstation 29 on my laptop. Said laptop is currently dual-booted Antergos Linux and Windows 10 Pro, so I know dual-booting is possible. It also was dual-booted with Ubuntu 18.04 at one time.
Any Anaconda experts here?
1 Like
Hmm that doesn’t seem like the same bug, I recognized @erubio0’s case as one I ran into as well that’s Silverblue-specific. IIRC Anaconda just copies the EFI directory without checking if it’s already present in the ostree variant?
1 Like
¿You know? You saved my day. This bug seems a little bit absurd TBH.
FTR to enter shell: Ctrl+Alt+F1; then Ctrl+B 2
1 Like
After doing this and finally having a working Fedora Silverblue, the grub screen doesn’t use any default value. I always have to select one deployment. Any suggestions to fix that?
Also I have:
Fedora 31.20191220.0 (Workstation Edition) (ostree:0)
Fedora 31.1.9 (Workstation Edition) (ostree:1)
I have no idea on which one is the good one, or what do ostree:1/0 mean… wasn’t it supposed to be using ostree always? 
1 Like
Hello @yajo, Welcome to the discussion.
The commits are listed from newest to oldest so 0 is the newest (an default selection) and 1 is the previous commit. The commits are always Ostree, what you are seeing is the variant of Fedora used for Silverblue (Workstation).
I too see the most recent commits at Grub menu, if I wait the most recent one boots, or I can select which one, there is time (~5 seconds in my case).
2 Likes
Thanks for your replies 
Yes, but in my case it will never choose one automatically, no matter what I do.
1 Like
Sorry @yajo, I have been away for a bit. Did you solve your problem with Grub? If so could you comment about the solution here for future info, and if not let’s see what we can figure out.
1 Like