WO2019144621A1 - Procédé, appareil et serveur pour acquérir un élément de démarrage d'os uefi - Google Patents

Procédé, appareil et serveur pour acquérir un élément de démarrage d'os uefi Download PDF

Info

Publication number
WO2019144621A1
WO2019144621A1 PCT/CN2018/103435 CN2018103435W WO2019144621A1 WO 2019144621 A1 WO2019144621 A1 WO 2019144621A1 CN 2018103435 W CN2018103435 W CN 2018103435W WO 2019144621 A1 WO2019144621 A1 WO 2019144621A1
Authority
WO
WIPO (PCT)
Prior art keywords
startup item
startup
uefi
valid
bios
Prior art date
Application number
PCT/CN2018/103435
Other languages
English (en)
Chinese (zh)
Inventor
颜伟
Original Assignee
郑州云海信息技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 郑州云海信息技术有限公司 filed Critical 郑州云海信息技术有限公司
Publication of WO2019144621A1 publication Critical patent/WO2019144621A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4406—Loading of operating system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4406—Loading of operating system
    • G06F9/4408—Boot device selection

Definitions

  • the present application relates to the field of server technologies, and in particular, to a method, an apparatus, and a server for acquiring a UEFI OS startup item.
  • UEFI Unified Extensible Firmware Interface
  • This interface allows the operating system to automatically load from a pre-booted operating environment to an operating system.
  • UEFI OS Operating System
  • some Internet companies use UEFI OS in their data center deployments, which are typically customized for UEFI OS based on internal services in order to better utilize the performance of the application.
  • the UEFI OS startup item path is also customized, so that the traditional startup scheme is not applicable to the customized UEFI OS, which causes the data center data system to fail to recover in time, causing irreparable damage to the customer.
  • a method, a device, and a server for acquiring a UEFI OS startup item are provided in the embodiment of the present application, so as to solve the problem that the startup solution in the prior art is not applicable to the customized UEFI OS, and the data center data system cannot be restored in time. .
  • the embodiment of the present application provides a method for acquiring a UEFI OS startup item, where the method includes:
  • the searching hard disk boot partition starts a directory of startup items, including:
  • the UEFI OS startup item is created according to the valid startup item file
  • the startup item directory in the hard disk boot partition is searched.
  • the BIOS OS After the first installation of the BIOS OS, the BIOS OS writes the BIOS OS startup item information in the BIOS NVRAM;
  • the searching for a valid startup item file in the preset whitelist startup item path includes: if the BIOS OS startup item information is not found in the BIOS NVRAM, searching for the preset whitelist startup item path is valid. Startup file.
  • the embodiment of the present application provides an apparatus for acquiring a UEFI OS startup item, including:
  • a search module for searching a boot entry directory in a hard disk boot partition
  • a search module for finding a valid startup item file in the startup item directory
  • a module is created for creating a UEFI OS startup item according to the valid startup item file.
  • the searching hard disk boot partition starts a directory of startup items, including:
  • the UEFI OS startup item is created according to the valid startup item file
  • the startup item directory in the hard disk boot partition is searched.
  • the BIOS OS After the first installation of the BIOS OS, the BIOS OS writes the BIOS OS startup item information in the BIOS NVRAM;
  • the searching for a valid startup item file in the preset whitelist startup item path includes: if the BIOS OS startup item information is not found in the BIOS NVRAM, searching for the preset whitelist startup item path is valid. Startup file.
  • an embodiment of the present application provides a server, including:
  • a memory for storing execution instructions of the processor
  • processor is configured to perform the method of any of the above first aspects.
  • the BIOS when the BIOS is upgraded or the motherboard is replaced on the existing UEFI OS system, the NVRAM is not erased, and the UEFI OS cannot be accessed; The way to cover the customized UEFI OS startup path, the valid UEFI OS startup items that cannot be found in the whitelist will not be missed, and the system will start normally.
  • FIG. 1 is a schematic flowchart of a method for acquiring a UEFI OS startup item according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of another method for obtaining a UEFI OS startup item according to an embodiment of the present disclosure
  • FIG. 3 is a schematic structural diagram of an apparatus for acquiring a UEFI OS startup item according to an embodiment of the present disclosure
  • FIG. 4 is a schematic structural diagram of a server according to an embodiment of the present application.
  • UEFI Unified Extensible Firmware Interface, a unified and extensible firmware interface
  • BIOS Basic Input Output System, basic input and output system
  • NVRAM Non-Volatile Random Access Memory, non-volatile random access memory
  • OS Operating System, operating system.
  • the OS After the UEFI OS is installed for the first time, the OS writes the UEFI OS startup item information in the BIOS NVRAM to ensure that the OS can start normally. Specifically, the startup content BOOTXXXX of the UEFI OS is written into the BIOS NVRAM, and the BIOS creates a startup item according to the content of the BOOTXXXX in the NVRAM and performs a system booting operation during the startup process.
  • the UEFI OS startup item information created by the OS in the BIOS NVRAM is erased. After the operation and maintenance operation is completed, the system is powered on again. If the UEFI OS startup item information is not found in the BIOS NVRAM, the boot failure will occur.
  • a boot entry can be created for the installed UEFI OS by the UEFI OS boot entry path recorded in the whitelist.
  • the whitelist contains the UEFI OS boot entry paths for all releases.
  • the UEFI OS startup item path will also be customized.
  • the general standard Redhat UEFI OS boot path is ⁇ EFI ⁇ Redhat ⁇ grub.efi, or the generic path ⁇ EFI ⁇ BOOT ⁇ BOOTX64.efi.
  • the customized UEFI OS startup path is ⁇ EFI ⁇ INT ⁇ grubx64.efi (INT stands for the user company name). This path is different from the startup path of all distribution UEFI OS.
  • the customized UEFI OS startup entry path cannot be found by whitelisting, and a valid startup entry file cannot be found, causing the startup to fail.
  • the embodiment of the present application adopts an automatic search mode to read a valid startup item file in the hard disk boot partition, thereby correctly creating a UEFI OS startup item, and completing the normal startup of the system.
  • FIG. 1 is a schematic flowchart of a method for obtaining a UEFI OS startup item according to an embodiment of the present disclosure. As shown in FIG. 1 , the method mainly includes the following steps.
  • Step S101 Search for a startup item directory in the hard disk boot partition.
  • the startup item directory contains the startup item file, such as the /EFI directory in the hard disk boot partition.
  • Step S102 Find a valid startup item file in the startup item directory. For example, the *.efi file.
  • Step S103 Create a UEFI OS startup item according to the valid startup item file.
  • the BIOS when the BIOS is upgraded or the motherboard is replaced on the existing UEFI OS system, the NVRAM is not erased, and the UEFI OS cannot be accessed; The way to cover the customized UEFI OS startup path, the valid UEFI OS startup items that cannot be found in the whitelist will not be missed, and the system will start normally.
  • FIG. 2 is a schematic flowchart of another method for obtaining a UEFI OS startup item according to an embodiment of the present disclosure. As shown in FIG. 2, the method mainly includes the following steps.
  • Step S201 Find BIOS OS startup item information in the BIOS NVRAM.
  • the OS After the UEFI OS is installed for the first time, the OS writes the UEFI OS startup item information in the BIOS NVRAM to ensure that the OS can start normally. Specifically, the startup content BOOTXXXX of the UEFI OS is written into the BIOS NVRAM, and the BIOS creates a startup item according to the content of the BOOTXXXX in the NVRAM and performs a system booting operation during the startup process.
  • Step S202 Determine whether the BIOS OS startup item information is found in the BIOS NVRAM.
  • BIOS OS startup item information is found in the BIOS NVRAM, the process proceeds to step S203; if the BIOS OS startup item information is not found in the BIOS NVRAM, the UEFI OS startup item information created by the OS in the BIOS NVRAM is erased. It may be caused by replacing the motherboard or updating the BIOS, and then proceeds to step S204.
  • Step S203 Create a startup item according to the UEFI OS startup item information in the BIOS NVRAM and perform a system booting action.
  • Step S204 Find a valid startup item file in the startup entry path of the preset whitelist.
  • the whitelist contains the UEFI OS startup entry path for all distributions.
  • Step S205 Determine whether a valid startup item file is found in the startup entry path of the preset whitelist.
  • step S206 If a valid startup item file is found in the preset whitelist startup item path, proceed to step S206; if a valid startup item file is not found in the preset whitelist startup item path, the UEFI OS is started. If the item path has been customized and modified, the process proceeds to step S207.
  • Step S206 Create a UEFI OS startup item according to the valid startup item file.
  • the valid startup item file here refers to a valid startup item file found through the whitelist's startup item path.
  • Step S207 Search for a startup item directory in the hard disk boot partition.
  • Step S208 Find a valid startup item file in the startup item directory.
  • Step S209 Create a UEFI OS startup item according to the valid startup item file.
  • the startup item is created by using the UEFI OS startup item information in the BIOS NVRAM, and then the startup item is created by using the UEFI OS startup item information in the white list, and finally the startup item is created by using the automatic search mode.
  • the startup strategy coexists, and the system startup efficiency is improved while ensuring that the system can be started normally.
  • FIG. 3 is a schematic structural diagram of an apparatus for acquiring a UEFI OS startup item according to an embodiment of the present application, as shown in FIG.
  • the device includes the following modules.
  • the searching module 301 is configured to search for a startup item directory in the hard disk boot partition
  • the searching module 302 is configured to search for a valid startup item file in the startup item directory
  • the creating module 303 is configured to create a UEFI OS startup item according to the valid startup item file.
  • the BIOS when the BIOS is upgraded or the motherboard is replaced on the existing UEFI OS system, the NVRAM is not erased, and the UEFI OS cannot be accessed; The way to cover the customized UEFI OS startup path, the valid UEFI OS startup items that cannot be found in the whitelist will not be missed, and the system will start normally.
  • the searching hard disk boot partition starts a directory of startup items, including:
  • the UEFI OS startup item is created according to the valid startup item file
  • the startup item directory in the hard disk boot partition is searched.
  • the BIOS OS after the first installation of the BIOS OS, the BIOS OS writes the BIOS OS startup item information in the BIOS NVRAM;
  • the searching for a valid startup item file in the preset whitelist startup item path includes: if the BIOS OS startup item information is not found in the BIOS NVRAM, searching for the preset whitelist startup item path is valid. Startup file.
  • the startup item is created by using the UEFI OS startup item information in the BIOS NVRAM, and then the startup item is created by using the UEFI OS startup item information in the white list, and finally the startup item is created by using the automatic search mode.
  • the startup strategy coexists, and the system startup efficiency is improved while ensuring that the system can be started normally.
  • FIG. 4 is a schematic structural diagram of a server according to an embodiment of the present disclosure.
  • the server 400 may include: a processor 410, a memory 420, and a communication unit 430. These components communicate through one or more buses. It will be understood by those skilled in the art that the structure of the server shown in the figure does not constitute a limitation of the present application, and it may be a bus structure or a star structure. More or fewer components may be included than in the drawings, or some components may be combined, or different component arrangements.
  • the communication unit 430 is configured to establish a communication channel, so that the storage device can communicate with other devices. Receive user data sent by other devices or send user data to other devices.
  • the processor 410 which is a control center of the storage device, connects various parts of the entire electronic device by using various interfaces and lines, by running or executing software programs and/or modules stored in the memory 420, and calling the storage in the memory. Data to perform various functions of the electronic device and/or process data.
  • the processor may be composed of an integrated circuit (IC), for example, may be composed of a single packaged IC, or may be composed of a plurality of packaged ICs that have the same function or different functions.
  • the processor 410 may include only a Central Processing Unit (CPU).
  • the CPU may be a single operation core, and may also include a multi-operation core.
  • the memory 420 is configured to store execution instructions of the processor 410, and the memory 420 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), Erase programmable read only memory (EEPROM), erasable programmable read only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
  • SRAM static random access memory
  • EEPROM Erase programmable read only memory
  • EPROM erasable programmable read only memory
  • PROM programmable read only memory
  • ROM read only memory
  • magnetic memory magnetic memory
  • flash memory magnetic or optical disk.
  • the terminal 400 When the execution instructions in the memory 420 are executed by the processor 410, the terminal 400 is enabled to perform some or all of the steps of the above method embodiments.
  • the present application further provides a computer storage medium, wherein the computer storage medium may store a program, and the program may include some or all of the steps in the embodiments provided by the application.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (English: read-only memory, abbreviated as: ROM) or a random access memory (English: random access memory, abbreviation: RAM).
  • the technology in the embodiments of the present application can be implemented by means of software plus a necessary general hardware platform.
  • the technical solution in the embodiments of the present application may be embodied in the form of a software product in essence or in the form of a software product, and the computer software product may be stored in a storage medium such as a ROM/RAM. , a diskette, an optical disk, etc., including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application or portions of the embodiments.
  • a computer device which may be a personal computer, server, or network device, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention concerne un procédé, un appareil et un serveur pour acquérir un élément de démarrage d'OS UEFI, le procédé consistant à : rechercher un répertoire d'éléments de démarrage dans une partition de démarrage de disque dur (S101) ; trouver un fichier d'élément de démarrage valide dans le répertoire d'éléments de démarrage (S102) ; et, sur la base du répertoire d'éléments de démarrage valide, créer un élément de démarrage d'OS UEFI (S103). À l'aide du présent procédé, lors de la mise en œuvre d'une opération telle qu'une mise à niveau de BIOS ou le remplacement d'une carte mère sur un système avec un système d'exploitation UEFI existant, la situation ne peut pas entrer dans l'OS UEFI en raison de l'effacement de la NVRAM. Le procédé de recherche automatique couvre un chemin de démarrage d'OS UEFI personnalisé, et des éléments de démarrage d'OS UEFI valides qui ne peuvent pas être trouvés sur une liste blanche ne seront pas manqués, assurant le fonctionnement normal du système.
