Solid state disk management method and apparatus, electronic device, and storage medium

Abstract

The present disclosure provides a solid state disk management method and apparatus, an electronic device, and a storage medium. The method comprises: stopping a read / write operation of a solid state disk on the basis of a received mode conversion instruction, the mode conversion instruction comprising a target mode; generating mode conversion information of the solid state disk, the mode conversion information comprising configuration management information of storage units of the solid state disk in a current mode; updating a driving program and a firmware program corresponding to the solid state disk into a driving program and a firmware program corresponding to the target mode; and on the basis of the mode conversion information and original storage data in the storage units, modifying a medium configuration corresponding to the storage units in the current mode into a medium configuration corresponding to the target mode. Embodiments of the present disclosure can solve the technical problems in the related art of relatively large data migration overhead and relatively low mode type conversion efficiency during mode conversion of a solid state disk.

Description

[0001] Solid-State Drive Management Method, Device, Electronic Device, and Storage Medium TECHNICAL FIELD The present disclosure relates to the field of data storage technology, and more specifically to a solid-state drive management method, device, electronic device, and storage medium. BACKGROUND With users' increasing demands for data storage and processing, solid-state drives (SSDs) have become the preferred choice for most large data centers and enterprise software applications. Currently, SSDs include not only traditional non-volatile memory express (NVMe) SSDs, but also different types such as Flexible Data Placement (FDP) and Zoned Name Space (ZNS). Because these three types of SSDs store and manage data differently, they cannot be directly mixed and used, nor can spare parts be shared. In related art, multiple SSDs of each type provide storage services in independent resource pools within a storage cluster of that type. However, these independent resource pools are not conducive to the scheduling and management of large-scale storage resources. Furthermore, changing the type of a solid-state drive typically requires reading data from the drive, formatting it, and then writing the original data. This increases data migration overhead, resulting in low SSD type conversion efficiency and poor SSD performance and flexibility. In view of the above problems, the present disclosure provides a solid-state drive management method, apparatus, electronic device, and storage medium to at least address the technical issues in the related art of high data migration overhead and low mode type conversion efficiency during SSD mode conversion. According to a first aspect of an embodiment of the present disclosure, a solid-state drive management method is provided, comprising: stopping read / write operations on the solid-state drive based on a received mode conversion instruction; the mode conversion instruction including a target mode; generating mode conversion information for the solid-state drive; the mode conversion information including configuration management information for each storage unit of the solid-state drive in the current mode; updating the driver and firmware corresponding to the solid-state drive to the driver and firmware corresponding to the target mode; and modifying the media configuration corresponding to the storage unit in the current mode to the media configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit.According to a second aspect of an embodiment of the present disclosure, a solid-state drive management device is provided. The solid-state drive management device includes: a stopping unit configured to stop read / write operations on the solid-state drive based on a received mode conversion instruction; the mode conversion instruction includes a target mode; a generating unit configured to generate mode conversion information for the solid-state drive; the mode conversion information includes configuration management information for each storage unit of the solid-state drive in a current mode; an updating unit configured to update the driver and firmware corresponding to the solid-state drive to the driver and firmware corresponding to the target mode; and a modifying unit configured to modify the media configuration corresponding to the storage unit in the current mode to the media configuration corresponding to the target mode based on the mode conversion information and the original storage data in the storage units. According to a third aspect of an embodiment of the present disclosure, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the computer program to implement the solid-state drive management method according to the first aspect. According to the third aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, the computer-readable storage medium storing the computer program, wherein the computer program is configured to execute the solid-state drive management method according to the first aspect when executed. In an embodiment of the present disclosure, a method is provided for stopping read / write operations on a solid-state drive (SSD) based on a received mode conversion instruction; the mode conversion instruction includes a target mode; generating mode conversion information for the SSD; the mode conversion information including configuration management information for each storage unit of the SSD in the current mode; updating the driver and firmware corresponding to the SSD to the driver and firmware corresponding to the target mode; and modifying the media configuration corresponding to the storage unit in the current mode to the media configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit. Compared to existing SSD mode conversion methods, the present disclosure can achieve SSD type conversion without formatting data after reading it from the drive. This not only reduces data movement operations and improves the efficiency of SSD mode conversion, but also enhances the performance and flexibility of SSD management and facilitates the scheduling and management of large-scale storage resources. BRIEF DESCRIPTION OF THE DRAWINGS Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the preferred embodiments below. The drawings are provided for illustration purposes only and are not to be construed as limiting the present disclosure. Also, like reference numerals are used throughout the drawings to denote like parts.In the accompanying drawings: FIG1 is a schematic diagram of an application environment of an optional solid-state hard disk management method according to an embodiment of the present disclosure; FIG2 is a schematic diagram of a flow chart of an optional solid-state hard disk management method according to an embodiment of the present disclosure; FIG3 is a schematic diagram of an optional solid-state hard disk mode conversion according to an embodiment of the present disclosure; FIG4 is a schematic diagram of an optional solid-state hard disk partition configuration according to an embodiment of the present disclosure; FIG5 is a schematic diagram of an optional solid-state hard disk mode conversion information according to an embodiment of the present disclosure; FIG6 is a schematic diagram of another optional solid-state hard disk mode conversion according to an embodiment of the present disclosure; FIG7 is a schematic diagram of another optional solid-state hard disk partition configuration according to an embodiment of the present disclosure; FIG8 is a schematic diagram of yet another optional solid-state hard disk mode conversion according to an embodiment of the present disclosure; FIG9 is a schematic diagram of yet another optional solid-state hard disk partition configuration according to an embodiment of the present disclosure; FIG10 is a schematic diagram of yet another optional solid-state hard disk mode conversion according to an embodiment of the present disclosure; FIG11 is a schematic diagram of yet another optional solid-state hard disk partition configuration according to an embodiment of the present disclosure; FIG12 is a schematic diagram of a flow chart of yet another optional solid-state hard disk management method according to an embodiment of the present disclosure; FIG13 is a schematic diagram of the structure of a solid-state hard disk management device provided by an embodiment of the present disclosure; Figure 14 is a schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS To help those skilled in the art better understand the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments represent only a portion of the present disclosure, and are not exhaustive. Based on the embodiments of the present disclosure, all other embodiments devised by persons of ordinary skill in the art without inventive effort should fall within the scope of protection of the present disclosure. It should be noted that the terms "first," "second," and so on, in the specification and claims of the present disclosure, and in the accompanying drawings, are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that such terms are interchangeable where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "comprises" and "having" and any variations thereof are intended to cover a non-exclusive inclusion. For example, a process, method, system, product or apparatus that includes a series of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, product or apparatus.The following are explanations of technical terms that may be used in this disclosure: Zoned Name Space (ZNS): Applicable to sequential writes, including foldable media disk drives and solid-state drives. Flexible Data Placement (FDP): No sequential write restrictions, applicable to Non-Volatile Memory Express (NVMe) devices, primarily solid-state drives (SSDs).

