A system installation method, device, equipment and storage medium

Abstract

The application discloses an operating system installation method and device, equipment and a storage medium, which are applied to a basic input / output system, and relate to the technical field of ARM servers, and the method comprises the following steps: a pre-boot execution environment is built in the process of powering on the current ARM server, so that the pre-boot execution environment is used to guide the installation of the operating system of the ARM server; the installation process of the operating system of the ARM server guided by the pre-boot execution environment is monitored, and it is judged whether the installation process is abnormal; when the installation process is abnormal, a target network card in the basic input / output system is determined, and the target network card is used to guide the pre-boot execution environment, so that the operating system of the ARM server is installed. Through the technical scheme, the ARM server can maintain an efficient and stable running state when using virtualization operation, and help the development of the domestic ARM CPU platform server service and the domestic cause.

Description

Technical Field

[0001] This invention relates to the field of ARM server technology, and in particular to an operating system installation method, apparatus, device, and storage medium. Background Technology

[0002] As a crucial carrier for network backend operations, servers not only maintain network operation and store data, but also serve as the platform for many network services and devices. Therefore, servers can be considered the fundamental carrier of IT (Internet Technology) information services. Each server is essentially a large-scale PC (Personal Computer) capable of installing operating systems, typically using a PXE (Preboot Execution Environment) network environment.

[0003] For ARM servers such as the FT2000+, due to the limitations of their ARM architecture, it is necessary to install an ARM-based OS (Operating System). However, the ARM-based OS may encounter some unexpected problems in its compatibility with the FT2000+ ecosystem. For example, when using the onboard network card or an external network card to install a domestic system via PXE network, anomalies may occur, making it impossible to install the system and only allowing access to the system's grub interface. Therefore, the firmware BIOS needs to perform some corresponding operations to deal with some unexpected situations.

[0004] In summary, ensuring the ARM server maintains efficient and stable operation and avoiding the GRUB interface when installing the system using a PXE network environment is a problem that needs to be solved. Summary of the Invention

[0005] In view of this, the purpose of this invention is to provide an operating system installation method, apparatus, device, and storage medium that can ensure the ARM server maintains a high-efficiency and stable operating state and avoids entering the GRUB interface when installing a system using a PXE network environment. The specific solution is as follows:

[0006] In a first aspect, this application discloses an operating system installation method, applied to a basic input / output system, comprising:

[0007] During the current power-on operation of the ARM server, a pre-boot execution environment is set up so as to use the pre-boot execution environment to boot and install the operating system of the ARM server;

[0008] The installation process of the operating system of the ARM server being installed in the pre-boot execution environment is monitored, and it is determined whether any abnormalities occur during the installation process.

[0009] If an error occurs during the installation process, the target network card in the basic input / output system is determined, and the pre-boot execution environment is booted using the target network card to install the operating system of the ARM server.

[0010] Optionally, determining whether an abnormality occurred during the installation process includes:

[0011] Determine whether the installation process encounters a first abnormal scenario of network installation environment abnormality;

[0012] Alternatively, determine whether a second abnormal scenario occurs during the installation process, preventing the installation of the operating system on the ARM server from being booted.

[0013] Optionally, the first abnormal scenario for determining whether an abnormal network installation environment occurs during the installation process includes:

[0014] When the operating system of the ARM server is installed using the pre-boot execution environment, if an abnormality is detected in the external network card driver, it is determined that the first abnormal scenario has occurred during the installation process.

[0015] Accordingly, determining whether a second abnormal scenario occurs during the installation process, preventing the installation of the operating system on the ARM server from being booted, includes:

[0016] If the configuration file corresponding to the external network card is larger than a preset threshold, or if the external network card is incompatible with the ARM server, then the installation process is determined to have encountered the second abnormal scenario.

[0017] Optionally, determining the target network card in the basic input / output system when an abnormality occurs during the installation process includes:

[0018] When the first abnormal scenario of network installation environment abnormality occurs during the installation process, the model of the network card pre-configured in the basic input / output system will be matched with the model of the external network card.

[0019] The network card in the basic input / output system that matches the model of the external network card is identified as the target network card in the basic input / output system.

[0020] Optionally, determining the target network card in the basic input / output system when an abnormality occurs during the installation process includes:

[0021] When the installation process encounters a second abnormal scenario where the operating system of the ARM server cannot be booted, the Grub interface is entered, and the operating system of the ARM server is installed using a preset temporary configuration file.

