Server and hard disk monitoring method and apparatus therefor, device and medium

By directly connecting the hard disk out-of-band monitoring controller to the target hard disk and using the hard disk status pin for signal modulation, the problem of limited hard disk out-of-band monitoring range is solved, the output of hard disk log data is realized, and the monitoring difficulty is reduced.

WO2025200599A1PCT designated stage Publication Date: 2025-10-02INSPUR SUZHOU INTELLIGENT TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/139297
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-03-29
Filing Date
2024-12-13
Publication Date
2025-10-02

AI Technical Summary

Technical Problem

In existing hard drive out-of-band monitoring solutions, the hard drive must be connected to a hard drive expansion card to achieve out-of-band monitoring, and hard drive status information can only be output through specified data pins. It is difficult to configure and utilize other pins, resulting in a limited range of hard drive out-of-band monitoring.

Method used

The hard drive out-of-band monitoring controller is directly connected to the target hard drive. By sending pin configuration information, using the hard drive status pin for signal modulation, and outputting hard drive log data, it can configure and monitor other hard drive pins.

Benefits of technology

Without connecting a hard drive expansion card, the monitorable range of hard drive out-of-band monitoring is increased, the monitoring difficulty is reduced, and the hard drive status pin is ensured to have no impact on the original function and to be able to output hard drive log data.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024139297_02102025_PF_FP_ABST
    Figure CN2024139297_02102025_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the technical field of hard disk monitoring, and discloses a server and a hard disk monitoring method and apparatus therefor, a device and a medium, which are applied to a hard disk out-of-band monitoring controller. The method comprises: determining a target hard disk which is detected by a system startup controller in an initialization stage, has an out-of-band monitoring function and is connected to a hard disk out-of-band monitoring controller; sending pin configuration information to the target hard disk, and obtaining a target signal outputted when the target hard disk has performed a corresponding configuration on the basis of the pin configuration information, wherein the pin configuration information comprises an identifier used for indicating a hard disk status pin which outputs the target signal and is in the target hard disk, and a configuration parameter used for configuring a signal modulation process of the target hard disk, the signal modulation process being based on hard disk log data and a hard disk status signal corresponding to the hard disk status pin; and demodulating the target signal to obtain the hard disk log data, and executing a monitoring task for the target hard disk. The present application supports configurations of pins of hard disks having an out-of-band monitoring function, thereby widening the range for monitoring hard disks.
Need to check novelty before this filing date? Find Prior Art

Description

A server and hard disk monitoring method, device, equipment and medium thereof

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to a Chinese patent application filed with the Patent Office of China on March 29, 2024, with application number 202410382028.X, entitled “A server and its hard disk monitoring method, device, equipment and medium”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application relates to the field of hard disk monitoring technology, and in particular to a server and a hard disk monitoring method, device, equipment and medium thereof. Background Art

[0004] Healthy hard drive operation is a key factor in ensuring device server reliability. To ensure accurate control of the hard drive's operating status, the device must monitor the drive during operation to obtain status information. Currently, the main hard drive monitoring solutions are divided into in-band and out-of-band hard drive monitoring. Out-of-band hard drive monitoring involves the device's out-of-band monitoring controller, such as the baseboard management controller, obtaining hard drive status information through communication with the hard drive expansion card connected to the hard drive. However, if the hard drive is not connected to a hard drive expansion card, out-of-band monitoring is not possible.

[0005] In the out-of-band monitoring solution for hard drives, the out-of-band monitoring controller can only monitor the hard drive out-of-band if both the out-of-band monitoring controller and the hard drive support the out-of-band monitoring function. Currently, hard drives can only output hard drive status information through specified data pins, making it difficult to configure and utilize other pins of the hard drive. Summary of the Invention

[0006] In view of this, the purpose of this application is to provide a server and hard drive monitoring method, apparatus, device, and medium thereof, which can not only ensure that the hard drive supports out-of-band monitoring functions, but also support the configuration of other hard drive pins, thereby increasing the range of hard drives that can be monitored in the hard drive out-of-band monitoring solution. The specific solution is as follows:

[0007] In a first aspect, the present application discloses a hard disk monitoring method, which is applied to a hard disk out-of-band monitoring controller, comprising:

[0008] Determine a target hard disk; the target hard disk is a hard disk having an out-of-band monitoring function and connected to the hard disk out-of-band monitoring controller via a first signal line detected by the system startup controller during the initialization phase;

[0009] Sending pin configuration information to a target hard disk, and obtaining, via a first signal line, a target signal output by the target hard disk after the target hard disk is configured accordingly according to the pin configuration information; the pin configuration information includes an identifier for indicating a hard disk status pin in the target hard disk that outputs the target signal, and configuration parameters for configuring a signal modulation process of the hard disk status signal corresponding to the hard disk status pin and the hard disk log data of the target hard disk;

[0010] The target signal is demodulated to obtain hard disk log data, and a monitoring task for the target hard disk is performed based on the hard disk log data.

[0011] In some embodiments, the hard disk out-of-band monitoring controller performs a first interactive operation with the target hard disk based on a two-line bidirectional communication mechanism; the first interactive operation is that the hard disk out-of-band monitoring controller sends pin configuration information to the target hard disk, and obtains the target signal output by the target hard disk after the target hard disk is configured accordingly according to the pin configuration information.

[0012] In some embodiments, when the hard disk status signal in the target signal is identified as a non-indication status signal or an invalid signal, and the current moment is the negotiation time period agreed upon with the target hard disk, the hard disk out-of-band monitoring controller performs a second interactive operation with the target hard disk based on a single-line bidirectional communication mechanism; the second interactive operation is that the hard disk out-of-band monitoring controller sends a reverse transmission request to the target hard disk, and when obtaining the target hard disk's permission signal for the reverse transmission request, outputs pin configuration information to the target hard disk.

[0013] In some embodiments, the initialization phase of the system startup controller includes:

[0014] When the server is powered on, the system startup controller is used to detect the version numbers of the hard disk out-of-band monitoring controller and the hard disk to be monitored, and based on the version numbers, it is determined whether the hard disk out-of-band monitoring controller and the hard disk to be monitored both support the out-of-band monitoring function;

[0015] If the system startup controller determines that both the hard disk out-of-band monitoring controller and the hard disk to be monitored support the out-of-band monitoring function, the hard disk to be monitored is used as the target hard disk, and the out-of-band monitoring functions of the hard disk out-of-band monitoring controller and the target hard disk are enabled, and the information of the target hard disk is sent to the hard disk out-of-band monitoring controller, so that the hard disk out-of-band monitoring controller can obtain the hard disk log data of the target hard disk;

[0016] If the hard disk out-of-band monitoring controller or the hard disk to be monitored does not support the out-of-band monitoring function, the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the hard disk to be monitored is disabled.

[0017] In some embodiments, the system boot controller is constructed based on a unified extensible firmware interface or a basic output input system, and the hard disk out-of-band monitoring controller includes a baseboard management controller and / or a complex programmable logic device.

[0018] In some embodiments, when the system boot controller is built based on the unified extensible firmware interface, the process of using the system boot controller to detect the version number of the hard disk out-of-band monitoring controller includes:

[0019] In the driver execution environment phase of the system startup controller, the system startup controller is used to send a target request for obtaining a version number of the baseboard management controller and / or the complex programmable logic device to the baseboard management controller through the intelligent platform management interface;

[0020] The system startup controller obtains the version number returned by the baseboard management controller after responding to the target request; wherein, the process of the baseboard management controller responding to the target request includes: the baseboard management controller reads the first version number corresponding to the baseboard management controller and / or reads the second version number corresponding to the complex programmable logic device from the first register used to store the version number according to the target request, and sends the read first version number and / or second version number to the system startup controller.

[0021] In some embodiments, determining whether the hard disk out-of-band monitoring controller supports the data monitoring function based on the version number includes:

[0022] Determine a first preset version number corresponding to the baseboard management controller, and if the first version number is not lower than the first preset version number, determine that the baseboard management controller supports the data monitoring function; wherein the first preset version number is the minimum version number of the baseboard management controller that supports the data monitoring function;

[0023] And / or, determine a second preset version number corresponding to the complex programmable logic device; if the second version number is not lower than the second preset version number, determine that the complex programmable logic device supports the data monitoring function; wherein the second preset version number is the lowest version number of the complex programmable logic device that supports the data monitoring function.

[0024] In some embodiments, the hard disk monitoring method further includes:

[0025] If the baseboard management controller does not read the first version number from the first register, or the system startup controller does not obtain the first version number sent by the baseboard management controller, the system startup controller detects whether there is a hard disk data display component on the web page interface of the baseboard management controller. If there is a hard disk data display component, it is determined that the baseboard management controller supports the out-of-band monitoring function.

[0026] In some embodiments, the hard disk monitoring method further includes:

[0027] If the baseboard management controller does not read the second version number from the first register, or the system startup controller does not obtain the second version number sent by the baseboard management controller, the system startup controller reads the memory size occupied by the code of the complex programmable logic device from the second register in the complex programmable logic device. If the memory size occupied by the code is the same as the code development size of the complex programmable logic device, it is determined that the complex programmable logic device supports the out-of-band monitoring function.

[0028] In some embodiments, when the system boot controller is built based on the unified extensible firmware interface, the process of using the system boot controller to detect the version number of the hard disk to be monitored includes:

[0029] In the driver execution environment phase of the system startup controller, the system startup controller is used to poll all hard disks to be monitored to obtain the third version number, vendor identifier, and organization unique identifier corresponding to each hard disk to be monitored;

[0030] Accordingly, whether the hard disk to be monitored supports the data monitoring function is determined based on the version number, including:

[0031] Determine whether the hard disk to be monitored supports the data monitoring function based on the third version number, the vendor identifier, and the organization unique identifier.

[0032] In some embodiments, determining whether the hard disk to be monitored supports the data monitoring function based on the third version number, the vendor identifier, and the organization unique identifier includes:

[0033] Determine a third preset version number corresponding to the hard disk to be monitored based on the vendor identifier and the organization unique identifier; the third preset version number is the minimum version number of the hard disk to be monitored that supports the data monitoring function;

[0034] If the third version number is not lower than the third preset version number, and the format of the hard disk management log of the hard disk to be monitored is correct, it is determined that the hard disk to be monitored supports the data monitoring function.

[0035] In some embodiments, the hard disk monitoring method further includes:

[0036] When the system boot controller is built based on the unified extensible firmware interface, if a function configuration modification instruction regarding the hard disk out-of-band monitoring controller and / or the target hard disk is obtained from the user through the first user interface during the boot device selection phase of the system boot controller, or if a function configuration modification instruction regarding the hard disk out-of-band monitoring controller and / or the target hard disk is obtained from the user through the second user interface during the early stage of operating system loading of the system boot controller, the hard disk out-of-band monitoring controller and / or the target hard disk is modified according to the obtained function configuration modification instruction;

[0037] After detecting that the first user interface or the second user interface is closed, detecting, by the system startup controller, whether the function configuration states of the hard disk out-of-band monitoring controller and the out-of-band monitoring function of the target hard disk are consistent; the function configuration state includes an on state and a off state;

[0038] If the function configuration status of the hard disk out-of-band monitoring controller and the target hard disk out-of-band monitoring function is inconsistent, the obtained function configuration modification instruction is determined to be an invalid instruction, and the modified configuration of the hard disk out-of-band monitoring controller and / or the target hard disk is cleared.

[0039] In some embodiments, the first user interface and the second user interface are used to display whether the current hard disk out-of-band monitoring controller and the current target hard disk support the out-of-band monitoring function, and whether the current hard disk out-of-band monitoring controller and the current target hard disk have enabled the out-of-band monitoring function.

[0040] In some embodiments, the hard disk monitoring method further includes:

[0041] The driver is installed through the system startup controller when the operating system starts. If the operating system obtains a function configuration modification instruction regarding the hard disk out-of-band monitoring controller and / or the target hard disk sent by the user through the terminal, the hard disk out-of-band monitoring controller and / or the target hard disk is modified based on the obtained function configuration modification instruction;

[0042] After detecting that the terminal is closed, the driver is used to detect whether the function configuration states of the hard disk out-of-band monitoring controller and the target hard disk out-of-band monitoring function are consistent; the function configuration state includes an on state and a off state;

