Hard disk firmware upgrading method and device, electronic equipment and storage medium

Abstract

The invention provides a hard disk firmware upgrading method and device, electronic equipment and a storage medium, and relates to the technical field of storage, the method comprises the steps that in response to a firmware upgrading instruction, a hard disk list is determined, and the hard disk list comprises a plurality of hard disks to be subjected to firmware upgrading; selecting a current target hard disk to be subjected to firmware upgrading from the hard disk list, and judging whether the OSD service corresponding to the target hard disk exceeds the fault domain limitation of a storage system after being stopped; and under the condition that the OSD service corresponding to the target hard disk is determined not to exceed the limitation of the fault domain after being stopped, performing firmware upgrading on the target hard disk. According to the method, fault domain judgment and automatic operation are combined, so that the security and reliability of hard disk firmware upgrading are improved, the upgrading process is optimized, the workload of operation and maintenance personnel is reduced, and stable operation of a storage system is guaranteed.

Description

Technical Field

[0001] The present disclosure relates to the field of storage technology, and in particular to a hard disk firmware upgrade method, device, electronic device and storage medium. Background Art

[0002] As the core component of the storage system, the performance and stability of the hard disk directly affect the operation quality of the entire system. In order to maintain the best performance of the hard disk and solve possible security vulnerabilities or other problems, upgrading the hard disk firmware becomes a necessary maintenance measure.

[0003] Related hard disk firmware upgrades usually rely on manual operations, requiring maintenance personnel to have high computer knowledge and operation skills. The manual upgrade process is complicated, involving the identification of hard disk manufacturers and models, the search and download of firmware update files, and the correct use of firmware upgrade tools. The risk of operational errors is high, which may cause hard disk damage or data loss. In addition, storage systems usually need to upgrade hard disk firmware without interrupting external services, which places higher requirements on the automation, accuracy and speed of the upgrade process. Therefore, there is an urgent need for a firmware update method that can automatically and efficiently complete the hard disk firmware upgrade under the premise of normal operation of the storage system, so as to reduce human errors and improve the success rate of the upgrade. Summary of the invention

[0004] The embodiments of the present disclosure provide a hard disk firmware upgrade method, device, electronic device and storage medium, aiming to solve the problems existing in the above-mentioned background technology.

[0005] In order to solve the above technical problems, the present disclosure is implemented as follows:

[0006] In a first aspect, an embodiment of the present disclosure provides a hard disk firmware upgrade method, the method comprising:

[0007] In response to the firmware upgrade instruction, determining a hard disk list, the hard disk list including a plurality of hard disks to be upgraded with firmware;

[0008] Selecting a target hard disk to be upgraded from the hard disk list, and determining whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping;

[0009] When it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after being stopped, the firmware of the target hard disk is upgraded.

[0010] Optionally, after the firmware of the target hard disk is upgraded, the method further includes:

[0011] Monitor the firmware upgrade progress of the target hard disk to determine whether the firmware upgrade of the target hard disk is completed within a preset time;

[0012] When it is monitored that the target hard disk completes the firmware upgrade within the preset time, the next hard disk to be upgraded is selected from the hard disk list as the new target hard disk, and the steps are executed: predicting whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping; until all the hard disks in the hard disk list complete the firmware upgrade.

[0013] Optionally, the method further comprises:

[0014] When it is detected that the target hard disk has not completed the firmware upgrade within the preset time, the OSD service corresponding to the target hard disk is stopped, and the target hard disk is isolated;

[0015] Continue to monitor the firmware upgrade progress of the target hard disk, and when it is detected that the firmware upgrade of the target hard disk is completed, restart the OSD service corresponding to the target hard disk.

[0016] Optionally, the method further comprises:

[0017] When it is determined that stopping the OSD service corresponding to the target hard disk will exceed the fault domain limit, waiting is performed;

[0018] While waiting for the previous hard disk firmware upgrade to be completed and its corresponding OSD service to be restarted, it is determined again whether the OSD service corresponding to the target hard disk will exceed the fault domain limit after being stopped;

[0019] When it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after being stopped, the firmware of the target hard disk is upgraded.

[0020] Optionally, in response to the firmware upgrade instruction, determining a hard disk list includes:

[0021] Determine all hard disks currently online from the storage system;

[0022] According to the firmware upgrade instruction, determine the hard disk model that needs firmware upgrade;

[0023] Obtain the firmware file version number, and filter out all hard disks that match the hard disk model but do not match the firmware file version number from all currently online hard disks;

[0024] Add all hard disks that match the hard disk model but do not match the firmware file version number to the hard disk list.

[0025] Optionally, selecting a target hard disk to be currently upgraded with firmware from the hard disk list, and determining whether stopping an OSD service corresponding to the target hard disk will exceed a fault domain limit of a storage system includes:

[0026] Determining the storage node to which the target hard disk belongs according to the topological structure of the storage system;

[0027] Obtain service information of OSD services on each storage node in the storage system;

[0028] According to the storage node to which the target hard disk belongs and the service information of the OSD services on each storage node in the storage system, predict the number of OSD services that will be stopped after the OSD service corresponding to the target hard disk is stopped;

[0029] Determine whether the number of OSD services to be stopped meets the fault domain limit of the storage system;

[0030] When the number of OSD services to be stopped is lower than the fault domain limit, it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after stopping; when the number of OSD services to be stopped is not lower than the fault domain limit, it is determined that the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping.

