On Fri, Mar 25, 2016 at 04:31:11PM +0000, Dan Douglas wrote:
>
> grub2-mkconfig generates no menu entries. Do I need anything generated
> by /etc/grub.d/00_header? That output looks like garbage.
>
You are better off not removing the header.
Are you running grub2-mkconfig from the chroot? The kernel+initramfs
should be located at /boot. In the case of btrfs you can make it a
subvolume but at the time of running grub2-mkconfig you should be chrooted
into your root subvolume and your kernel has to be at /boot.
> The only real relevant configuration in /etc/default/grub should be correct.
>
> GRUB_CMDLINE_LINUX="root=UUID=f0373f0c-3798-4965-a845-b1b94cc14731
> rootfstype=btrfs
> rootflags=rw,noatime,compress=zlib,space_cache,subvol=rootfs"
>From what I can remember you don't need any of that - if anything would be
relevant it's subvol=rootfs but grub should be able to figure that out.
> grub2-install also fails:
>
> # grub2-install --target=x86_64-efi /dev/sda
> Installing for x86_64-efi platform.
> grub2-install: error: cannot find EFI directory.
>
> What EFI directory? The one I created under /boot?
>
/dev/sda1 is your EFI partition, formatted as vfat. You can have it
mounted under /boot or under /boot/efi (I recommend the latter). Install
like this
# grub2-install --target=x86_64-efi --efi-directory=/boot/efi
You can also use dracut to build an uefi executable that includes your
kernel, the kernel commandline and the initramfs.
# dracut --uefi