[0043] If the function configuration status of the hard disk out-of-band monitoring controller and / or the target hard disk out-of-band monitoring function is inconsistent, the obtained function configuration modification instruction is determined to be an invalid instruction, and the modified configuration of the hard disk out-of-band monitoring controller and / or the target hard disk is cleared.

[0044] In some embodiments, the hard disk out-of-band monitoring controller is a baseboard management controller;

[0045] Accordingly, the monitoring task of the target hard disk is performed based on the hard disk log data, including:

[0046] Display hard disk log data on the target interface;

[0047] The corresponding preset threshold condition is determined based on the type of hard disk log data, and it is judged whether the hard disk log data meets the preset threshold condition. If not, an early warning prompt is issued.

[0048] In some embodiments, the hard disk out-of-band monitoring controller includes a baseboard management controller and a complex programmable logic device;

[0049] Accordingly, the monitoring task of the target hard disk is performed based on the hard disk log data, including:

[0050] After obtaining the hard disk log data output by the target hard disk through the hard disk status pin, an interrupt signal is sent to the baseboard management controller through the complex programmable logic device and the first target bus;

[0051] Responding to the interrupt signal through the baseboard management controller, and sending a data read request to the complex programmable logic device through the second target bus, so that the complex programmable logic device sends the hard disk log data to the baseboard management controller;

[0052] The baseboard management controller displays the hard disk log data on the target interface and issues an early warning when the hard disk log data does not meet the preset threshold conditions; the preset threshold conditions are threshold conditions corresponding to the type of hard disk log data.

[0053] In a second aspect, the present application discloses a server including a hard disk out-of-band monitoring controller and a system startup controller;

[0054] A hard drive out-of-band monitoring controller, configured to identify a target hard drive from the hard drives and send pin configuration information to the target hard drive; the target hard drive is a hard drive with out-of-band monitoring functionality detected by the system boot controller during the initialization phase, the pin configuration information including an identifier of a hard drive status pin indicating an output target signal on the target hard drive, and configuration parameters for configuring a signal modulation process for the target hard drive based on hard drive log data and a hard drive status signal corresponding to the hard drive status pin;

[0055] The target hard disk is configured according to the pin configuration information and then outputs a target signal to the hard disk out-of-band monitoring controller, so that the hard disk out-of-band monitoring controller demodulates the target signal to obtain hard disk log data and performs monitoring tasks on the target hard disk based on the hard disk log data.

[0056] In a third aspect, the present application discloses a hard disk monitoring device, which is applied to a hard disk out-of-band monitoring controller, comprising:

[0057] The hard disk determination module is used to determine the target hard disk; the target hard disk is a hard disk with an out-of-band monitoring function and connected to the hard disk out-of-band monitoring controller detected by the system startup controller during the initialization phase;

[0058] A configuration module, configured to send pin configuration information to a target hard drive and obtain a target signal output by the target hard drive after the target hard drive is configured accordingly according to the pin configuration information; the pin configuration information includes an identifier of a hard drive status pin in the target hard drive that outputs the target signal, and configuration parameters for configuring a signal modulation process for the target hard drive based on hard drive log data and the hard drive status signal corresponding to the hard drive status pin;

[0059] The monitoring module is used to demodulate the target signal to obtain hard disk log data, and perform monitoring tasks on the target hard disk based on the hard disk log data.

[0060] In a fourth aspect, the present application discloses an electronic device, comprising:

[0061] Memory, used to store computer programs;

[0062] The processor is used to execute a computer program to implement the steps of the hard disk monitoring method disclosed above.

[0063] In a fifth aspect, the present application discloses a computer non-volatile readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the steps of the aforementioned disclosed hard disk monitoring method are implemented.

[0064] It can be seen that the present application determines the target hard disk through the hard disk out-of-band monitoring controller; the target hard disk is a hard disk with out-of-band monitoring function that is detected by the system startup controller during the initialization phase and is connected to the hard disk out-of-band monitoring controller; pin configuration information is sent to the target hard disk, and the target signal output by the target hard disk after being configured accordingly according to the pin configuration information is obtained; the pin configuration information includes an identifier of the hard disk status pin for indicating the output target signal in the target hard disk, and configuration parameters for the signal modulation process of the hard disk status signal corresponding to the hard disk status pin for configuring the target hard disk; the target signal is demodulated to obtain the hard disk log data, and the monitoring task of the target hard disk is performed based on the hard disk log data.

[0065] Beneficial effects of the present application: In the present application, the hard disk out-of-band monitoring controller first needs to determine the target hard disk with out-of-band monitoring function in the server, specifically the system startup controller in the server detects each hard disk in the initialization phase to detect the hard disk with out-of-band monitoring function. And the present application adopts the method of directly connecting the hard disk out-of-band monitoring controller to the target hard disk to realize out-of-band monitoring of the target hard disk, without the need to connect the hard disk expansion card additionally, that is, regardless of whether the hard disk is connected to the hard disk expansion card, out-of-band monitoring of the hard disk can be realized, reducing the difficulty of out-of-band monitoring. Furthermore, the hard disk out-of-band monitoring controller can also send pin configuration information to the target hard disk, and the pin configuration information includes an identifier of the hard disk status pin for indicating the output target signal in the target hard disk, so that the target hard disk can output the target signal according to the hard disk status pin selected by the hard disk out-of-band monitoring controller; in addition, the pin configuration information also includes configuration parameters for configuring the target hard disk according to the signal modulation process of the hard disk status signal corresponding to the hard disk log data and the hard disk status pin, thereby modulating to obtain the target signal. By modulating the target hard drive's hard drive log data with the hard drive status signal corresponding to the original function of the hard drive status pin to obtain and output the target signal, the hard drive status pin can also output the hard drive log data, overcoming the current limitation that hard drive log data can only be output through a specified data pin connected to a hard drive expansion card. In other words, the target hard drive can output the target signal by modulating the hard drive log data with the hard drive status signal corresponding to the hard drive status pin selected by the hard drive out-of-band monitoring controller. This allows the hard drive out-of-band monitoring controller to obtain hard drive log data by directly connecting to the target hard drive. This solution does not affect the original function of the target hard drive, reduces the difficulty of out-of-band monitoring, and effectively expands the range of hard drives that can be monitored by hard drive out-of-band monitoring. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without any creative work.

[0067] FIG1 is a schematic structural diagram of an existing hard disk in-band monitoring system disclosed in this application;

[0068] FIG2 is a schematic structural diagram of an existing hard disk out-of-band monitoring system disclosed in this application;

[0069] FIG3 is a flow chart of a hard disk monitoring method disclosed in this application;

[0070] FIG4 is a flow chart of a detection method for the initialization phase of a system startup controller disclosed in this application;

[0071] FIG5 is a flowchart of a version number detection and modification configuration disclosed in this application;

[0072] FIG6 is a flowchart of a hard disk out-of-band monitoring method disclosed in this application;

[0073] FIG7 is a diagram showing the architecture of a hard disk monitoring system disclosed in this application;

[0074] FIG8 is a schematic structural diagram of a hard disk monitoring device disclosed in this application;

[0075] FIG9 is a structural diagram of an electronic device disclosed in this application. DETAILED DESCRIPTION

[0076] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0077] Out-of-band monitoring is a crucial monitoring solution for hard drive operations and maintenance. The device's out-of-band monitoring controller, such as a baseboard management controller (BMC), obtains hard drive status information through communication with the drive expansion card connected to the hard drive. However, if the hard drive is not connected to the expansion card, out-of-band monitoring is not possible. Furthermore, out-of-band monitoring requires both the out-of-band monitoring controller and the hard drive to support this functionality. Currently, hard drives can only output hard drive status information via designated data pins, making it difficult to configure and utilize other pins.

[0078] To this end, the embodiments of the present application disclose a server and its hard disk monitoring method, device, equipment and medium, which can not only ensure that the hard disk supports the out-of-band monitoring function, but also support the configuration of other pins of the hard disk, thereby increasing the range of monitorable hard disks in the hard disk out-of-band monitoring solution.

[0079] To facilitate understanding, the following describes the in-band and out-of-band hard drive monitoring solutions.

[0080] According to the network management method, the current equipment operation monitoring solutions are mainly divided into in-band management solutions and out-of-band management solutions.

[0081] In-band management allows network management data and service data to be transmitted over the same link. By logging into the device's operating system and accessing the device's user data, in-band management data can be obtained from the monitored device. As shown in Figure 1, in-band management is the process of obtaining monitoring data from monitored components through the central processing unit (CPU) running the operating system. For example, in an in-band monitoring solution for a hard drive, the CPU communicates with the hard drive, allowing it to access not only the user data stored there but also the hard drive log data recorded during operation. Users can then view this log data by logging into the operating system.

[0082] Out-of-band management involves managing the network through a dedicated network management channel, separating network management data from business data. This separate channel transmits only management data, improving network management efficiency and reliability while also enhancing the security of network management data.

[0083] Because in-band monitoring cannot meet maintenance requirements, after server deployment, out-of-band management and monitoring capabilities are provided through a baseboard management controller (BMC). A BMC is a dedicated service processor that uses sensors to monitor the status of a computer, network server, or other hardware device and communicates with the device's system administrator via independent connections. In practice, the BMC is typically installed on the motherboard or main circuit board of the monitored device. The BMC uses sensors to measure internal physical variables such as temperature, humidity, power supply voltage, fan speed, communication parameters, and operating system (OS) functions. If any of these variables exceeds specified limits, the BMC notifies the system administrator. The BMC also provides web services, including network communication capabilities and a webpage displaying the monitoring interface. Maintenance personnel can access BMC monitoring data by connecting to the BMC of the monitored device via a network cable at the facility site or by connecting the BMCs of multiple monitored devices via a network in a data center.

[0084] Due to the limited performance and pin count of the BMC in a BMC system, as the number of components and items requiring monitoring increases, complex programmable logic devices (CPLDs) are often included in BMC systems to offload performance pressure from the BMC and provide more pins for connecting sensors or monitored components. A CPLD primarily consists of three components: logic blocks, programmable interconnects, and input / output (I / O) blocks. A logic block in a CPLD typically includes 4 to 20 macrocells, each of which typically consists of a product term array, a product term allocation, and programmable registers. Each macrocell has multiple configurations and can be cascaded, enabling the implementation of complex combinational and sequential logic functions. CPLDs with higher integration densities often also include embedded array blocks with on-chip random access memory (RAM) / read-only memory (ROM). The programmable interconnects primarily provide the interconnect network between the logic blocks, macrocells, and I / O pins. Input / output blocks (I / O blocks) provide the interface between internal logic and the device's I / O pins.

[0085] As an important component of the server, the hard disk is an important target for out-of-band monitoring and management. According to the type of communication interface, it is mainly divided into Serial Attached SCSI (SAS) / Serial Advanced Technology Attachment (SATA) interface hard disks and Non-Volatile Memory Host Controller Interface Specification (NVMHCIS or NVM Express, NVMe) interface hard disks. Among them, the SAS interface is compatible with the SATA interface. According to the type of storage medium, hard disks are mainly divided into mechanical hard disks (HDD) and solid-state drives (SSD). Among them, mechanical hard disks mainly have SAS or SATA interfaces. Solid-state drives include SAS, SATA, and NVMe interface hard disks.

[0086] As shown in Figures 1 and 2, the server uses the hard drive by connecting it to the hard drive slot on the hard drive backplane. The hard drive interface typically uses a gold finger structure, where the pins mate with the slots on the hard drive, allowing connections to server-side components (e.g., data pins connect to the CPU) via the circuitry on the hard drive backplane.

[0087] In actual connections, some hard drives are plugged directly into the drive slots on the hard drive backplane, while others are connected to the backplane via a hard drive expander card. Types of hard drive expanders include RAID (Redundant Arrays of Independent Disks) cards, SAS (Serial Small Computer System Interface) expander cards, and SATA (Serial Advanced Technology Attachment) expander cards. Hard drives that plug directly into the drive slots, for example, connect to the CPU via an Advanced Host Controller Interface (AHCI) controller.