[0031] Optionally, performing a firmware upgrade on the target hard disk includes:

[0032] Get the firmware file from the operating system;

[0033] Performing integrity check on the firmware file;

[0034] When the firmware file passes the integrity check, writing the firmware file into a firmware area in the memory of the target hard disk;

[0035] When the firmware file is written, restart the target hard disk for verification;

[0036] When the target hard disk passes the restart verification, the target hard disk is added back into the storage system for operation.

[0037] In a second aspect, an embodiment of the present disclosure provides a hard disk firmware upgrade device, the device comprising:

[0038] A hard disk list determination module, configured to determine a hard disk list in response to a firmware upgrade instruction, wherein the hard disk list includes a plurality of hard disks to be upgraded with firmware;

[0039] A judgment module, used for selecting a target hard disk to be currently upgraded with firmware from the hard disk list, and judging whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping;

[0040] The firmware upgrade module is used to upgrade the firmware of the target hard disk when it is determined that the failure domain limit will not be exceeded after the OSD service corresponding to the target hard disk is stopped.

[0041] Optionally, the device further comprises:

[0042] A timeout judgment module is used to monitor the firmware upgrade progress of the target hard disk and judge whether the firmware upgrade of the target hard disk is completed within a preset time;

[0043] The module continues to execute, which is used to select the next hard disk to be upgraded from the hard disk list as the new target hard disk when it is monitored that the target hard disk completes the firmware upgrade within the preset time, and execute the steps of: predicting whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping; until all hard disks in the hard disk list complete the firmware upgrade.

[0044] Optionally, the device further comprises:

[0045] An isolation module is used to stop the OSD service corresponding to the target hard disk and isolate the target hard disk when it is detected that the firmware upgrade of the target hard disk has not been completed within a preset time;

[0046] The restart module is used to continue monitoring the firmware upgrade progress of the target hard disk, and when it is monitored that the firmware upgrade of the target hard disk is completed, restart the OSD service corresponding to the target hard disk.

[0047] Optionally, the device further comprises:

[0048] A waiting module, used for waiting when it is determined that the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping;

[0049] A re-judgment module is used to judge again whether the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping, while waiting for the previous hard disk firmware upgrade to be completed and restarting its corresponding OSD service;

[0050] The recovery upgrade module is used to upgrade the firmware of the target hard disk when it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after stopping.

[0051] Optionally, the hard disk list determination module includes:

[0052] A hard disk determination submodule, used to determine all hard disks currently online from the storage system;

[0053] A hard disk model determination submodule, used to determine the hard disk model that requires firmware upgrade according to the firmware upgrade instruction;

[0054] The screening submodule is used to obtain the firmware file version number, and screen out all hard disks that match the hard disk model but do not match the firmware file version number from all currently online hard disks;

[0055] The add list submodule is used to add all hard disks that meet the hard disk model but do not match the firmware file version number to the hard disk list.

[0056] Optionally, the judging module includes:

[0057] A node determination submodule, used to determine the storage node to which the target hard disk belongs according to the topological structure of the storage system;

[0058] An acquisition submodule, used to acquire service information of OSD services on each storage node in the storage system;

[0059] A quantity determination submodule, used to predict the number of OSD services that will be stopped after stopping the OSD service corresponding to the target hard disk according to the storage node to which the target hard disk belongs and the service information of the OSD services on each storage node in the storage system;

[0060] The judgment submodule is used to judge whether the number of OSD services to be stopped meets the fault domain limit of the storage system;

[0061] The fault domain limit determination submodule is used to determine that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after stopping when the number of OSD services to be stopped is lower than the fault domain limit; and to determine that the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping when the number of OSD services to be stopped is not lower than the fault domain limit.

[0062] Optionally, the firmware upgrade module includes:

[0063] A firmware file acquisition submodule is used to obtain the firmware file from the operating system;

[0064] An integrity check submodule, used to perform integrity check on the firmware file;

[0065] A writing submodule, used for writing the firmware file into a firmware area in the memory of the target hard disk if the firmware file passes the integrity check;

[0066] A restart verification submodule, used for performing restart verification on the target hard disk when the firmware file is written;

[0067] The running submodule is used to add the target hard disk back into the storage system for operation when the target hard disk passes the restart verification.

[0068] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the steps of a hard disk firmware upgrade method when executed by the processor.

[0069] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of a hard disk firmware upgrade method are implemented.

[0070] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0071] The present disclosure responds to the firmware upgrade instruction, first determines a list of multiple hard disks to be upgraded, then selects the target hard disks one by one for upgrading, and before each upgrade, determines whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping. The target hard disk will be upgraded to a new firmware only when it is ensured that the fault domain limit will not be exceeded. By combining fault domain judgment with automated operation, not only the security and reliability of hard disk firmware upgrades are improved, but also the upgrade process is optimized, the workload of operation and maintenance personnel is reduced, and the stable operation of the storage system is guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0073] Figure 1 It is a schematic diagram of the steps of a hard disk firmware upgrade method provided by an embodiment of the present disclosure;

[0074] Figure 2 It is a complete flow chart of a hard disk firmware upgrade method provided by an embodiment of the present disclosure;

[0075] Figure 3 The present invention is a schematic diagram of the architecture of a hard disk firmware upgrade device provided by an embodiment of the present invention. DETAILED DESCRIPTION

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

