Storage Controller Driver Sequence Management for Drive Letter Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing management of storage controllers in electronic devices results in randomly allocated drive letters, leading to chaos and potential data storage exceptions, as the sequence of running drivers is difficult to determine, causing non-continuous drive letter allocation and incorrect operations between system and data disks.
Innovation Solution
A method is introduced where the driver configuration files of a second storage controller are updated to include information in the driver image files, prioritizing the start time of the second storage controller during the virtual file system initialization, and allocating drive letters accordingly, while the first storage controller is started during the root file system initialization, ensuring continuous drive letter allocation across connected storage mediums.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If storage controllers run drivers in multithreaded mode, then driver execution flexibility is improved, but driver execution sequence becomes uncertain causing random drive letter allocation
Solution Approach 1:
The patent applies preliminary action by setting a driver execution sequence before multithreaded drivers actually run. The system determines and records the execution order of drivers before they operate, ensuring that even though drivers run in multithreaded mode with flexibility, they follow a predetermined sequence that guarantees consistent drive letter allocation. This resolves the contradiction by preparing the execution order in advance without restricting the multithreaded operation capability.
2Productivity
If drive letters are allocated randomly, then allocation speed is improved, but operational correctness deteriorates causing data storage exceptions
Solution Approach 1:
The system performs preliminary determination of the driver execution sequence before drive letter allocation occurs. By establishing the execution order in advance and recording it, the system ensures that drive letters are allocated in a predetermined sequence rather than randomly, guaranteeing operational correctness while maintaining efficient allocation speed through the pre-planned sequence.
Solution Approach 2:
The patent implements feedback by recording the actual driver execution sequence and using this information to allocate drive letters. The system monitors which driver executes first, second, third, etc., and uses this feedback information to assign drive letters accordingly. This feedback mechanism ensures that drive letter allocation matches the actual execution sequence, preventing operational errors while maintaining speed.
3Adaptability or versatility
If multiple storage controllers operate independently, then system scalability is improved, but drive letter continuity across controllers is lost
Solution Approach 1:
The patent merges the drive letter allocation management across multiple independent storage controllers by establishing a unified execution sequence that spans all controllers. Instead of each controller managing its own drive letters independently, the system coordinates the driver execution sequence across all controllers and allocates drive letters continuously according to this unified sequence, maintaining stability while preserving the scalability of having multiple independent controllers.
Data Source
AI summary
A method for managing storage controllers of an electronic device comprises acquires driver configuration files of first and second storage controller. A driver mapping file of a root file system is acquired according to the driver configuration files of the first storage controller and the second storage controller. The driver configuration file of the second storage controller is updated. A driver image file of the virtual file system is updated according to the driver configuration file of the second storage controller. An operation system of the electronic device is rebooted. The driver of the second storage controller is started according to the driver image file when the virtual file system starts, and the driver of the first storage controller is started according to the driver mapping file when a root file system starts. An electronic device and a computer readable storage medium applying the method are also disclosed.