CN120540917A

CN120540917A - Hard disk testing method, device, equipment and storage medium

Info

Publication number: CN120540917A
Application number: CN202510667871.7A
Authority: CN
Inventors: 刘伯书; 樊淋杰
Original assignee: Suzhou Metabrain Intelligent Technology Co Ltd
Current assignee: Suzhou Metabrain Intelligent Technology Co Ltd
Priority date: 2025-05-22
Filing date: 2025-05-22
Publication date: 2025-08-26

Abstract

The application provides a hard disk testing method, a device, equipment and a storage medium, which can be applied to the technical field of hard disk testing. The hard disk testing method includes the steps of responding to a test request for a target hard disk, executing a target error injection instruction matched with a target sector in the target hard disk, injecting logic errors into the target sector by the target error injection instruction, writing first preset data into the target sector under the condition that execution of the target error injection instruction is confirmed, executing reading operation on a target spare sector with a mapping relation with the target sector according to the mapping relation between the target hard disk sector and the spare sector under the condition that bad sector information of the target hard disk is confirmed to indicate that the target sector is a bad sector, obtaining first read data, and comparing the first read data with the first preset data to confirm a first test result for the target hard disk.

Description

Hard disk testing method, device, equipment and storage medium

Technical Field

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

Background

With the development of hard disk technology and the improvement of hard disk demands, hard disks are widely used. The hard disk is used as a core storage medium and is used for storing key data such as a service system, a database, user information and the like, and if the hard disk fails, the data can be lost or service is interrupted. Therefore, in order to improve data reliability and service stability, it is necessary to improve the robustness and stability of the hard disk.

However, the maintenance of the hard disk usually analyzes and processes the problems after the problems occur in the hard disk, so that the defects of the hard disk cannot be found before the problems occur, and the stability and the robustness of the hard disk are low.

Disclosure of Invention

In view of the foregoing, the present application provides a hard disk testing method, apparatus, device, medium, and program product.

According to a first aspect of the present application, there is provided a hard disk test method, including executing a target error injection instruction matching a target sector in a target hard disk in response to receiving a test request for the target hard disk, the target error injection instruction being used to inject a logical error into the target sector, writing first preset data into the target sector if it is determined that the execution of the target error injection instruction is completed, executing a read operation on a target spare sector having the mapping relation with the target sector according to a mapping relation between the bad sector and the spare sector of the target hard disk if it is determined that the bad sector of the target hard disk is a bad sector, to obtain first read data, and comparing the first read data with the first preset data to determine a first test result for the target hard disk.

The second aspect of the application provides a hard disk testing device, which comprises a target error injection module, a first writing module and a first reading module, wherein the target error injection module is used for responding to a test request for a target hard disk and executing a target error injection instruction matched with a target sector in the target hard disk, the target error injection instruction is used for injecting logic errors into the target sector, the first writing module is used for writing first preset data into the target sector when the execution of the target error injection instruction is determined to be completed, the first reading module is used for executing reading operation on a target spare sector which has the mapping relation with the target sector according to the mapping relation between the bad sector and the spare sector of the target hard disk when the bad sector information of the target hard disk is determined to be the bad sector, and the comparison determining module is used for comparing the first read data with the first preset data and determining a first testing result aiming at the target hard disk.

A third aspect of the application provides an electronic device comprising one or more processors and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method.

A fourth aspect of the application also provides a computer readable storage medium having stored thereon a computer program or instructions which when executed by a processor performs the steps of the above method.

The fifth aspect of the application also provides a computer program product comprising a computer program or instructions which, when executed by a processor, carries out the steps of the method described above.

According to the embodiment of the application, the logic error is actively injected into the target sector of the target hard disk before the target hard disk is used, so that the scene that the bad sector occurs in the actual use process of the target hard disk can be simulated. And the first preset data is written into the target sector after the logic error is injected so as to simulate the scene that a user executes writing operation on the bad sector and execute reading operation on the target spare sector of the target sector, so that whether the target hard disk can map the operation on the bad sector to the spare sector can be verified, the test on the remapping capacity of the target hard disk is realized, the processing mechanism of the target hard disk when the problem of the bad sector is processed is verified before the target hard disk is used, and the robustness and the stability of the hard disk are improved.

Drawings

The foregoing and other objects, features and advantages of the application will be apparent from the following description of embodiments of the application with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an application scenario diagram of a hard disk testing method, apparatus, device, medium and program product according to an embodiment of the application;

FIG. 2 schematically illustrates a flow chart of a hard disk testing method according to an embodiment of the application;

FIG. 3 schematically illustrates a flow chart of determining the protocol type of a target hard disk according to an embodiment of the application;

FIG. 4 schematically illustrates a change of the error count value according to an embodiment of the present application;

FIG. 5 schematically illustrates a mapping relationship according to an embodiment of the present application;

FIG. 6 schematically illustrates a flow chart of a hard disk testing method according to an embodiment of the application;

FIG. 7 schematically shows a block diagram of a hard disk test apparatus according to an embodiment of the present application, and

Fig. 8 schematically shows a block diagram of an electronic device adapted to implement a hard disk test method according to an embodiment of the application.

Detailed Description

