Pressure testing method of storage device, storage device and storage medium

Abstract

This application relates to the field of storage device testing technology, and provides a stress testing method, storage device, and storage medium for storage devices. During storage device testing, a network protocol stack load is generated internally via a local loopback address, while simultaneously performing read / write operations on the data disk to generate a storage load. These two loads are superimposed in parallel, and a power state switch is triggered during the load superposition process. Finally, the storage status of the data disk is checked to obtain the test results. Through this method, both network protocol stack load and storage load are generated internally within the storage device, enabling extreme stress testing of the storage device without relying on external devices. Furthermore, the stress test and power state switch are performed synchronously, ensuring testing efficiency while improving test sufficiency, thereby enhancing the reliability of the storage device and the efficiency of fault diagnosis.

Description

Technical Field

[0001] This application belongs to the field of equipment testing technology, and in particular relates to stress testing methods for storage devices, storage devices and storage media. Background Technology

[0002] With the continued growth in demand for digital office and personal data storage, storage devices are widely used in home and small and medium-sized enterprise scenarios. To ensure the stability of storage devices and data security, stress testing of the devices is necessary.

[0003] Currently, the primary method for testing storage devices is to apply network load to them using external devices. However, this process relies on the performance of the external devices, resulting in test results that do not accurately reflect the performance of the storage devices themselves, thus affecting test reliability and the efficiency of troubleshooting. Summary of the Invention

[0004] This application provides a stress testing method for storage devices, storage devices, and storage media, which can solve the technical problems of poor reliability in storage device testing and low efficiency in troubleshooting device faults.

[0005] In a first aspect, embodiments of this application provide a stress testing method for a storage device, the storage device including a data disk and a system disk; the method includes: Determine the target storage location for storing data on the data disk, and start the server process on the system disk. The server process is used to listen for the local loopback address of network packets. Send network packets to the local loopback address to generate network protocol stack load, and perform read and write operations at the target storage location to generate storage load; while the network protocol stack load and storage load persist, trigger the power state switch of the storage device. Check the status information of the data disk and system disk, and obtain the stress test results of the storage device based on the status information.

[0006] In one possible implementation of the first aspect, the storage device includes at least two data disks; determining a target storage location for storing data on the storage disks includes: Configure at least two data disks into a redundant disk array; Mount the redundant disk array to the specified directory and determine the specified directory as the target storage location.

[0007] In one possible implementation of the first aspect, sending network packets to the local loopback address to generate network protocol stack payload includes: Start the client process and enable multiple parallel threads on the client. Multiple parallel threads send network packets to the local loopback address to generate network protocol stack load until the network protocol stack resource utilization of the storage device reaches a preset threshold or continues to run for a preset duration.

[0008] In one possible implementation of the first aspect, the status information includes at least one of the following: the response status of the system disk, the read / write status of the data disk, and the storage status of the data disk; Check the status information of the data disk and system disk, and obtain the stress test results of the storage devices based on the status information, including: During periods of concurrent network protocol stack load and storage load, monitor the response status of the system disk and the read / write status of the data disk. After exiting the power state switch, check the storage status of the data disk, which indicates whether the data disk was able to successfully store data. The stress test results of the storage device are obtained based on the response status of the system disk, the read / write status of the data disk, and the storage status of the data disk.

[0009] In one possible implementation of the first aspect, when the operation of the system disk remains smooth, it is determined that the isolation between the system disk and the data disk is effective, and the response status is normal. The read / write status of the data disk is determined to be normal when the read / write throughput is less than or equal to the preset throughput.

[0010] In one possible implementation of the first aspect, after exiting the power state transition, the storage status of the data disk is checked, including: Check if the data disk can be mounted to the target storage location and obtain the mount check results; If the data disk can be mounted to the target storage location, check whether the file system metadata of the data disk is corrupted and obtain the consistency check results; If the mount check shows successful mounting and the consistency check shows no data corruption, the data disk's storage status is determined to be capable of successfully storing data.

[0011] In one possible implementation of the first aspect, triggering a power state switch of the storage device includes at least one of the following: Trigger storage device to switch to suspend state; trigger storage device to switch to hibernation state; trigger storage device to restart; trigger storage device to power off.

[0012] In one possible implementation of the first aspect, the system disk includes an M.2-based hard drive, and the data disk is a SATA-based solid-state drive or hard disk drive.

[0013] In a second aspect, embodiments of this application provide a storage device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described in any of the first aspects.

[0014] Thirdly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method of any one of the first aspects.

[0015] Fourthly, embodiments of this application provide a computer program product that, when run on a storage device, causes the storage device to execute any of the methods described in the first aspect above.

[0016] It is understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here.

[0017] In this embodiment, during storage device testing, a network protocol stack load is generated internally via a local loopback address, while a storage load is generated by performing read / write operations on the data disk. These two loads are then superimposed in parallel, and a power state switch is triggered during the load superposition process. Finally, the storage status of the data disk is checked to obtain the test results. This method generates both network protocol stack and storage loads internally, enabling extreme stress testing of the storage device without relying on external devices. Furthermore, the stress test and power state switch are performed synchronously, improving test sufficiency while maintaining testing efficiency. Secondly, by triggering a power state switch and checking the storage status during the sustained stress load, the technical problems of separation between storage device stress testing and power management verification, and incomplete test coverage, are resolved, thereby improving the testing reliability and troubleshooting efficiency of the storage device. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of this application; Figure 2 This is a flowchart illustrating a stress testing method for a storage device provided in an embodiment of this application. Figure 1 ; Figure 3This is a flowchart illustrating a stress testing method for a storage device provided in an embodiment of this application. Figure 2 ; Figure 4 This is a flowchart illustrating the process of determining the stress test results of a storage device according to an embodiment of this application; Figure 5 This is a schematic diagram illustrating the principle of a stress testing method for a storage device provided in an embodiment of this application; Figure 6 This is a timing diagram of a stress test process provided in an embodiment of this application; Figure 7 This is a structural block diagram of a pressure testing device provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of a storage device provided in an embodiment of this application. Detailed Implementation

