CN119690529A

CN119690529A - Method and device for controlling starting of server, storage medium and electronic equipment

Info

Publication number: CN119690529A
Application number: CN202411755724.7A
Authority: CN
Inventors: 孙永博; 李道童; 张炳会; 王东清; 周春芬
Original assignee: Suzhou Metabrain Intelligent Technology Co Ltd
Current assignee: Suzhou Metabrain Intelligent Technology Co Ltd
Priority date: 2024-11-30
Filing date: 2024-11-30
Publication date: 2025-03-25

Abstract

The embodiment of the application provides a method and a device for controlling starting of a server, a storage medium and electronic equipment, wherein the method comprises the steps of receiving a target starting request, responding to the target starting request, detecting target starting information corresponding to target storage equipment according to target equipment attributes of the target storage equipment and initial starting information corresponding to a target connector, and starting an operating system on a processor through the target storage equipment under the condition that the target starting information is used for indicating that the operating system is allowed to be started through the target storage equipment. The application solves the problem of lower success rate of server startup, thereby achieving the effect of improving the success rate of server startup.

Description

Method and device for controlling starting of server, storage medium and electronic equipment

Technical Field

The embodiment of the application relates to the field of computers, in particular to a method and a device for controlling starting of a server, a storage medium and electronic equipment.

Background

In the related art, in the case of starting the operating system of the server, the conventional BIOS cannot directly determine the corresponding storage device from the name of the start-up item, which results in low accuracy of the selection of the start-up item of the operating system, and may cause that the operating system of the server may not be started successfully.

For example, when two or more sets of storage devices are deployed on a server, one set of storage devices is used to support an operating system, and the remaining storage devices are used for data storage, if the operating system is erroneously mounted to the storage device for data storage, or the operating system is stored in the storage device for data storage. This may cause an operating system to be started erroneously, for example, when the operating system is installed, the operating system is installed on the hard disk set for storing data, and when the operating system is started, the operating system is started from the operating system on the hard disk set for storing data, and the operating system may be different from the operating system environment originally planned to be deployed by the user, for example, the operating system type, version, drive configuration, etc., so that the operating system may be affected in terms of service operation, or even cannot be operated at all.

In addition, if data is stored, the data is stored in a disk or a disk group on which an operating system is installed, so that the stored data conflicts with the operating system data, or the operating system data is deleted when the data is deleted, the problem that the operating system cannot be started is caused, and the upper layer service cannot be normally developed.

It can be appreciated that in the related art, there may be a problem that the boot item name generated by the BIOS cannot accurately reflect the information of the storage device, which results in low accuracy of boot item selection of the operating system, and further results in a server boot failure.

Disclosure of Invention

The embodiment of the application provides a method and a device for controlling the starting of a server, a storage medium and electronic equipment, which are used for at least solving the problem of low success rate of starting the server in the related technology.

According to one embodiment of the application, a method for controlling the startup of a server is provided, the server comprises a processor and startup firmware, the startup firmware is connected with the processor, the processor is used for being connected with a connector, the connector is used for being connected with a storage device, the startup firmware is also used for being connected with the storage device, the method is applied to the startup firmware, the method comprises the steps of receiving a target startup request, wherein the target startup request is used for requesting the startup of an operating system of the processor through a connected target storage device, the processor is connected with the target storage device through a target connector, responding to the target startup request, detecting target startup information corresponding to the target storage device according to target device attributes of the target storage device and initial startup information corresponding to the target connector, wherein the initial startup information is used for indicating whether the operation system is allowed to be started through a candidate storage device connected with the target connector, the initial startup information is configured on a target operation interface provided by the startup firmware, and the target startup information is used for allowing the operation of the target storage device through the target storage device to be started through the target operation interface.

In an exemplary embodiment, the detecting the target startup information corresponding to the target storage device according to the target device attribute of the target storage device and the initial startup information corresponding to the target connector includes screening the target connector from candidate connectors according to the target device type of the target storage device and the target identifier of the target storage device, wherein the target device attribute includes the target device type and the target identifier, and determining the target startup information according to the initial startup information.

In one exemplary embodiment, the screening the target connectors from candidate connectors according to the target device type of the target storage device and the target identifier of the target storage device includes detecting a target identifier range in which the target bus identifier falls when the target device type includes a first device type, the target identifier includes a target bus identifier of the target storage device, and acquiring the target connector corresponding to the target identifier range from an identifier range and a connector having a correspondence relationship, wherein when the target device type includes the first device type, the target connector includes a target port on the server, and when the target device type includes a second device type, and the target identifier includes a target bus identifier of the target storage device, a target device identifier of the target storage device, and a target function identifier of the target storage device, the target connector corresponding to the target bus identifier, the target device identifier, and the target function identifier are acquired from a connector having a correspondence relationship, a bus identifier, a device identifier, and a function identifier, and wherein when the target device type includes the second device type, the target device type includes the target bus identifier, and the target function identifier of the target storage device.

In one exemplary embodiment, the determining the target boot information according to the initial boot information includes determining the target boot information to indicate that the operating system is not allowed to boot through the target storage device if the initial boot information indicates that the candidate storage device connected through the target connector is not allowed to boot the operating system, and determining the target boot information to indicate that the operating system is allowed to boot through the target storage device if the initial boot information indicates that the candidate storage device connected through the target connector is allowed to boot the operating system.

In an exemplary embodiment, the target operation interface includes a reference connector and a start setting item, where the start setting item is used to set whether to allow the storage device connected by the reference connector to start the operating system, the reference connector includes the target connector, and before the target start information corresponding to the target storage device is detected according to the target device attribute of the target storage device and the initial start information corresponding to the target connector, the method further includes receiving a target configuration request triggered on the target operation interface, where the target configuration request is used to request that the start information of the target connector be configured as the initial start information, and in response to the target configuration request, the start information of the target connector is configured from the reference start information to the initial start information.

In an exemplary embodiment the initiation settings comprise a first setting for adapting initiation information of the reference connector to indicate that the operating system is not allowed to be initiated by a storage device to which the reference connector is connected and a second setting for adapting initiation information of the reference connector to indicate that the operating system is allowed to be initiated by a storage device to which the reference connector is connected, the receiving a target configuration request triggered on the target operation interface comprises detecting a first trigger operation performed by the first setting and detecting a second trigger operation performed by the second setting, determining that the target configuration request is received in case that the first trigger operation is detected by the first setting and the second trigger operation is detected not to be performed by the second setting, wherein the target configuration request is for requesting that the initiation information of the target connector is allowed to be initiated by the initial initiation information, the initial configuration information being used for indicating that the target connector is not allowed to be initiated by the storage device to be connected, the candidate configuration request being performed by the first setting and the target configuration request being performed by the first setting, and the target configuration request being received in case that the initial configuration information is not allowed to be initiated by the target connection is detected by the first setting, and the target configuration request being performed by the candidate device being determined to be triggered by the initial setting.

