CN115576739A - Hard disk firmware backup method, device, equipment and storage medium - Google Patents

Abstract

The application provides a firmware backup method, a device, equipment and a storage medium for a hard disk, wherein the method comprises the following steps: if the signal flow information appears on the firmware backup interface of the client, determining that a target hard disk of firmware to be backed up is placed in the channel port, responding to the firmware backup operation input by a user through the firmware backup interface by the client, acquiring identification information of the target hard disk, sending a firmware backup command to the target hard disk according to the identification information, receiving the firmware information from the target hard disk, and storing the firmware information into a file directory corresponding to the target hard disk. The method and the device can quickly meet the requirements of the user on the firmware information backup of the hard disk on the basis of accurately backing up the firmware information of the hard disk.

Description

Hard disk firmware backup method, device, equipment and storage medium

Technical Field

The present application relates to the field of firmware backup technologies for hard disks, and in particular, to a firmware backup method, apparatus, device, and storage medium for a hard disk.

Background

The hard disk is mainly composed of a disk body, a magnetic head, a disk, a spindle motor, a magnetic head controller, a circuit board, an interface, a cache and the like, and in addition, an indispensable important component is firmware. The firmware is software solidified in hardware, includes a program for initializing diagnosis, controlling rotation of a spindle motor, controlling a magnetic head controller and exchanging data between Random Access Memories (RAMs), can control the hard disk to perform operations such as data reading and writing, managing data storage positions, recording defective sectors and the like, and is an important coordinator for controlling normal starting and operation of the hard disk and interaction and mutual cooperation among all components.

In practical applications, after a firmware runs for a long time, problems or damages may occur to different degrees, thereby causing a hard disk failure, and at this time, the firmware needs to be repaired. However, the original firmware information is usually not disclosed, so that the workload of searching and collecting the original firmware information of the hard disk through a network is very large and time-consuming, and the original firmware information matching with the failed hard disk cannot be found.

Disclosure of Invention

The application provides a firmware backup method, device, equipment and storage medium for a hard disk, which are used for solving the problems that the workload of searching and collecting original firmware information of the hard disk through a network is very large and time-consuming, and the original firmware information matched with a failed hard disk cannot be found.

In a first aspect, the present application provides a firmware backup method for a hard disk, which is applied to a client, where the client is configured to execute a firmware backup interface obtained by rendering a firmware backup application, the firmware backup interface is configured to present signal stream information of a channel port corresponding to the firmware backup interface, the channel port is used for placing a hard disk of a firmware to be backed up, and the channel port is an interaction channel between the hard disk and the client, and the firmware backup method includes:

if the firmware backup interface presents signal flow information, determining a target hard disk with firmware to be backed up in a channel port;

responding to a firmware backup operation input by a user through a firmware backup interface, and acquiring identification information of a target hard disk;

sending a firmware backup command to the target hard disk according to the identification information;

receiving firmware information from a target hard disk;

and storing the firmware information into a file directory corresponding to the target hard disk.

Optionally, the obtaining of the identification information of the target hard disk includes: sending a command for reading hard disk information to a target hard disk; and receiving hard disk information from the target hard disk, wherein the hard disk information comprises identification information.

Optionally, sending a firmware backup command to the target hard disk according to the identification information includes: determining firmware to be backed up corresponding to the target hard disk according to the identification information, wherein the firmware to be backed up comprises at least one of a module, a Read Only Memory (ROM), a magnetic track and a system file; and sending a firmware backup command to the target hard disk according to the firmware to be backed up, wherein the firmware backup command is used for indicating that corresponding firmware information is acquired from the storage position of the firmware to be backed up in the target hard disk.

Optionally, after sending the firmware backup command to the target hard disk, the firmware backup method further includes: and if the firmware information corresponding to the firmware to be backed up is not acquired, sending a firmware backup command to the target hard disk through a serial Communication Port (COM).

Optionally, sending a firmware backup command to the target hard disk according to the identification information includes: determining a key corresponding to the target hard disk according to the identification information; verifying identity information with the target hard disk based on the secret key; and when the identity information passes the verification, sending a firmware backup command to the target hard disk according to the identification information.

Optionally, the storing the firmware information in the file directory corresponding to the target hard disk includes: establishing a hierarchical storage file directory corresponding to the target hard disk according to the identification information of the target hard disk and the firmware to be backed up corresponding to the target hard disk; and storing the firmware information to a hierarchical storage file directory corresponding to the target hard disk.

In a second aspect, the present application provides a firmware backup device for a hard disk, which is applied to a client, where the client is configured to execute a firmware backup interface rendered by a firmware backup application, the firmware backup interface is configured to present signal stream information of a channel port corresponding to the firmware backup interface, the channel port is used to place the hard disk of a firmware to be backed up, and the channel port is an interaction channel between the hard disk and the client, and the firmware backup device includes:

the determining module is used for determining a target hard disk in which the firmware to be backed up is placed in the channel port if the signal flow information is presented on the firmware backup interface;

the acquisition module is used for responding to the firmware backup operation input by a user through the firmware backup interface and acquiring the identification information of the target hard disk;

the sending module is used for sending a firmware backup command to the target hard disk according to the identification information;

the receiving module is used for receiving the firmware information from the target hard disk;

and the storage module is used for storing the firmware information into the file directory corresponding to the target hard disk.

Optionally, the obtaining module is specifically configured to: sending a command for reading hard disk information to a target hard disk; and receiving hard disk information from the target hard disk, wherein the hard disk information comprises identification information.

Optionally, the sending module is specifically configured to: determining firmware to be backed up corresponding to the target hard disk according to the identification information, wherein the firmware to be backed up comprises at least one of a module, a ROM, a magnetic track and a system file; and sending a firmware backup command to the target hard disk according to the firmware to be backed up, wherein the firmware backup command is used for indicating that corresponding firmware information is acquired from the storage position of the firmware to be backed up in the target hard disk.