[0020] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0021] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0022] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0023] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0024] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0025] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0026] First, the terminology used in the embodiments of this application will be explained: Network Attached Storage (NAS): refers to storage devices that provide data access services over a network, including but not limited to home NAS, enterprise NAS, and cloud storage gateway devices.

[0027] Solid State Drive (SSD): refers to a hard drive that uses semiconductor storage media to store data, including but not limited to solid state drives using M.2, SATA, U.2 or PCIe interfaces.

[0028] Hard disk drive (HDD): refers to a hard drive that uses magnetic platters and mechanical read / write arms to store data, including but not limited to HDDs using SATA or SAS interfaces.

[0029] M.2 interface: refers to a physical interface type used for internally installing solid-state drives.

[0030] NVMe (Non-Volatile Memory Express) protocol: refers to a high-speed transmission protocol designed for non-volatile storage media, which realizes data transmission based on the PCIe bus.

[0031] SATA (Serial Advanced Technology Attachment): refers to a serial hardware interface standard used to connect a host and a storage device for data transfer.

[0032] RAID (Redundant Array of Independent Disks) is a data storage technology that combines multiple physical storage devices into a single logical storage unit for management.

[0033] In the field of storage device testing, stress testing is an important means of verifying the stability of storage devices under extreme operating conditions. Current technologies primarily rely on external devices to apply network load or on simple tests using local read / write commands to perform stress testing on storage devices.

[0034] The inventors discovered that external testing methods are limited by the performance of auxiliary equipment, failing to accurately reflect the storage device's inherent limits, and that setting up the testing environment is cumbersome. Local read / write tests can only cover the sequential read / write performance of the storage medium, unable to simulate the comprehensive load brought by the network protocol stack. Furthermore, existing testing solutions typically only perform stress tests, making it difficult to detect data loss or system anomalies when the device malfunctions under high load.

[0035] In this embodiment of the application, when testing the storage device, a network protocol stack load is generated inside the storage device through the local loopback address, and a storage load is generated by performing read and write operations on the data disk. The two loads are superimposed in parallel, and a power state switch is triggered during the load superposition. Finally, the storage status of the data disk is checked to obtain the test results.

[0036] By employing the above method, network protocol stack load and storage load are simultaneously generated within the storage device, enabling extreme stress testing of the storage device without relying on external equipment. Furthermore, the stress test is performed synchronously with power state switching, improving test adequacy while ensuring testing efficiency. Secondly, by triggering power state switching and checking the storage status during sustained stress load, the problem of incomplete test coverage, which makes it difficult to detect data loss or system anomalies during high-load operation, is solved, thereby improving the reliability of storage device testing and the efficiency of fault diagnosis.

[0037] Figure 1 This is a schematic diagram illustrating an application scenario provided by an embodiment of this application. (Reference) Figure 1 This scenario includes storage devices.

[0038] In some embodiments, the stress testing method provided in this application can be applied to various storage devices employing a system disk and data disk separation architecture. The system disk is used to install the operating system and run test scripts, while the data disk is used to store user data and serve as the load target for stress testing. Optionally, the storage device includes, but is not limited to, NAS devices, personal computers, workstations, or servers. Taking a NAS device as an example, the NAS device can be deployed in a home or enterprise network, including, but not limited to, at least one of a single-bay NAS device, a multi-bay NAS device, or a self-built storage server.

[0039] In some embodiments, the storage device may execute the stress test of this application based on a test command triggered by the user, such as the user manually clicking the "Start Test" button through the management interface of the storage device or a mobile application to trigger the test; or the storage device may automatically execute the stress test of this application periodically according to a preset time; or the storage device may automatically execute the stress test of this application when an abnormality or warning occurs; or the storage device may automatically trigger the test when the system idles to a preset condition, etc.

[0040] In some embodiments, the storage device stores the test script, or the storage device can obtain the test script from other devices. The test script is used to automate all steps of the stress testing method described above. As an example, the test script can be a shell script that invokes system commands and testing tools to generate load, trigger power disturbances, and perform status checks.

[0041] In some embodiments, the storage device may be tested by the manufacturer using the stress test method described above before leaving the factory to verify the device quality, or the end user may trigger the test during use to troubleshoot the device.

[0042] Figure 2 This is a flowchart illustrating a stress testing method for a storage device provided in an embodiment of this application. Figure 1 It should be understood that the execution entity in this application embodiment is a storage device, which includes a data disk and a system disk.

[0043] In one possible implementation, the stress testing method described above can be executed automatically using test scripts running on a storage device, with the test scripts pre-stored on the system disk. When invoked, the test scripts are executed sequentially. Figure 2 The following steps are shown: S101, determine the target storage location for storing data on the data disk, and start the server process on the system disk. The server process is used to listen for the local loopback address of network packets.