In one exemplary embodiment, the target operation interface includes the reference connector and a function setting item having a corresponding relation, the function setting item is used for setting a connection parameter of the reference connector, the start setting item includes a third setting item, the third setting item is used for adjusting start information of the reference connector to be used for indicating that the operation system is not allowed to be started by a storage device connected with the reference connector in the function setting item, the receiving a target configuration request triggered on the target operation interface includes detecting a third trigger operation performed by the third setting item, and determining that the target configuration request is received when the third setting item is executed by the third trigger operation, wherein the target configuration request is used for requesting that start information of the target connector be configured as the initial start information, and the initial start information is used for indicating that candidate storage devices connected with the target connector are not allowed to be started by the operation system.

According to another embodiment of the application, a starting control device of a server is provided, the server comprises a processor and starting firmware, the starting firmware is connected with the processor, the processor is used for being connected with a connector, the connector is used for being connected with a storage device, the starting firmware is further used for being connected with the storage device, the device is applied to the starting firmware, the device comprises a first receiving module and is used for receiving a target starting request, the target starting request is used for requesting to start an operating system of the processor through a connected target storage device, the processor is connected with the target storage device through a target connector, a detecting module is used for responding to the target starting request, and detecting target starting information corresponding to the target storage device according to target device attributes of the target storage device and initial starting information corresponding to the target connector, wherein the initial starting information is used for indicating whether to start the operating system through a candidate storage device connected with the target connector, the initial starting information is provided on a target starting operation interface, the processor is used for allowing the operating system to start through the target storage device, and the initial starting information is used for indicating that the operating system is started through the target storage device.

According to a further embodiment of the application, there is also provided a computer readable storage medium having stored therein a computer program, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

According to a further embodiment of the application there is also provided an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

According to a further embodiment of the application, there is also provided a computer program product comprising a computer program which, when executed by a processor, implements the steps of any of the method embodiments described above.

According to the application, a user can configure the starting information corresponding to the connector on the target operation interface, so that whether the operating system is allowed to be started from the storage device connected with the connector is configured according to the user requirements, the starting firmware detects the starting information corresponding to the storage device according to the device attribute of the storage device and the starting information corresponding to the connector, the operating system can be started on the processor through the storage device only under the condition that the starting information indicates that the operating system is allowed to be started through the storage device connected with the connector, and the problem that the operating system is started in the wrong storage device is avoided.

Drawings

Fig. 1 is a hardware block diagram of a server apparatus of a startup control method of a server according to an embodiment of the present application;

FIG. 2 is a flow chart of a method of startup control of a server according to an embodiment of the present application;

FIG. 3 is a link structure schematic diagram of an NVME disk in accordance with an embodiment of the present application;

FIG. 4 is a schematic diagram of a link structure of a Sata disc according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a link structure of a USB memory device according to an embodiment of the present application;

FIG. 6 is a functional diagram supported in EFI_PCI_IO_PROTOCOL according to an embodiment of the present application;

FIG. 7 is a diagram of GetLocation function functions supported in EFI_PCI_IO_PROTOCOL according to an embodiment of the present application;

FIG. 8 is a schematic diagram of an alternative target operating interface in which a CPU is connected to a storage device via a port according to an embodiment of the present application;

FIG. 9 is a schematic diagram of an alternative target operating interface in which a CPU is coupled to a storage device via a controller, according to an embodiment of the present application;

FIG. 10 is a schematic diagram of an alternative startup creation rights process according to an embodiment of the application;

fig. 11 is a block diagram of a configuration of a startup control device of a server according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in detail below with reference to the accompanying drawings in conjunction with the embodiments.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.

First, terms related to the embodiments of the present application are explained as follows:

BIOS (basic Input/Output System), basic Input/Output System, BIOS (basic Input/Output System) is the most basic software code on a computer hardware System. The BIOS program is embedded in SPI chip of computer main board, and its main functions are power-on self-check, CPU and memory initialization, detection of input/output equipment and bootable equipment and finally guiding starting of operation system.

The method comprises the steps that computer products such as a server, a platform machine, a notebook computer, an industrial personal computer and the like are finally started into an operating system to work and operate the computer, two functions are necessarily needed, one is to install the operating system, the other is to start the operating system, the operating system is installed in various modes, after the operating system is installed through an optical driver, through PXE and the like, each piece of bootable equipment including the optical driver, the network card PXE, the operating system (possibly a plurality of operating systems) installed in various hard disks and the like is processed into a plurality of bootable items by the BIOS, a user can select which starting item to start according to needs, for example, the optical driver is to install the operating system from the optical driver, the PXE is to install the operating system from the PXE, and the installed operating system is to start into the operating system;

Specifically, to PXE, each Port (Port) of each network card on the machine can support PXE functions through the support of card drivers, and the BIOS generates a PXE start item, and can individually control the switch of each Port PXE function.

Furthermore, the BIOS can collect all the bootable items, including CD driver, PXE, operating system installed in various hard disks, etc., display in BIOS Setup interface for user to regulate the starting sequence (priority) of each starting item and set starting item switch, and simultaneously, the BIOS can realize shortcut key function of configuring all the starting items in starting process, give prompt in starting process, press which function key can start starting item setting function, after pressing the function key, such as F11, a window is popped up to display all the bootable items, and the user can select which starting item to start.

In addition, the BIOS can also generate a window which is entirely composed of PXE starting items and is used for customer selection, and the BIOS can also be similar to the F11 function.

PCH Platform Controller Hub, platform controller center.

UEFI-Unified Extensible FIRMWARE INTERFACE, unified extensible firmware interface, is a personal computer system specification that defines the software interface between the operating system and the system firmware.

And (3) a PXE (virtual machine) preboot execute environment, a pre-boot execution environment, a network mode of working in a Client/Server, supporting a workstation to download images from a remote Server through a network, and thus supporting starting an operating system through the network, wherein in the starting process, a terminal requires a DHCP (Dynamic Host Configuration Protocol ) Server to allocate IP (Internet Protocol, internet protocol) addresses, and then a starting software package is downloaded into a local memory for execution by using a TFTP (TRIVIAL FILE TRANSFER protocol, simple file transfer protocol) or MTFTP (Multicast TRIVIAL FILE TRANSFER protocol) protocol, and the starting software package completes basic software setting of the terminal (Client), so that a terminal operating system pre-installed in the Server is guided, and the PXE can guide various operating systems.

