Boot Disk Tracking via Raw State Marker Across Reboots
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
During the configuration and testing of computing devices, reboots can cause the disk numbering enumerated by the operating system to change, leading to potential failure in identifying the correct boot disk, which may result in incorrect installation of the customer OS and poor performance.
Innovation Solution
A marker is written to a designated region of the selected storage device in a raw state, allowing the system to identify and retain the boot disk across reboots, ensuring correct disk identification and configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the computing device is rebooted multiple times during testing and configuration, then the hardware components can be tested and configured, but the disk numbering enumerated by the operating system will be re-ordered, leading to potential failure in identifying the correct boot disk
Solution Approach 1:
The system performs a preliminary action by writing a marker to the boot disk before rebooting. This marker serves as a persistent identifier that survives reboots, allowing the system to reliably identify the correct boot disk even when disk numbering changes during multiple reboots in the testing and configuration process.
2Adaptability or versatility
If disk numbering is re-ordered after reboots, then the operating system can re-enumerate storage devices, but the boot disk identification becomes incorrect, resulting in wrong OS installation and poor performance
Solution Approach 1:
The marker acts as an intermediary element between the boot disk and the operating system's disk enumeration system. Instead of relying on transient disk numbering that changes with reboots, the marker provides a stable reference that mediates the identification process, ensuring accurate boot disk selection regardless of how the operating system re-enumerates storage devices.
3Device complexity
If the system relies on operating system disk enumeration to identify the boot disk, then the configuration process is simple, but the system becomes vulnerable to disk re-ordering during reboots
Solution Approach 1:
The boot disk essentially serves itself by containing the marker that identifies it across reboots. The marker is written to the boot disk during the configuration process and remains there, allowing the disk to be reliably identified without requiring complex tracking mechanisms or external reference systems. This self-identifying capability maintains reliability while keeping the configuration process relatively simple.
Data Source
AI summary
An apparatus in one embodiment comprises at least one processing device having a processor coupled to a memory. The processing device is configured to identify a given computing device that includes two or more storage devices, and to select a given one of the two or more storage devices as a boot disk for the given computing device, the given storage device being in a raw state. The processing device is also configured to write a marker to a designated region of the given storage device in the raw state, and to reboot the given computing device. The processing device is further configured to utilize the marker to identify the given storage device in the raw state as the boot disk for the given computing device subsequent to rebooting the given computing device.