[0044] In some embodiments, the storage device includes a data disk and a system disk. The system disk is used to install the operating system and store test scripts, while the data disk is used to store user data. Before executing the test, the storage device needs to determine the target storage location of the data disk. The target storage location refers to the mount path of the data disk in the operating system; the storage load generated during the test will be directed to this path.

[0045] In one possible implementation, the storage device employs a physically separated architecture for the system disk and data disk. The system disk is an M.2 interface NVMe solid-state drive, and the data disk is a SATA interface hard disk drive or solid-state drive, but not limited to these interface types. As an example, the storage device is a dual-bay or multi-bay network auxiliary storage device, with at least two data disks. Multiple data disks can be configured into a RAID array for use as a unified storage space. For example, with two data disks, the RAID array configured is (RAID 1 or RAID 5).

[0046] In some embodiments, after or simultaneously with determining the target storage location, the storage device starts a server process on the system disk. This server process listens for network connection requests on the local loopback address. As an example, after starting, the server process binds to the address 127.0.0.1 and enters a listening state, waiting for client processes to initiate connections. It should be noted that because the server process listens on the local loopback address, all subsequent network communication is completed within the storage device and does not go through the physical network interface card (NIC).

[0047] The above method can predetermine the target storage location for writing to the data disk, so that subsequent storage loads can be accurately applied to the data disk, avoiding test failures due to incorrect paths; at the same time, a server listening to the local loopback address is started on the system disk, so that subsequent network loads can complete the send and receive loop within the storage device without relying on external devices.

[0048] S102, send network packets to the local loopback address to generate network protocol stack load, and perform read and write operations at the target storage location to generate storage load.

[0049] In some embodiments, after completing the initialization configuration in S101, the storage device simultaneously initiates network stress generation and storage stress generation operations.

[0050] Specifically, during the network stress generation operation, the storage device starts a client process. This client process continuously sends network data packets to the local loopback address monitored by the server process in S101. The transmission path of these network data packets is a closed-loop path within the storage device's internal protocol stack. After the data packets are sent from the client process, they are processed by the operating system kernel's network protocol stack and directly loop back to the server process on the same device. In this process, the encapsulation, routing, checksum calculation, and protocol stack parsing of network data packets are all performed by the storage device's CPU and kernel protocol stack, resulting in continuous consumption of CPU and network protocol stack resources.

[0051] In the storage stress generation operation, the storage device invokes a storage testing tool to perform read and write operations on the target storage location determined in S101. As an example, the read and write operations include random read and write operations. Test data is generated from the system disk's memory space, transmitted to the SATA controller via the storage device's southbridge or PCH chip, and then written to the physical storage medium of the data disk by the SATA controller. In this process, the data flows through the memory bus, southbridge or PCH, SATA controller, and finally to the data disk, forming a realistic test of the SATA bus bandwidth, SATA controller processing power, and RAID array throughput.

[0052] In some embodiments, network stress generation and storage stress generation operations are executed in parallel. That is, the client process continuously sends network packets to the local loopback address, while the storage testing tool continuously performs read and write operations on the target storage location. During the network packet sending and read / write operations, the storage device's CPU needs to simultaneously handle interrupt requests from the network protocol stack and storage I / O. These two loads work together on the CPU, creating a parallel and superimposed high-load state to simulate the complex load conditions of multiple users accessing the system concurrently in real-world scenarios.

[0053] In this way, the storage device generates both network protocol stack load and storage load internally without relying on any external devices. These two loads are superimposed in parallel, covering the entire data link from the network protocol stack, CPU interrupt handling, bus transmission to the storage controller and data disk media. This makes the test conditions closer to real-world scenarios with multiple users accessing the device concurrently, avoiding test blind spots caused by single-dimensional testing, and laying a reliable load foundation for subsequent verification of data consistency under extreme load conditions and power disturbances.

[0054] S103, during the period when network protocol stack load and storage load persist, triggers the power state switch of the storage device.

[0055] In some embodiments, during the continuous operation of the network stress generation operation and the storage stress generation operation in S102, the storage device automatically triggers a power state switch. A power state switch refers to the transition of the storage device between different power states, including but not limited to at least one of the following: suspended state, hibernation state, system restart, or physical power failure.

[0056] In some embodiments, power state switching can be automatically triggered by the master control script while both network protocol stack load and storage load are not stopped. The master control script sends instructions to the operating system's power management service, and the operating system executes the corresponding power management operations upon receiving the instructions. Since power state switching occurs during the continuous superposition of two loads, when both the CPU and storage controller are under high load, the power management module needs to save and restore the device state under heavy system conditions, thereby effectively verifying the reliability of power switching of the storage device under extreme operating conditions.

[0057] As an example, in a suspended or hibernating state, the storage device saves the current system state and enters a low-power mode after receiving a power management command; the storage device is then woken up and returns to normal operation from the low-power mode, and the test process continues to execute subsequent steps.

[0058] As an example, for system restarts, the storage device performs a restart operation after receiving a restart command. After the operating system reboots, the test script is called again and continues to execute subsequent steps.

[0059] As an example, in the event of a physical power failure, the storage device cuts off power after receiving a power failure command, and then power is restored. After the operating system reboots, the test script is invoked again and continues to execute subsequent steps.

[0060] By introducing power state switching when the storage device is under high load, the extreme conditions of unexpected power loss, hibernation, or restart during busy periods in real-world usage scenarios can be simulated, thereby verifying the device's data retention and system recovery capabilities under extreme conditions.

[0061] S104 checks the status information of the data disk and system disk, and obtains the stress test results of the storage device based on the status information.