The method embodiments provided in the embodiments of the present application may be executed in a server apparatus or similar computing device. Taking the operation on the server device as an example, fig. 1 is a block diagram of a hardware structure of the server device of a method for controlling the startup of a server according to an embodiment of the present application. As shown in fig. 1, the server device may include one or more (only one is shown in fig. 1) processors 102 (the processor 102 may include, but is not limited to, a microprocessor MCU, a programmable logic device FPGA, or the like processing means) and a memory 104 for storing data, wherein the server device may further include a transmission device 106 for communication functions and an input-output device 108. It will be appreciated by those of ordinary skill in the art that the architecture shown in fig. 1 is merely illustrative and is not intended to limit the architecture of the server apparatus described above. For example, the server device may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.

The memory 104 may be used to store a computer program, for example, a software program of application software and a module, such as a computer program corresponding to a method for controlling the start of a server in an embodiment of the present application, and the processor 102 executes the computer program stored in the memory 104, thereby performing various functional applications and data processing, that is, implementing the above-mentioned method. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory remotely located with respect to the processor 102, which may be connected to the server device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of a server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, simply referred to as a NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is configured to communicate with the internet wirelessly.

In this embodiment, there is provided a method for controlling startup of a server, fig. 2 is a flowchart of a method for controlling startup of a server according to an embodiment of the present application, and as shown in fig. 2, the server includes a processor and startup firmware, the startup firmware is connected to the processor, the processor is used to connect to a connector, the connector is used to connect to a storage device, the startup firmware is also used to connect to the storage device, the method is applied to the startup firmware, and the method includes the following steps:

Step S202, a target starting request is received, wherein the target starting request is used for requesting starting an operating system of the processor through a connected target storage device, and the processor is connected with the target storage device through a target connector;

Step S204, responding to the target starting request, and detecting target starting information corresponding to the target storage device according to the target device attribute of the target storage device and initial starting information corresponding to the target connector, wherein the initial starting information is used for indicating whether to allow the candidate storage device connected with the target connector to start the operating system or not, and the initial starting information is configured on a target operating interface provided by the starting firmware;

Step S206, in a case where the target startup information is used to indicate that the operating system is allowed to be started by the target storage device, starting the operating system on the processor by the target storage device.

Through the steps, a user can configure the starting information corresponding to the connector on the target operation interface, whether the operating system is allowed to be started from the storage device connected with the connector or not is configured according to the user requirements, starting firmware detects the starting information corresponding to the storage device according to the device attribute of the storage device and the starting information corresponding to the connector, the operating system can be started on the processor through the storage device only under the condition that the starting information indicates that the operating system is allowed to be started through the storage device connected with the connector, and the problem that the operating system is started in the wrong storage device is avoided.

In the solution provided in step S202, the firmware at start-up Mai may include, but is not limited to, a program that is solidified in the storage space of the server, and the program may be, but is not limited to, an operating system for the processor at start-up Mai, for example, the firmware at start-up Mai may be, but is not limited to, including a BIOS.

Alternatively, in the present embodiment, the processor may be used for, but not limited to, data interaction through the connector without the storage device da in the server, for example, the data interaction may be, but not limited to, including a read operation and a write operation, and the processor may be, but not limited to, including a CPU.

Alternatively, in this embodiment, the connector may be used, but is not limited to, to connect the processor to the memory device, providing a physical connection and data transfer path between the processor and the memory device. The connector may include, but is not limited to, a controller to which a PCH or IOH (Input/Output Controller Hub ) or a switch chip is connected, or a port on a server to which no CPU is directly connected, such as PCIe (Peripheral Component Interconnect Express) port, sata (SERIAL ADVANCED technology attachment) port, etc.

Alternatively, in the present embodiment, the storage device may be, but is not limited to, used for storing an operating system, application programs, and data, and the storage device may be, but is not limited to, NVME (Non-Volatile Memory Express, non-volatile memory host controller interface specification), m.2, U.2, e3 s, sata, SAS (SERIAL ATTACHED SCSI (Small Computer SYSTEM INTERFACE, small Computer system interface), serial attached SCSI), SSD (Solid STATE DRIVE, solid state disk), USB (Universal Serial Bus ) hard disk, and the like.

Optionally, in this embodiment, the underlying data transmission protocol of the storage device, or the hardware interface specification, may include, but is not limited to, PCI (PERIPHERAL COMPONENT INTERCONNECT ), or PCIe, or Sata, USB, etc.

Fig. 3 is a schematic link structure of an NVME disk according to an embodiment of the present application, as shown in fig. 3, for an NVME disk, an external mala Raid (Redundant Array of INDEPENDENT DISKS ) card to extend a hard disk, and a PCI/PCIe protocol is used as the bottom layer, where the link structure of the NVME disk may include, but is not limited to, a PE Port (PCIe Port) Port where the NVME disk is directly connected to a CPU, and no intermediate PCH exists. With the development of computer technology, PCH has not been adopted.

FIG. 4 is a schematic diagram of a link structure of a Sata disk according to an embodiment of the present application, as shown in FIG. 4, where a PCH/IOH/switch chip is connected to multiple Sata controllers, each of which is further connected to the Sata disk, and one SataController may be used, but not limited to, to connect to one or more Sata disks.

FIG. 5 is a schematic diagram of a link configuration of a USB memory device according to an embodiment of the present application, as shown in FIG. 5, where a PCH/IOH/transfer chip is coupled to a plurality of USB controllers, each of which is in turn coupled to the USB memory device, and one USB Controller may be, but is not limited to, used to couple to one or more USB memory devices.

It should be noted that, since various types of switching devices exist, in fig. 3,4 and 5, there may be intermediate switching devices, for example, USB controIler connected to the USB storage device through the expansion device.

In the solution provided in step S204, the booting information may be, but is not limited to, used to indicate that the storage device connected through the connector is allowed to boot the operating system, or that the storage device connected through the connector is not allowed to boot the operating system.

In one exemplary embodiment, the target boot information corresponding to the target storage device may be detected, but is not limited to, according to a target device attribute of the target storage device and initial boot information corresponding to the target connector, by screening the target connector from candidate connectors according to a target device type of the target storage device and a target identifier of the target storage device, wherein the target device attribute includes the target device type and the target identifier, and determining the target boot information according to the initial boot information.

Alternatively, in this embodiment, different storage devices may, but are not limited to, correspond to different identifications, different storage devices may, but are not limited to, belong to the same device type, or different storage devices may, but are not limited to, belong to different device types. As an alternative example, the device type may be, but is not limited to being, determined in accordance with an underlying data transfer protocol of the storage device.

Alternatively, in this embodiment, the target device attribute may include, but is not limited to, a device attribute of the target storage device in multiple dimensions, and it is understood that the target device attribute may include, but is not limited to, one or more device attributes.