[0002] FTL: Flash Translation Layer.

[0003] GC: Garbage Collection, garbage collection mechanism.

[0004] LBA: Logical Block Address.

[0005] PBA: Physical Block Address. As an optional implementation, the above-mentioned solid-state drive management method can be applied, but is not limited to, in the application environment shown in Figure 1. This application environment may include, but is not limited to, application to a server equipped with a solid-state drive. The server includes a host instance and a solid-state drive (SSD) 1. The host instance is installed with multiple application software, such as Application 1 and Application 2, as well as an SSD management control program. Each of these application software interacts with SSD 1 through an SSD driver. SSD 1 includes an SSD controller and SSD firmware. The SSD firmware writes data to physical storage space (the flash memory cells of the SSD) through logical storage space. The above-mentioned server can be a single server, a server cluster consisting of multiple servers, or a cloud server. The cloud server includes, but is not limited to, a private cloud server or a public cloud server. The above-mentioned solid-state drive management method specifically involves the following steps: an SSD control program halts read / write operations on the solid-state drive based on a received mode conversion instruction; the mode conversion instruction includes a target mode; mode conversion information is generated for the solid-state drive; the mode conversion information includes configuration management information for each storage unit of the solid-state drive in the current mode; the driver and firmware corresponding to the solid-state drive are updated to the driver and firmware corresponding to the target mode; and based on the mode conversion information and the original storage data in each storage unit, the media configuration corresponding to the storage unit in the current mode is modified to the media configuration corresponding to the target mode. Current solid-state drives include not only traditional non-volatile memory express (NVMe) SSDs, but also flexible data placement (FDP) and zoned name space (ZNS) SSDs. Because these three types of SSDs store and manage data differently, they cannot be directly mixed and cannot share spare parts. In related art, multiple SSDs of each type provide storage services as independent resource pools within a storage cluster of that type. However, these multiple independent resource pools are not conducive to the scheduling and management of large-scale storage resources. Furthermore, changing the SSD type typically requires reading the data from the drive, formatting it, and then writing the original data. This increases data transfer overhead, resulting in low SSD mode conversion efficiency and poor performance and flexibility.In order to solve the above technical problem, as an optional implementation method, as shown in FIG2 , an embodiment of the present disclosure provides a solid state drive management method, comprising the following steps:

[0006] S202: Stop read / write operations on the solid-state drive based on the received mode conversion instruction; the mode conversion instruction includes a target mode. Specifically, in the disclosed embodiment, after a server equipped with a solid-state drive receives a mode conversion instruction sent by a user based on an SSD management control program, it stops read / write operations on the solid-state drive. It should be noted that the mode conversion instruction includes the target mode to which the solid-state drive is to be converted. For example, if the current mode is non-volatile memory extension mode (NVMe mode) and the target mode is flexible data location mode (FDP mode), the mode conversion instruction includes the FDP mode. The solid-state drive in the NVMe mode described above may also be referred to as a standard drive.

[0007] S204: Generate mode conversion information for the solid-state drive; the mode conversion information includes configuration management information for each storage unit of the solid-state drive in the current mode. Specifically, the SSD management control program obtains the current configuration management status of the solid-state drive, such as partition information, bad block bitmap, and wear status of storage units in each partition. It then generates mode conversion information corresponding to the solid-state drive and stores this mode conversion information in the mode conversion partition of the solid-state drive for persistent storage. It should be noted that a partition in the disclosed embodiment is a logical unit; a partition may correspond to multiple storage units (physical units). A storage unit here may be, for example, a flash memory block, each of which may contain multiple pages.

[0008] S206: Update the driver and firmware corresponding to the solid-state drive to the driver and firmware corresponding to the target mode. Specifically, when the current mode is non-volatile memory extension mode (NVMe mode) and the target mode is flexible data location mode (FDP mode), the NVMe mode firmware corresponding to the NVMe mode is replaced with the FDP firmware corresponding to the FDP mode. When the current mode is non-volatile memory extension mode (NVMe mode) and the target mode is partitioned namespace mode (ZNS mode), the NVMe firmware corresponding to the NVMe mode is replaced with the ZNS firmware corresponding to the ZNS mode, and the NVMe driver corresponding to the NVMe mode is replaced with the ZNS driver corresponding to the ZNS mode.

