CN106897063B - A method and system for permanently adding OS startup items to BIOS based on EFI - Google Patents

Abstract

The invention provides a method and a system for permanently adding an OS starting item into a BIOS based on EFI, wherein the addition of the OS starting item into the BIOS is realized by taking an EFI Shell environment as a carrier and adding the assistance of a Shell. The scheme of the invention can conveniently, efficiently and accurately permanently add the OS starting item into the BIOS, and the OS starting item can not be lost after the BIOS is restarted.

Description

A method and system for permanently adding OS startup items to BIOS based on EFI

technical field

The invention relates to the field of computers, in particular to a method and a system for permanently adding an OS startup item to a BIOS based on EFI.

Background technique

With the continuous development of the IT technology field and the introduction of the concept of Internet +, in the era of rapid development of the information industry and fierce competition, the importance of software and IT services is increasing day by day, and solution provision and IT service capabilities have become the development trend of IT enterprises. Comprehensive development of software and hardware, focusing on the ability to provide solutions, and gradually transforming to IT services are one of Inspur's development strategies, providing tailor-made services for industry users. There are currently a variety of customers, mainly involving the Internet, finance, government, military industry, etc. The OS used by customers is also diversified. At present, some customers use the standard Redhat OS, some customers use CentOS, and some customers use their own developed OS. The OS installation mode is divided into Legacy and UEFI. When the customer's business changes and the motherboard needs to be replaced, there may be a problem that the OS startup item cannot be found, and the OS cannot be entered normally. Although this problem can be solved by releasing the BIOS, after sales, A series of processes such as R&D and development, testing and verification, and release can take as little as one week to reach the customer, which greatly affects the customer's use.

Therefore, a method to permanently add OS boot items to BIOS based on EFI is necessary.

SUMMARY OF THE INVENTION

For solving the above-mentioned technical problems, the technical scheme of the present invention is as follows:

The present invention provides a method for permanently adding OS startup items to BIOS based on EFI, comprising the following steps:

SS1: The client collects its own startup item information and saves it;

SS2: The client reports its own startup item information to the management-level server;

SS3: The management-level server compares the client startup item information reported by the client before the motherboard is replaced and after the motherboard is replaced, and generates the missing startup item caused by the replacement of the motherboard on the client;

SS4: Insert the U disk into the USB interface of the client, and the boot item injector automatically adds the missing boot items to the BIOS of the client according to the missing boot items generated by the management-level server.

Further, step SS4 is specifically:

SS4-1: Store the Shell.efi file to the root directory of the U disk, and insert the U disk into the USB port of the client computer;

SS4-2: When the client computer is turned on, in the Post stage, the system is triggered to enter the startup item selection, and select UEFI: Built-inEFI Shell;

SS4-3: Enter UEFI: Built-in EFI Shell;

SS4-4: Execute the shell>map-r command under UEFI Shell to confirm that the U disk device belongs to fs1, and execute Shell.efi under fs1: to create a complete shell environment;

SS4-5: In the complete shell environment, execute the shell>map-r command to confirm that the HDD device belongs to fs1, and execute bcfgboot add 0grub.efi"A" under fs1: to add the OS boot item to the BIOS, where A Represents a missing startup item.

Further, step SS1 is specifically as follows: when the client starts up, collects its own startup item information and saves it.

Further, step SS2 is specifically as follows: after receiving the monitoring command from the management-level server, the client sends the startup item information of the current system to the management-level server.

Further, step SS3 is specifically as follows: the management-level server compares the client startup item information reported by the client before the motherboard is replaced and after the motherboard is replaced, and if the two startup item information is consistent, no follow-up operation is performed, and if it is inconsistent, a client is generated. The boot item is missing due to the replacement of the motherboard.

Further, after step SS4, step SS5 is also included:

SS5: Enter the client BIOS SETUP to confirm that the missing startup items are added successfully, and enter the OS normally.

Further, before step SS5, execute Ctrl+alt+Delete to restart the client and unplug the U disk.