[0088] As shown in Figure 1, the central processing unit (CPU) accesses the hard drive via a high-speed serial computer expansion bus (Peripheral Component Interconnect Express, PCI-Express, PCIe). Because hard drives with SAS or SATA interfaces cannot be directly connected to the high-speed serial computer expansion bus, a hard drive expansion card is required to perform signal protocol conversion. The CPU can also obtain or control hard drive status information by connecting to the hard drive backplane via a serial general-purpose input / output (sGPIO) line. In other words, the CPU can obtain hard drive log data by connecting to the hard drive expansion card via the high-speed serial computer expansion bus, or by obtaining hard drive log data through the advanced host controller interface, thereby achieving in-band monitoring of the hard drive.

[0089] As shown in Figure 2, if the baseboard management controller wants to obtain hard disk log data, it can access the hard disk expansion card through the integrated circuit bus (Inter-Integrated Circuit, IIC or I2C) for the hard disk connected to the hard disk expansion card. The baseboard management controller runs the monitoring software to send a transparent transmission command to the hard disk expansion card. The hard disk expansion card can forward the transparent transmission command to the hard disk. After the hard disk responds to the transparent transmission command, it sends the corresponding hard disk log data to the hard disk expansion card, and the hard disk expansion card forwards the hard disk log data to the baseboard management controller. In addition, the NVMe interface hard disk can be directly connected to the central processing unit through a high-speed serial computer expansion bus. The high-speed serial computer expansion bus between the hard disk and the central processing unit can provide an integrated circuit bus to the baseboard management controller to realize the function of forwarding commands and hard disk log data for the baseboard management controller as the hard disk expansion card. Only then can out-of-band monitoring of the hard disk be achieved.

[0090] It can be seen that in the current server monitoring architecture, the business data of the equipment cannot be displayed to the outside world for confidentiality reasons. That is, the operation and maintenance personnel do not have the authority to access the in-band data to obtain the hard disk log data that can be read by the central processing unit. The baseboard management controller used to implement out-of-band monitoring is also unable to directly access the hard disk data, resulting in the limitation of the out-of-band monitoring function of the hard disk. It makes it impossible for the out-of-band monitoring party to obtain the operating status of the hard disk in a timely and accurate manner, thereby threatening the reliability of the hard disk storage.

[0091] Since there is no data path between the baseboard management controller and the hard disk without the integrated circuit bus interface, out-of-band monitoring of the hard disk can only be achieved with the help of a hard disk expansion card that supports receiving transparent commands through the integrated circuit bus interface or a high-speed serial computer expansion bus that provides an integrated circuit bus interface. For hard disks that do not meet this condition, such as hard disks under the advanced host controller interface controller, out-of-band monitoring cannot be achieved.

[0092] 3 , an embodiment of the present application discloses a hard disk monitoring method, which is applied to a hard disk out-of-band monitoring controller. The method includes:

[0093] Step S11: determining a target hard disk; the target hard disk is a hard disk with an out-of-band monitoring function that is detected by the system startup controller during the initialization phase and is connected to the hard disk out-of-band monitoring controller.

[0094] In this embodiment, the hard disk out-of-band monitoring controller first needs to determine the target hard disk in the server that has the out-of-band monitoring function. Specifically, the system startup controller in the server detects each hard disk during the initialization phase to detect the hard disk that has the out-of-band monitoring function. In addition, this application adopts a method of directly connecting the hard disk out-of-band monitoring controller to the target hard disk to achieve out-of-band monitoring of the target hard disk. In other words, when this application performs out-of-band monitoring on the hard disk, the hard disk does not need to be additionally connected to a hard disk expansion card. In other words, regardless of whether the hard disk is connected to the hard disk expansion card, the hard disk out-of-band monitoring controller can achieve out-of-band monitoring of the hard disk, reducing the difficulty of out-of-band monitoring.

[0095] Step S12: Send pin configuration information to the target hard disk, and obtain the target signal output by the target hard disk after being configured accordingly according to the pin configuration information; the pin configuration information includes an identifier of the hard disk status pin for indicating the output target signal in the target hard disk, and configuration parameters for configuring the signal modulation process of the hard disk status signal corresponding to the hard disk status pin based on the hard disk log data and the hard disk status pin for configuring the target hard disk.

[0096] In this embodiment, the hard drive out-of-band monitoring controller can also send pin configuration information to the target hard drive. The pin configuration information includes an identifier for a hard drive status pin on the target hard drive that outputs a target signal, enabling the target hard drive to output the target signal according to the hard drive status pin selected by the hard drive out-of-band monitoring controller. Furthermore, the pin configuration information includes configuration parameters for configuring the target hard drive to modulate the signal based on the hard drive log data and the hard drive status signal corresponding to the hard drive status pin, thereby modulating the target signal. By having the target hard drive modulate the target signal using the hard drive log data and the hard drive status signal corresponding to the original function of the hard drive status pin to obtain and output the target signal, the hard drive status pin can also output hard drive log data, resolving the current limitation of only being able to output hard drive log data through a hard drive expansion card connected to a specified data pin.

[0097] That is, the embodiment of the present application can also use the hard disk status pin of the hard disk to output hard disk log data. In this way, for the hard disk, it can provide multiple pins to output hard disk log data, specifically including the data pin and hard disk status pin originally specified for outputting hard disk log data; among them, the data pin needs to be connected to the hard disk expansion card to output hard disk log data, and the hard disk status pin no longer needs to be connected to the hard disk expansion card, but is directly connected to the hard disk out-of-band monitoring controller, and outputs the hard disk log data through modulation.

[0098] It should be pointed out that the hard disk status pin specifically refers to the hard disk pin other than the data pin, power pin, and ground pin. The hard disk status pin of the hard disk mainly includes the hard disk status indication pin, hard disk production debugging pin, and hard disk idle pin.

[0099] Among them, the hard disk status indication pin includes the hard disk in-place status indication pin (p10 pin), the hard disk read / write status indication pin, etc. (p11 pin). The hard disk status indication pin is a pin used by the hard disk to output the hard disk status indication signal. For example, the hard disk in-place status indication pin is used to output the hard disk in-place status signal, and the hard disk read / write status indication pin is used to output the hard disk read / write status signal. When the hard disk is connected to the hard disk backplane, there are two main ways to connect the hard disk status indication pin. One is to connect to the baseboard management controller to inform the baseboard management controller of the corresponding hard disk status data, and the other is to connect to the control circuit on the hard disk backplane to control the status of the corresponding controlled element so that the user can know the corresponding hard disk status. For example, a hard disk status indicator light is provided on the hard disk backplane to indicate the operating status of the hard disk. For example, when the hard drive is in the read / write state, the hard drive read / write status indicator pin can be controlled to output a square wave signal to the amplifying drive circuit of the hard drive read / write status indicator to control the hard drive read / write status indicator to light up. When the hard drive is not in the read / write state (idle state), the hard drive read / write status indicator pin can be controlled to output a constant level signal (such as a constant high level signal) to turn off the hard drive read / write status indicator to indicate that it is in the idle state. This allows the user to know whether the hard drive is in the read / write state by observing the on and off of the hard drive read / write status indicator. The same principle applies to the hard drive status display based on the hard drive in-place status indicator pin. Alternatively, the hard drive can also output two different constant level signals (one high and one low) through these hard drive status indicator pins to indicate different states. These signals can be input to the baseboard management controller to trigger corresponding recording, processing, or control.

[0100] The production debug pins of hard drives are mainly the pins (debug pins) next to the SAS or SATA interface of hard drives. These pins are usually used during the production debug phase of the hard drive. In actual use of the hard drive, the production debug pins can be used to output boot information during the hard drive initialization phase.

[0101] NVMe hard drives, in addition to the aforementioned drive status indicator pins, also include a drive idle pin. Currently, NVMe hard drives primarily use three connector types: M.2, U.2, and CEM. The M.2 NVMe interface uses different key types for connecting different devices, with Key B and Key M being used for connecting solid-state drives. When an M.2 NVMe interface is connected to a SATA solid-state drive, the definition of its P10 pin is the same as that of P11 on SAS or SATA interfaces: both are drive read / write status indicators. When an M.2 NVMe interface is connected to an NVMe hard drive, its P10 pin is defined as an indicator light control pin. The U.2 NVMe interface is fully compatible with SAS and SATA interfaces, and its P11 pin also serves as a drive read / write status indicator. Pin P32 on the A side of the NVMe interface on the CEM (Compute Express Link Module) connector is a reserved pin and serves as a drive status pin in addition to the drive data pins. Multiple reserved pins exist on x8 (eight-lane) interfaces and above.

[0102] The above-mentioned hard disk status pins are not the pins used by the hard disk to output data, and there is no risk of leaking user data stored in the hard disk. Currently, after the hard disk is inserted into the hard disk backplane, these hard disk status pins are directly connected to the baseboard management controller or have the authority to connect to the baseboard management controller.

[0103] In the hard disk monitoring system provided in the embodiment of the present application, the hard disk status pin of the hard disk used may include at least one of a hard disk status indication pin, a hard disk production debugging pin, and a hard disk idle pin.

[0104] In this embodiment, if hard disk status indication pins such as hard disk in-place status indication pins and hard disk read / write status indication pins are used, since these hard disk pins are usually already connected to the general-purpose input / output (GPIO) pins of the baseboard management controller or the input / output (I / O) pins of the complex programmable logic device, this hardware architecture can be directly adopted without making changes to the hardware architecture of the server, which is simple and convenient to implement.

[0105] Currently, the hard drive production debug pins (debug pins) on devices are usually left floating, and typically include four pins. If the embodiments of the present application use the hard drive production debug pins as the hard drive pins for outputting hard drive log data, a connector with a corresponding number of pins can be used to connect the hard drive production debug pins to the GPIO pins of the baseboard management controller or the I / O pins of a complex programmable logic device.

[0106] Since the idle pins of the hard disk are usually only available in the interface of the hard disk with NVMe (Non Volatile Memory Host Controller Interface Specification, NVMHCIS or NVM Express, non-volatile memory host controller interface) interface, the high-speed signal cannot be left floating. At present, the idle pins of the hard disk in the NVMe interface are grounded through the resistor-capacitor circuit on the hard disk backplane after the hard disk is connected to the hard disk backplane. If the embodiment of the present application adopts the idle pins of the hard disk as the hard disk pins for the hard disk to output hard disk log data, the connection relationship between the idle pins of the hard disk and the hard disk backplane is changed to be connected to the GPIO pins of the baseboard management controller or the I / O pins of the complex programmable logic device.

[0107] For the target hard disk, it is first necessary to determine which hard disk status pin to use to output the hard disk log data based on the identification in the configuration information, and then further configure the signal modulation process based on the configuration parameters in the pin configuration information, that is, how the target hard disk modulates the hard disk status signal corresponding to the hard disk log data and the hard disk status pin to obtain the target signal and output it, so that the hard disk out-of-band monitoring controller can demodulate the target signal to obtain the hard disk log data.

[0108] Among them, the modulation method determined by the target hard disk according to the configuration parameters mainly includes the following two methods: the first method is that after the target hard disk converts the hard disk log data into a level signal, the level signal is directly inserted into the hard disk status signal corresponding to the hard disk status pin to obtain the target signal; the second method is that after the target hard disk converts the hard disk log data into a level signal, the level signal is inserted into the time period when the hard disk status signal corresponding to the hard disk status pin is an invalid signal to obtain the target signal. Through the modulation method of the present application, it does not affect the original function of the hard disk status pin, but can also output the hard disk log data, reduces the difficulty of out-of-band monitoring, and effectively increases the range of hard disks that can be monitored by hard disk out-of-band monitoring, so that the hard disk can output the hard disk log data by directly connecting to the hard disk out-of-band monitor through the hard disk status pin without connecting to the hard disk expansion card.

[0109] It should be pointed out that the process of the hard disk out-of-band monitoring controller sending pin configuration information to the target hard disk can occur at any stage. For example, when the target hard disk is monitored out-of-band for the first time, the pin configuration information is sent to it so that it can output the target signal after making corresponding configuration according to the pin configuration information. It can also occur during the system operation, at this time, the pin configuration information is sent to the target hard disk to replace the pins currently used by the target hard disk.