[0009] S208: Based on the mode conversion information and the original storage data in each storage unit, the media configuration corresponding to the storage unit in the current mode is modified to the media configuration corresponding to the target mode. Specifically, in the disclosed embodiment, after the driver and firmware corresponding to the solid-state drive are converted to the driver and firmware corresponding to the target mode, the original storage data in each storage unit of the converted driver and firmware is moved to the storage partition corresponding to the target mode. Then, based on the mode conversion information, the partition configuration and media management corresponding to the current mode are modified to the partition configuration and media management corresponding to the target mode. For example, independent physical space is allocated based on the task type of each application and the available capacity of the solid-state drive, and supported logical storage space is provided externally. The solid-state drive's read and write operations are then resumed, and data storage services are provided externally in the current mode. In an embodiment of the present disclosure, a method is provided for stopping read / write operations of a solid-state drive (SSD) based on a received mode conversion instruction; the mode conversion instruction includes a target mode; generating mode conversion information for the SSD; the mode conversion information includes configuration management information for each storage unit of the SSD in the current mode; updating a driver and firmware program corresponding to the SSD to a driver and firmware program corresponding to the target mode; and modifying a media configuration corresponding to a storage unit in the current mode to a media configuration corresponding to the target mode based on the mode conversion information and original storage data in each storage unit. Compared to the prior art mode conversion of SSDs, the present disclosure can achieve type conversion of the SSD without formatting data after reading it out. This not only reduces data movement operations and improves the efficiency of SSD type conversion, but also enhances the performance and flexibility of SSD management and facilitates the scheduling and management of large-scale storage resources. In one or more embodiments, the mode conversion information includes at least one of the following: a flash translation layer mapping table, used to indicate the mapping relationship between the logical block address and the physical block address in the storage unit of the solid-state drive; a data recovery queue, used to indicate the data recovery priority of each storage unit of the solid-state drive; a bad block bitmap, used to indicate the bad block location in each storage unit of the solid-state drive; wear data, used to mark the number of write / erase times corresponding to each storage unit of the solid-state drive; logical space configuration information, used to configure the number of logical spaces corresponding to the solid-state drive and the capacity corresponding to each logical space; physical space partitioning information, used to configure the flash memory blocks contained in each storage partition in the solid-state drive.Specifically, in the disclosed embodiment, as shown in FIG5 , mode conversion information includes one or more of a flash translation layer mapping table, a data recycling queue, a bad block bitmap, wear data, logical space configuration information, and physical space segmentation information. The flash translation layer (FTL) uses a mapping table, namely, a flash translation layer mapping table, to convert logical addresses to physical addresses. In the physical storage area of ​​a solid-state drive, such as NAND flash memory, each page contains not only a main data area but also an area specifically for storing out-of-band data (OOB). For example, a NAND flash memory page may have 2048 bytes for storing user data and a 64-byte OOB area for storing error correction codes (ECC) and other management information. This layout allows the storage device to perform error checking, correction, and management operations without interfering with the main data. The 00B area can store the physical and logical addresses of flash memory pages. As shown in Figure 5, physical address P1001 of the current page corresponds to logical address L1001, physical address P1002 corresponds to logical address L1002, and physical address P100N corresponds to logical address L100N. The SSD driver can derive the flash translation layer mapping relationship under normal paths. That is, the mapping relationship can be found by following the logical address path to the corresponding physical address. When a bad block appears on the hard drive or the mapping relationship changes, a full scan and rebuild of the SSD can be performed to obtain the flash translation layer mapping relationship corresponding to the abnormal path. The data recycling queue is used to manage data to be deleted or reorganized on the SSD. In SSDs and other flash memory devices, data cannot be simply overwritten; old data must be erased before new data can be written to the same location. This process involves distinguishing between valid data and invalid data (i.e., data that has been deleted or needs to be overwritten) and, when appropriate, clearing invalid data to free up space for new data. Specifically, when a file is deleted or data is overwritten, the data in the associated physical pages or blocks is not immediately removed from the storage medium. Instead, the data is marked invalid, and the logical address map is updated to point to the new data location. Pages or blocks containing invalid data are added to the data recycling queue. This data recycling queue tracks which data blocks are ready for garbage collection. The storage controller periodically performs garbage collection. During this process, the controller checks the recycling queue and selects blocks containing a large amount of invalid data for processing.Valid data is copied to a new location, while old blocks are erased, freeing up space for future use. During the garbage collection process, the storage controller also considers the wear leveling requirements of the storage medium, ensuring that data erase and write operations are evenly distributed across all storage units to extend the service life of the solid-state drive. In one or more embodiments, updating the driver and firmware corresponding to the solid-state drive with the driver and firmware corresponding to the target mode includes: obtaining pre-stored driver and firmware corresponding to the target mode; and replacing the driver and firmware corresponding to the current mode of the solid-state drive with the driver and firmware corresponding to the target mode. Specifically, in the disclosed embodiments, the driver and firmware corresponding to each mode can be pre-stored in a fixed partition of the current solid-state drive, or in a database of another storage server. When the driver and firmware of the solid-state drive need to be updated, the pre-stored driver and firmware corresponding to the target mode are obtained from the fixed partition of the current solid-state drive or the database of the storage server, and the driver and firmware corresponding to the current mode of the solid-state drive are replaced with the driver and firmware corresponding to the target mode. As shown in Figure 3 , when the current mode is Non-Volatile Memory Express (NVMe) mode and the target mode is Zoned Name Space (ZNS) mode, the SSD driver corresponding to NVMe mode is replaced with a ZNS driver, and the SSD firmware corresponding to NVMe mode is replaced with a ZNS firmware. As shown in Figure 6 , when the current mode is ZNS mode and the target mode is NVMe mode, the SSD driver corresponding to ZNS mode is replaced with an NVMe driver, and the SSD firmware corresponding to ZNS mode is replaced with an NVMe firmware. Because the drivers for Flexible Data Location (FDP) and Non-Volatile Memory Express (NVMe) modes are the same, program updates between FDP and standard drive modes only require updating the firmware. As shown in Figure 8 , when the current mode is FDP and the target mode is ZNS, the SSD driver corresponding to FDP mode is replaced with a ZNS driver, and the SSD firmware corresponding to FDP mode is replaced with a ZNS firmware.As shown in Figure 10, when the current mode is ZNS mode and the target mode is FDP mode, the driver corresponding to the SSD's ZNS mode is replaced with a driver corresponding to the FDP mode, and the firmware corresponding to the SSD's ZNS mode is replaced with a firmware corresponding to the FDP mode. In one or more embodiments, after generating the SSD's mode conversion information, the method further includes: writing the mode conversion information to a target storage unit of the SSD; and upon determining that the SSD has been updated to the driver and firmware corresponding to the target mode, reading the mode conversion information from the target storage unit. Specifically, in the disclosed embodiment, after generating the SSD's mode conversion information, the SSD's firmware writes the mode conversion information to the SSD's target storage unit (conversion information area), which includes one or more storage blocks. When the SSD has been updated to the driver and firmware corresponding to the target mode, the method reads the mode conversion information from the target storage unit and then reconstructs the hard disk storage environment corresponding to the target mode based on the mode conversion information. In one or more embodiments, the method of modifying the media configuration corresponding to the storage unit of the current mode to the media configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit includes: modifying the original partition configuration corresponding to the storage unit of the current mode to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit, wherein the target storage partition in the target partition configuration is configured to store the original storage data. Specifically, in the embodiments of the present disclosure, for example, based on the mode conversion information and the physical partitioning rules corresponding to the target mode, the partitions of the solid-state drive are adjusted, the original partition configuration corresponding to the storage unit of the current mode is modified to the target partition configuration corresponding to the target mode, and the original storage data is stored in the target storage partition corresponding to the target mode.In one or more embodiments, when the current mode is the non-volatile memory expansion mode and the target mode is the flexible data location mode, the original partition configuration corresponding to the storage unit of the current mode is modified to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit, including: migrating the original storage data from the original storage unit to the target storage partition based on the physical partition rule corresponding to the flexible data location mode in the mode conversion information, and erasing the data in the original storage unit; dividing the storage space of the solid-state drive into multiple storage partitions according to the logical space configuration information, physical space segmentation information and available capacity of the storage unit of the solid-state drive in the mode conversion information; each storage partition is configured to store data of an application type respectively, and the data of the application type corresponding to each storage partition is different; and updating the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions. Specifically, in the disclosed embodiments, during the switch from non-volatile memory expansion mode (standard disk mode) to FDP mode, since the SSD is not partitioned in standard disk mode, all currently written data on the SSD is treated as one of the multiple logical storage spaces in FDP mode. Currently written data that was not previously placed according to the physical partitioning rules in FDP mode is migrated to a designated partition, and the flash memory blocks corresponding to the written data before the migration are erased. Based on the task requirements of each application, the logical space configuration information and physical space partitioning information in the mode conversion information, and the available capacity of the SSD's storage units, the SSD's storage space is divided into multiple storage partitions. In FDP mode, each storage partition is configured to store data of a different application type, and each storage partition corresponds to a different application type, i.e., different storage partitions correspond to different data hotness and coldness. Then, based on the storage partition configuration information, the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions is updated. In one or more embodiments, when the current mode is the flexible data location mode and the target mode is the non-volatile memory expansion mode, the original partition configuration corresponding to the storage unit of the current mode is modified to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit, including: merging multiple storage partitions in the solid-state drive into one storage partition based on the physical partition rules corresponding to the non-volatile memory expansion mode in the mode conversion information, updating the logical address corresponding to the original storage data based on the partition information of the merged storage partition; and updating the mapping relationship between the physical address and the logical address of each storage unit in the merged storage partition.Specifically, in the disclosed embodiment, during the switch from FDP mode to standard disk mode, since the SSD is not partitioned in standard disk mode, it can be considered to have only one partition. The capacity of this partition can then be determined as a partition of the SSD in FDP mode. Based on the physical partitioning rules corresponding to the standard disk mode in the mode conversion information, multiple storage partitions in the SSD are merged into one storage partition. Data in the merged storage partition and subsequently written data are all configured to be stored indiscriminately, without distinguishing between hot and cold data. In one or more embodiments, when the current mode is the non-volatile memory extension mode and the target mode is the partition namespace mode, the original partition configuration corresponding to the storage unit of the current mode is modified to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit, including: migrating the original storage data from the original storage unit to the target storage partition based on the physical partition rule corresponding to the partition namespace mode in the mode conversion information, and erasing the data in the original storage unit; dividing the storage space of the solid-state hard disk into multiple storage partitions according to the task configuration information in the mode conversion information and the available capacity of the storage unit of the solid-state hard disk; each storage partition corresponds to a preset number of flash memory pages; and updating the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage areas. Specifically, in the disclosed embodiment, as shown in FIG3 , during the switch from standard disk mode to zoned namespace (ZNS) mode, the ZNS firmware retrieves mode conversion information from the conversion information area (target storage partition). Based on the physical partitioning rules corresponding to the ZNS mode in the mode conversion information, the ZNS firmware migrates the original stored data from the original storage unit to the target storage partition. Data recycling is then performed to erase the data in the original storage unit. Then, based on the task configuration information in the mode conversion information and the available capacity of the SSD's storage units, the SSD's storage space is divided into multiple storage partitions; each storage partition corresponds to a preset number of flash memory pages. The mapping relationship between the physical address and logical address of each storage unit in the multiple storage areas is updated. As shown in FIG4 , data written to the data space in standard disk mode is migrated to the Z0 partition of the ZNS mode storage partition. The remaining storage space with unwritten data is divided into k storage partitions, namely, Z1, Z2, through Zk.In one or more embodiments, when the current mode is partition namespace mode and the target mode is non-volatile memory expansion mode, modifying the original partition configuration corresponding to the storage unit in the current mode to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit includes: merging multiple storage partitions in the solid-state drive into one storage partition based on the physical partition rules corresponding to the non-volatile memory expansion mode in the mode conversion information; updating the logical addresses corresponding to the original storage data based on the partition information of the merged storage partition; and updating the mapping relationship between the physical addresses and logical addresses of each storage unit in the merged storage partition. Specifically, in the disclosed embodiment, as shown in FIG6 , during the switching process from ZNS mode to standard drive mode, the standard drive firmware obtains the mode conversion information from the conversion information area (target storage partition); merges the multiple storage partitions in the solid-state drive into one storage partition based on the physical partition rules corresponding to the non-volatile memory expansion mode in the mode conversion information; and updates the logical addresses corresponding to the original storage data based on the partition information of the merged storage partition. As shown in Figure 7, partition Z0 in the ZNS mode storage partition is a storage partition with written data. The data in partition Z0 is migrated to a preset storage unit in the standard disk mode, and then the data is merged with the other storage spaces with unwritten data, which are divided into k storage partitions, such as Z1, Z2, through Zk, into one storage partition. In one or more embodiments, when the current mode is the flexible data location mode and the target mode is the partition namespace mode, modifying the original partition configuration corresponding to the storage unit in the current mode to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit includes: retaining the original partition corresponding to the original storage data based on the physical partition rules corresponding to the partition namespace mode in the mode conversion information, and dividing the storage units in the solid-state drive, excluding the original partition, into multiple storage partitions; configuring each storage partition to write data sequentially according to the order of the storage units; and updating the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions.Specifically, in an embodiment of the present disclosure, as shown in FIG8 , during a switch from Flexible Data Location (FDP) mode to ZNS mode, the ZNS driver and ZNS firmware retrieve mode conversion information from the conversion information area (target storage partition). Based on the physical partitioning rules corresponding to the ZNS mode in the mode conversion information, the ZNS driver and ZNS firmware retain the original partition corresponding to the original stored data and divide the storage units of the solid-state drive, excluding the original partition, into multiple storage partitions. Each of the storage partitions is configured to write data sequentially in the order of the storage units. As shown in FIG9 , the storage partitions of the solid-state drive in FDP mode with written data include i storage partitions, RO1 to ROi. Based on the physical partitioning rules corresponding to the ZNS mode, the i storage partitions, RO1 to ROi, are mapped to i storage partitions, Z01 to ZOi, in the ZNS mode. The storage area of ​​the solid-state drive in FDP mode with unwritten data is divided into k storage partitions, Z1 to Zk. Finally, the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions is updated to complete the conversion of the solid-state drive mode. In one or more embodiments, when the current mode is the partition namespace mode and the target mode is the flexible data location mode, modifying the original partition configuration corresponding to the storage unit in the current mode to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit includes: retaining the original partition corresponding to the original storage data based on the physical partition rule corresponding to the flexible data location mode in the mode conversion information, and dividing the storage units in the solid-state drive other than the original partition into multiple storage partitions; the storage partitions are configured to respectively store data of a different application type, and the data of the application type corresponding to each storage partition is different; and updating the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions.Specifically, in an embodiment of the present disclosure, as shown in FIG10 , during a switch from ZNS mode to FDP mode, the FDP firmware obtains mode conversion information from the conversion information area (target storage partition). Then, based on the physical partitioning rules corresponding to the FDP mode in the mode conversion information, the FDP firmware retains the original partition corresponding to the original stored data and divides the storage units of the SSD, excluding the original partition, into multiple storage partitions. The storage partitions are configured to store data of a different application type, and each storage partition corresponds to data of a different application type. As shown in FIG11 , the storage partitions of the SSD in ZNS mode with written data include i storage partitions, Z01 to ZOi. The FDP firmware, based on the physical partitioning rules corresponding to the FDP mode, maps the i storage partitions, Z01 to ZOi, to i storage partitions, R01 to ROi, in the FDP mode. The FDP firmware also divides the unwritten storage area of ​​the SSD in ZNS mode into k storage partitions, R1 to Rk. Finally, the mapping between the physical address and logical address of each storage unit in the multiple storage partitions is updated to complete the SSD mode switch. Based on the above embodiment, in an application embodiment, as shown in FIG12 , the hard disk management method further includes:

