# US 2025/0165345 A1 · Method for detecting and recovering an inoperable drive

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0165345 A1
- Document ID: US20250165345A1
- Status: Published application
- Kind: A1
- Application number: 18/511,724
- Filed: 2023-11-16
- Published: 2025-05-22
- Earliest claimed: 2023-11-16
- Assignees: Western Digital Technologies, Inc.
- Applicants: Western Digital Technologies, Inc.
- Inventors: SHIVA KUMAR; RAMANATHAN MUTHIAH
- Web page: https://patentgrep.com/patent/US20250165345A1

## CPC

- G06F 11/1417: {Boot up procedures}
- G06F 11/1433: {during software upgrading}
- G06F 11/1441: {Resetting or repowering}
- G06F 2201/805: Real-time
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A storage device may recover from a firmware failure that places the storage device in an undetectable state. The storage device includes a memory device to store recovery firmware. A storage device controller includes a failure detector module that may identify the firmware failure when a periodic signal is not received by the failure detector module from a firmware thread, when the failure detector module determines that an initialization counter value is greater than an initialization threshold, or when the failure detector module receives a notification of a predefined number of power cycle events occurring with a given time frame. Upon identifying the firmware failure, the failure detector module updates a boot address. A recovery module May obtain recovery firmware from the memory device, based on the boot address, to recover the storage device in a recovery mode, and perform phased recovery actions to restart the storage device.

## Claims

### Claim 1

A storage device recovers from a firmware failure that places the storage device in an undetectable state, the storage device comprises:
a memory device to store recovery firmware; and
a controller including:
a failure detector module that identifies a firmware failure when one of a periodic signal is not received by the failure detector module from a firmware thread, an initialization counter value is greater than an initialization threshold, and a notification is received of a predefined number of power cycle events occurring with a given time frame; and that updates a boot address, and
a recovery module to obtain recovery firmware from the memory device, based on the boot address, to recover the storage device in a recovery mode and perform phased recovery actions to restart the storage device.

### Claim 2 (depends on 1)

The storage device of claim 1, wherein the failure detector module further comprises a watchdog timer to receive periodic signals from firmware threads, wherein the failure detector module triggers an interrupt signal to the controller to execute a recovery routine when the failure detector module identifies the firmware failure.

### Claim 3 (depends on 1)

The storage device of claim 1, wherein the controller comprises a boot loader to use an updated boot address to locate a light mount of the recovery firmware and to use the light mount of the recovery firmware to restart the storage device in the recovery mode.

### Claim 4 (depends on 1)

The storage device of claim 1, further comprising an initialization firmware to send an update to the failure detector module about a failure during initialization, wherein an event handler in the failure detector module increments the initialization counter when the storage device has been initialized without moving into an operational state.

### Claim 5 (depends on 1)

The storage device of claim 1, wherein the failure detector module records a time between successive host power cycles of the storage device and after a predefined number of successive power cycles of the storage device, the failure detector module determines that a failure has occurred and triggers an interrupt signal to the controller for the controller to execute a recovery routine to perform a controller reset.

### Claim 6 (depends on 1)

The storage device of claim 1, further comprising a real-time clock module to receive the notification for an initialization event from an initialization firmware whenever the storage device boots up.

### Claim 7 (depends on 1)

The storage device of claim 1, wherein in the recovery mode, the controller queries a host to confirm if a power cycle is expected by the host, and if it is, the. storage device switches to a normal initialization firmware and resumes operations, and if it is not, the controller performs the phased recovery actions.

### Claim 8 (depends on 1)

The storage device of claim 1, wherein the phased recovery actions include a first recovery phase wherein the storage device executes a light mount of the recovery firmware and enters a temporary read-only mode to enable a host to back-up data stored on the storage device.

### Claim 9 (depends on 1)

The storage device of claim 1, wherein the phased recovery actions include a second recovery phase wherein the storage device executes a first recovery attempt by exiting a read-only mode to allow read and write operations, wherein if the first recovery attempt fails, the storage device executes a second recovery attempt by sending l logical-to-physical tables to a host, erasing the logical-to-physical tables on the storage device, and retrieving the logical-to-physical tables from the host to allow the read and write operations.