Hereinafter, embodiments of the present application will be described with reference to the accompanying drawings. It should be understood that the description is only illustrative and is not intended to limit the scope of the application. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the application. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the present application.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a convention should be interpreted in accordance with the meaning of one of skill in the art having generally understood the convention (e.g., "a system having at least one of A, B and C" would include, but not be limited to, systems having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

With the rapid development of hard disk technology and rapid improvement of hard disk requirements, hard disks are widely applied to various application scenes of life, and requirements on stability and robustness of the hard disks are higher and higher. However, in the use process of the hard disk, after the hard disk is in a problem, the problem of the hard disk is analyzed and processed, so that the possible problem of the hard disk cannot be actively prevented before the hard disk is used, and the stability and the robustness of the hard disk are low.

In order to verify the stability and the robustness of a hard disk in advance, the embodiment of the application provides a hard disk testing method, which comprises the steps of responding to a test request for a target hard disk, executing a target error injection instruction matched with a target sector in the target hard disk, injecting logic errors into the target sector by the target error injection instruction, writing first preset data into the target sector under the condition that the execution of the target error injection instruction is confirmed, executing a read operation on the target spare sector with a mapping relation with the target sector according to the mapping relation between the sector of the target hard disk and the spare sector under the condition that the bad sector information of the target hard disk is confirmed to be the bad sector, obtaining first read data, comparing the first read data with the first preset data, and confirming a first test result for the target hard disk.

According to the embodiment of the application, the problem of sector damage of the hard disk in the actual use process is simulated by logically filling errors into the target sector, and the spare sector of the target sector can replace the work of the target sector under the condition that the target sector is verified to be a bad sector by writing data into the target sector, so that the processing mechanism of the target hard disk when the target hard disk encounters the problem of damage is verified before the target hard disk is formally put into use, and the robustness and the stability of the hard disk are improved.

Fig. 1 schematically illustrates an application scenario diagram of a hard disk testing method, apparatus, device, medium and program product according to an embodiment of the application.

As shown in fig. 1, the application scenario 100 according to this embodiment may include a first server 110 and a second server 120, where the first server 110 includes a target hard disk 111 to be tested.

The first server 110 may be a server for providing a test environment for the target hard disk 111. The second server 120 may be a server for providing a test service, for example, testing a target hard disk 111 in the first server 110, and determining a test result for the target hard disk 111.

It should be noted that the hard disk testing method provided in the embodiment of the present application may be generally executed by the second server 120. Accordingly, the hard disk testing device provided by the embodiment of the application can be generally arranged in the second server 120. The hard disk testing method provided by the embodiment of the application may also be performed by a server or a server cluster that is different from the second server 120 and is capable of communicating with the first server 110 and/or the second server 120. Accordingly, the hard disk testing device provided in the embodiment of the present application may also be disposed in a server or a server cluster different from the second server 120 and capable of communicating with the first server 110 and/or the second server 120.

It should be understood that the number of first servers, second servers, and hard disks in fig. 1 are merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The hard disk testing method of the application embodiment will be described in detail below with reference to fig. 2 to 6 based on the scenario described in fig. 1.

Fig. 2 schematically shows a flow chart of a hard disk testing method according to an embodiment of the application.

As shown in FIG. 2, the hard disk testing method of the embodiment includes operations S210-S240.

In response to receiving the test request for the target hard disk, a target debug instruction matching a target sector in the target hard disk is executed in operation S210.

Before the hard disk is put into use, when the robustness and stability of the hard disk are tested, the target hard disk to be tested can be placed in a first server capable of providing a test environment, a test request for the target hard disk is sent to a second server providing test service by the first server, and the second server tests the target hard disk in response to receiving the test request.

When the target hard disk is tested, the situation that the target hard disk generates a logic bad sector in the actual application process can be simulated by executing a target error injection instruction for injecting logic errors into the target sector, so that an error processing mechanism of the target hard disk is tested.

When a target sector is selected from a plurality of sectors of the target hard disk, the target sector may be selected randomly from the plurality of sectors, or a sector designated by the user may be determined as the target sector. For example, an input box for inputting a sector address may be displayed at the user's terminal, and the target sector may be determined based on the sector address input by the user in the input box.

Before executing the error injection instruction, the hard disk type of the target hard disk can be determined firstly because the instruction types corresponding to different hard disk types are different, and then the corresponding target error injection instruction can be determined according to the hard disk type of the target hard disk.

In operation S220, in case it is determined that the execution of the target error instruction is completed, first preset data is written to the target sector.

Under the condition that the execution of the target error injection instruction is completed, the target sector is injected with logic errors, at the moment, the target sector cannot normally execute read-write operation, first preset data can be written into the target sector, and the processing mode of the target hard disk in processing the write operation aiming at the logic bad sector is verified.

In operation S230, in the case where it is determined that the bad sector information of the target hard disk indicates that the target sector is a bad sector, a read operation is performed on the target spare sector having a mapping relationship with the target sector according to the mapping relationship between the target hard disk sector and the spare sector, to obtain the first read data.

Since the hard disk generally has a bad block management mechanism, for example, bad sector information is updated according to the real-time status of each sector in the hard disk, it can be determined whether the target hard disk has identified the target sector as a bad sector according to the bad sector information of the target hard disk.

The bad sector information can store the bad sector address of each bad sector, so that whether the bad sector information represents that the target sector is a bad sector can be determined according to the bad sector address and the sector address of the target sector, and whether the target hard disk updates the bad sector information in real time can be determined. For example, in the case where the sector address of the target sector is included in the bad sector address, it may be determined that the bad sector information indicates that the target sector is a bad sector.

In some embodiments, the bad sector information may be stored in a predetermined area of the target hard disk in the form of a data table, such as a bad sector table. Therefore, the bad sector table can be obtained according to the preset area corresponding to the target hard disk, and whether the target hard disk has identified the target sector as a bad sector is determined according to the bad sector table.

To ensure the stability and robustness of the hard disk, the hard disk typically has remapping capabilities, enabling operations for logically bad sectors to be mapped into other sectors, with other sectors being utilized to handle the operations.

For example, when the target hard disk has the remapping capability, the target hard disk determines a target spare sector for replacing the target sector from a plurality of spare sectors, maps the write operation for the target sector into the target spare sector, and writes first preset data into the target spare sector to replace the target sector with the target spare sector.

In some embodiments, the mapping between bad sectors and spare sectors may be stored in bad sector information, such as in a bad sector table. In the case where the bad sector information indicates that the target sector is a bad sector, a target spare sector corresponding to the target sector may be determined from the bad sector information.

Under the condition that the target hard disk has remapping capacity, the remapping capacity of the target hard disk can be tested, so that the remapping capacity of the target hard disk in the using process is ensured, and the stability and the robustness of the target hard disk are improved.

When the remapping capacity of the target hard disk is tested, a read operation can be performed on the target spare sector, the stored data in the target spare sector is read as first read data, and whether the first preset data is written in the target spare sector or not can be determined according to the read data.

In operation S240, the first read data is compared with the first preset data to determine a first test result for the target hard disk.

When comparing the first read data with the first preset data, it may be determined whether the first preset data is included in the first read data. Under the condition that the first read data comprises first preset data, determining that the first test result is that the remapping capacity of the target hard disk is normal, otherwise, determining that the remapping capacity of the target hard disk is abnormal.

According to the embodiment of the application, the target error injection instruction is generated by determining the protocol type of the target hard disk based on the drive letter of the target hard disk, determining the initial error injection instruction matched with the target hard disk according to the protocol type, and generating the target error injection instruction according to the initial error injection instruction and the first address of the target sector.

Because the instruction tools corresponding to the hard disks with different protocol types are different, the target error marking instruction can be generated according to the protocol type of the target hard disk and the first address of the target sector so as to realize error marking of the target sector. Wherein the first address may be a logical address of the target sector in a logical block addressing (Logical Block Addressing, LBA) manner.

When determining the protocol type of the target hard disk, the protocol type can be judged according to the drive letter of the target hard disk. For example, the protocol type of the target hard disk may be determined based on the drive path of the drive.

When determining the initial error injection instruction matched with the target hard disk, an instruction tool matched with the protocol type direction can be determined first, then the initial error injection instruction used for injecting logic errors under the instruction tool is determined, unrecoverable errors are written into the sectors, and the artificial manufacture of the logic bad sectors is realized.

For example, the instruction tool matching the serial advanced technology attachment (SERIAL ADVANCED Technology Attachment, SATA) protocol is hdparm, the initial debug instruction may be-make-bad-sector, the instruction tool matching the Non-volatile memory host controller interface Specification (Non-Volatile Memory Express, NVME) protocol is NVME, the initial debug instruction may be write-uncor, the instruction tool matching the serial attached Small computer System interface (SERIAL ATTACHED SCSI, SAS) protocol is sg write long, and the initial debug instruction may be-wr uncor.

After determining the initial error injection instruction, in order to inject a logic error into the target sector, a first address may be added to the initial error injection instruction to generate a target error injection instruction.

According to the embodiment of the application, the target error-injection instruction matched with the target sector is generated by determining the protocol type of the target hard disk and the first address of the target sector, so that the accuracy of the target error-injection instruction is improved, and the accuracy of hard disk testing is further improved.

According to the embodiment of the application, the protocol type of the target hard disk is determined based on the drive letter of the target hard disk, wherein the method comprises the steps of obtaining the drive letter of the target hard disk, determining that the protocol type of the target hard disk is a first protocol type when the drive letter path of the drive letter is a first preset path, obtaining the protocol parameter of the target hard disk when the drive letter path of the drive letter is a second preset path, determining that the protocol type of the target hard disk is a second protocol type when the parameter value of the protocol parameter is the first preset parameter value, and determining that the protocol type of the target hard disk is a third protocol type when the parameter value of the protocol parameter is the second preset parameter value.

When the drive letter of the target hard disk is acquired, a drive letter inquiry instruction can be executed to obtain the drive letter containing the drive letter path. For example, the disc symbol query instruction may be lsblk, the disc symbol obtained by the query may be/dev/sd or/dev/nvme ×n1, and the disc symbol path may be/dev/sd or/dev/nvme.

The first preset path may be/dev/NVME, where the first protocol type corresponding to the first preset path is NVME protocol.

The second preset path may be/dev/sd, and the protocol type corresponding to the second preset path includes a second protocol type and a third protocol type. The second protocol type may be SATA protocol, and the third protocol type may be SAS protocol.

Because the protocol type corresponding to the second preset path includes the second protocol type and the third protocol type at the same time, the protocol type of the target hard disk cannot be distinguished only by the drive letter path, so that the protocol parameters of the target hard disk can be further acquired to determine the protocol type of the target hard disk.

The protocol parameter corresponding to the second protocol type may be SATA Version and the protocol parameter corresponding to the third protocol type may be Transport protocol. In some embodiments, the protocol parameters may be obtained from Self-Monitoring analysis and reporting technology (SMART) information of the target hard disk.

When the protocol types of the hard disk are different, the protocol parameters contained in the SMART information may also be different. For example, the SMART report of the hard disk of the SATA protocol includes the protocol parameter SATA Version, and the SMART report of the hard disk of the SAS protocol does not include the protocol parameter SATA Version.

In some embodiments, the first preset parameter value may be set to SATA and the second preset parameter value may be SAS. Specifically, the parameter value of SATA Version of the target hard disk may be queried first, when the parameter value is a first preset parameter value SATA, the protocol of the target hard disk is determined to be SATA, and when the parameter value cannot be queried, the parameter value Transport protocol of the target hard disk is queried again, and when the parameter value is a second preset parameter value SAS, the protocol of the target hard disk is determined to be SAS.

According to the embodiment of the application, the protocol type of the target hard disk is determined according to the drive letter path of the target hard disk and the parameter value of the protocol parameter, so that the accuracy of the determined protocol type is improved, the hard disk test method is suitable for hard disks of different protocol types, and the application range of the hard disk test method is enlarged.

Fig. 3 schematically shows a flow chart of determining the protocol type of a target hard disk according to an embodiment of the application.

As shown in FIG. 3, determining the protocol type of the target hard disk includes operations S310-S370.

In operation S310, an identifier of a target hard disk is acquired.

In operation S320, it is determined whether the drive path is a first preset path. If the drive path is the first preset path, operation S350 is performed, and otherwise operation S330 is performed.

In operation S330, the protocol parameters of the target hard disk are acquired.

In operation S340, it is determined whether the parameter value of the protocol parameter is a first preset parameter value. In case that the parameter of the protocol type is the first preset parameter value, operation S360 is performed, and otherwise operation S370 is performed.

In operation S350, it is determined that the protocol type of the target hard disk is the first protocol type.

In operation S360, it is determined that the protocol type of the target hard disk is the second protocol type.

In operation S370, it is determined that the protocol type of the target hard disk is the third protocol type.

According to the embodiment of the application, after executing the target error injection instruction matched with the target sector in the target hard disk, the hard disk test method further comprises the steps of obtaining a current error report count value in the process of executing the read operation on the target sector, comparing the current error report count value with a historical error report count value to obtain a comparison result, and determining that the execution of the target error injection instruction is completed under the condition that the comparison result represents that a new error is newly added.

In order to ensure the accuracy of the test result, verification is required after the target error-marked instruction is executed, and the error processing mechanism of the target hard disk is tested under the condition that the execution of the target error-marked instruction is completed.

In determining whether execution of the target error instruction is complete, a read operation may be performed on the target sector. Under the condition that the target sector is a bad sector, the read-write operation cannot be normally executed, and error reporting is generated, so that whether the target hard disk fails to report errors or not can be determined by comparing error reporting count values before and after the read operation is executed, and further whether the target sector is a bad sector or not can be determined.

The current error reporting count value may be an error reporting count value after the execution of the read operation, and the historical error reporting count value may be an error reporting count value before the execution of the read operation. For example, the error count value may be acquired and determined to be a historical error count value before the read operation is performed, and the error count value may be acquired and determined to be a current error count value after the read operation is performed.

In some embodiments, the error count types corresponding to the hard disks of different protocol types may also be different, so that it is also necessary to determine the error count type corresponding to the target hard disk according to the protocol type of the target hard disk. For example, the error count corresponding to SATA protocol and SAS protocol may be Reported _ Uncorrect and the error count corresponding to NVME may be media_error.

When comparing the current error reporting count value with the historical error reporting count value, if the historical error reporting count value is A, whether the current error reporting count value is A+1 can be determined. Under the condition that the current error reporting count value is A+1, the comparison result can be determined to represent that new error reporting exists, the execution of the target error injection instruction is completed, and under the condition that the current error reporting count value is A, the comparison result can be determined to represent that no new error reporting exists, and the execution of the target error injection instruction fails.

In other embodiments of the present application, the error count value may be obtained and determined to be the initial error count value before executing the destination error marking instruction. And under the conditions that the initial error reporting count value is A, the historical error reporting count value is A and the current error reporting count value is A+1, determining that the comparison result represents that the newly increased error reporting exists, and completing the execution of the target error injection instruction.

According to the embodiment of the application, the execution condition of the target error injection instruction is checked, so that the subsequent testing step can be executed again under the condition that the execution of the target error injection instruction is completed, and the testing accuracy is improved.

Fig. 4 schematically shows a change schematic of the error count value according to an embodiment of the present application.

As shown in fig. 4, when the error count value is the initial error count value 410, the value is a. After executing the target error marking instruction, the error reporting count value is a historical error reporting count value 420, and the value is A. After the read operation is performed, the error report count value is the current error report count value 430, and since the read operation cannot be performed when the target sector is a bad sector, an error report is generated, and the value is a+1.

According to an embodiment of the present application, the mapping relationship includes a sub-mapping relationship between bad sector addresses and spare sector addresses. According to the mapping relation between the bad sector and the spare sector of the target hard disk, performing read operation on the target spare sector with the mapping relation with the target sector to obtain first read data, wherein the read operation is performed on the target spare sector by utilizing the sub-mapping relation according to the first address of the target sector to obtain first read data.

In the bad sector information, the bad sector may be identified by a sector address of the bad sector, and the spare sector may be identified by a sector address of the spare sector, so that the mapping relationship between the bad sector and the spare sector may include a mapping relationship between the bad sector address and the spare sector address.

In the embodiment of the present application, the target error injection instruction may include a first address of the target sector, and further, in the case that the bad sector information includes the sector information of the target sector, the second address of the target spare sector of the target sector may be determined according to the first address of the target sector.

When the data stored in the target spare sector is read, a read operation may be performed on the second address using a read data command corresponding to the target hard disk to obtain the first read data.

According to the embodiment of the application, the second address of the target spare sector is obtained according to the sub-mapping relation, so that the second address is utilized to directly execute the reading operation on the target spare sector, the remapping capacity of the target hard disk is further verified, and the accuracy of the first read data is improved.

Fig. 5 schematically shows a schematic diagram of a mapping relationship according to an embodiment of the application.

As shown in fig. 5, the target hard disk includes 8 sectors, such as sector 0, sector 1, sector 2, sector 6, and sector 7. When the sector 1 is a bad sector, the spare sector having a mapping relation with the sector 1 is the sector 7, and the sector 7 is used for replacing the sector 1 to perform read-write operation.

According to the embodiment of the application, the hard disk testing method further comprises the steps of executing the target error marking instructions on a plurality of target sectors of the target hard disk respectively, executing high-load write operation on the target hard disk by using a preset script under the condition that the execution of the target error marking instructions is completed, acquiring an error reporting count value in the process of executing the high-load write operation, and determining a fourth testing result for the target hard disk according to the error reporting count value.

In the embodiment of the disclosure, a fault instruction is executed on a plurality of target sectors respectively, a plurality of logic bad sectors are manufactured to simulate a scene that a large number of logic bad sectors exist in a target hard disk, and the bearing capacity of high load is verified when the large number of logic bad sectors exist in the target hard disk.

Because the target hard disk has remapping capability, the error count value will not change even if a write operation is performed to the target sector. However, when there are a large number of logically bad sectors and high load is applied to the target hard disk, the stability of the target hard disk is reduced, and thus the write operation for the bad sectors may not be mapped to the spare sectors, resulting in error reporting.

When the fourth test result is determined according to the error reporting count value, the fourth test result can be determined according to the time when the error reporting count value changes for the first time and the change trend of the error reporting count value in the writing operation process. For example, the later the time when the error count value changes for the first time, the stronger the bearing capacity of the target hard disk to high load when a large number of logic bad sectors exist, and the stronger the stability.

According to the embodiment of the application, the fault injection is carried out on the plurality of sectors, the scene that a large number of logic bad sectors exist in the target hard disk is simulated, and the scene that a large number of logic bad sectors exist in the target hard disk is combined with the scene bearing high-load read-write operation, so that the stability of the target hard disk is verified, the verification of the target hard disk is more comprehensive, and the stability of the target hard disk is improved.

The hard disk testing method further comprises the steps of executing a target recovery instruction matched with a target sector in the target hard disk, executing power-off operation on the target hard disk to simulate abnormal power-off of the target hard disk under the condition that the execution of the target recovery instruction is confirmed, executing power-on operation on the target hard disk, comparing information of the target sector with information of the bad sector, and determining a second testing result aiming at the target hard disk.

Because the user can repair the logic bad sector in the actual application process of the hard disk, when the target hard disk is tested, the situation that the user repairs the logic bad sector can be simulated by executing the target recovery instruction for repairing the target sector after the logic error is injected, so that the processing mechanism of the target hard disk after the logic bad sector is repaired is tested.

The target restoration instruction needs to be generated before it is executed. In some embodiments, the target recovery instruction is generated in a similar manner to the target error injection instruction by determining an initial recovery instruction matching the target hard disk based on the protocol type of the target hard disk, and generating the target recovery instruction based on the initial recovery instruction and the first address of the target sector.

The initial recovery instruction may restore the target sector to normal by overwriting the target sector. For example, the data stored in the target sector may be backed up before the execution of the target error instruction, and the target sector may be rewritten with the backup data when the target sector is restored.

Upon determining an initial recovery instruction matching the target hard disk, the instruction tool matching SATA is hdparm, the instruction tool matching SAS is sg_dd, and the instruction tool matching NVME is NVME.

After determining the initial recovery instruction, the first address may be added to the initial recovery instruction to obtain a target recovery instruction to recover the target sector.

After the target recovery instruction is executed, whether the target recovery instruction is executed is verified. After the target recovery instruction is executed, the subsequent test operation is carried out, and the accuracy of the test process is improved.

Upon verifying that the target recovery instruction is complete in execution, a read operation may be performed on the target sector. Since the target sector is recovered to be normal, the read operation can be normally executed, and therefore, the error reporting condition can not occur, and the error reporting count values before and after the read operation is executed are the same, and are the same as the current error reporting count value and are both A+1.

Because the hard disk can also have the problems of abnormal power failure and the like in the actual use process, the bad sector repair scene of the hard disk can be further combined with the abnormal power failure scene so as to further verify the robustness and the stability of the target hard disk.

When the hard disk is abnormally powered down, flash metadata, bad sector information and the like may be lost. Therefore, the information persistence capability of the target hard disk, such as whether the bad sector information is wrong, can be verified after the target hard disk is powered off and powered on again.

Since the target sector has been restored to the normal sector before the power-off, the bad sector information of the target hard disk after the re-power-on should not include the information of the target sector. When comparing the information of the target sector with the information of the bad sector, under the condition that the information of the target sector is not included in the information of the bad sector, the second test result is determined to be that the information persistence capability of the target hard disk is higher, and the firmware can read the historical bad sector information from the nonvolatile storage medium.

According to the embodiment of the application, the bad sector recovery scene is combined with the abnormal power failure scene to be closer to the actual use condition of the target hard disk, so that verification of the information persistence capability of the hard disk under the abnormal power failure scene is realized, and the robustness of the target hard disk is improved.

According to the embodiment of the application, after the power-on operation is performed on the target hard disk, the hard disk testing method further comprises the steps of writing second preset data into the first address of the target sector, performing a read operation on the second address of the target standby sector to obtain second read data, performing a read operation on the first address of the target sector to obtain third read data, and determining a third testing result aiming at the target hard disk based on the second preset data, the second read data and the third read data.

Under the abnormal electric field failure condition, the mapping relation reconstruction capability of the target hard disk can be verified. For example, it may be verified whether the target hard disk still maps a write operation for the target hard disk to the target spare sector according to a mapping relationship between the target sector and the target spare sector in a case where the target sector has been restored to the normal sector.

When verifying the mapping relationship reconstruction capability of the target hard disk, it may be determined whether the second preset data is written into the target sector or the target spare sector by writing the second preset data into the target sector.

When the mapping relationship between the target sector and the target spare sector is not reconstructed by the target hard disk, the read operation performed on the first address of the target sector is still mapped to the target spare sector for execution, so that the read operation needs to be performed on the target sector and the target spare sector respectively to determine whether the second preset data is written into the target sector or the target spare sector.

The second read data may be data stored in the target spare sector and the third read data may be data stored in the target sector. When the second read data does not include the second preset data and the third read data includes the second preset data, the target sector can be determined to normally write the second preset data, and the third test result is that the target hard disk can reconstruct the mapping relation between the sector and the spare sector under the abnormal power failure condition.

According to the embodiment of the application, by combining the bad sector recovery scene with the abnormal power failure scene, whether the target sector can normally write data after the power is on again is tested, and further whether the mapping relation between the sector and the spare sector can be rebuilt in the abnormal power failure scene is tested, so that the robustness of the target hard disk is improved.

Fig. 6 schematically shows a flow chart of a hard disk testing method according to an embodiment of the application.

As shown in FIG. 6, the hard disk testing method includes operations S601 to S609.

In operation S601, an identifier of a target hard disk is acquired.

In operation S602, a protocol type of the target hard disk is determined.

In operation S603, a destination error instruction is generated and executed.

In operation S604, the check object marks the execution of the erroneous instruction.

In operation S605, a first test result is determined.

In operation S606, a target restoration instruction is generated and executed.

In operation S607, the execution of the target restoration instruction is checked.

In operation S608, a second test result is determined.

In operation S609, a third test result is determined.

Based on the hard disk testing method, the application also provides a hard disk testing device. The device will be described in detail below in connection with fig. 7.

Fig. 7 schematically shows a block diagram of a hard disk testing apparatus according to an embodiment of the present application.

As shown in fig. 7, the hard disk testing apparatus 700 of this embodiment includes a target error marking module 710, a first writing module 720, a first reading module 730, and a comparison determining module 740.

The target debug module 710 is configured to execute a target debug instruction matching a target sector in the target hard disk in response to receiving a test request for the target hard disk, the target debug instruction being configured to inject a logical error into the target sector. In an embodiment, the error-of-order module 710 may be used to perform the operation S210 described above, which is not described herein.

The first writing module 720 is configured to write first preset data to the target sector if it is determined that execution of the target error instruction is completed. In an embodiment, the first writing module 720 may be used to perform the operation S220 described above, which is not described herein.

The first reading module 730 is configured to, when it is determined that the bad sector information of the target hard disk indicates that the target sector is a bad sector, perform a reading operation on a target spare sector having a mapping relationship with the target sector according to a mapping relationship between the bad sector and the spare sector of the target hard disk, so as to obtain first read data. In an embodiment, the first reading module 730 may be used to perform the operation S230 described above, which is not described herein.

The comparison determining module 740 is configured to compare the first read data with first preset data and determine a first test result for the target hard disk. In an embodiment, the comparison determination module 740 may be configured to perform the operation S240 described above, which is not described herein.

According to an embodiment of the present application, the mapping relationship includes a sub-mapping relationship between bad sector addresses and spare sector addresses. The data reading module 730 includes an address determination module and a data reading sub-module.

The address determination submodule is used for determining a second address of the target spare sector according to the first address of the target sector by utilizing the sub-mapping relation.

The data reading sub-module is used for executing reading operation on the target spare sector by using the second address to obtain first reading data.

According to an embodiment of the present application, the hard disk testing apparatus 700 further includes a target recovery module, a target power-off module, and a target power-on module.

The target recovery module is used for executing a target recovery instruction matched with a target sector in the target hard disk, and the target recovery instruction is used for recovering the target sector after the logic error is injected.

And the target power-off module is used for executing power-off operation on the target hard disk under the condition that the execution of the target recovery instruction is determined to be completed so as to simulate abnormal power-off of the target hard disk.

The target power-on module is used for executing power-on operation on the target hard disk, comparing information of the target sector with information of the bad sector, and determining a second test result aiming at the target hard disk.

According to an embodiment of the present application, the hard disk testing apparatus 700 further includes a second writing module, a second reading module, a third reading module, and a result determining module.

The second writing module is used for writing second preset data to the first address of the target sector.

The second reading module is used for executing reading operation on a second address of the target spare sector to obtain second read data.

And the third reading module is used for executing reading operation on the first address of the target sector to obtain third reading data.

The result determining module is used for determining a third test result aiming at the target hard disk based on the second preset data, the second read data and the third read data.

According to an embodiment of the present application, the hard disk testing apparatus 700 further includes a count acquisition module, a count comparison module, and an execution determination module.

The counting acquisition module is used for acquiring the current error reporting count value in the process of executing the reading operation on the target sector.

The counting and comparing module is used for comparing the current error reporting count value with the historical error reporting count value to obtain a comparison result.

The execution determining module is used for determining that the execution of the target error marking instruction is completed under the condition that the comparison result represents that the new error is added.

According to an embodiment of the present application, the hard disk testing apparatus 700 further includes a drive letter obtaining module, a first determining module, a second determining module, and a third determining module.

The drive letter acquisition module is used for acquiring the drive letter of the target hard disk.

The first determining module is configured to determine that the protocol type of the target hard disk is a first protocol type when the drive path of the drive is a first preset path.

The second determining module is configured to determine that the protocol type of the target hard disk is a second protocol type when the parameter value of the protocol parameter is a first preset parameter value.

And the third determining module is used for determining that the protocol type of the target hard disk is a third protocol type under the condition that the parameter value of the protocol parameter is a second preset parameter value.

Any of the plurality of modules of the target error injection module 710, the first writing module 720, the first reading module 730, and the comparison determination module 740 may be combined in one module or any of the plurality of modules may be split into a plurality of modules according to an embodiment of the present application. Or at least some of the functionality of one or more of the modules may be combined with, and implemented in, at least some of the functionality of other modules. According to embodiments of the application, at least one of the target error injection module 710, the first write module 720, the first read module 730, and the comparison determination module 740 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging the circuitry, or in any one of or a suitable combination of any of the three. Or at least one of the destination labeling module 710, the first writing module 720, the first reading module 730, and the comparison determination module 740 may be at least partially implemented as a computer program module which, when executed, may perform the corresponding functions.

As shown in fig. 8, an electronic device 800 according to an embodiment of the present application includes a processor 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. The processor 801 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 801 may also include on-board memory for caching purposes. The processor 801 may comprise a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the application.

In the RAM 803, various programs and data required for the operation of the electronic device 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flow according to the embodiment of the present application by executing programs in the ROM 802 and/or the RAM 803. Note that the program may be stored in one or more memories other than the ROM 802 and the RAM 803. The processor 801 may also perform various operations of the method flow according to embodiments of the present application by executing programs stored in one or more memories.

According to an embodiment of the application, the electronic device 800 may further comprise an input/output (I/O) interface 805, the input/output (I/O) interface 805 also being connected to the bus 804. The electronic device 800 may also include one or more of an input portion 806 including a keyboard, a mouse, etc., an output portion 807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), etc., and a speaker, etc., a storage portion 808 including a hard disk, etc., and a communication portion 809 including a network interface card such as a LAN card, a modem, etc., connected to an input/output (I/O) interface 805. The communication section 809 performs communication processing via a network such as the internet. The drive 810 is also connected to an input/output (I/O) interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as needed so that a computer program read out therefrom is mounted into the storage section 808 as needed.