[0077] With the continuous development of data storage technology and the increasing complexity of application scenarios, the requirements of storage systems for reliability and availability are gradually increasing, especially in large data centers and enterprise-level storage environments, where hard disk firmware upgrades are a key link in ensuring system stability and performance. However, the traditional firmware upgrade process often has problems such as complex operations and affected system stability. Especially when facing parallel upgrades of multiple hard disks, how to avoid service interruptions and fault domain overruns has become a challenge that technicians must overcome. The present disclosure is aimed at the above pain points and proposes a method for intelligently upgrading hard disk firmware while ensuring the stability of the storage system. It can not only effectively reduce the service interruption time during the upgrade process and improve the overall reliability and availability of the system, but also significantly reduce the complexity and risk of operation and maintenance operations. It has broad application prospects and practical value. The specific implementation method of the embodiment of the present disclosure and the beneficial effects it brings are described in detail below.

[0078] Figure 1 FIG. 1 is a schematic diagram of the steps of a hard disk firmware upgrade method provided by an embodiment of the present disclosure. Figure 1 As shown, the method includes:

[0079] Step S101, in response to a firmware upgrade instruction, determining a hard disk list, the hard disk list including a plurality of hard disks to be upgraded with firmware;

[0080] Step S102, selecting a target hard disk to be currently upgraded with firmware from the hard disk list, and determining whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping;

[0081] Step S103: When it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after being stopped, the firmware of the target hard disk is upgraded.

[0082] Involving step S101, after receiving the firmware upgrade instruction, the hard disks in the current storage system will be scanned and identified, aiming to determine all online hard disks, and filter out the hard disks that need to be upgraded, and build a list of hard disks to be upgraded. Specifically, when screening hard disks, the hard disk model and firmware version specified in the firmware upgrade instruction are used to determine which hard disks need to be upgraded. If the hard disk model meets the specified model and the current firmware version is lower than the new firmware version, the target hard disk will be added to the list to be upgraded.

[0083] Involving step S102, the target hard disk to be upgraded for firmware is selected from the hard disk list. This selection process is performed one by one, that is, the hard disks are selected from the list as the target hard disks to be updated each time, and the firmware upgrade operation is performed on only one hard disk at a time, thereby reducing the risk of concurrency. Determine whether the OSD (object storage daemon) service corresponding to the target hard disk to be tested will cause the storage system to exceed the limit of the fault domain after it is stopped. The so-called fault domain refers to the maximum allowable failure range in the storage system. For example, in a distributed storage system, in order to ensure data redundancy and high availability of the system, the storage system allows multiple hard disks or OSD services to fail within a certain range without affecting the overall normal operation. If stopping the OSD service of the target hard disk will cause the fault domain to exceed the limit (that is, the system cannot withstand more hard disks or service failures), the upgrade operation must be postponed and wait for the previous service to resume.

[0084] Involving step S103, when it is determined that stopping the OSD service of the target hard disk will not affect the fault domain stability of the storage system, the firmware upgrade operation will be started by calling a specific firmware upgrade tool to read the new firmware version and write it to the firmware area of ​​the hard disk.

[0085] The present disclosure responds to the firmware upgrade instruction, first determines a list of multiple hard disks to be upgraded, then selects the target hard disks one by one for upgrading, and before each upgrade, determines whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping. The target hard disk will be upgraded to a new firmware only when it is ensured that the fault domain limit will not be exceeded. By combining fault domain judgment with automated operation, not only the security and reliability of hard disk firmware upgrades are improved, but also the upgrade process is optimized, the workload of operation and maintenance personnel is reduced, and the stable operation of the storage system is guaranteed.

[0086] Exemplarily, after the firmware of the target hard disk is upgraded, the method further includes: monitoring the firmware upgrade progress of the target hard disk to determine whether the target hard disk has completed the firmware upgrade within a preset time; when it is monitored that the target hard disk has completed the firmware upgrade within the preset time, selecting the next hard disk to be upgraded from the hard disk list as the new target hard disk, and executing the steps of: predicting whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping; until all hard disks in the hard disk list complete the firmware upgrade.

[0087] During the firmware upgrade of the target hard disk, the upgrade progress is monitored in real time. The core indicator of the monitoring is the time required for the firmware upgrade to monitor the upgrade timeout. If the upgrade is completed within the preset time (such as 5 seconds), it means that the firmware upgrade of the target hard disk is successful. This result is recorded and the next hard disk is prepared to be selected from the hard disk list as the new target hard disk. Similarly, for each new target hard disk, before the upgrade, it is predicted whether the corresponding OSD service will affect the fault domain limit of the storage system after it stops. If the prediction result shows that the limit will not be exceeded, the upgrade operation will continue; if the limit will be exceeded, the upgrade of the target hard disk will be suspended until the storage system returns to an acceptable state. The above process will be executed in a loop until all hard disks in the hard disk list have completed the firmware upgrade. By upgrading the hard disks one by one, not only the risk of concurrent operations is reduced, but also the availability and stability of the storage system at any time are ensured.

[0088] Assume that there are 5 hard disks in the storage system that need to be upgraded, and the hard disk models are A1 to A5. According to the above process, the firmware of hard disk A1 is upgraded first, and it is monitored whether it is completed within 5 seconds. If A1 is successfully upgraded within the specified time, A2 is selected for upgrade, and hard disks are selected for upgrade in turn until A1 to A5 are upgraded.

