# Cannot install boot loader **URL:** \ **Category:** Project Discussion\ **Tags:** silverblue-team\ **Created:** [October 6, 2018, 4:56pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486 "2018-10-06T16:56:48Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![msmafra](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/msmafra/32/55765_2.png) [@msmafra](https://discussion.fedoraproject.org/u/msmafra)\ **Post date:** [October 6, 2018, 4:56pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/1 "2018-10-06T16:56:48Z")
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. ---
**Author:** ![miabbott](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/miabbott/32/11_2.png) [@miabbott](https://discussion.fedoraproject.org/u/miabbott)\ **Post date:** [October 6, 2018, 9:04pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/2 "2018-10-06T21:04:34Z")
Could you provide any kind of error output or logs from a failed install? ---
**Author:** ![msmafra](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/msmafra/32/55765_2.png) [@msmafra](https://discussion.fedoraproject.org/u/msmafra)\ **Post date:** [October 10, 2018, 2:48pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/3 "2018-10-10T14:48:40Z")
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. ---
**Author:** ![refi64](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/refi64/32/1607_2.png) [@refi64](https://discussion.fedoraproject.org/u/refi64)\ **Post date:** [October 11, 2018, 1:08am UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/4 "2018-10-11T01:08:23Z")
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? ---
**Author:** ![msmafra](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/msmafra/32/55765_2.png) [@msmafra](https://discussion.fedoraproject.org/u/msmafra)\ **Post date:** [October 11, 2018, 2:10am UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/5 "2018-10-11T02:10:01Z")
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. ---
**Author:** ![burni](https://avatars.discourse-cdn.com/v4/letter/b/603e79/32.png) [@burni](https://discussion.fedoraproject.org/u/burni)\ **Post date:** [December 3, 2018, 10:12am UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/6 "2018-12-03T10:12:03Z")
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](https://workupload.com/archive/UtzBdAP) How can i get it to work? ---
**Author:** ![refi64](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/refi64/32/1607_2.png) [@refi64](https://discussion.fedoraproject.org/u/refi64)\ **Post date:** [December 3, 2018, 4:29pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/7 "2018-12-03T16:29:26Z")
Manual or automatic partitioning? ---
**Author:** ![burni](https://avatars.discourse-cdn.com/v4/letter/b/603e79/32.png) [@burni](https://discussion.fedoraproject.org/u/burni)\ **Post date:** [December 3, 2018, 8:54pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/8 "2018-12-03T20:54:37Z")
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. ---
**Author:** ![refi64](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/refi64/32/1607_2.png) [@refi64](https://discussion.fedoraproject.org/u/refi64)\ **Post date:** [December 4, 2018, 4:28am UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/9 "2018-12-04T04:28:51Z")
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? ---
**Author:** ![cpaul](https://avatars.discourse-cdn.com/v4/letter/c/3c6eb4/32.png) [@cpaul](https://discussion.fedoraproject.org/u/cpaul)\ **Post date:** [January 4, 2019, 9:21am UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/10 "2019-01-04T09:21:38Z")
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 > **[G3gaMXW](https://workupload.com/archive/G3gaMXW)** > > Upload documents, images and files for free - without registration. ---
**Author:** ![refi64](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/refi64/32/1607_2.png) [@refi64](https://discussion.fedoraproject.org/u/refi64)\ **Post date:** [January 4, 2019, 4:18pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/11 "2019-01-04T16:18:24Z")
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? ---
**Author:** ![burni](https://avatars.discourse-cdn.com/v4/letter/b/603e79/32.png) [@burni](https://discussion.fedoraproject.org/u/burni)\ **Post date:** [January 15, 2019, 6:19am UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/12 "2019-01-15T06:19:50Z")
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. ---
**Author:** ![erubio0](https://avatars.discourse-cdn.com/v4/letter/e/eb7434/32.png) [@erubio0](https://discussion.fedoraproject.org/u/erubio0)\ **Post date:** [January 21, 2019, 3:34pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/13 "2019-01-21T15:34:20Z")
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 `.0` with the existing folder): ```auto chroot /mnt/sysimage/ostree/deploy/fedora-workstation/deploy/.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 ``` ---
**Author:** ![znmeb](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/znmeb/32/144_2.png) [@znmeb](https://discussion.fedoraproject.org/u/znmeb)\ **Post date:** [January 21, 2019, 6:58pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/14 "2019-01-21T18:58:18Z")
It might be this one: [https://bugzilla.redhat.com/show\_bug.cgi?id=1168118](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? ---
**Author:** ![refi64](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/refi64/32/1607_2.png) [@refi64](https://discussion.fedoraproject.org/u/refi64)\ **Post date:** [January 22, 2019, 3:44am UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/15 "2019-01-22T03:44:08Z")
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? ---
**Author:** ![yajo](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/yajo/32/1199_2.png) [@yajo](https://discussion.fedoraproject.org/u/yajo)\ **Post date:** [December 20, 2019, 10:32am UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/17 "2019-12-20T10:32:30Z")
¿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 ---
**Author:** ![yajo](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/yajo/32/1199_2.png) [@yajo](https://discussion.fedoraproject.org/u/yajo)\ **Post date:** [December 20, 2019, 11:42am UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/18 "2019-12-20T11:42:47Z")
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: ```auto 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? 😖 ---
**Author:** ![jakfrost](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/jakfrost/32/30655_2.png) [@jakfrost](https://discussion.fedoraproject.org/u/jakfrost)\ **Post date:** [December 27, 2019, 1:51pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/19 "2019-12-27T13:51:50Z")
Hello @yajo, Welcome to the discussion. > [@yajo](#): > > I have no idea on which one is _the good one_ , or what do ostree:1/0 mean 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). > [@yajo](#): > > the grub screen doesn’t use any default value. I always have to select one deployment. Any suggestions to fix that? 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). ---
**Author:** ![yajo](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/yajo/32/1199_2.png) [@yajo](https://discussion.fedoraproject.org/u/yajo)\ **Post date:** [January 7, 2020, 12:57pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/20 "2020-01-07T12:57:16Z")
Thanks for your replies 😄 > [@jakfrost](#): > > 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). Yes, but in my case it will never choose one automatically, no matter what I do. ---
**Author:** ![jakfrost](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/jakfrost/32/30655_2.png) [@jakfrost](https://discussion.fedoraproject.org/u/jakfrost)\ **Post date:** [January 25, 2020, 3:09pm UTC](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486/21 "2020-01-25T15:09:19Z")
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. [Next page](https://discussion.fedoraproject.org/t/cannot-install-boot-loader/486.md?page=2)