Description of problem: I was having trouble setting the default GRUB boot menu entry using grub2-set-default, so I read https://fedoraproject.org/wiki/GRUB_2. This document states: "The above method fails to work on some F20 (and newer) systems due to a missing or improperly linked /boot/grub2/grubenv file. The /boot/grub2/grubenv is symbolic linked to /boot/efi/EFI/fedora/grubenv but /boot is not mounted at the time of booting. So grub2 does not have access to the environment variables. To fix this, change /boot/grub2/grubenv to point to ../efi/EFI/fedora/grubenv instead and your chosen default OS will boot without any problems." I tried recreating the symbolic link as described, but GRUB still failed to boot the menu entry I wanted. I *copied* grubenv from boot/efi/EFI/fedora/grubenv to /boot/grub2/grubenv instead, and that finally worked. However, I now have two copies of grubenv, and I am concerned some utility might cause them to become out of sync. (You cannot place the file at /boot/grub2/grubenv and the symbolic link at /boot/efi/EFI/fedora/grubenv because the efi filesystem is vfat.) Is the documentation wrong? Would it be possible to get rid of one of the copies of grubenv? Version-Release number of selected component (if applicable): grub2-efi-2.02-0.34.fc24.x86_64 grub2-efi-modules-2.02-0.34.fc24.x86_64 grub2-tools-2.02-0.34.fc24.x86_64
This issue persists in Fedora 26 Alpha.
*** This bug has been marked as a duplicate of bug 1335533 ***