[0062] In some embodiments, the status check action of step S104 can be distributed between the stress phase and the recovery phase of the storage device.

[0063] During the stress test phase, the storage device acquires the read / write throughput of the data disk while the network protocol stack load and storage load of S102 operate in parallel to verify whether the read / write performance of the data disk is within the normal range. As an example, if the data disk is a SATA interface storage medium, its read / write throughput is limited by the bandwidth limit of the SATA interface. If the actual throughput is within the normal fluctuation range of this bandwidth limit, it indicates that the read / write performance of the data disk is normal. Simultaneously, the storage device monitors the response status of the system disk during the stress test phase. Since the system disk and data disk are physically independent, high-load read / write operations on the data disk should not affect the normal operation of the system disk. If the system disk maintains a smooth response during the stress test, it indicates that the isolation between the system disk and the data disk is effective.

[0064] During the recovery phase, after the storage device exits the power state switch, it checks whether the data disk can be successfully mounted to the target storage location determined in S101, and checks whether the written data on the data disk is complete. If the data disk cannot be mounted normally or the written data is corrupted, it indicates that the power disturbance caused the data disk to malfunction. Simultaneously, the storage device also checks whether the file system of the data disk is corrupted. If the file system check passes and the data integrity verification is successful, it indicates that the storage device can still maintain data consistency under the combined effects of extreme load and power disturbance.

[0065] Furthermore, the storage device obtains its stress test result based on one or more of the above-mentioned check results. If all the above checks pass, the stress test result is considered passed; if any check fails, the stress test result is considered failed.

[0066] By performing multi-dimensional status checks during the stress and recovery phases, the stability of the system disk and data disk under the physical isolation architecture can be verified, as well as the data consistency and system recovery capabilities of the storage device under extreme operating conditions and power disturbances.

[0067] Figure 3 This is a flowchart illustrating a stress testing method for a storage device provided in an embodiment of this application. Figure 2 It should be understood that the processing method in this application embodiment is executed by a storage device. For example... Figure 3 As shown, the stress testing method includes the following steps: S201, which sets up at least two data disks as a redundant disk array.

[0068] In some embodiments, the storage device is configured with multiple data disks, which provide storage space for user data. To improve storage capacity utilization, parallel data read / write capabilities, or data redundancy and security, the storage device uses at least two data disks to form a redundant array, i.e., a RAID array. As an example, the RAID array level can be RAID 1 or RAID 5, but is not limited to these levels. RAID 1 provides data redundancy protection by writing the same data to two data disks simultaneously using mirroring; RAID 5 provides redundancy protection while improving storage space utilization and read / write performance through striped writing and distributed parity. By forming a redundant array, multiple physical data disks are recognized as a unified logical storage unit in the operating system, facilitating subsequent unified mounting and access.

[0069] S202, mount the redundant disk array to the specified directory and determine the specified directory as the target storage location.

[0070] In some embodiments, the storage device mounts the redundant disk array assembled in S201 to a designated directory of the operating system. Mounting refers to the process of associating storage space in the storage device with a directory in the operating system's directory tree. After successful mounting, applications and testing tools can access the data disk's storage space through this directory. The storage device designates this designated directory as the target storage location, and all read and write operations in subsequent storage load generation operations are directed to this directory. This method determines the target of the storage load, ensuring that data write operations during testing are accurately applied to the data disk, rather than the system disk or other storage areas.

[0071] S203, start the client process and start multiple parallel threads on the client.

[0072] In some embodiments, the storage device starts a client process after completing environment initialization. This client process is used to send network packets to the server process started in S101. After the client process starts, multiple parallel threads are further started. Each thread independently initiates a connection to the server process and sends network packets. The multiple threads execute in parallel, thereby generating concurrent network traffic and increasing the load on the network protocol stack. As an example, the number of parallel threads can be used to simulate a real-world scenario where multiple users access the storage device simultaneously; for example, starting 10 parallel threads (simulating 10 users).

[0073] By enabling multiple parallel threads, the client process can more realistically simulate scenarios of concurrent access by multiple users, making the network protocol stack load closer to actual usage conditions.

[0074] S204 sends network data packets to the local loopback address through multiple parallel threads to generate network protocol stack load until the network protocol stack resource utilization of the storage device reaches a preset threshold or continues to run for a preset duration.

[0075] In some embodiments, the status information includes at least one of the following: the response status of the system disk, the read / write status of the data disk, and the storage status of the data disk.

[0076] In some embodiments, the client process continuously sends network packets to the local loopback address through multiple parallel threads started in S203. Since the destination address is the local loopback address, all network packets do not pass through the physical network card, but are encapsulated, routed, and loopback processed within the network protocol stack of the operating system kernel. During this process, the processing logic of the network protocol stack (including packet processing, checksum calculation, congestion control, etc. at each layer of the TCP / IP protocol stack) is continuously triggered, resulting in continuous consumption of CPU and network protocol stack resources.

[0077] In some embodiments, network packet transmission continues until a preset stopping condition is met. As an example, the stopping condition could be that the network protocol stack resource utilization of the storage device reaches a preset threshold. For instance, when the CPU's network interrupt handling utilization reaches 90% or higher, it can be considered that the network protocol stack load has been sufficiently applied, and network packet transmission stops at this point. As another example, the stopping condition could be that continuous operation reaches a preset duration. For example, the test script could be set to transmit network packets continuously for 10 minutes, automatically stopping transmission after the time expires. By using these methods, the intensity of the network protocol stack load is ensured to be sufficient and controllable, improving the reliability of the test results.