DEVICE PATH (device path) of the device may include, but is not limited to, DEVICE PATH Node (device path Node) including one or more different attributes, these DEVICE PATH nodes describing various kinds of attributes da of the device from different angles. It can be understood that one Node corresponds to an attribute of the storage device in one dimension, and there are mainly 6 large types DEVICE PATH Node:

(1) Hardware device path (HARDWARE DEVICE PATH) the hardware device path defines how the device connects to the resource domain of the system, which is simply the shared memory, memory mapped I/O, and I/O space of the system. The hardware device path is further divided into subtypes such as PCI device path (PCIDEVICE PATH) and Controller device path (Controller DEVICE PATH).

Through PCIDEVICE PATH, the Function and Device Number attributes of the Device can be obtained.

(2) ACPI (Advanced Configuration and Power Interface, advanced configuration no power management interface) device path for describing devices that are not line da in an industry standard manner, which devices must be described in ACPI namespace line da using ACPI AML (ACPI MACHINE Language, ACPI machine surprised), which device path is connected to the ACPI namespace. Its PCI Root Bus number (PCI root bus number) can be obtained from match of ACPIDEVICE PATH data of the device, da line HID UID CID (HARDWARE ID (Identification, identification number), hardware identifier, unique ID, unique identifier, compatible ID, compatible identifier), etc. And the functions and the Device numbers of the devices in the hardware Device path can be uniquely positioned to the specific devices, because the combination of the Bus, the Device and the Function numbers of the PCIe devices is unique and the devices are not in one-to-one correspondence.

(3) Message device path (MESSAGING DEVICE PATH) a device path for describing a device connection outside the system resource domain, which may describe physical message information, such as a SCSI ID, or abstract information, such as a network protocol IP address. MESSAGING DEVICE PATH are also various sub-types, which are refined to devices not relevant to embodiments of the present application, such as USB DEVICE PATH, SATA DEVICE PATH, MAC (MEDIA ACCESS Control) ADDRESS DEVICE PATH (media access Control address device path), etc.

(4) A media device path (MEDIA DEVICE PATH) that describes a portion of the media abstracted by the boot service, e.g., the media device path may define which partition on the hard disk is being used. In the media device path, the media device path is further divided into subtypes such as a hard disk media device path and a file path media device path.

(5) BIOS boot Mai specifies a device path (BIOS Boot Specification DEVICE PATH) for directing to boot an older version of the operating system, which is based on BIOS boot Mai specification version 1.01.

(6) Hardware device path End (End of HARDWARE DEVICE PATH) this device path node is used to represent the End of a device path instance or device path structure, depending on the subtype.

Under the UEFI specification, DEVICE PATH specific to a device is composed of nodes of each of the different types DEVICE PATH described above, the nodes being DEVICE PATH nodes, for example, the completion DEVICE PATH of a USB device is PciRoot (0 x 0)/PCI (0 x14, 0)/USB (0, 0), wherein "/" is separated by different DEVICE PATH nodes, which respectively correspond to different DEVICE PATH categories of the device, i.e., attribute data of the device from the angles of the categories.

The same is true for Sata and DEVICE PATH of PCIe NVME hard disk devices, such as DEVICE PATH: pciRoot (0)/PCI (0 x1C, 0)/PCI (0, 0)/NVME (1, C3-70-00-0002-0D-08-00) of NVME disk. These DEVICE PATH attributes are assigned to complete during the initialization phase of the device and form DEVICE PATH data list.

Through the support of DEVICE PATH protocol, the attribute of PCIe Bus, device and Function Number of the Device can be obtained, and the attribute values of Bus, device and Function Number of each PCIE DEVICE and Bridge at each level on the whole PCIe chain from the terminal Device to the top Root Port can be traced through the algorithm supported by PCI/PCIe standard.

Note that the manner of DEVICE PATH PROTOCOLs described above is not the only manner of acquiring Bus Device Function Number of the device and PCIe Port or Controller, and other manners of acquiring Bus Device Function Number of the device and PCIe Port or Controller are applicable, for example, getLocation (acquisition location) function supported in UEFI specification efi_pci_io_procol (ENHANCED FIRMWARE INTERFACE PCI I/O procol, enhanced PCI I/O firmware interface Protocol) may also acquire Bus Device Function Number of the PCIe device.

FIG. 6 is a functional function diagram supported in EFI_PCI_IO_PROTOCOL according to an embodiment of the present application, as shown in FIG. 6, the EFI_PCI_IO PROTOCOL provides drivers for accessing basic Memory, IO, PCI configuration and DMA (Direct Memory Access interface) interfaces of its PCI controller, wherein the EFI_PCI_IO PROTOCOL provides drivers including GetLocation functional functions.

FIG. 7 is a schematic diagram of GetLocation function functions supported in EFI_PCI_IO_PROTOCOL according to one embodiment of the application, as shown in FIG. 7, getLocation function may implement the function of retrieving the current PCI bus identification, device identification, and function identification of the PCI controller.

In one exemplary embodiment, the target connector may be, but is not limited to, screened from candidate connectors according to a target device type of a target storage device and a target identification of the target storage device by detecting a target identification range within which the target bus identification falls, and obtaining the target connector corresponding to the target identification range from an identification range and connector having a correspondence, in a case where the target device type includes the first device type, the target connector includes a target port on the server, and in a case where the target device type includes a second device type, and the target identification includes a target bus identification of the target storage device, a target device identification of the target storage device, and a target function identification of the target storage device, obtaining the target bus identification, the target device identification, and the target function identification from a connector having a correspondence, a bus identification, a device identification, and a function identification, in a case where the target device type includes the target bus identification, and the target function identification, and obtaining the target bus identification, in a case where the target device type includes the target bus identification, the target device identification, and the target function identification, in a case where the target device type includes the target bus identification, the target device identification, and the target function identification, and the target bus identification, and the target function identification, respectively, of the target device.

Alternatively, in this embodiment, the storage device of the first device type may, but is not limited to, a storage device including a connector that can determine a connector corresponding to the storage device only through a bus identifier, for example, an NVME hard disk. For NVME hard disk, it can be traced back to which PCIe Port of which CPU it is connected to based on the Bus identification in the acquired device attributes, because the Bus Number supported by each PCIe Port is configurable or a fixed range of values within which it is known which PCIe Port the hard disk device is connected to. Alternatively, in this embodiment, in the case where the connector includes a port on the server, the identification range of the Bus identification corresponding to the port may be, but not limited to, different, for example, a Bus number range of 1 to 10 for port 1 and a Bus number range of 11 to 20 for port 2.

Optionally, in this embodiment, the storage Device of the second Device type may, but is not limited to, a storage Device including a connector corresponding to the storage Device determined by a Bus identifier (Bus Number), a Device identifier (Device Number), and a Function identifier (Function Number), for example, a Sata hard disk and a USB hard disk. For Sata hard disks and USB hard disks, it can be traced back to which Controller it is connected, since each Controller is a logical PCIe device, has the corresponding BusNumber, deviceNumber, function Number attributes, and is fixed.

