Technical information

HGST Ultrastar C15K600 Hard Disk Drive Specification
292
18.60
WRITE LONG (10) (3F)
Table 268 WRITE LONG (3F)
Byte
Bit
7
6
5
4
3
2
1
0
0
Command Code = 3Fh
1
COR_DIS WR_UNCOR PBLOCK=0
Reserved = 0 Obsolete
2-5
(MSB)
Logical Block Address
(LSB)
6
Reserved = 0
7-8
(MSB)
Byte Transfer Length
(LSB)
9
VU = 0
Reserved = 0
FLAG
LINK
The WRITE LONG command requests the drive to write one block of data transferred from the Initiator.
The transfer data must include
- User Data
- 18 bytes of MEDC data
All WRITE LONG commands will behave as if the WR_UNCOR bit was set with the exception of having the
COR_DIS bit set. COR_DIS bit behavior will take precedence if both WR_UNCOR and COR_DIS bits are set
Parameters are
- COR_DIS - correction disabled, bit 7 in byte 1. When this bit is set to one, the drive will mark the LBA as a
pseudo unrecovered error with correction disabled. A subsequent read to this LBA would:
a) Perform no error recovery on the block; perform no automatic reallocation of the affected logical blocks,
including any automatic reallocation enabled by the Read-Write Error Recovery mode page;
b) Not consider errors on the affected logical blocks to be informational exception conditions as defined in the
Information Exceptions Control mode page (see SPC-4);
c) not log errors on the affected logical blocks in the Error Counter log pages
d) On a read to the LBA, return check condition status with the sense key set to Medium Error and the
additional sense code set to read error marked bad by client.
- WR_UNCOR - write uncorrectable, bit 6 in byte 1. If the COR_DIS bit is not set, the drive will behave in the
following manor regardless of the state of this bit. The drive will create a pseudo unrecovered error with
correction enabled. On following read commands to the LBA, the drive will:
a) use our normal recovery procedures (which will end in a hard error);
b) perform no automatic reallocation of the affected logical blocks, including any automatic reallocation
enabled by the Read-Write Error Recovery mode page;
c) consider errors on the affected logical blocks to be informational exception conditions as defined in the
Information Exceptions Control mode page (see SPC-4);
d) log errors on the affected logical blocks in the Error Counter log pages