UEFI Boot Meta Data Dynamic Image Location

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Information handling systems face challenges in booting and accessing diagnostic or service OS images during pre-boot environments due to limitations in existing filesystems, such as FAT32 and EFI System Partition, which are time-consuming and unable to handle larger images or function without internet connectivity.

Innovation Solution

Implementing UEFI Boot Meta Data to dynamically locate and load bootable images from OS partitions without mounting the entire filesystem layout, allowing for faster image booting and system recovery by storing metadata separately and creating a boot loader path, thus overcoming dependencies on specific filesystems like NTFS or EXT3.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire filesystem layout and metadata are mounted in UEFI pre-boot mode to access bootable images, then the bootable images can be accessed, but the process becomes time-consuming and defeats the purpose of dynamic loading

Engineering Contradiction:
Improveaccessibility of bootable imagesVSAvoidboot time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential bootable image files from the filesystem without mounting the entire filesystem layout and metadata. By selectively accessing only the necessary boot images through direct file paths stored in the EFI partition, the system avoids the time-consuming process of mounting complete filesystems while still ensuring reliable access to bootable images.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of performing the complete action of mounting the entire filesystem (which is excessive for the task), the patent performs only the partial action needed - directly accessing specific bootable image files through stored paths. This partial approach achieves the goal of boot image accessibility without the overhead of complete filesystem mounting.

Inventive Principle:
Principle #16Partial or excessive action

2Ease of operation

If the EFI System Partition is used to store bootable images, then pre-boot access is enabled, but the partition space is limited and cannot house larger images such as diagnostic OS images

Engineering Contradiction:
Improvepre-boot accessibilityVSAvoidstorage capacity
Core Design Contradiction:
Ease of operationVSVolume of stationary object

Solution Approach 1:

The patent segments the storage architecture into two parts: the EFI System Partition (ESP) stores only the essential boot loader and metadata, while the actual bootable images (including large diagnostic OS images) are stored in the main OS partition. This segmentation allows the ESP to maintain its role in pre-boot accessibility while the larger capacity OS partition accommodates larger images.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a boot loader as an intermediary component in the ESP that facilitates access to bootable images stored in the OS partition. The boot loader acts as a mediator that bridges the pre-boot environment and the full filesystem, enabling the system to load large images from the OS partition without requiring them to be stored in the limited ESP space.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If bootable images are stored in non-contiguous locations in OS partitions, then storage flexibility is improved, but the system cannot locate and access these images during pre-boot environment

Engineering Contradiction:
Improvestorage flexibilityVSAvoidlocatability of boot images
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent performs preliminary action by storing the file paths and locations of bootable images in the EFI partition during the image creation process. This advance recording of location information enables the pre-boot environment to locate and access bootable images stored in non-contiguous locations in the OS partition without difficulty, as the paths are already known and stored.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If FAT32 filesystem is used in UEFI pre-boot mode, then bootable images can be accessed, but the overhead of mounting the entire filesystem layout and metadata is time-consuming

Engineering Contradiction:
Improvefilesystem compatibilityVSAvoidboot speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the essential functionality needed for boot image access from the FAT32 filesystem mounting process. Instead of mounting the entire FAT32 filesystem with all its layout and metadata overhead, the system directly accesses bootable images using stored file paths, extracting only the necessary file access capability without the complete filesystem mounting overhead.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Instead of performing the complete FAT32 filesystem mounting action (which is excessive), the patent performs only the partial action of directly accessing files through stored paths. This partial approach maintains filesystem compatibility while eliminating the time-consuming mounting overhead.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11169818B2Systems and methods for dynamically locating and accessing operating system (OS) file system data from a pre-boot environment
Publication Date: 2021.11.09 DELL PROD LP
  • US11169818B2 patent drawing
  • US11169818B2 patent drawing
  • US11169818B2 patent drawing

AI summary

Systems and methods that may be implemented in a Unified Extensible Firmware Interface (UEFI) pre-boot environment time to dynamically locate and load bootable images stored in one or more operating system (OS) partitions on a system storage device/s (e.g., HDD, SSD) that is formatted with an advanced filesystem (e.g., such as NTFS, EXT3, etc.). An OS-based filesystem-independent method may be provided to access OS filesystem data during UEFI pre-boot time. Individual selected boot images stored across multiple OS filesystem partitions may be located and loaded to boot from UEFI pre-boot.