[0022] Optionally, after installing the operating system of the ARM server using a preset temporary configuration file, the process further includes:

[0023] This will replace the configuration file corresponding to the Grub interface with the configuration file corresponding to the target network card.

[0024] Optionally, the operating system installation method further includes:

[0025] If the installation process does not encounter the second abnormal scenario where the operating system of the ARM server cannot be booted, the corresponding pre-boot execution environment is rebuilt during the power-on operation of other ARM servers so as to use the current pre-boot execution environment to boot and install the operating system of the other ARM servers.

[0026] Secondly, this application discloses an operating system installation apparatus, applied to a basic input / output system, comprising:

[0027] The pre-boot execution environment setup module is used to set up a pre-boot execution environment during the current ARM server power-on operation, so as to use the pre-boot execution environment to boot and install the operating system of the ARM server;

[0028] The installation process monitoring module is used to monitor the installation process of the operating system of the ARM server in the pre-boot execution environment and determine whether any abnormalities occur in the installation process.

[0029] The target network card boot installation module is used to determine the target network card in the basic input / output system when an abnormality occurs during the installation process, and to use the target network card to boot the pre-boot execution environment to install the operating system of the ARM server.

[0030] Thirdly, this application discloses an electronic device, which includes a processor and a memory; wherein the memory is used to store a computer program, which is loaded and executed by the processor to implement the operating system installation method as described above.

[0031] Fourthly, this application discloses a computer-readable storage medium for storing a computer program; wherein the computer program, when executed by a processor, implements the operating system installation method as described above.

[0032] In this application, applied to a Basic Input / Output System (BIOS), a pre-boot execution environment is first established during the power-on operation of the current ARM server to boot and install the ARM server's operating system. Then, the installation process of the BIOS booting and installing the ARM server's operating system is monitored, and any abnormalities are identified. When an abnormality occurs, the target network interface card (NIC) in the BIOS is determined, and the BIOS boots the pre-boot execution environment using the target NIC to install the ARM server's operating system. This approach addresses the issue that, due to the limitations of the ARM architecture, the BIOS needs to adapt to the ARM server's operating system during installation to handle unforeseen circumstances. By monitoring the pre-boot execution environment's installation process and addressing installation abnormalities, the BIOS utilizes its own target NIC driver to guide the pre-boot execution environment into operating system installation mode. This solves the problem of PXE installation failing due to abnormal NIC driver loading, resulting in only access to the GRUB interface, and also prevents future system access problems. In addition, the Basic Input / Output System (BIOS) installs drivers for network cards that can be used on the ARM server platform on the operating system, ensuring that the server can run normally after the system is installed. Through the efficient control mechanism of the BIOS, the ARM server maintains a high-efficiency and stable operating state when using virtualization operations, thus contributing to the development of domestic ARM CPU platform server services and domestic industries. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0034] Figure 1 This is a flowchart of an operating system installation method disclosed in this application;

[0035] Figure 2 This is a schematic diagram of an operating system installation method disclosed in this application;

[0036] Figure 3 This is a flowchart of a specific operating system installation method disclosed in this application;

[0037] Figure 4 This is a schematic diagram of the structure of an operating system installation device disclosed in this application;

[0038] Figure 5 This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0039] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0040] For ARM servers such as the FT2000+, due to the limitations of their ARM architecture, it is necessary to install an ARM-based OS. However, the ARM-based OS may encounter some unexpected problems in its compatibility with the FT2000+ ecosystem. For example, when using the onboard network card or an external network card to install a domestic system via PXE network, anomalies may occur, making it impossible to install the system and only allowing access to the system's grub interface. Therefore, the firmware BIOS needs to perform some corresponding operations to deal with some unexpected situations.

[0041] To address this, this application provides an operating system installation solution that ensures the ARM server maintains a high-efficiency and stable operating state and avoids entering the GRUB interface when installing the system using a PXE network environment.

[0042] This invention discloses an operating system installation method, see [link to relevant documentation]. Figure 1 As shown, applied to a basic input / output system, the method includes:

[0043] Step S11: During the current power-on operation of the ARM server, a pre-boot execution environment is built so as to use the pre-boot execution environment to boot and install the operating system of the ARM server.

