| Summary: | Grub Boot failure after update 182 | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | dnl <ipfire> |
| Component: | --- | Assignee: | Arne.F <arne.fitzenreiter> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | Crash | ||
| Priority: | - Unknown - | CC: | adolf.belka, ipfire.org, michael.tremer |
| Version: | 2 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
|
Description
dnl
2024-01-07 23:59:06 UTC
PS: The boot.mod file itself does not appear to be the problem. It has the same checksum as one I have on an IPFire VM. The system seems unable to boot EFI yet since performing the update & reboot Grub doesn't attempt to boot using legacy BIOS any longer. There is no evidence of disk or filesystem corruption. /boot is fine and all the /boot/grub/i386-pc/ file checksums match a test IPFire VM. If I boot using a recovery image, such as SuperGrub, it detects only EFI boot options also, however it allows me the option to extract entries from grub.cfg. When I choose to boot one of the entries from grub.cfg it boots without problem. I have tried to run the following: ``` grub-install --no-floppy --recheck --force --target=i386-pc /dev/sda ``` I still end up at `grub rescue >` though. Arne.F has stated in the forum: "on systems with xfs filesystem on the boot partition grub seems not correct installed (always?)." My system uses XFS for /boot (and root). > https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=7b40a1c6e275d097c89a8411db1d1e37b75c8e6d
> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=c903d67c7e602a0bbc7c3ea4afefe66cccd6a344
The GRUB update has been reverted from the updater so that we won't break any systems. The following update will ship the final version which seems to fix most of the known problems.
Thank you very much! I'll test this as soon as the update to core update 182 is available on my system. I also had the bootloader issue and after booting manually re-applied the core 182 update (set manually the version to 181 and used pakfire upgrade) and then reinstalled the bootloader to fix it. The last step might not have been necessary but felt safer and I didn't have the time to experiment. Thank you for providing an updated 182 package! Thanks to Deyan in the forum I've been able to re-apply 182 on my system, but unfortunately it has not resolved the problem. The symptoms appear identical. I've put two screenshots in the forum post: https://community.ipfire.org/t/core-update-182-caused-grub-boot-failure/10826/40?u=dnl The latter shows that a problem I saw once before after manually running a grub install or using the /usr/bin/install-bootloader script where the console font becomes corrupt. Updating it a second time appeared to resolve this. So I'll try to re-apply 182 a second time late today to see if it changes. I re-applied 182 a second time and rebooted. Unfortunately my system still won't boot (same problem) and the graphical corruption in the console is still present. (In reply to dnl from comment #8) > I re-applied 182 a second time and rebooted. Unfortunately my system still > won't boot (same problem) and the graphical corruption in the console is > still present. Is there any chance that you can give Core Update 183 a go? That should hopefully contain a proper fix for the XFS boot issue. I am not sure where are standing with this one regarding BIOS bugs. Thanks Michael It's now working!! This morning I forced the system to re-update to 182 and ran install-bootloader and it is working. The graphical corruption on the console is also gone. I had not realised that I needed to rebuild grub (with the install-bootloader) script after updating to 182 again. I had assumed it would automatically run when grub was upgraded. Do I need to prepare for when you update grub again please? (In reply to dnl from comment #10) > I had not realised that I needed to rebuild grub (with the > install-bootloader) script after updating to 182 again. I had assumed it > would automatically run when grub was upgraded. We did not run that script, because people usually upgrade rather than downgrade and on upgraded systems we would not touch the boot loader at all. > Do I need to prepare for when you update grub again please? The update to GRUB 2.12 is now in Core Update 183. It would be great to know whether that works for you, or if we are being put into the same position again... Can you maybe just clone your machine so that you don't break production? (In reply to Michael Tremer from comment #11) > The update to GRUB 2.12 is now in Core Update 183. It would be great to know > whether that works for you, or if we are being put into the same position > again... > > Can you maybe just clone your machine so that you don't break production? Unfortunately this is my home IPFire system and I don't have a spare SSD/disk to put in it. My family tolerates outages worse than my clients at work! Still, I'll try to arrange a few hours sometime. Hopefully I can always just boot it with a USB stick again if it fails. Am I correct in saying that you believe the problem is related to: * Legacy BIOS boot * with XFS filesystems * on Intel baytrail hardware? Note that when the problem happened Grub was always trying to boot EFI, not BIOS. Thanks again! PS: If I test update 183 now, is it possible to later change back to the 'stable' release when that release version becomes the stable version? (In reply to dnl from comment #13) > PS: If I test update 183 now, is it possible to later change back to the > 'stable' release when that release version becomes the stable version? Sorry for the late reply. Yes, it is the dropdown at the bottom of the Pakfire page where you can just go back to stable. Thank you Michael I recognise that if there's a problem I'll be affected anyway, but I am nervous about testing this. Last time it took me a number of hours to stumble upon a workaround. I appreciate that you said in the test release announcement that you're confident the problem is fixed. I'll aim to try this early one weekend day, probably this weekend. Hopefully if there is a problem I can work around it the same way again. I'm very happy to report that after I: * Changed the Pakfire repository to "Testing" * Installed all updates (strangely it installed testing 182 and then testing 183 even though the system was already on production 182) * Ran install-bootloader * Rebooted It all rebooted without problem! During boot, after the IPFire full screen logo was displayed, some text was overlaid which had me worried: ``` EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data in to PCR 9. ``` but it booted fine after that. Is my system now using EFI boot? I have found it difficult to tell conclusively. Thanks again! Thanks for the confirmation. And to me this looks like you have an EFI system there, yes. Thank you. This has been confusing, as I'm fairly sure my system was built with legacy BIOS boot. Anyway it's working now, so I can't complain! If it helps, the new grub.cfg has set root='hd0,msdos5' while a backup copy from before had that using 'msdos4'. My system has 6 partitions: Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 264191 262144 128M 83 Linux /dev/sda2 264192 329727 65536 32M ef EFI (FAT-12/16/32) /dev/sda3 329728 2292233 1962506 958.3M 82 Linux swap / Solaris /dev/sda4 2293760 125045423 122751664 58.5G 5 Extended /dev/sda5 2295808 96667647 94371840 45G 83 Linux /dev/sda6 96669696 125045423 28375728 13.5G 83 Linux So msdos4 is an empty extended partition (header?) while 5 is actually the root filesystem (sda6 is a Linux VM in its own partition). (In reply to dnl from comment #18) > This has been confusing, as I'm fairly sure my system was built with legacy > BIOS boot. Anyway it's working now, so I can't complain! Our installer will install everything so that the device can boot in EFI mode and legacy mode. > If it helps, the new grub.cfg has set root='hd0,msdos5' while a backup copy > from before had that using 'msdos4'. We default to the classic MS-DOS partition table unless the disk is larger than 2TB where we need to use GPT. Thank you again Michael. Should I close this ticket now that it is resolved? I'm not sure of the etiquette here. |