[0078] S205, triggers a power state switch for the storage device during the period when network protocol stack load and storage load persist; In some embodiments, the storage device triggers a power state transition while network packet transmission and read / write operations are both continuously running. The power state transition simulates power events such as suspension, hibernation, restart, or power failure that occur under extreme load conditions in real-world usage scenarios. The power state transition includes at least one of the following: The storage device is triggered to switch to a suspended state. This suspended state corresponds to the S3 state, in which the storage device cuts off power to the CPU and most hardware, retaining power only to the memory to maintain the data in memory; the system state is preserved in memory. Upon wake-up, the storage device restores the system state from memory, with a relatively fast recovery speed.

[0079] Triggering the storage device to switch to hibernation mode. Hibernation mode corresponds to state S4. In this state, the storage device writes the data in memory to a hibernation file on the data disk or system disk, and then completely cuts off power. Upon waking, the storage device reads the data from the hibernation file and restores it to memory. The recovery speed is slow but consumes no power.

[0080] Triggering a storage device restart. A restart refers to the process by which the storage device reboots the operating system. During a restart, the system goes through a normal shutdown process and a re-initialization process.

[0081] Triggering a power outage on the storage device. A power outage refers to the complete disconnection of power to the storage device, simulating a physical power failure. As an example, the storage device can achieve physical power-off and power-on operations by controlling power relays, etc.

[0082] By introducing various types of power state switching when the storage device is operating under high load, the above methods can cover all kinds of power events that may occur in real-world usage scenarios, thereby comprehensively verifying the stability and data retention capabilities of the storage device under extreme operating conditions and power disturbances.

[0083] S206, check the status information of the data disk and system disk, and obtain the stress test results of the storage device based on the status information.

[0084] In some embodiments, the storage device performs status checks on the data disk and system disk during the stress and recovery phases, respectively. During the stress phase, the storage device checks the response status of the system disk and the read / write status of the data disk to verify the effectiveness of the isolation between the system disk and the data disk, as well as the performance of the data disk under stress. During the recovery phase, the storage device checks the storage status of the data disk to verify whether power disturbances have caused damage to the data disk or data loss. Based on the above status information, the storage device obtains a comprehensive stress test result.

[0085] By using the above methods, the state of storage devices after stress testing and power disturbances can be evaluated from multiple dimensions, resulting in comprehensive and accurate test results.

[0086] Figure 4 This is a flowchart illustrating the process for determining the stress test results of a storage device according to an embodiment of this application. It should be understood that the execution entity of the processing method in this embodiment is the storage device. Figure 4 As shown, the process of determining the stress test results includes the following steps: S301 monitors the response status of the system disk and the read / write status of the data disk during periods of concurrent network protocol stack load and storage load. In some embodiments, during the parallel operation of network stress generation and storage stress generation, the storage device continuously monitors the status information of the system disk and data disk.

[0087] For the system disk, the storage device monitors its response status. Since the system disk and data disk are physically independent, the system disk runs the operating system and test scripts, while the data disk handles the storage load. Ideally, the system disk's response should not be affected when the data disk is under high read / write load. If the system disk experiences stuttering or delays, it indicates resource contention or bus contention between the system disk and data disk, suggesting poor isolation.

[0088] In some embodiments, when the system disk operates smoothly, it is determined that the isolation between the system disk and the data disk is effective, and the response status is normal. Optionally, the smoothness of system disk operation can be determined by monitoring the system disk's I / O wait time, CPU utilization, or SSH connection response status.

[0089] For data disks, the storage device monitors their read / write status. Specifically, during sustained storage load, when the data disk is under high-intensity read / write operations, the storage device obtains the actual read / write throughput of the data disk. Since the data disk connects to the storage device's motherboard using a SATA interface, and the SATA interface itself has a bandwidth limit, the data disk's read / write throughput should not exceed the theoretical bandwidth limit of the SATA interface. Specifically, if the actual read / write throughput is less than or equal to the preset throughput, it indicates that the data disk's read / write performance is within the normal range, and the read / write status is normal. If the actual read / write throughput is significantly higher than the preset throughput, this situation may be inconsistent with the actual interface type of the data disk, possibly indicating that test data was incorrectly written to the system disk or other high-speed storage areas; in this case, the read / write status is abnormal.

[0090] As an example, the preset throughput can be the theoretical bandwidth limit of the SATA interface or the value obtained by multiplying the limit by a certain coefficient. For a SATA interface data disk, its theoretical bandwidth limit is about 600MB / s, and the preset throughput can be set to a value slightly lower than this theoretical value (e.g., 500MB / s) to eliminate the influence of fluctuations in the test environment.

[0091] S302, after exiting the power state switch, checks the storage status of the data disk. The storage status indicates whether the data disk was able to successfully store data.

[0092] In some embodiments, after the storage device exits a power state transition, it performs a storage state check on the data disk. This storage state check verifies whether power disturbances have affected the availability and data integrity of the data disk.

[0093] In some embodiments, checking the storage status of a data disk includes the following steps: S1, check whether the data disk can be mounted to the target storage location and obtain the mount check results.

[0094] Mounting is a prerequisite for the operating system to access the data disk storage space. If the data disk cannot be mounted properly, the data within it cannot be recognized and accessed by the operating system. As an example, if the data disk can be successfully mounted to the target storage location after a power disturbance, the mount check result is a successful mount; if the mount fails, the mount check result is a mount failure, indicating that the power disturbance caused a serious abnormality in the data disk's file system or storage device hardware.