Optionally, after sending the firmware backup command to the target hard disk, the sending module is further configured to: and if the firmware information corresponding to the firmware to be backed up is not acquired, sending a firmware backup command to the target hard disk through COM.

Optionally, the sending module is specifically configured to: determining a key corresponding to the target hard disk according to the identification information; verifying identity information with the target hard disk based on the secret key; and when the identity information passes the verification, sending a firmware backup command to the target hard disk according to the identification information.

Optionally, the saving module is specifically configured to: establishing a hierarchical storage file directory corresponding to the target hard disk according to the identification information of the target hard disk and the firmware to be backed up corresponding to the target hard disk; and storing the firmware information to a hierarchical storage file directory corresponding to the target hard disk.

In a third aspect, the present application provides an electronic device, comprising: a memory and a processor;

the memory is used for storing program instructions;

the processor is used for calling the program instructions in the memory to execute the firmware backup method of the hard disk according to the first aspect of the application.

In a fourth aspect, the present application provides a computer-readable storage medium, in which computer program instructions are stored, and when the computer program instructions are executed, the method for backing up firmware of a hard disk according to the first aspect of the present application is implemented.

In a fifth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements a firmware backup method for a hard disk according to the first aspect of the present application.

The client is used for executing a firmware backup interface obtained by rendering of a firmware backup application, the firmware backup interface is used for presenting signal stream information of a channel port corresponding to the firmware backup interface, the channel port is used for placing a hard disk of firmware to be backed up, the channel port is an interactive channel of the hard disk and the client, if the signal stream information is presented on the firmware backup interface of the client, a target hard disk of the firmware to be backed up is determined to be placed in the channel port, the client responds to firmware backup operation input by a user through the firmware backup interface, identification information of the target hard disk is obtained, a firmware backup command is sent to the target hard disk according to the identification information, the firmware information from the target hard disk is received, and the firmware information is stored into a file directory corresponding to the target hard disk. According to the method and the device, the firmware information of the target hard disk is acquired through the firmware backup interface of the client, namely, the service of one-key backup of the firmware information of the hard disk is provided for the user, so that the requirement of the user on the backup of the firmware information of the hard disk can be quickly met on the basis of accurately backing up the firmware information of the hard disk.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;

fig. 2 is a flowchart of a firmware backup method for a hard disk according to an embodiment of the present application;

fig. 3 (a) to fig. 3 (c) are schematic structural diagrams of a passage opening according to an embodiment of the present application;

fig. 4 is a flowchart of a firmware backup method for a hard disk according to another embodiment of the present application;

fig. 5 is a schematic structural diagram of a firmware backup apparatus for a hard disk according to an embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

First, some technical terms related to the present application are explained:

track: before the disk is shipped, the manufacturer formats the disk of the disk, and the disk of the disk is divided into a plurality of concentric circles, which are tracks (tracks). Every disk surface of the current hard disk has tens of thousands of magnetic tracks, which is convenient for management, each magnetic track has a number, the magnetic tracks are numbered sequentially from outside to inside from 0 logically, and the magnetic track before the magnetic track of 0 is a negative magnetic track.

A module: the key modules exist in the maximum negative magnetic track of the hard disk, part of the key modules can be loaded into the memory after the hard disk is electrified, and the integrity and the correctness of the key modules are the precondition for the normal operation of the hard disk.

ROM: the hard disk is positioned on the circuit board, and is loaded into a cache of the hard disk after being powered on, wherein the cache contains important disk information. For example, a west hard disk is divided into an external ROM and an internal ROM, where the external ROM is a Basic Input Output System (BIOS) chip on a hard disk circuit board and mainly functions to control a magnetic head; the built-in ROM, i.e. the circuit board, has no BIOS chip, i.e. the ROM information exists on the disk, and the function is the same as that of the external ROM. For another example, the Seagate hard disk currently has only an external ROM, which contains information such as a circuit board and a magnetic head.

Firmware plays a vital role in the normal operation of a hard disk. After the firmware runs for a long time, the problem of large and small extent or direct damage can occur, so that the hard disk fails, and at the moment, the firmware needs to be repaired. The firmware repair needs to be modified or replaced in a covering mode according to the original firmware information, but the original firmware information cannot be identified by a computer operating system, common equipment and software cannot access the original firmware information, and the original firmware information is generally the core secret of each hard disk manufacturer and is not disclosed to the outside. Therefore, the workload of searching and collecting the original firmware information of the hard disk through the network is very large and time-consuming, and it cannot be guaranteed that the original firmware information matching the failed hard disk is found. Particularly, in the hard disk repair and electronic data recovery process of staff identification, the requirement uncertainty of hard disk firmware is high, and corresponding firmware data needs to be matched according to the time limit of a submission hard disk in a short time, so that the working requirement of the staff cannot be met through network searching. In order to meet the rapid and urgent work requirements of workers and better support the inspection and identification of the hard disk, it is very necessary to develop the work of collecting and backing up the hard disk firmware data in the early stage. At present, a comprehensive inspection tool in the industry can acquire the hard disk firmware, but the comprehensive inspection tool is not convenient enough in the aspects of hard disk firmware acquisition and backup and cannot be popularized and applied in a large range due to high specialty, high price, complex functions and complex operation.

