Linux REAR BMR - kernel panic - not syncing - attempting to kill init - FATAL dont know how to handle

Linux REAR BMR - kernel panic - not syncing - attempting to kill init - FATAL dont know how to handle

During a linux, ReaR based BMR, specifically in virtual platforms and environments (ie ONAPP), they may change name/paths of driver paths when booting in various different manners (ie booting from ISO vs booting from prebuilt templates for example). 

This can be addressed as per below (we will use OnAPP as a use case scenario here)

Follow the Clusterlogics (ReaR) BMR instructions to create the bootable ISO image required for BMR

1) upload the recovery ISO to OnAPP




2) Boot the VM from the ISO




3) Select Recovery (rescue) mode when presented.  please note, often times there is a 30-60 second timeout here, so, you may need to watch and act quickly once presented




4) this scenario is no different then any other BMR up to this point.  the purpose of this KB is related to this scenario right here. OnAPP or other scenarios may change name/path of driver folders, and you will see an output and options as per below. Select #5 below and proceed, but, you can expect issues when booting the VM (as per #6 below)




6) when you see a fatal screen such as the below on booting after BMR process continues, you know you have this scenario as described in this KB




7) By fixing boot/grub - you can resolve the issue and reboot the VM or server.  This step is often required when migrating or restoring to dissimilar hardware, or from different Hypervisor platforms for example.  Advanced users need to enter single user mode, mount and fix grub and reboot.  You are all done

8) various platforms if you are working with VMs can assist you here as well.  for example, with OnAPP, select the option to "Reboot in Recovery Mode"




9) log into recovery mode and mount your disk




10) fix /mnt/etc/grub and /mnt/etc/fstab
Examples

FROM


to



FROM


TO


11) Power off in console, restart VM from within OnAPP and it will boot without errors and the BMR is complete of your OnAPP VM

    • Related Articles

    • Linux REAR BMR - kernel panic - not syncing - attempting to kill init - FATAL dont know how to handle

      During a linux, ReaR based BMR, specifically in virtual platforms and environments (ie ONAPP), they may change name/paths of driver paths when booting in various different manners (ie booting from ISO vs booting from prebuilt templates for example).  ...

    • Linux BMR (ReaR)

      Bacula4 has developed a new Linux BMR tool.  This is more tightly integrated with our GUI and is based on the ReaR *nix server imaging technology. This new Linux BMR replaces the legacy/original Linux BMR found HERE For existing customers, using the ...

    • New Linux (ReaR) BMR announced

      Hello today we are pleased to announce the launch of our new Linux (ReaR) BMR solution. With this new Linux BMR utility, we are able to support practically every flavour of *.nix systems, and have brought the BMR process into our GUI.  A much more ...

    • Linux BMR (ReaR)

      Bare Metal Restore (ReaR) Bacula4 has developed a new Linux BMR tool.  This is more tightly integrated with our GUI and is based on the ReaR *nix server imaging technology. To activate Bare Metal Restore (ReaR) simply enable it on the backup wizard: ...

    • Linux Server Migration using ReaR BMR

      You can use Bacula ReaR BMR to quickly, easily and safely perform server migrations. Step one: prepare server Prepare source server: Define new IP address: echo eth0 192.268.1.100/24 >/etc/rear/mappings/ip_addresses Define new route (optional - if ...