PCT/CN2018/103435 2018-01-25 2018-08-31 Procédé, appareil et serveur pour acquérir un élément de démarrage d'os uefi WO2019144621A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810073935.0A CN108287735A (zh) 2018-01-25 2018-01-25 一种获取uefi os启动项的方法、装置及服务器
CN201810073935.0 2018-01-25

Publications (1)

Publication Number Publication Date
WO2019144621A1 true WO2019144621A1 (fr) 2019-08-01

Family

ID=62835820

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/103435 WO2019144621A1 (fr) 2018-01-25 2018-08-31 Procédé, appareil et serveur pour acquérir un élément de démarrage d'os uefi

Country Status (2)

Country Link
CN (1) CN108287735A (fr)
WO (1) WO2019144621A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108287735A (zh) * 2018-01-25 2018-07-17 郑州云海信息技术有限公司 一种获取uefi os启动项的方法、装置及服务器
CN109002330A (zh) * 2018-07-27 2018-12-14 郑州云海信息技术有限公司 一种识别uefi os启动项的方法、装置及设备
CN112905252A (zh) * 2021-02-20 2021-06-04 山东英信计算机技术有限公司 一种服务器bios启动项顺序的排序方法及介质
CN114546502B (zh) * 2022-02-11 2023-08-25 苏州浪潮智能科技有限公司 一种基于白名单创建启动项的方法、装置及可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8060734B1 (en) * 2008-10-13 2011-11-15 Symantec Corporation Systems and methods for providing recommendations to improve boot performance based on community data
CN103294500A (zh) * 2012-03-05 2013-09-11 联想(北京)有限公司 一种信息处理的方法及电子设备
CN106897063A (zh) * 2017-02-22 2017-06-27 郑州云海信息技术有限公司 一种基于efi将os启动项永久添加至bios中的方法及系统
US20170308704A1 (en) * 2016-04-20 2017-10-26 Sophos Limited Boot security
CN108287735A (zh) * 2018-01-25 2018-07-17 郑州云海信息技术有限公司 一种获取uefi os启动项的方法、装置及服务器

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106201604A (zh) * 2016-07-01 2016-12-07 南京百敖软件有限公司 一种计算机多应用场景的启动配置方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8060734B1 (en) * 2008-10-13 2011-11-15 Symantec Corporation Systems and methods for providing recommendations to improve boot performance based on community data
CN103294500A (zh) * 2012-03-05 2013-09-11 联想(北京)有限公司 一种信息处理的方法及电子设备
US20170308704A1 (en) * 2016-04-20 2017-10-26 Sophos Limited Boot security
CN106897063A (zh) * 2017-02-22 2017-06-27 郑州云海信息技术有限公司 一种基于efi将os启动项永久添加至bios中的方法及系统
CN108287735A (zh) * 2018-01-25 2018-07-17 郑州云海信息技术有限公司 一种获取uefi os启动项的方法、装置及服务器