The present application also provides a computer-readable storage medium that may be included in the apparatus/device/system described in the above embodiments, or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present application.

According to embodiments of the application, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the application, the computer-readable storage medium may include ROM 802 and/or RAM 803 and/or one or more memories other than ROM 802 and RAM 803 described above.

Embodiments of the present application also include a computer program product comprising a computer program containing program code for performing the method shown in the flowcharts. When the computer program product runs in a computer system, the program code is used for enabling the computer system to realize the hard disk testing method provided by the embodiment of the application.

The above-described functions defined in the system/apparatus of the embodiment of the present application are performed when the computer program is executed by the processor 801. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the application.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed, and downloaded and installed in the form of a signal on a network medium, and/or from a removable medium 811 via a communication portion 809. The computer program may comprise program code that is transmitted using any appropriate network medium, including but not limited to wireless, wireline, etc., or any suitable combination of the preceding.

In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809, and/or installed from the removable media 811. The above-described functions defined in the system of the embodiment of the present application are performed when the computer program is executed by the processor 801. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the application.

According to embodiments of the present application, program code for carrying out computer programs provided by embodiments of the present application may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or in assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that the features recited in the various embodiments of the application can be combined and/or combined in a variety of ways, even if such combinations or combinations are not explicitly recited in the present application. In particular, the features recited in the various embodiments of the application can be combined and/or combined in various ways without departing from the spirit and teachings of the application. All such combinations and/or combinations fall within the scope of the application.