[0095] S2, if the data disk can be mounted to the target storage location, checks whether the file system metadata of the data disk is corrupted and obtains the consistency check results.

[0096] After the data disk is successfully mounted, the storage device further checks for file system corruption. File system metadata records critical information such as file storage location, size, and permissions. Corrupted metadata can lead to unreadable files or incorrect data content. As an example, the storage device executes a file system consistency check tool to verify the integrity of the file system metadata. If the file system check passes, the consistency check result is that the data is not corrupted; if the check finds corrupted metadata, the consistency check result is that the data is corrupted.

[0097] S3, if the mount check result is successful and the consistency check result is that the data is not corrupted, determine that the data disk's storage status is that it can successfully store data.

[0098] When the data disk is successfully mounted and the file system is not corrupted, it indicates that the data disk can still work normally after undergoing multiple tests of network load, storage load, and power disturbance, and its storage status is normal. If the mount check fails or the consistency check finds data corruption, the storage status is abnormal, indicating that the power disturbance has caused the data disk to be unusable or data to be lost.

[0099] By using the above methods, the state of the data disk after a power disturbance is comprehensively checked from both the mount level and the file system level, ensuring that the data disk can be recognized by the operating system and that the data structure stored inside is complete and usable.

[0100] S303 obtains the stress test results of the storage device based on the response status of the system disk, the read / write status of the data disk, and the storage status of the data disk.

[0101] In some embodiments, the storage device integrates the various status information obtained in S301 and S302 to generate stress test results for the storage device. Specifically, the stress test results are obtained in the following ways: If the system disk responds normally, it indicates that the physical isolation between the system disk and the data disk is effective during the storage load process, and the normal operation of the system disk is not affected by the high load read and write of the data disk.

[0102] If the data disk's read / write status is normal, it indicates that during storage load conditions, the data disk's read / write performance is within the normal range of the SATA interface bandwidth, and the data disk and SATA controller can work normally under extreme throughput pressure.

[0103] If the data disk's storage status indicates that it can successfully store data, it means that after a power disturbance, the data disk can be mounted normally, the file system is not damaged, and the data remains intact. The storage device can still ensure data consistency under the combined effects of extreme load and power disturbance.

[0104] When all three states are normal, the storage device determines that the stress test result is passed; if any of the above states are abnormal, the storage device determines that the stress test result is failed and records the corresponding abnormal information.

[0105] By using the above methods, the stress test results of storage devices are comprehensively evaluated from three dimensions: system disk isolation effect, data disk read / write performance, and data integrity after power disturbance, so that the test conclusions are comprehensive, accurate, and traceable.

[0106] Figure 5 This is a schematic diagram illustrating the principle of a stress testing method for a storage device according to an embodiment of this application. The following is in conjunction with... Figure 5 The overall architecture and working principle of the embodiments of this application are described.

[0107] refer to Figure 5 The stress testing method provided in this application is applied to a storage device that employs a physically separated system disk and data disk architecture. The system disk is an M.2 interface NVMe protocol solid-state drive used to install the operating system, store test scripts, and record test logs; the data disk is a SATA interface mechanical hard drive or solid-state drive used to store user data and serve as the load target for stress testing. As an example, the number of data disks is at least two, and multiple data disks can be configured into a redundant array of disks (RAID), such as RAID 0 or RAID 1. Figure 5 Taking two data disks as an example to form a RAID0 array, the array is mounted to a specified directory (e.g., / home / test), which is determined as the target storage location.

[0108] In this embodiment, the storage device runs a test control layer, which is stored in the system disk as a shell script. When the test script is invoked, it executes test logic through system memory, applying load to the data disk and network protocol stack.

[0109] Continue to refer to Figure 5 During stress testing, the test control layer initiates write operations to the data disk via system memory. Specifically, the test script calls storage testing tools to perform read and write operations on the target storage location of the data disk. The written data is transferred from system memory to the redundant disk array (DBA) after being scheduled by the kernel I / O scheduler, and finally written to the physical medium of the SATA data disk. Because the test script runs in the system disk's memory space, while the data is actually written to the SATA data disk, this data flow path is forced to traverse the entire link from the memory bus, southbridge or PCH chip, SATA controller to the data disk medium. Figure 5 In the illustrated embodiment, the data write path is represented by a solid arrow.

[0110] Meanwhile, the test control layer also generates network protocol stack load through the local loopback address. Specifically, the test script starts a network test client process, continuously sending network data packets to the local loopback address listened to by the server process running on the system disk. After the network data packets are sent from the client process, they are processed by the network protocol stack in the operating system memory and directly looped back to the server process on the same storage device. Figure 5 In the illustrated embodiment, the closed-loop path of the network protocol stack load is represented by a dashed arrow. This network load is superimposed on the aforementioned storage load, jointly impacting the CPU and network protocol stack resources of the storage device.

[0111] Meanwhile, the test control layer also generates network protocol stack load through the local loopback address. Specifically, the test script starts a network test client process, which continuously sends network data packets to the local loopback address listened to by the server process running on the system disk. After the network data packets are sent from the client process, they are processed by the operating system kernel's network protocol stack and directly loop back to the server process on the same storage device. Figure 5 In the illustrated embodiment, the closed-loop path of the network protocol stack load is represented by a dashed arrow. This network load is superimposed on the aforementioned storage load, jointly impacting the CPU and network protocol stack resources of the storage device.

