CN110826114B - User data testing method and device based on SSD after safe erasure - Google Patents
User data testing method and device based on SSD after safe erasure Download PDFInfo
- Publication number
- CN110826114B CN110826114B CN201911033348.XA CN201911033348A CN110826114B CN 110826114 B CN110826114 B CN 110826114B CN 201911033348 A CN201911033348 A CN 201911033348A CN 110826114 B CN110826114 B CN 110826114B
- Authority
- CN
- China
- Prior art keywords
- user data
- lba
- ssd
- script
- value
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer
- G06F21/78—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure storage of data
- G06F21/79—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure storage of data in semiconductor storage media, e.g. directly-addressable memories
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
- G11C29/04—Detection or location of defective memory elements, e.g. cell constructio details, timing of test signals
- G11C29/08—Functional testing, e.g. testing during refresh, power-on self testing [POST] or distributed testing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2143—Clearing memory, e.g. to prevent the data from being stolen
Abstract
The application relates to a user data testing method, a device, computer equipment and a storage medium based on SSD after safe erasure, wherein the method comprises the following steps: the method comprises the following steps of (1) fully writing the solid state disk twice by operating a test script and utilizing an FIO (flash-in-package) read-write tool; the method comprises the following steps of utilizing an hdparm tool to safely erase the solid state disk; after the safe erasing, reading user data on each LBA of the solid state disk by using an hdparm tool, and storing the read data into a corresponding file; judging whether the value of the user data in the stored file is 0 or not; if not, the script reports an error, the script stops and the test is finished; if the value is 0, it indicates that the user data on the corresponding LBA has been cleared. The invention can automatically judge whether the user data of all the LBAs on the SSD is cleared after the SSD is safely erased, if not, the user data is probably caused by the abnormal condition of the SSD when executing the safe erasing command, thereby effectively ensuring the safety of the SSD user data.
Description
Technical Field
The invention relates to the technical field of solid state disk storage, in particular to a user data testing method and device based on SSD after safe erasure, computer equipment and a storage medium.
Background
At present, an SSD (solid state disk) has been widely used in various occasions, and at present, in the PC market, the conventional HDD has been gradually replaced, providing a better experience for users in terms of reliability and performance.
In the conventional technology, when the SSD is securely erased, all user data on the SSD should be cleared, that is, data on each LBA of the SSD should be 0, and none of the data thereon can be recovered. However, if the SSD firmware design has a defect, some or even most of the data on the LBA may not be cleared after the SSD is securely erased, and the data that is not cleared may be recovered, so that there is a possibility that the user data is stolen. However, the current testing tool or method for SSD secure erase only concerns whether the SSD is securely erased, but does not concern whether the user data on all LBAs of the SSD is actually erased (i.e. cleared) after the SSD is securely erased, so that the security of the SSD user data cannot be effectively guaranteed.
Disclosure of Invention
Therefore, it is necessary to provide a method, an apparatus, a computer device, and a storage medium for testing user data after SSD secure erase, which can automatically determine whether the user data of all LBAs on the SSD has been cleared after the SSD is securely erased.
A user data testing method based on SSD after safe erasure comprises the following steps:
acquiring a user data test request after safe erasure based on the SSD;
according to the user data test request after the SSD-based safe erasing, a solid state disk is fully written twice by operating a test script and utilizing an FIO read-write tool;
the solid state disk is safely erased by using an hdparm tool;
after safe erasing, reading user data on each LBA of the solid state disk by using an hdparm tool, and storing the read data into a corresponding file;
judging whether the value of the user data in the stored file is 0 or not; if not, the script reports an error, the script stops and the test is finished; if the value is 0, it indicates that the user data on the corresponding LBA has been cleared.
In one embodiment, the step of reading the user data on each LBA of the solid state disk by using an hdparm tool after the secure erase, and saving the read data in a corresponding file further includes:
sequentially reading user data on each LBA of the solid state disk by using an hdparm tool, wherein the user data comprises all the user data from the LBA to the last LBA;
and automatically saving the data on the corresponding LBA into the txt file with the value of the LBA as the name.
In one embodiment, the determining whether the value of the user data in the saved file is 0; if not, the script reports an error, the script stops and the test is finished; if the value is 0, the step of indicating that the user data on the corresponding LBA has been cleared further includes:
comparing the value of the user data on the saved txt file with 0;
if the value of the user data in the saved txt file is not 0, the script reports an error, the script stops and the test is finished;
if the value of the user data on the saved txt file is 0, the user data on the LBA is cleared;
and deleting the saved txt file.
In one embodiment, after the step of clearing the user data on the corresponding LBA if the user data is 0, the method further includes:
and continuously detecting the user data on the next LBA until the user data on a certain LBA is detected to be not 0 or all the LBA data are detected, stopping the test, and exiting the script.
An apparatus for testing user data after SSD-based secure erase, the apparatus comprising:
the acquisition module is used for acquiring a user data test request after SSD safe erasure;
a full write module, configured to write a full solid state disk twice by running a test script and using an FIO read-write tool according to the user data test request after the SSD-based secure erase;
the erasing module is used for safely erasing the solid state disk by using an hdparm tool;
the reading module is used for reading the user data on each LBA of the solid state disk by using an hdparm tool after safe erasure, and storing the read data in a corresponding file;
the judging module is used for judging whether the value of the user data in the stored file is 0 or not; if not, the script reports an error, the script stops and the test is finished; if the value is 0, it indicates that the user data on the corresponding LBA has been cleared.
In one embodiment, the reading module is further configured to:
sequentially reading user data on each LBA of the solid state disk by using an hdparm tool, wherein the user data comprises all the user data from the LBA to the last LBA;
and automatically saving the data on the corresponding LBA into the txt file with the value of the LBA as the name.
In one embodiment, the determining module is further configured to:
comparing the value of the user data on the saved txt file with 0;
if the value of the user data in the saved txt file is not 0, the script reports an error, the script stops and the test is finished;
if the value of the user data on the saved txt file is 0, the user data on the LBA is cleared;
and deleting the saved txt file.
In one embodiment, the apparatus further comprises:
and the circulating module is used for continuously detecting the user data on the next LBA until the user data on a certain LBA is detected to be not 0 or all the LBA data are detected, stopping the test and exiting the script.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of any of the above methods when executing the computer program.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of any of the methods described above.
According to the user data testing method and device based on SSD safe erasing, the computer equipment and the storage medium, the solid state disk is fully written twice by operating the test script and utilizing the FIO read-write tool; the solid state disk is safely erased by using an hdparm tool; after safe erasing, reading user data on each LBA of the solid state disk by using an hdparm tool, and storing the read data into a corresponding file; judging whether the value of the user data in the stored file is 0 or not; if not, the script reports an error, the script stops and the test is finished; if the value is 0, it indicates that the user data on the corresponding LBA has been cleared. The testing method provided by the invention is simple and efficient, can automatically judge whether the user data of all the LBAs on the SSD is cleared after the SSD is safely erased, if not, the user data is probably caused by the abnormal condition of the SSD when executing the safe erasing command, thereby being capable of exposing in advance and solving the related SSD firmware design defects, effectively ensuring the safety of the SSD user data and improving the quality of the SSD product.
Drawings
FIG. 1 is a schematic flow chart illustrating a method for testing user data after SSD-based secure erase in one embodiment;
FIG. 2 is a schematic flowchart of a method for testing user data after SSD-based secure erase in another embodiment;
FIG. 3 is a schematic flowchart of a method for testing user data after SSD-based secure erase in yet another embodiment;
FIG. 4 is a block diagram of a device for testing user data after SSD-based secure erase, according to one embodiment;
FIG. 5 is a block diagram of a device for testing user data after SSD-based secure erase in another embodiment;
FIG. 6 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
Generally, when the SSD is securely erased, all user data on the SSD should be cleared, that is, data on each LBA of the SSD should be 0, and none of the data thereon can be recovered. However, if the SSD firmware design has a defect, some or even most of the data on the LBA may not be cleared after the SSD is securely erased, and the data that is not cleared may be recovered, so that there is a possibility that the user data is stolen. However, the current testing tool or method related to the SSD secure erase only concerns whether the SSD is securely erased, but does not concern whether the user data on all LBAs of the SSD is actually erased (i.e. cleared) after the SSD is securely erased, and the SSD only needs to be cleared, that is, the SSD really implements the secure erase function.
Based on this, the invention aims to provide a simple and efficient test method which can automatically judge whether the user data of all the LBAs on the SSD has been cleared after the SSD is safely erased.
In one embodiment, as shown in fig. 1, there is provided a method for testing user data after SSD secure erase, the method comprising:
102, acquiring a user data test request after safe erasure based on SSD;
104, according to a user data test request after safe erasure based on the SSD, a FIO read-write tool is used for writing the solid state disk to the full disk twice by running a test script;
106, safely erasing the solid state disk by using an hdparm tool;
step 110, judging whether the value of the user data in the stored file is 0; if not, the script reports an error, the script stops and the test is finished; if the value is 0, it indicates that the user data on the corresponding LBA has been cleared.
Specifically, in the method for testing user data after SSD secure erase provided in this embodiment, the hardware requirements include: the computer to be tested: no mandatory requirement; SSD to be tested: the SATA interface SSD. The software requirements are as follows: operating the system: centos 7.0Linux operating system; testing the script: self-written shell test scripts. It can be understood that: for the Linux operating system, there is no mandatory requirement for this in this embodiment. The preferred operating system in this embodiment is the Centos 7.0 Linux.
In the above application environment, in the present embodiment, in a Linux system, shell test scripts are written by using FIO and hdparm tools, and the test scripts can automatically detect whether user data of all LBAs on the SSD is cleared after the SSD is securely erased. Specifically, first, a user data test request after the SSD secure erase is acquired. And then, according to the test request, the solid state disk is fully written twice by using the FIO read-write tool through running the test script. And then, the solid state disk is safely erased by using an hdparm tool, after the solid state disk is safely erased, the user data on each LBA of the solid state disk, namely all the user data from the LBA equal to 0 to the last LBA, is read by using the hdparm tool, and the read data is stored in a corresponding file. Finally, judging whether the value of the user data in the stored file is 0 or not; if not, the script reports an error, the script stops and the test is finished; if the value is 0, it indicates that the user data on the corresponding LBA has been cleared, and continues to detect the user data on the next LBA.
In one embodiment, after step 110, the method further comprises: and continuously detecting the user data on the next LBA until the user data on a certain LBA is detected to be not 0 or all the LBA data are detected, stopping the test, and exiting the script.
In the above embodiment, in the Linux system, shell test scripts are written by using FIO and hdparm tools, so that whether the user data of all LBAs on the SSD is cleared after the SSD is securely erased can be automatically determined, and if not, the user data is likely to be caused by an abnormality occurring in the SSD when executing the secure erase command, so that the SSD firmware design defects related to the SSD can be exposed in advance and solved, the security of the SSD user data is effectively ensured, and the SSD product quality is improved.
In an embodiment, as shown in fig. 2, a method for testing user data after SSD secure erase is provided, in which after the secure erase, a hdparm tool is used to read user data on each LBA of a solid state disk, and the read data is saved in a corresponding file, further includes:
step 202, sequentially reading user data on each LBA of the solid state disk by using an hdparm tool, where the user data includes all user data from the LBA to the last LBA;
in step 204, the data on the corresponding LBA is automatically saved to the txt file named the LBA value.
In one embodiment, as shown in fig. 3, a method for testing user data after SSD secure erase is provided, in which it is determined whether a value of user data in a saved file is 0; if not, the script reports an error, the script stops and the test is finished; if the value is 0, the step of indicating that the user data on the corresponding LBA has been cleared further includes:
step 302, comparing the value of the user data on the saved txt file with 0;
step 304, if the value of the user data in the saved txt file is not 0, the script reports an error, the script stops, and the test is finished;
step 306, if the value of the user data on the txt file is saved to be 0, it indicates that the user data on the LBA has been cleared;
and step 308, deleting the saved txt file.
In this embodiment, a method for testing user data after a secure erase based on SSD is provided, and the complete implementation steps include:
1. the SSD is written to the full disk twice by using the FIO read-write tool.
2. And safely erasing the SSD by using an hdparm tool.
3. The hdparm tool is used to read the user data on each LBA of the SSD (i.e. all user data from LBA 0 to last LBA) and automatically save the data on that LBA to the txt file named the value of that LBA.
4. Comparing the value of the user data in the saved txt file with 0, if the value is not 0, reporting an error by the script, stopping the script and ending the test; if the value is 0, it indicates that the user data on the LBA has been cleared, and continues to detect the user data on the next LBA.
5. Delete saved txt file.
6. And (5) circularly executing the steps 3 to 5 until the user data on a certain LBA is detected to be not 0 or all the LBA data are detected, stopping the test, and exiting the script.
In the embodiment, whether the user data of all the LBAs on the SSD is cleared after the SSD is securely erased can be automatically determined, and if not, it is likely that the user data is caused by an exception occurring when the SSD executes the secure erase command, so that the SSD firmware design defect related thereto can be exposed in advance and solved, thereby effectively ensuring the security of the SSD user data, and improving the SSD product quality.
It should be understood that although the various steps in the flow charts of fig. 1-3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 1-3 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 4, there is provided an SSD-based securely erased user data testing apparatus 400, comprising:
an obtaining module 401, configured to obtain a user data test request after being securely erased based on the SSD;
a full write module 402, configured to write a full solid state disk twice by running a test script and using an FIO read-write tool according to a user data test request after the SSD security erasure;
the erasing module 403 is configured to perform secure erasing on the solid state disk by using an hdparm tool;
a reading module 404, configured to read user data on each LBA of the solid state disk by using an hdparm tool after the secure erase, and store the read data in a corresponding file;
a judging module 405, configured to judge whether a value of user data in a stored file is 0; if not, the script reports an error, the script stops and the test is finished; if the value is 0, it indicates that the user data on the corresponding LBA has been cleared.
In one embodiment, the reading module 404 is further configured to:
sequentially reading user data on each LBA of the solid state disk by using an hdparm tool, wherein the user data comprises all the user data from the LBA to the last LBA;
the data on the corresponding LBA is automatically saved to the txt file named the value of the LBA.
In one embodiment, the determining module 405 is further configured to:
comparing the value of the user data on the saved txt file with 0;
if the value of the user data in the saved txt file is not 0, the script reports an error, the script stops and the test is finished;
if the value of the user data on the saved txt file is 0, the user data on the LBA is cleared;
deleting the saved txt file.
In one embodiment, as shown in fig. 5, there is provided an SSD-based securely erased user data testing apparatus 400, the apparatus further comprising:
the loop module 406 is configured to continue to detect the user data on the next LBA until it is detected that the user data on a certain LBA is not 0 or all LBA data have been detected, stop the test, and exit the script.
For specific limitations of the device for testing user data after the SSD secure erase, refer to the above limitations of the method for testing user data after the SSD secure erase, which are not described herein again.
In one embodiment, a computer device is provided, the internal structure of which may be as shown in FIG. 6. The computer apparatus includes a processor, a memory, and a network interface connected by a device bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The nonvolatile storage medium stores an operating device, a computer program, and a database. The internal memory provides an environment for the operation device in the nonvolatile storage medium and the execution of the computer program. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method for testing user data after a secure erase based on SSD.
Those skilled in the art will appreciate that the architecture shown in fig. 6 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above method embodiments when executing the computer program.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the above respective method embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (8)
1. A user data testing method based on SSD after safe erasure is characterized by comprising the following steps:
acquiring a user data test request after safe erasure based on the SSD;
according to the user data test request after the SSD-based safe erasing, a solid state disk is fully written twice by operating a test script and utilizing an FIO read-write tool;
the solid state disk is safely erased by using an hdparm tool;
after safe erasing, reading user data on each LBA of the solid state disk by using an hdparm tool, and storing the read data into a corresponding file;
judging whether the value of the user data in the stored file is 0 or not; if not, the script reports an error, the script stops and the test is finished; if the value is 0, the user data on the corresponding LBA is cleared;
the step of reading the user data on each LBA of the solid state disk by using an hdparm tool after the secure erase, and saving the read data in a corresponding file further comprises: sequentially reading user data on each LBA of the solid state disk by using an hdparm tool, wherein the user data comprises all the user data from the LBA to the last LBA; and automatically saving the data on the corresponding LBA into the txt file with the value of the LBA as the name.
2. The method according to claim 1, wherein the determining whether the value of the user data in the saved file is 0; if not, the script reports an error, the script stops and the test is finished; if the value is 0, the step of indicating that the user data on the corresponding LBA has been cleared further includes:
comparing the value of the user data on the saved txt file with 0;
if the value of the user data in the saved txt file is not 0, the script reports an error, the script stops and the test is finished;
if the value of the user data on the saved txt file is 0, the user data on the LBA is cleared;
and deleting the saved txt file.
3. The SSD safety-erased based user data testing method of claim 1 or 2, wherein after the step of indicating that the user data on the corresponding LBA has been cleared if the user data is 0, the method further comprises:
and continuously detecting the user data on the next LBA until the user data on a certain LBA is detected to be not 0 or all the LBA data are detected, stopping the test, and exiting the script.
4. An apparatus for testing user data after a secure erase based on an SSD, the apparatus comprising:
the acquisition module is used for acquiring a user data test request after SSD safe erasure;
a full write module, configured to write a full solid state disk twice by running a test script and using an FIO read-write tool according to the user data test request after the SSD-based secure erase;
the erasing module is used for safely erasing the solid state disk by using an hdparm tool;
the reading module is used for reading the user data on each LBA of the solid state disk by using an hdparm tool after safe erasure, and storing the read data in a corresponding file;
the judging module is used for judging whether the value of the user data in the stored file is 0 or not; if not, the script reports an error, the script stops and the test is finished; if the value is 0, the user data on the corresponding LBA is cleared;
the reading module is further configured to: sequentially reading user data on each LBA of the solid state disk by using an hdparm tool, wherein the user data comprises all the user data from the LBA to the last LBA; and automatically saving the data on the corresponding LBA into the txt file with the value of the LBA as the name.
5. The device according to claim 4, wherein the determining module is further configured to:
comparing the value of the user data on the saved txt file with 0;
if the value of the user data in the saved txt file is not 0, the script reports an error, the script stops and the test is finished;
if the value of the user data on the saved txt file is 0, the user data on the LBA is cleared;
and deleting the saved txt file.
6. The device for testing user data after SSD safe erasure according to claim 4 or 5, wherein said device further comprises:
and the circulating module is used for continuously detecting the user data on the next LBA until the user data on a certain LBA is detected to be not 0 or all the LBA data are detected, stopping the test and exiting the script.
7. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 3 are implemented when the computer program is executed by the processor.
8. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911033348.XA CN110826114B (en) | 2019-10-28 | 2019-10-28 | User data testing method and device based on SSD after safe erasure |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911033348.XA CN110826114B (en) | 2019-10-28 | 2019-10-28 | User data testing method and device based on SSD after safe erasure |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110826114A CN110826114A (en) | 2020-02-21 |
| CN110826114B true CN110826114B (en) | 2021-10-26 |
Family
ID=69551136
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911033348.XA Active CN110826114B (en) | 2019-10-28 | 2019-10-28 | User data testing method and device based on SSD after safe erasure |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110826114B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113986126B (en) * | 2021-10-26 | 2023-07-04 | 深圳忆联信息系统有限公司 | TCG data deleting method and device based on solid state disk and computer equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101667458A (en) * | 2009-09-22 | 2010-03-10 | 成都市华为赛门铁克科技有限公司 | Method for erasing solid state disk wholly and equipment thereof |
| CN109817271A (en) * | 2018-11-21 | 2019-05-28 | 中国航空工业集团公司洛阳电光设备研究所 | A kind of detection method of solid state hard disk bad block |
| CN110221772A (en) * | 2019-04-25 | 2019-09-10 | 深圳市金泰克半导体有限公司 | A kind of solid state hard disk working method, system, computer equipment and storage medium |
| CN110310692A (en) * | 2019-06-28 | 2019-10-08 | 上海华虹集成电路有限责任公司 | A kind of nonvolatile memory erasing control method enhancing service life |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9665743B2 (en) * | 2015-02-26 | 2017-05-30 | Whitecanyon Software, Inc. | Selective storage device wiping system and method |
| US10579364B2 (en) * | 2018-01-12 | 2020-03-03 | Robin Systems, Inc. | Upgrading bundled applications in a distributed computing system |
| CN110286853B (en) * | 2019-06-06 | 2024-02-06 | 大唐微电子技术有限公司 | Data writing method and device and computer readable storage medium |
-
2019
- 2019-10-28 CN CN201911033348.XA patent/CN110826114B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101667458A (en) * | 2009-09-22 | 2010-03-10 | 成都市华为赛门铁克科技有限公司 | Method for erasing solid state disk wholly and equipment thereof |
| CN109817271A (en) * | 2018-11-21 | 2019-05-28 | 中国航空工业集团公司洛阳电光设备研究所 | A kind of detection method of solid state hard disk bad block |
| CN110221772A (en) * | 2019-04-25 | 2019-09-10 | 深圳市金泰克半导体有限公司 | A kind of solid state hard disk working method, system, computer equipment and storage medium |
| CN110310692A (en) * | 2019-06-28 | 2019-10-08 | 上海华虹集成电路有限责任公司 | A kind of nonvolatile memory erasing control method enhancing service life |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110826114A (en) | 2020-02-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3506104A1 (en) | Coverage test support device and coverage test support method | |
| US11688483B2 (en) | Managing block retirement for temporary operational conditions | |
| CN110618892A (en) | Bug positioning method and device for solid state disk, electronic equipment and medium | |
| CN110727597B (en) | Method for checking invalid code completion case based on log | |
| CN110826114B (en) | User data testing method and device based on SSD after safe erasure | |
| CN115620799A (en) | Firmware simulation-based fault site backtracking method and equipment and readable storage medium | |
| CN112363909B (en) | Automatic test method for reliability of file system in relay protection device | |
| CN112732181B (en) | Data migration method and related device of SSD | |
| CN110222501B (en) | Method for checking running code and storage medium | |
| CN109086162B (en) | Memory diagnosis method and device | |
| CN109686397B (en) | Memory with self-checking function and its checking method | |
| CN114639437B (en) | Memory test method, device, equipment and storage medium | |
| CN111985010A (en) | Interception verification method and device for notebook hard disk, computer equipment and storage medium | |
| CN114496052A (en) | Method and device for testing permission mode function of SSD (solid State drive) in non-operation power state | |
| CN114420194A (en) | Test method and device for power failure protection function of solid state disk and computer equipment | |
| CN110275596B (en) | Solid state disk-based power-on initialization acceleration method and device and computer equipment | |
| CN114093409A (en) | Flash memory verification method and device, computer equipment and storage medium | |
| CN113470725A (en) | Method and device for testing dynamic random access memory | |
| CN110795275A (en) | Abnormal block identification method and device based on abnormal power failure process | |
| CN116701042B (en) | Memory data retention method, retention device and related equipment | |
| CN112562774B (en) | Storage device mounting method and device, computer device and storage medium | |
| CN112151107B (en) | SSD Critical burning field testing method and device based on asynchronous events | |
| CN113870939A (en) | Test method and device for reading advance and retreat times of solid state disk PS4 and computer equipment | |
| CN114385574A (en) | Log processing method and device, electronic equipment and storage medium | |
| CN114996068A (en) | Error information function testing method and device based on solid state disk and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |