Справочник Пользователя для Acronis backup recovery 10 workstation
Copyright © Acronis, Inc., 2000-2009
153
6.3.11. Bootability troubleshooting
If a system was bootable at the time of backup, you expect that it will boot after recovery. However,
the information the operating system stores and uses for booting up may become outdated during
recovery, especially if you change volume sizes, locations or destination drives. Acronis Backup &
Recovery 10 automatically updates Windows loaders after recovery. Other loaders might also be
fixed, but there are cases when you have to re-activate the loaders. Specifically when you recover
Linux volumes, it is sometimes necessary to apply fixes or make booting changes so that Linux can
boot and load correctly.
the information the operating system stores and uses for booting up may become outdated during
recovery, especially if you change volume sizes, locations or destination drives. Acronis Backup &
Recovery 10 automatically updates Windows loaders after recovery. Other loaders might also be
fixed, but there are cases when you have to re-activate the loaders. Specifically when you recover
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 recovered 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 recovered on dissimilar hardware and the new hardware is incompatible with
the most critical drivers included in the backup
the most critical drivers included in the backup
Solution for Windows: Recover the volume once again. When configuring recovery, opt for
using Acronis Universal Restore and specify the appropriate HAL and mass storage drivers.
using Acronis Universal Restore and specify the appropriate HAL and mass storage drivers.
•
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.
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.
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
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.
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
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.
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.