The embodiments of the present application are described above. These examples are for illustrative purposes only and are not intended to limit the scope of the present application. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the application, and such alternatives and modifications are intended to fall within the scope of the application.

Claims

1. A method for testing a hard disk, the method comprising:

in response to receiving a test request for a target hard disk, executing a target error injection instruction matched with a target sector in the target hard disk, wherein the target error injection instruction is used for injecting a logic error into the target sector;

Writing first preset data into the target sector under the condition that the execution of the target error injection instruction is determined to be completed;

Under the condition that the bad sector information of the target hard disk is determined to indicate that the target sector is a bad sector, according to the mapping relation between the bad sector and the spare sector of the target hard disk, performing a read operation on the target spare sector with the mapping relation with the target sector to obtain first read data;

Comparing the first read data with the first preset data, and determining a first test result aiming at the target hard disk.

2. The method of claim 1, wherein the mapping relationship comprises a sub-mapping relationship between a bad sector address and a spare sector address, wherein the performing a read operation on a target spare sector having the mapping relationship with the target sector according to the mapping relationship between the bad sector and the spare sector of the target hard disk to obtain first read data comprises:

determining a second address of the target spare sector by utilizing the sub-mapping relation according to the first address of the target sector;

And executing a read operation on the target standby sector by using the second address to obtain the first read data.

