| View previous topic :: View next topic |
| Author |
Message |
Adarion
Tux's lil' helper
Joined: 22 Aug 2005
Posts: 78
|
 Posted: Tue Mar 19, 2024 10:11 am Post subject: Grub2 out of range 452 error =sys-boot/grub-2.12-r2 broken? |
 |
|
Hello Gentoo-forum.
As far as I see Grub 2 =sys-boot/grub-2.12-r2 is somehow broken.
(Before anyone tells me, yes, I know bootloaders can be considered "an obscure part of firmware" and they do not need much changing, but imagine you install Gentoo on a new system and have no access to older versions.)
I updated Grub on a system with the same procedure as always.
| Code: | * compile grub (USE were device-mapper mount, no strange CFLAGS)
# emerge -1 grub
* then install (SSD was mapped as sdb not sda here)
# grub-install /dev/sdb
(/boot mounted at /dev/sdb1)
* yes, new file-dates in /boot/grub
* and, even though that shouldn't be strictly necessary
# grub-mkconfig -o /boot/grub/grub.cfg |
Same procedure as every year, James.
However, for some reason, I ended up with an out of range error 452 on grub all the time.
The only thing that would still allow me to get into the system was using the failsafe sub-option on the two Kernels I currently have at /boot (6.6.13 and 6.6.21).
Downgrading to =sys-boot/grub-2.06-r9 (and grub-install etc.) instantly solved the problem and I can boot regularly.
So I must suspect that something in =sys-boot/grub-2.12-r2 is broken.
Should I file a bug-report?
Anybody with a similar problem?
Did I miss something?
(PS: architecture is amd64, mostly stable stuff with few exceptions taken from ~amd64 where deemed necessary; system is a Kabini CPU, stuff worked here before and just seemed to have broken with the grub update)
_________________
stop tcpa, swpatents, corrupt politicians and other scary stuff |
|
| Back to top |
|
 |
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3830
|
| Posted: Tue Mar 19, 2024 10:21 am Post subject: |
|
|
Although I have no trace to show, sys-boot/grub-2.12-r2 failed to boot on MBR here.
Can't recall if it was at grub or kernel level.
Had to fallback to previous version. 
Another updated UEFI system booted properly.
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
| Back to top |
|
|
freke
Veteran
Joined: 23 Jan 2003
Posts: 1026
Location: Somewhere in Denmark
|
| Posted: Tue Mar 19, 2024 6:29 pm Post subject: |
|
|
Only BIOS/MBR systems here but haven't experienced any issues | Code: | ns ~ # emerge -pv sys-boot/grub
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 0.55 s (backtrack: 0/20).
[ebuild R ] sys-boot/grub-2.12-r2:2/2.12-r2::gentoo USE="fonts nls themes verify-sig -device-mapper -doc -efiemu -libzfs -mount -sdl (-test) -truetype" GRUB_PLATFORMS="pc -coreboot -efi-32 -efi-64 -emu -ieee1275 (-loongson) -multiboot -qemu (-qemu-mips) -uboot -xen -xen-32 -xen-pvh" 0 KiB |
|
|
| Back to top |
|
|
Adarion
Tux's lil' helper
Joined: 22 Aug 2005
Posts: 78
|
| Posted: Fri Apr 05, 2024 3:03 pm Post subject: |
|
|
Yes, mostly MBR classic booting here, too.
It seems =sys-boot/grub-2.12-r3 was released very recently; does anyone have good experiences with that? I won't dare to touch anything until I'm safe, esp. since the old version were removed from the tree.
_________________
stop tcpa, swpatents, corrupt politicians and other scary stuff |
|
| Back to top |
|
|
freke
Veteran
Joined: 23 Jan 2003
Posts: 1026
Location: Somewhere in Denmark
|
| Posted: Fri Apr 05, 2024 4:42 pm Post subject: |
|
|
| Adarion wrote: | Yes, mostly MBR classic booting here, too.
It seems =sys-boot/grub-2.12-r3 was released very recently; does anyone have good experiences with that? I won't dare to touch anything until I'm safe, esp. since the old version were removed from the tree. |
| Code: | ns ~ # emerge -pv sys-boot/grub
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 0.54 s (backtrack: 0/20).
[ebuild R ] sys-boot/grub-2.12-r3:2/2.12-r3::gentoo USE="fonts nls themes verify-sig -device-mapper -doc -efiemu -libzfs -mount -sdl (-test) -truetype" GRUB_PLATFORMS="pc -coreboot -efi-32 -efi-64 -emu -ieee1275 (-loongson) -multiboot -qemu (-qemu-mips) -uboot -xen -xen-32 -xen-pvh" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
ns ~ # grub-install /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.
ns ~ # grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.6.21-gentoo-x86_64
Found linux image: /boot/vmlinuz-6.6.18-gentoo-x86_64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
ns ~ # |
Again - simple BIOS/MBR boot, boots (for me) as expected |
|
| Back to top |
|
|
svoop
n00b
Joined: 11 Jan 2009
Posts: 64
|
| Posted: Sat May 11, 2024 3:51 pm Post subject: |
|
|
| Adarion wrote: | Yes, mostly MBR classic booting here, too.
It seems =sys-boot/grub-2.12-r3 was released very recently; does anyone have good experiences with that? I won't dare to touch anything until I'm safe, esp. since the old version were removed from the tree. |
This happened to me once after an update because I failed to grub-install to all drives in the box. The fix was pretty easy since the box is located in a server farm which features a rescue system into which I could boot, repeat the grub-installing and then reboot normally again. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Installing Gentoo