[0110] In some embodiments, the hard disk out-of-band monitoring controller performs a first interactive operation with the target hard disk based on a two-line bidirectional communication mechanism; the first interactive operation is that the hard disk out-of-band monitoring controller sends pin configuration information to the target hard disk and obtains the target signal output by the target hard disk after being configured accordingly according to the pin configuration information. That is, in this embodiment, two signal lines can be used to achieve bidirectional communication between the hard disk out-of-band monitoring controller and the target hard disk, wherein the hard disk out-of-band monitoring controller obtains the target signal output by the target hard disk after being configured accordingly according to the pin configuration information via the first signal line, and then sends the pin configuration information to the target hard disk via the second signal line. By using two signal lines to achieve bidirectional communication between the hard disk out-of-band monitoring controller and the target hard disk, it can be ensured that the data transmission on the two signal lines does not interfere with each other.

[0111] In some embodiments, when the hard disk status signal in the target signal is identified as a non-indicating status signal or an invalid signal, and the current time is within the negotiation time period agreed upon with the target hard disk, the hard disk out-of-band monitoring controller performs a second interactive operation with the target hard disk based on a single-line bidirectional communication mechanism; the second interactive operation is that the hard disk out-of-band monitoring controller sends a reverse transmission request to the target hard disk, and upon receiving a permission signal from the target hard disk for the reverse transmission request, outputs pin configuration information to the target hard disk. In other words, to save computer resources, embodiments of the present application can also use a single signal line to achieve bidirectional communication between the hard disk out-of-band monitoring controller and the target hard disk. Because a single signal line can only achieve one-way data transmission at a time, that is, either the hard disk out-of-band monitoring controller sends pin configuration information to the target hard disk, or the target hard disk outputs the target signal to the hard disk out-of-band monitoring controller. Therefore, in order to determine who is currently sending data, arbitration logic needs to be designed at both ends of the single line. For example, in embodiments of the present application, the main task of the signal line is to receive the target signal output by the target hard disk, thereby demodulating the target signal to obtain hard disk log data for out-of-band monitoring. Therefore, it is necessary to specify under what circumstances the hard disk out-of-band monitoring controller can send pin configuration information to the target hard disk. Specifically, this embodiment stipulates that only when the hard disk out-of-band monitoring controller identifies that the hard disk status signal in the target signal is a non-indication status signal or an invalid signal, and the current moment is the negotiation time period agreed upon with the target hard disk, can it send a reverse transmission request to the target hard disk through the signal line, and only when it obtains the target hard disk's permission signal for the reverse transmission request can it output the pin configuration information to the target hard disk through the signal line. Among them, the non-indication status signal means that the hard disk status pin is currently in an idle state, the invalid signal means that the signal output by the hard disk status signal does not carry any information, and the negotiation time period is used to stipulate that the hard disk out-of-band monitoring controller can only reversely transmit data within this time period. That is, this embodiment provides a method using single-line bidirectional communication to realize data transmission between the hard disk out-of-band monitoring controller and the target hard disk.

[0112] Step S13: Demodulate the target signal to obtain hard disk log data, and perform a monitoring task on the target hard disk based on the hard disk log data.

[0113] In this embodiment, the hard disk out-of-band monitoring controller demodulates the target signal to obtain hard disk log data, and performs a monitoring task on the target hard disk based on the hard disk log data.

[0114] In some embodiments, the hard disk out-of-band monitoring controller is a baseboard management controller; accordingly, the monitoring task of the target hard disk is performed based on the hard disk log data, including: displaying the hard disk log data on the target interface; determining the corresponding preset threshold conditions based on the type of the hard disk log data, and judging whether the hard disk log data meets the preset threshold conditions, and issuing an early warning prompt if it does not meet the conditions. That is, when the hard disk out-of-band monitoring controller is a baseboard management controller (BMC), that is, the BMC is directly connected to the target hard disk to monitor it out-of-band, then after demodulating the hard disk log data, the BMC directly displays the hard disk log data on its target interface, and determines the corresponding preset threshold conditions based on the type of the hard disk log data. It should be pointed out that the hard disk status information to be monitored includes temperature, number of bad sectors, cumulative number of errors, etc. The threshold conditions corresponding to different status information are inconsistent. Therefore, this application needs to judge whether the hard disk log data meets the corresponding threshold conditions, and issue an early warning prompt if it does not meet the conditions. For example, when the hard disk temperature exceeds 70 degrees, an early warning is issued.

[0115] In some embodiments, the hard disk out-of-band monitoring controller includes a baseboard management controller and a complex programmable logic device; accordingly, the monitoring task of the target hard disk is performed based on the hard disk log data, including: after obtaining the hard disk log data output by the target hard disk through the hard disk status pin, an interrupt signal is sent to the baseboard management controller through the complex programmable logic device and using the first target bus; the baseboard management controller responds to the interrupt signal and sends a data read request to the complex programmable logic device through the second target bus, so that the complex programmable logic device sends the hard disk log data to the baseboard management controller; the baseboard management controller displays the hard disk log data on the target interface, and issues a warning prompt when the hard disk log data does not meet the preset threshold condition; the preset threshold condition is the threshold condition corresponding to the type of the hard disk log data.

[0116] That is, the hard disk out-of-band monitoring controller may include a baseboard management controller (BMC) and a complex programmable logic device (CPLD), that is, in the embodiment of the present application, the BMC is connected to the target hard disk through the CPLD to realize out-of-band monitoring of the target hard disk, and the BMC is connected to each CPLD through the first target bus and the second target bus; wherein the CPLD can be a CPLD on the backplane, used to connect to a solid-state / mechanical hard disk with a SAS (Serial Attached SCSI, serial-attached SCSI interface, where SCSI is Small Computer System Interface, small computer system interface) interface or a SATA (Serial Advanced Technology Attachment, serial advanced technology attachment) interface, or it can be a CPLD on the motherboard, used to connect to a solid-state hard disk with an NVMe (Non Volatile Memory Host Controller Interface Specification, non-volatile memory host controller interface) interface. After the CPLD acquires the target hard drive output signal via the first signal line and demodulates it to obtain the hard drive log data, it then sends an interrupt signal to the BMC via the first target bus. In response to the interrupt signal, the BMC sends a data read request to the CPLD via the second target bus to read the hard drive log data from the CPLD. After reading the hard drive log data, the BMC displays the hard drive log data on the local target interface and issues a warning if the hard drive log data does not meet a preset threshold condition, which corresponds to the type of hard drive log data. Furthermore, the above-mentioned solution, through interrupts, can avoid the BMC from frequently polling the CPLD to read the hard drive log data, reducing pressure on the BMC.

[0117] Beneficial effect: In the present application, the hard disk out-of-band monitoring controller first needs to determine the target hard disk with out-of-band monitoring function in the server, specifically, the system startup controller in the server detects each hard disk in the initialization phase to detect the hard disk with out-of-band monitoring function. And the present application adopts the method of directly connecting the hard disk out-of-band monitoring controller to the target hard disk through the first signal line to realize out-of-band monitoring of the target hard disk, without the need to connect the hard disk expansion card additionally, that is, regardless of whether the hard disk is connected to the hard disk expansion card, out-of-band monitoring of the hard disk can be realized, reducing the difficulty of out-of-band monitoring. Furthermore, the hard disk out-of-band monitoring controller can also send pin configuration information to the target hard disk, and the pin configuration information includes an identifier of the hard disk status pin for indicating the output target signal in the target hard disk, so that the target hard disk can output the target signal according to the hard disk status pin selected by the hard disk out-of-band monitoring controller; in addition, the pin configuration information also includes configuration parameters for configuring the target hard disk according to the signal modulation process of the hard disk status signal corresponding to the hard disk log data and the hard disk status pin, thereby modulating to obtain the target signal. By modulating the target hard drive using the hard drive log data and the hard drive status signal corresponding to the original function of the hard drive status pin to obtain and output the target signal, the hard drive status pin can also output the hard drive log data, thus overcoming the current limitation that hard drive log data can only be output through the specified data pin connected to the hard drive expansion card. In other words, the target hard drive can output the target signal by modulating the hard drive log data and the hard drive status signal corresponding to the hard drive status pin selected by the hard drive out-of-band monitoring controller. This allows the hard drive out-of-band monitoring controller to obtain the hard drive log data by directly connecting to the target hard drive via the first signal line. This solution does not affect the original function of the target hard drive, reduces the difficulty of out-of-band monitoring, and effectively expands the range of hard drives that can be monitored by hard drive out-of-band monitoring.

[0118] It should be noted that, in addition to detecting whether each hard disk has the out-of-band monitoring function during the initialization phase, the system startup controller also needs to detect whether the hard disk out-of-band monitoring controller supports the out-of-band monitoring function, and determine whether to enable the out-of-band monitoring function based on the detection result. For details, see Figures 4 and 5. This application discloses an execution process of the system startup controller during the initialization phase, which specifically includes:

[0119] Step S21: When the server is powered on, the system startup controller is used to detect the version numbers of the hard disk out-of-band monitoring controller and the hard disk to be monitored, and based on the version numbers, it is determined whether the hard disk out-of-band monitoring controller and the hard disk to be monitored both support the out-of-band monitoring function.

[0120] In this embodiment, after the server is powered on, the system startup controller is used to detect the version numbers of the hard disk out-of-band monitoring controller and the hard disk to be monitored, and based on the version numbers, it is determined whether the hard disk out-of-band monitoring controller and the hard disk to be monitored both support the out-of-band monitoring function.

[0121] It is understandable that the embodiment of the present application pre-debugs and configures the hard disk and the hard disk out-of-band monitoring controller so that the out-of-band monitoring system composed of the hard disk and the hard disk out-of-band monitoring controller can have the out-of-band monitoring functions they need, thereby enabling the entire out-of-band monitoring system to operate normally. After debugging and configuring, their respective version numbers are modified so that after checking the corresponding version numbers later, it is considered that the hard disk and the hard disk out-of-band monitoring controller support the out-of-band monitoring function. Among them, for the hard disk, compared to the original hard disk that only uses the hard disk status pin to output the corresponding hard disk status signal, it needs to support the modulation of the hard disk log data and the hard disk status signal corresponding to the hard disk status pin and then output the corresponding target signal; for the hard disk out-of-band monitoring controller, it needs to support the demodulation of the target signal according to the corresponding signal demodulation rules to obtain the hard disk log data, and then perform out-of-band monitoring on the target hard disk based on the hard disk log data.

[0122] It should be noted that existing out-of-band monitoring solutions all assume that the hard disk transmits hard disk log data through the specified data pin, and the hard disk status pin only needs to complete the corresponding status indication function. For example, when the hard disk is in the read-write state, the hard disk read-write status indication pin P11 can be controlled to output a square wave signal to control the hard disk read-write status indicator light to light up. When the hard disk is not in the read-write state (idle state), the hard disk read-write status indication pin P11 is controlled to output a constant level signal (such as a constant high level signal) to indicate that it is in the idle state, so that the user can know whether the hard disk is in the read-write state by watching the hard disk read-write status indicator light on and off.

[0123] Therefore, for the hard disk, since this application additionally adds the function of using its hard disk status pin to output the hard disk log data, and for the hard disk out-of-band monitoring controller, it additionally adds the function of demodulating the hard disk output signal to obtain the hard disk log data and parse the data, it is necessary to use the system startup controller to detect the version number of the hard disk and the hard disk out-of-band monitoring controller.

[0124] In addition, the embodiment of the present application needs to ensure that both the hard disk out-of-band monitoring controller and the hard disk to be monitored support the out-of-band monitoring function, because the interaction between the hard disk out-of-band monitoring controller and the hard disk to be monitored is complementary. If only one of them supports the out-of-band monitoring function, the entire out-of-band monitoring system cannot operate normally.

[0125] It should be noted that the system boot controller can be specifically constructed based on the Unified Extensible Firmware Interface (UEFI) or the Basic Input Output System (BIOS), and the hard disk out-of-band monitoring controller includes a baseboard management controller (BMC) and / or a complex programmable logic device (CPLD). In other words, in this embodiment, the BIOS or UEFI can specifically detect during the initialization phase whether the hard disk out-of-band monitoring controller and the hard disk to be monitored both support the out-of-band monitoring function.

[0126] In a specific embodiment, when the system startup controller is constructed based on the unified extensible firmware interface, the process of using the system startup controller to detect the version number of the hard disk out-of-band monitoring controller includes: in the driver execution environment stage of the system startup controller, using the system startup controller to send a target request for obtaining the version number of the baseboard management controller and / or the complex programmable logic device to the baseboard management controller through the intelligent platform management interface; obtaining, through the system startup controller, the version number returned by the baseboard management controller after responding to the target request; wherein, the process of the baseboard management controller responding to the target request includes: the baseboard management controller reads the first version number corresponding to the baseboard management controller and / or reads the second version number corresponding to the complex programmable logic device from the first register for storing the version number according to the target request, and sends the read first version number and / or second version number to the system startup controller.