[0010] 51 , stop the read and write (10) operations of the solid state drive.

[0011] 52. Generate mode conversion information and persist the mode conversion information.

[0012] 53, update the firmware, driver and software interface corresponding to the solid state drive.

[0013] 54. Read the above mode conversion information and rebuild the production environment (media configuration) corresponding to the solid state drive.

[0014] 55, restore the read and write (10) operation of the solid-state drive. The embodiment of the present disclosure has the following beneficial technical effects: it can enable the same solid-state drive component to adjust the application mode according to the usage scenario and its own status, thereby improving the resource reuse rate, avoiding resource deployment islands, and reducing data migration. Based on the information required for the operation of each mode of the solid-state drive, the conversion information required for mode switching and the generation and storage method of the conversion information are cleverly designed. By refreshing the firmware and updating the driver, a storage mechanism under mode switching is constructed; and by reading the conversion information, the working environment of the medium and data is rebuilt; and the breakpoint status of data reading and writing can be picked up to ensure that the solid-state drive can provide storage services to various applications in the new mode. The solid-state drive can be quickly integrated into the storage cluster, improving the resource scheduling capability of the cluster. It should be noted that for the above-mentioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should know that the present disclosure is not limited by the order of the actions described, because according to the present disclosure, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are preferred embodiments, and the actions and modules involved are not necessarily required by this disclosure. According to another aspect of the embodiments of the present disclosure, a solid-state drive management device for implementing the above-mentioned solid-state drive management method is also provided. As shown in FIG13 , the device includes: a stopping unit 1302, configured to stop read / write operations on the solid-state drive based on a received mode conversion instruction; the mode conversion instruction includes a target mode; a generating unit 1304, configured to generate mode conversion information for the solid-state drive; the mode conversion information includes configuration management information for each storage unit of the solid-state drive in the current mode; an updating unit 1306, configured to update the driver and firmware corresponding to the solid-state drive to the driver and firmware corresponding to the target mode; and a modifying unit 1308, configured to modify the media configuration corresponding to the storage unit in the current mode to the media configuration corresponding to the target mode based on the mode conversion information and the original storage data in the storage unit.In an embodiment of the present disclosure, a method is provided for stopping read / write operations of a solid-state drive (SSD) based on a received mode conversion instruction; the mode conversion instruction includes a target mode; generating mode conversion information for the SSD; the mode conversion information includes configuration management information for each storage unit of the SSD in the current mode; updating a driver and firmware program corresponding to the SSD to a driver and firmware program corresponding to the target mode; and modifying a media configuration corresponding to a storage unit in the current mode to a media configuration corresponding to the target mode based on the mode conversion information and original storage data in each storage unit. Compared to the prior art mode conversion of SSDs, the present disclosure can achieve type conversion of the SSD without formatting data after reading it out. This not only reduces data movement operations and improves the efficiency of SSD type conversion, but also enhances the performance and flexibility of SSD management and facilitates the scheduling and management of large-scale storage resources. In one or more embodiments, the mode conversion information includes at least one of the following: a flash translation layer mapping table indicating the mapping relationship between logical block addresses and physical block addresses in the storage units of the solid-state drive; a data recycling queue indicating the data recycling priority of each storage unit of the solid-state drive; a bad block bitmap indicating the location of bad blocks in each storage unit of the solid-state drive; wear data marking the number of write / erase cycles corresponding to each storage unit of the solid-state drive; logical space configuration information configuring the number of logical spaces corresponding to the solid-state drive and the capacity of each logical space; and physical space partitioning information configuring the flash memory blocks included in each storage partition of the solid-state drive. In one or more embodiments, the update unit 1306 includes: an acquisition module configured to acquire pre-stored driver and firmware programs corresponding to the target mode; and a replacement module configured to replace the driver and firmware programs corresponding to the current mode of the solid-state drive with the driver and firmware programs corresponding to the target mode. In one or more embodiments, the solid-state drive management device further includes: a writing module configured to write the mode conversion information into a target storage unit of the solid-state drive; a reading module configured to determine that the solid-state drive has been updated to a driver and firmware program corresponding to the target mode, and read the mode conversion information from the target storage unit.In one or more embodiments, the modification unit 1308 includes: a modification module, configured to modify the original partition configuration corresponding to the storage unit in the current mode to a target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit, wherein the target storage partition in the target partition configuration is configured to store the original storage data. In one or more embodiments, when the current mode is the non-volatile memory expansion mode and the target mode is the flexible data location mode, the modification module includes: a first management subunit, which is configured to migrate the original storage data from the original storage unit to the target storage partition and erase the data in the original storage unit based on the physical partitioning rule corresponding to the flexible data location mode in the mode conversion information; a first partitioning subunit, which is configured to divide the storage space of the solid-state hard disk into multiple storage partitions based on the logical space configuration information, the physical space segmentation information and the available capacity of the storage unit of the solid-state hard disk in the mode conversion information; each storage partition is configured to store data of an application type respectively, and the data of the application type corresponding to each storage partition is different; a first update subunit, which is configured to update the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions. In one or more embodiments, when the current mode is the flexible data location mode and the target mode is the non-volatile memory expansion mode, the modification module includes: a first merging sub-unit, configured to merge multiple storage partitions in the solid-state drive into one storage partition based on the physical partition rule corresponding to the non-volatile memory expansion mode in the mode conversion information, and update the logical address corresponding to the original storage data based on the partition information of the merged storage partition; and a second updating sub-unit, configured to update the mapping relationship between the physical address and the logical address of each storage unit in the merged storage partition. In one or more embodiments, when the current mode is the non-volatile memory extension mode and the target mode is the partition namespace mode, the modification module includes: a second management subunit, which is configured to migrate the original storage data from the original storage unit to the target storage partition and erase the data in the original storage unit based on the physical partitioning rules corresponding to the partition namespace mode in the mode conversion information; a second partitioning subunit, which is configured to divide the storage space of the solid-state hard disk into multiple storage partitions based on the task configuration information in the mode conversion information and the available capacity of the storage unit of the solid-state hard disk; each storage partition corresponds to a preset number of flash memory pages; and a third update subunit, which is configured to update the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage areas.In one or more embodiments, when the current mode is partition namespace mode and the target mode is non-volatile memory expansion mode, the modification module includes: a second merging sub-unit configured to merge multiple storage partitions in the solid-state drive into one storage partition based on the physical partitioning rules corresponding to the non-volatile memory expansion mode in the mode conversion information, and update the logical address corresponding to the original storage data based on the partition information of the merged storage partition; a fourth updating sub-unit configured to update the mapping relationship between the physical address and the logical address of each storage unit in the merged storage partition. In one or more embodiments, when the current mode is flexible data location mode and the target mode is partition namespace mode, the modification module includes: a third partitioning sub-unit configured to retain the original partition corresponding to the original storage data and partition the storage units in the solid-state drive, excluding the original partition, into multiple storage partitions based on the physical partitioning rules corresponding to the partition namespace mode in the mode conversion information; each storage partition is configured to write data sequentially in the order of the storage units; and a fifth updating sub-unit configured to update the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions. In one or more embodiments, when the current mode is partition namespace mode and the target mode is flexible data location mode, the modification module includes: a fourth partitioning subunit configured to, based on the physical partitioning rules corresponding to the flexible data location mode in the mode conversion information, retain the original partition corresponding to the original stored data and partition the storage units in the solid-state drive, excluding the original partition, into multiple storage partitions; the storage partitions are configured to respectively store data of a specific application type, with each storage partition corresponding to a different application type; and a sixth updating subunit configured to update the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions. According to another aspect of the embodiments of the present disclosure, an electronic device for implementing the above-mentioned solid-state drive management method is also provided. The electronic device may be the terminal device or server shown in FIG. 1 . This embodiment uses the electronic device as a server as an example. As shown in FIG. 14 , the electronic device includes a memory 1402 and a processor 1404. The memory 1402 stores a computer program, and the processor 1404 is configured to execute the steps of any of the above-mentioned method embodiments using the computer program. Optionally, in this embodiment, the electronic device may be at least one of a plurality of network devices in a computer network. Optionally, in this embodiment, the processor may be configured to execute the following steps through a computer program:

[0015] 51. Stop the read / write operation of the solid state drive based on a received mode conversion instruction; the mode conversion instruction includes a target mode;

[0016] 52, generating mode conversion information of the solid-state drive; the mode conversion information includes configuration management information of each storage unit of the solid-state drive in the current mode;

[0017] 53. Update the driver and firmware corresponding to the solid state drive to the driver and firmware corresponding to the target mode;

[0018] 54. Based on the mode conversion information and the original storage data in each storage unit, the media configuration corresponding to the storage unit in the current mode is modified to the media configuration corresponding to the target mode. Memory 1402 may be used to store software programs and modules, such as program instructions / modules corresponding to the solid-state drive management method and apparatus in the embodiments of the present disclosure. Processor 1404 executes the software programs and modules stored in memory 1402 to execute various functional applications and data processing, thereby implementing the solid-state drive management method. Memory 1402 may include high-speed random access memory (RAM) or non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, memory 1402 may further include memory remotely located from processor 1404, and such remote memory may be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof. Memory 1402 may specifically, but is not limited to, be used to store solid-state drive partition information and the mapping between logical addresses and physical addresses. As an example, as shown in FIG14 , the memory 1402 may include, but is not limited to, the stop unit 1302, generate unit 1304, update unit 1306, and modify unit 1308 of the solid-state drive management device. Furthermore, it may also include, but is not limited to, other modules and units of the solid-state drive management device, which are not described in detail in this example. Optionally, the transmission device 1406 is configured to receive or transmit data via a network. Specific examples of such networks include wired networks and wireless networks. In one example, the transmission device 1406 includes a network interface controller (NIC), which can be connected to other network devices and routers via a network cable to communicate with the Internet or a local area network. In one example, the transmission device 1406 is a radio frequency (RF) module configured to communicate wirelessly with the Internet. Furthermore, the electronic device also includes a connection bus 1408 for connecting the various modules and components of the electronic device. In other embodiments, the electronic device may be a node in a distributed system, wherein the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting the multiple nodes through network communication.Nodes can form a peer-to-peer (P2P) network. Any computing device, such as a server or terminal, can become a node in the blockchain system by joining the P2P network. In one or more embodiments, the present disclosure further provides a computer program product or computer program, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the aforementioned solid-state drive management method. The computer program is configured to execute the steps of any of the aforementioned method embodiments when executed. Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program configured to perform the following steps: 51. Stopping read / write operations on the solid-state drive based on a received mode conversion instruction; the mode conversion instruction includes a target mode.