Also Published As

Publication number Publication date
CN108287735A (zh) 2018-07-17

Similar Documents

Publication Publication Date Title
WO2019144621A1 (fr) Procédé, appareil et serveur pour acquérir un élément de démarrage d'os uefi
US8423991B2 (en) Embedded network device and firmware upgrading method
JP5368947B2 (ja) プラットフォームの高速リスタートを可能にする方法およびシステム
US8171280B2 (en) Method of running multiple operating systems on an X86-based computer system having a dedicated memory region configured as a do not use region
US8433890B2 (en) Preparing and preserving a system configuration during a hot upgrade
US8171276B2 (en) Minimal startup mode for performing multiple-reboot configuration
US20170010884A1 (en) Systems And Methods To Securely Inject Binary Images And Code Into Firmware
US20060020845A1 (en) Unattended BIOS recovery
US10019598B2 (en) Dynamic service discovery
US20160335080A1 (en) Method and apparatus for patching
US8918776B2 (en) Self-adapting software system
US10936407B2 (en) System and method to reduce address range scrub execution time in non-volatile dual inline memory modules
US10664598B1 (en) Firmware security patch deployment
US9235426B2 (en) Multicore processor system, computer product, and notification method for updating operating system
WO2012031567A1 (fr) Procédé de résilience, et dispositif pour système de fichiers
CN106598651A (zh) 一种嵌入式系统及该系统的升级方法
CN115390996A (zh) 虚拟机迁移方法和装置、计算设备和存储介质
CN103455750B (zh) 一种嵌入式设备的高安验证方法及装置
US9026777B2 (en) Automatic update of persistent boot parameter storage
CN115291946A (zh) 鸿蒙系统移植方法、装置、电子设备及可读介质
JP7102524B2 (ja) 複数のバイナリイメージのファームウェア公開
CN114780019A (zh) 电子设备的管理方法、装置、电子设备及存储介质
CN114385251A (zh) 基于存储器的操作系统引导方法、系统、终端及存储介质
CN102591691B (zh) 硬盘启动方法和基于bios的操作系统启动加载方法
CN112631621A (zh) 一种依赖包管理方法、装置、服务器及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18901929

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18901929

Country of ref document: EP

Kind code of ref document: A1