[0089] Exemplarily, the method also includes: when it is monitored that the target hard disk has not completed the firmware upgrade within a preset time, stopping the OSD service corresponding to the target hard disk and isolating the target hard disk; continuing to monitor the firmware upgrade progress of the target hard disk, and when it is monitored that the target hard disk has completed the firmware upgrade, restarting the OSD service corresponding to the target hard disk.

[0090] When the firmware of the target hard disk is upgraded, the upgrade process is monitored in real time. If it is detected that the firmware upgrade of the target hard disk has not been completed within the preset time (such as 5 seconds), the timeout processing mechanism is triggered. In order to prevent the unfinished upgrade from having an adverse effect on the system, the OSD service associated with the target hard disk will be stopped to isolate the source of the fault and avoid possible system crashes or data corruption. After stopping the OSD service, the target hard disk is isolated, which means that the target hard disk will be temporarily inactive in the storage system and cannot participate in normal data access operations. It is designed to ensure that the target hard disk will not interfere with other parts of the system before the upgrade is completed.

[0091] After the isolation process, the monitoring of the target hard disk will not be stopped, but its upgrade progress will continue to be tracked. The firmware upgrade status of the target hard disk will be continuously monitored, and the target hard disk will be waited for to be finally upgraded to ensure that the firmware of the hard disk can be successfully updated to the latest version. If it is found in subsequent monitoring that the target hard disk still cannot be upgraded in the isolated state, it is necessary to further automatically trigger other emergency processing mechanisms, such as marking the target hard disk as a faulty disk for subsequent replacement. When it is detected that the firmware upgrade of the target hard disk is finally completed, the OSD service associated with the target hard disk is restarted to rejoin the target hard disk to the storage system. The target hard disk can re-participate in data access operations and resume normal working status. After restarting the OSD service corresponding to the target hard disk, the isolation of the target hard disk is lifted, and it is restored to an active component in the storage system. At this point, the firmware of the target hard disk has been upgraded and reconnected to the system through the restarted OSD service, ensuring the integrity and stability of the storage system.

[0092] Assume that in the storage system, there is a hard disk B2 that needs to be upgraded in firmware. During the upgrade process, the system detects that the B2 hard disk fails to complete the firmware upgrade within 5 seconds, so it starts the timeout processing mechanism to prevent the upgrade failure from affecting the storage system and stops the OSD service associated with B2. Subsequently, the B2 hard disk is isolated so that it no longer participates in the normal data processing operations of the storage system. Although the B2 hard disk is in an isolated state, its firmware upgrade progress is still continuously monitored. When the B2 hard disk finally completes the upgrade, its corresponding OSD service is restarted to release the isolation state and rejoin it to the system.

[0093] The above timeout upgrade strategy can effectively manage the timeout problem during the hard disk firmware upgrade process, ensuring that the storage system always maintains stability and high availability during the upgrade process.

[0094] Exemplarily, the method also includes: waiting when it is determined that the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping; while waiting for the previous hard disk firmware upgrade to be completed and its corresponding OSD service to be restarted, again determining whether the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping; and performing a firmware upgrade on the target hard disk when it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after stopping.

[0095] Before upgrading the firmware of the target hard disk, it is first necessary to determine whether stopping the OSD service of the target hard disk will cause the storage system's fault domain to exceed the limit. That is, determine whether stopping the OSD service of the target hard disk will cause the storage system to exceed the allowable fault domain range. If it is determined that stopping the OSD service of the target hard disk will cause the fault domain to exceed the limit, the firmware upgrade will not be performed immediately, but the system will enter a waiting state. At this time, priority will be given to waiting for the hard disk that has entered the upgrade process to complete its firmware upgrade and restart its corresponding OSD service. When entering the waiting state, the progress of the previous firmware upgrade is continuously monitored so that the fault domain judgment can be re-performed at an appropriate time. The hard disk that is being upgraded will be waited for to complete its firmware upgrade and restart the OSD service of the target hard disk. After the OSD service is restarted, the fault domain capacity of the storage system is restored, thereby providing conditions for the firmware upgrade of the target hard disk. After the upgrade of the previous hard disk is completed and the OSD service is restarted, it is re-evaluated whether stopping the OSD service corresponding to the target hard disk will still cause the fault domain to exceed the limit. If it is determined that stopping the OSD service of the target hard disk at this time will no longer exceed the fault domain limit, the firmware upgrade of the target hard disk will be allowed.

[0096] Assume that in a storage system, there are multiple hard disks that need to undergo a firmware upgrade. Hard disks A1 and A2 are both marked as requiring an upgrade during the initial check. However, when checking A1, it was found that stopping its OSD service would not exceed the fault domain limit, so A1 was upgraded first. After A1's upgrade was completed and its OSD service was restarted, the system then processed A2. In the initial judgment, it was found that stopping A2's OSD service at this time would cause the fault domain to exceed the limit, so the system would not upgrade A2 immediately, but would enter a waiting state. Next, after waiting for A1's upgrade to complete and restarting its OSD service, it was again evaluated whether stopping A2's OSD service would exceed the fault domain limit. This time, since A1's OSD service had been restarted, it was determined that A2 could safely stop its OSD service for the upgrade. Therefore, the firmware upgrade for A2 was started.

[0097] Through the above-mentioned firmware upgrade strategy of step-by-step judgment and waiting, the storage system can safely upgrade the firmware of each hard disk without affecting the overall stability. The core is to ensure that the system will not exceed the fault domain limit at any time, as well as intelligent upgrade scheduling. It is suitable for large-scale distributed storage systems and can effectively maintain the overall stability of the system when there are a large number of hard disks and frequent firmware upgrades.