[0019] 52. Generate mode conversion information of the solid state drive; the mode conversion information includes configuration management information of each storage unit of the solid state drive in the current mode;

[0020] 53. Update the driver and firmware corresponding to the solid state drive to the driver and firmware corresponding to the target mode;

[0021] 54. Based on the mode conversion information and the original storage data in each storage unit, modify the media configuration corresponding to the storage unit in the current mode to the media configuration corresponding to the target mode. Optionally, in this embodiment, those skilled in the art will appreciate that all or part of the steps in the various methods of the above embodiments can be completed by a program instructing hardware associated with the terminal device. The program can be stored in a computer-readable storage medium, which may include a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. The serial numbers of the above embodiments of the present disclosure are for descriptive purposes only and do not represent the merits of the embodiments. If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the above-mentioned computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure, or the portion that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes instructions for causing one or more computer devices (such as personal computers, servers, or network devices) to execute all or part of the steps of the various embodiments of the present disclosure. In the above-described embodiments of the present disclosure, the descriptions of each embodiment are given with emphasis. For portions not described in detail in a particular embodiment, reference can be made to the relevant descriptions of other embodiments. In the several embodiments provided in the present disclosure, it should be understood that the disclosed client can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is merely a logical functional division. In actual implementation, other divisions may be employed, such as combining or integrating multiple units or components into another system, or omitting or disabling certain features. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through interfaces, or indirect coupling or communication connection between units or modules, which may be electrical or otherwise. Units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the objectives of the present embodiment as needed. Furthermore, the functional units in various embodiments of the present disclosure may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit.The above-mentioned integrated units can be implemented in either hardware or software functional units. The above are merely preferred embodiments of the present disclosure. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present disclosure, and such improvements and modifications should be considered within the scope of protection of the present disclosure. The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, storage, and display, etc.) involved in the present disclosure are all authorized by the user or fully authorized by all parties. The collection, use, and processing of such data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation portals are provided for the user to choose to authorize or reject.