[0127] It should be pointed out that the UEFI system can be divided into seven stages from power-on to shutdown. These seven stages are: SEC (Security), PEI (Pre Extensible Firmware Interface Initialization), DXE (Driver Execution Environment), BDS (Boot Dev Select), TSL (Transient System Load), RT (Run Time), and AL (After Life). In the DXE stage of UEFI, UEFI uses the Intelligent Platform Management Interface (IPMI) to request the baseboard management controller to obtain the version number of the baseboard management controller and / or the complex programmable logic device; the baseboard management controller reads the first version number corresponding to the baseboard management controller and / or the second version number corresponding to the complex programmable logic device from the first register used to store the version number according to the target request, and sends the read first version number and / or second version number to UEFI.

[0128] Furthermore, the present application can implement a security verification mechanism in a system boot controller built on UEFI to ensure that the version number received from the BMC is credible. Specifically, it is necessary to create a set of key pairs for signing and verification. A set of predefined public keys are embedded in UEFI to verify the signatures of external providers. Correspondingly, the BMC needs to use the corresponding private key to sign the version number information that needs to be sent to the system boot controller, and ensure the security and integrity of the information through these signatures. During the UEFI startup process, the signature of the BMC firmware is verified by the UEFI firmware to determine whether the version number is credible based on the signature. In addition, the present application uses an encryption protocol to pre-create a secure channel between the BMC and the system boot controller built on UEFI, so as to achieve secure communication between the system boot controller and the BMC based on the secure channel.

[0129] Accordingly, the system startup controller determines whether the hard disk out-of-band monitoring controller supports the data monitoring function based on the version number, including: determining a first preset version number corresponding to the baseboard management controller, and if the first version number is not lower than the first preset version number, determining that the baseboard management controller supports the data monitoring function; wherein the first preset version number is the minimum version number supported by the baseboard management controller for the data monitoring function; and / or determining a second preset version number corresponding to the complex programmable logic device, and if the second version number is not lower than the second preset version number, determining that the complex programmable logic device supports the data monitoring function; wherein the second preset version number is the minimum version number supported by the complex programmable logic device for the data monitoring function. It should be pointed out that the out-of-band monitoring function mainly refers to the data monitoring function, that is, when the system startup controller determines whether the baseboard management controller and the complex programmable logic device support the out-of-band monitoring function, it mainly determines whether they support the function of monitoring hard disk log data (i.e., the data monitoring function). It is understandable that hard drive out-of-band monitoring primarily monitors hard drive log data, while this application adds the ability to output hard drive log data using its hard drive status pin. For a hard drive out-of-band monitoring controller, if the hard drive out-of-band monitoring controller includes a baseboard management controller and a complex programmable logic device (CPLD), the CPLD needs to support signal demodulation and storage of hard drive log data, while the baseboard management controller needs to support reading and parsing hard drive log data from the CPLD. Therefore, this application detects version numbers to determine whether the current version of the baseboard management controller and / or CPLD supports the aforementioned hard drive log data monitoring function.

[0130] In addition, to determine whether the baseboard management controller and complex programmable logic device support the data monitoring function, their current version number is compared with the minimum version number that supports the out-of-band monitoring function. If the current version number is not lower than the minimum version number, it means that the baseboard management controller and complex programmable logic device support the data monitoring function.

[0131] It should be pointed out that if the baseboard management controller does not read the first version number from the first register, or the system startup controller does not obtain the first version number sent by the baseboard management controller, the system startup controller will detect whether there is a hard disk data display component in the web interface of the baseboard management controller. If there is a hard disk data display component, it is determined that the baseboard management controller supports the out-of-band monitoring function. It should be noted that for some baseboard management controllers that cannot find the version number from the first register, or the system startup controller cannot obtain the version number of the baseboard management controller, the embodiment of the present application also provides another method for confirming whether the baseboard management controller supports the out-of-band monitoring function. The web interface of the baseboard management controller is provided with a hard disk data display component, which can display the obtained hard disk log data on the screen in real time. When the system startup controller cannot obtain the version number of the baseboard management controller, it will detect whether there is a hard disk data display component in the corresponding position of the BMC web interface. If it exists, it is considered that the baseboard management controller supports this system function.

[0132] It should be noted that if the baseboard management controller does not read the second version number from the first register, or the system startup controller does not obtain the second version number sent by the baseboard management controller, the system startup controller reads the memory size occupied by the code of the complex programmable logic device from the second register in the complex programmable logic device. If the memory size occupied by the code is the same as the code development size of the complex programmable logic device, it is determined that the complex programmable logic device supports the out-of-band monitoring function. It should be noted that for some complex programmable logic devices that cannot find the version number from the first register, or the system startup controller cannot obtain the version number of the complex programmable logic device, the embodiment of the present application also provides another method for confirming whether the complex programmable logic device supports the out-of-band monitoring function. A second register is provided in the complex programmable logic device for storing the memory size occupied by the code of the complex programmable logic device. When the system startup controller cannot obtain the version number of the complex programmable logic device, it will read the memory size occupied by the code of the complex programmable logic device from the second register. If the memory size occupied by the code is the same as the code development size of the complex programmable logic device, it is determined that the complex programmable logic device supports the out-of-band monitoring function.

[0133] In a specific embodiment, when the system boot controller is built based on the unified extensible firmware interface, the process of using the system boot controller to detect the version number of the hard disk to be monitored includes: in the driver execution environment stage of the system boot controller, using the system boot controller to poll all the hard disks to be monitored to obtain the third version number, vendor identifier and organization unique identifier corresponding to each hard disk to be monitored; accordingly, determining whether the hard disk to be monitored supports the data monitoring function based on the version number includes: determining whether the hard disk to be monitored supports the data monitoring function based on the third version number, vendor identifier and organization unique identifier. Similar to the process of detecting the hard disk out-of-band monitoring controller, the system boot controller determines whether the hard disk supports the out-of-band monitoring function, mainly determining whether the hard disk supports the data monitoring function, that is, whether it can use its hard disk status pin to output hard disk log data. In the DXE stage of UEFI, UEFI can poll all hard disks to be monitored through the PCIE bus, and determine whether the hard disk supports the data monitoring function through the ATA Pass Through command. Specifically, UEFI polls all hard disks to be monitored to obtain the third version number, vendor ID and organizationally unique identifier (OUI) corresponding to each hard disk to be monitored, and then determines whether the hard disk to be monitored supports the data monitoring function based on the third version number, vendor ID and organizationally unique identifier.

[0134] Specifically, the above-mentioned determination of whether the monitored hard disk supports the data monitoring function based on the third version number, the vendor identifier, and the organization unique identifier includes: determining the third preset version number corresponding to the monitored hard disk based on the vendor identifier and the organization unique identifier; the third preset version number being the minimum version number of the monitored hard disk that supports the data monitoring function; if the third version number is not less than the third preset version number, and the format of the hard disk management log of the monitored hard disk is correct, then it is determined that the monitored hard disk supports the data monitoring function. It is understandable that when the system startup controller determines whether the monitored hard disk supports the data monitoring function, it also compares the version number of each monitored hard disk with the minimum version number that supports the out-of-band monitoring function. If the current version number is not less than the minimum version number, and the format of the hard disk management log of the monitored hard disk is correct, then it is determined that the monitored hard disk supports the data monitoring function.

[0135] Step S22: If the system startup controller determines that both the hard disk out-of-band monitoring controller and the hard disk to be monitored support the out-of-band monitoring function, the hard disk to be monitored is used as the target hard disk, and the out-of-band monitoring functions of the hard disk out-of-band monitoring controller and the target hard disk are enabled, and the information of the target hard disk is sent to the hard disk out-of-band monitoring controller, so that the hard disk out-of-band monitoring controller can obtain the hard disk log data of the target hard disk.

[0136] In this embodiment, if the system startup controller determines that both the hard drive out-of-band monitoring controller and the hard drive to be monitored support the out-of-band monitoring function, the hard drive to be monitored is designated as the target hard drive, and the out-of-band monitoring function of both the hard drive out-of-band monitoring controller and the target hard drive is enabled. In other words, the out-of-band monitoring function of both the hard drive out-of-band monitoring controller and the target hard drive is enabled only if both the hard drive out-of-band monitoring controller and the hard drive to be monitored support the out-of-band monitoring function. The system startup controller then sends the target hard drive's information to the hard drive out-of-band monitoring controller, allowing the hard drive out-of-band monitoring controller to obtain the target hard drive's hard drive log data.

[0137] Step S23: If the hard disk out-of-band monitoring controller or the hard disk to be monitored does not support the out-of-band monitoring function, the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the hard disk to be monitored is disabled.

[0138] In this embodiment, if the hard disk out-of-band monitoring controller or the hard disk to be monitored does not support the out-of-band monitoring function, the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the hard disk to be monitored is disabled. It should be noted that the out-of-band monitoring function of both the hard disk out-of-band monitoring controller and the hard disk to be monitored is disabled by default. That is, if either the hard disk out-of-band monitoring controller or the hard disk to be monitored does not support the out-of-band monitoring function, the out-of-band monitoring function of both cannot be enabled.

[0139] It should be noted that the embodiment of the present application supports users to modify the configuration of the out-of-band monitoring function in the user interface. In a specific embodiment, when the system startup controller is constructed based on the unified extensible firmware interface, if the function configuration modification instruction about the hard disk out-of-band monitoring controller and / or the target hard disk is obtained from the user through the first user interface during the boot device selection phase of the system startup controller, or if the function configuration modification instruction about the hard disk out-of-band monitoring controller and / or the target hard disk is obtained from the user through the second user interface during the early stage of the operating system loading of the system startup controller, the hard disk out-of-band monitoring controller and / or the target hard disk are modified and configured according to the obtained function configuration modification instruction; after detecting that the first user interface or the second user interface is closed, the system startup controller is used to detect whether the function configuration status of the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the target hard disk are consistent; the function configuration status includes an on state and a off state; if the function configuration status of the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the target hard disk are inconsistent, the obtained function configuration modification instruction is determined to be an invalid instruction, and the modified configuration of the hard disk out-of-band monitoring controller and / or the target hard disk is cleared. Among them, the first user interface and the second user interface are used to display whether the current hard disk out-of-band monitoring controller and the current target hard disk support the out-of-band monitoring function, and whether the current hard disk out-of-band monitoring controller and the current target hard disk have enabled the out-of-band monitoring function.

[0140] It should be pointed out that the first user interface is specifically the setup interface, and the second user interface is specifically the shell interface, that is, the user can manually check whether the hard disk out-of-band monitoring controller and the target hard disk support and enable the out-of-band monitoring function in the setup interface of the BDS stage of UEFI and the shell interface of the TSL stage, and can also configure the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the target hard disk. If the user modifies the functional configuration status of the hard disk out-of-band monitoring controller and the target hard disk regarding the out-of-band monitoring function through the setup interface and the shell interface, then after detecting that the setup interface or the shell interface is closed, UEFI needs to reconfirm whether the functional configuration status of the hard disk out-of-band monitoring controller and the target hard disk regarding the out-of-band monitoring function is consistent, that is, whether the out-of-band monitoring function is turned on / off at the same time. If one side is not turned on / off, the user's configuration change this time is invalid, and the user's modified configuration of the hard disk out-of-band monitoring controller and / or target hard disk is cleared.

[0141] The specific process is as follows: UEFI enters the Setup interface. After entering, you can check whether the hard disk out-of-band monitoring controller and the target hard disk support the out-of-band monitoring function and whether the function is enabled; if the hard disk out-of-band monitoring controller and the target hard disk both support this system function, you can enable or disable the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the target hard disk by changing the options. In addition, you can also enter a value to change the output interval of the hard disk output target signal; if the user enables / disables the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the target hard disk, then when leaving the Setup interface, UEFI confirms whether the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the target hard disk is enabled / disabled at the same time, otherwise the user's configuration changes will be invalid. In addition, after UEFI enters the Shell, the same process as above can be executed through the corresponding command.