The storage location of the hard disk firmware may vary according to the brand of the hard disk. For example, a west hard disk and a xijie hard disk, the locations of firmware storage of the two hard disks are generally located at two places, one place is in the ROM chip of the circuit board, and the other place is located on the negative track (i.e. the track in front of the zero track) of the hard disk. Taking western digital hard disk as an example, firmware information of western digital hard disk is mainly represented in the form of modules, and one module may record only one information or may record multiple information, so the sizes of modules are not consistent, and each module has a fixed position in the firmware area and is not stored continuously. The modules of the hard disk firmware mainly comprise the following types: management modules, configuration and configuration tables, defect lists, and work record tables, etc. The firmware management module comprises an initial diagnosis module, a servo motor rotation control module, a magnetic head positioning module, an information exchange module of a hard disk controller buffer memory and the like; the configuration and configuration table contains logical and physical information about disk space; the Defect List contains a permanent Defect List (P-List) for recording defects generated during the production of the hard disk, a Grown Defect List (G-List) for recording defects generated during the use of the hard disk, a firmware area Defect List (for recording defects generated during the firmware area of the hard disk), a track table (i.e., a compressed P-List) and a working record table (for recording auxiliary information during the production and operation of the hard disk). Taking the working principle of the west hard disk as an example, a part of firmware information of the west hard disk is stored in a ROM on a circuit board and is used for operating a disk firmware Area (SA) of the hard disk after the hard disk is powered on, and the other part of firmware information is stored on a disk track of the hard disk and is used for realizing access to user data. After the hard disk is loaded with a power supply, the main control chip of the circuit board loads the ROM module firstly, and then reads and loads the module of the disk firmware area of the hard disk. Specifically, the main control on the circuit board is initiated, the circuit board is initialized, the main data of the ROM is initialized, and after the initialization is completed, the action of loading the ROM module is executed. The main ROM module serial number (ID) and contents are as follows, where the ID of each module is represented by 16:

(1) Module 0A: the module comprises a head map corresponding to the current head;

(2) Module 0B: the module contains the location information (address and length) of each module in the ROM;

(3) Module 01: the module comprises form information of all module sizes and coordinates of the firmware area, including start and end position information;

(4) The module 30: the module is a firmware area decoder module and comprises position information of firmware defective sectors;

(5) Module 0D: the ROM firmware comprises a version number of ROM firmware and a plurality of flag bits;

(6) And a module 4F: the module contains firmware version number information;

(7) The module 47: the module contains boot adaptation parameter information of the firmware area, is mainly used for configuring electronic components of the firmware area, and is a key and only module for starting the hard disk.

The loading sequence of each ROM module is as follows: module 0B (for obtaining addresses and lengths of module 01 and ROM modules), module 0A (for obtaining a disk cavity head map), module 30 (for detecting firmware region translators), module 0D (for obtaining some configuration information), and module 4F (for obtaining version microcode information). If the module 47 cannot be loaded normally, then the reading and writing of the SA area is abnormal. The main control chip works firstly, because the work of the main control chip depends on the microprogram in the ROM, the microprogram in the ROM needs to be loaded into the main control for processing, and finally the processed information is loaded into the cache, and the level is the state of working in the circuit board. When the circuit board level works normally, the next level of work is carried out: disk > > connect head > > the spindle motor starts rotating and reaches rated speed > > the head is positioned to firmware area > > Load the microcode from firmware area and guide the module to Load the Register (LDR) (i.e. footprint (OVERLAYS)) > > correct all connected heads > > initialize the translator.

In summary, a set of complicated firmware loading, reading and self-checking links are provided before the hard disk is normally started, and the method is a key link for normal operation of the hard disk, and effective and complete firmware is very important for hard disk repair.

Based on the above problems, the present application provides a method, an apparatus, a device, and a storage medium for firmware backup of a hard disk, which provide resources for hard disk repair by reading firmware from hard disks of different brands, families, and models and establishing catalogs for storing firmware backup in a classified manner.

First, an application scenario of the solution provided in the present application will be described below.

Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application. As shown in fig. 1, in the application scenario, a hard disk 120 of the firmware to be backed up is placed in the channel port 110, and the client 130 backs up the firmware of the hard disk 120 through the channel port 110. For a specific implementation process of the client 130 backing up the firmware of the hard disk 120 through the channel port 110, reference may be made to the schemes of the following embodiments.

It should be noted that fig. 1 is only a schematic diagram of an application scenario provided in this embodiment, and this embodiment of the present application does not limit the devices included in fig. 1, and also does not limit the positional relationship between the devices in fig. 1. For example, in the application scenario shown in fig. 1, a data storage device may be further included, and the data storage device may be an external memory with respect to the client 130, or may be an internal memory integrated in the client 130.

In the following embodiments of the present application, firmware backup of the west hard disk and the xie hard disk is taken as an example for explanation.

Fig. 2 is a flowchart of a firmware backup method for a hard disk according to an embodiment of the present application, where the method according to the embodiment of the present application is applied to a client, the client is configured to execute a firmware backup interface rendered by a firmware backup application, the firmware backup interface is configured to present signal stream information of a channel port corresponding to the firmware backup interface, the channel port is used to place a hard disk of firmware to be backed up, and the channel port is an interaction channel between the hard disk and the client. The client may be an electronic device. As shown in fig. 2, the method of the embodiment of the present application includes:

s201, if signal flow information appears on the firmware backup interface, determining that a target hard disk of firmware to be backed up is placed in a channel port.

In this embodiment of the present application, exemplarily, fig. 3 (a) to 3 (c) are schematic structural diagrams of a channel port provided in an embodiment of the present application, as shown in fig. 3 (a) to 3 (c), the channel port is a box for placing a hard disk of firmware to be backed up, and the box includes main interfaces:

serial Advanced Technology Attachment (SATA) 3.0 hard disk slot 301 to SATA3.0 hard disk slot 304, for supporting hot-plug, 4 blocks of 2.5 inch or 3.5 inch hard disks may be inserted simultaneously;

