MX-19: FEEDBACK of latest GRUB 2.04-9~mx19+5 update

[Hessed_Elohim]

Yes, sorry about that.. I was referring precisely to that error.

I attach an image of i get:

https://i.imgur.com/TrmZl17.jpg

And not, unfortunately I cant make a bootable cd either.



Mod note: image changed to link, please read the forum rules.

[tony37]

Or a bootable SD card?
Apparently the normal method to get out of grub rescue doesn't work with a grub_calloc error: https://www.reddit.com/r/mynodebtc/comm ... rub_error/

[fehlix]

Or a bootable SD card?
Apparently the normal method to get out of grub rescue doesn't work with a grub_calloc error: https://www.reddit.com/r/mynodebtc/comm ... rub_error/

The "grub_calloc error" indicates a mismatch of the installed grub modules and the used grub-bootloader from the MBR. This can happen during grub-package upgrade where the grub-loader was not properly installed, perhaps by not selecting the MBR of the boot drive. The way to fix is with booting into a LiveMedia e.g. with MX Linux, and run MX Boot Repair. Another method: In case another OS is installed: If e.g. WinOS is installed, one could install Grub2Win within WinOS and let Grub2win generate a boot-menu entry for the install MX Linux system.
If another Linux is installed one could "chroot" into MX Linux and repair grub from within the chrooted system.

[tony37]

If another Linux is installed one could "chroot" into MX Linux and repair grub from within the chrooted system.

How could you get there if your Grub is busted? Bios menu?
Ideal would be if Hessed could get into his system using some arcane commands in the grub rescue prompt but the normal procedure using 'set root', 'set prefix', 'insmod normal' doesn't seem to work with grub_calloc errors

[fehlix]

If another Linux is installed one could "chroot" into MX Linux and repair grub from within the chrooted system.

How could you get there if your Grub is busted? Bios menu?
Ideal would be if Hessed could get into his system using some arcane commands in the grub rescue prompt but the normal procedure using 'set root', 'set prefix', 'insmod normal' doesn't seem to work with grub_calloc errors

Indeed if that's a BIOS/MBR booting system with only one MBR/Drive, it might not straight forward to repair without a liveMedia or another PC.

[tony37]

@ Hessed: A final option may be to try to boot your pc from your smartphone (I suppose you're using that now to have internet). There is an app for this called DriveDroid: https://beebom.com/how-to-boot-linux-on ... oid-phone/
I never used it but I'll test it and see how it works. But I already see you need root access to your Android, which doesn't seem to be so easy and you can also lose your smartphone warranty, so I'm not sure I can recommend this to you.

[Hessed_Elohim]

Hi again.. I managed to get a pendrive, and burn an iso of MX .. how should I proceed now?

[fehlix]

Hi again.. I managed to get a pendrive, and burn an iso of MX .. how should I proceed now?

First try to boot from the USBstick.
Next, try MX Boot Repair.
If that does not help, reboot again an on the LiveUSB Boot menu, navigate to Boot Rescue menu, and try to found Grub.cfg menus. To boot into the system.
And re-run MX Boot Repair from the booted system.
If that still does no help, post "MX Quick System Info" and someone will find a clue to get it sorted.

[Hessed_Elohim]

news.. I did not get the grub to detect the OS
but as I already had the LiveUSB of the MX19.2 (18 was installed) I decided to do a bckup and start from scratch.
thank you all very much for your contributions and comments.
Regards