[0142] In addition, the embodiment of the present application also supports users to modify the configuration of the out-of-band monitoring function at the terminal of the operating system. Specifically, the driver is installed when the operating system starts up through the system startup controller. If the operating system obtains the function configuration modification instruction about the hard disk out-of-band monitoring controller and / or the target hard disk sent by the user through the terminal, the hard disk out-of-band monitoring controller and / or the target hard disk are modified based on the obtained function configuration modification instruction; after detecting that the terminal is closed, the driver is used to detect whether the function configuration status of the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the target hard disk are consistent; the function configuration status includes the on state and the off state; if the function configuration status of the out-of-band monitoring function of the hard disk out-of-band monitoring controller and / or the target hard disk is inconsistent, the obtained function configuration modification instruction is determined to be an invalid instruction, and the modified configuration of the hard disk out-of-band monitoring controller and / or the target hard disk is cleared.

[0143] It is understood that the system startup controller installs a driver during operating system startup to confirm whether the out-of-band monitoring function of the hard drive out-of-band monitoring controller is enabled. If so, the following process is performed: When a hot-inserted hard drive is detected, the operating system obtains the hard drive's vendor ID, organizational unique identifier, and version number. Based on these, the operating system confirms whether the hard drive supports out-of-band monitoring, determines the hard drive's management log address, retrieves the hard drive management log from the address, and confirms whether the hard drive management log format is correct. If the hard drive supports out-of-band monitoring and the management log format is correct, the hard drive's out-of-band monitoring function for this system is enabled. Users can view and modify the status and configuration of the complex programmable logic device, baseboard management controller, and hard drive related to this system function by entering commands in the terminal. If the user enables / disables the system function of the hard drive out-of-band monitoring controller and / or the target hard drive, the driver confirms whether the out-of-band monitoring function of both the hard drive out-of-band monitoring controller and the target hard drive is enabled / disabled when the terminal is closed; otherwise, the user's configuration changes will be invalid.

[0144] It can be seen that in the embodiment of the present application, the system startup controller will respectively detect whether each hard disk and the hard disk out-of-band monitoring controller supports the out-of-band monitoring function during the initialization phase, and determine whether to enable the out-of-band monitoring function based on the detection results. The out-of-band monitoring function is only enabled when both the hard disk and the hard disk out-of-band monitoring controller support the out-of-band monitoring function. In addition, the present application also supports users to manually view and modify the configuration of the out-of-band monitoring function in the setup interface of the BDS phase of UEFI and the shell interface of the TSL phase, and also supports manual viewing and modification of the configuration of the out-of-band monitoring function in the operating system terminal. After detecting that the setup interface and the shell interface are closed or the terminal is closed, the UEFI / driver needs to reconfirm whether the functional configuration status of the hard disk out-of-band monitoring controller and the target hard disk regarding the out-of-band monitoring function is consistent, that is, confirm whether the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the target hard disk is turned on / off at the same time, otherwise the user's configuration change will be invalid. That is, no matter at any stage of system operation, the functional configuration status of the hard disk out-of-band monitoring controller and the target hard disk regarding the out-of-band monitoring function needs to be consistent, that is, turned on or off at the same time. If the user only modifies the functional configuration status of one of them, making the functional configuration status of the two inconsistent after the modification, the user's modified configuration here is considered invalid to ensure the normal operation of the system.

[0145] Specifically referring to FIG6 , the present application discloses a flow chart of monitoring a hard disk using a baseboard management controller and a complex programmable logic device.

[0146] First, the system startup controller detects whether the hard disk, baseboard management controller, and complex programmable logic device all support the out-of-band monitoring function, and receives the results of the hard disk, baseboard management controller, and complex programmable logic device supporting the out-of-band monitoring function. The present embodiment does not limit whether the system startup controller detects the hard disk first or the baseboard management controller and complex programmable logic device first. Both can be detected simultaneously or in a specified order. Figure 6 is only a specific example provided for the convenience of describing the process of this solution.

[0147] Furthermore, if the hard disk, baseboard management controller, and complex programmable logic device all support out-of-band monitoring, the out-of-band monitoring functions of the hard disk, baseboard management controller, and complex programmable logic device are enabled, and the function enabling result is returned. Similarly, the present embodiment does not limit whether the system startup controller first enables the out-of-band monitoring function of the hard disk or the baseboard management controller and complex programmable logic device. Both functions can be enabled simultaneously or in a prescribed order. Figure 6 is merely a specific example provided for the convenience of describing the process of this solution.

[0148] After the out-of-band monitoring functions of the hard disk, baseboard management controller and complex programmable logic device are enabled, the hard disk can perform the step of transmitting the hard disk log data to the outside so that the baseboard management controller and complex programmable logic device can perform out-of-band monitoring of the hard disk.

[0149] Specifically, the hard disk modulates the hard disk status signal corresponding to the hard disk log data and the hard disk status pin to output a target signal to the complex programmable logic device. The complex programmable logic device demodulates the target signal to obtain the hard disk log data and stores it locally, and sends an interrupt signal to the baseboard management controller to remind the baseboard management controller to read the data. The baseboard management controller responds to the interrupt signal and reads the hard disk log data from the complex programmable logic device, and then displays it on its target interface, and issues a warning prompt when the hard disk log data does not meet the preset threshold conditions.

[0150] The embodiment of the present application further discloses a server, comprising a hard disk out-of-band monitoring controller, a hard disk, a system startup controller, and a first signal line;

[0151] A hard drive out-of-band monitoring controller, configured to identify a target hard drive from the hard drives and send pin configuration information to the target hard drive; the target hard drive is a hard drive with out-of-band monitoring functionality detected by the system boot controller during the initialization phase, the pin configuration information including an identifier of a hard drive status pin indicating an output target signal on the target hard drive, and configuration parameters for configuring a signal modulation process for the target hard drive based on hard drive log data and a hard drive status signal corresponding to the hard drive status pin;

[0152] The target hard disk is configured according to the pin configuration information and then outputs a target signal to the hard disk out-of-band monitoring controller through the first signal line, so that the hard disk out-of-band monitoring controller demodulates the target signal to obtain hard disk log data and performs monitoring tasks on the target hard disk based on the hard disk log data.

[0153] That is, in this application, the hard disk out-of-band monitoring controller first determines the target hard disk with out-of-band monitoring function from each hard disk in the server. Specifically, the system startup controller in the server detects each hard disk during the initialization phase to detect the hard disk with out-of-band monitoring function. Furthermore, the hard disk out-of-band monitoring controller can also send pin configuration information to the target hard disk. The pin configuration information includes an identifier of the hard disk status pin for indicating the output target signal in the target hard disk, so that the target hard disk can output the target signal according to the hard disk status pin selected by the hard disk out-of-band monitoring controller; in addition, the pin configuration information also includes configuration parameters for configuring the target hard disk according to the hard disk log data and the signal modulation process of the hard disk status signal corresponding to the hard disk status pin, thereby modulating the target signal. By using the hard disk log data and the hard disk status signal corresponding to the original function of the hard disk status pin to modulate the target signal and output it, the hard disk status pin can also output the hard disk log data, which solves the current limitation that the hard disk log data can only be output by connecting the hard disk expansion card through the specified data pin. After the target hard drive is configured accordingly according to the pin configuration information, it outputs a target signal to the hard drive out-of-band monitoring controller via the first signal line, so that the hard drive out-of-band monitoring controller demodulates the target signal to obtain the hard drive log data and performs the monitoring task on the target hard drive based on the hard drive log data. In other words, the target hard drive can output the target signal by modulating the hard drive status signal corresponding to the hard drive log data and the hard drive status pin selected by the hard drive out-of-band monitoring controller, so that the hard drive out-of-band monitoring controller can obtain the hard drive log data by directly connecting to the target hard drive via the first signal line. In this way, the hard drive out-of-band monitoring controller directly connects to the target hard drive via the first signal line to achieve out-of-band monitoring of the target hard drive, without the need for an additional hard drive expansion card. In other words, regardless of whether the hard drive is connected to the hard drive expansion card, out-of-band monitoring of the hard drive can be achieved. The above solution does not affect the original function of the target hard drive, reduces the difficulty of out-of-band monitoring, and effectively increases the range of hard drives that can be monitored by hard drive out-of-band monitoring.

[0154] As shown in FIG7 , this application takes the hard disk out-of-band monitoring controller as a baseboard management controller and a complex programmable logic device as an example to explain the technical solution of this application in detail.

[0155] First, the hard disk monitoring system architecture shown in Figure 7 is composed of a baseboard management controller, a first target bus, a second target bus, a complex programmable logic device, a target hard disk, and a system startup controller.

[0156] The baseboard management controller is connected to the complex programmable logic devices on each hard disk backplane / mainboard in the server system through the first target bus and the second target bus. It is responsible for obtaining the hard disk log data stored in each complex programmable logic device by polling through the second target bus, or receiving the interrupt signal sent by the complex programmable logic device through the first target bus, and then obtaining the hard disk log data stored in the corresponding complex programmable logic device through the second target bus.

[0157] The first target bus is a signal bus for out-of-band management in the server system, which meets the requirements of complex programmable logic devices to send interrupt signals to the baseboard management controller; when the second target bus supports the interrupt function, the first target bus is an optional component.

[0158] The second target bus is the data bus for out-of-band management in the server system. It works in a one-master-multiple-slave mode, where the baseboard management controller is the master device, and each complex programmable logic device is a slave device. The second target bus is a required component.

[0159] The complex programmable logic device consists of a hard disk monitoring data service module and a pulse width demodulation module:

[0160] The hard disk monitoring data service module is responsible for receiving and temporarily storing the hard disk log data demodulated by the pulse width demodulation module. When there is data, it sends an interrupt to the baseboard management controller through the first target bus, responds to the data read request sent by the baseboard management controller through the second target bus, and returns the hard disk log data.

[0161] The pulse width demodulation module is connected to a pin of a target hard drive through a pin, accurately identifying the level duration of the current output signal of the hard drive pin, and demodulating the current output signal based on the level duration to obtain the hard drive log data.

[0162] The target hard disk uses the current hard disk log data to modulate the hard disk pin output signal to obtain the current output signal, and outputs it to the complex programmable logic device through the hard disk pin.

[0163] The system startup controller can automatically detect the hard disk, complex programmable logic device, and baseboard management controller when the server starts up, and confirm the versions of the hard disk, complex programmable logic device, and baseboard management controller; it can be understood that the embodiment of the present application has pre-debugged and configured the hard disk, complex programmable logic device, and baseboard management controller, and modified their respective version information, so that the out-of-band monitoring system composed of the hard disk, complex programmable logic device, and baseboard management controller can have the out-of-band monitoring functions they need, so that the entire out-of-band monitoring system can operate normally. Therefore, by detecting its version number, it can be determined whether the hard disk, complex programmable logic device, and baseboard management controller support the out-of-band monitoring function at the same time. If they all support it, the out-of-band monitoring function of the three modules is turned on. If the hard disk, complex programmable logic device, and baseboard management controller cannot support the out-of-band monitoring function at the same time, it is confirmed that the three modules have all turned off the out-of-band monitoring function. Among them, the hard disk, complex programmable logic device, and baseboard management controller all have the out-of-band monitoring function turned off by default.

[0164] As shown in FIG8 , an embodiment of the present application discloses a hard disk monitoring device, which is applied to a hard disk out-of-band monitoring controller. The device includes:

[0165] The hard disk determination module 11 is used to determine the target hard disk; the target hard disk is a hard disk with an out-of-band monitoring function detected by the system startup controller during the initialization phase and connected to the hard disk out-of-band monitoring controller via a first signal line;

[0166] Configuration module 12, configured to send pin configuration information to a target hard drive and obtain, via a first signal line, a target signal output by the target hard drive after the target hard drive is configured accordingly according to the pin configuration information; the pin configuration information includes an identifier for indicating a hard drive status pin in the target hard drive that outputs the target signal, and configuration parameters for configuring a signal modulation process for the target hard drive based on hard drive log data and the hard drive status signal corresponding to the hard drive status pin;

[0167] The monitoring module 13 is configured to demodulate the target signal to obtain hard disk log data, and perform a monitoring task on the target hard disk based on the hard disk log data.