Claims

Claims 1. A method for managing a solid-state drive, the method comprising: Stop the read / write operation of the solid-state drive based on the received mode conversion instruction; the mode conversion instruction includes a target mode; generate mode conversion information of the solid-state drive; the mode conversion information includes configuration management information of each storage unit of the solid-state drive in the current mode; update the driver and firmware program corresponding to the solid-state drive to the driver and firmware program corresponding to the target mode; based on the mode conversion information and the original storage data in the each storage unit, modify the media configuration corresponding to the storage unit of the current mode to the media configuration corresponding to the target mode.

2. The method according to claim 1, wherein: The mode conversion information includes at least one of the following: a flash translation layer mapping table, used to indicate the mapping relationship between the logical block address and the physical block address in the storage unit of the solid-state drive; a data recovery queue, used to indicate the data recovery priority of each storage unit of the solid-state drive; a bad block bitmap, used to indicate the bad block location in each storage unit of the solid-state drive; wear data, used to mark the number of write / erase times corresponding to each storage unit of the solid-state drive; logical space configuration information, used to configure the number of logical spaces corresponding to the solid-state drive and the capacity corresponding to each logical space; physical space partitioning information, used to configure the flash memory blocks contained in each storage partition in the solid-state drive.

3. The method according to claim 1 or 2, wherein: Updating the driver and firmware programs corresponding to the solid-state drive to the driver and firmware programs corresponding to the target mode includes: obtaining pre-stored driver and firmware programs corresponding to the target mode; and replacing the driver and firmware programs corresponding to the current mode of the solid-state drive with the driver and firmware programs corresponding to the target mode.

