Operating System Upgrade With Recovery-Mode Partition Table Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing operating system upgrade methods fail to efficiently adjust the partition architecture during version upgrades, particularly when adding or deleting partitions, due to the inability to modify the partition table in the recovery mode without access to user data.
Innovation Solution
A method involving a virtual A/B upgrade and recovery mode is proposed, where the partition table is refreshed in the recovery mode, and the operating system is started to upgrade data in a virtual A/B manner, utilizing a reserve partition to add or delete partitions without affecting the availability of existing partitions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the partition table is modified during operating system upgrade to add or delete partitions, then the partition architecture can be adjusted to meet new version requirements, but the existing recovery mode cannot access user data to perform partition modifications
Solution Approach 1:
The partition table modification process is segmented into two independent phases: (1) Partition architecture adjustment phase where the partition table is modified to add/delete partitions, and (2) User data migration phase where user data is copied from old partitions to new partitions. This segmentation allows partition structure changes to be performed without requiring access to user data during the modification process, resolving the contradiction between adaptability and ease of operation.
Solution Approach 2:
The partition table is modified in advance before user data migration occurs. The system performs preliminary partition architecture adjustments by updating the partition table to reflect the new partition structure, then subsequently migrates user data to the newly created or modified partitions. This preliminary action enables the partition table to be adjusted without requiring access to user data during the modification process.
2Adaptability or versatility
If the partition table is updated in recovery mode without access to user data, then partition architecture can be adjusted, but user data security and availability cannot be ensured
Solution Approach 1:
The system introduces an intermediary data migration process that acts as a bridge between partition table modification and user data access. The partition table is first modified to establish the new partition structure, then user data is migrated through this intermediary process to the new partitions. This intermediary mechanism ensures that partition architecture can be flexibly adjusted while user data security is maintained through controlled migration procedures including verification and rollback capabilities.
3Adaptability or versatility
If the operating system upgrade process modifies partition architecture, then the system can support new version requirements, but the upgrade process becomes more complex and time-consuming
Solution Approach 1:
The upgrade process is designed to be dynamic and adaptive based on the specific partition changes required. The system automatically detects whether partition architecture modification is needed for the target version, and only performs the complex partition table modification and data migration steps when necessary. For upgrades that don't require partition changes, the system skips these complex steps and performs only simple data updates, thereby reducing overall upgrade complexity while maintaining version upgrade compatibility.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments of this application provide an operating system upgrade method and device, a storage medium, and a computer program product. The method includes: obtaining an operating system upgrade package, where the operating system upgrade package includes a second partition table and operating system upgrade data, and address configurations of partitions with a same name are consistent in the second partition table and the first partition table; triggering a first restart of the electronic device, where after the first restart, the electronic device enters a recovery mode; updating a partition table of the electronic device to the second partition table in the recovery mode; triggering a second restart of the electronic device, where after the second restart, the electronic device loads data of a basic partition, a first static partition, and a dynamic partition to run the first operating system; and upgrading an operating system of the electronic device according to the operating system upgrade data, and upgrading the first operating system to a second operating system. An upgrade solution in the embodiments of this application greatly simplifies operation difficulty of updating a partition table, and improves user experience.