IP Library › Granted Patent US 10,459,812
Granted Patent B2
US 10,459,812 · App. 15/402,494 · Granted Oct 29, 2019

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

Inventors: Ahmad A. J. Ali (Austin, TX); Charles E. Rose (Nashua, NH)
Assignee: Dell Products, LP
G06F11/2064G06F9/4408G06F11/073G06F11/079G06F11/0727G06F11/0763G06F11/1004G06F11/20G06F2201/805G06F2201/82
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 10,459,812
App. No.
15/402,494
Granted
Oct 29, 2019
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 (74)

1. An information handling system comprising:

a processor; and

a configuration detection and error handler configured 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 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.

2. The information handling system of claim 1 , wherein the handler is further configured 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 handler is further configured 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 handler is further configured 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 handler is further configured 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, after reading the first sector of the second storage volume, the handler is further configured 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.

9. 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 after determining that the first storage volume and the second storage volume are configured as mirrored storage volumes;

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

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

10. The method of claim 9 , 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.

11. The method of claim 10 , 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.

12. The method of claim 10 , 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.

13. The method of claim 10 , 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.

14. The method of claim 13 , 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.

15. The method of claim 13 , 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.

16. The method of claim 9 , wherein, after reading the first sector of the second storage volume, the method further comprises:

reading a second sector of the second storage volume;

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

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

17. An information handling system comprising:

a processor; and

a configuration detection and error handler configured 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; and

after determining that the first storage volume and the second storage volume are configured as mirrored storage volumes, 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.

18. The information handling system of claim 17 wherein, after reading the first sector of the second storage volume, the configuration/error module is further configured 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.

Assignments (11)
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 (051302/0528) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO WYSE TECHNOLOGY L.L.C.); SECUREWORKS CORP.
Reel/Frame 060438/0593 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (041829/0873) Recorded Apr 26, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO WYSE TECHNOLOGY L.L.C.)
Reel/Frame 059803/0724 →
RELEASE OF SECURITY INTEREST AT REEL 041808 FRAME 0516 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL INTERNATIONAL, L.L.C.; DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; MOZY, INC.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 058297/0573 →
RELEASE OF SECURITY INTEREST AT REEL 051449 FRAME 0728 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.; SECUREWORKS CORP.; EMC CORPORATION
Reel/Frame 058002/0010 →
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 Dec 31, 2019
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.; SECUREWORKS CORP.; EMC CORPORATION
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 051449/0728 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Dec 16, 2019
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC; WYSE TECHNOLOGY L.L.C.; SECUREWORKS CORP.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 051302/0528 →
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 →
PATENT SECURITY INTEREST (NOTES) Recorded Feb 28, 2017
From: DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; MOZY, INC.; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 041829/0873 →
PATENT SECURITY INTEREST (CREDIT) Recorded Feb 24, 2017
From: DELL INTERNATIONAL, L.L.C.; DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; MOZY, INC.; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 041808/0516 →
Continuity (2)
Continuation 14333232 · Jul 16, 2014
Related Publication 20170132098A1 · May 11, 2017