3. The method according to claim 1, wherein the method further comprises:

Executing a target recovery instruction matched with a target sector in the target hard disk, wherein the target recovery instruction is used for recovering the target sector after the logic error is injected;

Under the condition that the execution of the target recovery instruction is determined to be completed, executing power-off operation on the target hard disk so as to simulate abnormal power-off of the target hard disk;

and executing power-on operation on the target hard disk, comparing the information of the target sector with the information of the bad sector, and determining a second test result aiming at the target hard disk.

4. The method of claim 3, wherein after performing a power-up operation on the target hard disk, the method further comprises:

writing second preset data into a first address of the target sector;

Performing a read operation on a second address of the target spare sector to obtain second read data;

Performing a read operation on the first address of the target sector to obtain third read data;

and determining a third test result aiming at the target hard disk based on the second preset data, the second read data and the third read data.

5. The method of claim 1, wherein after executing the target debug instruction that matches a target sector in the target hard disk, the method further comprises:

Acquiring a current error report count value in the process of executing reading operation on the target sector;

comparing the current error reporting count value with the historical error reporting count value to obtain a comparison result;

and under the condition that the comparison result represents that a new addition error exists, determining that the execution of the target error injection instruction is completed.

6. The method according to claim 1, wherein the method further comprises:

determining the protocol type of the target hard disk based on the drive letter of the target hard disk;