[0168] Beneficial effect: In the present application, the hard disk out-of-band monitoring controller first needs to determine the target hard disk with out-of-band monitoring function in the server, specifically, the system startup controller in the server detects each hard disk in the initialization phase to detect the hard disk with out-of-band monitoring function. And the present application adopts the method of directly connecting the hard disk out-of-band monitoring controller to the target hard disk through the first signal line to realize out-of-band monitoring of the target hard disk, without the need to connect the hard disk expansion card additionally, that is, regardless of whether the hard disk is connected to the hard disk expansion card, out-of-band monitoring of the hard disk can be realized, reducing the difficulty of out-of-band monitoring. Furthermore, the hard disk out-of-band monitoring controller can also send pin configuration information to the target hard disk, and the pin configuration information includes an identifier of the hard disk status pin for indicating the output target signal in the target hard disk, so that the target hard disk can output the target signal according to the hard disk status pin selected by the hard disk out-of-band monitoring controller; in addition, the pin configuration information also includes configuration parameters for configuring the target hard disk according to the signal modulation process of the hard disk status signal corresponding to the hard disk log data and the hard disk status pin, thereby modulating to obtain the target signal. By modulating the target hard drive using the hard drive log data and the hard drive status signal corresponding to the original function of the hard drive status pin to obtain and output the target signal, the hard drive status pin can also output the hard drive log data, thus overcoming the current limitation that hard drive log data can only be output through the specified data pin connected to the hard drive expansion card. In other words, the target hard drive can output the target signal by modulating the hard drive log data and the hard drive status signal corresponding to the hard drive status pin selected by the hard drive out-of-band monitoring controller. This allows the hard drive out-of-band monitoring controller to obtain the hard drive log data by directly connecting to the target hard drive via the first signal line. This solution does not affect the original function of the target hard drive, reduces the difficulty of out-of-band monitoring, and effectively expands the range of hard drives that can be monitored by hard drive out-of-band monitoring.

[0169] In some embodiments, the hard disk out-of-band monitoring controller performs a first interactive operation with the target hard disk based on a two-line bidirectional communication mechanism; the first interactive operation is that the hard disk out-of-band monitoring controller sends pin configuration information to the target hard disk, and obtains the target signal output by the target hard disk after the target hard disk is configured accordingly according to the pin configuration information.

[0170] In some embodiments, the device is used to identify that the hard disk status signal in the target signal is a non-indication status signal or an invalid signal, and the current moment is the negotiation time period agreed with the target hard disk, and the hard disk out-of-band monitoring controller performs a second interactive operation with the target hard disk based on a single-line bidirectional communication mechanism; the second interactive operation is that the hard disk out-of-band monitoring controller sends a reverse transmission request to the target hard disk, and when obtaining the target hard disk's permission signal for the reverse transmission request, outputs pin configuration information to the target hard disk.

[0171] In some embodiments, during the initialization phase of the system startup controller, the apparatus further comprises:

[0172] A version detection module is used to detect the version numbers of the hard disk out-of-band monitoring controller and the hard disk to be monitored using the system startup controller when the server is powered on, and to determine whether the hard disk out-of-band monitoring controller and the hard disk to be monitored both support the out-of-band monitoring function based on the version numbers;

[0173] A function enabling module is used to, if the system startup controller determines that both the hard disk out-of-band monitoring controller and the hard disk to be monitored support the out-of-band monitoring function, use the hard disk to be monitored as the target hard disk, enable the out-of-band monitoring functions of the hard disk out-of-band monitoring controller and the target hard disk, and send information about the target hard disk to the hard disk out-of-band monitoring controller so that the hard disk out-of-band monitoring controller can obtain hard disk log data of the target hard disk;

[0174] The function disabling module is used to disable the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the hard disk to be monitored if the hard disk out-of-band monitoring controller or the hard disk to be monitored does not support the out-of-band monitoring function.

[0175] In some embodiments, the system boot controller is constructed based on a unified extensible firmware interface or a basic output input system, and the hard disk out-of-band monitoring controller includes a baseboard management controller and / or a complex programmable logic device.

[0176] In some embodiments, when the system startup controller is constructed based on the unified extensible firmware interface, the version detection module is specifically used to use the system startup controller to send a target request for obtaining the version number of the baseboard management controller and / or the complex programmable logic device to the baseboard management controller through the intelligent platform management interface during the driver execution environment stage of the system startup controller; obtain the version number returned by the baseboard management controller after responding to the target request through the system startup controller; wherein, the process of the baseboard management controller responding to the target request includes: the baseboard management controller reads the first version number corresponding to the baseboard management controller and / or reads the second version number corresponding to the complex programmable logic device from the first register for storing the version number according to the target request, and sends the read first version number and / or second version number to the system startup controller.

[0177] In some embodiments, the version detection module is specifically used to determine a first preset version number corresponding to the baseboard management controller. If the first version number is not lower than the first preset version number, it is determined that the baseboard management controller supports the data monitoring function; wherein the first preset version number is the minimum version number of the baseboard management controller supporting the data monitoring function; and / or, determine a second preset version number corresponding to the complex programmable logic device. If the second version number is not lower than the second preset version number, it is determined that the complex programmable logic device supports the data monitoring function; wherein the second preset version number is the minimum version number of the complex programmable logic device supporting the data monitoring function.

[0178] In some embodiments, the apparatus further comprises:

[0179] The component detection unit is used to detect whether there is a hard disk data display component on the web page interface of the baseboard management controller through the system startup controller if the baseboard management controller fails to read the first version number from the first register, or the system startup controller fails to obtain the first version number sent by the baseboard management controller. If the hard disk data display component exists, it is determined that the baseboard management controller supports the out-of-band monitoring function.

[0180] In some embodiments, the apparatus further comprises:

[0181] A memory comparison unit is used to read the code occupied memory size of the complex programmable logic device from the second register in the complex programmable logic device through the system startup controller if the baseboard management controller fails to read the second version number from the first register, or the system startup controller fails to obtain the second version number sent by the baseboard management controller; if the code occupied memory size is the same as the code development size of the complex programmable logic device, it is determined that the complex programmable logic device supports the out-of-band monitoring function.

[0182] In some embodiments, when the system startup controller is built based on the unified extensible firmware interface, the version detection module is specifically used to use the system startup controller to poll all hard disks to be monitored during the driver execution environment stage of the system startup controller to obtain the third version number, vendor identifier and organization unique identifier corresponding to each hard disk to be monitored; based on the third version number, vendor identifier and organization unique identifier, determine whether the hard disk to be monitored supports the data monitoring function.

[0183] In some embodiments, the version detection module is specifically used to determine the third preset version number corresponding to the hard disk to be monitored based on the vendor identifier and the organization unique identifier; the third preset version number is the minimum version number of the hard disk to be monitored that supports the data monitoring function; if the third version number is not lower than the third preset version number, and the format of the hard disk management log of the hard disk to be monitored is correct, it is determined that the hard disk to be monitored supports the data monitoring function.

[0184] In some embodiments, the apparatus further comprises:

[0185] A first configuration unit is configured to, when the system boot controller is constructed based on the Unified Extensible Firmware Interface, modify the configuration of the hard disk out-of-band monitoring controller and / or the target hard disk using the obtained function configuration modification instruction if a function configuration modification instruction regarding the hard disk out-of-band monitoring controller and / or the target hard disk is sent by a user through a first user interface during a boot device selection phase of the system boot controller, or if a function configuration modification instruction regarding the hard disk out-of-band monitoring controller and / or the target hard disk is sent by a user through a second user interface during an early stage of operating system loading of the system boot controller;

[0186] A first state detection unit is configured to detect, after detecting that the first user interface or the second user interface is closed, whether the function configuration states of the hard disk out-of-band monitoring controller and the out-of-band monitoring function of the target hard disk are consistent through the system startup controller; the function configuration state includes an on state and a off state;

[0187] The first configuration clearing unit is used to determine that the obtained function configuration modification instruction is an invalid instruction if the function configuration status of the hard disk out-of-band monitoring controller and the target hard disk out-of-band monitoring function are inconsistent, and clear the modified configuration of the hard disk out-of-band monitoring controller and / or the target hard disk.

[0188] In some embodiments, the first user interface and the second user interface are used to display whether the current hard disk out-of-band monitoring controller and the current target hard disk support the out-of-band monitoring function, and whether the current hard disk out-of-band monitoring controller and the current target hard disk have enabled the out-of-band monitoring function.

[0189] In some embodiments, the apparatus further comprises:

[0190] A second configuration unit is configured to install a driver program via a system startup controller when the operating system is started, and if the operating system obtains a function configuration modification instruction regarding the hard disk out-of-band monitoring controller and / or the target hard disk sent by the user via the terminal, modify the configuration of the hard disk out-of-band monitoring controller and / or the target hard disk based on the obtained function configuration modification instruction;

[0191] A second state detection unit is used to detect whether the function configuration states of the hard disk out-of-band monitoring controller and the target hard disk out-of-band monitoring function are consistent through a driver after detecting that the terminal is closed; the function configuration state includes an on state and a off state;

[0192] The second configuration clearing unit is used to determine that the obtained function configuration modification instruction is an invalid instruction if the function configuration status of the hard disk out-of-band monitoring controller and / or the target hard disk out-of-band monitoring function is inconsistent, and clear the modified configuration of the hard disk out-of-band monitoring controller and / or the target hard disk.

[0193] In some embodiments, the hard disk out-of-band monitoring controller is a baseboard management controller;

[0194] Correspondingly, the monitoring module includes:

[0195] A display unit, used for displaying hard disk log data on a target interface;

[0196] The first warning unit is used to determine the corresponding preset threshold condition based on the type of hard disk log data, and judge whether the hard disk log data meets the preset threshold condition, and issue a warning prompt if it does not meet the condition.

[0197] In some embodiments, the hard disk out-of-band monitoring controller includes a baseboard management controller and a complex programmable logic device;

[0198] Correspondingly, the monitoring module includes:

[0199] an interrupt signal sending unit, configured to send an interrupt signal to a baseboard management controller via a complex programmable logic device and a first target bus after acquiring hard disk log data outputted by the target hard disk via the hard disk status pin;

[0200] a data reading unit, configured to respond to the interrupt signal through the baseboard management controller and send a data reading request to the complex programmable logic device through the second target bus, so that the complex programmable logic device sends the hard disk log data to the baseboard management controller;

[0201] The second warning unit is used to display the hard disk log data on the target interface through the baseboard management controller and issue a warning prompt when the hard disk log data does not meet the preset threshold condition; the preset threshold condition is a threshold condition corresponding to the type of hard disk log data.

[0202] Figure 9 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Specifically, the device 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. Memory 22 is used to store a computer program, which is loaded and executed by processor 21 to implement the relevant steps of the hard disk monitoring method performed by the electronic device disclosed in any of the aforementioned embodiments.

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

[0204] Among them, the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 21 can be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 21 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 21 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 21 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0205] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or CD, etc. The resources stored thereon include an operating system 221, a computer program 222 and data 223, etc. The storage method can be temporary storage or permanent storage.

[0206] The operating system 221 is used to manage and control the various hardware devices and computer programs 222 on the electronic device, so as to enable the processor 21 to calculate and process the massive amount of data 223 in the memory 22. It can be Windows, Unix, Linux, etc. In addition to including computer programs capable of performing the hard disk monitoring method performed by the electronic device disclosed in any of the aforementioned embodiments, the computer programs 222 may further include computer programs capable of performing other specific tasks. Data 223 may include data received by the electronic device from external devices, as well as data collected by its own input and output interface 25.

[0207] Furthermore, an embodiment of the present application also discloses a computer non-volatile readable storage medium, in which a computer program is stored. When the computer program is loaded and executed by a processor, the hard disk monitoring method steps disclosed in any of the aforementioned embodiments are implemented.

[0208] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from the other embodiments. Reference can be made to the descriptions of the identical or similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and the relevant parts can be referred to the descriptions of the methods.

[0209] Those skilled in the art may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the composition and steps of each example according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0210] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art.

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