the two SATA3.0 epitaxial interfaces 305 are used for connecting a hard disk and performing heat exchange repair or signal short circuit repair on the hard disk;

two standard square power outlets 306 for supplying power to two SATA3.0 extensions interfaces 305 (which are dedicated interfaces for one-key backup firmware);

a power input interface 307 for supplying power to the box, wherein the socket specification of the interface is a DC power adapter of 5.5x2.5 (unit: mm), the input voltage is required to be 16V-24V, and the output power is not lower than 90W;

a power switch button 308 for pressing the button to turn on the box, flipping it open and turning off the box;

two Universal Serial Bus (USB) 3.0 output interfaces 309 for connecting USB mobile hard disks;

a square USB3.1 input interface 310 for connecting a computer host;

the box also includes a decorative light 311, two port reset buttons 312.

Illustratively, the client is a desktop computer, and the client is connected to the box through the square USB3.1 input interface 310 to communicate with the hard disk of the firmware to be backed up placed on the SATA3.0 hard disk slot 301 to the SATA3.0 hard disk slot 304 of the box. In the firmware backup interfaces rendered by the firmware backup application of the client, corresponding firmware backup interfaces are respectively provided from the SATA3.0 hard disk slot 301 to the SATA3.0 hard disk slot 304 corresponding to the box, for example, the SATA3.0 hard disk slot 301 corresponds to a first firmware backup interface, the SATA3.0 hard disk slot 302 corresponds to a second firmware backup interface, the SATA3.0 hard disk slot 303 corresponds to a third firmware backup interface, and the SATA3.0 hard disk slot 304 corresponds to a fourth firmware backup interface. Assuming that a hard disk of firmware to be backed up is placed on the SATA3.0 hard disk slot 301 of the box in the powered-on state, that is, the hard disk is in the powered-on state, the box feeds back some micro-signal changes, such as voltage and current, corresponding to the SATA3.0 hard disk slot 301 to the client, the client presents signal flow information (corresponding to the micro-signal changes) on the first firmware backup interface corresponding to the SATA3.0 hard disk slot 301, and then the client determines that a target hard disk of firmware to be backed up is placed on the SATA3.0 hard disk slot 301.

S202, responding to the firmware backup operation input by the user through the firmware backup interface, and acquiring the identification information of the target hard disk.

After the client determines that the target hard disk of the firmware to be backed up is placed in the channel port, a user can input the firmware backup operation through a firmware backup interface corresponding to the client, and accordingly, the client responds to the firmware backup operation input by the user through the firmware backup interface and acquires the identification information of the target hard disk. The identification information of the target hard disk is, for example, the model, serial number, firmware version, and capacity of the hard disk. For obtaining the identification information of the target hard disk, reference may be made to related technologies or subsequent embodiments, which are not described herein again.

S203, according to the identification information, sending a firmware backup command to the target hard disk.

After obtaining the identification information of the target hard disk, the client may send a firmware backup command to the target hard disk according to the identification information of the target hard disk. For example, if the target hard disk is determined to be a west hard disk according to the identification information of the target hard disk, a firmware backup command is sent to the west hard disk. It is understood that the firmware backup command is a command that the target hard disk can support. As to how to send the firmware backup command to the target hard disk according to the identification information, reference may be made to related technologies or subsequent embodiments, which are not described herein again.

Further, sending the firmware backup command to the target hard disk according to the identification information may include: determining a key corresponding to the target hard disk according to the identification information; verifying identity information with the target hard disk based on the secret key; and when the identity information passes the verification, sending a firmware backup command to the target hard disk according to the identification information.

Illustratively, a program (also referred to as a factory program) provided by a hard disk manufacturer for upgrading the firmware of the hard disk is used for interacting with the hard disk, the communication between the hard disk and the factory program is monitored in real time through a bus analyzer, when a protocol command packet sent by the factory program enables the hard disk to open the access right of the firmware area, the protocol command packet is captured and analyzed, and the key of the hard disk is obtained in a decompilated mode. For example, after obtaining the identification information of the target hard disk, the client may verify the identity information by using the key corresponding to the west hard disk and the west hard disk, that is, send the command corresponding to the key to the west hard disk, assuming that the target hard disk is determined to be the west hard disk according to the identification information. When receiving the return information that the western digital hard disk passes the key verification (namely identity information verification), the client sends a corresponding firmware backup command to the western digital hard disk to acquire the firmware information of the western digital hard disk.

And S204, receiving the firmware information from the target hard disk.

After the client sends the firmware backup command to the target hard disk, the target hard disk returns the corresponding firmware information to the client through the channel port according to the firmware backup command, and the client receives the firmware information. It can be understood that different firmware backup commands correspond to different firmware information, and the client acquires the corresponding firmware information from the target hard disk by sending the different firmware backup commands.

And S205, storing the firmware information into a file directory corresponding to the target hard disk.

After the client obtains the firmware information of the target hard disk, the client can store the firmware information into a file directory corresponding to the target hard disk in the client. For how to store the firmware information in the file directory corresponding to the target hard disk, reference may be made to related technologies or subsequent embodiments, which are not described herein again.

After the firmware information of the target hard disk is stored in the file directory corresponding to the target hard disk in the client, when the target hard disk fails, the firmware of the target hard disk can be repaired by using the firmware information of the target hard disk stored in the client.

