No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

The SUSE Client Cannot Be Restarted During the BMR and Error Message "Boot loader installation failed" Is Displayed

Publication Date:  2015-07-29 Views:  32 Downloads:  0
Issue Description
An ATAE board runs the SUSE 11 system. An HDP3500E is used to perform the BMR on the ATAE. After the file system of the ATAE board is restored, error message Boot loader installation failed is displayed during the installation of the GRUB boot program. As a result, the BMR for the ATAE board fails.



Handling Process
1.  Run the grub command to enter the GRUB configuration page.

dl380-backup:~ # grub
    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]
grub>


2.  Run the find /boot/grub/stage1 command to query the boot partition information.

grub> find /boot/grub/stage1
(hd0,1)


3.  Run the root command to configure the GRUB boot partition.

grub> root (hd0,1)
Filesystem type is ext2fs, partition type 0x83


4.  Run the setup command to write the GRUB configuration in the master boot record (MBR).

grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"...  17 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,1)/boot/grub/stage2
/boot/grub/menu.lst"... succeeded
Done.


5.  Run the quit command to exit.

grub> quit

6.  Restart the client to complete the BMR.
Root Cause
The GRUB boot program fails to be installed and the operating system fails to be restarted.

In the SUSE 11 system, the GRUB configuration device.map uses the disk IDs to differentiate root partition information of the boot partition. However, the NetBackup requires that the boot partition information be identified by partition types when the system searches for the boot partition information in the device.map file. The NetBackup fails to locate an entry in the partition form in the GRUB configuration device.map file. The device.map file contains the information about the boot partition location identified as hd0 disk. The NetBackup automatically identifies another disk, that is, hd1, as the disk where the boot partition locates and writes the information about disk hd1 in the device.map file. However, the actual partition is disk hd0 rather than disk hd1. During the installation of GRUB boot program, the NetBackup cannot identify the boot partition in the GRUB configuration file and therefore the GRUB boot program fails to be installed.


END