[0044] In this embodiment, for ARM servers such as the FT2000+, due to the limitations of their ARM architecture, an ARM-based OS system needs to be installed, and the system installation utilizes a PXE network environment. Therefore, taking the FT2000+ server as an example, when the FT2000+ server powers on normally, a pre-boot execution environment (PXE environment) is set up to automatically package the system, and the terminal operating system in the ARM server is booted through the pre-boot execution environment (PXE environment).

[0045] Step S12: Monitor the installation process of the operating system of the ARM server in the pre-boot execution environment and determine whether any abnormalities occur during the installation process.

[0046] In this embodiment, the firmware BIOS (Basic Input Output System) monitors the process of booting and installing the operating system in the pre-boot execution environment (PXE environment) to determine whether any abnormalities occur during the PXE boot installation process.

[0047] In one specific implementation, an anomaly during the PXE boot installation process manifests as an abnormal network installation environment, which is considered the first anomaly scenario. Understandably, if the external network card driver is faulty, this is then considered an anomaly in the PXE network installation environment. The firmware BIOS will detect this as getting stuck at the first step; that is, during PXE booting, the first step fails to boot into the external network card's boot environment.

[0048] In another specific implementation, when the PXE network environment is normal, the pre-boot execution environment begins to boot and install the operating system. During this process, an anomaly occurs where the system cannot be booted normally, meaning the ARM server's operating system cannot be installed. In this case, the scenario of a network installation environment anomaly is considered the second anomaly scenario. It should be noted that if the size of the configuration file corresponding to the external network card under the operating system exceeds a preset threshold—that is, the network card driver EFI (Extensible Firmware Interface) file is too large or incompatible with the ARM platform of the ARM server—this is considered an anomaly in the installation process that prevents the installation of the ARM server's operating system.

[0049] Step S13: When an abnormality occurs during the installation process, the target network card in the basic input / output system is determined, and the pre-boot execution environment is booted using the target network card to install the operating system of the ARM server.

[0050] In one specific implementation, when the installation process encounters the first abnormal scenario of a network installation environment anomaly, i.e., a network card driver loading anomaly occurs, the firmware BIOS provides the network card driver to support the normal operation of the network card on network platforms such as the FT2000+ ARM server. Specifically, the model of the network card pre-configured in the basic input / output system is matched with the model of the external network card; the network card in the basic input / output system that matches the model of the external network card is determined as the target network card in the basic input / output system. The pre-boot execution environment is then booted using the target network card to install the operating system of the ARM server.

[0051] It should be noted that the firmware BIOS itself supports various network card models. The system matches the network card model to the network card model of the Basic Input / Output System (BIOS) to find a usable network card driver. This matching can be done using the network card's vendor ID and / or the device's own ID; no specific limitations are specified here. Furthermore, the BIOS utilizes its own BIOS driver, i.e., it uses the target network card to guide the PXE environment into system installation mode. This eliminates the need for network cards from foreign manufacturers and avoids incompatibility issues with ARM platforms like the FT2000+, preventing the provision of an ARM driver environment. This contributes to the development of domestic ARM CPU platform server services and the domestic industry.

[0052] In another specific implementation, when the installation process encounters a second abnormal scenario where the operating system of the ARM server cannot be booted, due to an abnormal network card driver loading, the current network card driver EFI file is too large or incompatible with the platform, causing PXE installation to fail and only the Grub interface can be entered. At this time, because the EFI configuration file provided by the operating system has an abnormal BIOS, a preset temporary configuration file is used to forcibly replace the configuration file provided by the operating system, and the booting and installation of the operating system of the ARM server continues.

[0053] Furthermore, due to a problem with the operating system's installation boot files, to ensure a successful system boot next time, after installing the ARM server's operating system using a preset temporary configuration file, the firmware BIOS needs to replace the problematic network card's configuration file. This can be done by replacing it with the configuration file corresponding to the target network card, or by updating the problematic network card's configuration file, thus ensuring system and platform configuration compatibility. In this way, the basic input / output system utilizes its own network card driver to assist in the boot process, installing a driver for the network card compatible with this platform into the operating system. This allows for normal system installation and avoids future issues caused by accessing the GRUB interface, preventing system installation failures and other problems upon subsequent system boots.

