IP Library › Granted Patent US 9,569,297
Granted Patent B2
US 9,569,297 · App. 14/333,232 · Granted Feb 14, 2017

Seamless method for booting from a degraded software raid volume on a UEFI system

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,569,297
App. No.
14/333,232
Granted
Feb 14, 2017
Kind
B2
Abstract

An information handling system includes a processor and a configuration detection and error handling module operable to read a first tag data file from a first storage volume, read a second tag data file from a second storage volume, and determine that the first storage volume and the second storage volume are configured as mirrored storage volumes based upon the first tag data file and the second tag data file.

Claims (70)

1. An information handling system comprising:

a processor; and

a configuration detection and error handling (configuration/error) module operable to:

read a first tag data file from a first storage volume;

read a second tag data file from a second storage volume;

determine that the first storage volume and the second storage volume are configured as mirrored storage volumes based upon the first tag data file and the second tag data file;

read a third tag data file from the first storage volume; and

read a fourth tag data file from the second storage volume;

wherein the determination that the first storage volume and the second storage volume are configured as mirrored storage volumes is further based upon the third tag data file and the fourth tag data file.

2. The information handling system of claim 1 , wherein the configuration/error module is further operable to:

compare the first tag data file and the second tag data file;

wherein the determination that the first storage volume and the second storage volume are configured as mirrored storage volumes is further based upon the comparison of the first tag data file and the second tag data file.

3. The information handling system of claim 2 , wherein in comparing the first tag data file and the second tag data file, the configuration/error module is further operable to:

compare a first name of the first tag data file to a second name of the second tag data file;

wherein the first storage volume and the second storage volume are determined to be configured as mirrored storage volumes when the first name is the same as the second name.

4. The information handling system of claim 2 , wherein in comparing the first tag data file and the second tag data file, the configuration/error module is further operable to:

compare the contents of a first OS boot loader name field of the first tag data file to the contents of a second OS boot loader name filed of the second tag data file;

wherein the first storage volume and the second storage volume are determined to be configured as mirrored storage volumes when the contents of first OS boot loader name field is the same as the contents of second OS boot loader name field.

5. The information handling system of claim 2 , wherein in comparing the first tag data file and the second tag data file, the configuration/error module is further operable to:

compare the contents of a first OS boot loader authenticator field of the first tag data file to the contents of a second OS boot loader authenticator filed of the second tag data file;

wherein the first storage volume and the second storage volume are determined to be configured as mirrored storage volumes when the contents of first OS boot loader authenticator field is the same as the contents of second OS boot loader authenticator field.

6. The information handling system of claim 5 , wherein:

the contents of the first OS boot loader authenticator field includes a first checksum for a first OS boot loader stored on the first storage volume; and

the contents of the second OS boot loader authenticator field includes a second checksum for a second OS boot loader stored on the second storage volume.

7. The information handling system of claim 5 , wherein:

the contents of the first OS boot loader authenticator field includes a first date stamp for a first OS boot loader stored on the first storage volume; and

the contents of the second OS boot loader authenticator field includes a second date stamp for a second OS boot loader stored on the second storage volume.

8. The information handling system of claim 1 , wherein: the first tag data file includes a reference to the third tag data file; the second tag data file includes a reference to the fourth tag data file; the third tag data file includes a reference to the first tag data file; and the fourth tag data file includes a reference to the second tag data file.

9. The information handling system of claim 1 , wherein, after determining that the first storage volume and the second storage volume are configured as mirrored storage volumes, the configuration/error module is further operable to:

read a first sector of the first storage volume;

determine that the first sector of the first storage volume included bad data; and

read the first sector of the second storage volume in response to determining that the first sector of the first storage volume included bad data.

10. The information handling system of claim 9 , wherein, after reading the first sector of the second storage volume, the configuration/error module is further operable to:

read a second sector of the second storage volume;

determine that the second sector of the second storage volume included bad data; and

read the second sector of the first storage volume in response to determining that the second sector of the second storage volume included bad data.

11. A method comprising:

reading, by a configuration detection and error handling (configuration/error) module of an information handling system, a first tag data file from a first storage volume;

reading, by the configuration/error module, a second tag data file from a second storage volume;

determining, by the configuration/error module, that the first storage volume and the second storage volume are configured as mirrored storage volumes based upon the first tag data file and the second tag data file;