[0212] The above is a detailed introduction to the hard disk monitoring method, device, equipment and storage medium provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core ideas. At the same time, for general technical personnel in this field, based on the ideas of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A hard disk monitoring method, characterized in that: Applicable to hard disk out-of-band monitoring controllers, including: Determine a target hard disk; the target hard disk is a hard disk with an out-of-band monitoring function and connected to the hard disk out-of-band monitoring controller detected by the system startup controller during the initialization phase; Sending pin configuration information to the target hard disk and obtaining a target signal output by the target hard disk after the target hard disk is configured according to the pin configuration information; the pin configuration information includes an identifier configured to indicate a hard disk status pin in the target hard disk that outputs the target signal, and configuration parameters configured to configure a signal modulation process of the target hard disk based on hard disk log data and the hard disk status signal corresponding to the hard disk status pin; The target signal is demodulated to obtain the hard disk log data, and a monitoring task for the target hard disk is performed based on the hard disk log data.

2. The hard disk monitoring method according to claim 1, characterized in that: The hard disk out-of-band monitoring controller performs a first interactive operation with the target hard disk based on a two-line bidirectional communication mechanism; the first interactive operation is that the hard disk out-of-band monitoring controller sends pin configuration information to the target hard disk, and obtains the target signal output by the target hard disk after the target hard disk is configured accordingly according to the pin configuration information.

3. The hard disk monitoring method according to claim 1, wherein: When it is identified that the hard disk status signal in the target signal is a non-indication status signal or an invalid signal, and the current moment is the negotiation time period agreed upon with the target hard disk, the hard disk out-of-band monitoring controller performs a second interactive operation with the target hard disk based on a single-line bidirectional communication mechanism; the second interactive operation is that the hard disk out-of-band monitoring controller sends a reverse transmission request to the target hard disk, and when obtaining the permission signal of the target hard disk for the reverse transmission request, outputs the pin configuration information to the target hard disk.

4. The hard disk monitoring method according to claim 1, wherein: The initialization phase of the system startup controller includes: When the server is powered on, the system startup controller is used to detect the version numbers of the hard disk out-of-band monitoring controller and the hard disk to be monitored, and based on the version numbers, it is determined whether the hard disk out-of-band monitoring controller and the hard disk to be monitored both support the out-of-band monitoring function; If the system startup controller determines that both the hard disk out-of-band monitoring controller and the hard disk to be monitored support the out-of-band monitoring function, the hard disk to be monitored is used as the target hard disk, and the out-of-band monitoring functions of the hard disk out-of-band monitoring controller and the target hard disk are enabled, and information of the target hard disk is sent to the hard disk out-of-band monitoring controller, so that the hard disk out-of-band monitoring controller can obtain the hard disk log data of the target hard disk; If the hard disk out-of-band monitoring controller or the hard disk to be monitored does not support the out-of-band monitoring function, enabling the out-of-band monitoring function of the hard disk out-of-band monitoring controller and the hard disk to be monitored is prohibited.

5. The hard disk monitoring method according to claim 4, characterized in that: The system startup controller is constructed based on a unified extensible firmware interface or a basic input / output system, and the hard disk out-of-band monitoring controller includes a baseboard management controller and / or a complex programmable logic device.

6. The hard disk monitoring method according to claim 5, characterized in that: When the system startup controller is constructed based on the unified extensible firmware interface, the process of using the system startup controller to detect the version number of the hard disk out-of-band monitoring controller includes: In a driver execution environment phase of the system startup controller, using the system startup controller to send a target request configured to obtain a version number of the baseboard management controller and / or the complex programmable logic device to the baseboard management controller through an intelligent platform management interface; The system startup controller obtains the version number returned by the baseboard management controller after responding to the target request; wherein, the process of the baseboard management controller responding to the target request includes: the baseboard management controller reads the first version number corresponding to the baseboard management controller and / or reads the second version number corresponding to the complex programmable logic device from a first register configured to store version numbers according to the target request, and sends the read first version number and / or second version number to the system startup controller.

7. The hard disk monitoring method according to claim 6, characterized in that: Determining whether the hard disk out-of-band monitoring controller supports a data monitoring function based on the version number includes: Determine a first preset version number corresponding to the baseboard management controller, and if the first version number is not lower than the first preset version number, determine that the baseboard management controller supports the data monitoring function; wherein the first preset version number is the minimum version number of the baseboard management controller that supports the data monitoring function; And / or, determine a second preset version number corresponding to the complex programmable logic device; if the second version number is not lower than the second preset version number, determine that the complex programmable logic device supports the data monitoring function; wherein, the second preset version number is the lowest version number of the complex programmable logic device that supports the data monitoring function.

8. The hard disk monitoring method according to claim 6, characterized in that: Also includes: If the baseboard management controller does not read the first version number from the first register, or the system startup controller does not obtain the first version number sent by the baseboard management controller, the system startup controller detects whether there is a hard disk data display component on the web page interface of the baseboard management controller. If the hard disk data display component exists, it is determined that the baseboard management controller supports the out-of-band monitoring function.

9. The hard disk monitoring method according to claim 6, characterized in that: Also includes: If the baseboard management controller does not read the second version number from the first register, or the system startup controller does not obtain the second version number sent by the baseboard management controller, the system startup controller reads the code occupied memory size of the complex programmable logic device from the second register in the complex programmable logic device. If the code occupied memory size is the same as the code development size of the complex programmable logic device, it is determined that the complex programmable logic device supports the out-of-band monitoring function.

10. The hard disk monitoring method according to claim 5, characterized in that: When the system boot controller is constructed based on the unified extensible firmware interface, the process of using the system boot controller to detect the version number of the hard disk to be monitored includes: In the driver execution environment phase of the system startup controller, the system startup controller is used to poll all hard disks to be monitored to obtain the third version number, vendor identifier, and organization unique identifier corresponding to each hard disk to be monitored; Accordingly, determining whether the hard disk to be monitored supports the data monitoring function based on the version number includes: Determine whether the hard disk to be monitored supports a data monitoring function based on the third version number, the vendor identifier, and the organization unique identifier.

11. The hard disk monitoring method according to claim 10, characterized in that: The determining whether the hard disk to be monitored supports the data monitoring function based on the third version number, the vendor identifier, and the organization unique identifier includes: Determine a third preset version number corresponding to the hard disk to be monitored based on the supplier identifier and the organization unique identifier; the third preset version number is the minimum version number of the hard disk to be monitored that supports the data monitoring function; If the third version number is not lower than the third preset version number, and the format of the hard disk management log of the hard disk to be monitored is correct, it is determined that the hard disk to be monitored supports the data monitoring function.

12. The hard disk monitoring method according to claim 5, characterized in that: Also includes: When the system boot controller is constructed based on a unified extensible firmware interface, if a function configuration modification instruction regarding the hard disk out-of-band monitoring controller and / or the target hard disk is obtained from a user through a first user interface during a boot device selection phase of the system boot controller, or if a function configuration modification instruction regarding the hard disk out-of-band monitoring controller and / or the target hard disk is obtained from a user through a second user interface during an early stage of operating system loading of the system boot controller, the hard disk out-of-band monitoring controller and / or the target hard disk are modified and configured using the obtained function configuration modification instruction; After detecting that the first user interface or the second user interface is closed, detecting, by the system startup controller, whether the functional configuration states of the hard disk out-of-band monitoring controller and the out-of-band monitoring function of the target hard disk are consistent; the functional configuration state includes an on state and a off state; If the functional configuration status of the hard disk out-of-band monitoring controller and the out-of-band monitoring function of the target hard disk are inconsistent, the obtained functional configuration modification instruction is determined to be an invalid instruction, and the modified configuration of the hard disk out-of-band monitoring controller and / or the target hard disk is cleared.

13. The hard disk monitoring method according to claim 12, characterized in that: The first user interface and the second user interface are configured to display whether the current hard disk out-of-band monitoring controller and the current target hard disk support the out-of-band monitoring function, and whether the current hard disk out-of-band monitoring controller and the current target hard disk have enabled the out-of-band monitoring function.

14. The hard disk monitoring method according to claim 4, characterized in that: Also includes: The driver is installed by the system startup controller when the operating system is started. If the operating system obtains a function configuration modification instruction regarding the hard disk out-of-band monitoring controller and / or the target hard disk sent by the user through the terminal, the hard disk out-of-band monitoring controller and / or the target hard disk are modified based on the obtained function configuration modification instruction; After detecting that the terminal is closed, detecting, by the driver, whether the functional configuration states of the hard disk out-of-band monitoring controller and the out-of-band monitoring function of the target hard disk are consistent; the functional configuration state includes an on state and a off state; If the functional configuration status of the hard disk out-of-band monitoring controller and / or the out-of-band monitoring function of the target hard disk is inconsistent, the obtained functional configuration modification instruction is determined to be an invalid instruction, and the modified configuration of the hard disk out-of-band monitoring controller and / or the target hard disk is cleared.

15. The hard disk monitoring method according to any one of claims 1 to 14, characterized in that: The hard disk out-of-band monitoring controller is a baseboard management controller; Accordingly, the monitoring task of the target hard disk based on the hard disk log data includes: Displaying the hard disk log data on the target interface; A corresponding preset threshold condition is determined based on the type of the hard disk log data, and it is judged whether the hard disk log data meets the preset threshold condition. If not, an early warning prompt is issued.

16. The hard disk monitoring method according to any one of claims 1 to 14, characterized in that: The hard disk out-of-band monitoring controller includes a baseboard management controller and a complex programmable logic device; Accordingly, the monitoring task of the target hard disk based on the hard disk log data includes: After obtaining the hard disk log data output by the target hard disk through the hard disk status pin, sending an interrupt signal to the baseboard management controller through the complex programmable logic device and using the first target bus; Responding to the interrupt signal through the baseboard management controller and sending a data read request to the complex programmable logic device through a second target bus, so that the complex programmable logic device sends the hard disk log data to the baseboard management controller; The baseboard management controller displays the hard disk log data on the target interface and issues an early warning when the hard disk log data does not meet a preset threshold condition; the preset threshold condition is a threshold condition corresponding to the type of the hard disk log data.

17. A server, characterized in that: Includes hard disk out-of-band monitoring controller and system startup controller; The hard disk out-of-band monitoring controller is configured to determine a target hard disk from the hard disks and send pin configuration information to the target hard disk; the target hard disk is a hard disk with an out-of-band monitoring function detected by the system startup controller during the initialization phase, and the pin configuration information includes an identifier of a hard disk status pin configured to indicate an output target signal in the target hard disk, and configuration parameters configured to configure a signal modulation process of the target hard disk based on hard disk log data and a hard disk status signal corresponding to the hard disk status pin; The target hard disk is configured to output the target signal to the hard disk out-of-band monitoring controller after being configured accordingly according to the pin configuration information, so that the hard disk out-of-band monitoring controller demodulates the target signal to obtain the hard disk log data, and performs the monitoring task of the target hard disk based on the hard disk log data.

18. A hard disk monitoring device, characterized in that: Applicable to hard disk out-of-band monitoring controllers, including: A hard disk determination module is configured to determine a target hard disk; the target hard disk is a hard disk with an out-of-band monitoring function and connected to the hard disk out-of-band monitoring controller detected by the system startup controller during the initialization phase; a configuration module configured to send pin configuration information to the target hard disk and obtain a target signal output by the target hard disk after the target hard disk is configured accordingly according to the pin configuration information; the pin configuration information includes an identifier configured to indicate a hard disk status pin in the target hard disk that outputs the target signal, and configuration parameters configured to configure a signal modulation process of the target hard disk based on hard disk log data and the hard disk status signal corresponding to the hard disk status pin; The monitoring module is configured to demodulate the target signal to obtain the hard disk log data, and perform a monitoring task on the target hard disk based on the hard disk log data.

19. An electronic device, characterized in that: include: a memory configured to store a computer program; The processor is configured to execute the computer program to implement the steps of the hard disk monitoring method according to any one of claims 1 to 16.

20. A computer-readable non-volatile storage medium, characterized in that: It is configured to store a computer program; wherein, when the computer program is executed by a processor, the steps of the hard disk monitoring method according to any one of claims 1 to 16 are implemented.

Citation Information

Patent Citations

  • Condition monitoring system of solid state disk

    CN103176883A

  • Hard disk inspection method, device and system

    CN112527594A

  • Performance monitoring method and device for solid state disk, equipment and medium

    CN117472690A

  • Hard disk management method and device, computer readable storage medium and electronic equipment

    CN117632637A

  • Server, hard disk monitoring method and device thereof, equipment and medium

    CN117992311A