By combining the equipment type and the identification information of the target storage equipment, the target connector is accurately screened out from a series of candidate connectors, the process ensures that the system can accurately position the connector corresponding to the storage equipment, and the accuracy of identifying the connector corresponding to the storage equipment is improved.

Alternatively, in this embodiment, the processor may be used, but not limited to, to connect to a storage device through a destination port, for example, the processor may be used, but not limited to, to connect to an NVME hard disk through a port.

Optionally, in this embodiment, the connectors corresponding to the target bus identifier and the target device identifier may be selected from the candidate connectors, and then the connectors corresponding to the target function identifier may be selected from the connectors, or the connectors corresponding to the target device identifier and the target function identifier may be selected from the candidate connectors, and then the connectors corresponding to the target bus identifier may be selected from the connectors, or the connectors corresponding to the target bus identifier, the target device identifier and the target function identifier may be selected from the candidate connectors.

Alternatively, in this embodiment, the adaptor may include, but is not limited to, a adaptor chip and a controller connected to the adaptor chip, and the controller may be, but is not limited to, connected to the storage device.

It should be noted that, the above method for obtaining the correspondence between the device and the PCIe Port or the Controller through the PCIe chain is not necessarily the only method, and if there are other methods to achieve the correspondence, the method is also applicable to the present solution.

In one exemplary embodiment, the target boot information may be determined based on the initial boot information by, but is not limited to, determining the target boot information to indicate that the operating system is not allowed to boot through the target storage device if the initial boot information indicates that the candidate storage device connected through the target connector is not allowed to boot the operating system, and determining the target boot information to indicate that the operating system is allowed to boot through the target storage device if the initial boot information indicates that the candidate storage device connected through the target connector is allowed to boot the operating system.

Alternatively, in the present embodiment, the operating system may not be allowed to be started up by any storage device connected through the target connector, but may not be limited to, in the case where the initial startup information is used to indicate that the operating system is not allowed to be started up by the candidate storage device connected through the target connector.

Alternatively, in the present embodiment, the operating system may be allowed to be started up by any one of the storage devices connected through the target connector, but not limited to, in the case where the initial startup information is used to indicate that the operating system is allowed to be started up by the candidate storage device connected through the target connector.

By the method, whether the operating system is allowed to be started from a certain port or the storage device connected with the controller under the transfer chip is accurately controlled according to the content configured on the Set up interface of the BIOS by the user, and the operating system can be prevented from being started from the wrong storage device under the condition that the storage device used for starting the operating system is wrongly appointed by the user, so that the running stability of the server is improved.

In an exemplary embodiment, the target operation interface includes a reference connector and a start setting item, where the start setting item is used to set whether to allow the storage device connected by the reference connector to start the operating system, the reference connector includes the target connector, and before the target start information corresponding to the target storage device is detected according to the target device attribute of the target storage device and the initial start information corresponding to the target connector, a target configuration request triggered on the target operation interface is received, where the target configuration request is used to request that the start information of the target connector be configured as the initial start information, and the start information of the target connector is configured from the reference start information to the initial start information in response to the target configuration request.

Alternatively, in this embodiment, one connector may be used for, but not limited to, connecting one or more storage devices, and one connector may be used for, but not limited to, corresponding to one start setting item, that is, there is a one-to-one correspondence between the connector and the start setting item.

Alternatively, in this embodiment, the reference activation information may be, but is not limited to, null, for example, the current user has not set activation information for the target connector, or the reference activation information is not null, for example, the current user has set activation information for the target connector.

Alternatively, in the present embodiment, the reference start-up information and the initial start-up information may be, but are not limited to, the same, or the reference start-up information and the initial start-up information may be different.

In an exemplary embodiment the initiation settings comprise a first setting for adapting initiation information of the reference connector to indicate that initiation of the operating system by a storage device to which the reference connector is connected is not allowed, and a second setting for adapting initiation information of the reference connector to indicate that initiation of the operating system by a storage device to which the reference connector is connected is allowed, a target configuration request triggered on the target operation interface may be received by, but not limited to, detecting a first trigger operation performed by the first setting and detecting a second trigger operation performed by the second setting, determining that the target configuration request is received in case that the first trigger operation is detected by the first setting and the second trigger operation is not performed, wherein the target configuration request is for requesting initiation information of the target connector to be configured as the initial initiation information, the target configuration request is not allowed to be configured in case that the target configuration request is received in case that the first trigger operation is not performed by the first setting and the second trigger operation is not performed by the second setting is detected, determining that the target configuration request is received in case that the initiation information is not performed by the first setting, the initial boot information is used to indicate that the candidate storage device connected through the target connector is allowed to boot the operating system.

A user may configure the boot information of the connector on the target operation interface, fig. 8 is a schematic diagram of an alternative target operation interface in which the CPU is connected to the storage device through a port, as shown in fig. 8, and may include, but not limited to, a port on the server with reference to the connector, a processor is connected to the storage device through a port, a port on the server includes 3 ports, for example, a boot setting item includes a first setting item and a second setting item, each port has a corresponding first setting item and a second setting item, where the first setting item may be represented by NO (NO) for indicating that the storage device connected through the port is not allowed to boot the operating system, and the second setting item may be represented by YES (YES) for indicating that the storage device connected through the port is allowed to boot the operating system.

After the first trigger operation is performed on the first setting item in the boot setting item 1 corresponding to the port 1, the boot information of the port 1 may be configured to indicate that the port 1 is not allowed to boot the operating system through the connected storage device, after the second trigger operation is performed on the second setting item in the boot setting item 2 corresponding to the port 2, the boot information of the port 2 may be configured to indicate that the port 2 is allowed to boot the operating system through the connected storage device, and after the first trigger operation is performed on the first setting item in the boot setting item 3 corresponding to the port 3, the boot information of the port 3 may be configured to indicate that the port 3 is allowed to boot the operating system through the connected storage device.

By means of the method, a user can set the starting setting items corresponding to the connectors at one time on the target operation interface, so that the starting information of the connectors can be configured in parallel, and the configuration efficiency of the starting information of the connectors is improved.

In one exemplary embodiment, the target operation interface includes the reference connector and a function setting item having a correspondence relationship, the function setting item is used for setting a connection parameter of the reference connector, the start setting item includes a third setting item, the third setting item is used for adjusting start information of the reference connector to be used for indicating that the operation system is not allowed to be started by a storage device connected with the reference connector, the target configuration request triggered on the target operation interface can be received, but is not limited to, by detecting a third trigger operation performed by the third setting item, and the target configuration request is determined to be received when the third setting item is executed with the third trigger operation, wherein the target configuration request is used for requesting that the start information of the target connector be configured as the initial start information, and the initial start information is used for indicating that the candidate storage device connected with the target connector is not allowed to be started by the operation system.