The firmware backup method of the hard disk is applied to a client, the client is used for executing a firmware backup interface obtained by rendering of a firmware backup application, the firmware backup interface is used for presenting signal stream information of a channel port corresponding to the firmware backup interface, the channel port is used for placing the hard disk of firmware to be backed up, the channel port is an interactive channel between the hard disk and the client, if the signal stream information is presented on the firmware backup interface of the client, a target hard disk with the firmware to be backed up in the channel port is determined, the client responds to firmware backup operation input by a user through the firmware backup interface, acquires identification information of the target hard disk, sends a firmware backup command to the target hard disk according to the identification information, receives the firmware information from the target hard disk, and stores the firmware information into a file directory corresponding to the target hard disk. According to the embodiment of the application, the firmware information of the target hard disk is acquired through the firmware backup interface of the client, namely, the service of one-key backup of the firmware information of the hard disk is provided for a user, so that the requirement of the user on the backup of the firmware information of the hard disk can be quickly met on the basis of accurately backing up the firmware information of the hard disk.

Fig. 4 is a flowchart of a firmware backup method for a hard disk according to another embodiment of the present application, where the method according to the embodiment of the present application is applied to a client. On the basis of the above embodiments, the embodiments of the present application further describe how to perform firmware backup of a hard disk. As shown in fig. 4, the method of the embodiment of the present application may include:

s401, if signal flow information exists on the firmware backup interface, determining that a target hard disk of firmware to be backed up is placed in the channel port.

For a detailed description of this step, reference may be made to the description related to S201 in the embodiment shown in fig. 2, and details are not described here.

S402, responding to the firmware backup operation input by the user through the firmware backup interface, and sending a command for reading hard disk information to the target hard disk.

Illustratively, a command to read hard disk information is such as 0xEC in hexadecimal representation. The client sends a 0xEC command to the target hard disk in response to the firmware backup operation input by the user through the firmware backup interface, so as to read the hard disk information.

S403, hard disk information from the target hard disk is received, wherein the hard disk information comprises identification information.

Illustratively, after a client sends a command for reading hard disk information to a target hard disk, the hard disk returns the hard disk information to the client according to the command, and the client displays the received hard disk information on a firmware backup interface, wherein the hard disk information contains identification information. Exemplarily, if the received hard disk information is: hard disk model: WDC WD20EZRZ-00Z5HB0; hard disk serial number: WD-WCC4M1FV8XF3; hard disk firmware version: 80.00A80; hard disk capacity: 2TB, the target hard disk can be determined to be a Western digital hard disk according to the hard disk model. In the process of acquiring the hard disk information, the client sends a key command corresponding to the western digital hard disk to verify the identity information, and after the identity information is verified, the client automatically detects and identifies the RAM, the segment bit table, the ROM and the firmware area directory of the western digital hard disk (for example, reads the parameters of the firmware) to confirm that all information of the western digital hard disk can be normally read, and the firmware area can be normally accessed to send a firmware backup command to the western digital hard disk. Exemplarily, if the received hard disk information is: hard disk type: ST3500418AS; hard disk serial number: 5VM72755; hard disk firmware version: CC38; hard disk capacity: 465.76G, it can be determined that the target hard disk is a xijie hard disk according to the hard disk model. In the process of obtaining the hard disk information, the client side sends a secret key command corresponding to the Seagate hard disk to verify the identity information, and after the identity information is verified, the client side automatically detects and identifies the RAM, the segment bit table, the ROM, the modules in the cache and the firmware area system files of the Seagate hard disk to confirm that all information of the Western hard disk can be read normally, and the firmware area can be accessed normally to send a firmware backup command to the Seagate hard disk.

S404, determining the firmware to be backed up corresponding to the target hard disk according to the identification information.

The firmware to be backed up comprises at least one of a module, a ROM, a magnetic track and a system file.

Exemplarily, if the target hard disk is a west hard disk, determining the firmware to be backed up corresponding to the west hard disk includes: the device comprises a ROM module positioned in a ROM chip on a circuit board, a firmware module positioned in a negative magnetic track on a disk and all non-empty negative magnetic tracks; if the target hard disk is the Seagate hard disk, determining the firmware to be backed up corresponding to the Seagate hard disk comprises the following steps: ROM information located in a ROM chip on a circuit board, module information located in a cache, a system file located on a negative track (SYSTEM FILES, SYSFILES).

S405, according to the firmware to be backed up, sending a firmware backup command to the target hard disk.

The firmware backup command is used for indicating that corresponding firmware information is acquired from a storage position of the firmware to be backed up on the target hard disk.

After determining the firmware to be backed up corresponding to the target hard disk, the client may send a firmware backup command to the target hard disk according to the firmware to be backed up. Exemplarily, if the target hard disk is a west hard disk and the firmware to be backed up is a module, the client sends a module backup command to the west hard disk. Optionally, a timeout for sending the firmware backup command to the target hard disk may be set to ensure that the hard disk will not make an error during the backup.

S406, receiving the firmware information from the target hard disk.

For a detailed description of this step, reference may be made to the related description of S204 in the embodiment shown in fig. 2, and details are not repeated here.

Optionally, after sending the firmware backup command to the target hard disk, the method further includes: and if the firmware information corresponding to the firmware to be backed up is not acquired, sending a firmware backup command to the target hard disk through COM.

Illustratively, the target hard disk is a west hard disk, and after the west hard disk is powered on, a ROM module of the west hard disk is usually loaded into the cache, and ROM firmware information in the cache can be obtained by sending a firmware backup command corresponding to the ROM to the west hard disk. If the western digital hard disk is in a state that the data in the cache cannot be accessed, a firmware backup command corresponding to the ROM can be sent to the western digital hard disk in a mode of connecting the COM port, and the ROM firmware information is backed up.

Based on steps S405 and S406, the west hard disk and the xie hard disk are specifically described as examples. Exemplarily, if the target hard disk is a west hard disk, the firmware information of the west hard disk is obtained through the following three steps:

(1) And sending a firmware backup command corresponding to the module to the western digital hard disk to backup the module of the western digital hard disk, and acquiring the ID number and the size of each module bottom layer.

