Hard disk management system, method and device
Through the perception module, the hard disk insertion attribute information is detected and naming rules are constructed, which solves the problem of slow positioning during hard disk replacement, and achieves rapid fault location and intuitive understanding of hard disk parameters.
Patent Information
- Application Number
- CN202510724493.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-30
- Publication Date
- 2025-08-12
AI Technical Summary
In the prior art, the physical location and logical identification need to be cross-compared when replacing the hard disk, resulting in a longer fault processing time.
The perception module detects the attribute information when the hard disk is inserted, and uses naming rules to build the hard disk name, including physical location coordinates and hardware information, to realize dynamic naming.
Quickly locate the hard disk fault location, shorten the fault handling time, adapt to hard disk replacement scenarios, and facilitate operators to understand hard disk parameters.
Smart Images
Figure CN120469841A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of server hard disk management, and in particular to a hard disk management system, method, and device. Background Art
[0002] In the operation and maintenance management of server systems, the hard disk is the core data storage unit, and its effective management is directly related to the reliability of system operation.
[0003] Server systems often contain multiple hard drives of different types. To distinguish them, they are typically named. Traditionally, hard drives are named using generic serial numbers or manufacturer-preset names. This traditional naming scheme requires operators to cross-check physical locations with logical identifiers when replacing a hard drive, increasing troubleshooting time.
[0004] It can be seen that how to achieve fast positioning of a hard disk is a problem that needs to be solved by those skilled in the art. Summary of the Invention
[0005] The present application provides a hard disk management system, method and device to at least solve the problem of slow hard disk positioning in the related art.
[0006] This application provides a hard disk management system, including a perception module and a processing module; The sensing module is connected to the processing module and is used to detect when a hard disk is inserted, obtain the attribute information of the hard disk, and transmit the backplane signal containing the attribute information to the processing module; The processing module is used to receive the backplane signal transmitted by the sensing module; analyze the backplane signal according to the set naming rules to determine the naming information of the hard disk; wherein the naming information includes the physical location coordinates and hardware information; and construct the name of the hard disk based on the naming information.
[0007] This application also provides a hard disk management method, which is applicable to the above-mentioned hard disk management system, and the method includes: Receive the backplane signal transmitted by the sensing module; wherein the backplane signal includes the attribute information of the hard disk; the attribute information is obtained when the sensing module detects that the hard disk is inserted; Analyze the backplane signal according to the set naming rules to determine the naming information of the hard disk; wherein the naming information includes the physical location coordinates and hardware information; Constructs the name of the hard disk based on the naming information.
[0008] The present application also provides a hard disk management device, which is applicable to the above-mentioned hard disk management system, and the device includes a receiving unit, an analyzing unit and a constructing unit; A receiving unit, configured to receive a backplane signal transmitted by the sensing module; wherein the backplane signal includes attribute information of the hard disk; the attribute information is obtained when the sensing module detects that the hard disk is inserted; An analysis unit, configured to analyze the backplane signal according to a set naming rule to determine the naming information of the hard disk; wherein the naming information includes physical location coordinates and hardware information; A building block used to construct a hard disk name based on the naming information.
[0009] The present application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for implementing the steps of any of the above-mentioned hard disk management methods when executing the computer program.
[0010] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned hard disk management methods are implemented.
[0011] The present application also provides a computer program product, including a computer program, which implements the steps of any of the above-mentioned hard disk management methods when executed by a processor.
[0012] According to the present application, when the sensing module detects the insertion of a hard drive, it obtains the hard drive's attribute information and transmits a backplane signal containing the attribute information to the processing module. Since the attribute information includes the hard drive's insertion position and some general hard drive parameter information, and the naming rules record the naming information required to construct the hard drive name and the method for extracting this naming information, the processing module, upon receiving the backplane signal transmitted by the sensing module, analyzes the backplane signal based on the naming rules to obtain the naming information required to construct the hard drive name. The naming information can include physical location coordinates and hardware information. The hard drive name can be constructed based on the naming information. This application dynamically names the hard drive upon insertion, making it well suited for hard drive replacement scenarios. By setting naming rules, standardized management of hard drive names is ensured. The naming information includes physical location coordinates that reflect the actual location of the hard drive. When a hard drive fails, operators can quickly locate the hard drive's physical location based on the hard drive name, effectively reducing hard drive failure processing time. Furthermore, the naming information includes hardware information, ensuring that the hard drive name can be adaptively adjusted after replacing a hard drive in the same insertion position and facilitating intuitive understanding of the hard drive's general parameters. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0014] Figure 1 A schematic diagram of the structure of a hard disk management system provided in an embodiment of the present application; Figure 2 A schematic diagram of a hierarchical collaborative architecture of a hard disk management system provided in an embodiment of the present application; Figure 3 A flowchart of a hard disk management method provided in an embodiment of the present application; Figure 4 A structural diagram of a hard disk management device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0015] The following will be combined with the accompanying 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 them. 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.
[0016] It should be noted that, in the description of this application, the terms "comprises," "includes," 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. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.
[0017] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.
[0018] Next, a hard disk management system provided by an embodiment of the present application is described in detail. Figure 1 This is a structural diagram of a hard disk management system provided in an embodiment of the present application. The system includes a sensing module 11 and a processing module 12.
[0019] The sensing module 11 is connected to the processing module 12 and is used to detect that a hard disk is inserted, obtain the attribute information of the hard disk, and transmit the backplane signal containing the attribute information to the processing module 12 .
[0020] The attribute information of a hard disk may include the hard disk insertion location, hard disk type, hard disk manufacturer information, serial number, etc. In the embodiment of the present application, the attribute information to be obtained can be determined based on the naming information required for the hard disk naming. For example, if the naming information includes physical location coordinates, the attribute information of the hard disk insertion location needs to be obtained.
[0021] The backplane signal can be in a signal format recognizable by the processing module 12. After acquiring the hard drive attribute information, the sensing module 11 can convert the attribute information into a backplane signal based on a signal format recognizable by the processing module, thereby transmitting the backplane signal to the processing module 12. It should be noted that if the processing module 12 can directly recognize the attribute information, no conversion is required, and the attribute information can be directly transmitted to the processing module 12 as a backplane signal.
[0022] The processing module 12 is used to receive the backplane signal transmitted by the sensing module 11; analyze the backplane signal according to the set naming rules to determine the naming information of the hard disk; wherein the naming information includes the physical location coordinates and hardware information; and construct the name of the hard disk based on the naming information.
[0023] The naming rule can record the naming information required to construct the hard disk name and the method of extracting the naming information. The naming rule can be pre-set by the administrator and built into the processing module 12.
[0024] In the embodiment of the present application, in order to quickly locate the actual physical location of the hard disk according to the hard disk name, the naming rule may include a method of extracting the physical location coordinates. The physical location coordinates reflect the actual physical location of the hard disk.
[0025] Hardware names are constructed based on physical coordinate locations, ensuring a strong correlation between the names and physical locations. When a hardware failure occurs, maintenance personnel can quickly locate the problematic hard drive, shortening the mean time to repair. This approach is particularly suitable for large-scale maintenance scenarios involving high-density storage servers.
[0026] To ensure that hard drive names intuitively reflect their performance, hard drive names can be based not only on physical location coordinates but also on hardware information. This hardware information can include any one or any combination of drive type, capacity, rotation speed, manufacturer information, and serial number. In addition to this hardware information, new information can be added based on naming requirements. Automatic name updates based on drive status (such as failure or warning) can be supported, for example, changing the name of a faulty hard drive to "_Fault" (suffix).
[0027] It should be noted that the hard disk management system provided in the embodiment of the present application can be applied to network cards, graphics processing units (GPUs), power modules, etc., to achieve unified naming management of all hardware in the server.
[0028] As can be seen from the above technical solution, the hard drive management system includes a sensing module and a processing module. The sensing module is connected to the processing module and is used to detect the insertion of a hard drive, obtain the hard drive's attribute information, and transmit a backplane signal containing the attribute information to the processing module. Since the attribute information includes the hard drive's insertion position and some general parameters of the hard drive, the naming rules record the naming information required to construct the hard drive name and the method for extracting this naming information. Therefore, after receiving the backplane signal transmitted by the sensing module, the processing module analyzes the backplane signal based on the naming rules to obtain the naming information required to construct the hard drive name. The naming information can include physical location coordinates and hardware information. The name of the hard drive can be constructed based on the naming information. This application dynamically names the hard drive when it is inserted, which is well suited for hard drive replacement scenarios. By setting naming rules, standardized management of each hard drive name is ensured. The naming information includes physical location coordinates that reflect the actual location of the hard drive. When a hard drive fails, the operator can quickly locate the physical location of the hard drive based on the hard drive name, effectively shortening the hard drive failure processing time. The naming information also includes hardware information, which ensures that the hard disk name can be adaptively adjusted after the hard disk is replaced in the same insertion position, and facilitates operators to intuitively understand some general parameters of the hard disk.
[0029] In the embodiment of the present application, according to the functions that the processing module 12 needs to implement, the processing module 12 may include a position encoder 121, a feature extraction engine 122 and a naming rule interpreter 123.
[0030] The position encoder 121 is used to parse the backplane signal to determine the physical position coordinates of the hard disk.
[0031] In practical applications, the physical location coordinates of a hard drive can be uniquely identified by the chassis number (C), cage number (B), and slot number (S). In other words, the physical location coordinates can include the chassis number, cage number, and slot number.
[0032] The motherboard's chassis number is factory-set, and position encoder 121 can directly obtain the chassis number of the motherboard where the hard drive resides. After receiving the backplane signal transmitted by sensing module 11, position encoder 121 can determine the hard drive's cage number and slot number based on the hard drive's insertion position contained in the backplane signal. The physical location coordinates are then derived by sequentially combining the chassis number, cage number, and slot number.
[0033] The feature extraction engine 122 is used to obtain the hard disk type contained in the backplane signal; and query the parameter information of the hard disk using the protocol corresponding to the hard disk type.
[0034] Different hard drive types use different protocols to query key parameters. If the hard drive is a serial connection drive, feature extraction engine 122 responds to storage protocol instructions to obtain hard drive parameter information. If the hard drive is a non-volatile storage medium, feature extraction engine 122 obtains hard drive parameter information through a management interface. This parameter information may include hard drive capacity.
[0035] There are many types of hard drives, such as serial attached hard drives (SATA / SAS) and non-volatile memory express (NVMe).
[0036] For SATA / SAS hard drives, you can use specialized computer hard drive interface standard commands (Advanced Technology Attachment, ATA) and Small Computer System Interface (SCSI) to obtain the hard drive capacity. For NVMe hard drives, you can read the hard drive capacity through the management interface.
[0037] The naming rule interpreter 123 is used to combine the physical location coordinates, hard disk type and parameter information to generate a hard disk name.
[0038] In order to standardize hard disk names, the naming rule interpreter 123 may convert raw data obtained from different interfaces into a unified attribute format, including standardized capacity, storage type, and the like.
[0039] Among them, standardized capacity can convert hard disk capacity into a value in terabytes (TB) or gigabytes (GB).
[0040] Storage types include solid-state drives (SSDs), hard disk drives (HDDs), and non-volatile memory express (NVMe). SATA and SAS mentioned above are both solid-state drives.
[0041] Taking the combination of physical location coordinates (location), hard disk capacity (capacity), and storage type (type) to generate a hardware name as an example, the user's preset naming pattern is as follows: {location}_{capacity}TB_{type}. The generated hardware name can be: C1-B2-S3_4TB_NVMe.
[0042] In addition, for mechanical hard disks, the parameter information obtained can also include the rotational speed, and the rotational speed information can be included in the name. For example, HDD_7200 indicates a mechanical hard disk with a rotational speed of 7200.
[0043] In an embodiment of the present application, in order to achieve persistence of the name, the user-defined name can be stored in a non-volatile memory to ensure that it is not lost during a power outage.
[0044] The naming rule interpreter 123 can pre-store naming rules preset by the user; in the absence of a custom name set by the user, the hard disk capacity is converted into a standard capacity according to the capacity unit contained in the naming rule; the hard disk type is converted into a corresponding target storage type according to the storage type corresponding to each hard disk type contained in the naming rule; according to the naming format contained in the naming rule, the physical location coordinates, standard capacity, and target storage type are combined to generate the name of the hard disk; in the presence of a custom name set by the user, the custom name is used as the name of the hard disk.
[0045] The hard disk management system provided in this application can realize hot-swap synchronization and automatically inherit the original slot naming rules when the hard disk is replaced.
[0046] In actual applications, to keep hard disk names concise, you can use intelligent abbreviations for storage types. For example, NVMe is abbreviated as N, and HDD_7200 is abbreviated as H7.
[0047] In an embodiment of the present application, by combining the physical location coordinates of the hard drive, the hard drive capacity, and the storage type to generate a hardware name, the administrator can directly determine key information such as the hard drive's physical location, capacity, and storage type based on the hard drive's name without relying on additional query tools, significantly improving operational efficiency and reducing human error. Furthermore, a hot-swap synchronization mechanism can be implemented, with the system responding to hard drive hot-swap events in real time and automatically updating naming information to ensure that the hardware name is strictly synchronized with the actual hardware status. When a hard drive is replaced, the new hard drive can inherit the naming rules of the original slot and intelligently adjust the capacity difference prompt to ensure naming continuity.
[0048] It should be noted that, in the embodiment of the present application, the information contained in the hard disk name can be flexibly set. The above-mentioned naming of the hard disk based on the physical location coordinates, hard disk capacity and storage type is only one feasible implementation method.
[0049] In practical applications, the hardware name can be backed up in both non-volatile memory and the hard disk itself, and a cyclic redundancy check (CRC) mechanism can be used to ensure data reliability and avoid information loss due to single point failures.
[0050] In the embodiment of the present application, in order to realize the functions required by the sensing module 11, the sensing module 11 may include a hard disk backplane 111 and a baseboard management controller (BMC) 112. The attribute information may include the hard disk insertion position and hard disk type.
[0051] In actual applications, the hard disk backplane 111 is connected to the baseboard management controller 112 to obtain the hard disk insertion position of the hard disk and transmit the hard disk insertion position to the baseboard management controller 112 .
[0052] The baseboard management controller 112 is used to obtain the hard disk type through the serial bus; receive the hard disk insertion position transmitted by the hard disk backplane 111; convert the hard disk insertion position and hard disk type into a backplane signal, and transmit the backplane signal to the processing module 12.
[0053] The hard disk insertion position may include physical slot information. In order to identify whether the hard disk is effectively inserted, the hard disk backplane 111 may obtain a slot status signal and physical slot information, and transmit the slot status signal and physical slot information to the baseboard management controller 112.
[0054] When receiving the slot status signal and physical slot information transmitted by the hard disk backplane 111, the baseboard management controller 112 sends an in-place test command to the hard disk; when receiving the in-place response signal fed back from the hard disk within the set time, it determines that the hard disk is effectively inserted; when not receiving the in-place response signal fed back from the hard disk within the set time, it determines that the hard disk is invalidly inserted; when the hard disk is effectively inserted, the operation of converting the hard disk insertion position and hard disk type into backplane signals is executed.
[0055] The set time may be set according to the time of a single interaction between the hard disk and the baseboard management controller 112 .
[0056] In the embodiment of the present application, the baseboard management controller 112 can ensure the effectiveness of the insertion action by testing the insertion of the hard disk, thereby avoiding hard disk insertion recognition errors caused by signal interference.
[0057] It should be noted that the processing module 12 can be a software module deployed on the baseboard management controller 112 or deployed on other chips. The chip deployed with the processing module 12 is connected to the baseboard management controller 112 to achieve interaction with the baseboard management controller 112.
[0058] In this embodiment of the present application, to further improve the acquired attribute information, the sensing module 11 may further include a field replaceable unit (FRU) 113. The FRU 113 is connected to the hard drive backplane 111 and the baseboard management controller 112, respectively, and is configured to acquire the hard drive manufacturer information and serial number through the hard drive backplane 111 and transmit the hard drive manufacturer information and serial number to the baseboard management controller 112.
[0059] The baseboard management controller 112 receives the manufacturer information and serial number of the hard disk transmitted by the field replaceable chip 113 and can convert the hard disk insertion position, hard disk type, manufacturer information and serial number of the hard disk into a backplane signal.
[0060] In the embodiment of the present application, the naming information required for naming the hard disk can be varied and can be flexibly set based on actual needs.
[0061] For example, you can name a hard disk based on its physical location coordinates, hard disk capacity, manufacturer information (unit_vendor), and serial number (serial).
[0062] Example template: "{location}_{capacity}{unit}_{vendor}-{serial_last4}"; Generates the result: "C1B2S3_4TB_Samsung-3F2A".
[0063] Considering that hard drive manufacturers are relatively fixed, a mapping table of manufacturer names and abbreviations can be pre-established. After obtaining the manufacturer name, the mapping table can be directly queried to determine its corresponding abbreviation. For example, Samsung is abbreviated as Sam.
[0064] In addition to abbreviating the manufacturer name, you can also configure interception rules for the serial number.
[0065] In the embodiment of the present application, by abbreviating the manufacturer name and truncating the serial number, the length of the hard disk name can be effectively controlled, ensuring the simplicity and good readability of the hard disk name.
[0066] In order to facilitate unified management of hard disk names and support dynamic adjustment of hard disk names, the hard disk management system further includes an interaction module 13 ; the interaction module 13 is connected to the processing module 12 and is used to perform read and write operations on the hard disk names.
[0067] The interaction module 13 may include a webpage submodule 131 , an interface submodule 132 and a command submodule 133 .
[0068] The webpage submodule 131, the interface submodule 132 and the command submodule 133 are three parallel submodules that can obtain the same data and achieve the same purpose. The user can operate the hard disk name through any of the three submodules.
[0069] In actual applications, the webpage submodule 131 may generate an editable name table so that the user can modify the names contained in the name table.
[0070] In practical applications, the webpage submodule 131 can dynamically generate an editable name table based on the Vue.js component, a JavaScript framework for building user interfaces. The implementation technology for dynamically generating an editable name table includes real-time asynchronous storage, front-end verification of name uniqueness, and generation of modification record audit logs.
[0071] The webpage submodule 131 may adopt a web user interface (Web UI), ie, a web interface.
[0072] Users can modify hardware names through the Web UI. For example, if the processing module is encapsulated in the BMC, users can access the editable name table through the Web UI. To modify the name, they can edit the new name in the table and send a PATCH request to the BMC through the Web UI. The BMC writes the new name to non-volatile memory. After successful storage, the BMC returns a success response to the Web UI, which then displays the updated results.
[0073] The interface submodule 132 may provide an access interface to facilitate users to obtain the name of the hardware.
[0074] The interface submodule 132 may use an extensible platform management application (Redfish API).
[0075] The Redfish API provides a PATCH interface for the / redfish / v1 / Chassis / {id} / Drives resource.
[0076] The command submodule 133 is configured to execute read and write operations on the hard disk name according to the name read and write command input by the user.
[0077] The command submodule 133 may use an Intelligent Platform Management Interface (IPMI) command line. IPMI command extension: A new 0x3A subcommand is added for name read and write operations.
[0078] The interactive module 13 can provide a name template function, allowing users to quickly generate a name by selecting a preset template (such as "Data_XX" or "Backup_XX"). The modification history of the hard disk name is saved to facilitate user backtracking and recovery.
[0079] In this embodiment, an operating system-independent interaction module is implemented to support user-defined names through the BMC web interface, IPMI command line, or Redfish interface, enabling out-of-band management. This allows enterprises to configure naming rule templates based on their needs (e.g., adding fields such as department and purpose) to meet diverse management requirements. Furthermore, the hard disk management system is implemented based on the existing BMC architecture, and through extended IPMI commands and standardized Redfish interfaces, it is seamlessly compatible with the mainstream server management ecosystem.
[0080] In the embodiment of the present application, a security mechanism can be set up to ensure the security of the hardware name. When a user modifies the hard disk name through the interactive module 13, the user's identity can be first authenticated. To achieve secure authentication of the user's identity, a security authentication process can be deployed within the processing module 12, and the user's identity information and the corresponding access rights of each user can be pre-recorded in the memory connected to the processing module 12. The access rights may include read permission, write permission, modify permission, delete permission, etc.
[0081] When the interaction module 13 sends an operation request to the processing module 12, it may include user identity information. The processing module 12 then matches the received user identity information with the user identity information stored in the memory. If the memory contains user identity information that matches the user identity information carried in the operation request, the user may be granted access rights corresponding to the matching user identity information.
[0082] In the embodiment of the present application, by authenticating the user's identity, the security of the hard disk name is guaranteed, preventing unauthorized users from maliciously modifying the customized hardware name. Furthermore, setting access rights for different users can better meet the management needs of different users and effectively reduce the possibility of unauthorized users making mistakes.
[0083] Figure 2 This is a schematic diagram of a hierarchical collaborative architecture of a hard disk management system provided in an embodiment of the present application. The hard disk management system includes a perception module 11, a processing module 12, and an interaction module 13. The perception module 11 includes a hard disk backplane 111, a baseboard management controller 112, and a field replaceable chip 113. The processing module 12 includes a position encoder 121, a feature extraction engine 122, and a naming rule interpreter 123. The interaction module 13 includes a webpage submodule 131, an interface submodule 132, and a command submodule 133.
[0084] Figure 2 The hard drive management system in the system adopts a layered collaborative architecture, forming a complete data path from the hardware perception layer to the data processing layer and the interaction layer. The hard drive backplane 111 in the hardware perception layer detects hard drive insertion and collects slot status signals and physical slot information. The hard drive backplane 111 can communicate with the baseboard management controller 112 via the Serial Port Interface (SGPIO) bus used for backplane signal transmission. The hard drive backplane 111 can include a built-in field programmable gate array (FPGA). The FPGA slot pre-processes the slot status signals and physical slot information before transmitting them to the baseboard management controller 112. Pre-processing involves converting the data into a format recognizable by the baseboard management controller 112. The hard drive backplane 111 communicates with the field replaceable chip 113 via a serial bus, namely the I2C bus. The field replaceable chip 113 can obtain the hard drive manufacturer information and serial number from the hard drive backplane 111 and transmit the hard drive manufacturer information and serial number to the baseboard management controller 112.
[0085] The data processing layer can be implemented in the BMC firmware. The position encoder 121, feature extraction engine 122 and naming rule interpreter 123 included in the data processing layer can exchange data through shared memory.
[0086] Taking the naming format of "chassis number-cage number-slot number_capacity_storage type" as an example, the location encoder 121 can uniquely identify the physical location of the hard drive by obtaining the chassis number, cage number, and slot number. The feature extraction engine 122 can combine the obtained hard drive capacity and storage type into a feature identifier. The naming rule interpreter 123 can combine the chassis number, cage number, slot number, hard drive capacity, and storage type according to the naming format to generate the final hardware name, such as C1-B2-S3_4TB_SSD.
[0087] The interaction layer provides a multi-channel management interface. The WebUI engine in the webpage submodule 131 dynamically renders editable name lists based on Vue.js components. The interface submodule 132 responds to automation tool calls via the Redfish RESTful interface. The command submodule 133 handles command line interface (CLI) operations via the IPMI extended command channel.
[0088] In this embodiment of the present application, all name modification operations are subject to permission verification and are ultimately written synchronously to non-volatile memory and the hard disk SMART log area by the persistence service, forming a dual backup. To ensure the readability of the hardware name, the use of special characters such as & and % can be restricted when the user modifies the hard disk name. In addition to modifying the hardware name, users can also expand custom fields, such as adding project numbers, operation and maintenance tags, etc.
[0089] Considering that in actual applications, hardware name conflicts may occur after the user modifies the hardware name, in this case, a location suffix can be added to resolve the name conflict.
[0090] When a hot-swap event is triggered, the interrupt service routine notifies each module to update through the event bus to ensure that the naming status is strictly synchronized with the physical device.
[0091] The hard disk management system adopts a layered decoupling design, which not only ensures real-time performance but also supports flexible rule configuration and cross-platform expansion.
[0092] In this embodiment, the generated hardware name can be written to three locations simultaneously: first, it is stored in the BMC's non-volatile memory to ensure it is not lost during a power outage; then, the name mapping table in memory is updated to improve access speed; and finally, it is synchronized to the hard disk's own storage area via the management bus. The system can generate a checksum for each name record and maintain a modification log.
[0093] The hard disk management system provided in the embodiment of the present application can be combined with disk array (Redundant Arrays of Independent Disks, RAID) management: in the RAID array, a name is assigned to each hard disk to facilitate the identification and management of the hard disks in the array. Combined with storage virtualization: in a storage virtualization environment, names are assigned to virtual hard disks to improve the management efficiency of virtual storage resources. Combined with AI operation and maintenance: Customized hard disk names are combined with AI operation and maintenance systems to achieve intelligent monitoring and early warning of hard disk status. Hardware value-added services: The customized hard disk name function is used as a value-added service for server hardware to enhance product competitiveness. Enterprise customization: Provide customized hard disk naming solutions for corporate customers to meet specific industry needs (such as finance and the Internet).
[0094] Figure 3 The flowchart of a hard disk management method provided in an embodiment of the present application is applicable to the above-mentioned hard disk management system. The method includes:
[0095] S301: Receive a backplane signal transmitted by a sensing module.
[0096] The backplane signal includes the attribute information of the hard disk; the attribute information is obtained when the sensing module detects that the hard disk is inserted.
[0097] S302: Analyze the backplane signal according to the set naming rule to determine the naming information of the hard disk.
[0098] The naming information includes physical location coordinates and hardware information.
[0099] S303: Construct a name for the hard disk based on the naming information.
[0100] In some embodiments, analyzing the backplane signal according to a set naming rule to determine the naming information of the hard disk, and constructing the name of the hard disk based on the naming information includes: Analyze the backplane signal to determine the physical location coordinates of the hard drive; Get the hard disk type contained in the backplane signal; use the protocol corresponding to the hard disk type to query the hard disk parameter information; The physical location coordinates, hard disk type, and parameter information are combined to generate the hard disk name.
[0101] In some embodiments, the physical location coordinates include a chassis number, a cage number, and a slot number; Parsing the backplane signal to determine the physical location coordinates of the hard drive includes: Obtain the chassis number of the motherboard where the hard drive is located; determine the cage number and slot number of the hard drive based on the hard drive insertion position contained in the backplane signal; and obtain the physical location coordinates by combining the chassis number, cage number, and slot number in that order; Querying the hard disk parameter information using the protocol corresponding to the hard disk type includes: If the hard disk is a serial connection hard disk, obtaining hard disk parameter information in response to a storage protocol instruction; if the hard disk is a non-volatile storage medium, obtaining hard disk parameter information through a management interface; wherein the parameter information includes hard disk capacity; The physical location coordinates, hard disk type, and parameter information are combined to generate the hard disk name, including: Pre-store user-preset naming rules; if there is no user-set custom name, convert the hard disk capacity to standard capacity according to the capacity unit included in the naming rule; convert the hard disk type to the corresponding target storage type according to the storage type corresponding to each hard disk type included in the naming rule; according to the naming format included in the naming rule, combine the physical location coordinates, standard capacity, and target storage type to generate the hard disk name; if there is a user-set custom name, use the custom name as the hard disk name.
[0102] For descriptions of features in the embodiment corresponding to the hard disk management method, reference may be made to the relevant descriptions of the embodiment corresponding to the hard disk management system, which will not be detailed here.
[0103] As can be seen from the above technical solution, the processing module can receive a backplane signal transmitted by the sensing module. This backplane signal contains hard drive attribute information. This attribute information is obtained by the sensing module when it detects a hard drive insertion. Since the attribute information includes the hard drive's insertion position and some general hard drive parameter information, and the naming rules record the naming information required to construct the hard drive name and the method for extracting this naming information, the processing module can analyze the backplane signal based on the naming rules to obtain the naming information required to construct the hard drive name. The naming information can include physical location coordinates and hardware information. The hard drive name can be constructed based on the naming information. This application dynamically names the hard drive upon insertion, which is well suited for hard drive replacement scenarios. By setting a naming rule, standardized management of each hard drive name is ensured. The naming information includes physical location coordinates that reflect the actual location of the hard drive. When a hard drive fails, the operator can quickly locate the physical location of the hard drive based on the hard drive name, effectively shortening the hard drive failure processing time. The naming information also includes hardware information, ensuring that the hard drive name can be adaptively adjusted after replacing a hard drive in the same insertion position and facilitating the operator's intuitive understanding of some of the hard drive's general parameters.
[0104] Figure 4 This is a structural diagram of a hard disk management device provided in an embodiment of the present application, which is applicable to the above-mentioned hard disk management system. The device includes a receiving unit 41, an analyzing unit 42 and a constructing unit 43.
[0105] The receiving unit 41 is used to receive the backplane signal transmitted by the sensing module; wherein the backplane signal includes the attribute information of the hard disk; the attribute information is obtained when the sensing module detects that the hard disk is inserted.
[0106] The analysis unit 42 is configured to analyze the backplane signal according to a set naming rule to determine the naming information of the hard disk; wherein the naming information includes physical location coordinates and hardware information.
[0107] The construction unit 43 is configured to construct a name of the hard disk based on the naming information.
[0108] In some embodiments, the analysis unit includes a parsing subunit, an acquisition subunit, and a query subunit; The parsing subunit is used to parse the backplane signal to determine the physical location coordinates of the hard disk; The acquisition subunit is used to obtain the hard disk type contained in the backplane signal; A query subunit, used to query parameter information of the hard disk using a protocol corresponding to the hard disk type; A construction unit used to combine the physical location coordinates, hard disk type, and parameter information to generate a hard disk name.
[0109] In some embodiments, the physical location coordinates include a chassis number, a cage number, and a slot number; The parsing subunit is used to obtain the chassis number of the motherboard where the hard disk is located; determine the cage number and slot number of the hard disk according to the hard disk insertion position contained in the backplane signal; and obtain the physical location coordinates by combining the chassis number, cage number and slot number in sequence; a query subunit, configured to obtain hard disk parameter information in response to a storage protocol instruction when the hard disk is a serial connection hard disk; and to obtain hard disk parameter information through a management interface when the hard disk is a non-volatile storage medium; wherein the parameter information includes hard disk capacity; A construction unit is used to pre-store a naming rule preset by the user; in the absence of a custom name set by the user, convert the hard disk capacity into a standard capacity according to the capacity unit included in the naming rule; convert the hard disk type into a corresponding target storage type according to the storage type corresponding to each hard disk type included in the naming rule; according to the naming format included in the naming rule, combine the physical location coordinates, standard capacity, and target storage type to generate a name for the hard disk; in the absence of a custom name set by the user, use the custom name as the name of the hard disk.
[0110] For the description of the features in the embodiment corresponding to the hard disk management device, please refer to the relevant description of the embodiment corresponding to the hard disk management method, and no further details will be given here.
[0111] As can be seen from the above technical solution, the receiving unit can receive the backplane signal transmitted by the sensing module. This backplane signal contains the hard drive's attribute information. The attribute information is obtained by the sensing module when the hard drive is inserted. Since the attribute information includes the hard drive's insertion position and some general hard drive parameter information, and the naming rules record the naming information required to construct the hard drive name and the method for extracting this naming information, the analysis unit can obtain the naming information required to construct the hard drive name by analyzing the backplane signal based on the naming rules. The naming information can include physical location coordinates and hardware information. The construction unit can construct the hard drive name based on the naming information. This application dynamically names the hard drive upon insertion, which is well suited for hard drive replacement scenarios. By setting a naming rule, standardized management of each hard drive name is ensured. The naming information includes physical location coordinates that reflect the actual location of the hard drive. When a hard drive fails, the operator can quickly locate the hard drive's physical location based on the hard drive name, effectively shortening the hard drive failure processing time. The naming information also includes hardware information, ensuring that the hard drive name can be adaptively adjusted after replacing a hard drive in the same insertion position and facilitating the operator's intuitive understanding of the hard drive's general parameters.
[0112] Through the description of the above implementation methods, those skilled in the art can clearly understand that the system according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method.
[0113] An embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any of the above-mentioned hard disk management method embodiments.
[0114] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above-mentioned hard disk management method embodiments when running.
[0115] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.
[0116] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any of the above-mentioned hard disk management method embodiments are implemented.
[0117] An embodiment of the present application also provides another computer program product, including a non-volatile computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the steps in any of the above-mentioned hard disk management method embodiments.
[0118] Professionals 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 components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0119] The above is a detailed introduction to the hard disk management system, method, and device provided by the present application. This article uses specific examples to illustrate the principles and implementation methods of the present application. The description of the above examples is only intended to help understand the method and core ideas of the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.
Claims
1. A hard disk management system, characterized in that: Includes perception module and processing module; The sensing module is connected to the processing module and is used to detect that a hard disk is inserted, obtain the attribute information of the hard disk, and transmit the backplane signal containing the attribute information to the processing module; The processing module is used to receive the backplane signal transmitted by the sensing module; analyze the backplane signal according to the set naming rules to determine the naming information of the hard disk; wherein the naming information includes physical location coordinates and hardware information; and construct the name of the hard disk based on the naming information.
2. The hard disk management system according to claim 1, characterized in that: The processing module includes a position encoder, a feature extraction engine and a naming rule interpreter; The position encoder is used to parse the backplane signal to determine the physical position coordinates of the hard disk; The feature extraction engine is used to obtain the hard disk type contained in the backplane signal; and query the parameter information of the hard disk using the protocol corresponding to the hard disk type; The naming rule interpreter is used to combine the physical location coordinates, the hard disk type and the parameter information to generate a name for the hard disk.
3. The hard disk management system according to claim 2, characterized in that: The physical location coordinates include chassis number, cage number and slot number; The position encoder is used to obtain the chassis number of the motherboard where the hard disk is located; determine the cage number and slot number of the hard disk according to the hard disk insertion position contained in the backplane signal; and obtain the physical position coordinates by combining the chassis number, cage number and slot number in sequence; The feature extraction engine is configured to, when the hard disk is a serially connected hard disk, obtain parameter information of the hard disk in response to a storage protocol instruction; and when the hard disk is a non-volatile storage medium, obtain parameter information of the hard disk through a management interface; wherein the parameter information includes hard disk capacity; The naming rule interpreter is used to pre-store user-preset naming rules; in the absence of a user-set custom name, convert the hard disk capacity into a standard capacity according to the capacity unit contained in the naming rule; according to the storage type corresponding to each hard disk type contained in the naming rule, convert the hard disk type into a corresponding target storage type; according to the naming format contained in the naming rule, combine the physical location coordinates, the standard capacity, and the target storage type to generate the name of the hard disk; in the presence of a user-set custom name, use the custom name as the name of the hard disk.
4. The hard disk management system according to claim 1, characterized in that: The sensing module includes a hard disk backplane and a baseboard management controller; the attribute information includes the hard disk insertion position and hard disk type; The hard disk backplane is connected to the baseboard management controller, and is used to obtain the hard disk insertion position of the hard disk and transmit the hard disk insertion position to the baseboard management controller; The baseboard management controller is used to obtain the hard disk type through the serial bus; receive the hard disk insertion position transmitted by the hard disk backplane; convert the hard disk insertion position and the hard disk type into a backplane signal, and transmit the backplane signal to the processing module.
5. The hard disk management system according to claim 4, characterized in that: The hard disk backplane is used to obtain a slot status signal and physical slot information, and transmit the slot status signal and the physical slot information to the baseboard management controller; The baseboard management controller is used to send an in-place test command to the hard disk upon receiving the slot status signal and the physical slot information transmitted by the hard disk backplane; determine that the hard disk is effectively inserted upon receiving an in-place response signal fed back by the hard disk within a set time; determine that the hard disk is invalidly inserted upon not receiving an in-place response signal fed back by the hard disk within a set time; and, if the hard disk is effectively inserted, execute an operation of converting the hard disk insertion position and the hard disk type into a backplane signal.
6. The hard disk management system according to claim 4, characterized in that: The sensing module also includes a field replaceable chip; The field replaceable chip is connected to the hard disk backplane and the baseboard management controller respectively, and is used to obtain the manufacturer information and serial number of the hard disk through the hard disk backplane; and transmit the manufacturer information and serial number of the hard disk to the baseboard management controller; The baseboard management controller is used to receive the manufacturer information and serial number of the hard disk transmitted by the field replaceable chip; and convert the hard disk insertion position, the hard disk type, the hard disk manufacturer information and serial number into the backplane signal.
7. The hard disk management system according to claim 1, characterized in that: Also includes interactive modules; The interaction module is connected to the processing module and is used to perform read and write operations on the name of the hard disk.
8. The hard disk management system according to claim 7, characterized in that: The interactive module includes a web page submodule, an interface submodule and a command submodule; The webpage submodule is used to generate an editable name table to facilitate users to modify the names contained in the name table; The interface submodule is used to provide an access interface so that the user can obtain the name of the hardware; The command submodule is used to perform read and write operations on the name of the hard disk according to the name read and write command input by the user.
9. A hard disk management method, characterized in that: The hard disk management system according to any one of claims 1 to 7, wherein the method comprises: Receive a backplane signal transmitted by a sensing module; wherein the backplane signal includes attribute information of the hard disk; the attribute information is obtained when the sensing module detects that the hard disk is inserted; Analyzing the backplane signal according to a set naming rule to determine the naming information of the hard disk; wherein the naming information includes physical location coordinates and hardware information; A name for the hard disk is constructed based on the naming information.
10. A hard disk management device, characterized in that: The hard disk management system according to any one of claims 1 to 7, wherein the device comprises a receiving unit, an analyzing unit and a constructing unit; The receiving unit is configured to receive a backplane signal transmitted by the sensing module; wherein the backplane signal includes attribute information of the hard disk; the attribute information is obtained when the sensing module detects that the hard disk is inserted; The analysis unit is configured to analyze the backplane signal according to a set naming rule to determine the naming information of the hard disk; wherein the naming information includes physical location coordinates and hardware information; The construction unit is configured to construct a name of the hard disk based on the naming information.