Browse Prior Art Database

Self Detection and Correction Method for Handling Multiple Boot Images

IP.com Disclosure Number: IPCOM000199557D
Publication Date: 2010-Sep-09
Document File: 4 page(s) / 27K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for system self control/correction during the boot process within a multi-boot image environment. When the system detects an error, it automatically reverts to the correct target image. The method ensures that a system always boots from the correct image, helping to eliminate loss of access to data.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 4

Self Detection and Correction Method for Handling Multiple Boot Images

The advantage of a multi-boot environment is that it allows the system to switch back

and forth between different boot images. With this multi- boot environment, however,

systems encounter the problem of controlling from which boot image (standard or

alternate) to boot the system. If the bootlist is lost or altered, then the system is in

danger of launching from the wrong boot image, causing loss of access to client or

customer data.

Known solutions include switching the boot image manually, one by one, with the hope

that the system will come up correctly without loss of access to the customer data: the

correct boot image is not known at that point. This is not a reliable solution.

The solution to the boot problems disclosed here provides a self control/correction

process, launched during boot, which guides the system to boot from the correct image

regardless of how and from where the system boots. This solution reverts the system to

the correct image; always booting from the correct image helps to eliminate loss of

access.

The invention provides a method of self-detection and self-healing: if the tracking

system identifies that the boot image is altered or the system has switched to an

incorrect boot image, then the invention automatically reverts the system to boot back to

a desired target image. This automated self healing (tracking/reverting) of the boot

image does not exist within other boot process.

For code load:
The boot code is installed on multiple images. Then, an initial boot configuration is

created at a particular location which will be accessible to both system based on the

image from which the system will be booted.
1. Load the Dual Boot Management on the current code image. Add the boot

monitoring event to the system boot process to track which boot image the

system is running during boot. The initial configuration will be used during boot to

keep track what the current boot image is.
2. Duplicate the current code image to create the alternate code image.
• Install new code to create the new alternate code image.
• The new code image and current images coexist on same boot disks.

1

Page 2 of 4

3. Set up temporary boot configuration (initial boot configuration) to point to the new

alternate boot image.
• The initial boot configuration will be created at this point to point to the

new alternate code image.
• Boot the system from the new alternate code image.
• Go to step 4.

For normal boot process:...