Specifically, the ID, the offset Address of the firmware Block Address (ABA), and the size of each module may be obtained by accessing the module 01 directory of the west hard disk, so as to backup each module. When the module 01 cannot be used (for example, a bad track appears at the module 01 position), searching is carried out on the track for each module ID, so that each module of the module is backed up in an ID acquisition mode. Exemplarily, table 4 is specific information of each module of the west hard disk provided in an embodiment of the present application, and as shown in table 4, each module includes a module ID (hexadecimal representation), a module description, a module level, a module ABA offset address, and a module size.

TABLE 4

Wherein, the meaning of each module level is respectively as follows:

a: a base module, each disk being unique;

b: the main modules are generally the same as the hard disks in the same family;

c: a secondary module that can be cleared directly;

d: the auxiliary module does not influence the normal operation of the hard disk, but is used for some optional functions: such as Self-scanning (Self-Scan);

d: affecting data reading;

s: affecting the starting of the hard disk;

r: self-check/self-restore procedure call.

The meanings of the corresponding module levels after the module levels are combined are respectively as follows:

as: the hard disk operates as a key and unique module, including adaptation data. The damaged hard disks themselves cannot be repaired, only the original content can be tried to be read from the copy, and if and only if in the worst case they can be tried to be overwritten with firmware modules of the same family and the same model and version, there is a possibility that the disks are knocked and cannot be repaired permanently.

Ad: and the user data key and unique module comprises a decoding table module. If the damaged hard disk is repaired without data, the damaged hard disk can be overwritten by the copy of other hard disks; if it is data recovery, it is necessary to attempt to recover them by repeatedly reading the original tables.

B: the microcode boot module covers areas such as area allocation tables, hard disk IDs, etc. These modules are not unique to each hard disk, but are unique to a family or even a particular model. If damaged, it can be replaced with a module of the same hard disk of other firmware version.

C: secondary tables, such as SMART tables, G-List tables, etc., may be cleared. The recovery of these modules can be usually completed only by using the working mechanism of the hard disk itself, and it is also allowable to copy the corresponding modules from other hard disks for overwriting (preferably, the same model in the same family), which does not affect the operation of the hard disk and the integrity of user data.

And Dd: and the auxiliary module does not influence the hard disk operation and the integrity of user data but participates in the recovery of other key modules. Such as the original decoder (which may be used to recover the decoder).

Dr: the auxiliary module is not needed for normal hard disk operation and participates in executing hard disk maintenance functions, such as self-checking or calibration.

(2) And sending a firmware backup command corresponding to the ROM to the Western hard disk to backup the ROM of the Western hard disk, and respectively obtaining the module ID and the module size in the ROM and the ROM bottom layer.

Specifically, after the west hard disk is powered on, the ROM module of the west hard disk is usually loaded into the cache, and the ROM firmware information in the cache can be obtained by sending a firmware backup command corresponding to the ROM to the west hard disk. If the western digital hard disk is in a state that the data in the cache cannot be accessed, a firmware backup command corresponding to the ROM can be sent to the western digital hard disk in a mode of connecting the COM port, and the ROM firmware information is backed up. The backup ROM module includes: a 0A module (i.e., a head bitmap module), a 0B module (i.e., a ROM directory module 1), a 20B module (i.e., a ROM directory module 2), a 30 module (i.e., an SA translation module), a 47 module (i.e., an SA adaptation module), a 0D module (i.e., a ROM configuration module), and a 4F module (i.e., a micro-program firmware version module).

(3) The method comprises the steps of sending a firmware backup command corresponding to a magnetic track to the western digital hard disk, backing up the magnetic track of the western digital hard disk, and acquiring the magnetic track used by firmware information according to the size of the magnetic track divided by a disk by identifying all firmware bottom layer information positioned in a negative magnetic track.

Specifically, the position of the firmware area of the negative magnetic track is determined according to the module parameters, the magnetic track of the used firmware area is automatically identified, the unused area is eliminated, and the magnetic track data at the corresponding position is read for backup through reading the disk segment bit table module according to the description of the initial position, the end position and the sector number of each magnetic track in the module.

Exemplarily, if the target hard disk is a shiagate hard disk, the firmware information of the shiagate hard disk is obtained through the following three steps:

(1) And sending a firmware backup command corresponding to the module to the Seagate hard disk to backup the module of the Seagate hard disk and obtain the module information in the cache.

Specifically, a module ID number is obtained and a module size of useful module information is intercepted by sending a hard disk Advanced Technology Attachment (ATA) firmware backup command corresponding to the module to the xijie hard disk, extracting the module from the cache. If the corresponding module information cannot be obtained from the cache of the xie hard disk, the module information can be read by sending a firmware backup command corresponding to the module to the xie hard disk in a mode of connecting a COM port, for example, the module information can be read by a preset frequency of 38400. For example, for a xie hard disk with a firmware lock, firmware unlocking needs to be performed on the xie hard disk, and firmware information corresponding to a module of the xie hard disk can be obtained in the above manner.

(2) And sending a firmware backup command corresponding to the ROM to the Seagate hard disk to backup the ROM of the Seagate hard disk and obtain backup ROM information.

Specifically, the ATA firmware backup command corresponding to the ROM is sent to the Seagate hard disk, relevant ROM information is extracted from the cache, and the backup ROM information is obtained after the relevant ROM information is intercepted according to the size of the ROM. If the ROM information can not be acquired by sending the ATA firmware backup command, the firmware backup command corresponding to the ROM can be sent to the Seagate hard disk in a mode of connecting the COM port, the information in the ROM on the circuit board is directly read, and the backup ROM is acquired. For example, for a xie hard disk with a firmware lock, firmware unlocking of the xie hard disk is required to obtain ROM information of the xie hard disk in the above manner.

