[Bug 935579] New: GRUB fails to find its own files
http://bugzilla.opensuse.org/show_bug.cgi?id=935579 Bug ID: 935579 Summary: GRUB fails to find its own files Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: pastas4@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- I ran the YaST bootloader configuration in order to refresh the GRUB config file (didn't make any changes), and it resulted in GRUB not finding any of its own modules on next boot, hence failing to boot anything. I'm using UEFI, so the GRUB EFI file is on an EFI SYSTEM partition, whereas the modules are located on the BTRFS / partition. What might have confused it further is that I followed the suggestion on the Btrfs wiki to have / a default subvolume as opposed to the root of the drive. A workaround for that is to install GRUB into the EFI SYSTEM partition itself by using `grub2-install --efi-directory=/boot/efi --boot-directory=/boot/efi --bootloader-id=opensuse`. It would be nice if that was an option in YaST bootloader settings, ideally on by default for UEFI GRUB. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=935579
http://bugzilla.opensuse.org/show_bug.cgi?id=935579#c1
Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=935579
http://bugzilla.opensuse.org/show_bug.cgi?id=935579#c2
Dainius Masiliunas
http://bugzilla.opensuse.org/show_bug.cgi?id=935579
http://bugzilla.opensuse.org/show_bug.cgi?id=935579#c3
Josef Reidinger
http://bugzilla.opensuse.org/show_bug.cgi?id=935579
http://bugzilla.opensuse.org/show_bug.cgi?id=935579#c4
Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=935579
http://bugzilla.opensuse.org/show_bug.cgi?id=935579#c5
--- Comment #5 from Dainius Masiliunas
http://bugzilla.opensuse.org/show_bug.cgi?id=935579
http://bugzilla.opensuse.org/show_bug.cgi?id=935579#c6
Dainius Masiliunas
http://bugzilla.opensuse.org/show_bug.cgi?id=935579
http://bugzilla.opensuse.org/show_bug.cgi?id=935579#c7
Michael Chang
As for the /boot/efi/EFI directory, it just has /boot/efi/EFI/opensuse/grubx64.efi, I don't think it's worth attaching that...
I think there are two possible ways you can try to recover the failure boot. 1. edit /etc/default/grub and change SUSE_BTRFS_SNAPSHOT_BOOTING="false", run update-bootloader --reint 2. Enable Secure Boot in YaST bootloader. For #1. it changes to settings to your previous use case, that is path is interpreted from toplevel subvol (/slash/boot/...) so that grub modules in a separate subvol can always be accessed ... For #2. as long as all required modules are built in signed /boot/efi/EFI/opensuse/grub.efi. it should also work. A solution is needed for SUSE_BTRFS_SNAPSHOT_BOOTING="true" with Secure Boot "off" which is your case currently. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=935579
http://bugzilla.opensuse.org/show_bug.cgi?id=935579#c8
--- Comment #8 from Michael Chang
(In reply to Dainius Masiliunas from comment #6)
As for the /boot/efi/EFI directory, it just has /boot/efi/EFI/opensuse/grubx64.efi, I don't think it's worth attaching that...
I think there are two possible ways you can try to recover the failure boot.
1. edit /etc/default/grub and change SUSE_BTRFS_SNAPSHOT_BOOTING="false", run update-bootloader --reint
update-bootloader --reinit -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=935579
http://bugzilla.opensuse.org/show_bug.cgi?id=935579#c9
Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=935579
http://bugzilla.opensuse.org/show_bug.cgi?id=935579#c10
Dainius Masiliunas
participants (1)
-
bugzilla_noreply@novell.com