### Claim 10 (depends on 9)

The storage device of claim 9, wherein when at least one of the first recovery attempt and the second recovery attempt fails, the storage device disallows normal host operations, requests the host to perform a field firmware upgrade and boots up in a normal mode.

### Claim 11 (depends on 1)

The storage device of claim 1, wherein when a program-erase-count of the storage device is high, the controller performs a physical erase to refresh meta blocks, wherein the controller executes different light mount firmware options for recovery of the storage device based on an average program-erase-count of the memory device, wherein age and wear out of the memory device determines a recovery mechanism.

### Claim 12 (depends on 1)

The storage device of claim 1, wherein the storage device is a multi-protocol storage device that one of performs recovery in a protocol where failure did not occur and includes different light mount firmware options and performs recovery based on a mode of operation.

### Claim 13

A method in a storage device for recovering from a firmware failure that places the storage device in an undetectable state, the storage device comprises a controller to perform the method comprising:
identifying a firmware failure when one of a periodic signal is not received by a failure detector module from a firmware thread, an initialization counter value is greater than an initialization threshold, and a notification is received of a predefined number of power cycle events occurring with a given time frame;
updating a boot address;
obtaining recovery firmware from a memory device based on an updated boot address;
recovering the storage device in a recovery mode with the recovery firmware; and
performing phased recovery actions to restart the storage device.

### Claim 14 (depends on 13)

The method of claim 13, further comprising sending an update to the failure detector module about a failure during initialization and incrementing the initialization counter when the storage device has been initialized without moving into an operational state.

### Claim 15 (depends on 13)

The method of claim 13, further comprising recording a time between successive host power cycles of the storage device, and after a predefined number of successive power cycles of the storage device, determining that a failure has occurred and triggering an interrupt signal to execute a recovery routine to perform a controller reset.

### Claim 16 (depends on 13)

The method of claim 13, wherein the phased recovery actions comprise a first recovery phase including executing a light mount of the recovery firmware and entering a temporary read-only mode to enable a host to back-up data stored on the storage device.

### Claim 17 (depends on 13)

The method of claim 13, wherein the phased recovery actions comprise a second recovery phase including executing a first recovery attempt by exiting a read-only mode to allow read and write operations, and if the first recovery attempt fails, executing a second recovery attempt by sending logical-to-physical tables to a host, erasing the logical-to-physical tables on the storage device, and retrieving the logical-to-physical tables from the host to allow read and write operations.

### Claim 18 (depends on 13)

The method of claim 13, wherein when a program-erase-count of the storage device is high, the method comprises performing a physical erase to refresh meta blocks and executing different light mount firmware options for recovery of the storage device based on an average program-erase-count of the memory device.

### Claim 19 (depends on 13)

The method of claim 13, wherein the storage device is a multi-protocol storage device, and the method comprises performing one of recovery in a protocol where failure did not occur and based on a mode of operation.

### Claim 20

A method in a storage device for recovering from a firmware failure that places the storage device in an undetectable state, the storage device comprises a controller to perform the method comprising:
identifying a firmware failure when one of a periodic signal is not received by a failure detector module from a firmware thread, an initialization counter value is greater than an initialization threshold, and a notification is received of a predefined number of power cycle events occurring with a given time frame;
updating a boot address;
obtaining recovery firmware from a memory device based on an updated boot address;
recovering the storage device in a recovery mode with the recovery firmware;
executing a light mount of the recovery firmware to restart the storage device and enter a temporary read-only mode to enable a host to back-up data stored on the storage device; and
executing a first recovery attempt by exiting a read-only mode to allow read and write operations, and if the first recovery attempt fails, executing a second recovery attempt by sending logical-to-physical tables to a host, erasing the logical-to-physical tables on the storage device, and retrieving the logical-to-physical tables from the host to allow read and write operations.