[0098] Figure 2 FIG. 1 is a complete flow chart of a hard disk firmware upgrade method provided by an embodiment of the present disclosure. Figure 2As shown, the first step is to upload the firmware version and execute the online hard disk firmware upgrade tool. Before the firmware upgrade operation starts, the new firmware version needs to be uploaded to the storage system. Through the online hard disk firmware upgrade tool, all the hard disks currently online in the storage system are identified, and the hard disk models and version numbers that need to be upgraded are screened. These hard disks will be added to the hard disk list to be upgraded. The second step is to specify the disk model to be upgraded and start the upgrade. After uploading the firmware and identifying the hard disk to be upgraded, the user specifies the hard disk model to be upgraded and starts the upgrade process. This operation is the response of the firmware upgrade tool to the user input. According to the specified hard disk model, the hard disk that meets the conditions will be selected from the hard disk list as the target hard disk for upgrade. The third step is to determine whether the storage cluster fault domain will be exceeded after the OSD service corresponding to the hard disk is stopped. Before upgrading the specified target hard disk, first evaluate whether stopping the OSD service corresponding to the target hard disk will cause the storage cluster fault domain limit to be exceeded. The fourth step is to continue to upgrade the target hard disk firmware if it is determined that stopping the OSD service of the target hard disk will not exceed the fault domain limit. During the upgrade process, the progress of the upgrade will be monitored to ensure that the upgrade can be completed smoothly. If the system determines that stopping the OSD service of the target hard disk will exceed the fault domain limit, the upgrade will not be performed immediately, but will enter a waiting state. At this time, wait for the hard disk that was previously being upgraded to complete the firmware upgrade and restart its corresponding OSD service. When these services are back online and the system is in a stable state, it will be re-determined whether the firmware upgrade of the target hard disk can be performed, and the upgrade operation will be performed when conditions permit. Step 5. During the firmware upgrade process, the upgrade progress will be monitored to determine whether the target hard disk has completed the upgrade within the preset time. If the upgrade is successfully completed within the preset time, the next hard disk to be upgraded will be selected from the hard disk list, and the above steps will be repeated until all hard disks have completed the firmware upgrade. If the firmware upgrade of the target hard disk fails to complete within the preset time, further measures will be taken. Stop the OSD service corresponding to the target hard disk, and isolate the target hard disk to prevent the long-term incomplete upgrade from affecting other parts of the system. At the same time, the upgrade progress of the target hard disk will continue to be monitored until the upgrade is completed, and restart its OSD service after completion. During the upgrade process, the delay of a hard disk will not hinder the upgrade process of other hard disks.

[0099] The disclosed embodiment provides a safe and reliable hard disk firmware upgrade mechanism, which ensures that the firmware upgrade can proceed smoothly through real-time evaluation of fault domain limitations, strict monitoring of the upgrade process and timeout processing mechanism, and fully guarantees the stability of the storage system during the upgrade process. This process effectively reduces the risks in the upgrade process through multiple steps of judgment and processing, and improves the overall reliability and security of the system.

[0100] Exemplarily, in response to a firmware upgrade instruction, determining a hard disk list includes: determining all hard disks that are currently online from the storage system; determining the hard disk models that require firmware upgrades based on the firmware upgrade instruction; obtaining the firmware file version number, and filtering out all hard disks that meet the hard disk model but do not match the firmware file version number from all hard disks that are currently online; and adding all hard disks that meet the hard disk model but do not match the firmware file version number to the hard disk list.

[0101] After receiving the firmware upgrade instruction, first perform a comprehensive scan of the storage system to identify all online hard disks in the current system and obtain the hard disk list of the storage system for subsequent screening and judgment. Obtain detailed information of each hard disk, including the hard disk model, firmware version number, etc. Parse the firmware upgrade instruction and extract the hard disk model specified in the instruction. These specified hard disk models are usually the hard disk types that need to be upgraded, ensuring the targetedness of the upgrade operation. Compare the scanned hard disks with the hard disk models specified in the firmware upgrade instruction. Only hard disks whose hard disk models meet the requirements of the firmware upgrade instruction will be considered for further firmware upgrade operations. Obtain the latest firmware file version number from the firmware upgrade instruction or pre-configuration. Then, perform version comparison on all hard disks that meet the specified model. Filter out those hard disks whose firmware version numbers do not match (i.e., lower than the latest version) from the online hard disks, and only these hard disks will be identified as requiring firmware upgrade. For all hard disks that meet the specified hard disk model but do not match the firmware version, add them to the hard disk list to be upgraded. In actual operation, if a new hard disk that needs to be upgraded is found in subsequent scanning or judgment, the hard disk list to be upgraded is dynamically updated to ensure that each upgrade operation is based on the latest storage system status.

[0102] Exemplarily, a target hard disk to be upgraded with firmware is selected from the hard disk list, and it is determined whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after it is stopped, including: determining the storage node to which the target hard disk belongs according to the topological structure of the storage system; obtaining service information of the OSD service on each storage node in the storage system; predicting the number of OSD services that will be stopped after the OSD service corresponding to the target hard disk is stopped according to the storage node to which the target hard disk belongs and the service information of the OSD service on each storage node in the storage system; determining whether the number of OSD services that are about to be stopped meets the fault domain limit of the storage system; if the number of OSD services that are about to be stopped is lower than the fault domain limit, determining that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after it is stopped; if the number of OSD services that are about to be stopped is not lower than the fault domain limit, determining that the OSD service corresponding to the target hard disk will exceed the fault domain limit after it is stopped.