(3) And backing up the system file of the Seagate hard disk by sending a firmware backup command corresponding to the system file to the Seagate hard disk to obtain a backed-up system file.

Specifically, the ATA firmware backup command corresponding to the ROM is sent to the Seagate hard disk, the system file is directly extracted from the firmware area, and the system file is intercepted according to the volume number and the file size of the system file to obtain the backed-up system file. If the system file cannot be obtained by sending the ATA firmware backup command, the firmware backup command corresponding to the system file can be sent to the Seagate hard disk in a mode of connecting the COM port, the volume number and the size (displayed by 16-system code) of the required system file are obtained, and the system file is intercepted to obtain the backed-up system file. For example, for a xie hard disk with a firmware lock, the firmware of the xie hard disk needs to be unlocked, and the system file of the xie hard disk can be obtained in the above manner.

S407, establishing a hierarchical storage file directory corresponding to the target hard disk according to the identification information of the target hard disk and the firmware to be backed up corresponding to the target hard disk.

Illustratively, the client acquires the corresponding brand, family and model according to the identification information of the target hard disk, establishes corresponding folders according to the three grades, the highest level is the brand folder, the next level is the family folder, and the lowest level is the model folder, and then establishes the folder corresponding to the firmware to be backed up according to the firmware to be backed up corresponding to the target hard disk. Illustratively, for each model of Seagate hard disk, the model folder comprises three folders of ROM, module and system file; for each type of Western digital hard disk, the type folder comprises three types of folders of ROM, module and magnetic track.

S408, storing the firmware information to a hierarchical storage file directory corresponding to the target hard disk.

After the firmware information of the target hard disk is obtained, the firmware information can be saved to a hierarchical storage file directory corresponding to the target hard disk in the client.

Optionally, the firmware information of the target hard disk may be backed up by checking the firmware to be backed up of the target hard disk at one time on a firmware backup interface of the client. For example, if the target hard disk is a west hard disk, the one-time checking of the firmware to be backed up on the firmware backup interface of the client may include: the module, the magnetic track and the ROM realize one-key quick backup of the firmware information of all Western digital hard disks.

Optionally, the firmware information of the target hard disk stored by the client can be uploaded to a server for storing the firmware information of hard disks of all models through a network to form a firmware database, and the hard disk firmware information collected by each client is screened and duplicated in the uploading process, then is automatically uploaded to the server and can be downloaded and called at any time, so that the firmware information of the target hard disk can be conveniently shared and used in different places at a later stage.

The firmware backup method of the hard disk is applied to a client, if signal stream information appears on a firmware backup interface of the client, a target hard disk with firmware to be backed up is determined to be placed in a channel port, a command for reading hard disk information is sent to the target hard disk in response to a firmware backup operation input by a user through the firmware backup interface, the hard disk information from the target hard disk is received, the hard disk information comprises identification information, the firmware to be backed up corresponding to the target hard disk is determined according to the identification information, the firmware to be backed up comprises at least one of a module, a ROM, a magnetic track and a system file, a firmware backup command is sent to the target hard disk according to the firmware to be backed up, the firmware information from the target hard disk is received, a hierarchical storage file directory corresponding to the target hard disk is established according to the identification information of the target hard disk and the firmware to be backed up corresponding to the target hard disk, and the firmware information is stored in the hierarchical storage file directory corresponding to the target hard disk. According to the embodiment of the application, the firmware information of the target hard disk is acquired through the firmware backup interface of the client, namely, the service of one-key backup of the firmware information of the hard disk is provided for a user, so that the requirement of the user on the backup of the firmware information of the hard disk can be quickly met on the basis of accurately backing up the firmware information of the hard disk.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

Fig. 5 is a schematic structural diagram of a firmware backup device for a hard disk, which is applied to a client, where the client is configured to execute a firmware backup interface rendered by a firmware backup application, the firmware backup interface is configured to present signal stream information of a channel port corresponding to the firmware backup interface, the channel port is used for placing the hard disk of the firmware to be backed up, and the channel port is an interaction channel between the hard disk and the client. As shown in fig. 5, the firmware backup apparatus 500 for a hard disk according to the embodiment of the present application includes: a determining module 501, an obtaining module 502, a sending module 503, a receiving module 504 and a saving module 505. Wherein:

the determining module 501 is configured to determine, if signal flow information exists on the firmware backup interface, that a target hard disk of the firmware to be backed up is placed in the channel port.

The obtaining module 502 is configured to obtain identification information of the target hard disk in response to a firmware backup operation input by a user through a firmware backup interface.

A sending module 503, configured to send a firmware backup command to the target hard disk according to the identification information.

A receiving module 504, configured to receive firmware information from the target hard disk.

A saving module 505, configured to save the firmware information to a file directory corresponding to the target hard disk.

In some embodiments, the obtaining module 502 may be specifically configured to: sending a command for reading hard disk information to a target hard disk; and receiving hard disk information from the target hard disk, wherein the hard disk information comprises identification information.

Optionally, the sending module 503 may be specifically configured to: determining firmware to be backed up corresponding to the target hard disk according to the identification information, wherein the firmware to be backed up comprises at least one of a module, a ROM, a magnetic track and a system file; and sending a firmware backup command to the target hard disk according to the firmware to be backed up, wherein the firmware backup command is used for indicating that corresponding firmware information is acquired from the storage position of the firmware to be backed up in the target hard disk.

In some embodiments, the sending module 503, after sending the firmware backup command to the target hard disk, may further be configured to: and if the firmware information corresponding to the firmware to be backed up is not acquired, sending a firmware backup command to the target hard disk through COM.

Optionally, the sending module 503 may be specifically configured to: determining a key corresponding to the target hard disk according to the identification information; verifying identity information with the target hard disk based on the secret key; and when the identity information passes the verification, sending a firmware backup command to the target hard disk according to the identification information.