In addition, the present invention provides a system for permanently adding OS startup items to BIOS based on EFI, including a client computer, a management-level server, a startup item injector, and a U disk, wherein the management-level server, the startup item injector, and the U disk are respectively Connect with the client, the management-level server is connected to the startup item injector, the client collects its own startup item information and saves it when it starts up, and after receiving the monitoring command from the management-level server, the client sends the startup item information of the current system To the management-level server, the management-level server compares the client startup item information reported by the client before the motherboard is replaced and after the motherboard is replaced. If the two startup items are consistent, no subsequent operations will be performed. Missing startup items caused by the motherboard; save the Shell.efi file to the root directory of the U disk, and insert the U disk into the USB interface of the client computer. The startup item injector automatically adds the missing startup items according to the missing startup items generated by the management server. into the client's BIOS.

Further, the startup item injector automatically adds the missing startup item to the BIOS of the client according to the missing startup item generated by the management-level server. Specifically: the client is powered on, and in the Post stage, the startup item injector triggers the system to enter the startup item selection, Select UEFI: Built-in EFI Shell; enter UEFI: Built-in EFI Shell; execute the shell>map-r command under UEFI Shell, confirm that the U disk device belongs to fs1, and execute Shell.efi under fs1: to create a complete Shell environment; in a complete shell environment, execute the shell>map-r command to confirm that the HDD device belongs to fs1, and execute bcfgboot add 0grub.efi"A" under fs1: to add the OS boot item to the BIOS, where A stands for If the startup item is missing, after the startup item injection operation is complete, execute Ctrl+alt+Delete to restart the client and unplug the U disk, and enter the BIOS SETUP of the client to confirm that the missing startup item is added successfully, and enter the OS normally.

Further, the startup item injection operation can be completed by the startup item injector according to the collected client state and performing a button simulation trigger operation.

The solution of the present invention can conveniently, efficiently and accurately add the OS startup item to the BIOS permanently, and it will not be lost after restarting. After several verifications on the server, the results show that the method is feasible, which not only reduces the work for research and development It also provides convenience for the later maintenance of the server and the use of customer operation and maintenance.

Description of drawings

FIG. 1 shows a flowchart of a method for permanently adding an OS boot item to a BIOS based on EFI in the present invention.

FIG. 2 shows a block diagram of the system structure for permanently adding an OS boot item to the BIOS based on EFI in the present invention.

Detailed ways

The technical solutions of the present invention are further described below with reference to the accompanying drawings and specific embodiments of the description. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.

This solution uses the EFI Shell environment as the carrier, with the assistance of the Shell.efi file and the corresponding EFI shell commands to add the OS boot items to the BIOS. The specific implementation process is as follows:

FIG. 1 is a flowchart of a method for permanently adding an OS boot item to a BIOS based on EFI according to an embodiment of the present invention.

As shown in FIG. 1, a method for permanently adding an OS boot item to a BIOS based on EFI according to an embodiment of the present invention includes:

SS1: The client collects its own startup item information and saves it;

SS2: The client reports its own startup item information to the management-level server;

SS3: The management-level server compares the client startup item information reported by the client before the motherboard is replaced and after the motherboard is replaced, and generates the missing startup item caused by the replacement of the motherboard on the client;

SS4: Insert the U disk into the USB interface of the client, and the startup item injector automatically adds the missing startup items to the BIOS of the client computer according to the missing startup items generated by the management-level server.

In an embodiment of the present invention, step SS4 is specifically:

SS4-1: Store the Shell.efi file to the root directory of the U disk, and insert the U disk into the USB port of the client computer;

SS4-2: When the client computer is turned on, in the Post stage, the system is triggered to enter the startup item selection, and select UEFI: Built-inEFI Shell;

SS4-3: Enter UEFI: Built-in EFI Shell;

SS4-4: Execute the shell>map-r command under UEFI Shell to confirm that the U disk device belongs to fs1, and execute Shell.efi under fs1: to create a complete shell environment;

SS4-5: In a complete shell environment, execute the shell>map-r command to confirm that the HDD device belongs to fs1, and execute bcfgboot add0grub.efi "A" under fs1: to add the OS boot item to the BIOS, where A stands for Missing startup item.

In an embodiment of the present invention, step SS1 is specifically as follows: when the client starts up, collects its own startup item information and saves it.

