# US 2019/0279678 A1 · Magnetic disk device configured to write parity data that is based on data being written to a parity sector when noo error is detected in writing the data being written

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

- Number: US 2019/0279678 A1
- Document ID: US20190279678A1
- Status: Published application
- Kind: A1
- Application number: 16/120,290
- Filed: 2018-09-02
- Published: 2019-09-12
- Earliest claimed: 2018-03-06
- Assignees: Kabushiki Kaisha Toshiba; Toshiba Electronic Devices & Storage Corporation
- Applicants: Kabushiki Kaisha Toshiba; Toshiba Electronic Devices & Storage Corporation
- Inventors: Syosuke MARUYAMA; Kana FURUHASHI; Yosuke KONDO
- Web page: https://patentgrep.com/patent/US20190279678A1

## CPC

- G11B 19/045: {by detecting mistracking}
- G11B 20/1816: {Testing}
- G11B 20/00615: {said format change concerning the logical format of the recording medium, e.g. the structure of sectors, blocks, or frames}
- G11B 20/00927: {wherein said defects or errors are generated on purpose, e.g. intended scratches}
- G11B 20/1833: {by adding special lists or symbols to the coded information (G11B20/1806, G11B20/1866 take precedence)}
- G11B 20/1879: {Direct read-after-write methods}
- G11B 19/04: Arrangements for preventing, inhibiting, or warning against double recording on the same blank or against other recording or reproducing malfunctions
- G11B 19/041: {Detection or prevention of read or write errors}
- G11B 20/0063: {wherein the modification to the logical format mainly concerns management data, e.g., by changing the format of the TOC or the subcode}
- G11B 20/0092: {involving measures which are linked to media defects or read/write errors}
- G11B 2020/1823: {wherein a flag is set when errors are detected or qualified}
- G11B: INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER (recording measured values in a way that does not require playback through a transducer G01D9/00; recording or playback apparatus using mechanically marked tape, e.g. punched paper tape, or using unit records, e.g. punched or magnetically marked cards G06K; transferring data from one type of record carrier to another G06K1/18; circuits for coupling output of reproducer to radio receiver H04B1/20; gramophone pick-ups or like acoustic electromechanical transducers or circuits therefor H04R)

## Abstract

A magnetic disk device includes a plurality of tracks and a controller. The controller receives write data to be written to a first sector of a track, generates a first data string based on the write data and a logical identifier for the first sector, attempts to cause the first data string to be written to the first sector, determines whether a write error has occurred while the first data string is written to the first sector, generates a second data string based at least in part on the first data string, and in response to determining that no write error has occurred while the first data string is written to the first sector, writes a parity data string that is based at least in part on the second data string to a second sector of the track that stores parity data for the track.

## Claims

### Claim 1

A magnetic disk device comprising:
a magnetic disk that includes a plurality of tracks on which data are written to and read from; and
a controller configured to
receive write data to be written to a first sector of a track in the plurality of tracks,
generate a first data string based on the write data and on a logical identifier for the first sector,
attempt to cause the first data string to be written to the first sector,
determine whether a write error has occurred while the first data string is written to the first sector,
generate a second data string based at least in part on the first data string, and
in response to determining that no write error has occurred while the first data string is written to the first sector, cause a parity data string that is based at least in part on the second data string to be written to a second sector of the track that stores parity data for the track.

### Claim 2 (depends on 1)

The magnetic disk device according to claim 1,
wherein the second sector of the track that stores parity data for the track is disposed at an end of the track.

### Claim 3 (depends on 1)

The magnetic disk device according to claim 1,
wherein the controller generates the first data string by performing a mixing function on the write data and the logical identifier for the first sector.

### Claim 4 (depends on 1)

The magnetic disk device according to claim 1, wherein the controller is further configured to:
receive write data to be written to a third sector of the track that is adjacent to the first sector of the track,
generate a third data string based on the write data to be written to the third sector of the track and a logical identifier for the third sector,
attempt to cause the third data string to be written to the third sector, and
determine whether a write error has occurred while the third data string is written to the third sector.

### Claim 5 (depends on 4)

The magnetic disk device according to claim 4, wherein the controller is further configured to:
generate a fourth data string based at least in part on the first data string and the third data string, and
in response to the controller determining that no write error has occurred while the third data string is written to the third sector, cause the parity data string to be written to the second sector of the track that stores parity data for the track, and
the parity data string that is based at least in part on the second data string is also based at least in part on the fourth data string.