determining an initial error injection instruction matched with the target hard disk according to the protocol type;

and generating the target error injection instruction according to the initial error injection instruction and the first address of the target sector.

7. The method of claim 6, wherein the determining the protocol type of the target hard disk based on the drive letter of the target hard disk comprises:

Acquiring a drive letter of the target hard disk;

Under the condition that the drive path of the drive is a first preset path, determining that the protocol type of the target hard disk is a first protocol type;

Under the condition that the drive letter path of the drive letter is a second preset path, acquiring protocol parameters of the target hard disk;

Under the condition that the parameter value of the protocol parameter is a first preset parameter value, determining that the protocol type of the target hard disk is a second protocol type;

And under the condition that the parameter value of the protocol parameter is a second preset parameter value, determining that the protocol type of the target hard disk is a third protocol type.

8. A hard disk testing apparatus, the apparatus comprising:

The target error-injection module is used for responding to the received test request for the target hard disk and executing a target error-injection instruction matched with a target sector in the target hard disk, wherein the target error-injection instruction is used for injecting logic errors into the target sector;

the first writing module is used for writing first preset data into the target sector under the condition that the execution of the target error injection instruction is determined to be completed;

The first reading module is used for executing reading operation on a target spare sector with the mapping relation with the target sector according to the mapping relation between the bad sector and the spare sector of the target hard disk under the condition that the bad sector information of the target hard disk is determined to indicate that the target sector is the bad sector, so as to obtain first reading data;

And the comparison and determination module is used for comparing the first read data with the first preset data and determining a first test result aiming at the target hard disk.

9. An electronic device, comprising:

One or more processors;

a memory for storing one or more computer programs,

Characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1-7.

10. A computer-readable storage medium, on which a computer program or instructions is stored, which, when executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.