In an embodiment of the present invention, step SS2 is specifically: after the client receives the monitoring command from the management-level server, the client sends the startup item information of the current system to the management-level server.

In an embodiment of the present invention, step SS3 is specifically as follows: the management-level server compares the client startup item information reported by the client before the motherboard is replaced and after the motherboard is replaced, and if the two startup item information is consistent, no subsequent operations are performed. , if it is inconsistent, the missing startup item of the client computer caused by the replacement of the motherboard will be generated.

In an embodiment of the present invention, after step SS4, it further includes step SS5:

SS5: Enter the client BIOS SETUP to confirm that the missing startup items are added successfully, and enter the OS normally.

Before step SS5, execute Ctrl+alt+Delete to restart the client and unplug the U disk.

FIG. 2 is a block diagram of a system structure for permanently adding an OS boot item to a BIOS based on EFI according to an embodiment of the present invention.

As shown in FIG. 2, a system for permanently adding an OS boot item to a BIOS based on EFI according to an embodiment of the present invention is used to implement the above-mentioned method for permanently adding an OS boot item to the BIOS based on EFI. The system includes a client computer, management-level server, startup item injector, and U disk, wherein the management-level server, startup item injector, and U disk are respectively connected with the client computer, and the management-level server is connected with the startup item injector.

When the client starts up, it collects its own startup item information and saves it. After the client receives the monitoring command from the management-level server, it sends the startup item information of the current system to the management-level server. After the motherboard is replaced, the client startup item information reported respectively is compared. If the two startup item information is consistent, no follow-up operation is performed.

When judging that the client computer lacks the startup item due to the replacement of the motherboard, the management-level server prompts the administrator to inject the startup item into the client computer.

The startup item injector can obtain the missing startup items of the client from the management-level server, and collect the running status of the client in real time.

Copy the Shell.efi file to the root directory of the U disk, and insert the U disk into the USB port of the client; when the client is powered on, in the Post stage, the boot item injector triggers the system to enter the boot item selection, and select UEFI: Built-in EFI Shell; Enter UEFI: Built-in EFI Shell; execute the shell>map-r command under UEFI Shell to confirm that the U disk device belongs to fs1, and execute Shell.efi under fs1: to create a complete Shell environment; in the complete Shell Under the environment, execute the shell>map-r command to confirm that the HDD device belongs to fs1, and execute bcfg boot add 0grub.efi"A" under fs1: to add the OS boot item to the BIOS, where A represents the missing boot item.

After the startup item injection operation is complete, execute Ctrl+alt+Delete to restart the client computer and unplug the USB flash drive, and enter the BIOS SETUP of the client computer to confirm that the missing startup items are added successfully, and enter the OS normally.

It should be noted that the above operations can be implemented by the startup item injector according to the collected client state and performing a button simulation trigger operation.

Through the above solution, the OS startup items can be added to the BIOS permanently, conveniently, efficiently and accurately, and it will not be lost after restarting. After several verifications on the server, the results show that this method is feasible, which not only reduces the research and development. It also provides convenience for the later maintenance of the server and the use of customer operation and maintenance.

Although some aspects have been described in the context of an apparatus, it is obvious that these aspects also represent a description of the corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method step also represent a description of a corresponding block or item or feature of a corresponding apparatus. Some or all of the method steps may be performed by (or using) hardware devices such as microprocessors, programmable computers, or electronic circuits. One or more of the most important method steps can be performed by such means.

The implementation may be in hardware or in software or may use a digital storage medium such as a floppy disk, DVD, Blu-ray, CD, ROM, PROM, EPROM, EEPROM, or flash memory having electronically readable control signals stored thereon to perform the electronically readable control signals cooperating with (or capable of cooperating with) a programmable computer system to cause the corresponding method to be performed. A data carrier may be provided with electronically readable control signals capable of cooperating with a programmable computer system to cause the methods described herein to be carried out.

The implementation may also take the form of a computer program product having program code operative to perform the method when the computer program product is run on a computer. The program code may be stored on a machine-readable carrier.

What has been described above is illustrative only, and it is to be understood that modifications and variations of the arrangements and details described herein will be apparent to those skilled in the art. It is, therefore, intended that the scope of the appended claims be limited only by the specific details presented by way of description and explanation above.