[0103] The topology of the storage system consists of multiple storage nodes, each of which contains one or more hard disks and corresponding OSD services. First, it is necessary to identify the storage node where the target hard disk is located, because the distribution of hard disks and OSD services on different nodes has a direct impact on the redundancy and fault tolerance of the entire system. Assume that a storage system contains three storage nodes A, B, and C, each of which has 10 hard disks and 10 OSD services. If you want to upgrade the target hard disk on node A, you first need to confirm that the target hard disk belongs to node A. Obtain the service information of the OSD services running on each node in the storage system. The service information includes the status (such as normal operation, paused) and number of each OSD service on each node, which serves as an important basis for subsequent judgment of whether the fault domain limit will be exceeded. In the above example, it is assumed that there are currently 9 normal operating OSD services on node A, and nodes B and C have 10 normal operating OSD services respectively. According to the storage node to which the target hard disk belongs and the service information of the OSD services on each storage node in the storage system, the number of OSD services that are about to stop in the system is predicted. The prediction is not limited to the current node, but also needs to consider the impact of the global system. If the service information of the OSD service on each storage node in the storage system indicates that the OSD service of one hard disk of node A has been stopped, the OSD service of two hard disks of node B has been stopped, and the OSD service of three hard disks of node C has been stopped, before the firmware upgrade of the target hard disk located at node A is performed, it is predicted that after stopping the OSD service corresponding to the target hard disk, the number of OSD services to be stopped is 1+2+3+1=7. Determine whether the number of OSD services to be stopped meets the fault domain limit of the storage system. As mentioned above, the fault domain limit refers to the maximum failure range that the storage system can tolerate. For example, in a storage system with an N+2 redundancy strategy, at most two OSD services are allowed to fail at the same time without affecting the data integrity and availability of the system. Based on the information obtained in the previous steps, it is necessary to determine whether stopping the OSD service of the target hard disk will cause the system to exceed the allowed fault domain limit. Specifically, when the number of OSD services to be stopped is lower than the fault domain limit, it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after stopping; when the number of OSD services to be stopped is not lower than the fault domain limit, it is determined that the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping. If the storage system allows a maximum of 8 OSD services to fail without affecting operation, and if the OSD service corresponding to the target hard disk is stopped, the number of OSD services to be stopped is 7 < 8, so the redundancy of the storage system is still within the allowable range, and it is determined that the failure domain limit will not be exceeded after the OSD service corresponding to the target hard disk is stopped.On the contrary, if the storage system allows a maximum of 6 OSD services to fail without affecting operation, and if after stopping the OSD service corresponding to the target hard disk, the number of OSD services to be stopped is 7>6, then after the OSD service of the target hard disk is stopped, the fault domain limit will be exceeded. At this time, you must wait for the OSD service of the previous hard disk to recover before upgrading the firmware.

[0104] Exemplarily, performing a firmware upgrade on the target hard disk includes: obtaining a firmware file from an operating system; performing an integrity check on the firmware file; if the firmware file passes the integrity check, writing the firmware file to a firmware area in the memory of the target hard disk; if the firmware file is written, performing a restart verification on the target hard disk; if the target hard disk passes the restart verification, re-adding the target hard disk to the storage system for operation.

[0105] Before performing a firmware upgrade, you first need to obtain the firmware file to be upgraded from the operating system. Download the latest firmware file from the manufacturer or storage system's management console and save it in the specified path. Make sure that the operating system can access the storage path of the firmware file so that it can be read and verified later. After obtaining the firmware file, perform an integrity check on the file to ensure that the firmware file has not been damaged or tampered with during the download or transmission process. The integrity check includes hash check and digital signature verification. Specifically, the integrity check is used to calculate the hash value of the file (such as MD5, SHA-256) and compare it with the hash value provided by the official. Digital signature verification is used to verify the digital signature of the firmware file to ensure that the file source is reliable and has not been tampered with. For example, the operating system calculates the SHA-256 hash value of the downloaded firmware file and compares it with the hash value provided by the manufacturer. If the two are consistent, it means that the file has not been tampered with and the verification passes; otherwise, the verification fails and you need to download it again or confirm the security of the file.

[0106] Once the firmware file passes the integrity check, write the firmware file to the firmware area of ​​the target hard disk. Specifically, load the firmware file into the temporary memory area of ​​the hard disk, and then write the loaded firmware file data into the firmware area of ​​the hard disk. After the firmware file is written, restart the target hard disk to verify whether the new firmware file is successfully loaded and can work normally. After the hard disk is powered off, it is powered on again, loads the new firmware, and confirms that the hard disk can start normally with the support of the new firmware file and perform basic read and write operations. After the target hard disk successfully passes the restart verification, the target hard disk will be re-added to the storage system and resume its normal service status in the storage system.

[0107] Exemplarily, the method also includes: before executing the firmware upgrade operation, pre-checking the health status of the target hard disk; when the health status of the target hard disk meets the predetermined conditions, allowing the firmware upgrade operation to be performed; when the health status of the target hard disk does not meet the predetermined conditions, skipping the firmware upgrade of the target hard disk, and generating a report after the upgrade is completed to record the target hard disk and its health status.