[0054] In this application, applied to a Basic Input / Output System (BIOS), a pre-boot execution environment is first established during the power-on operation of the current ARM server to boot and install the ARM server's operating system. Then, the installation process of the BIOS booting and installing the ARM server's operating system is monitored, and any abnormalities are identified. When an abnormality occurs, the target network interface card (NIC) in the BIOS is determined, and the BIOS boots the pre-boot execution environment using the target NIC to install the ARM server's operating system. This approach addresses the issue that, due to the limitations of the ARM architecture, the BIOS needs to adapt to the ARM server's operating system during installation to handle unforeseen circumstances. By monitoring the pre-boot execution environment's installation process and addressing installation abnormalities, the BIOS utilizes its own target NIC driver to guide the pre-boot execution environment into operating system installation mode. This solves the problem of PXE installation failing due to abnormal NIC driver loading, resulting in only access to the GRUB interface, and also prevents future system access problems. In addition, the Basic Input / Output System (BIOS) installs drivers for network cards that can be used on the ARM server platform on the operating system, ensuring that the server can run normally after the system is installed. Through the efficient control mechanism of the BIOS, the ARM server maintains a high-efficiency and stable operating state when using virtualization operations, thus contributing to the development of domestic ARM CPU platform server services and domestic industries.

[0055] For example, such as Figure 2The diagram illustrates a specific application of this embodiment of the method. First, the FT2000+ server powers on and runs normally. The server host performs virtualization operations, such as creating virtual machines and cloud desktops. Then, a PXE environment is built on the ARM server to automatically install the system. During this process, the firmware BIOS monitors the PXE boot installation process, checking for abnormalities in the PXE network installation environment or failures to boot, and determining if any installation process anomalies occur. If boot failure is caused by an abnormal PXE network installation environment, the firmware BIOS matches its own network card driver with the network card model to find a usable driver. The firmware BIOS then uses its own BIOS network card driver to guide the PXE environment into system installation mode. After booting into the PXE network environment, if the boot process fails to boot into the installation system, it checks if there is an abnormality in entering the GRUB interface. If an anomaly occurs, the firmware BIOS uses a suitable network card EFI configuration file to boot the system. Additionally, if the OS-provided EFI configuration file is abnormal, a temporary configuration file is used to forcibly replace the OS-provided configuration file, continuing the system installation. When installing an operating system in a large-scale network PXE environment, if no error occurs during the boot process that prevents the installation of the operating system on the ARM server, the corresponding pre-boot execution environment is rebuilt during the power-on operation of other ARM servers so that the operating system on the other ARM servers can be booted and installed using the current pre-boot execution environment.

[0056] This application discloses a specific operating system installation method. See [link to relevant documentation]. Figure 3 As shown, applied to a basic input / output system, the method includes:

[0057] Step S21: During the current power-on operation of the ARM server, a pre-boot execution environment is built so as to use the pre-boot execution environment to boot and install the operating system of the ARM server.

[0058] In this embodiment of the application, a pre-boot execution environment can be built during the power-on operation of the current ARM server, such as the FT2000+ server, and the operating system of the ARM server can be installed using the pre-boot execution environment.

[0059] Step S22: Determine whether the installation process encounters a first abnormal scenario of network installation environment abnormality; or, determine whether the installation process encounters a second abnormal scenario of inability to boot the operating system of the ARM server.

[0060] In this embodiment of the application, when using the pre-boot execution environment to boot and install the operating system of the ARM server, the server firmware BIOS needs to monitor the PXE installation process. This is mainly to solve the problem that when installing the system using the PXE network environment, the PXE installation cannot proceed normally due to abnormal loading of the network card driver, and can only enter the grub interface, which causes trouble for the large-scale use of the network PXE environment to install the system.

[0061] In this embodiment, determining whether the installation process encounters a first abnormal scenario of network installation environment abnormality, or determining whether the installation process encounters a second abnormal scenario of inability to boot the operating system of the ARM server, can resolve issues such as abnormal network card driver loading under the OS, problems with network card driver loading under the system after entering the boot installation of the operating system, or mismatch between the size of the driver provided under the OS and the hardware design of the server CPU platform. If an abnormal network card driver loading occurs, the firmware BIOS provides a network card driver to support the normal operation of the network card on the FT2000+ network platform; if the network card driver EFI file under the OS is too large or incompatible with the platform, the BIOS needs to identify it when installing the OS network card driver, and use its own driver to help boot into a system that can be installed normally, avoiding the system failing to install due to entering the GRUB interface, and also avoiding problems when entering the system later. The firmware BIOS needs to install a driver for the network card that can be used by this platform on the OS to ensure that the server can run normally after the system is installed.