4. The method according to claim 1 or 2, wherein After generating the mode conversion information of the solid-state drive, the method further includes: writing the mode conversion information into a target storage unit of the solid-state drive; determining that the solid-state drive has been updated to a driver and firmware program corresponding to the target mode, and reading the mode conversion information from the target storage unit.

5. The method according to claim 1 or 2, wherein: The method of modifying the medium configuration corresponding to the storage unit of the current mode to the medium configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit includes: modifying the medium configuration corresponding to the storage unit of the current mode to the medium configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit The original partition configuration corresponding to the target mode is modified to a target partition configuration corresponding to the target mode, in which the target storage partition is configured to store the original storage data.

6. The method according to claim 5, wherein: In the case that the current mode is the non-volatile memory expansion mode and the target mode is the flexible data location mode, the original partition configuration corresponding to the storage unit of the current mode is modified to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit, including: migrating the original storage data from the original storage unit to the target storage partition based on the physical partition rule corresponding to the flexible data location mode in the mode conversion information, and erasing the data in the original storage unit; dividing the storage space of the solid-state hard disk into multiple storage partitions according to the logical space configuration information, the physical space segmentation information and the available capacity of the storage unit of the solid-state hard disk in the mode conversion information; each storage partition is configured to store data of an application type respectively, and the data of the application type corresponding to each storage partition is different; and updating the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions.

7. The method according to claim 5, wherein: In the case where the current mode is the flexible data location mode and the target mode is the non-volatile memory expansion mode, the original partition configuration corresponding to the storage unit of the current mode is modified to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit, including: merging multiple storage partitions in the solid-state drive into one storage partition based on the physical partition rule corresponding to the non-volatile memory expansion mode in the mode conversion information, updating the logical address corresponding to the original storage data based on the partition information of the merged storage partition; and updating the mapping relationship between the physical address and the logical address of each storage unit in the merged storage partition.

8. The method according to claim 5, wherein: In the case where the current mode is the non-volatile memory extension mode and the target mode is the partition namespace mode, the original partition configuration corresponding to the storage unit of the current mode is modified to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit, including: migrating the original storage data from the original storage unit to the target storage partition based on the physical partition rule corresponding to the partition namespace mode in the mode conversion information, and erasing the data in the original storage unit; dividing the storage space of the solid-state hard disk into multiple storage partitions according to the task configuration information in the mode conversion information and the available capacity of the storage unit of the solid-state hard disk; each storage partition corresponds to a preset number of flash memory pages; and updating the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage areas.

9. The method according to claim 5, wherein: In a case where the current mode is the partition namespace mode and the target mode is the non-volatile memory extension mode, the modifying, based on the mode conversion information and the original storage data in each storage unit, the original partition configuration corresponding to the storage unit in the current mode to the target partition configuration corresponding to the target mode includes: modifying the original partition configuration corresponding to the storage unit in the current mode to the target partition configuration corresponding to the target mode based on the physical partition rule corresponding to the non-volatile memory extension mode in the mode conversion information; 19. Merge multiple storage partitions in the hard disk into one storage partition, update the logical address corresponding to the original storage data based on the partition information of the merged storage partition; and update the mapping relationship between the physical address and the logical address of each storage unit in the merged storage partition.

10. The method according to claim 5, wherein: In the case where the current mode is the flexible data location mode and the target mode is the partition namespace mode, the original partition configuration corresponding to the storage unit of the current mode is modified to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit, including: retaining the original partition corresponding to the original storage data based on the physical partition rule corresponding to the partition namespace mode in the mode conversion information, dividing the storage units in the solid-state drive except the original partition into multiple storage partitions; each of the storage partitions is configured to write data in sequence according to the order of the storage units; and updating the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions.

11. The method according to claim 5, wherein: In the case that the current mode is the partition namespace mode and the target mode is the flexible data location mode, the original partition configuration corresponding to the storage unit of the current mode is modified to the target partition configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit, including: retaining the original partition corresponding to the original storage data based on the physical partition rule corresponding to the flexible data location mode in the mode conversion information, dividing the storage units in the solid-state drive except the original partition into multiple storage partitions; the storage partitions are configured to respectively store data of an application type, and the data of the application type corresponding to each storage partition is different; and updating the mapping relationship between the physical address and the logical address of each storage unit in the multiple storage partitions.

12. A solid state drive management device, the device comprising: a stop unit configured to stop the read / write operation of the solid state drive based on the received mode conversion instruction; The mode conversion instruction includes a target mode; a generating unit configured to generate mode conversion information of the solid-state drive; the mode conversion information includes configuration management information of each storage unit of the solid-state drive in a current mode; an updating unit configured to update a driver and firmware program corresponding to the solid-state drive to a driver and firmware program corresponding to the target mode; The modification unit is configured to modify the medium configuration corresponding to the storage unit of the current mode to the medium configuration corresponding to the target mode based on the mode conversion information and the original storage data in each storage unit.

13. An electronic device comprising 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 according to any one of claims 1 to 11.

14. A computer-readable storage medium having a computer program stored thereon, wherein the program is executed by a processor to implement the method according to any one of claims 1 to 11.

Images