[0108] Before the firmware upgrade, if the hard disk has shown signs of failure or is in poor health, forcibly performing a firmware upgrade may cause the hard disk to be completely damaged or even cause data loss. Therefore, the disclosed embodiment adds a check on the health status of the hard disk before the upgrade operation to effectively avoid upgrade failures caused by hard disk health problems. The pre-check content includes the SMART status of the hard disk, the hard disk error log, the current temperature and the read and write error rate. By analyzing the above health parameters, it is determined whether the target hard disk to be upgraded is suitable for firmware upgrade. The predetermined condition can be a threshold value based on the health status of the hard disk. For example, if the SMART status of the target hard disk shows that certain key parameters exceed a predetermined safety threshold (such as too many reallocated sectors, uncorrected read and write errors, etc.), the target hard disk is considered to be unsuitable for firmware upgrade. When the health status of the target hard disk does not meet the predetermined conditions, the upgrade of the target hard disk will be skipped to prevent the upgrade operation from being performed on a hard disk with potential problems, thereby avoiding further damage to the storage system. At the same time, the detailed information of these target hard disks that have not been upgraded, including the health status of the hard disk, the reason for skipping, and the generation of a report, provide a basis for subsequent maintenance and replacement of the hard disk, and help the operation and maintenance personnel to deal with potential hard disk failures in a timely manner.

[0109] The present disclosure not only solves the problems of high complexity, high risk and high time cost of traditional manual firmware upgrades, but also further considers the health of the hard disk during the upgrade process, significantly improving the security of the firmware upgrade operation and the reliability of the system.

[0110] Figure 3 FIG. 1 is a schematic diagram of the architecture of a hard disk firmware upgrade device provided by an embodiment of the present disclosure. Figure 3 As shown, the device comprises:

[0111] A hard disk list determination module 201 is used to determine a hard disk list in response to a firmware upgrade instruction, wherein the hard disk list includes a plurality of hard disks to be upgraded with firmware;

[0112] The judgment module 202 is used to select a target hard disk to be currently upgraded from the hard disk list, and judge whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping;

[0113] The firmware upgrade module 203 is used to upgrade the firmware of the target hard disk when it is determined that the failure domain limit will not be exceeded after the OSD service corresponding to the target hard disk is stopped.

[0114] Exemplarily, the device further comprises:

[0115] A timeout judgment module is used to monitor the firmware upgrade progress of the target hard disk and judge whether the firmware upgrade of the target hard disk is completed within a preset time;

[0116] The module continues to execute, which is used to select the next hard disk to be upgraded from the hard disk list as the new target hard disk when it is monitored that the target hard disk completes the firmware upgrade within the preset time, and execute the steps of: predicting whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping; until all hard disks in the hard disk list complete the firmware upgrade.

[0117] Exemplarily, the device further comprises:

[0118] An isolation module is used to stop the OSD service corresponding to the target hard disk and isolate the target hard disk when it is detected that the firmware upgrade of the target hard disk has not been completed within a preset time;

[0119] The restart module is used to continue monitoring the firmware upgrade progress of the target hard disk, and when it is monitored that the firmware upgrade of the target hard disk is completed, restart the OSD service corresponding to the target hard disk.

[0120] Exemplarily, the device further includes:

[0121] A waiting module, used for waiting when it is determined that the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping;

[0122] A re-judgment module is used to judge again whether the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping, while waiting for the previous hard disk firmware upgrade to be completed and restarting its corresponding OSD service;

[0123] The recovery upgrade module is used to upgrade the firmware of the target hard disk when it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after stopping.

[0124] Exemplarily, the hard disk list determination module includes:

[0125] A hard disk determination submodule, used to determine all hard disks currently online from the storage system;

[0126] A hard disk model determination submodule, used to determine the hard disk model that requires firmware upgrade according to the firmware upgrade instruction;

[0127] The screening submodule is used to obtain the firmware file version number, and screen out all hard disks that match the hard disk model but do not match the firmware file version number from all currently online hard disks;

[0128] The add list submodule is used to add all hard disks that meet the hard disk model but do not match the firmware file version number to the hard disk list.

[0129] Exemplarily, the judging module includes:

[0130] A node determination submodule, used to determine the storage node to which the target hard disk belongs according to the topological structure of the storage system;

[0131] An acquisition submodule, used to acquire service information of OSD services on each storage node in the storage system;

[0132] A quantity determination submodule, used to predict the number of OSD services that will be stopped after stopping the OSD service corresponding to the target hard disk according to the storage node to which the target hard disk belongs and the service information of the OSD services on each storage node in the storage system;

[0133] The judgment submodule is used to judge whether the number of OSD services to be stopped meets the fault domain limit of the storage system;

[0134] The fault domain limit determination submodule is used to determine that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after stopping when the number of OSD services to be stopped is lower than the fault domain limit; and to determine that the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping when the number of OSD services to be stopped is not lower than the fault domain limit.

[0135] Exemplarily, the firmware upgrade module includes:

[0136] A firmware file acquisition submodule is used to obtain the firmware file from the operating system;

[0137] An integrity check submodule, used to perform integrity check on the firmware file;

[0138] A writing submodule, used for writing the firmware file into a firmware area in the memory of the target hard disk if the firmware file passes the integrity check;

[0139] A restart verification submodule, used for performing restart verification on the target hard disk when the firmware file is written;