### Claim 6 (depends on 4)

The magnetic disk device according to claim 4, wherein the controller is further configured to:
generate the third data string based on the write data to be written to the third sector prior to attempting to cause the third data string to be written to the third sector.

### Claim 7 (depends on 4)

The magnetic disk device according to claim 4, wherein the controller is further configured to: generate the fourth data string based at least in part on the first data string and the third data string by performing an XOR operation on the first data string and the third data string.

### Claim 8 (depends on 4)

The magnetic disk device according to claim 4, wherein the controller is further configured to: generate a fourth data string based at least in part on the first data string and the third data string,
store the fourth data string in a parity data buffer, and
in response to the controller determining that a write error has occurred while the third data string is written to the third sector, output a control signal that prevents the fourth data string from being overwritten until the third data string is written to a non-defective sector of the track.

### Claim 9 (depends on 8)

The magnetic disk device according to claim 8, wherein the controller is further configured to:
in response to the controller determining that the write error has occurred while the third data string is written to the third sector, designate the third sector as a defective sector.

### Claim 10 (depends on 8)

The magnetic disk device according to claim 8, wherein the controller is further configured to:
in response to the controller determining that the write error has occurred while the third data string is written to the third sector, attempt to cause the third data string to be written to a fifth sector of the track, and
determine whether a write error has occurred while the third data string is written to the fifth sector.

### Claim 11 (depends on 10)

The magnetic disk device according to claim 10, wherein the fifth sector of the track is adjacent to the third sector of the track.

### Claim 12 (depends on 10)

The magnetic disk device according to claim 10, wherein the controller is further configured to:
in response to the controller determining that no write error has occurred while the third data string is written to the fifth sector, cause the parity data string to be written to the second sector of the track that stores parity data for the track,
wherein the parity data string that is based at least in part on the second data string is also based at least in part on the fourth data string.

### Claim 13 (depends on 10)

The magnetic disk device according to claim 10, wherein the controller is further configured to:
in response to the controller determining that no write error has occurred while the third data string is written to the fifth sector, output a control signal that allows the fourth data string to be overwritten.

### Claim 14 (depends on 13)

The magnetic disk device according to claim 13, wherein the control signal that allows the fourth data string to be overwritten is transmitted to a read channel of the magnetic disk device.

### Claim 15

A method of writing data in a magnetic disk device which performs writing/reading of data on a magnetic disk, the method comprising:
receiving write data to be written to a first sector of a track in the plurality of tracks;
generating a first data string based on the write data and on a logical identifier for the first sector;
attempting to cause the first data string to be written to the first sector;
determining whether a write error has occurred while the first data string is written to the first sector;
generating a second data string based at least in part on the first data string; and
in response to determining that no write error has occurred while the first data string is written to the first sector, writing a parity data string that is based at least in part on the second data string to a second sector of the track that stores parity data for the track.

### Claim 16 (depends on 15)

The method according to claim 15, wherein
generating the first data string comprises performing a mixing function on the write data and the logical identifier for the first sector.

### Claim 17 (depends on 15)

The method according to claim 15, further comprising:
receiving write data to be written to a third sector of the track that is adjacent to the first sector of the track;
generating a third data string based on the write data to be written to the third sector of the track and a logical identifier for the third sector;
attempting to cause the third data string to be written to the third sector; and
determining whether a write error has occurred while the third data string is written to the third sector.

### Claim 18 (depends on 17)

The method according to claim 17, further comprising:
generating a fourth data string based at least in part on the first data string and the third data string; and
in response to the determining that no write error has occurred while the third data string is written to the third sector, writing the parity data string to the second sector of the track that stores parity data for the track,
wherein the parity data string that is based at least in part on the second data string is also based at least in part on the fourth data string.

### Claim 19 (depends on 17)

The method according to claim 17, further comprising:
generating the third data string based on the write data to be written to the third sector prior to attempting to cause the third data string to be written to the third sector.

### Claim 20 (depends on 17)

The method according to claim 17, further comprising:
generating the fourth data string based at least in part on the first data string and the third data string by performing an XOR operation on the first data string and the third data string.
