Restoring Manjaro Grub after Ubuntu upgrade

On a multi-boot Linux computer where Ubuntu has already been installed, adding on Manjaro Linux installs its own version of Grub (that I’ll call Arch-Grub) that is different but compatible with that previously installed (that I’ll call Debian-Grub).

Addendum: The below instructions worked for Manjaro releases before March 2018. For some instructions dated May 2021 (that worked in February 2022), see “Restore Manjaro boot after dualbooted Ubuntu-Mate replaced grub” at https://forum.manjaro.org/t/restore-manjaro-boot-after-dualbooted-ubuntu-mate-replaced-grub/67583/2

On some of my laptops, the “grub-install — rechedk — no-rs-codes” would give a response “grub-install: error: install device isn’t specified”.
The manual command was then “grub-install /dev/sda” for the laptop with a single drive, and “grub-install /dev/sdb” for the laptop with two drives where I wanted to not boot off the first drive with Windows installed.

Updating Ubuntu to a newer version (or installing an older version) restores Debian-Grub, replacing the working Arch-Grub. This will result in Debian-Grub showing both Ubuntu and Manjaro as options on booting. Choosing Ubuntu from Arch-Grub works just fine. However, choosing Manjaro from Debian-Grub will lead to a black screen with messages, e.g.:

… Failed to execute /init (error -13)
… Starting init: /sbin/init exists but couldn’t execute it (error -13)
… Starting init: /bin/init exists but couldn’t execute it (error -13)
… Starting init: /bin/sh exists but couldn’t execute it (error -13)
… Kernel panic – not syncing: No working init found. Try passing init option to kernel …
…
… —[ end Kernel panic – not syncing: No working init found …

“Kernal Panic after upgrade” as reported by ben1 in December 2017

On my Thinkpad X200, the only way to exit this screen was to pull the battery for a cold reboot.

The reason that Arch-Grub is different from Debian-Grub is that it loads Intel microcode before the OS, rather than inside the OS.

Manjaro will load intel-ucode using grub.
Unlike other OS’s, it is not built into initd (initramfs) nor into kernel.
But it will load this separately (first) from /boot/intel-ucode.img

But don’t worry about this. It will be done automatically for you when you install or boot Manjaro (provided you use Manjaro’s bootloader (grub) as default bootloader).

… says gohlip | “Does manjaro supply intel microcode automatically?” | May 2016 at https://forum.manjaro.org/t/does-manjaro-supply-intel-microcode-automatically/646/2

Thus, Arch-Grub does more work than Debian-Grub. Arch-Grub will successfully start Ubuntu (based on Debian), but Debian-Grub will not successfully start Manjaro (based on Arch). The resolution is to replace Debian-Grub with Arch-Grub to the multiboot system.

gohlip suggests seven ways to fix this …

1. chroot from livecd (which you’re aware of, I think)
2. use this method which does not need chroot or boot livecd but still make manjaro default boot
3. remove intel-code from manjaro OS but you’ll boot Manjaro without intel microcode enabled
4. …

The Intel microcode updates are theoretically desirable for patches, e.g. Spectre, but unfortunately the Core 2 Duo Penryn CPU I have isn’t one of the them, says “Intel finishes Spectre patching, some older CPUs won’t receive planned updates” | Brad Chacos | April 4, 2018 at https://www.pcworld.com/article/3268007/components-processors/intel-finishes-spectre-cpu-patches-cancels-update-plans.html

After digging into trying to remove the intel-ucode, I figured out it was simpler to just use a Manjaro install DVD (or USB) to restore the Arch-Grub. This then has to be done after every Ubuntu upgrade … but is relatively straightforward (and having a Manjaro install ISO burned onto a DVD means that it’s readily at hand).

Here’s a summary of the steps I’ve used:

With Ubuntu running, use GPartEd to confirm which partition has Manjaro installed. (In my case, it was sda11).
Boot from the Manjaro install DVD or USB.
When the menu appears, choose the LiveDVD option (rather than immediately (re-)installing Manjaro, which isn’t necessary).
Open a terminal.
Confirm the partition with Manjaro installed:
$ sudo fdisk -l
$ lsblk -f
Mount the Manjaro system partition (mine was sda11):
$ sudo mount /dev/sda11 /mnt
Reinstall Arch-Grub:
$ sudo grub-install –boot-directory=/mnt/boot /dev/sda

(That’s two hyphens preceding “boot-directory”)!

This method is consistent with the description of “Restore the GRUB Bootloader” at https://wiki.manjaro.org/index.php?title=Restore_the_GRUB_Bootloader for a BIOS (not UEFI) system.

While this procedure will have to be repeated after every Ubuntu upgrade, it’s understandable and replicable.

#arch, #boot, #debian, #dual-boot, #kernel-panic, #manjaro, #multiboot, #ubuntu

daslu 11:24 am on May 19, 2018

Thank you so much for this! It just saved me so much trouble.
ThedoorIsAjarMan 11:34 pm on July 26, 2018

Appears to only work with bios-legacy and Windows installation, not GPT ESP, or dual linux ubuntu-manjaro boot.
From your link: “And all the following applies only to bios-legacy/msdos.”
From your link: “((Case 2) Windows installation.
Boot up a livecd, at livecd terminal,
sudo mount /dev/sdxy /mnt
sudo grub-install –boot-directory=/mnt/boot /dev/sda”
TheDoorIsAjarMan 12:07 am on July 27, 2018

My apologies,
I tried it in GPT ESP, and it worked; what an unreliable forum.
i.e.
This is a known issue. The Grub bootloader settings of most distros cannot boot Manjaro and Arch. You need to make Manjaro take control of Grub again. Here is a guide:
https://wiki.manjaro.org/index.php?title=Restore_the_GRUB_Bootloader
It is not very easy to understand, but if you basically run
either
mhwd-chroot
or
manjaro-chroot -a
on a Manjaro live USB you will get the system chrooted automatically and then can run
sudo grub-install –recheck /dev/sda
sudo update-grub

but it still does not work.
- TheDoorIsaJarMan 12:46 am on August 2, 2018
  
  Doesn’t Work.
daviding 2:32 pm on August 2, 2018

At the end of July, I successfully used this procedure on a Thinkpad X200 (single physical drive), and X230T (mSATA physical drive, alongside the SATA drive).

I upgraded Kubuntu 18.04 to 18.04.1 LTS, and then Ubuntu 18.04 to 18.04.1 LTS on each laptop. This resulted in the Manjaro-Grub getting overwritten with Debian-Grub. I repeated the procedure to restore Manjaro-Grub, and can now again boot each of the four distros.

If the above instructions are not working for you, try posting to one of the cited threads, i.e.

“Quadruple boot Grub worked with Manjaro 17.1.9, missing a distro on Manjaro 17.1.10 install” at https://forum.manjaro.org/t/quadruple-boot-grub-worked-with-manjaro-17-1-9-missing-a-distro-on-manjaro-17-1-10-install/49784 …

.. and/or ..

“Kernel panic – not syncing: VFS: Unable to mount root fs on” at https://forum.manjaro.org/t/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on/21226
coldpizza 8:56 am on August 15, 2018
A relatively ugly workaround which allows booting arch from the ubuntu’s grub is to install arch’s grub to the arch’s own partition (or disk if you are using a separate disk which is not set as the boot disk), and then chainload it from ubuntu’s grub.

sample entry in /etc/grub.d/40_custom:
```
	menuentry "chainload hd1 MBR" {
		set root="(hd1)"
		chainloader +1
	}
```
This assumes your arch is residing on hd1 and that you installed arche’s grub to that device.
TheDoorIsAjarMan 10:39 pm on August 17, 2018
Thanks coldpizza – I assume “MBR” is for MBR and would need to be slightly modified to work with UEFI.
I simply installed a Ubuntu-based distro without a bootloader, and then added os-prober to the Arch-based distro.

1. Install an Arch based Distro (first), e.g. Manjaro
2. Then (second) install another Ubuntu based distro (e.g. Mint) without a bootloader with the Ubiquity installer.
[Optional – ubiquity –help ,first]
You simply need to start the installer from a terminal: ubiquity -b before installing the Ubuntu distro with the graphical installer.

1. In Arch based terminal, Mount the partition with the new system (non-Arch based distro,).
– List the partitions of your system: lsblk
- Mount it: (non-Arch based) sudo mount /dev/sd#x /mnt
- e.g. sudo mount /dev/sda3 /mnt
- note: mount device (hardware) to linux tree directory (software)
- [optional, to view cd /mnt/ ,ls (should see OS files) ,cd ]
2. Install OS prober: sudo pacman -S os-prober
3. Update GRUB: sudo grub-mkconfig -o /boot/grub/grub.cfg
(should have found mint) (actually reconfigure grub)

There is one drawback of this setup. You need to repeat the procedure of mounting and updating GRUB manually every time you update (ANY KERNEL IN ANY DISTRO) kernel in your main or your second system. If you have several additional systems, you need to mount them all and run GRUB update.

Thanks daviding, but the manjaro forum communication leaves a lot to be desired.