Optionally, in this embodiment, a third setting item may be added to an existing function switch item of a connector, to implement configuration of starting information of the connector, and fig. 9 is a schematic diagram of a target operation interface of an optional CPU connected to a storage device through a controller according to an embodiment of the present application, as shown in fig. 9, may but not limited to use a reference connector including a controller under a switch chip, a processor is connected to the storage device through the controller under the switch chip, the controller under the switch chip includes 3 controllers as an example, and each controller has a corresponding function setting item, where the third setting item is set in the function setting item, and the third setting item may but is not limited to include an Enable item and a Disable item, where the Enable item is used to indicate that the storage device connected through the controller is allowed to start an operating system, and the Disable item is used to indicate that the storage device connected through the controller is not allowed to start the operating system. The third trigger operation may be performed on the third setting item 1 under the function setting item 1 corresponding to the controller 1, that is, when the Disable item is selected, the start-up information of the controller 1 may be configured to indicate that the operating system is not allowed to be started up by the storage device connected to the controller 1, the third trigger operation may be performed on the third setting item 2 under the function setting item 2 corresponding to the controller 2, that is, the start-up information of the controller 2 may be configured to indicate that the operating system is not allowed to be started up by the storage device connected to the controller 2, and the trigger operation may be performed on the third setting item 3 under the function setting item 3 corresponding to the controller 3, that is, when the Enable item is selected, the start-up information of the controller 3 may be configured to indicate that the operating system is allowed to be started up by the storage device connected to the controller 3.

By the mode, the third setting item is newly added in the existing function setting items of the connector, computer resources required by the newly added third setting item are reduced, the utilization efficiency of the computer resources is improved, and a user can configure the starting information of the connectors in parallel by setting the third setting items corresponding to the connectors on the target operation interface at one time, but is not limited to, and the efficiency of configuring the starting information of the connectors is improved.

Alternatively, in this embodiment, the storage device may include a PCIe hard disk device, the reference connector includes a Port on the server, and the processor may implement a new function item for each CPU (Central Processing Unit ) PCIe Port in a BIOS Setup interface (corresponding to the target operation interface) menu, for example, naming the new function item as Boot Option Permission (launch Mai option authority, corresponding to launch Mai setting item), and providing two setting items Yes (corresponding to the second setting item) and No (corresponding to the first setting item). Allowing devices under the Port to create a start Mai item when set to Yes and not allowing devices under the Port to create a start Mai item when set to No. Or adding a sub-setting item Disable Boot Function (disabling the start Mai function, which is equivalent to the third setting item) in the function switch item of the PCIe PORT, when this sub-setting item is selected, the device under the PORT is not allowed to create the start Mai item, which is used to control the hard disk connected under this PCIe PORT, including the hard disk connected to the Raid card transfer under this PCIe PORT, and whether the OS start Mai item can be formed.

For example, when creating an OS (Operating System) Boot Option of Mai, tracing back to the CPU PCIe Port where the device is located by the above method, and acquiring the newly built Boot Option Permission under the Port, or setting the function switch item of PCIe Port, when Boot Option Permission is set to Yes, or the function switch item of PCIe Port is set to Enable, the Boot Mai item is normally created from the device under the Port, when Boot Option Permission is set to No, or the function switch item of PCIe Port is set to Disable Boot Function, the creation of the Boot Mai item is skipped, that is, the Boot Mai item is not generated.

For USB or Sata discs, the reference connector may include a Controller under the switch chip, and the processor may implement a new function item Boot Option Permission in the configuration menu of each Controller, provide two setting items Yes and No, or add a setting item Disable Boot Function in the Controller switch function item, and implement Disable Boot Function in the switching item of each USB or Sata Port when the support chip of the USB and Sata Port can be set for each Port da row switch, for example. Then after the Controller corresponding to each device is located, when Boot Option Permission is set to Yes or the function switch item of the Controller/USB Port/Sata Port is set to Enable, the start Mai item is normally created from the device under the Port, and when Boot Option Permission is set to No or the function switch item of the Controller/USB Port/Sata Port is set to Disable Boot Function, the creation of the start Mai item is skipped, that is, the start Mai item is not generated.

Note that Boot Option Permission and Disable Boot Function are not unique names of the settings, but may be names that explicitly indicate functions.

In the technical solution provided in step S206, in the case where the target startup information is used to indicate that the operating system is not allowed to be started by the target storage device, the operating system may be, but is not limited to, started on the processor by the target storage device, and the alarm information is generated, where the alarm information may be, but is not limited to, used to indicate that the operating system is not allowed to be started on the processor by the target storage device.

Optionally, in this embodiment, after the alarm information is generated, the method further includes jumping to the target operation interface, displaying a start setting item corresponding to the target connector on the target operation interface, prompting a user on the target operation interface whether to adjust, responding to a trigger operation executed by the start setting item, and configuring the start information of the target connector.

According to the embodiment of the application, under the condition that a user hopes to start the operating system through the wrong storage device, the system can directly jump to the configuration interface of the connector, so that the process of repeatedly calling the configuration interface by the user is avoided, the time required for calling the configuration interface is saved, and the configuration efficiency of the configuration information of the connector is improved.

It should be noted that, the technical solution of the embodiment of the present application may be, but not limited to, used in the case of the UEFI startup mode, and may be, but not limited to, other manners of obtaining the correspondence between the device and the at PCIePort or the Controller through the PCIe chain in the Legacy startup mode, for example, an autonomous development function may be used to collect various attributes of the bootable device, including Bus Device Function Number of the device, and further obtain the correspondence between the device and the at PCIe Port or the Controller through the PCIe chain.

Optionally, in this embodiment, the technical solution of the embodiment of the present application may also implement whether to allow PXE to switch for a network card connected to a certain CPU PCIe Port, for example, the storage device in the technical solution of the embodiment of the present application may be replaced with a network card device, and other processes may be similar, or may also be used in other firmware, software, and OS similar scenarios and schemes required.

FIG. 10 is a schematic diagram of an alternative boot creation permission process according to an embodiment of the present application, as shown in FIG. 10, the BIOS (corresponding to the boot firmware) first configures the boot information of each connector according to the user's requirement, for example, the user may select, through the target operation interface, whether to allow creation of the boot operating system from the storage device under the connector. Then, when the user wants a certain storage device to start an operating system, by reading DEVICEPATH information of the storage device, a PCIE Port (corresponding to a connector) or a Controller (corresponding to a connector) to which the storage device is connected is identified. The BIOS further queries the PCIE Port or Controller connected to the storage device for startup information. If set to enable, BIOS will normally create OS boot items on the storage device, if set to disable, or select Disable Boot Function (corresponding to the third setting item) in the function select settings, BIOS will skip the boot item creation of the device, avoiding the unauthorized storage device from booting the operating system.

