Method for boot recovery

• US 7,480,819 B1
• Filed: 02/21/2007
• Issued: 01/20/2009
• Est. Priority Date: 06/27/2003
• Status: Expired due to Term

• Current Assignee: PMC-Sierra Incorporated (Microchip Technology Incorporated)
• Original Assignee: Adaptec Incorporated (Steel Partners Holdings LP)
• Inventors: Mahmoud, Fadi A., Sridaran, Ganapathy S.
• Primary Examiner(s): Beausoliel; Robert
• Assistant Examiner(s): Riad; Amine
• Application Number:
  US11/677,491
• Time in Patent Office: 699 Days
• Field of Search: 714/6, 714/36, 713/1
• US Class Current: 714/6.12
• CPC Class Codes: G06F 11/1417 Boot up procedures

Abstract

A method for recovering boot-up data in a computer system is provided. The method includes storing boot up data in a first container that is accessible by an operating system and copying the boot up data from the first container to a second container that is inaccessible by the operating system. If boot up using the boot up data from the first container fails, the method further includes copying the boot up data from the second container to the first container and booting up the computer system using the boot up data copied into the first container from the second container.

Claims

1. A method for recovering boot up data in a computer system, comprising:

storing boot up data in a first container that is accessible by an operating system;

copying the boot up data from the first container to a second container that is inaccessible by the operating system;

if boot up using the boot up data from the first container fails, copying the boot up data from the second container to the first container; and

booting up the computer system using the boot up data copied into the first container from the second container.

2. The method as recited in claim 1 wherein copying occurs in response to a specified event selected from a set of events consisting essentially of an elapsed period of time, and recognition of the presence of a virus in the first container.

3. The method as recited in claim 1 wherein copying occurs in response to an occurrence of a predefined calendar date.

4. The method as recited in claim 1 wherein the second container is selected from a set consisting essentially of an operating system secure sector, a portion of at least one disk drive, and a logical storage unit.

5. The method as recited in claim 1 wherein the boot data includes at least a master boot record and system files.

6. The method as recited in claim 1 wherein the first container is accessible through firmware on a host adapter.

7. The method as recited in claim 1 wherein the first container is selected from a set consisting essentially of at least a portion of at least one storage device, and a logical storage unit.

8. The method as recited in claim 1 wherein the copying is done by a firmware on a host adapter.

9. The method as recited in claim 1 further including determining whether the first container is free of a virus, with copying further including copying upon determining whether the first container if free of said virus.

10. A method for recovering boot up data comprising:

generating a first logical storage unit, the first logical storage unit being configured to be accessible by an operating system;

generating a second logical storage unit, the second logical storage unit being configured to be inaccessible by the operating system;

storing boot up data in the first logical storage unit;

determining whether the boot up data in the first logical storage unit contains a virus; and

copying the boot up data from the first logical storage unit to the second logical storage unit upon determining whether said boot up data in the first logical storage unit is free of the virus.

11. The method for recovering boot up data as recited in claim 10 wherein copying further includes setting a recovery bit in a nonvolatile memory of a host adapter to initiate boot recovery upon determining the boot up data in the first logical storage unit is free of the virus and;

copying the boot up data from the second logical storage unit to boot up data locations in the first logical storage in response to the presence of the recovery bit; and

unsetting the recovery bit after the computer system has been booted up.

12. The method as recited in claim 10 wherein copying further includes determining whether occurred is a specified event selected from a set of events consisting essentially of an elapsed period of time, and recognition of the presence of a virus in the first logical storage unit, and copying the boot up data from the first logical storage unit to the second logical storage unit in response to the event and upon determining whether said boot up data in the first logical storage unit is free of the virus.

13. The method as recited in claim 10 wherein copying further includes determining whether occurred is a predefined calendar date, and copying the boot up data from the first logical storage unit to the second logical storage unit in response to the event and upon determining whether said boot up data in the first logical storage unit is free of the virus.

14. The method for recovering boot up data as recited in claim 10 wherein the copying of the boot up data from the first logical storage unit to the second logical storage unit is managed by firmware being run in a host adapter.

15. A method for recovering boot up data comprising:

generating a first container in a storage system, the first container being inaccessible to the operating system;

generating a second container in the storage system, copying boot up data from the second container to the first container; and

when input requesting boot recovery is received;

setting a recovery bit;

copying boot up data from the first container to a master boot record location and a system file location within a second container, the first container being inaccessible to an operating system;

booting up using the copied boot up data in the first container; and

unsetting the recovery bit.

16. The method as recited in claim 15 wherein the first container is selected from a set consisting essentially of an operating system secure sector, at least a portion of at least one disk drive, a portion of at least one disk.

17. The method as recited in claim 15 wherein the second container is at least a portion of at least one disk drive.

18. The as recited in claim 15 wherein the boot data includes at least a master boot record and system files.

19. The method as recited in claim 15 wherein the first container is accessible through firmware on a host adapter.

20. The as recited in claim 15 wherein the storage system includes at least one disk drive.