[0062] Step S23: When the first abnormal scenario of network installation environment abnormality occurs during the installation process, the model of the network card pre-configured in the basic input / output system is matched with the model of the external network card; the network card in the basic input / output system that matches the model of the external network card is determined as the target network card in the basic input / output system.

[0063] In this embodiment, the system monitors for problems such as abnormal PXE network installation environment or inability to boot and install. If the external network card driver is abnormal, the firmware BIOS will detect that it will get stuck in the first step, that is, it will be unable to boot into the external network card's boot environment in the first step. At this time, the firmware BIOS needs to match its own network card driver with the network card model to find a usable network card driver. The firmware BIOS then uses its own BIOS driver to induce the PXE environment to enter the system installation mode.

[0064] Step S24: When the installation process encounters a second abnormal scenario where the operating system of the ARM server cannot be booted, enter the Grub interface and use a preset temporary configuration file to install the operating system of the ARM server.

[0065] In this embodiment, the PXE installation environment is normal and can boot normally. However, after booting into the PXE network environment, it fails to boot into the installation system and eventually enters the GRUB interface, failing to boot the packaged system normally. The main problem is that the size of the EFI file used to boot the OS system is incompatible with the FT2000+ARM platform. Other platforms will also experience the same problem, leading to the inability to install the system normally. At this time, the BIOS will monitor for abnormal booting into GRUB. If an abnormality occurs, the firmware BIOS needs to use a matching network card EFI configuration file to boot the system. Since the OS-provided EFI configuration file is abnormal, the BIOS should use a preset temporary configuration file to forcibly replace the OS-provided configuration file and continue booting the system. In addition, because the OS-provided installation boot file is faulty, the firmware BIOS needs to replace the faulty network card configuration file to ensure system and platform configuration compatibility on the next boot.

[0066] The above-described solution in this embodiment is applied to a basic input / output system (PIS) to build a pre-boot execution environment during the power-on and operation of the current ARM server, so as to use the pre-boot execution environment to boot and install the operating system of the ARM server. The system determines whether the installation process encounters a first abnormal scenario of network installation environment anomaly; or, determines whether the installation process encounters a second abnormal scenario of being unable to boot and install the operating system of the ARM server. When the installation process encounters the first abnormal scenario of network installation environment anomaly, the model of the network card pre-configured in the PIS is matched with the model of the external network card; the network card in the PIS that matches the model of the external network card is determined as the target network card in the PIS. When the installation process encounters the second abnormal scenario of being unable to boot and install the operating system of the ARM server, the system enters the Grub interface and uses a preset temporary configuration file to install the operating system of the ARM server. Therefore, this application is applied to Basic Input / Output Systems (PIS). Because of the limitations of the ARM architecture during the installation of operating systems on ARM server series, the PIS requires corresponding ecological coordination operations to handle unforeseen circumstances. Thus, by monitoring the pre-boot execution environment's (PXE) process for operating system installation through the PIS, and in the event of installation anomalies, the PIS utilizes its own target network card driver to guide the PXE environment into operating system installation mode. This solves the problem of PXE installation failing due to abnormal network card driver loading, resulting in only access to the GRUB interface, and also prevents future system boot problems. Furthermore, the PIS installs network card drivers compatible with the ARM server platform, ensuring the server can operate normally after system installation. Through the PIS's efficient control mechanism, the ARM server maintains a high-efficiency and stable operating state during virtualization operations, contributing to the development of domestically produced ARM CPU platform server services and the domestic industry.

[0067] Accordingly, embodiments of this application also disclose an operating system installation device applied to a basic input / output system, see [link to relevant documentation]. Figure 4 As shown, the device includes:

[0068] The pre-boot execution environment setup module 11 is used to set up a pre-boot execution environment during the current ARM server power-on operation, so as to use the pre-boot execution environment to boot and install the operating system of the ARM server;

[0069] The installation process monitoring module 12 is used to monitor the installation process of the operating system of the ARM server in the pre-boot execution environment and determine whether the installation process is abnormal.

[0070] The target network card boot installation module 13 is used to determine the target network card in the basic input / output system when an abnormality occurs during the installation process, and to use the target network card to boot the pre-boot execution environment to install the operating system of the ARM server.