reading a first sector of the first storage volume;

determining that the first sector of the first storage volume included bad data;

reading the first sector of the second storage volume in response to determining that the first sector of the first storage volume included bad data; and

booting the information handling system from the mirrored storage volumes.

12. The method of claim 11 , further comprising:

comparing the first tag data file and the second tag data file;

wherein the determination that the first storage volume and the second storage volume are configured as mirrored storage volumes is further based upon the comparison of the first tag data file and the second tag data file.

13. The method of claim 12 , wherein in comparing the first tag data file and the second tag data file, the method further comprises:

comparing a first name of the first tag data file to a second name of the second tag data file;

wherein the first storage volume and the second storage volume are determined to be configured as mirrored storage volumes when the first name is the same as the second name.

14. The method of claim 12 , wherein in comparing the first tag data file and the second tag data file, the method further comprises:

comparing the contents of a first OS boot loader name field of the first tag data file to the contents of a second OS boot loader name filed of the second tag data file;

wherein the first storage volume and the second storage volume are determined to be configured as mirrored storage volumes when the contents of first OS boot loader name field is the same as the contents of second OS boot loader name field.

15. The method of claim 12 , wherein in comparing the first tag data file and the second tag data file, the method further comprises:

comparing the contents of a first OS boot loader authenticator field of the first tag data file to the contents of a second OS boot loader authenticator filed of the second tag data file;

wherein the first storage volume and the second storage volume are determined to be configured as mirrored storage volumes when the contents of first OS boot loader authenticator field is the same as the contents of second OS boot loader authenticator field.

16. The method of claim 15 , wherein:

the contents of the first OS boot loader authenticator field includes a first checksum for a first OS boot loader stored on the first storage volume; and

the contents of the second OS boot loader authenticator field includes a second checksum for a second OS boot loader stored on the second storage volume.

17. The method of claim 15 , wherein:

the contents of the first OS boot loader authenticator field includes a first date stamp for a first OS boot loader stored on the first storage volume; and

the contents of the second OS boot loader authenticator field includes a second date stamp for a second OS boot loader stored on the second storage volume.

18. A non-transitory computer-readable medium including code for performing a method, the method comprising:

reading, by a configuration detection and error handling (configuration/error) module of an information handling system, a first tag data file from a first storage volume;

reading, by the configuration/error module, a second tag data file from a second storage volume;

determining, by the configuration/error module, that the first storage volume and the second storage volume are configured as mirrored storage volumes based upon the first tag data file and the second tag data file;

reading a first sector of the first storage volume;

determining that the first sector of the first storage volume included bad data;

reading the first sector of the second storage volume in response to determining that the first sector of the first storage volume included bad data; and

booting the information handling system from the mirrored storage volumes.

Assignments (15)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061753/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001) Recorded Apr 26, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061324/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 3, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL, L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; WYSE TECHNOLOGY L.L.C.
Reel/Frame 058216/0001 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 040136/0001 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040134/0001 →
RELEASE OF REEL 033625 FRAME 0748 (NOTE) Recorded Sep 14, 2016
From: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; COMPELLENT TECHNOLOGIES, INC.; SECUREWORKS, INC.
Reel/Frame 040027/0050 →
RELEASE OF REEL 033625 FRAME 0688 (TL) Recorded Sep 14, 2016
From: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; COMPELLENT TECHNOLOGIES, INC.; SECUREWORKS, INC.
Reel/Frame 040027/0757 →
RELEASE OF REEL 033625 FRAME 0711 (ABL) Recorded Sep 13, 2016
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; COMPELLENT TECHNOLOGIES, INC.; SECUREWORKS, INC.
Reel/Frame 040016/0903 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 16, 2014
From: ALI, AHMAD A.J.; ROSE, CHARLES E.
To: DELL PRODUCTS, LP
Reel/Frame 033962/0261 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (TERM LOAN) Recorded Aug 27, 2014
From: COMPELLENT TECHNOLOGIES, INC.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; SECUREWORKS, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 033625/0688 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (ABL) Recorded Aug 27, 2014
From: COMPELLENT TECHNOLOGIES, INC.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; SECUREWORKS, INC.
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 033625/0711 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (NOTES) Recorded Aug 27, 2014
From: COMPELLENT TECHNOLOGIES, INC.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; SECUREWORKS, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 033625/0748 →