Reboot Management via Master Flag and Component Stack
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Storage systems face significant downtime during firmware, software, and hardware upgrades due to the need for individual reboots of each upgrade component, leading to prolonged unavailability of electronic content.
Innovation Solution
A method that utilizes a master reboot flag and an initiation component stack to determine and manage reboot requirements, allowing for immediate, deferred, or no reboots, thereby minimizing downtime by consolidating reboot procedures and avoiding endless reboot loops.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If individual reboots are performed for each firmware, software, and hardware upgrade component, then system integrity is ensured, but downtime is significantly prolonged
Solution Approach 1:
The patent combines multiple individual reboot operations into a single consolidated reboot operation. The system executes a stack of initiation components (firmware, software, hardware upgrades) and consolidates all necessary reboots into one final reboot operation, thereby ensuring system integrity while dramatically reducing the total downtime compared to performing separate reboots for each component.
Solution Approach 2:
The system performs preliminary actions by executing the complete stack of initiation components and setting a master reboot flag to 'reboot required' before the final reboot. This allows all upgrade components to be prepared and staged in advance, with the actual reboot deferred until the optimal moment, thus minimizing system unavailability while ensuring all updates are ready to be applied together.
2Reliability
If multiple individual reboots are performed during upgrades, then each component is properly initialized, but the risk of endless reboot loops increases
Solution Approach 1:
The system implements a master reboot flag that provides feedback control over the reboot process. Each initiation component checks the master reboot flag status, and the flag is set to 'reboot required' only when necessary and cleared after the reboot is executed. This feedback mechanism ensures proper component initialization while preventing endless reboot loops by providing a centralized control point that tracks and manages reboot states throughout the upgrade process.
3Productivity
If reboots are deferred to minimize downtime, then system availability is improved, but the risk of delaying necessary reboots must be managed
Solution Approach 1:
The system dynamically adjusts the reboot timing based on the execution status of initiation components. The master reboot flag transitions from 'no reboot required' to 'reboot required' at appropriate moments during the component stack execution, allowing the system to defer reboots when safe to maximize availability, while ensuring reboots are executed at the correct moment to maintain reliability. This dynamic approach optimizes the balance between system availability and reboot timing accuracy.
Data Source
AI summary
A method, computer program product, and computing system for initiating a computing device includes setting a master reboot flag to no reboot required. A first software component in an initiation component stack is executed. Upon completing execution of the first software component, a determination is made concerning whether the computing device requires: an immediate reboot, a deferred reboot, or no reboot.