121 Copyright © Acronis International GmbH, 2002-2015
Windows was recovered to a dynamic volume that cannot be bootable
Solution: Recover Windows to a basic, simple or mirrored volume.
A system volume was recovered to a disk that does not have an MBR
When you configure recovery of a system volume to a disk that does not have an MBR, the
program prompts whether you want to recover the MBR along with the system volume. Opt
for not recovering, only if you do not want the system to be bootable.
Solution: Recover the volume once again along with the MBR of the corresponding disk.
The system uses Acronis OS Selector
Because the Master Boot Record (MBR) can be changed during the system recovery, 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) backup
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) backup
LILO contains numerous references to absolute sector numbers and so cannot be repaired
automatically except for the case when all data is recovered 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 Backup 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 recovered from an LVM volume backup 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.
5.5.1 How to reactivate GRUB and change its configuration
Generally, you should refer to the boot loader manual pages for the appropriate procedure. There is
also the corresponding Knowledge Base article on the Acronis website.