According to the technical scheme provided by the embodiment of the application, the problem of false starting of a user operating system is solved, the functions of the existing boot operating system of the BIOS are expanded and enhanced, more user use scenes are covered, the product performance is improved, when a user does not want to start in which hard disk device (equivalent to storage equipment) or in which group of hard disk devices the OS starting item is started, the corresponding Boot Option Permission (equivalent to the starting setting item) is set as No (equivalent to the first setting item), or the PCIe Port/Controller/Sata and USB Port switch function item (equivalent to the third setting item) is set as Disable Boot Function, the requirements of starting from the device are met, other functions of the device are not influenced, the efficiency of selecting the starting item of the operating system is improved, and the customer satisfaction is improved.

From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present application.

The embodiment also provides a device for controlling the start of the server, which is used for implementing the foregoing embodiments and preferred embodiments, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

Fig. 11 is a block diagram of a startup control apparatus of a server according to an embodiment of the present application, as shown in fig. 11, the server including a processor and startup firmware, the startup firmware being connected to the processor, the processor being used to connect to a connector, the connector being used to connect to a storage device, the startup firmware being further used to connect to the storage device, the apparatus being applied to the startup firmware, the apparatus including:

A first receiving module 1102, configured to receive a target boot request, where the target boot request is used to request to boot an operating system of the processor through a connected target storage device, and the processor is connected to the target storage device through a target connector; the detecting module 1104 is configured to respond to the target startup request, and detect target startup information corresponding to the target storage device according to a target device attribute of the target storage device and initial startup information corresponding to the target connector, where the initial startup information is used to indicate whether to allow the candidate storage device connected by the target connector to start the operating system, and the initial startup information is configured on a target operation interface provided by the startup firmware;

a startup module 1106 configured to, if the target startup information is used to indicate that the operating system is allowed to be started by the target storage device, start the operating system on the processor by the target storage device.

By means of the device, a user can configure the starting information corresponding to the connector on the target operation interface, whether the storage device connected with the connector is allowed to start the operation system or not is configured according to the user requirements, starting firmware detects the starting information corresponding to the storage device according to the device attribute of the storage device and the starting information corresponding to the connector, the operation system can be started on the processor through the storage device only under the condition that the starting information indicates that the storage device connected with the connector is allowed to start the operation system, and the problem that the operation system is started in the wrong storage device is avoided.

In one exemplary embodiment, the detection module includes:

a screening unit, configured to screen, according to a target device type of a target storage device and a target identifier of the target storage device, the target connector from candidate connectors, where the target device attribute includes the target device type and the target identifier;

and the first determining unit is used for determining the target starting information according to the initial starting information.

In an exemplary embodiment, the screening unit is configured to:

Detecting a target identification range in which the target bus identification falls under when the target equipment type comprises a first equipment type and the target identification comprises a target bus identification of the target storage equipment, and acquiring the target connector corresponding to the target identification range from an identification range with a corresponding relation and a connector, wherein when the target equipment type comprises the first equipment type, the target connector comprises a target port on the server;

And acquiring the target bus identifier, the target device identifier and the target function identifier corresponding to the target function identifier from connectors, bus identifiers, device identifiers and function identifiers with corresponding relations under the condition that the target device type comprises a second device type and the target identifier comprises a target bus identifier of the target storage device, a target device identifier of the target storage device and a target function identifier of the target storage device, wherein the target connector comprises an adapter connected with the processor under the condition that the target device type comprises the second device type.

In an exemplary embodiment, the first determining unit is configured to:

Determining, in a case where the initial boot information is used to indicate that booting of the operating system is not allowed through the candidate storage device to which the target connector is connected, the target boot information is used to indicate that booting of the operating system is not allowed through the target storage device;

And determining the target starting information to indicate that the operating system is allowed to be started through the target storage device under the condition that the initial starting information is used for indicating that the candidate storage device connected through the target connector is allowed to be started through the operating system.

In an exemplary embodiment, the target operation interface includes a reference connector and a start setting item, where the reference connector and the start setting item are related, and the start setting item is used to set whether to allow the storage device connected by the reference connector to start the operating system, and the reference connector includes the target connector, and the apparatus further includes:

The second receiving module is configured to receive a target configuration request triggered on the target operation interface before detecting target startup information corresponding to the target storage device according to the target device attribute of the target storage device and the initial startup information corresponding to the target connector, where the target configuration request is used to request that startup information of the target connector be configured as the initial startup information;

And the configuration module is used for responding to the target configuration request and configuring the starting information of the target connector from the reference starting information to the initial starting information.

In one exemplary embodiment, the boot setting item includes a first setting item for adjusting boot information of the reference connector to indicate that the operating system is not allowed to boot through the storage device connected to the reference connector, and a second setting item for adjusting boot information of the reference connector to indicate that the operating system is allowed to boot through the storage device connected to the reference connector, the second receiving module includes:

a first detection unit configured to detect a first trigger operation performed by the first setting item and detect a second trigger operation performed by the second setting item;

A second determining unit configured to determine that the target configuration request is received, in a case where it is detected that the first setting item is subjected to the first triggering operation and it is detected that the second setting item is not subjected to the second triggering operation, wherein the target configuration request is used to request configuration of startup information of the target connector to the initial startup information, the initial startup information being used to indicate that a candidate storage device connected through the target connector is not allowed to start the operating system;

And a third determining unit configured to determine that the target configuration request is received, in a case where it is detected that the first setting item is not subjected to the first triggering operation and it is detected that the second setting item is subjected to the second triggering operation, where the target configuration request is used to request configuration of startup information of the target connector to the initial startup information, and the initial startup information is used to indicate a candidate storage device that is allowed to be connected through the target connector to start the operating system.

In one exemplary embodiment, the target operation interface includes the reference connector and a function setting item having a correspondence relationship, the function setting item is used for setting a connection parameter of the reference connector, the start setting item includes a third setting item, the third setting item is used for adjusting start information of the reference connector to indicate that the storage device connected through the reference connector is not allowed to start the operation system, and the second receiving module further includes:

a second detection unit configured to detect a third trigger operation performed by the third setting item;

A fourth determining unit configured to determine that the target configuration request is received in a case where the third setting item is executed with the third triggering operation, where the target configuration request is used to request configuration of startup information of the target connector to the initial startup information, and the initial startup information is used to indicate that the candidate storage device connected through the target connector is not allowed to startup the operating system.

