Browse Prior Art Database

A Flexible UEFI Recovery Mechanism.

IP.com Disclosure Number: IPCOM000224482D
Publication Date: 2012-Dec-25
Document File: 1 page(s) / 20K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a Flexible UEFI Recovery Mechanism. The Flexible UEFI Recovery mechanism uses a system management controller to help discover, update and fix an unbootable image.

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

Page 01 of 1

A Flexible UEFI Recovery Mechanism.

In current system design, UEFI is stored in flash memory on planar.For reliability reason, either fixed Boot Block or backup image is required in order to recover the system from a bad primary UEFI. Both conventional recovery mechanisms have their shortage as Boot Block can't recover by its own if the entire flash part is corrupted and backup image requires a doubled size of storage. The disclosure can overcome the scenario of fully corrupted boot image without increasing flash memory size by leveraging a service processor (i.e. BMC) that already exists in most of our server designs.

The firmware recovery mechanism introduced here uses system management controller to help discover, update and fix an unbootable image. During system boot process, BMC monitors POST progress by communications between the two entities. When BMC finds UEFI is not able to successfully boot, it will start the recovery mechanism. A bootable image can be either preserved in BMC embed data store or dynamically retrieved from peripheral devices. Comparing to Boot Block design, the mechanism can self recover from fully damaged firmware image. On the other hand, no additional flash part space for storing backup uEFI image is required. Therefore, the mechanism it more reliable than Boot Block design while keeping the cost lower than dual UEFI image system.

On a system that has firmware recoverability, UEFI notify service processor its own boot progress. If...