Firmware Partition Switching for Block Error Correction

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing information handling systems face challenges in timely detection and management of firmware corruption due to failures in flash memory devices, leading to disruptive reboots when multiple block failures occur, and they lack efficient mechanisms for correcting all detected bad memory blocks during a single reboot.

Innovation Solution

The implementation of a baseboard management controller that initiates a DM-Verity daemon for periodic patrol reads of firmware partitions, detects block failures, and switches to a redundant firmware partition upon reaching a threshold of errors, allowing for correction of all bad blocks during a single reboot, thereby reducing the number of reboots and ensuring system stability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If periodic patrol reads are performed to detect block failures, then detection precision is improved, but system complexity increases due to the need for DM-Verity daemon and monitoring mechanisms

Engineering Contradiction:

Improveblock failure detection precisionVSAvoidsystem complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The system employs a DM-Verity daemon that automatically performs patrol reads and monitors firmware partitions for block failures without requiring external intervention. The baseboard management controller autonomously detects errors, switches partitions, and initiates reboots, making the system self-diagnosing and self-correcting.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The baseboard management controller acts as an intermediary between the firmware partitions and the host system. It monitors the health of firmware partitions through patrol reads, detects block failures, and manages the switching between primary and secondary firmware partitions, isolating the complexity of error management from the main system.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If the system switches to a redundant firmware partition upon detecting block failures, then reliability is improved, but the number of reboots increases causing system disruption

Engineering Contradiction:

Improvefirmware availabilityVSAvoidsystem downtime

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system maintains a secondary firmware partition as a pre-prepared backup before any failures occur. When block failures are detected in the primary partition, the system can immediately switch to the pre-configured secondary partition without needing to create or validate a backup at the moment of failure, reducing recovery time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements a redundant firmware partition that serves as a cushion against primary partition failures. This backup partition is maintained in advance with valid firmware images, providing a safety buffer that allows the system to withstand block failures without complete shutdown or extended downtime.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

3Measurement precision

If multiple block failures are detected in the primary firmware partition, then measurement precision is improved, but system stability deteriorates due to repeated reboots

Engineering Contradiction:

Improveerror detection accuracyVSAvoidsystem stability

Core Design Contradiction:

Measurement precisionVSStability of the object's composition

Solution Approach 1:

The firmware is segmented into at least two separate partitions: a primary firmware partition and a secondary firmware partition. This segmentation allows the system to isolate failures to one partition while maintaining operational capability through the other partition, preventing cascading failures and repeated reboots.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system changes the operational parameter of the boot partition by switching from the primary firmware partition to the secondary firmware partition when block failures are detected. This parameter change (active partition selection) allows the system to maintain stability by transitioning to a known good state rather than repeatedly rebooting into a failed state.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS11726879B2Multiple block error correction in an information handling system

Publication Date: 2023.08.15 DELL PROD LP

AI summary

An information handling system includes a first memory and a baseboard management controller. The first memory stores a first firmware partition and a second firmware partition. The baseboard management controller includes a second memory. The baseboard management controller begins execution of a DM-Verity daemon, and performs periodic patrol reads of the first firmware partition. The baseboard management controller detects one or more block failures in the first firmware partition, and stores information associated with the one or more block failures in a message box of the second memory. In response to the entire first firmware partition being scanned, the baseboard management controller switches a boot partition from the first firmware partition to the second firmware partition, and initiates a reboot of the information handling system.