[0140] The running submodule is used to add the target hard disk back into the storage system for operation when the target hard disk passes the restart verification.

[0141] An embodiment of the present disclosure also provides an electronic device, including a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, the various processes in the above-mentioned embodiment of a hard disk firmware upgrade method are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0142] The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, each process in the above-mentioned embodiment of a hard disk firmware upgrade method is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the embodiments can be referred to each other.

[0143] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, devices, electronic devices, and storage media. Therefore, the embodiments of the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present disclosure may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0144] The embodiments of the present disclosure are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a server, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing terminal device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the functions specified in the process. Figure 1A process or multiple processes and / or boxes Figure 1 These computer program instructions can also be loaded into a computer or other programmable data processing terminal device, so that a series of operation steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable terminal device provide for implementing the process in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0145] Although the preferred embodiments of the present disclosure have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present disclosure.

[0146] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the term "include" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "include..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements. The above is a detailed introduction to a hard disk firmware upgrade method, device, electronic device and storage medium provided by the present disclosure. The present disclosure is explained in detail using specific examples in this article to illustrate the principles and implementation methods of the present disclosure. The description of the above embodiments is only used to help understand the method and its core idea of ​​the present disclosure; at the same time, for those of ordinary skill in the art, according to the idea of ​​the present disclosure, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present disclosure.

Claims

1. A hard disk firmware upgrade method, characterized in that: The method comprises: In response to the firmware upgrade instruction, determining a hard disk list, the hard disk list including a plurality of hard disks to be upgraded with firmware; Selecting a target hard disk to be upgraded from the hard disk list, and determining whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping; When it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after being stopped, the firmware of the target hard disk is upgraded.

2. The method according to claim 1, characterized in that After the firmware of the target hard disk is upgraded, the method further includes: Monitor the firmware upgrade progress of the target hard disk to determine whether the firmware upgrade of the target hard disk is completed within a preset time; When it is monitored that the target hard disk completes the firmware upgrade within the preset time, the next hard disk to be upgraded is selected from the hard disk list as the new target hard disk, and the steps are executed: predicting whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping; until all the hard disks in the hard disk list complete the firmware upgrade.

3. The method according to claim 2, characterized in that The method further comprises: When it is detected that the target hard disk has not completed the firmware upgrade within the preset time, the OSD service corresponding to the target hard disk is stopped, and the target hard disk is isolated; Continue to monitor the firmware upgrade progress of the target hard disk, and when it is detected that the firmware upgrade of the target hard disk is completed, restart the OSD service corresponding to the target hard disk.

4. The method according to claim 1, characterized in that The method further comprises: When it is determined that stopping the OSD service corresponding to the target hard disk will exceed the fault domain limit, waiting is performed; While waiting for the previous hard disk firmware upgrade to be completed and its corresponding OSD service to be restarted, it is determined again whether the OSD service corresponding to the target hard disk will exceed the fault domain limit after being stopped; When it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after being stopped, the firmware of the target hard disk is upgraded.

5. The method according to claim 1, characterized in that The step of determining a hard disk list in response to the firmware upgrade instruction includes: Determine all hard disks currently online from the storage system; According to the firmware upgrade instruction, determine the hard disk model that needs firmware upgrade; Obtain the firmware file version number, and filter out all hard disks that match the hard disk model but do not match the firmware file version number from all currently online hard disks; Add all hard disks that match the hard disk model but do not match the firmware file version number to the hard disk list.

6. The method according to claim 1, characterized in that Selecting a target hard disk to be upgraded from the hard disk list, and determining whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping, including: Determining the storage node to which the target hard disk belongs according to the topological structure of the storage system; Obtain service information of OSD services on each storage node in the storage system; According to the storage node to which the target hard disk belongs and the service information of the OSD services on each storage node in the storage system, predict the number of OSD services that will be stopped after the OSD service corresponding to the target hard disk is stopped; Determine whether the number of OSD services to be stopped meets the fault domain limit of the storage system; When the number of OSD services to be stopped is lower than the fault domain limit, it is determined that the OSD service corresponding to the target hard disk will not exceed the fault domain limit after stopping; when the number of OSD services to be stopped is not lower than the fault domain limit, it is determined that the OSD service corresponding to the target hard disk will exceed the fault domain limit after stopping.

7. The method according to claim 1, characterized in that Performing a firmware upgrade on the target hard disk includes: Get the firmware file from the operating system; Performing integrity check on the firmware file; When the firmware file passes the integrity check, writing the firmware file into a firmware area in the memory of the target hard disk; When the firmware file is written, restart the target hard disk for verification; When the target hard disk passes the restart verification, the target hard disk is added back into the storage system for operation.

8. A hard disk firmware upgrade device, characterized in that: The device comprises: A hard disk list determination module, configured to determine a hard disk list in response to a firmware upgrade instruction, wherein the hard disk list includes a plurality of hard disks to be upgraded with firmware; A judgment module, used for selecting a target hard disk to be currently upgraded with firmware from the hard disk list, and judging whether the OSD service corresponding to the target hard disk will exceed the fault domain limit of the storage system after stopping; The firmware upgrade module is used to upgrade the firmware of the target hard disk when it is determined that the failure domain limit will not be exceeded after the OSD service corresponding to the target hard disk is stopped.

9. An electronic device, characterized in that: include: A processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein when the computer program is executed by the processor, the steps of the method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images