[0112] pass Figure 5The architecture and principles illustrated demonstrate that the storage device generates both network protocol stack load and storage load simultaneously within the device itself, without relying on any external devices. These two loads are superimposed in parallel, covering the entire data link from the network protocol stack, CPU interrupt handling, bus transmission to the storage controller and data disk media. Power state switching is triggered during the continuous existence of these two loads, and the storage status is checked after the power state switching ends. This solves the technical problem of the separation between storage device stress testing and power management verification, resulting in incomplete test coverage. It significantly improves the sufficiency and reliability of testing storage devices under extreme operating conditions.

[0113] Corresponding to the processing method in the above embodiments, Figure 6 This is a timing diagram of a stress test process provided in an embodiment of this application. The following is in conjunction with... Figure 6 The timing relationship and execution entity of each stage in the stress test process in the embodiments of this application are explained.

[0114] refer to Figure 6 The stress testing method provided in this application includes four stages executed sequentially: load ramp-up stage, stable high-voltage operation stage, power disturbance stage, and system recovery stage. The test script is executed primarily by the system disk of the storage device. Changes in system state are controlled by the operating system of the storage device, changes in power state are executed by the power management module of the storage device in response to system commands, and read / write operations on stored data are executed by the SATA controller and data disk of the storage device in response to the commands of the test script.

[0115] During the load ramp-up phase, the test script launches the storage testing tool and the network testing client. The storage testing tool begins performing read and write operations to the target storage location on the data disk, while the network testing client begins sending network packets to the local loopback address. At this time, both the storage load and the network protocol stack load on the storage device are gradually increasing and have not yet reached their peak values.

[0116] During the stable high-voltage operation phase, both the storage load and network protocol stack load of the storage device reach and remain at preset high load levels. On the storage side, the test script continuously performs high-concurrency random read and write operations on the data disk through storage testing tools, keeping the data disk and SATA controller in a high-throughput state. On the network side, the test script continuously sends network data packets to the local loopback address through a network test client, keeping the network protocol stack in a high-throughput state. The system status is a high-load operation state, and the power supply status is a normal power supply state. During this phase, the storage device generates both network protocol stack load and storage load internally without relying on any external devices. These two loads are superimposed in parallel, jointly affecting the CPU and network protocol stack resources of the storage device.

[0117] During the power disturbance phase, the test script automatically triggers a power state switch during the continuous operation of the load in the stable high-voltage operation phase. Specifically, the test script sends a power state switch command to the power management module of the storage device, and the power management module responds to the command by performing the corresponding power operation. For example... Figure 6 As shown, the power state switches from normal power supply to any of the following states: suspended, hibernation, power outage during restart, or physical power failure. At the moment of power state switching, the storage device is operating under high load, and the processes of storage and network testing tools are interrupted due to the system state change. This stage simulates the extreme conditions of a sudden power event on a storage device under extreme load in real-world usage scenarios.

[0118] During the system recovery phase, after the storage device exits a power state switch and is powered on or woken up, the operating system executes the system boot process, and the file system is remounted. The test script automatically performs a data integrity check after system recovery, checking the integrity of written data on the data disk and whether the file system is corrupted. If both the data integrity check and the file system check pass, it indicates that the storage device can maintain data consistency under the combined effects of extreme load and power disturbances.

[0119] pass Figure 6 The timing flow shown covers all aspects of power disturbance testing under extreme conditions, from load application, high load maintenance, power disturbance triggering to system recovery and verification. The test script acts as the control core in each stage, automatically scheduling the collaborative work of each module without manual intervention, thus achieving fully automated testing.

[0120] Corresponding to the processing method in the above embodiments, Figure 7 This is a structural block diagram of a pressure testing device according to an embodiment of this application. The optimized rule generation device is applied to a storage device. For ease of explanation, only the parts relevant to the embodiment of this application are shown. (Refer to...) Figure 7 The device includes: The server process startup module 71 is used to determine the target storage location for storing data on the data disk and to start the server process on the system disk. The server process is used to listen for the local loopback address of network packets. The load generation module 72 is used to send network data packets to the local loopback address to generate network protocol stack load, and to perform read and write operations at the target storage location to generate storage load. The power state switching module 73 is used to trigger the power state switching of the storage device during the continuous existence of network protocol stack load and storage load. The test result acquisition module 74 is used to check the status information of the data disk and system disk, and obtain the stress test results of the storage device based on the status information.

[0121] In some embodiments, the storage device includes at least two data disks; the server process startup module 71 is specifically used for: Configure at least two data disks into a redundant disk array; Mount the redundant disk array to the specified directory and determine the specified directory as the target storage location.

[0122] In some embodiments, the service process startup module 71 is specifically used to: start the client process and start multiple parallel threads of the client; send network data packets to the local loopback address through multiple parallel threads to generate network protocol stack load until the network protocol stack resource utilization rate of the storage device reaches a preset threshold or continues to run for a preset duration.

[0123] In some embodiments, the status information includes at least one of the following: the response status of the system disk, the read / write status of the data disk, and the storage status of the data disk; The test result acquisition module 74 is specifically used to: monitor the response status of the system disk and the read / write status of the data disk during the parallel superposition of network protocol stack load and storage load; After exiting the power state switch, check the storage status of the data disk, which indicates whether the data disk was able to successfully store data. The stress test results of the storage device are obtained based on the response status of the system disk, the read / write status of the data disk, and the storage status of the data disk.

[0124] In some embodiments, when the operation of the system disk remains smooth, it is determined that the isolation between the system disk and the data disk is effective, and the response status is normal. The read / write status of the data disk is determined to be normal when the read / write throughput is less than or equal to the preset throughput.

