Acronis Snap Deploy 4 - User Guide - Manual (Page 124)

124 Copyright © Acronis International GmbH, 2002-2012
Specifically, when you deploy Linux volumes, it is sometimes necessary to apply fixes or make
booting changes so that Linux can boot and load correctly.
Below is a summary of typical situations that require additional user actions.
Why a deployed operating system may be unbootable
 The machine BIOS is configured to boot from another HDD.
Solution: Configure the BIOS to boot from the HDD where the operating system resides.
 The system was deployed to dissimilar hardware and the new hardware is incompatible with
the most critical drivers included in the backup
Solution: Use Acronis Universal Deploy option in deployment template (p. 81) to install the
appropriate drivers and modules.
 The system uses Acronis OS Selector
Because the Master Boot Record (MBR) can be changed during the system deployment, Acronis
OS Selector, which uses the MBR, might become inoperable. If this happens, reactivate Acronis
OS Selector as follows.
Solution: Boot the machine from the Acronis Disk Director's bootable media and select in the
menu Tools -> Activate OS Selector.
 The system uses GRand Unified Bootloader (GRUB) and was recovered from a normal (not
from a raw, that is, sector-by-sector) master image
One part of the GRUB loader resides either in the first several sectors of the disk or in the first
several sectors of the volume. The rest is on the file system of one of the volumes. System
bootability can be recovered automatically only when the GRUB resides in the first several
sectors of the disk and on the file system to which direct access is possible. In other cases, the
user has to manually reactivate the boot loader.
Solution: Reactivate the boot loader. You might also need to fix the configuration file.
 The system uses Linux Loader (LILO) and was recovered from a normal (not from a raw, that is,
sector-by-sector) master image
LILO contains numerous references to absolute sector numbers and so cannot be repaired
automatically except for the case when all data is deployed to the sectors that have the same
absolute numbers as on the source disk.
Solution: Reactivate the boot loader. You might also need to fix the loader configuration file for
the reason described in the previous item.
 The system loader points to the wrong volume
This may happen when system or boot volumes are not recovered to their original location.
Solution: Modification of the boot.ini or the boot\bcd files fixes this for Windows loaders.
Acronis Snap Deploy 4 does this automatically and so you are not likely to experience the
problem. For the GRUB and LILO loaders, you will need to correct the GRUB configuration files. If
the number of the Linux root partition has changed, it is also recommended that you change
/etc/fstab so that the SWAP volume can be accessed correctly.
 Linux was deployed from an LVM volume master image to a basic MBR disk
Such system cannot boot because its kernel tries to mount the root file system at the LVM
volume.
Solution: Change the loader configuration and /etc/fstab so that the LVM is not used and
reactivate the boot loader.