Hardware reset management for universal flash storage
US-2024036977-A1 · Feb 1, 2024 · US
US9575840B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9575840-B1 |
| Application number | US-201414461192-A |
| Country | US |
| Kind code | B1 |
| Filing date | Aug 15, 2014 |
| Priority date | Aug 15, 2014 |
| Publication date | Feb 21, 2017 |
| Grant date | Feb 21, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Aspects of the subject technology relate to executing a boot sequence from a recovery image. A determination of a validity of one or more keyblocks is made. A determination of a first version identifier and a second version identifier is made. A comparison of the first version identifier and the second version identifier is performed. A boot sequence from a recovery image is executed based on the comparison.
Opening claim text (preview).
What is claimed is: 1. A computing system, comprising: one or more processors; and a non-transitory machine-readable medium comprising instructions stored therein, which when executed by the one or more processors, cause the one or more processors to perform operations comprising: detecting a first recovery image accessible to the computing system; determining a validity of a first keyblock associated with the first recovery image; if the first keyblock is determined to be valid, determining a first version identifier associated with the first keyblock; determining a second version identifier, wherein the second version identifier is contained in the computing system; comparing the first version identifier with the second version identifier; determining whether to impose a delay of a predetermined temporal duration prior to executing a boot sequence from the first recovery image based at least on the comparison; and executing the boot sequence from the first recovery image based on determining whether to impose the delay. 2. The computing system of claim 1 , wherein the second version identifier is associated with a second keyblock that is contained in the computing system, the operations further comprising: determining a validity of the second keyblock, wherein the determining the second version identifier and the comparing the first version identifier with the second version identifier are performed when the second keyblock is determined to be valid. 3. The computing system of claim 2 , wherein the operations further comprise: imposing the delay of the predetermined temporal duration prior to executing the boot sequence from the first recovery image when the first keyblock is determined to be valid and the second keyblock is determined to not be valid. 4. The computing system of claim 2 , wherein the operations further comprise: detecting a predetermined input; and imposing the delay of the predetermined temporal duration prior to executing the boot sequence from the first recovery image when the predetermined input is detected, wherein the determining the validity of the second keyblock and determining the second version identifier are not performed when the predetermined input is detected. 5. The computing system of claim 1 , wherein the operations further comprise imposing the delay of the predetermined temporal duration prior to executing the boot sequence from the first recovery image when the first version identifier is associated with a version of a recovery image that is older than a version of the recovery image associated with the second version identifier. 6. The computing system of claim 5 , wherein the operations further comprise providing for display a screen indicating the imposed delay. 7. The computing system of claim 1 , wherein the operations further comprise executing the boot sequence without imposing the delay of the predetermined temporal duration prior to executing the boot sequence from the first recovery image when the first version identifier is associated with a version of a recovery image that is not older than a version of the recovery image associated with the second version identifier. 8. The computing system of claim 1 , wherein the operations further comprise: detecting a predetermined input; and imposing the delay of the predetermined temporal duration prior to executing the boot sequence from the first recovery image when the predetermined input is detected, wherein the determining the second version identifier is not performed when the predetermined input is detected. 9. The computing system of claim 1 , wherein the first recovery image and the first keyblock are contained in a storage device communicably connected to the computing system. 10. The computing system of claim 9 , wherein the storage device is a removable machine-readable storage device connected to the computing system. 11. The computing system of claim 1 , further comprising a non-volatile memory, wherein the second version identifier is contained in a writable portion of the non-volatile memory. 12. A machine-implemented method, comprising: detecting a valid recovery image accessible to a computing system; determining a first version identifier associated with the valid recovery image; determining a second version identifier; comparing the first version identifier with the second version identifier; determining whether to impose a delay of a predetermined temporal duration prior to executing a boot sequence from the valid recovery image based at least on the comparison; and executing the boot sequence from the valid recovery image based on determining whether to impose the delay. 13. The method of claim 12 , wherein the second version identifier is associated with a second keyblock that is contained in the computing system, the method further comprising: determining a validity of the second keyblock, wherein the determining the second version identifier and the comparing the first version identifier with the second version identifier are performed when the second keyblock is determined to be valid. 14. The method of claim 13 , further comprising: imposing the delay of the predetermined temporal duration prior to executing the boot sequence from the valid recovery image when the second keyblock is determined to not be valid. 15. The method of claim 13 , further comprising: detecting a predetermined input; and imposing the delay of the predetermined temporal duration prior to executing the boot sequence from the valid recovery image when the predetermined input is detected, wherein the determining the validity of the second keyblock and determining the second version identifier are not performed when the predetermined input is detected. 16. The method of claim 12 , further comprising imposing the delay of the predetermined temporal duration prior to executing the boot sequence from the valid recovery image when the first version identifier is associated with a version of a recovery image that is older than a version of the recovery image associated with the second version identifier. 17. The method of claim 12 , further comprising executing the boot sequence without imposing the delay of the predetermined temporal duration prior to executing the boot sequence from the valid recovery image when the first version identifier is associated with a version of a recovery image that is not older than a version of the recovery image associated with the second version identifier. 18. A non-transitory machine-readable medium comprising instructions stored therein, which when executed by a system, cause the system to perform operations comprising: detecting a valid recovery image accessible to the system; determining a first version identifier associated with the valid recovery image; determining a second version identifier, wherein the second version identifier is contained in the system; determining, based on the first version identifier and the second version identifier, whether to impose a delay of a predetermined temporal duration prior to executing a boot sequence from the valid recovery image; and executing the boot sequence from the valid recovery image based on determining whether to impose the delay. 19. The non-transitory machine-readable medium of claim 18 , wherein the delay is not imposed when the first version identifier is associated with a version of a recovery image that is not older than a version of the recovery image associated with the second version identifier.
Boot up procedures · CPC title
Restarting or rejuvenating · CPC title
Reconfiguring to eliminate the error (group management mechanisms in a peer-to-peer network H04L67/1044) · CPC title
Point-in-time backing up or restoration of persistent data · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.