[0071] Therefore, the above-described solution in this embodiment, applied to a Basic Input / Output System (BIOS), firstly establishes a pre-boot execution environment during the power-on operation of the current ARM server to guide the installation of the ARM server's operating system. Then, it monitors the installation process of the ARM server's operating system under the guidance of the pre-boot execution environment and determines whether any abnormalities occur. When an abnormality occurs, the target network interface card (NIC) in the BIOS is identified, and the NIC is used to guide the pre-boot execution environment to install the ARM server's operating system. In this way, because the ARM architecture limits the installation process of ARM server operating systems, the BIOS needs to perform corresponding ecosystem-based operations to cope with unforeseen circumstances. By monitoring the pre-boot execution environment's operating system installation process through the BIOS, and addressing installation abnormalities, the BIOS uses its own target NIC driver to guide the pre-boot execution environment into operating system installation mode. This solves the problem of PXE network environment installation failing due to abnormal NIC driver loading, resulting in only access to the GRUB interface, and also avoids future system access problems. In addition, the Basic Input / Output System (BIOS) installs drivers for network cards that can be used on the ARM server platform on the operating system, ensuring that the server can run normally after the system is installed. Through the efficient control mechanism of the BIOS, the ARM server maintains a high-efficiency and stable operating state when using virtualization operations, thus contributing to the development of domestic ARM CPU platform server services and domestic industries.

[0072] In some specific embodiments, the boot installation process monitoring module 12 includes:

[0073] The first abnormal scenario judgment module is used to determine whether the installation process encounters a first abnormal scenario of abnormal network installation environment.

[0074] The second abnormal scenario judgment module is used to determine whether the installation process encounters a second abnormal scenario that prevents the installation of the operating system of the ARM server from being booted.

[0075] In some specific implementations, the first abnormal scenario judgment module includes:

[0076] The first abnormal scenario determination unit is used to determine that the first abnormal scenario has occurred during the installation process if an abnormality is detected in the external network card driver when the operating system of the ARM server is installed using the pre-boot execution environment.

[0077] Accordingly, the second abnormal scenario judgment module includes:

[0078] The second abnormal scenario determination unit is used to determine that the installation process has encountered the second abnormal scenario if the configuration file corresponding to the external network card is greater than a preset threshold, or if the external network card is incompatible with the ARM server.

[0079] In some specific implementations, the target network card boot installation module 13 includes:

[0080] The network card matching module is used to match the model of the network card pre-configured in the basic input / output system with the model of the external network card when the first abnormal scenario of network installation environment abnormality occurs during the installation process.

[0081] The target network card determination module is used to determine the network card in the basic input / output system that matches the model of the external network card as the target network card in the basic input / output system.

[0082] In some specific implementations, the target network card boot installation module 13 includes:

[0083] The forced boot installation module is used to enter the Grub interface and install the operating system of the ARM server using a preset temporary configuration file when a second abnormal scenario occurs during the installation process and the installation process fails to boot the operating system of the ARM server.

[0084] In some specific implementations, the target network card boot installation module 13 is further configured to: after installing the operating system of the ARM server using a preset temporary configuration file, replace the configuration file corresponding to the Grub interface with the configuration file corresponding to the target network card.

[0085] In some specific implementations, the operating system installation device is further configured to, if the second abnormal scenario of being unable to boot and install the operating system of the ARM server does not occur during the installation process, rebuild the corresponding pre-boot execution environment during the power-on operation of other ARM servers, so as to use the current pre-boot execution environment to boot and install the operating system of the other ARM servers.

[0086] Furthermore, embodiments of this application also disclose an electronic device, Figure 5 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.

[0087] Figure 5 This is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the operating system installation method disclosed in any of the foregoing embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be an ARM server.

[0088] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0089] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, etc. The resources stored on it can include an operating system 221, computer programs 222, and data 223, etc. The data 223 can include various types of data. The storage method can be temporary storage or permanent storage.

