Sandisk Technologies Inc.

Western Digital Technologies, Inc.

Dattatreya B Nayak

Vinod Sasidharan

Ramanathan Muthiah

Rohit Prasad

Arun Kumar Shukla

Noor Mohamed A A

Ganesh Kumar Pathirakani

Nagaraj Dandigenahalli Rudrappa

Akash Dungrani

Karthik N E

Yunas Rashid

Venkatesh Ramadoss

Tarun Nimmagadda

Narendra Bayanaboina

Arun Shukla

Silky Mohanty

A host may not have a large enough internal non-volatile memory to store generated data, such as video. In such situations, the host can store the data in an external data storage device, such as an external solid-state drive (SSD). However, if the storage rate of the external data storage device drops below the rate at which the host is generating and sending the data to the external data storage device, data loss can occur. To help avoid this situation, the host can use a dual-write method in which a portion of the data is both sent to the external data storage device for storage and written in the host's internal non-volatile memory. That way, if the portion of the data sent to the external data storage device is lost, the portion of the data can be resent from the host's internal non-volatile memory.

Host and dual write method for avoiding data loss when writing to an external data storage device

Embodiments described herein provide a device for storing parity information. The device includes a wireless transceiver, a memory, and an electronic processor coupled to the wireless transceiver and the memory. The electronic processor is configured to receive, with the wireless transceiver, the parity information from a data storage device controller, and store the parity information in the memory.

Devices, methods, and computer-readable media to store backed-up parity information

Instead of all the NAND memory having asynchronous independent plane read (AIPR) enabled, a system utilizes a master-SSD to route data to multiple client SSDs via a controller memory buffer (CMB) according to the underlying NAND hardware (HW) of each of the client SSDs. The master-SSD will also analyze the application data retrieval of the logical data that is to be routed. The system comprises SSDs with AIPR NAND circuitry and SSDs with non-AIPR NAND circuitry. The system further comprises the master-SSD that will route data to any of the SSDs in the system based on the data retrieval type (sequential or random). Each of the SSDs can be of a different type beyond the NAND chip, such as HW IPs or specific firmware (FW) that is tuned towards specific data routing and retrieval requirements.

Data routing in networked SSDs

Storage devices may be utilized in external devices that communicate with host computing devices over various communication ports and protocols. Traditionally, storage devices utilize bootloading data, such as boot ROMS, to start normal operations of the device. However, many storage devices are unable to change or update bootloading data once the device has been manufactured or deployed. Thus, methods, systems, and devices described herein decouple the bootloading process from the storage device and load bootloading data from an external device. The bootloading data can be loaded via a wireless communication connection from an external device, where it can be updated as needed. Once loaded, the bootloader can begin the process of loading firmware and starting the normal operation of the drive over regular wired communication ports. When the bootloading data or firmware cannot be loaded externally, traditional booting methods can be used utilizing previously stored copies of the required data.

Decoupled external storage device booting

Embodiments described herein provide a data storage device that backs-up parity information. The data storage device includes a memory and a data storage device controller coupled to the memory and including a storage sub-system and a security sub-system. The storage sub-system includes parity information within a second memory. The data storage device further includes a bus for transferring data between the data storage device controller and an external device in communication with the data storage device controller. The data storage device controller is configured to initiate a parity information back-up request, send, from the second memory of the storage sub-system, the parity information to the security sub-system based on the initiation of the parity information back-up request, and control the security sub-system to transmit the parity information to the external device.

Devices, methods, and computer-readable media to back-up parity information

A data storage device includes interfaces for coupling the data storage device to a host system and a server system. The data storage device also includes a device memory for storing or providing data. The data storage device also includes a controller comprising a storage subsystem and a security subsystem. The storage subsystem is configured to receive a host command, receive a probe request for an exception state, generate and transmit, to the security subsystem, a report for the exception state. In response to receiving an update from the security subsystem, the storage subsystem restarts at least a portion of the controller. The security subsystem is configured to monitor and transmit a probe request to the storage subsystem, transmit the report to the server system, receive the update from the server system, and transmit the update to the storage subsystem. Methods and systems are also disclosed.

Handling data storage device failure using remote system

This disclosure relates to systems, methods, and data storage devices, such as a data storage device comprising a data path and a controller. The data path comprises a data port to transmit data between a host computer system and the data storage device. The data storage device registers with the host computer system as a block data storage device. A non-volatile storage medium stores encrypted user content data. A cryptography engine is connected between the data port and the storage medium and uses cryptographic key data to encrypt and decrypt user content data. The controller is configured to send the encrypted user content data for back-up storage external to the data storage device as encrypted by the cryptographic key data, and communicate with a user device over a communication channel that is different from the data path, to send the cryptographic key data for decryption of the encrypted user content external to the data storage device.

Data storage device backup

A data storage device includes a memory device and a controller coupled to the memory device. The controller is configured to operate under at least a first device protocol and a second device protocol, where the first and second device protocols have different endurance and protection requirements. When data is programmed to the memory device using the first device protocol, but is read from the memory device using the second device protocol, the differing endurance and protection requirements may cause issues in reading the data. In order to alleviate the issues, during idle time of the second device protocol, the controller may program the data using the endurance and protection requirements of the second device protocol to a different portion of the memory device so that the data may be read using either or both device protocols with the appropriate recovery information.

Delayed XOR rebuild with priority in multi-protocol products

A data storage device includes a host interface for coupling the data storage device to a host system. The data storage device also includes a device memory for storing or providing data in response to commands receive from the host system. The data storage device also includes a controller comprising a storage subsystem and a security subsystem. The storage subsystem is configured to receive a host command from the host interface, and process the host command for the device memory. The security subsystem includes a device recovery circuit configured to monitor the storage subsystem for an exception state, and reinitialize pending operations for the storage subsystem after the exception state. Methods and systems are also disclosed.

Exception handling using security subsystem in storage device

Technology is disclosed herein for handling of mixed random read and sequential read command sequences. Plane read commands are formed from one or more sequential read commands. A sequential read command may be split into multiple plane read commands at plane boundaries. The plane read commands are submitted to the respective planes as asynchronous independent plane read commands. Random read commands may be submitted to the planes as asynchronous independent plane read (AIPR) commands on par with the split sequential read commands. Therefore, AIPR may be used for both sequential read commands and random read commands. Submitting a split sequential read command to one or more planes while one or more other planes are performing a random read command can significantly improve performance.

Splitting sequential read commands

The devices, methods, and apparatuses of the present disclosure address a lack of parallelism in a typical approach by eliminating the static mapping of the two or more low-density parity check (LDPC) engines to a plurality of flash controllers. The devices, methods, and apparatuses of the present disclosure include a dynamic LDPC mapping to the plurality of flash controllers.

Data storage device with dynamic mapping of low-density parity check (LDPC) engines

A data storage device and method for host-initiated cached read to recover corrupted data within timeout constraints are provided. In one embodiment, a data storage device is provided comprising a volatile memory, a non-volatile memory, and a controller. The controller is configured to receive a read look-ahead command from a host to perform a read look-ahead of a first logical address; receive a read command from the host to read a second logical address; and execute the read look-ahead command by performing the following as background operations while executing the read command: read data for a location in the non-volatile memory that corresponds to the first logical address; correct an error in the data; and cache the corrected data in the volatile memory. The cached corrected data can be sent back to the host in response to the host requesting a read of the same logical address. Other embodiments are provided.

Growing community of inventors

Udupi, India

Dattatreya B Nayak