It should be noted that each of the above modules may be implemented by software or hardware, and the latter may be implemented by, but not limited to, the above modules all being located in the same processor, or each of the above modules being located in different processors in any combination.

Embodiments of the present application also provide a computer readable storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

In an exemplary embodiment, the computer readable storage medium may include, but is not limited to, a U disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, etc. various media in which a computer program may be stored.

An embodiment of the application also provides an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

In an exemplary embodiment, the electronic device may further include a transmission device connected to the processor, and an input/output device connected to the processor.

Embodiments of the application also provide a computer program product comprising a computer program which, when executed by a processor, implements the steps of any of the method embodiments described above.

Embodiments of the present application also provide another computer program product comprising a non-volatile computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of any of the method embodiments described above.

Embodiments of the present application also provide a computer program comprising computer instructions stored in a computer readable storage medium, a processor of a computer device reading the computer instructions from the computer readable storage medium, the processor executing the computer instructions to cause the computer device to perform the steps of any of the method embodiments described above.

Specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the exemplary implementation, and this embodiment is not described herein.

It will be appreciated by those skilled in the art that the modules or steps of the application described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps of them may be fabricated into a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.

The above description is only of the preferred embodiments of the present application and is not intended to limit the present application, but various modifications and variations can be made to the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principle of the present application should be included in the protection scope of the present application.

Claims

1. A start-up control method of a server is characterized in that the server comprises a processor and start-up firmware, the start-up firmware is connected with the processor, the processor is used for being connected with a connector, the connector is used for being connected with a storage device, the start-up firmware is also used for being connected with the storage device, the method is applied to the start-up firmware, and the method comprises the following steps:

Receiving a target starting request, wherein the target starting request is used for requesting starting an operating system of the processor through a connected target storage device, and the processor is connected with the target storage device through a target connector;

Responding to the target starting request, and detecting target starting information corresponding to the target storage device according to target device attributes of the target storage device and initial starting information corresponding to the target connector, wherein the initial starting information is used for indicating whether to allow the candidate storage device connected through the target connector to start the operating system or not, and the initial starting information is configured on a target operating interface provided by the starting firmware;

And in the case that the target startup information is used for indicating that the operating system is allowed to be started through the target storage device, starting the operating system on the processor through the target storage device.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

The detecting the target startup information corresponding to the target storage device according to the target device attribute of the target storage device and the initial startup information corresponding to the target connector includes:

Screening the target connector from candidate connectors according to a target equipment type of target storage equipment and a target identifier of the target storage equipment, wherein the target equipment attribute comprises the target equipment type and the target identifier;

and determining the target starting information according to the initial starting information.

3. The method of claim 2, wherein the step of determining the position of the substrate comprises,

The screening the target connector from the candidate connectors according to the target device type of the target storage device and the target identifier of the target storage device comprises the following steps:

4. The method of claim 2, wherein the step of determining the position of the substrate comprises,

The determining the target starting information according to the initial starting information comprises the following steps:

5. The method of claim 1, wherein the step of determining the position of the substrate comprises,

The target operation interface comprises a reference connector with a corresponding relation and a starting setting item, wherein the starting setting item is used for setting whether to allow the storage device connected by the reference connector to start the operating system, the reference connector comprises the target connector, and before the target starting information corresponding to the target storage device is detected according to the target device attribute of the target storage device and the initial starting information corresponding to the target connector, the method further comprises the steps of:

Receiving a target configuration request triggered on the target operation interface, wherein the target configuration request is used for requesting to configure starting information of the target connector into the initial starting information;

And responding to the target configuration request, and configuring the starting information of the target connector from reference starting information to the initial starting information.

6. The method of claim 5, wherein the step of determining the position of the probe is performed,

The boot setting item includes a first setting item for adjusting boot information of the reference connector to indicate that booting of the operating system is not allowed through the storage device connected to the reference connector, and a second setting item for adjusting boot information of the reference connector to indicate that booting of the operating system is allowed through the storage device connected to the reference connector, the receiving a target configuration request triggered on the target operating interface includes:

detecting a first trigger operation executed by the first setting item, and detecting a second trigger operation executed by the second setting item;

Determining, in a case where it is detected that the first setting item is subjected to the first trigger operation and it is detected that the second setting item is not subjected to the second trigger operation, that the target configuration request is received, wherein the target configuration request is used to request configuration of boot information of the target connector to the initial boot information, and the initial boot information is used to indicate that a candidate storage device connected through the target connector is not allowed to boot the operating system;

And determining that the target configuration request is received when the first setting item is detected not to execute the first triggering operation and the second setting item is detected to execute the second triggering operation, wherein the target configuration request is used for requesting to configure the starting information of the target connector into the initial starting information, and the initial starting information is used for indicating candidate storage devices which are allowed to be connected through the target connector to start the operating system.

7. The method of claim 5, wherein the step of determining the position of the probe is performed,

The target operation interface includes the reference connector and a function setting item with a corresponding relation, the function setting item is used for setting a connection parameter of the reference connector, the starting setting item includes a third setting item, the third setting item is among the function setting items, the third setting item is used for adjusting starting information of the reference connector to be used for indicating that the storage device connected by the reference connector is not allowed to start the operation system, and the receiving the target configuration request triggered on the target operation interface includes:

detecting a third trigger operation executed by the third setting item;

And determining that the target configuration request is received under the condition that the third setting item is executed with the third triggering operation, wherein the target configuration request is used for requesting to configure the starting information of the target connector into the initial starting information, and the initial starting information is used for indicating that candidate storage devices which are not allowed to be connected through the target connector start the operating system.

8. A start control device of a server is characterized in that,

The server comprises a processor and a starting firmware, wherein the starting firmware is connected with the processor, the processor is used for being connected with a connector, the connector is used for being connected with a storage device, the starting firmware is also used for being connected with the storage device, and the device is applied to the starting firmware and comprises:

The first receiving module is used for receiving a target starting request, wherein the target starting request is used for requesting starting an operating system of the processor through a connected target storage device, and the processor is connected with the target storage device through a target connector;

The detection module is used for responding to the target starting request, detecting target starting information corresponding to the target storage device according to the target device attribute of the target storage device and initial starting information corresponding to the target connector, wherein the initial starting information is used for indicating whether the candidate storage device connected through the target connector is allowed to start the operating system or not, and the initial starting information is configured on a target operating interface provided by the starting firmware;

And the starting module is used for starting the operating system on the processor through the target storage device under the condition that the target starting information is used for indicating that the operating system is allowed to be started through the target storage device.

9. A computer-readable storage medium comprising,

The computer readable storage medium has stored therein a computer program, wherein the computer program when executed by a processor realizes the steps of the method as claimed in any of claims 1 to 7.

10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that,

The processor, when executing the computer program, implements the steps of the method as claimed in any one of claims 1 to 7.