[0090] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the operating system installation method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0091] Furthermore, this application also discloses a computer-readable storage medium, which includes random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, magnetic disks, optical disks, or any other form of storage medium known in the art. The computer program, when executed by a processor, implements the aforementioned operating system installation method. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0092] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0093] The steps of operating system installation or algorithm described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0094] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0095] The above provides a detailed description of an operating system installation method, apparatus, device, and storage medium provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. An operating system installation method, characterized in that, Applied to basic input / output systems, including: During the current power-on operation of the ARM server, a pre-boot execution environment is set up so as to use the pre-boot execution environment to boot and install the operating system of the ARM server; The installation process of the operating system of the ARM server being installed in the pre-boot execution environment is monitored, and it is determined whether any abnormalities occur during the installation process. When an abnormality occurs during the installation process, the target network interface card (NIC) in the Basic Input / Output System (BIOS) is determined, and the pre-boot execution environment is booted using the target NIC to install the operating system of the ARM server. Specifically, when a first abnormal scenario occurs during the installation process, involving a network installation environment, the model of the NIC pre-configured in the BIOS is matched with the model of the external NIC. The NIC in the BIOS that matches the model of the external NIC is identified as the target NIC in the BIOS. When a second abnormal scenario occurs during the installation process, indicating an inability to boot and install the operating system of the ARM server, the Grub interface is entered, and the operating system of the ARM server is installed using a preset temporary configuration file. The first abnormal scenario includes an inability to boot into the external NIC's boot environment during the first step of PXE booting. The second abnormal scenario includes an external NIC configuration file size exceeding a preset threshold or incompatibility with the ARM platform of the ARM server.

2. The operating system installation method according to claim 1, characterized in that, The determination of whether the installation process is abnormal includes: Determine whether the installation process encounters a first abnormal scenario of network installation environment abnormality; Alternatively, determine whether a second abnormal scenario occurs during the installation process, preventing the installation of the operating system on the ARM server from being booted.

3. The operating system installation method according to claim 2, characterized in that, The first abnormal scenario for determining whether a network installation environment abnormality occurs during the installation process includes: When the operating system of the ARM server is installed using the pre-boot execution environment, if an abnormality is detected in the external network card driver, it is determined that the first abnormal scenario has occurred during the installation process. Accordingly, determining whether a second abnormal scenario occurs during the installation process, preventing the installation of the operating system on the ARM server from being booted, includes: If the configuration file corresponding to the external network card is larger than a preset threshold, or if the external network card is incompatible with the ARM server, then the installation process is determined to have encountered the second abnormal scenario.

4. The operating system installation method according to claim 1, characterized in that, After installing the operating system of the ARM server using a preset temporary configuration file, the process further includes: This will replace the configuration file corresponding to the Grub interface with the configuration file corresponding to the target network card.

5. The operating system installation method according to any one of claims 2 to 4, characterized in that, Also includes: If the installation process does not encounter the second abnormal scenario where the operating system of the ARM server cannot be booted, the corresponding pre-boot execution environment is rebuilt during the power-on operation of other ARM servers so as to use the current pre-boot execution environment to boot and install the operating system of the other ARM servers.

6. An operating system installation device, characterized in that, Applied to basic input / output systems, including: The pre-boot execution environment setup module is used to set up a pre-boot execution environment during the current ARM server power-on operation, so as to use the pre-boot execution environment to boot and install the operating system of the ARM server; The installation process monitoring module is used to monitor the installation process of the operating system of the ARM server in the pre-boot execution environment and determine whether any abnormalities occur in the installation process. The target network card boot installation module is used to determine the target network card in the basic input / output system (BIOS) when an abnormality occurs during the installation process, and to use the target network card to boot the pre-boot execution environment to install the operating system of the ARM server. Specifically, when a first abnormal scenario occurs during the installation process, the model of the network card pre-configured in the BIOS is matched with the model of the external network card; the network card in the BIOS that matches the model of the external network card is determined as the target network card in the BIOS. When a second abnormal scenario occurs during the installation process, where the installation of the ARM server's operating system cannot be booted, the module enters the Grub interface and uses a preset temporary configuration file to install the ARM server's operating system. The first abnormal scenario includes the inability to boot into the external network card's boot environment during the first step of PXE booting; the second abnormal scenario includes the configuration file size corresponding to the external network card under the operating system exceeding a preset threshold, or incompatibility with the ARM platform of the ARM server.

7. An electronic device, characterized in that, The electronic device includes a processor and a memory; wherein the memory is used to store a computer program, which is loaded and executed by the processor to implement the operating system installation method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, Used to store computer programs; wherein the computer programs, when executed by a processor, implement the operating system installation method as described in any one of claims 1 to 5.

Images