How to repair Manjaro/Grub after it has been restored from a Clonezilla backup image

Some of you might have run into it. Your system broke or you messed something up, so you wanted to restore your system from a Clonezilla backup.

The backup of your disk went fine and restoring it also seemed to go well in Clonezilla.

But then you boot your computer.

And you find out that Grub doesn't even load.

So what can you do?

Here's the solution:

To repair a Manjaro installation that was restored using Clonezilla, but doesn't even boot Grub after restoring it - do the following:

Boot into Manjaro's live cd and mount your actual Manjaro installation into /mnt

  • Replace /dev/sdX with your actual harddrive device (ex. sdb)
sudo mount /dev/sdX /mnt

Then chroot into /mnt using mhwd-chroot (you can download mhwd-chroot from the Manjaro repositories)

sudo mhwd-chroot /mnt

Now install grub. This will probably install it on the same partition as the Manjaro installation itself, even if you previously had grub installed on a separate partition.

grub-install /dev/sdX

Recheck to ensure that the installation has completed without any errors:

grub-install --recheck /dev/sdX

Now automatically configure Grub:


Reboot the system. Watch the magic.

Extra note: If prior to the Clonezilla restoration process Grub was installed on a separate partition, then installing Grub can generate the following error: "warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible."

To Solve this error, open gParted. This is fixed by creating a 2MB partition on the hard disk and setting its flag to "bios_grub". However, if after a Clonezilla restore the Grub boot partition already exists, then you only need to set the flag to "bios_grub". :slight_smile:


manjaro-chroot -a is acceptable as well for mounting and chrooting into, or you put your command as a bare minimum requirement?

So, if restoring to a new MBR disk (non-UEFI),

Pre-step: fsck drive

  1. Re-install GRUB
  2. Add previous kernel boot parameters
  3. Change fstab entry to the new UUID(s)

Forum kindly sponsored by