Claims (10)

1. a method for permanently adding OS boot items into BIOS based on EFI, is characterized in that comprising the following steps: SS1: The client collects its own startup item information and saves it; SS2: The client reports its own startup item information to the management-level server; SS3: The management-level server compares the client startup item information reported by the client before the motherboard is replaced and after the motherboard is replaced, and generates the missing startup item caused by the replacement of the motherboard on the client; SS4: Insert the U disk into the USB interface of the client, and the boot item injector automatically adds the missing boot items to the BIOS of the client according to the missing boot items generated by the management-level server. 2. The method according to claim 1, wherein step SS4 comprises: SS4-1: Store the Shell.efi file to the root directory of the U disk, and insert the U disk into the USB port of the client computer; SS4-2: When the client computer is turned on, in the Post stage, the system is triggered to enter the startup item selection, and select UEFI: Built-in EFIShell; SS4-3: Enter UEFI: Built-in EFI Shell; SS4-4: Execute the shell>map-r command under UEFI Shell to confirm that the U disk device belongs to fs1, and execute Shell.efi under fs1: to create a complete shell environment; SS4-5: In the complete shell environment, execute the shell>map-r command to confirm that the HDD device belongs to fs1, and execute bcfg boot add 0 grub.efi"A" under fs1: to add the OS boot item to the BIOS, where A represents the missing initiator. 3 . The method according to claim 1 , wherein the step SS1 is specifically: collecting and saving the startup item information of the client when it starts up. 4 . 4 . The method according to claim 1 , wherein the step SS2 is specifically: after receiving the monitoring command from the management-level server, the client sends the startup item information of the current system to the management-level server. 5 . 5. method according to claim 1, is characterized in that, step SS3 is specifically: the management level server compares the client startup item information reported respectively before the client replaces the mainboard and after replacing the mainboard, if the startup item information twice If they are consistent, no subsequent operations will be performed. If they are inconsistent, a missing startup item will be generated due to the replacement of the motherboard on the client computer. 6. method according to claim 1, is characterized in that, also comprises step SS5 after step SS4: SS5: Enter the client BIOS SETUP to confirm that the missing startup items are added successfully, and enter the OS normally. 7. The method according to claim 6, wherein before step SS5, Ctrl+alt+Delete needs to be executed to restart the client and unplug the U disk. 8. a system based on EFI that OS startup item is permanently added in BIOS, it is characterized in that, comprise client computer, management level server, startup item injector, U disk, wherein management level server, startup item injector, U disk Connect to the client respectively, the management server is connected to the startup item injector, the client collects its own startup item information and saves it when it starts up. After the client receives the monitoring command from the management level server, the startup item information of the current system is It is sent to the management-level server, and the management-level server compares the client startup item information reported by the client before the motherboard is replaced and after the motherboard is replaced. If the two startup items are consistent, no subsequent operations will be performed. The missing startup items caused by the replacement of the motherboard; save the Shell.efi file to the root directory of the U disk, and insert the U disk into the USB interface of the client computer. The startup item injector automatically injects the missing startup items according to the missing startup items generated by the management server added to the client's BIOS. 9. The system according to claim 8, wherein the startup item injector automatically adds the missing startup item to the BIOS of the client according to the missing startup item generated by the management-level server, specifically: the client is powered on, and in the Post stage , the boot item injector triggers the system to enter the boot item selection, select UEFI: Built-in EFI Shell; enter UEFI: Built-in EFI Shell; execute the shell>map-r command under UEFI Shell to confirm that the U disk device belongs to fs1, and Execute Shell.efi under fs1: to create a complete shell environment; in the complete shell environment, execute the shell>map-r command to confirm that the HDD device belongs to fs1, and execute bcfg boot add 0 grub.efi" under fs1: A"Add the OS startup item to the BIOS, where A represents the missing startup item. After the startup item injection operation is completed, execute Ctrl+alt+Delete to restart the client and unplug the U disk, and enter the client's BIOS SETUP to confirm the missing startup item The addition is successful and the OS is entered normally. 10 . The system according to claim 9 , wherein the startup item injection operation is completed by the startup item injector according to the collected client state and performing a key-press simulation trigger operation. 11 .

Images