Optionally, the saving module 505 is specifically configured to: establishing a hierarchical storage file directory corresponding to the target hard disk according to the identification information of the target hard disk and the firmware to be backed up corresponding to the target hard disk; and storing the firmware information to a hierarchical storage file directory corresponding to the target hard disk.

The apparatus of this embodiment may be configured to implement the technical solution of any one of the above-mentioned method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.

Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application. Illustratively, the electronic device may be provided as a computer. Referring to fig. 6, electronic device 600 includes a processing component 601 that further includes one or more processors and memory resources, represented by memory 602, for storing instructions, such as application programs, that are executable by processing component 601. The application programs stored in memory 602 may include one or more modules that each correspond to a set of instructions. Further, the processing component 601 is configured to execute instructions to perform any of the method embodiments described above.

The electronic device 600 may also include a power component 603 configured to perform power management for the electronic device 600, a wired or wireless network interface 604 configured to connect the electronic device 600 to a network, and an input-output (I/O) interface 605. The electronic device 600 may operate based on an operating system, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM or the like, stored in the memory 602.

The application also provides a computer-readable storage medium, in which computer execution instructions are stored, and when a processor executes the computer execution instructions, the scheme of the firmware backup method for the hard disk is implemented.

The present application also provides a computer program product comprising a computer program which, when executed by a processor, implements an aspect of the firmware backup method for a hard disk as described above.

The computer-readable storage medium may be implemented by any type of volatile or non-volatile storage device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. Readable storage media can be any available media that can be accessed by a general purpose or special purpose computer.

An exemplary readable storage medium is coupled to the processor such the processor can read information from, and write information to, the readable storage medium. Of course, the readable storage medium may also be an integral part of the processor. The processor and the readable storage medium may reside in an Application Specific Integrated Circuits (ASIC). Of course, the processor and the readable storage medium may also reside as discrete components in a firmware backup device on a hard disk.

Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims (10)

1. A firmware backup method of a hard disk is applied to a client, the client is used for executing a firmware backup interface obtained by rendering of a firmware backup application, the firmware backup interface is used for presenting signal flow information of a channel port corresponding to the firmware backup interface, the channel port is used for placing the hard disk of firmware to be backed up, the channel port is an interactive channel between the hard disk and the client, and the firmware backup method comprises the following steps:

if signal flow information appears on the firmware backup interface, determining that a target hard disk of firmware to be backed up is placed in the channel port;

responding to a firmware backup operation input by a user through the firmware backup interface, and acquiring identification information of the target hard disk;

sending a firmware backup command to the target hard disk according to the identification information;

receiving firmware information from the target hard disk;

and storing the firmware information to a file directory corresponding to the target hard disk.

2. The method of claim 1, wherein the obtaining the identification information of the target hard disk comprises:

sending a command for reading hard disk information to the target hard disk;

and receiving hard disk information from the target hard disk, wherein the hard disk information comprises the identification information.

3. The method for firmware backup of hard disk according to claim 1, wherein the sending a firmware backup command to the target hard disk according to the identification information comprises:

determining firmware to be backed up corresponding to the target hard disk according to the identification information, wherein the firmware to be backed up comprises at least one of a module, a Read Only Memory (ROM), a magnetic track and a system file;

and sending a firmware backup command to the target hard disk according to the firmware to be backed up, wherein the firmware backup command is used for indicating that corresponding firmware information is acquired from the storage position of the firmware to be backed up in the target hard disk.

4. The method for firmware backup of hard disk according to claim 3, further comprising, after sending the firmware backup command to the target hard disk:

and if the firmware information corresponding to the firmware to be backed up is not acquired, sending a firmware backup command to the target hard disk through a serial communication port COM.

5. The method for firmware backup of hard disk according to any of claims 1 to 4, wherein the sending a firmware backup command to the target hard disk according to the identification information comprises:

determining a key corresponding to the target hard disk according to the identification information;

verifying identity information with the target hard disk based on the secret key;

and when the identity information passes the verification, sending a firmware backup command to the target hard disk according to the identification information.

6. The method for backing up firmware on a hard disk according to any one of claims 1 to 4, wherein the saving the firmware information to the file directory corresponding to the target hard disk includes:

establishing a hierarchical storage file directory corresponding to the target hard disk according to the identification information of the target hard disk and the firmware to be backed up corresponding to the target hard disk;

and storing the firmware information to a hierarchical storage file directory corresponding to the target hard disk.

7. A firmware backup device of a hard disk is applied to a client, the client is used for executing a firmware backup interface obtained by rendering of a firmware backup application, the firmware backup interface is used for presenting signal flow information of a channel port corresponding to the firmware backup interface, the channel port is used for placing the hard disk of firmware to be backed up, the channel port is an interactive channel between the hard disk and the client, and the firmware backup device comprises:

the determining module is used for determining that a target hard disk of firmware to be backed up is placed in the channel port if the firmware backup interface presents signal flow information;

the acquisition module is used for responding to the firmware backup operation input by a user through the firmware backup interface and acquiring the identification information of the target hard disk;

the sending module is used for sending a firmware backup command to the target hard disk according to the identification information;

the receiving module is used for receiving the firmware information from the target hard disk;

and the storage module is used for storing the firmware information into a file directory corresponding to the target hard disk.

8. An electronic device, comprising: a memory and a processor;

the memory is to store program instructions;

the processor is used for calling the program instructions in the memory to execute the firmware backup method of the hard disk according to any one of claims 1 to 6.

9. A computer-readable storage medium having stored thereon computer program instructions which, when executed, implement the firmware backup method for a hard disk according to any one of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that the computer program, when executed by a processor, implements a firmware backup method for a hard disk according to any of claims 1 to 6.

Images