[0125] In some embodiments, the test result acquisition module 74 is specifically used to: check whether the data disk can be mounted to the target storage location and obtain the mounting check result; If the data disk can be mounted to the target storage location, check whether the file system metadata of the data disk is corrupted and obtain the consistency check results; If the mount check shows successful mounting and the consistency check shows no data corruption, the data disk's storage status is determined to be capable of successfully storing data.

[0126] In some embodiments, when the power state switching module 73 triggers a power state switch of the storage device, it includes at least one of the following: Trigger storage device to switch to suspend state; trigger storage device to switch to hibernation state; trigger storage device to restart; trigger storage device to power off.

[0127] In some embodiments, the system disk includes an M.2-based hard disk, and the data disk includes a SATA-based solid-state drive or hard disk drive.

[0128] Figure 8 This is a schematic diagram of the structure of a storage device provided in an embodiment of this application. Figure 8 As shown, the storage device includes: at least one processor 80 ( Figure 8 (Only one is shown in the diagram) a processor, a memory 81, and a computer program 82 stored in the memory 81 and executable on at least one processor 80, wherein the processor 80 executes the computer program 82 to implement the steps in any of the above-described model update method embodiments.

[0129] Storage device 8 can be a computing device such as a desktop computer, laptop, handheld computer, or cloud server. This storage device may include, but is not limited to, processor 80 and memory 81. Those skilled in the art will understand that... Figure 8 This is merely an example of storage device 8 and does not constitute a limitation on storage device 8. It may include more or fewer components than shown, or combine certain components, or different components, such as input / output devices, network access devices, etc.

[0130] The processor 80 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0131] In some embodiments, memory 81 may be an internal storage unit of storage device 8, such as a hard disk or memory of storage device 8. In other embodiments, memory 81 may be an external storage device of storage device 8, such as a plug-in hard disk, smart media card (SMC), secure digital card (SD) card, flash card, etc., provided on storage device 8. Furthermore, memory 81 may include both internal storage units and external storage devices of storage device 8. Memory 81 is used to store operating system, storage device, bootloader, data, and other programs, such as program code of computer programs. Memory 81 can also be used to temporarily store data that has been output or will be output.

[0132] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a device / control device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks.

[0133] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0134] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0135] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0136] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps described in the various method embodiments above.

[0137] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the above-described method embodiments.

[0138] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. A computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographic device / storage device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, a computer-readable medium cannot be an electrical carrier signal or a telecommunication signal.

[0139] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0140] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0141] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0142] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0143] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A stress testing method for a storage device, characterized in that, The storage device includes a data disk and a system disk; the method includes: Determine the target storage location for storing data on the data disk, and start a server process on the system disk. The server process is used to listen for the local loopback address of network packets. Send network packets to the local loopback address to generate network protocol stack load, and perform read and write operations at the target storage location to generate storage load; while the network protocol stack load and the storage load exist, trigger the power state switch of the storage device; Check the status information of the data disk and the system disk, and obtain the stress test results of the storage device based on the status information.

2. The method according to claim 1, characterized in that, The storage device includes at least two of the data disks; Determining the target storage location for storing data on the storage disk includes: At least two of the data disks are configured into a redundant disk array; The redundant disk array is mounted to a specified directory, and the specified directory is determined as the target storage location.

3. The method according to claim 1, characterized in that, Sending network packets to the local loopback address to generate network protocol stack payload includes: Start the client process and enable multiple parallel threads for the client; The network protocol stack load is generated by sending network data packets to the local loopback address through multiple parallel threads until the network protocol stack resource utilization of the storage device reaches a preset threshold or continues to run for a preset duration.

4. The method according to any one of claims 1-3, characterized in that, The status information includes at least one of the following: the response status of the system disk, the read / write status of the data disk, and the storage status of the data disk; The step of checking the status information of the data disk and the system disk, and obtaining the stress test results of the storage device based on the status information, includes: During the parallel superposition of the network protocol stack load and the storage load, the response status of the system disk and the read / write status of the data disk are monitored. After exiting the power state switch, check the storage status of the data disk, which indicates whether the data disk can successfully store data. The stress test results of the storage device are obtained based on the response status of the system disk, the read / write status of the data disk, and the storage status of the data disk.

5. The method according to claim 4, characterized in that, When the operation of the system disk remains smooth, it is determined that the isolation between the system disk and the data disk is effective, and the response status is normal. When the read / write throughput of the data disk is less than or equal to the preset throughput, the read / write status of the data disk is determined to be normal.

6. The method according to claim 4, characterized in that, After exiting the power state switch, checking the storage status of the data disk includes: Check whether the data disk can be mounted to the target storage location and obtain the mount check result; If the data disk can be mounted to the target storage location, check whether the file system metadata of the data disk is corrupted and obtain the consistency check result; If the mount check result indicates successful mounting and the consistency check result indicates that the data is not corrupted, then the storage status of the data disk is determined to be capable of successfully storing data.

7. The method according to any one of claims 1-3, characterized in that, The triggering of the power state switching of the storage device includes at least one of the following: Trigger the storage device to switch to a suspended state; Trigger the storage device to switch to hibernation mode; Trigger the restart of the storage device; This triggers a power outage of the storage device.

8. The method according to any one of claims 1-3, characterized in that, The system disk includes an M.2-based hard drive, and the data disk is a SATA-based solid-state drive or hard disk drive.

9. A storage device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as claimed in any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 8.

Images