SCSI Commands Reference Manual
Parallel SCSI
Fibre Channel (FC)
Serial Attached SCSI (SAS)
Rev. A
SCSI Commands Reference Manual
Parallel SCSI
Fibre Channel (FC)
Serial Attached SCSI (SAS)
Rev. A
©2006, Seagate Technology LLC All rights reserved
Publication number: 100293068, Rev. A
February 2006
Seagate and Seagate Technology are regis tered trademarks of Seagate Technology LLC.
SeaTools, SeaFONE, SeaB OARD, Se aTDD, and the Wave logo are e ither regis tered trademarks or trademarks of Seagate Technology LLC. Other product names are registered trademarks or trademarks of their owners.
Seagate reserves the right to ch ange, witho ut notice, product offerings or spec ifications . No
part of this publication may be reproduc ed in any form w ithout wr itte n per mi ssio n of Seagate
Technology LLC.
Revision status summary sheet
Revision Date Sheets Affected
Rev. A 02/14/06 All.
SCSI Commands Reference Manual, Rev. A iii
iv SCSI Commands Reference Manual, Rev. A
Table of Contents
Table of Contents .............................................................................................................................. v
List of Tables .................................................................................................................................... xi
1.0 Definitions, symbols, abbreviations, keywords, and conventions .............................................. 1
1.1 Definitions .................................................................................................................................... 2
1.2 Symbols and abbreviations ........................................................................................................ 12
1.3 Keywords ................................................................................................................................... 14
1.4 Conventions ............................................................................................................................... 15
2.0 General Concepts ........................................................................................................................... 17
2.1 Command Descriptor Block (CDB) ............................................................................................ 18
2.1.1 CDB usage and structure ............................................................................................... 18
2.1.2 The fixed length CDB formats ......................................................................................... 18
2.1.3 The variable length CDB formats .................................................................................... 22
2.2 Common CDB fields .................................................................................................................. 24
2.2.1 Operation Code .............................................................................................................. 24
2.2.2 Service action ................................................................................................................. 24
2.2.3 Logical block address ..................................................................................................... 24
2.2.4 Transfer length ................................................................................................................ 25
2.2.5 Parameter list length ....................................................................................................... 25
2.2.6 Allocation length ............................................................................................................. 25
2.2.7 Control ............................................................................................................................ 26
2.2.8 Grouping function ........................................................................................................... 27
2.3 Parameter rounding ................................................................................................................... 28
2.4 Sense data ................................................................................................................................. 29
2.4.1 Sense data introduction .................................................................................................. 29
2.4.1.1 Descriptor format sense data ............................................................................. 30
2.4.1.1.1 Descriptor format sense data overview ........................................................ 30
2.4.1.1.2 Information sense data descriptor ................................................................ 32
2.4.1.1.3 Command-specific information sense data descriptor ................................. 33
2.4.1.1.4 Sense key specific sense data descriptor .................................................... 34
2.4.1.1.5 Field replaceable unit sense data descriptor ............................................... 38
2.4.1.1.6 Vendor specific sense data descriptors ....................................................... 38
2.4.1.2 Fixed format sense data .................................................................................... 39
2.4.1.3 Current errors ..................................................................................................... 40
2.4.1.4 Deferred errors ................................................................................................... 40
2.4.1.5 Sense key and sense code definitions ............................................................... 42
2.4.1.6 Additional Sense and Additional Sense Qualifier codes .................................... 43
3.0 Command Reference ...................................................................................................................... 51
3.1 CHANGE DEFINITION command ............................................................................................. 54
3.2 COMPARE command ................................................................................................................ 56
3.3 COPY command ........................................................................................................................ 56
3.4 COPY AND VERIFY command ................................................................................................. 56
3.5 FORMAT UNIT command ......................................................................................................... 57
SCSI Commands Reference Manual, Rev. A v
3.5.1 FORMAT UNIT command overview ................................................................................57
3.5.2 FORMAT UNIT parameter list .........................................................................................60
3.5.2.1 FORMAT UNIT parameter list overview .............................................................60
3.5.3 Parameter list header ......................................................................................................60
3.5.4 Initialization pattern descriptor ........................................................................................64
3.5.5 Address descriptor formats .............................................................................................66
3.5.5.1 Address descriptor formats overview .................................................................66
3.5.5.2 Short block format address descriptor ................................................................67
3.5.5.3 Long block format address descriptor ................................................................67
3.5.5.4 Bytes from index format address descriptor .......................................................68
3.5.5.5 Physical sector format address descriptor ..........................................................69
3.6 INQUIRY command ...................................................................................................................70
3.6.1 INQUIRY command introduction .....................................................................................70
3.6.2 Standard INQUIRY data ..................................................................................................72
3.6.3 SCSI Parallel Interface specific INQUIRY data ...............................................................78
3.6.4 Vital product data ............................................................................................................79
3.7 LOCK-UNLOCK Cache (10) command ......................................................................................80
3.8 LOCK-UNLOCK Cache (16) command ......................................................................................80
3.9 LOG SELECT command ............................................................................................................81
3.10 LOG SENSE command ..............................................................................................................84
3.11 MODE SELECT(6) command ....................................................................................................86
3.12 MODE SELECT(10) command ..................................................................................................88
3.13 MODE SENSE(6) command ......................................................................................................89
3.13.1 MODE SENSE(6) command introduction .......................................................................89
3.13.1.1 Current values ....................................................................................................90
3.13.1.2 Changeable values .............................................................................................91
3.13.1.3 Default values .....................................................................................................91
3.13.1.4 Saved values ......................................................................................................91
3.13.1.5 Initial responses ..................................................................................................91
3.14 MODE SENSE(10) command ....................................................................................................92
3.15 PERSISTENT RESERVE IN command .....................................................................................93
3.15.1 PERSISTENT RESERVE IN command introduction ......................................................93
3.15.2 READ KEYS service action .............................................................................................93
3.15.3 READ RESERVATION service action ............................................................................94
3.15.3.1 READ RESERVATION service action introduction ............................................94
3.15.3.2 PERSISTENT RESERVE IN parameter data for READ RESERVATION ..........94
3.15.3.3 Persistent reservations scope ............................................................................96
3.15.3.4 Persistent reservations type ...............................................................................97
3.15.4 REPORT CAPABILITIES service action .........................................................................97
3.15.5 READ FULL STATUS service action ............................................................................100
3.16 PERSISTENT RESERVE OUT command ...............................................................................103
3.16.1 PERSISTENT RESERVE OUT command introduction ................................................103
3.16.2 PERSISTENT RESERVE OUT service actions ............................................................104
3.16.3 Basic PERSISTENT RESERVE OUT parameter list ....................................................105
3.16.4 PERSISTENT RESERVE OUT command with REGISTER AND MOVE service .........108
3.17 PRE-FETCH (10) command, PRE-FETCH (16) command ......................................................110
3.18 PREVENT ALLOW MEDIUM REMOVAL command ................................................................110
3.19 READ (6) command .................................................................................................................111
3.20 READ (10) command ...............................................................................................................113
3.21 READ (12) command ...............................................................................................................118
3.22 READ (16) command ...............................................................................................................119
3.23 READ (32) command ...............................................................................................................120
3.24 READ BUFFER command .......................................................................................................122
3.24.1 READ BUFFER command introduction ........................................................................122
3.24.1.1 Vendor specific mode (01h) ..............................................................................123
vi SCSI Commands Reference Manual, Rev. A
3.24.1.2 Data mode (02h) .............................................................................................. 123
3.24.1.3 Descriptor mode (03h) ..................................................................................... 123
3.24.1.4 Echo buffer mode (0Ah) ................................................................................... 124
3.24.1.5 Echo buffer descriptor mode (0Bh) .................................................................. 125
3.24.1.6 Enable expander communications protocol and Echo buffer (1Ah) ................. 125
3.25 READ CAPACITY (10) command ............................................................................................126
3.25.1 READ CAPACITY (10) overview .................................................................................. 126
3.25.2 READ CAPACITY (10) parameter data ........................................................................ 127
3.26 READ CAPACITY (16) command ............................................................................................128
3.26.1 READ CAPACITY (16) command overview ................................................................. 128
3.26.2 READ CAPACITY (16) parameter data ........................................................................ 129
3.27 READ DEFECT DATA (10) command ..................................................................................... 130
3.27.1 READ DEFECT DATA (10) command overview .......................................................... 130
3.27.2 READ DEFECT DATA (10) parameter data ................................................................. 131
3.28 READ DEFECT DATA (12) command ..................................................................................... 133
3.29 READ LONG (10) command ................................................................................................... 135
3.30 READ LONG (16) command ................................................................................................... 136
3.31 REASSIGN BLOCKS command .............................................................................................. 137
3.31.1 REASSIGN BLOCKS command overview .................................................................... 137
3.31.2 REASSIGN BLOCKS parameter list ............................................................................. 138
3.32 RECEIVE DIAGNOSTIC RESULTS command ....................................................................... 140
3.33 RELEASE(6) command ........................................................................................................... 143
3.34 RELEASE (10) command ........................................................................................................ 144
3.34.1 RELEASE(10) command introduction .......................................................................... 144
3.34.2 Logical unit release ....................................................................................................... 144
3.34.3 Third-party release ........................................................................................................ 144
3.35 REPORT DEVICE IDENTIFIER command .............................................................................. 146
3.36 REPORT LUNS command ...................................................................................................... 148
3.37 REQUEST SENSE command .................................................................................................151
3.37.1 Sense Key Specific field ............................................................................................... 155
3.38 RESERVE(6) command .......................................................................................................... 158
3.39 RESERVE (10) command ....................................................................................................... 159
3.39.1 RESERVE (10) command introduction ......................................................................... 159
3.39.2 Logical unit reservation ................................................................................................ 159
3.39.3 Third-party reservation .................................................................................................. 160
3.39.4 Superseding reservations ............................................................................................. 160
3.40 REZERO UNIT command ........................................................................................................ 162
3.41 SEEK command ...................................................................................................................... 163
3.42 SEEK EXTENDED command .................................................................................................. 164
3.43 SEND DIAGNOSTIC command ...............................................................................................165
3.44 SET DEVICE IDENTIFIER command ...................................................................................... 168
3.45 START STOP UNIT command ................................................................................................ 170
3.46 SYNCHRONIZE CACHE (10) command ................................................................................. 172
3.47 SYNCHRONIZE CACHE (16) command ................................................................................. 173
3.48 TEST UNIT READY command ................................................................................................ 174
3.49 VERIFY (10) command ............................................................................................................ 175
3.50 VERIFY (12) command ............................................................................................................ 185
3.51 VERIFY (16) command ............................................................................................................ 186
3.52 VERIFY (32) command ............................................................................................................ 187
3.53 WRITE (6) command ............................................................................................................... 189
3.54 WRITE (10) command ............................................................................................................. 190
3.55 WRITE (12) command ............................................................................................................. 194
3.56 WRITE (16) command ............................................................................................................. 195
3.57 WRITE (32) command ............................................................................................................. 196
3.58 WRITE AND VERIFY (10) command ...................................................................................... 198
SCSI Commands Reference Manual, Rev. A vii
3.59 WRITE AND VERIFY (12) command .......................................................................................199
3.60 WRITE AND VERIFY (16) command .......................................................................................200
3.61 WRITE AND VERIFY (32) command .......................................................................................201
3.62 WRITE BUFFER command .....................................................................................................203
3.62.1 WRITE BUFFER command introduction .......................................................................203
3.62.2 Combined header and data mode (00h) .......................................................................204
3.62.3 Vendor specific mode (01h) ..........................................................................................204
3.62.4 Data mode (02h) ...........................................................................................................204
3.62.5 Download microcode mode (04h) .................................................................................205
3.62.6 Download microcode and save mode (05h) ..................................................................205
3.62.7 Download microcode with offsets mode (06h) ..............................................................205
3.62.8 Download microcode with offsets and save mode (07h) ...............................................206
3.62.9 Write data to echo buffer mode (0Ah) ...........................................................................207
3.62.10 Enable expander communications protocol and Echo buffer mode (1Ah) ....................207
3.62.11 Disable expander communications protocol mode (1Bh) ..............................................207
3.62.12 Download application log mode (1Ch) ..........................................................................207
3.63 WRITE LONG (10) command ..................................................................................................211
3.64 WRITE LONG (16) command ..................................................................................................212
3.65 WRITE SAME (10) command ..................................................................................................213
3.66 WRITE SAME (16) command ..................................................................................................215
3.67 WRITE SAME (32) command ..................................................................................................216
4.0 Parameters for all device types ....................................................................................................219
4.1 Diagnostic parameters .............................................................................................................220
4.1.1 Diagnostic page format and page codes for all device types ........................................220
4.1.2 Supported diagnostic pages (00h) ................................................................................221
4.1.3 Translate Address page (40h) .......................................................................................222
4.1.4 SCSI Enclosure Services pages (01h - 2Fh) ................................................................224
4.2 Log parameters ........................................................................................................................225
4.2.1 Log page structure and page codes for all device types ...............................................225
4.2.2 Application Client log page (0Fh) ..................................................................................230
4.2.3 Background Scan Results log page (15h) .....................................................................232
4.2.3.1 Medium Scan Parameter ..................................................................................235
4.2.4 Cache Statistics page (37h) ..........................................................................................237
4.2.5 Error counter log pages (WRITE, READ, and VERIFY, 02h, 03h, and 05h) .................237
4.2.6 Factory Log page (3Eh) ................................................................................................239
4.2.7 Informational Exceptions log page (2Fh) ......................................................................239
4.2.8 Non-Medium Error log page (06h) ................................................................................241
4.2.9 Self-Test Results log page (10h) ...................................................................................242
4.2.10 Start-Stop Cycle Counter log page (0Eh) ......................................................................245
4.2.11 Supported Log Pages log page (00h) ...........................................................................248
4.2.12 Temperature log page (0Dh) .........................................................................................249
4.3 Mode parameters .....................................................................................................................251
4.3.1 Mode parameters overview ...........................................................................................251
4.3.2 Mode parameter list format ...........................................................................................251
4.3.3 Mode parameter header formats ...................................................................................251
4.3.4 Mode parameter block descriptor formats .....................................................................253
4.3.4.1 General block descriptor format .......................................................................253
4.3.5 Mode page and subpage formats and page codes .......................................................254
4.3.6 Mode parameter block descriptors ................................................................................256
4.3.6.1 Mode parameter block descriptors overview ....................................................256
4.3.6.2 Short LBA mode parameter block descriptor ....................................................257
4.3.6.3 Long LBA mode parameter block descriptor ....................................................258
4.3.7 Background Control mode page (1Ch) .........................................................................260
4.3.8 Caching Parameters page (08h) ...................................................................................261
viii SCSI Commands Reference Manual, Rev. A
4.3.9 Control mode page (0Ah) ............................................................................................. 264
4.3.10 Control Extension mode page (0Ah) .............................................................................269
4.3.11 Disconnect-Reconnect mode page (02h) ..................................................................... 270
4.3.11.1 Disconnect-Reconnect mode page for Parallel SCSI ...................................... 270
4.3.11.2 Disconnect-Reconnect mode page for FCP (02h) ........................................... 273
4.3.11.2.1 Overview and format of Disconnect-Reconnect mode page for FCP ........ 273
4.3.11.3 Disconnect-Reconnect mode page for SAS (02h) ........................................... 275
4.3.11.3.1 Disconnect-Reconnect mode page overview ............................................. 275
4.3.12 Format Parameters page (03h) .................................................................................... 278
4.3.13 Informational Exceptions Control mode page (1Ch) ..................................................... 280
4.3.14 Notch page (0Ch) ......................................................................................................... 283
4.3.15 Power Condition mode page (1Ah) ...............................................................................285
4.3.16 Read-Write Error Recovery mode page (01h) .............................................................. 287
4.3.17 Protocol Specific Logical Unit mode page (18h) ........................................................... 293
4.3.17.1 Protocol specific parameters ............................................................................ 293
4.3.17.1.1 Protocol specific parameters introduction .................................................. 293
4.3.17.2 Fibre Channel Logical Unit Control mode page (18h) ...................................... 295
4.3.17.3 SAS Protocol-Specific Logical Unit mode page ............................................... 296
4.3.17.3.1 Protocol-Specific Logical Unit mode page - short format (18h) ................. 296
4.3.18 Protocol Specific Port mode page (19h) ....................................................................... 297
4.3.18.1 Port Control Mode page (19h) for Parallel SCSI .............................................. 298
4.3.18.1.1 Margin control subpage .............................................................................300
4.3.18.1.2 Saved training configuration values subpage ............................................ 302
4.3.18.1.3 Negotiated settings subpage ..................................................................... 304
4.3.18.1.4 Report transfer capabilities subpage ........................................................ 305
4.3.18.2 Port Control Mode page (19h) for Fibre Channel (FC) ..................................... 305
4.3.18.3 Protocol Specific Port Mode page (19h) for Serial Attached SCSI (SAS) ........ 307
4.3.18.3.1 Protocol-specific Port mode page overview ............................................... 307
4.3.18.3.2 Protocol-Specific Port mode page - short format ....................................... 308
4.3.18.3.3 Protocol-Specific Port mode page - Phy Control And Discover subpage (19h) 310
4.3.19 Rigid Drive Geometry Parameters page (04h) ............................................................. 312
4.3.20 Unit Attention parameters page (00h) ........................................................................... 314
4.3.21 Verify Error Recovery mode page (07h) ....................................................................... 316
4.4 Vital product data parameters .................................................................................................. 318
4.4.1 Vital product data parameters overview and page codes ............................................. 318
4.4.2 ASCII Information VPD page (01h - 7Fh) ..................................................................... 319
4.4.3 Date Code page (C1h) .................................................................................................. 320
4.4.4 Device Behavior page (C3h) ......................................................................................... 321
4.4.5 Extended INQUIRY Data VPD page (86h) ................................................................... 322
4.4.6 Firmware Numbers page (C0h) ....................................................................................324
4.4.7 Device Identification VPD page (83h) ...........................................................................327
4.4.8 Jumper Settings page (C2h) ......................................................................................... 330
4.4.9 Supported Vital Product Data pages (00h) ................................................................... 333
4.4.10 Unit Serial Number page (80h) ..................................................................................... 334
Index ....................................................................................................... 335
SCSI Commands Reference Manual, Rev. A ix
x SCSI Commands Reference Manual, Rev. A
List of Tables
Table 1. ISO v American Numbering Conventions .................................................................................. 15
Table 2. Typical CDB for 6-byte commands ............................................................................................ 18
Table 3. Typical CDB for 10-byte commands .......................................................................................... 19
Table 4. Typical CDB for 12-byte commands .......................................................................................... 19
Table 5. Typical CDB for 16-byte commands .......................................................................................... 20
Table 6. Typical CDB for long LBA 16-byte commands .......................................................................... 21
Table 7. Typical variable length CDB ...................................................................................................... 22
Table 8. Typical variable length CDB for long LBA 32-byte commands .................................................. 23
Table 9. OPERATION CODE byte .......................................................................................................... 24
Table 10. Group Code values .................................................................................................................... 24
Table 11. Control Byte ............................................................................................................................... 26
Table 12. Sense data response codes ...................................................................................................... 29
Table 13. Descriptor format sense data ..................................................................................................... 30
Table 14. Sense data descriptor format ..................................................................................................... 31
Table 15. Sense data descriptor types ...................................................................................................... 31
Table 16. Information sense data descriptor format .................................................................................. 32
Table 17. Command-specific information sense data descriptor format .................................................... 33
Table 18. Sense key specific sense data descriptor format ...................................................................... 34
Table 19. Sense key specific field definitions ............................................................................................ 35
Table 20. Field pointer sense key specific data ......................................................................................... 35
Table 21. Actual retry count sense key specific data ................................................................................. 36
Table 22. Progress indication sense key specific data .............................................................................. 37
Table 23. Segment pointer sense key specific data .................................................................................. 37
Table 24. Field replaceable unit sense data descriptor format .................................................................. 38
Table 25. Vendor specific sense data descriptor format ............................................................................ 38
Table 26. Fixed format sense data ............................................................................................................ 39
Table 27. Sense key descriptions .............................................................................................................. 42
Table 28. Additional Sense and Additional Sense Qualifier codes ............................................................ 43
Table 29. CHANGE DEFINITION command .............................................................................................54
Table 30. Definition parameter field ........................................................................................................... 54
Table 31. FORMAT UNIT command ......................................................................................................... 57
Table 32. FORMAT UNIT command address descriptor usage ................................................................ 59
Table 33. FORMAT UNIT parameter list ................................................................................................... 60
Table 34. Short parameter list header ....................................................................................................... 61
Table 35. Long parameter list header ........................................................................................................ 61
Table 36. FMTPINFO bit, RTO_REQ bit, and PROTECTION FIELDS USAGE field ................................ 61
Table 37. Initialization pattern descriptor ................................................................................................... 64
Table 38. Initialization pattern modifier (IP MODIFIER) field ..................................................................... 65
SCSI Commands Reference Manual, Rev. A xi
Table 39. initialization pattern type field .....................................................................................................66
Table 40. Address descriptor formats ........................................................................................................67
Table 41. Short block format address descriptor (000b) ............................................................................67
Table 42. Long block format address descriptor (011b) .............................................................................67
Table 43. Bytes from index format address descriptor (100b) ...................................................................68
Table 44. Physical sector format address descriptor (101b) ......................................................................69
Table 45. INQUIRY command ...................................................................................................................70
Table 46. Standard INQUIRY data format .................................................................................................72
Table 47. PERIPHERAL QUALIFIER ........................................................................................................73
Table 48. PERIPHERAL DEVICE TYPE ....................................................................................................74
Table 49. VERSION field codes .................................................................................................................75
Table 50. Taret Port GroupSupport codes .................................................................................................76
Table 51. BQue and CmdQue bit combinations .........................................................................................77
Table 52. SPI-specific standard INQUIRY bits ...........................................................................................78
Table 53. ADDR and WBUS bit rela tio nship s ............................ ...... ............................................. .............79
Table 54. CLOCKING codes ......................................................................................................................79
Table 55. LOG SELECT command ............................................................................................................81
Table 56. Page Control field values ...........................................................................................................82
Table 57. LOG SENSE command ..............................................................................................................84
Table 58. MODE SELECT(6) command ....................................................................................................86
Table 59. Mode page policies ....................................................................................................................86
Table 60. MODE SELECT(10) command ..................................................................................................88
Table 61. MODE SENSE(6) command ......................................................................................................89
Table 62. Page control (PC) field ...............................................................................................................89
Table 63. Mode page code usage for all devices .......................................................................................90
Table 64. MODE SENSE(10) command ....................................................................................................92
Table 65. PERSISTENT RESERVE IN command .....................................................................................93
Table 66. PERSISTENT RESERVE IN service action codes ....................................................................93
Table 67. PERSISTENT RESERVE IN parameter data for READ KEYS ..................................................94
Table 68. PERSISTENT RESERVE IN parameter data for READ RESERVATION with reservation .......95
Table 69. PERSISTENT RESERVE IN data for READ RESERVATION with no reservation held ............95
Table 70. Persistent reservation scope codes ...........................................................................................96
Table 71. Persistent reservation type codes ..............................................................................................97
Table 72. PERSISTENT RESERVE IN parameter data for REPORT CAPABILITIES ..............................98
Table 73. Persistent Reservation Type Mask format .................................................................................99
Table 74. PERSISTENT RESERVE IN parameter data for READ FULL STATUS .................................100
Table 75. PERSISTENT RESERVE IN full status descriptor format ........................................................101
Table 76. PERSISTENT RESERVE OUT command ...............................................................................103
Table 77. PERSISTENT RESERVE OUT service action codes ..............................................................104
Table 78. PERSISTENT RESERVE OUT parameter list .........................................................................105
Table 79. PERSISTENT RESERVE OUT specify initiator ports additional parameter data ....................106
Table 80. PERSISTENT RESERVE OUT service actions and valid parameters (part 1 of 2) .................107
Table 81. PERSISTENT RESERVE OUT command with REGISTER AND MOVE service ....................108
Table 82. PERSISTENT RESERVE OUT service actions and valid parameters (part 2 of 2) .................108
Table 83. READ (6) command .................................................................................................................111
Table 84. Protection information checking for READ (6) .........................................................................112
Table 85. READ (10) command ...............................................................................................................113
xii SCSI Commands Reference Manual, Rev. A
Table 86. RDPROTECT field ................................................................................................................... 113
Table 87. Force unit access for read operations ..................................................................................... 117
Table 88. READ (12) command ............................................................................................................... 118
Table 89. READ (16) command ............................................................................................................... 119
Table 90. READ (32) command ............................................................................................................... 120
Table 91. READ BUFFER command ....................................................................................................... 122
Table 92. READ BUFFER MODE field .................................................................................................... 122
Table 93. READ BUFFER header ........................................................................................................... 123
Table 94. Buffer offset boundary ............................................................................................................. 124
Table 95. READ BUFFER descriptor ....................................................................................................... 124
Table 96. Echo buffer descriptor .............................................................................................................. 125
Table 97. READ CAPACITY (10) command ............................................................................................126
Table 98. READ CAPACITY (10) parameter data ................................................................................... 127
Table 99. READ CAPACITY (16) command ............................................................................................128
Table 100. READ CAPACITY (16) parameter data ................................................................................... 129
Table 101. P_TYPE field and PROT_EN bit ..............................................................................................................129
Table 102. READ DEFECT DATA (10) command ..................................................................................... 130
Table 103. READ DEFECT DATA (10) parameter data ............................................................................ 131
Table 104. READ DEFECT DATA (12) command ..................................................................................... 133
Table 105. READ DEFECT DATA (12) parameter data ............................................................................ 134
Table 106. READ LONG (10) command ................................................................................................... 135
Table 107. READ LONG (16) command ................................................................................................... 136
Table 108. REASSIGN BLOCKS command ..............................................................................................137
Table 109. REASSIGN BLOCKS parameter list ........................................................................................ 138
Table 110. REASSIGN BLOCKS short parameter list header ................................................................... 138
Table 111. REASSIGN BLOCKS long parameter list header .................................................................... 138
Table 112. RECEIVE DIAGNOSTIC RESULTS command ....................................................................... 140
Table 113. Diagnostic Data Bytes ............................................................................................................. 141
Table 114. RELEASE(6) Command .......................................................................................................... 143
Table 115. RELEASE (10) Command ....................................................................................................... 144
Table 116. RELEASE(10) parameter list ................................................................................................... 145
Table 117. REPORT DEVICE IDENTIFIER command .............................................................................. 146
Table 118. REPORT DEVICE IDENTIFIER parameter data ..................................................................... 146
Table 119. REPORT LUNS command ...................................................................................................... 148
Table 120. SELECT REPORT field ........................................................................................................... 148
Table 121. REPORT LUNS parameter data format ................................................................................... 149
Table 122. REQUEST SENSE command ................................................................................................. 151
Table 123. Response codes 70h and 71h sense data format ................................................................... 153
Table 124. Field pointer bytes ................................................................................................................... 155
Table 125. Actual Retry Count Bytes ......................................................................................................... 156
Table 126. Progress Indication Bytes ........................................................................................................ 156
Table 127. Segment pointer bytes ............................................................................................................. 156
Table 128. RESERVE(6) command .......................................................................................................... 158
Table 129. RELEASE (10) Command ....................................................................................................... 159
Table 130. RESERVE(10) ID only parameter list ...................................................................................... 160
Table 131. REZERO UNIT command (01h) .............................................................................................. 162
Table 132. SEEK command (0Bh) ............................................................................................................. 163
SCSI Commands Reference Manual, Rev. A xiii
Table 133. SEEK command (2Bh) .............................................................................................................164
Table 134. SEND DIAGNOSTIC command ...............................................................................................165
Table 135. SELF-TEST CODE field ...........................................................................................................166
Table 136. SET DEVICE IDENTIFIER command ......................................................................................168
Table 137. SET DEVICE IDENTIFIER parameter list ................................................................................169
Table 138. START STOP UNIT command ............................................................................... ...... ....... . ...170
Table 139. POWER CONDITION field .......................................................................................................170
Table 140. SYNCHRONIZE CACHE (10) command .................................................................................172
Table 141. SYNC_NV bit ...........................................................................................................................172
Table 142. SYNCHRONIZE CACHE (16) command .................................................................................173
Table 143. TEST UNIT READY command ................................................................................................174
Table 144. Preferred TEST UNIT READY responses ................................................................................174
Table 145. VERIFY (10) command ............................................................................................................175
Table 146. VRPROTECT field with BYTCHK set to zero - medium ...........................................................176
Table 147. VRPROTECT field with BYTCHK set to one - medium ............................................................179
Table 148. VRPROTECT field with BYTCHK set to one - data-out buffer .................................................181
Table 149. VRPROTECT field with BYTCHK set to one - byte-by-byte comparison requirements ...........183
Table 150. VERIFY (12) command ............................................................................................................185
Table 151. VERIFY (16) command ............................................................................................................186
Table 152. VERIFY (32) command ............................................................................................................187
Table 153. WRITE (6) command ...............................................................................................................189
Table 154. WRITE (10) command .............................................................................................................190
Table 155. WRPROTECT field ..................................................................................................................190
Table 156. Force unit access for write operations .....................................................................................193
Table 157. WRITE (12) command .............................................................................................................194
Table 158. WRITE (16) command .............................................................................................................195
Table 159. WRITE (32) command .............................................................................................................196
Table 160. WRITE AND VERIFY (10) command .......................................................................................198
Table 161. WRITE AND VERIFY (12) command .......................................................................................199
Table 162. WRITE AND VERIFY (16) command .......................................................................................200
Table 163. WRITE AND VERIFY (32) command .......................................................................................201
Table 164. WRITE BUFFER command .....................................................................................................203
Table 165. WRITE BUFFER MODE field ...................................................................................................203
Table 166. Application log data WRITE BUFFER format ...........................................................................208
Table 167. ERROR TYPE field ..................................................................................................................209
Table 168. CODE SET field .......................................................................................................................209
Table 169. ERROR LOCATION FORMAT field .........................................................................................209
Table 170. WRITE LONG (10) command ..................................................................................................211
Table 171. WRITE LONG (16) command ..................................................................................................212
Table 172. WRITE SAME (10) command ..................................................................................................213
Table 173. LBDATA bit and PBDATA bit ...................................................................................................214
Table 174. WRITE SAME (16) command ..................................................................................................215
Table 175. WRITE SAME (32) command ..................................................................................................216
Table 176. Diagnostic page format ............................................................................................................220
Table 177. Diagnostic page codes .............................................................................................................221
Table 178. Supported diagnostic pages .....................................................................................................221
Table 179. Translate Address page—Receive Diagnostic (40h) ...............................................................222
xiv SCSI Commands Reference Manual, Rev. A
Table 180. Address Field Logical Block Address Format .......................................................................... 223
Table 181. Address Field Physical Sector Address Format ...................................................................... 223
Table 182. SCSI Enclosure Services page ................................................................................................ 224
Table 183. Log page format ....................................................................................................................... 225
Table 184. Log parameter ......................................................................................................................... 226
Table 185. Threshold met criteria .............................................................................................................. 227
Table 186. Log page codes ....................................................................................................................... 229
Table 187. Application client log page ....................................................................................................... 230
Table 188. General usage application client parameter data .................................................................... 230
Table 189. Parameter control bits for general usage parameters (0000h through 0FFFh) ....................... 231
Table 190. Background Scan Results log page ......................................................................................... 232
Table 191. Background Scan Results Parameter codes ........................................................................... 232
Table 192. Background scanning status parameter format ....................................................................... 233
Table 193. Background Scanning Status codes ........................................................................................ 234
Table 194. Medium scan parameter format ............................................................................................... 235
Table 195. REASSIGN STATUS FIELD .................................................................................................... 236
Table 196. Cache Statistics page (37h) ..................................................................................................... 237
Table 197. Error counter log page codes .................................................................................................. 237
Table 198. Parameter codes for error counter log pages ..........................................................................238
Table 199. Factory Log page (3Eh) ........................................................................................................... 239
Table 200. Informational Exceptions log page ........................................................................................... 239
Table 201. Informational exceptions parameter codes .............................................................................. 239
Table 202. Informational exceptions general parameter data ................................................................... 240
Table 203. Parameter control bits for Informational exceptions log parameter (0000h) ............................ 240
Table 204. Non-medium error event parameter codes .............................................................................. 241
Table 205. Non-Medium Error page (06h) ................................................................................................. 241
Table 206. Self-Test Results log page ....................................................................................................... 242
Table 207. Self-test results log parameter format ...................................................................................... 243
Table 208. Parameter control bits for self-test results log parameters ...................................................... 243
Table 209. SELF-TEST RESULTS field .................................................................................................... 244
Table 210. Start-Stop Cycle Counter log page .......................................................................................... 245
Table 211. Parameter control bits for date of manufacture parameter (0001h) ......................................... 246
Table 212. Parameter control bits for accounting date parameter (0002h) ............................................... 247
Table 213. Parameter control bits for start-stop cycle counter parameters (0003h and 0004h) ................ 247
Table 214. Supported log pages ................................................................................................................ 248
Table 215. Temperature log page ............................................................................................................. 249
Table 216. Parameter control bits for temperature parameters (0000h and 0001h) ................................. 250
Table 217. Mode parameter list ................................................................................................................. 251
Table 218. Mode parameter header(6) ...................................................................................................... 251
Table 219. Mode parameter header(10) .................................................................................................... 252
Table 220. General mode parameter block descriptor ..............................................................................253
Table 221. Page_0 mode page format ...................................................................................................... 254
Table 222. SUB_PAGE mode page format ............................................................................................... 254
Table 223. Mode page codes and subpage codes ....................................................................................256
Table 224. Short LBA mode parameter block descriptor ........................................................................... 257
Table 225. Long LBA mode parameter block descriptor ........................................................................... 258
Table 226. Background Control mode page .............................................................................................. 260
SCSI Commands Reference Manual, Rev. A xv
Table 227. Caching Parameters page (08h) ..............................................................................................261
Table 228. Control mode page ...................................................................................................................264
Table 229. Task set type (TST) field ..........................................................................................................264
Table 230. QUEUE ALGORITHM MODIFIER field ....................................................................................265
Table 231. Queue error management (QERR) field ..................................................................................266
Table 232. Unit attention interlocks control (UA_INTLCK_CTRL) field ......................................................267
Table 233. AUTOLOAD MODE field ..........................................................................................................268
Table 234. Control Extension mode page ..................................................................................................269
Table 235. Disconnect-Reconnect mode page ..........................................................................................270
Table 236. Data transfer disconnect control ..............................................................................................272
Table 237. Disconnect-Reconnect mode page (02h) .................................................................................273
Table 238. Disconnect-Reconnect mode page for SAS .............................................................................276
Table 239. Format Parameters page (03h) ................................................................................................278
Table 240. Informational Exceptions Control mode page ..........................................................................280
Table 241. Method of reporting informational exceptions (MRIE) field ......................................................281
Table 242. Notch page (0Ch) .....................................................................................................................283
Table 243. Power Condition mode page ....................................................................................................285
Table 244. Read-Write Error Recovery mode page ...................................................................................287
Table 245. Combined error recovery bit descriptions ................................................................................289
Table 246. protocol identifier values ..........................................................................................................293
Table 247. Protocol Specific Logical Unit mode page ................................................................................293
Table 248. Fibre Channel Logical Unit Control mode page (18h) ..............................................................295
Table 249. SAS Protocol-Specific Logical Unit mode page subpages .......................................................296
Table 250. Protocol-Specific Logical Unit mode page for SAS SSP - short format ...................................296
Table 251. Page_0 format Protocol Specific Port mode page ...................................................................297
Table 252. Sub_page format Protocol Specific Port mode page ...............................................................297
Table 253. Port Control Mode page short format (19h) .............................................................................298
Table 254. Port Control Mode page long format (19h) ...............................................................................299
Table 255. Margin control subpage ............................................................................................................301
Table 256. Saved training configuration values subpage ..........................................................................302
Table 257. Negotiated settings subpage ....................................................................................................304
Table 258. Report transfer capabilities subpage ........................................................................................305
Table 259. Fibre Channel Interface Control page (19h) .............................................................................306
Table 260. Protocol-Specific Port mode page subpages ...........................................................................308
Table 261. Protocol-Specific Port mode page for SAS SSP - short format ................................................308
Table 262. Protocol-Specific Port mode page SAS SSP - Phy Control And Discover subpage ................310
Table 263. SAS phy mode descriptor .......................................................................................................311
Table 264. Rigid Drive Geometry Parameters page (04h) .........................................................................312
Table 265. Unit Attention parameters page (00h) ......................................................................................314
Table 266. Verify Error Recovery mode page ............................................................................................316
Table 267. Vital product data page codes ..................................................................................................318
Table 268. ASCII Information VPD page ...................................................................................................319
Table 269. ETF Log Date Code page (C1h) ..............................................................................................320
Table 270. Device Behavior page (C3h) ....................................................................................................321
Table 271. Extended INQUIRY Data VPD page ........................................................................................322
Table 272. SPT field ...................................................................................................................................322
Table 273. Firmware Number s page (C0h) ........................................................................ ....... ...... .... .......324
xvi SCSI Commands Reference Manual, Rev. A
Table 274. Firmware Numbers page (C0h) (Applies to model families not covered by Table 273) .......... 325
Table 275. Device Identification VPD page ............................................................................................... 327
Table 276. Identification Descriptor ........................................................................................................... 328
Table 277. Code Set .................................................................................................................................. 328
Table 278. PROTOCOL IDENTIFIER values ............................................................................................ 328
Table 279. ASSOCIATION field ................................................................................................................. 329
Table 280. IDENTIFIER Type field ............................................................................................................ 329
Table 281. Device Identification page example ......................................................................................... 330
Table 282. Jumper Settings page (C2h) .................................................................................................... 330
Table 283. Drive ID bit ............................................................................................................................... 331
Table 284. Supported Vital Product Data pages ....................................................................................... 333
Table 285. Unit Serial Number page (80h) ................................................................................................ 334
SCSI Commands Reference Manual, Rev. A xvii
xviii SCSI Commands Reference Manual, Rev. A
1.0 Definitions, symbols, abbreviations, keywords, and conventions
This clause contain s the def initions, s ymbols, abbreviat ions, ke ywords and, con ventions us ed throu ghout this
manual. These items are fr om the Americ an National Standards Institute T10 co mmittee as referenc ed in the
SCSI Primary Commands SPC-4 rev 2 draft and the SCSI Block Commands SBC -2 rev 16 draft.
Applicable Documents:
T10/1416-D SCSI Primary Commands - 3 (SPC-3) Revision 23
T10/1731-D SCSI Primary Commands - 4 (SPC-4) Revision 2
T10/xxxx-D SCSI Block Commands - 3 (SBC-3) Revision 2
T10/1560-D Fibre Channel Protocol for SCSI, Third Editon (FCP-3) Revision 4
T10/1760-D Serial Attached SCSI - 2 (SAS-2) Revision 00
T10/1683-D SCSI Architecure Model - 4 (SAM-4) Revision 3
SCSI Commands Reference Manual, Rev. A 1
1.1 Definitions
Access control list (ACL)
The data used by a SCSI target device to configure access rights for initiator ports according to the access
controls state of the SCSI target device.
Access control list entry (ACE)
One entry in the access control list.
Access controls
An optional SCSI target dev ice feat ure that res tricts ini tiator port acces s to sp ecifi c logical units and mod i-
fies the information a bout logical units in the parame ter data of the INQUIRY and REPORT LUNS com-
mands.
Access controls coordinator
The entity within a SCSI targ et device that c oordinates the manageme nt and enfor cement of ac cess con-
trols for all logi cal u nits withi n the S CS I target de vice . The acce ss c ontro ls coor dinat or is always addr ess-
able through the ACCESS CONTROLS well known logical unit and LUN 0.
active power condition
When a device server is capable of res ponding to a ll of its suppor ted comma nds, incl uding medi a access
requests, without delay.
additional sense code
A combination of the ADDITIONAL SENSE CODE and ADDITI ONAL SENSE CODE QUALIFIER fie lds in
the sense data.
Alias list
A list of alias v alues and their assoc iated desi gnations maintained by the device server an d managed by
the CHANGE ALIASES command and REPORT ALIASES command.
Alias value
A numeric value associated to a designation in the alias list and used in command or parameter data to ref-
erence a SCSI target device or SCSI target port.
Application client
An object that is th e s ourc e o f S C SI c omm and s. F urther d efi nit ion of an application client may be found in
SAM-3.
Attached medium changer
A medium changer that is attached to and accessed through some other type of SCSI device.
Attribute
A single unit of MAM information.
Auto contingent allegiance (ACA)
The task set condition established following the return of a CHECK CONDITION status when the NACA bit
is set to one in the CONTROL byte. A detailed definition of ACA may be found in SAM-3.
Blocked task
A task that is in the b locked state. Tasks become blocked when an ACA condition occurs. The blocked
state ends when the ACA condition is c leare d. A detail ed def ini ti on of the bl oc ke d task state may be foun d
in SAM-3.
Byte
A sequence of eight contiguous bits considered as a unit.
Cache
See cache memory.
2 SCSI Commands Reference Manual, Rev. A
Cache memory
A temporary and often v olatile data storage area outside th e area accessible by applicat ion clients that
may contain a subset of the data stored in the non-volatile data storage area.
Check data
Information contained within a re dundancy group that may allow lo st or destroyed XOR-protected data to
be recreated.
Command
A request describing a unit of work to be performed by a device server. A detailed definition of a command
may be found in SAM-3.
Command descriptor block (CDB)
The structure used to communicat e commands fr om an appli cation clie nt to a device s erver. A CDB may
have a fixed length of up to 16 bytes or a variable length of between 12 and 260 bytes.
Command standard
A SCSI standard that defin es the model, comma nds, and parameter data for a de vice type (e.g., SB C-2,
SSC-2, SMC-2, MMC-4, or SES-2).
Company_id
Synonym for OUI.
Control mode page
A mode page that provides controls over SCSI features (e.g., task set management and error logging) that
are applicable to all device types.
Control Extension mode page
A mode page that provides controls over SCSI features that are applicable to all device types.
Copy manager
The device server that receives an EXTENDED COPY command and performs the operation requested.
Copy target device
The name given by the EX TENDED COPY command to a source or destinati on logical unit (i.e., a c opy
target device is a logical unit, not a SCSI target device).
Cyclic redundancy check (CRC)
An error checking mechanism that checks data integrity by computing a polynomial algorithm based
checksum.
Data defect list (DLIST)
A list of defects sent by the application client to the device server during a FORMAT UNIT command.
Data-in buffer
The buffer specified by the a pplicati on clie nt to receiv e data from the device ser ver duri ng the proce ssing
of a command.
Data-out buffer
The buffer specified by the applicati on client to supply data that is sent from the appl ication client to the
device server during the processing of a command.
Default protection information
Values placed into protec tion information fi elds if an applicati on client does not s pecify specifi c protection
information values.
Deferred error
A CHECK CONDITION status and sense data that is returned as the resul t of an er r or or exception condition that occurred during p roce ssing o f a previo us co mmand f or which GOOD, CO NDITION MET, INTERMEDIATE, and INTERMEDIATE-CONDITION MET status has already been returned.
SCSI Commands Reference Manual, Rev. A 3
Designation
When used in reference to access controls, a name and optional identifier information that specifies a
SCSI target device or SCSI target port for as so ci ation wi th an al ia s v alu e in the ali as lis t. Othe rw is e, a dis-
tinguishing name, identifier, or title.
Device Identification VPD page
A VPD page that provides the means to re trieve identification info rmation about the SCSI device, lo gical
unit, and SCSI port.
Device server
An object within a logi cal unit that processes S CSI tasks according to the rul es of task management. A
detailed definition of a device server may be found in SAM-3.
Device service request
A request, submi tted by an appl ication client, conveying a S CSI command to a device serv er. A detailed
definition of a device service request may be found in SAM-3.
Device service response
The response returne d to an application cli ent by a device se rver on completion o f a SCSI command. A
detailed definition of a device service response may be found in SAM-3.
Device type
The type of peripheral device (i.e., device model) implemented by the device ser ver and indic ated by the
contents of the PERIPHERAL DEVICE TYPE field in the standard INQUIRY data.
Direct-access block device
A device that is capable of containing data stored in blocks that each have a unique logical block address.
Disconnect-Reconnect mode page
A mode page that provides the application client the means to tune the performance of the service delivery
subsystem.
Domain
An I/O system con sisting of a set of SCSI devices that i nteract with one anoth er by means of a s ervice
delivery subsystem.
Element
An addressable physical component of a medium changer SCSI device that may serve as the location of a
removable unit of data storage medium. A detailed definition of an element may be found in SMC-2.
Enabled task state
The only task state in whi ch a task may make progress towards completion. A d etailed definition of the
enabled task state may be found in SAM-3.
Error correcting code (ECC)
An error checki ng mechanism that che cks data integrity and enables some errors i n the data to be cor-
rected.
Exclusive-or (XOR)
A Boolean arithmetic function on two binary input values that results in an output value of 1 if one and only
one of the input values is 1.
Extended Unique Identifier, a 48-bit globally unique identifier (EUI-48)
The IEEE maintains a tutorial describing EUI-48 at http://standards.ieee.org/regauth/oui/tutorials/
EUI48.html.
Extended Unique Identifier, a 64-bit globally unique identifier (EUI-64)
The IEEE maintains a tutorial describing EUI-64 at http://standards.ieee.org/regauth/oui/tutorials/
EUI64.html.
4 SCSI Commands Reference Manual, Rev. A
Extent
A fixed set of logical blocks occupying contiguous logical block addresses on a single logical unit.
Faulted I_T nexus
The I_T nexus on which a CHECK CONDITIO N status was returned tha t resulted in the establishmen t of
an ACA. The faulted I_T nexus condition is cleared when the ACA condition is cleared.
Field
A group of one or more contiguous bits, a part of a larger structure such as a CDB or sense data.
Format corrupt
a vendor-specific condition in which the application client may not be able to perform read operations, write
operations, or verify operations.
Grown defect list (GLIST)
All defects sent by the application client to the device server.
Hard reset
A condition resul ting fr om th e even ts defined by SAM -3 i n which th e SC SI de vice perfo rms the hard reset
operations described in SAM-3, the standard, and the applicable command standards.
Host
A SCSI device with the characteristics of a primary computing device, typically a personal computer, workstation, server, minicomputer, mainframe com puter, or auxiliary computing device. A ho st includ es one or
more SCSI initiator devices.
IEEE company_id
Synonym for OUI.
I_T nexus
A nexus between a SCSI initiator port and a SCSI target port.
I_T nexus loss
A condition resultin g from the events def ined by SA M-3 in which th e SCSI de vice perfor ms the I_T nex us
loss operations described in SAM-3, the standard, and the applicable command standards.
I_T_L nexus
A nexus between a SCSI initiator port, a SCSI target port, and a logical unit.
I_T_L_Q nexus transaction
The information transferred between SCSI ports in a single data structure with defined boundaries (e.g., an
information unit).
Idle power condition
When a device server is capable of res ponding to a ll of its supported comma nds, includi ng media ac cess
requests, but commands may take longer to complete than when in the active power condition.
Implicit head of queue
An optional processing model for specified commands wherein the specified commands may be treated as
if they had been received with a HEAD OF QUEUE
task attribute.
Initiator device name
A SCSI device name of a SCSI initiator device or of a SC SI target/initiator device when operatin g as a
SCSI initiator device.
Initiator port
Synonymous with SCSI initiator port.
SCSI Commands Reference Manual, Rev. A 5
Initiator port identifier
A value by which a SCSI initiator port is referenced within a SCSI domain.
Initiator port name
A SCSI port name of a SCSI initiator port or of a SCSI target/i nit iat or port when ope ra tin g as a SCSI in itia -
tor port.
Internet protocol domain name
The name of a compute r or hierarchy o f computers withi n the domain name s ystem defined b y the IETF
(see RFC 1035 and RFC 1591). The Internet Assigned Numbers Authority maintains a list of domain name
assignments at http://www.iana.org/assignments/domain-names.
Internet protocol number
A coded value assigned to identify protocols that layer on the Internet protocol (see RFC 791). The Internet
protocol number assign ed to the transmission control p rotocol (TCP, see RFC 79 3) is six. The Internet
Assigned Numbers Authority maintains a list of Internet protocol number assignments at http://
www.iana.org/assignments/protocol-numbers.
Linked command
One in a series of SCSI commands processe d by a single task that col lectively make up a disc rete I/O
operation. A detailed definition of a linked command may be found in SAM-3.
Least significant bit (LSB)
In a binary code, the bit or bit po sition with the sma llest numerical weighting in a group of bits that, when
taken as a whole, represent a numerical value (e.g., in the number 0001b, the bit that is set to one).
Left-aligned
A type of field containing ASCII data in whi ch unused byte s are placed at the end of the field ( highest off-
set) and are filled with ASCII space (20h) characters.
Logical block
A set of data bytes accessed and referenced as a unit.
Logical block address (LBA)
The value used to reference a logical block.
Logical unit
An externally addressa ble entity within a SCSI target device that im plements a SCSI device model and
contains a device server. A detailed definition of a logical unit may be found in SAM-3.
Logical unit access control descriptor (LUACD)
The structure within an ACE that ide ntifies a logical unit to which acc ess is allowed an d specifie s the LUN
by which the logical unit is to be accessed.
Logical unit certification list (CLIST)
Defects detected by the dev ice serve r during an optional certific ation proc ess perf ormed duri ng the FOR-
MAT UNIT command.
Logical unit inventory
The list of the logical unit numbers reported by a REPORT LUNS command.
Logical unit number (LUN)
An encoded 64-bit identifier for a logical unit. A detailed definition of a logical unit number may be found in
SAM-3.
Logical unit reset
A condition resu lting from the events de fined by SAM-3 in which the logica l unit performs the logical unit
reset operations described in SAM-3, the standard, and the applicable command standards.
6 SCSI Commands Reference Manual, Rev. A
Media
Plural of Medium
Medium
A physical entity that stores data in a nonv olatile manner (i.e., r etained through a power c ycle) in accordance with commands processed by the device server.
Medium auxiliary memory (MAM)
An auxiliary mem ory res iding on a medium that is accessi ble to the device server (e.g., a tape cartr idge).
Medium auxiliary memory may be nonvolatile and independent of the main function of the device server.
Medium changer
A device that mechaniz es the movement o f media to and from th e SCSI device that records on or re ads
from the media. A detailed definition of a medium changer may be found in SMC-2.
Most significant bit (MSB)
In a binary code, the bit or bit position wi th the largest numerical weightin g in a group of bits that, when
taken as a whole, represent a numerical value (e.g., in the number 1000b, the bit that is set to one).
Name
A label of an object that is unique within a specified context and should never change (e.g., the term name
and worldwide identifier (WWID) may be interchangeable).
Network address authority (NAA)
A field within a name that specifies the format and length of that name. See FC-FS.
Nexus
A relationship betwe en two SCSI devic es, and the SCSI ini tiator port and SCS I target port objects withi n
those SCSI devices.
Non-volatile cache
Cache that retains data through power cycles.
Non-volatile cache memory
Cache memory that retains data through power cycles.
Non-volatile medium
A physical storage medium that retains data written to it for subsequent read operations through power
cycles (e.g., a disk withi n a device that stores data as ma gnetic field changes tha t do not require device
power to exist).
Null-padded
A type of field in which unused bytes are placed at the end of the fie ld (i.e., highest offset) and are filled
with ASCII null (00h) characters.
Null-terminated
A type of field in which the last used byte (i.e., hi ghest offset) is required to contain an ASCII null (00h)
character.
One
The logical true condition of a variable.
Operation Code
The first byte of a SCSI CDB shall contain an operation code identifying the operation being requested by the CDB.
Organizationally unique identifier (OUI)
A numeric identi fier that is assigned by t he IEEE such that no a ssigned identifiers are ident ical. OUI is
equivalent to company_id or IEEE company_id. The IEEE prefers OUI for EUI-48 identifiers and
company_id for EUI-64 i dentif iers. However, the numeric identi fier is call ed an O UI when it is ass igne d by
the IEEE. The IEEE maintains a tutorial describing the OUI at http://standards.ieee.org/regauth/oui/.
SCSI Commands Reference Manual, Rev. A 7
Page
A regular parameter struct ure (or format) used by several com mands. These pages are identified wi th a
value known as a page code.
Persist through power loss
An optional capability associated with some features that allows an application client to request that a
device server maintain information regarding that feature across power failures.
Persistent reservation holder
The I_T nexus(es) that are allowed to release or change a persistent reservation without preempting it.
Power cycle
Power being removed from and later applied to a SCSI device.
Power on
A condition result ing from the events defined b y SAM-3 in wh ich the SCSI device perform s the power o n
operations described in SAM-3, the standard, and the applicable command standards.
Primary defect list (PLIST)
The list of defects that are considered permanent defects.
Protection information
Fields appended to each logica l block that contain a cyclic redundanc y check (CRC), an application tag,
and a reference tag.
Protocol identifier
A coded value used in various fields to identify the protocol to which other fields apply.
Protocol specific
A requirement that is defin ed by a SC SI transp ort protoc ol standard . A detailed definition of protoc ol spe-
cific may be found in SAM-3.
Protocol standard
A SCSI standard that defines SCSI transport protocol (e.g., SAS, SPI-5, SBP-3, or FCP-2).
Proxy token
An identifier for a logical unit that may be used to gain temporary access to that logical unit in the presence
of access controls.
Redundancy group
A grouping of XOR- protected data and associate d check data into a single type of data redundanc y (see
SCC-2). the standard only supports the XOR type of redundancy.
Request for comment (RFC)
The name given to standards developed by the Internet Engineering Task Force.
Registered
The condition that exists for an I_T nexus following the successful completion of a PERSISTENT
RESERVE OUT command with a REGISTER service action, REGISTER A ND IGNORE EXISTING KEY
service action, or REGISTER AND MOVE service action and lasting until the registration is removed.
Registrant
An I_T nexus that is registered.
Right-aligned
A type of field c ontaining ASCII da ta in whi ch unus ed by tes a re placed a t the start of the field ( i.e., lowest
offset) and are filled with ASCII space (20h) characters.
8 SCSI Commands Reference Manual, Rev. A
Relative port identifier
An identifier for a SCSI port that is unique within a SCSI device. Application clients may use the SCSI Ports
VPD page to determine relative port identifier values.
Relative initiator port identifier
A relative port identifier for a SCSI initiator port.
Relative target port identifier
A relative port identifier for a SCSI target port.
SCSI device
A device that contains on e or more SCSI ports that are conne cted to a service delivery subsystem and
supports a SCSI application protocol.
SCSI device name
A name of a SCSI device that is world wide unique within the protocol of a SCSI domain in which the SCSI
device has SCSI por ts. The SCSI device name may b e made available to other SCSI devices or SCSI
ports in protocol specific ways.
SCSI domain
The interconnection of two or more SCSI devices and a service delivery subsystem. A detailed definition of
a SCSI Domain may be found in SAM-3.
SCSI initiator device
A SCSI device contain ing app li cat ion cl ie nts and S C S I ini ti ator po rts that originate device serv i ce a nd task
management requests to be processed by a SCSI target device and receives device service and task management responses from SCSI target devices.
SCSI initiator port
A SCSI initiator device obje ct acts as the co nnection betw een appli cation clients an d the servic e delivery
subsystem through which requests and responses are routed.
SCSI port
A port of a SCSI d evice that c onnects the applica tion client, device server o r task manager t o the ser vice
delivery subsystem.
SCSI port identifier
A value by whi ch a SCSI p ort is refe renced within a domain. T he SCSI po rt identifi er is either an initia tor
port identifier or a target port identifier.
SCSI port name
A name of a SCSI port that is world wide unique wi thin the pr otocol of the S CSI domai n of that SCS I port.
The name may be made av ailable to other SCSI devices or SCSI ports in that S CSI domain in protocol
specific ways.
SCSI Ports VPD page
A VPD page that allows retriev al of information a bout all the SCSI ports in a S CSI target device or SCS I
target/initiator device.
SCSI target device
A SCSI device containing logical units and SCSI target ports that rec eives device service and task management requests for processing and sends device service and task management responses to SCSI initiator devices.
SCSI target port
A SCSI target device object that acts as the connection bet ween device server s and task managers an d
the service delivery subsystem through which requests and responses are routed.
SCSI transport protocol standard
A SCSI standard that defines a SCSI transport protocol (e.g., FCP-2, SAS, SRP, or SBP-3).
SCSI Commands Reference Manual, Rev. A 9
Sense data
Data describing an error or exceptional condition that a device server delivers to an application client in the
same I_T_L_Q nexus transaction as a CHECK CONDITION status or in response to a REQUEST SENSE
command. The format of sense data is defined in SPC-4.
Sense key
The contents of the
SENSE KEY field in the sense data.
Service action
A request describing a unit of work to be performed by a devi c e se rv er. A service action is an exte ns ion of
a command.
Service delivery subsystem
That part of a SCSI I/O syst em that t ransmits ser vice re quests to a logica l unit o r SCSI target device an d
returns logical unit or SCSI target device responses to a SCSI initiator device.
Standby power condition
When a device server is capable of accepting commands , but not capable of processing medi a access
commands.
Status
One byte of response inform ation sent from a device server to an applic ation client upon completion of
each command.
Storage array controller
Any combination of an initiator and ap plication clients (see SAM-3) that orig inates SCSI co mmands, con-
verts input LUNs to output LUNs, and converts input LBAs to output LBAs. A storage array controller orga-
nizes a group of direct -access block devices into various obj ects (e.g., redundancy groups and volume
sets). See SCC-2.
System
One or more SCSI domains operating as a single configuration.
Target device name
A SCSI device name of a SCSI target device or of a SCSI target/initiator device when operating as a SCSI
target device.
Target port
Synonymous with SCSI target port.
Target port asymmetric access state
The characteristic tha t defines the behavi or of a target port and the al lowable command set fo r a logical
unit when commands and task m anagement func tions are routed through the target port maintaining that
state.
Target port group
A set of target ports that are in the same target port asymmetric access state at all times.
Target port group asymmetric access state
The target port asymmetric access state common to the set of target ports in a target port group.
Target port identifier
A value by which a SCSI target port is referenced within a SCSI domain.
Target port name
A SCSI port name of a SCSI targe t port or of a SCSI targe t/initiato r port when oper ating as a SCSI targe t
port.
10 SCSI Commands Reference Manual, Rev. A
T ask
An object within a logical unit that rep resents the work associated with a command or a g roup of linked
commands. A detailed definition of a task may be found in SAM-3.
Task set
A group of tasks within a logi cal unit, whose interac tion is de pendent on th e task managem ent (queui ng)
and ACA rules. See SAM-3 and the Control mode page.
TCP port numb ers
One of the data needed to establi sh a TCP conne ction. TCP po rt numbers may be a ssigned to prot ocols
that layer on TCP by the Intern et Assigned Numbers Authority. The Internet Assigned Numbers Authority
maintains a list of TCP port number assignments at http://www.iana.org/assignments/ port-numbers.
Third-party command
A command sent to one SCSI device requesting than an operation be performed involving two other SCSI
devices (e.g., the EXTEND ED COPY co mmand ma y perfo rm cop y operati ons betw een two or mor e SCSI
devices none of which are the SCSI device to which the EXTENDED COPY command was sent).
Unit attention condition
A state that a logical unit maintains while it has asynchronous s tatus information to repo rt to the initiator
ports associated with one or more I_T nexuses. See SAM-3.
Universal time (UT)
The time at longitude zero, colloquially kno wn as Greenwich Mea n Time. See http://aa.usno.nav y.mil/faq/
docs/UT.html.
URI Schemes
The Internet Assigne d Numbers Authority mai ntains a list of schemes fo r URI and URL names at http://
www.iana.org/assignments/uri-schemes.
User data
Data contained in logical blocks that is not protection information.
UTF-8
A character set that is a transformation format of the character set defined by ISO 10646. See RFC 2279.
Vendor specific (VS)
Something (e.g., a bit, field, or code value) that is not defined by the standard and may be vendor defined.
Volatile cache memory or Volatile cache
Cache memory that does not retain data through power cycles.
Volatile medium
Medium that does not retain data written to i t for a subs equent rea d oper ation t hrough pow er cy cles (e.g .,
a silicon memory device that loses data written to it if device power is lost).
Well known logical unit
A logical unit that only do es speci fic func tions . Well known log ical units allow an ap plica tion cl ient to is sue
requests to receive and manage specific information usually relating to a SCSI target device.
Well known logical unit number (W-LUN)
The logical unit number that identifies a well known logical unit.
XOR operation
Performing an XOR bitwise on two identical-sized multiple-bit input values (e.g., the current value of a logical block and the n ew value for that logical block ). In a storag e array imple menting a redund ancy group,
the XOR operation is used in error c orrec tion al gorithms and may be perfor med by the sto rage array controller or by the direct-access block devices.
SCSI Commands Reference Manual, Rev. A 11
XOR-protected data
Logical blocks, including user data and protection information, if any, that are part of a redundancy group.
Zero
The logical false condit ion of a vari able.
Zero-padded
A type of field in which unused bytes are place d at the end of the field (i.e., highest offset) and are filled
with zeros.
1.2 Symbols and abbreviations
See Table 1 for abbreviations of standards bodi es (e.g., I SO). Addit ional sy mbols an d abbreviat ions use d
in the manual include:
Abbreviation Meaning
< less than
> greater than
ACE Access Control list Entry
ACL Access Control List
ACA Auto Contingent Allegiance
ADC Automation/Drive Interface - Commands
ADT Automation/Drive Interface - Transport Protocol
ASC Additional Sense Code
ASCII American Standard Code for Information Interchange
ASCQ Additional Sense Code Qualifier
ATA AT Attachment (see www.t13.org)
ATAPI AT Attachment with Packet Interface (see www.t13.org)
CDB Command Descriptor Block
CRC Cyclic Redundancy Check
CLIST logical unit certification list
D_ID Destination Identifier (defined in FC-FS)
DLIST data defect list
ECC error correcting code
EUI-48 Extended Unique Identifier, a 48-bit globally unique identifier
EUI-64 Extended Unique Identifier, a 64-bit globally unique identifier
FC-FS Fibre Channel Framing and Signaling Interface
FCP-2 Fibre Channel Protocol for SCSI -2
GLIST grown defect list
HTTP Hypertext Transfer Protocol (see RFC 2616)
I/O input/output
ID Identifier or Identification
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
IP Internet Protocol
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
iSCSI Internet SCSI
ISO Organization for International Standards
LBA Logical Block Address
12 SCSI Commands Reference Manual, Rev. A
LSB Least Significant Bit
LUACD Logical Unit Access Control Descriptor
LUN Logical Unit Number
MAM Medium Auxiliary Memory
MMC-4 SCSI Multi-Media Commands -4
MSB Most Significant Bit
NAA Network Address Authority
n/a not applicable
INCITS InterNational Committee for Information Technology Standards
OCRW SCSI Specification for Optical Card Reader/Writer
OSD Object-based Storage Devices Commands
OUI Organizationally Unique Identifier
PLIST primary defect list
RAID Redundant Array of Independent Disks
RBC SCSI Reduced Block Commands
RDMA Remote Direct Memory Access (see SRP)
RFC Request For Comments
RMC SCSI Reduced Multi-Media Commands
SAM-2 SCSI Architecture Model -2
SAM-3 SCSI Architecture Model -3
SAM-4 SCSI Architecture Model -4
SAT SCSI / ATA Translation
SBC-2 SCSI Block Commands -2
SBC-3 SCSI Block Commands -3
SBP-3 Serial Bus Protocol -3
SCC-2 SCSI Controller Commands -2
SCC-3 SCSI Controller Commands -3
SCSI The architecture defined by the family of standards described in clause 1
SES SCSI-3 Enclosure Services
SES-2 SCSI Enclosure Services -2
SMC-2 SCSI Media Changer Commands -2
SMC-3 SCSI Media Changer Commands -3
SPC SCSI-3 Primary Commands (ANSI INCITS 301-1997)
SPC-2 SCSI Primary Commands -2
SPC-3 SCSI Block Commands - 3
SPC-4 SCSI Primary Commands -4
SPI-5 SCSI Parallel Interface -5
SRP SCSI RDMA Protocol
SSC-2 SCSI Stream Commands -2
TCP Transmission Control Protocol (see RFC 793)
URI Uniform Resource Identifier (see RFC 2396 and RFC 3305)
URL Uniform Resource Locator (see RFC 2396 and RFC 3305)
UT Universal time
USB Universal Serial Bus (see www.usb.org)
VPD Vital Product Data
VS Vendor Specific
W-LUN Well known logical unit number
SCSI Commands Reference Manual, Rev. A 13
1.3 Keywords
Expected
A keyword used to describe the behavior of the hardware or software in the design models assumed by the
standard. Other hardware and software design models may also be implemented.
Ignored
A keyword used to descr ibe an unused bit, byte, word, field or code value. The contents or value of a n
ignored bit, byte, word, field or code value shall not be examined by the receiving SCSI device and may be
set to any value by the transmitting SCSI device.
Invalid
A keyword used to des cribe an illegal or unsupported bit, byte, word, field or code v alue. Receipt of an
invalid bit, byte, word, field or code value shall be reported as an error.
Mandatory
A keyword indicating an item that is required to be implemented as defined in this
standard.
May
A keyword that indicates flexibility of choice with no implied preference (equivalent to “may or may not”).
May not
Keywords that indicate flexibility of choice with no implied preference (equivalent to “may or may not”).
Need not
Keywords indicating a feature that is not required to be implemented (equivalent to “is not required to”).
Obsolete
A keyword indicatin g that an item was defined in prior SCSI s tandards but has been removed from the
standard.
Optional
A keyword that describes features that are not requir ed to be implemented by the s tandard. However, if
any optional feature defined in the standard is implemented, then it shall be implemented as defined in the
standard.
Reserved
A keyword referring to bits, bytes, words, fi elds and co de value s that are s et aside f or future standa rdiza-
tion. A reserved b it, byte , wo r d o r fi eld s ha ll be s et to z ero, or i n acco rdanc e wi th a f utur e exten si on to th e
standard. Recipients are not required to check reserved bits, bytes, words or fields for zero values. Receipt
of reserved code values in defined fields shall be reported as an error.
Restricted
A keyword referring to b its, bytes, words, and fiel ds that are set aside for use in other SCS I standards. A
restricted bit, b yte, word, or field s hall be tr eated as a reserv ed bit, byte, word or field f or the p urposes o f
the requirements defined in the standard.
Shall
A keyword indica ting a mandator y requirement. Designers are re quired to impleme nt all such mand atory
requirements to ensure interoperability with other products that conform to the standard.
Should
A keyword indicating flex ibili ty of cho ice with a str ong ly pr eferr ed al ternative; equivalent to the phras e “it is
strongly recomme nde d.”
Vendor-specific
Something (e.g., a bit , fie ld, or cod e va lu e) that is n ot de fin ed by the sta ndard a nd m ay be us ed d ifferen tly
in various implementations.
14 SCSI Commands Reference Manual, Rev. A
1.4 Conventions
Certain words and terms used in the standard have a spe cific meaning beyo nd the normal Engli sh meaning.
These words and terms are defined ei ther in this clause or in the text where they firs t appear. Names of com-
mands, status codes, sense keys, and additional sense codes are in all uppercase (e.g., REQUEST SENSE).
If there is more than one CDB length for a particular command (e.g., MODE SENSE(6) and MODE
SENSE(10)) and the name of the command is u sed in a sentence without any CDB length descriptor (e.g .,
MODE SENSE), then the condition specified in the sentence applies to all CDB lengths for that command.
Names of fields and state var iables are in uppe rcase (e.g. NAME) . When a field or state variable name c on-
tains acronyms, uppercase let ters may be used for readabilit y. Normal case is used when the contents of a
field or state variable are being discussed. Fields or state variables containing only one bit are usually referred
to as the NAME bit instead of the NAME field.
Normal case is used for words having the normal English meaning.
A binary number is r ep re se nte d i n the standa rd by any sequence of dig its c om pris ed of onl y th e West ern- Ar a-
bic numerals 0 and 1 imme diately followed by a lower -case b (e.g., 0101b). Under scores or spaces may be
included between characters in binary number representations to increase readability or delineate field bound-
aries (e.g., 0 0101 1010b or 0_0101_1010b).
A hexadecimal numbe r is represented in the standard by any se quence of digits com prised of only the West-
ern-Arabic numera ls 0 through 9 and /or th e uppe r-cas e Eng lish l etters A thr ough F immedi ately followed b y a
lower-case h (e.g., FA23h). Underscores or spaces may be included in hexadecimal number representations to
increase readability or delineate field boundaries (e.g., B FD8CFA23h or B_FD8C_FA23h).
A decimal number is represented in the standard by any sequence of digits comprised of only the Western-Ara-
bic numerals 0 through 9 not immediately followed by a lower-case b or lower-case h (e.g., 25).
When the value of the bit or field is not relevant, x or xx appears in place of a specific value.
the standard uses the ISO convention for representing decimal numbers (e.g., the thousands and higher multi-
ples are separated by a space and a comm a is used as the decim al point). Table 1 shows some examples of
decimal numbers represented using the ISO and American conventions.
Table 1 — ISO v American Numbering Conventions
ISO American
0,6 0.6
3,141 592 65 3.14159265
1 000 1,000
1 323 462 1,323,462.95
Lists sequenced by letters (e.g., a) red, b) blue, c) green) show no ordering relationship between the listed
items. Lists sequenced by numbers (e.g., 1) red, 2) blue, 3) green) show an ordering relationship between the
listed items.
If a conflict arises between tex t, tables or figur es, the order of pr ecedence to r esolve th e conflicts is tex t, then
tables, and finally figu res. Not al l tables o r fi gures a re fu lly describe d in the tex t. Tables show data format and
values. Notes do not constitute any requirements for implementors.
SCSI Commands Reference Manual, Rev. A 15
16 SCSI Commands Reference Manual, Rev. A
2.0 General Concepts
This manual defines behav iors that are co mmon to all Seagate SC SI device mo dels. This man ual defines the
SCSI commands that are ba si c to m or e th an o ne d is c dr iv e mo del an d th e SC SI c om man ds tha t ma y apply to
any SCSI Interface, including Parallel, Fibre Channel, and Serial Attached SCSI (SAS).
SCSI Commands Reference Manual, Rev. A 17
2.1 Command Descriptor Block (CDB)
2.1.1 CDB usage and structure
A command is communic ate d by se ndi ng a comma nd des c ripto r bl ock (C DB) to the dev ic e se rver. For several
commands, the CD B is accompanied by a list of param eters in the Data-Out Buffer. See the specific commands for de tailed information.
If a logical unit validates reserved CDB fields and receives a reserved field within the CDB that is not zero, then
the logical unit sh all t er min ate th e c om ma nd with CH ECK C ON D ITIO N status, wi th the s ens e key s et to ILL EGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
If a logical unit rece ives a res erved CDB co de value in a fi eld other than the
OPERATION CODE field, then the
logical unit shall termin ate the co mmand wi th CHECK CO NDITION sta tus, with the s ense ke y set to ILL EGAL
REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
The fixed length CDB formats are des cribe d in 2.1 .2. The v ariabl e lengt h CDB form ats are des cribed in 2.1.4 .
The CDB fields that ar e common to most commands ar e described in 2.1.5. The fields s hown in 2.1.2 and
2.1.3 and described in 2.1. 4 are us ed c on sist entl y by mo st co mmands. However, the actual usage of any fi el d
(except
OPERATION CODE and CONTROL) is desc ribed in the subclause de fining that command. If a device
server receives a CDB containing an operation code that is invalid or not supported, the command shall be terminated with CHECK CO NDITION status, with the se nse key set to ILLE GAL REQUEST, and the additional
sense code set to INVALID COMMAND OPERATION CODE.
For all commands, if th ere is an in vali d parameter in the CDB , the dev ice server shal l termin ate the comman d
without altering the medium.
2.1.2 The fixed length CDB formats
All fixed length CDBs shall have an OPERATION CODE field as their first byte and a CONTROL byte as their last byte.
Table 2 shows the typical format of a 6-byte CDB. Table 3 shows the typical format of a 10-byte CDB. Table 4 shows the
typical format of a 12-byt e CDB. Table 5 shows the typical forma t of a 16-by te CDB . Table 6 shows the form
at of a 16-byte
CDB for commands that provide for a long LBA.
Table 2 — Typical CDB for 6-byte commands
Bit
Byte
0 OPERATION CODE
1 Miscellaneous CDB information (MSB)
2 LOGICAL BLOCK ADDRESS (if required)
3 (LSB)
4
5 CONTROL
76543210
TRANSFER LENGTH (if required)
PARAMETER LIST LENGTH (if required)
ALLOCATION LENGTH (if required)
18 SCSI Commands Reference Manual, Rev. A
Table 3 — Typical CDB for 10-byte commands
Bit
Byte
0 OPERATION CODE
1 Miscellaneous CDB information SERVICE ACTION (if required)
2 (MSB) LOGICAL BLOCK ADDRESS (if required)
3
4
5 (LSB)
6 Miscellaneous CDB information
7 (MSB) TRANSFER LENGTH (if required)
8
9 CONTROL
76543210
PARAMETER LIST LENGTH (if required)
ALLOCATION LENGTH (if required)
Table 4 — Typical CDB for 12-byte commands
Bit
Byte
76543210
(LSB)
0 OPERATION CODE
1 Miscellaneous CDB information SERVICE ACTION (if required)
2 (MSB) LOGICAL BLOCK ADDRESS (if required)
3
4
5 (LSB)
6 (MSB) TRANSFER LENGTH (If required)
7
8
9 (LSB)
10 Miscellaneous CDB information
11 CONTROL
PARAMETER LIST LENGTH (if required)
ALLOCATION LENGTH (if required)
SCSI Commands Reference Manual, Rev. A 19
Table 5 — Typical CDB for 16-byte commands
Bit
Byte
0 OPERATION CODE
1 Miscellaneous CDB information SERVICE ACTION (if required)]
2 (MSB) LOGICAL BLOCK ADDRESS (if required)
3
4
5 (LSB)
6 (MSB) Additional CDB data (if required)
7
8
9 (LSB)
10 (MSB) TRANSFER LENGTH (If required)
11
12
13 (LSB)
14 Miscellaneous CDB information
76543210
PARAMETER LIST LENGTH (if required)
ALLOCATION LENGTH (if required)
15 CONTROL
20 SCSI Commands Reference Manual, Rev. A
Table 6 — Typical CDB for long LBA 16-byte commands
Bit
Byte
0 OPERATION CODE
1 Miscellaneous CDB information
2 (MSB)
3 LOGICAL BLOCK ADDRESS
4
5
6
7
8
9 (LSB)
10 (MSB) TRANSFER LENGTH (If required)
11
12
13 (LSB)
14 Miscellaneous CDB information
76543210
PARAMETER LIST LENGTH (if required)
ALLOCATION LENGTH (if required)
15 Control
SCSI Commands Reference Manual, Rev. A 21
2.1.3 The variable length CDB formats
The first byte of a variable length CDB shall contain the operation code 7Fh. The CONTROL byte is the second
byte in the variable length CDB (see table 7)
Table 7 — Typical variable length CDB
Bit
Byte
0 OPERATION CODE (7Fh)
1 CONTROL
2 Miscellaneous CDB information
3 Miscellaneous CDB information
4 Miscellaneous CDB information
5 Miscellaneous CDB information
6 Miscellaneous CDB information
7 ADDITIONAL CDB LENGTH (n–7)
8 (MSB) SERVICE ACTION
9 (LSB)
10
:
n
ADDITIONAL CDB LENGTH field
The ADDITIONAL CDB LENGTH field specifies the number of additional CDB bytes. This value in the ADDITIONAL CDB
LENGTH field shall be a multiple of 4. If the number of CDB bytes delivered by the service delivery subsystem is not sufficient to contain the number of bytes specified by the ADDITIONAL CDB LENGTH field, then the command shall be terminated with CHECK CONDITION sta tus, wi th the s ense key set to ILL EGAL REQ UEST, and the additional sense co de set to
INV ALID FIELD IN CDB.
76543210
Service Action specific fields
SERVICE ACTION field
The SERVICE ACTION field specifies the action being requested by the application client. The SERVICE ACTION field is
required in the vari abl e l eng th C DB format and is describ ed in 4 . 3.4 .2. Each se rvi ce ac tio n c ode des c r ipt ion def ine s a num ber of service action specific fields that are needed for that service action.
A 32-byte variable length CDB format is defined for long LBA operations (see table 8)
22 SCSI Commands Reference Manual, Rev. A
Table 8 — Typical variable length CDB for long LBA 32-byte commands
Bit
Byte
0 OPERATION CODE (7Fh)
1 CONTROL
2 Miscellaneous CDB information
3 Miscellaneous CDB information
4 Miscellaneous CDB information
5 Miscellaneous CDB information
6 Miscellaneous CDB information
7 Additional CDB Length (n–7) [9]
8 (MSB) SERVICE ACTION
9 (LSB)
10 Miscellaneous CDB information DPO FUA Miscellaneous CDB information
11 Miscellaneous CDB information
12 (MSB) LOGICAL BLOCK ADDRESS
19 (LSB)
20 Miscellaneous CDB information
76543210
27
28 (MSB) TRANSFER LENGTH (If required)
31
PARAMETER LIST LENGTH (if required)
ALLOCATION LENGTH (if required)
(LSB)
SCSI Commands Reference Manual, Rev. A 23
2.2 Common CDB fields
2.2.1 Operation Code
The first byte of a SCSI CDB shall contain an operation code identifying the operation being requested by the CDB. Some
operation codes pro vi de fo r mo difi ca tio n of th ei r ope r ati on ba se d on a se rvi ce acti on (see 2.1. 4.2). In such cases, the op eration code and service action code combine to identify the operation being requested. The location of the SERVICE
ACTION field in the CDB varies depending on the operation code value.
The OPERATION CODE (see t ab le 10) o f th e C DB ha s a G ROU P CODE fi eld and a COMMAND CODE field. The three-bit
GROUP CODE field provides for eight groups of command codes. The five-bit COMMAND CODE field provides for thirtytwo command codes in each group. A total of 256 possible operation codes exist. Operation codes are defined in the standard and other command standards. The group code value shall determine the length of the CDB
Table 9 — OPERATION CODE byte
Bit76543210
GROUP CODE COMMAND CODE
The value in the GROUP CODE field specifies one of the groups shown in Table 10.
Table 10 — Group Code values
Group
Code
000b 6 byte commands see Table 2
001b 10 byte commands see Table 3
010b 10 byte commands see Table 3
011b
100b 16 byte commands see Table 5 and Table 6
101b 12 byte commands see Table 4
110b Vendor Specific
111b Vendor Specific
a
The format of the co mmands us ing operatio n code 7Fh is des cribed
in 2.1.3. With the exception of operation code 7Fh, all group code
011b operation codes are reserved.
Meaning Typical CDB Format
Reserved
a
(see table 11).
2.2.2 Service action
All CDB formats except the 6-byte format provide for a SERVICE ACTION field containing a coded value identifying a function to be perfo rmed under the more general command function speci fied in the OPERATION
CODE field. While the SERVICE ACTION field is define d for CDB formats, it is use d as describe d in this subclause only in tho se CDB formats that contain a SERVICE ACTION field. When the sp ecific field SERVICE
ACTION is not defined in a CDB format, the bits identified as th e SERVICE ACTION field in a CDB shal l be
used or reserved as specified by the particular CDB format.
2.2.3 Logical block address
The logical block add ress es on a logica l u nit or with in a volume o r partiti on sh all be gin with bloc k zero a nd be
contiguous up to the last logical block of that logical unit or within that volume or partition.
24 SCSI Commands Reference Manual, Rev. A
A six-byte CDB may contain a 21-bit LOGICAL BLOCK ADDRESS field. The ten-byte an d the twelve-byte
CDBs may contain 32-bit LOGICAL BLOCK A DDRESS fields. The sixteen-byte CDB has two formats: on e
allows a 32-bit LOGICAL BLOCK ADDRESS field (see Table 5) and the other allows a 64-bit LOGICAL BLOCK
ADDRESS field (see Table 6). LOGICAL BLOCK ADDRESS fields in additional parameter data have their
length specified for each occurrence. See the specific command descriptions.
2.2.4 Transfer length
The TRANSFER LEN GTH field specifies the amount of data t o be transferred, us ually the numb er of blocks.
Some commands use transfer length to specify the req uested number of bytes to be sent as defi ned in the
command description.
Commands that use one byte for the TRANSFER LENGTH field may allow up to 256 blocks or 256 bytes of
data to be transferred by one command.
In commands that use multiple bytes for the TRANSFER LENGTH field, a transfer length of zero specifies that
no data transfer shall take place. A value of one or greater specifies the number of blocks or bytes that shall be
transferred. Refer to the specific command description for further information.
2.2.5 Parameter list length
The PARAMETER LIST LENGTH field is used to specify the number of bytes sent f rom the Data-Out Buffer.
This field is typica lly used in CDBs for parameters th at are sent to a device server (e.g., mode parameters,
diagnostic parameters, log parameters). A parameter length of zero specifies that no data shall be transferred.
This condition shall not be considered as an error, unless otherwise specified.
2.2.6 Allocation length
The ALLOCATION LENGTH field specifies the max imum number of bytes tha t an application client has allocated in the Data-In Buffe r. An allocation le ngth of zer o sp ecifi es tha t no data sh all be trans ferred. This c ondition shall not be considered as an error. The device server shall terminate transfers to the Data-In Buffer when
the number of bytes specified by the ALLO CATION LENGTH field have been transferred or when all availabl e
data have been trans ferred, whichever i s less. The a llocation length is used to l imit the maxim um amount of
variable length data (e.g., mode data, log data, diagnostic data) returned to an application client. If the information being transferr ed to the Da ta-In Bu ffer incl ude s fi el ds containin g counts of the number of bytes in s om e or
all of the data, then the c ontents of th ese fiel ds sh all no t be alt ered to reflec t the trunc ation, if any, that results
from an insufficient ALLOCATION LENGTH value, unless the standard that describes the Data-In Buffer format
states otherwise.
If the amount of information to be transferred ex ceeds the maximum value that the ALLOCATION LENGTH
field is capable of specifying, the device server shall transfer no data and terminate the command with CHECK
CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INVALID FIELD IN CDB.
SCSI Commands Reference Manual, Rev. A 25
2.2.7 Control
The contents of the CONTROL byte are de fin ed i n SA M-4. The CONTROL byte has the sa me de fin iti on for all
commands.
SAM-4 clause 5.2 states:
All CDBs shall con tain a CONTROL byte (see table 11). The location of the CONTROL byte with in a CDB
depends on the CDB format (see 2.1.2 and 2.1.3).
Table 11 — Control Byte
Bit76543210
Vendor Specific Reserved NACA Obsolete [1] LINK
[1] Bit 1 of the Control byte was formerly the Flag bit See Flag bit below).
All SCSI transport pro tocol standards shall define th e functionality needed for a logical unit to implement th e
NACA bit and LINK bit.
NACA (Normal ACA) bit
The NACA (Normal ACA) bit specifies whether an auto contingent allegiance (ACA) is established if the command returns
with CHECK CONDITION status. An NACA bit set to one specifies that an ACA shall be established.
0 An NACA bit set to zero specifies that an ACA shall not be established. The actions for ACA are specified in SAM-4
clause 5.8.2. Acti on s th at may b e required when an ACA is no t es t ab lis hed are described in SAM-4 clause 5.8.1. All
logical units shall implement support for the NACA value of zero and may support the NACA value of one (i.e.,
ACA). The ability to sup port a NA CA va lu e of o ne i s i ndi ca ted w ith t he NO RMACA bit in the stand ard INQU IRY data
(see SPC-4).
1 If the NACA bit is set to one but the logical unit does not support ACA, the command shall be terminated with
CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to
INV ALID FIELD IN CDB.
LINK bit
The LINK bit is used to continue the task across multiple commands. Support for the LINK bit is optional. The application
client sets the LINK bit to one to specify a request for continuation of the task across two or more commands.
1 If the LINK bit is set to one and the command completes successfully, a logical unit that supports the LINK bit shall
continue the task and return a status of INTERMEDIATE or INTERMEDIATE-CONDITION MET and a service
response of LINKED COMM AND CO MPLETE (se e SAM-4). If the LIN K bit is set to one and the logic al unit does n ot
support linked commands, the command shall be terminated with CHECK CONDITION status, with the sense key
set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.D FIELD IN CDB.
FLAG bit -- declared Obsolete by T10
Bit 1 (formerly the flag bit) was made obsolete prior to the release of SAM-2 in September of 2002.
Note. In older model d rives the F lag b it may h ave b een us ed in conjunc tion with th e Lin k bit to notify the
initiator in an expedited manner that the command has completed.
Support for the F lag bit is a logical unit option. If the Link bit and Flag b it are both set to o ne, and if the
command completes with a status of Inte rmedi ate or Inte rmedi ate -C ondi ti on Met , a drive that sup ports the
Flag bit returns a service response of Linked Command Complete (with Flag).
The drive completes the command with a status of Check Condition and a sense key of Illegal Request if:
[a] • The Link bit is set to one and the drive does not support linked commands, or
[b] • The Flag bit is set to one and the drive does not support the Flag bit, or
[c] • The Flag bit is set to one and the Link bit is set to zero.
26 SCSI Commands Reference Manual, Rev. A
2.2.8 Grouping function
A grouping function is a function that collects information about attributes associated with commands (i.e.,
information about c ommand s with t he same group va lue are coll ected int o the spec ified g roup). The defini tion
of the attributes and the gr oups is outside the scope of this s tandard. Groups are identified with the
NUMBER
field in the CDB of certain commands (e.g., the WRITE (10) command (see 3.54)).
GROUP
The collection of this in formation is outside the sc ope of this standar d (e.g., the i nformatio n may not be tran smitted using any SCSI protocols).
Note. An exam ple of how grouping could be used, consider two applications using a subsystem; one
application stre ams d ata and anoth er ac cesse s data r andom ly. If the streaming applica tio n groups
all of its commands with one value (e.g., x), and the random application groups all of its commands
with another value (e.g., y), then a group x defined to hold performance metrics collects all the performance metrics for th e streamed comm ands together and a group y de fined to also h old performance metrics colle cts all t he perfor mance metric s for the random comm ands t oget her. The result
is two sets of performance metric s (i.e ., x and y). A mana gem ent ap pli c ation then reads the performance metrics and determines if the performance of a specific group is acceptable.
Support for the grouping function is indicated in the
(see SPC-4).
GROUP_SUP bit in the Extended INQUIRY Data VPD page
SCSI Commands Reference Manual, Rev. A 27
2.3 Parameter rounding
Certain parameters sent to a SCSI targ et port with va rious comma nds conta in a rang e of va lues. Targets may
choose to implement onl y selected values from this range. When the target recei ves a value that it does not
support, it either rejects the command (CHECK CONDITION status with Illegal Request Sense key) or it
rounds the value rec eived to a sup ported value . The targe t shall r ejec t unsupp orted value s unle ss round ing is
permitted in the description of the parameter.
Rounding of parameter values, when permitted (Rounding is enabled by MODE SELECT command, page
code 00h, byte 2, bit 2) shall be performed as follows:
a SCSI target port that receives a parameter value that is not an exact supported value shall adjust the value to
one that it supports and shall return CHECK CONDITION status with a sense key of Recovered Error. The
additional sense co de shall be set to Roun ded Parameter. The initiator is res ponsible to is sue an appropriat e
command to learn what value the target has selected.
Implementor ’s Note: Generally, the target should adjust maximum-value fi elds down to the next lower supported value than the on e specified by the initiator. Minimum-value field s should be rounded up to the next
higher supported value than the one specified by the initiator. In some cases, the type of rounding (up or down)
is explicitly specified in the description of the parameter.
28 SCSI Commands Reference Manual, Rev. A
2.4 Sense data
2.4.1 Sense data introduction
Sense data shall be returned in the sam e I_T_L_ Q ne xu s tr ansac ti on as a CHECK CONDITIO N s tatus and as
parameter data in response to the REQUES T SENSE command. Sens e data returned in the same I_T_L_Q
nexus transaction as a CHECK CONDITION status shall be either fixed or descriptor format sense data for mat
based on the value of the D_SENSE bit in the Con trol mode page. The REQUE ST SENS E command may be
used to request either the fixed format sense data or the descriptor format sense data.f
The first byte of all sense data contains the RESPONSE CODE field that indicates the error type and format of
the sense data (see table 12).
T able 12 — Sense data response codes
Response
Code
00h - 6Fh Reserved
70h Current 2.4.1.3 Fixed 2.4.1.2
71h Deferred 2.4.1.4 Fixed 2.4.1.2
72h Current 2.4.1.3 Descriptor 2.4.1.1
73h Deferred 2.4.1.4 Descriptor 2.4.1.1
74h - 7Eh Reserved
7Fh Vendor specific
Description Reference Description Reference
Error type Sense data format
The RESPONSE CODE field shall be set to 70h in all unit attention sense data in which:
a) The ADDITIONAL SENSE CODE field is set to 29h; or
b) The additional sense code is set to MODE PARAMETERS CHANGED.
SCSI Commands Reference Manual, Rev. A 29
2.4.1.1 Descriptor format sense data
2.4.1.1.1 Descriptor format sense data overview
The descriptor format sens e data for respo nse codes 72h ( curren t errors) and 73h (d eferred er rors) is define d
in table 13.
T a ble 13 — Descriptor format sense data
Bit
Byte
0 Reserved RESPONSE CODE (72h or 73h)
1 Reserved SENSE KEY
2 ADDITIONAL SENSE CODE
3 ADDITIONAL SENSE CODE QUALIFIER
4
5
6
7 ADDITIONAL SENSE LENGTH (n-7)
8
76543210
Reserved
Sense Data Descriptor(s)
.
.
.
SENSE DATA DESCRIPTOR 0 (see table 14)
n
RESPONSE CODE field
The contents of the RESPONSE CODE fi eld indicate the error typ e a nd format of the sense data (see 2.4.1). For de sc ript or
format sense data, the RESPONSE CODE field shall be set to 72h or 73h.
SENSE KEY, ADDITIONAL SENSE CODE and ADDITIONAL SENSE CODE QUALIFIER fields
The SENSE KEY, ADDITIONAL SENSE CODE and ADDITIONAL SENSE CODE QUALIFIER fields provide a hierarchy of
information. The hierarchy provides a top-down approach for an application client to determine information relating to the
error and exception conditions.
SENSE KEY field
The SENSE KEY field indicates generic information describ ing an error or exception conditio n. Th e s ens e key s are def ine d
in 2.4.1.5.
ASC (ADDITIONAL SENSE CODE) field
The ADDITIONAL SENSE CODE (ASC) field indicates further information related to the error or exception condition
reported in the SENSE KEY field. Support of the additional sense codes not required by this standard is optional. A list of
additional sense codes is in 2.4.1.5. If the device server does not have further information related to the error or exception
condition, the additional sense code shall be set to zero.
SENSE DATA DESCRIPTOR X (see table 14)
30 SCSI Commands Reference Manual, Rev. A
ASCQ (ADDITIONAL SENSE CODE QUALIFIER) field
The ADDITIONAL SENSE CODE QUALIFIER (ASCQ) field indicates detailed information related to the additional sense
code. If the error or exception condition is reported by the device server, the value returned shall be as specified in 2.4.1.5.
If the device server does not have det aile d inform ation rela ted to the error or ex ceptio n condi tion, the ad dition al sens e code
qualifier shall be set to zero.
ADDITIONAL SENSE LENGTH field
The ADDITIONAL SENSE LENGTH field indicates the number of additional sense bytes that follow. The additional sense
length shall be less than or equal to 244 (i.e., limiting the total length of the sense data to 252 bytes). If the sense data is
being returned as parameter data by a REQUEST SENSE command, then the relationship between the ADDITIONAL
SENSE LENGTH field and the CDB ALLOCATION LENGTH field is defined in 2.4.1.1.1.
SENSE DATA DESCRIPTORS field
Sense data descriptors (see table 14) provide specific sense information. A given type of sense data descriptor shall be
included in the sense data only when the information it contains is valid.
Table 14 — Sense data descriptor format
Bit
Byte
0 DESCRIPTOR TYPE
1 ADDITIONAL LENGTH (n-1)
2 SENSE DATA DESCRIPTOR SPECIFIC
n
DESCRIPTOR TYPE field
The DESCRIPTOR TYPE field contains a type code (see table 15) that identifies the type of sense data descriptor. No
more than one sense data descriptor of each type shall be included in the descriptor format sense data.
76543210
Table 15 — Sense data descriptor types
Type Description Reference
00h
01h
02h
03h
04h
05h
06h
07h
08h
09h
0Ah - 7Fh
80h - FFh
Information 2.4.1.1.2
Command specific information 2.4.1.1.3
Sense key specific 2.4.1.1.4
Field replaceable unit 2.4.1.1.5
Stream commands SSC-3
Block commands SBC-2
OSD object identification OSD
OSD response integrity check value OSD
OSD attribute identification OSD
ATA Return SAT
Reserved
Vendor specific 2.4.1.1.6
SCSI Commands Reference Manual, Rev. A 31
ADDITIONAL LENGTH field
The ADDITIONAL LENGTH field indicates the number of sense data descriptor specific bytes that follow in the sense data
descriptor.
2.4.1.1.2 Information sense data descriptor
The information sense data descriptor (see table 16) provides information that is device-type or command specific and is defined in a command standard.
Table 16 — Information sense data descriptor format
Bit
Byte
0 DESCRIPTOR TYPE (00h)
1 ADDITIONAL LENGTH (0Ah)
2 VALID (1b) Reserved
3 Reserved
4
11
DESCRIPTOR TYPE and ADDITIONAL LENGTH fields
The DESCRIPTOR TYPE and ADDITIONAL LENGTH fields are described in 2.4.1.1.1. For the information sense data
descriptor, the DESCRIPTOR TYPE field shall be set to 00h and the ADDITIONAL LENGTH field shall be set to 0Ah.
76543210
INFORMATION
The VALID bit shall be set to one.
Note. In previous v ersions of this standard and in the fixed format sense data, the VALID bi t indicates
whether the contents of the INFORMATION field is valid as defined by a command standard. Since
the contents of the INFORMATION field are valid whenever an information sense data descriptor is
included in the sense data, the only legal value for the VALID bit is set to one.
INFORMA T ION field
The contents of the INFORMATION field are device-type or command specific and are defined in a command standard.
When a four byte quantity is stored in the INFORMATION field, the first four bytes shall be zero.
32 SCSI Commands Reference Manual, Rev. A
2.4.1.1.3 Command-specific information sense data descriptor
The command-specifi c informa tion sens e data descriptor (see table 17) prov ides inf ormation that de pends on
the command on which the exception condition occurred.
Table 17 — Command-specific information sense data descriptor format
Bit
Byte
0 DESCRIPTOR TYPE (01h)
1 ADDITIONAL LENGTH (0Ah)
2 Reserved
3 Reserved
4 COMMAND-SPECIFIC INFORMATION
11
DESCRIPTOR TYPE and ADDITIONAL LENGTH fields
The DESCRIPTOR TYPE and ADDITIONAL LENGTH fields are described in 2.4.1.1.1. For the command-specific information sense data descriptor, the DESCRIPTOR TYPE field shall be set to 01h and the ADDITIONAL LENGTH field shall be
set to 0Ah.
COMMAND-SPECIFIC INFORMATION field
The COMMAND-SPECIFIC INFORMATION field contains information that depends on the command on which the exception condition occu rred. Wh en a fou r byte quanti ty is s tored i n the COMMAND-SPECIFIC INFORMAT ION field, the first fo ur
bytes shall be zero.
Further meaning for the COMMAND-SPECIFIC INFORMATION field is defined within the command description in the
appropriate command standard (e.g., see SBC-2 for the REASSIGN BLOCKS commands, or SPC-3 the EXTENDED
COPY command).
76543210
SCSI Commands Reference Manual, Rev. A 33
2.4.1.1.4 Sense key specific sense data descriptor
2.4.1.1.4.1 Sense key specific sense data descriptor introduction
The sense key s pecific sens e data descripto r (see table 18) pr ovides addi tional inform ation about the exception condition. The format and content of the sense-key specific data depends on the value in the SENSE KEY
field (see 2.4.1.1.1).
Table 18 — Sense key specific sense data descriptor format
Bit
Byte
0
1
2
3
4
5
76543210
DESCRIPTOR TYPE (02h)
ADDITIONAL LENGTH (06h)
Reserved
Reserved
SKSV (1b)
SENSE KEY SPECIFIC
6
7
The DESCRIPTOR TYPE and ADDITIONAL LENGTH fields are described in 2.4.1.1.1. For the sense-key specific sense
data descriptor, the DESCRIPTOR TYPE field shall be set to 01h and the ADDITIONAL LENGTH field shall be set to 06h.
SKSV (Sense-key specific valid) bit
The sense-key specific valid (SKSV) bit shall be set to one.
Reserved
Note. In previous versions of this standard and in the fixed format sense data, the SKS V bit indicates
whether the contents of the SENSE KEY SPE CIFIC fiel d are vali d as define d by a com mand standard. Since the cont ents of the SENSE KEY SP ECIFIC fiel d are vali d whenever a sense k ey specific sense data descriptor is included in the sense data, the only legal value for the SKSV bit is set
to one.
34 SCSI Commands Reference Manual, Rev. A
The definition of the SENSE KEY SPECIFIC field (see table 19) is determined by the val ue of th e SENSE KEY
field (see 2.4.1.1.1).
T a ble 19 — Sense key specific field definitions
Sense Key Sense Key Specific Field Definition Reference
ILLEGAL REQUEST Field pointer 2.4.1.1.4.2
HARDWARE ERROR,
MEDIUM ERROR, or
RECOVERED ERROR
NO SENSE or NOT READY Progress i ndication 2.4.1.1.4.4
COPY ABORTED Segment pointer 2.4.1.1.4.5
All other sense keys The sense key specific sense data descriptor shall not appear in the descriptor for-
2.4.1.1.4.2 Field pointer sense key specific data
Actual retry count 2.4.1.1.4.3
mat sense data and the SKSV bit (s ee 2.4.1 .2) sha ll be s et to zero i n the fi xed format
sense data.
If the sense key is ILLEGAL REQUEST, then the SENSE KEY SPECIFIC field shall be as shown in table 20.
Table 20 — Field pointer sense key specific data
Bit
Byte
0
1
2
76543210
SKSV (1b) C/D Reserved BPV BIT POINTER
(MSB)
FIELD POINTER
(LSB)
SKSV bit
The SKSV bit is described in 2.4.1.1.4.1 for descriptor format sense data and in 2.4.1.2 for fixed format sense data.
C/D (Command Data) bit
A command data (C/D) bit set to one indicates that the illegal parameter is in the CDB. A C/D bit set to zero indicates that
the illegal parameter is in the data parameters sent by the application client in the Data-Out Buffer.
BPV (Bit Pointer Valid) bit
A bit pointer valid (BPV) bit set to zero indicates that the value in the BIT POINTER field is not valid. A BPV bit set to one
indicates that the BIT POINTER field specifies which bit of the byte designated by the FIELD POINTER field is in error.
When a multiple-bit field is in error, the BIT POINTER field shall point to the first bit (i.e., the left-most bit) of the field.
FIELD POINTER field
The FIELD POINTER field indicate s which byte o f the CD B or of the p ara meter d ata was i n error. Bytes are numbered starting from zero, as shown in the tables describing the commands and parameters. When a multiple-byte field is in error, the
field pointer shall point to the first byte (i.e., the left-most byte) of the field. If several consecutive bytes are reserved, each
shall be treated as a single-byte field.
Note. The byt es identified as being i n e rro r a re no t necessarily the by tes tha t ne ed to b e c han ged to cor -
rect the problem.
SCSI Commands Reference Manual, Rev. A 35
2.4.1.1.4.3 Actual retry count sense key specific data
If the sense key is HARDWARE ERROR, MEDIUM ERROR, or RECOVERED ERROR, then the SENSE KEY
SPECIFIC field shall be as shown in
table 21.
T able 21 — Actual retry count sense key specific data
Bit
Byte
0
1
2
76543210
SKSV (1b) Reserved
(MSB) ACTUAL RETRY COUNT
(LSB)
The SKSV bit is described in 2.4.1.1. 4.1 for desc riptor format sens e data and in 2.4 .1.2 for fixed form at sens e
data.
The ACTUAL RETRY COUNT field returns vendor specific information on the number of retries of the recovery
algorithm used in attempting to recover an error or exception condition.
36 SCSI Commands Reference Manual, Rev. A
Note. This field should be computed in the same way as the retry count fields within the Read-Write Error
Recovery mode page.
2.4.1.1.4.4 Progress indication sense key specific data
If the sense key is NO SENSE or NOT READY, the SENSE KEY SPECIFIC field shall be as shown in table 22.
T able 22 — Progress indication sense key specific data
Bit
Byte
0
1
2
76543210
SKSV (1b) Reserved
(MSB) PROGRESS INDICATION
(LSB)
The SKSV bit is described in 2.4.1.1. 4.1 for desc riptor format sens e data and in 2.4 .1.2 for fixed form at sens e
data.
The PROGRESS INDICATION field is a percent complete indication in which the returned value is a numerator
that has 65 536 (10000h) as its denominator. The progress indication shall be based upon the total operation.
Note. The progre ss indicati on shoul d be time relat ed, howev er this is no t an absolute r equireme nt. (E.g .,
since format time varies with the number of defects encountered, etc., it is reasonable for the
device server to a ssign values to various steps withi n the process. Th e granularity o f these steps
should be small enough to provide reas ona ble as su ranc es to the app lic at ion c li ent t hat progr es s is
being made.)
2.4.1.1.4.5 Segment pointer sense key specific data
If the sense key is COPY ABORTED, the SENSE KEY SPECIFIC field shall be as shown in table 23.
T able 23 — Segment pointer sense key specific data
Bit
Byte
0
1
2
76543210
SKSV (1b) Reserved SD Reserved BPV BIT POINTER
(MSB) FIELD POINTER
(LSB)
The SKSV bit is described in 2.4.1.1.4.1 for descriptor format s ense da ta and in 2.4.1.2 f or fi xed for m at se ns e
data.
The segment descriptor (SD) bit indicates whether the field pointer is relative to the start of the parameter list or
to the start of a segment descriptor. An
the parameter list . An
SD bit set to one indicates that the fie ld pointe r is rel ative to the s tart of th e segmen t
SD bit set to zero indicates that the field pointer is relative to the start of
descriptor indicated by the third and fourth bytes of the COMMAND-SPECIFIC INFORMATION field.
A bit pointer valid (BPV) bit set to zero indicates that the value in the BIT POINTER field is not valid. A BPV bit
set to one indicates that the BIT POINTER field specifies which bit of the byte designated by the FIELD
POINTER field is in error. When a multiple-bit field is in error, the BIT POINTER field shall point to the mostsignificant (i.e., left-most) bit of the field.
SCSI Commands Reference Manual, Rev. A 37
The FIELD POINTER field indicates which byte of the parameter list or segment descriptor was in error.
If the parameter list is in excess of 65 528 bytes in length and SD is set to zero, the FIELD POINTER value
may not fit in two bytes provided by the sense key specific sense data descriptor.
2.4.1.1.5 Field replaceable unit sense data descriptor
The field replaceable unit sense data descriptor (see table 24) provides information about a component that
has failed.
Table 24 — Field replaceable unit sense data descriptor format
Bit
Byte
0
1
2
3
DESCRIPTOR TYPE and ADDITIONAL LENGTH fields
The DESCRIPTOR TYPE and ADDITIONAL L ENGT H fie lds ar e de sc rib ed in 2.4. 1.1 . 1. F or t he f iel d re pla ceabl e unit sense
data descriptor, the DESCRIPTOR TYPE field shall be set to 03h and the ADDITIONAL LENGTH field shall be set to 02h.
FIELD REPLACEABLE UNIT CODE field
Non-zero values in the FIELD REPLACEABLE UNIT CODE field are used to identify a component that has failed. A value
of zero in this field indicates that no specific component has been identified to have failed or that the data is not available.
The format of this information is not specified by this standard. Additional information about the field replaceable unit may
be available in the ASCII Information VPD page, if supported by the device server.
76543210
DESCRIPTOR TYPE (03h)
ADDITIONAL LENGTH (02h)
Reserved
field replaceable unit code
2.4.1.1.6 Vendor specific sense data descriptors
Vendor specific sense data descriptors (see table 25) contain vendor specific data that further defines the
nature of the exception condition.
Table 25 — Vendor specific sense data descriptor format
Bit
Byte
0
1
2
n
DESCRIPTOR TYPE and ADDITIONAL LENGTH fields
The DESCRIPTOR TYPE and ADDITIONAL LENGTH fields are described in 2.4.1.1.1. For the vendor specific sense data
descriptor, the DESCRIPTOR TYPE field shall be set to a value between 80h and FFh, inclusive.
76543210
DESCRIPTOR TYPE (80h - FFh)
ADDITIONAL LENGTH (n-1)
Vendor specific
38 SCSI Commands Reference Manual, Rev. A
2.4.1.2 Fixed format sense data
The fixed format sense data for response cod es 70h (curren t errors) and 71h (defer red errors) is defi ned in
table 26.
T able 26 — Fixed format sense data
Bit
Byte
0 VALID RESPONSE CODE (70H OR 71H)
1 Obsolete
2 FILEMARK EOM ILI RESERVED SENSE KEY
3
4
5
6
7 ADDITIONAL SENSE LENGTH (N-7)
8
9
10
11
12 ADDITIONAL SENSE CODE
76543210
INFORMATION
COMMAND-SPECIFIC INFORMATION
13 ADDITIONAL SENSE CODE QUALIFIER
14 FIELD REPLACEABLE UNIT CODE
15 SKSV
16
17
18
n
VALID bit
SENSE KEY SPECIFIC
ADDITIONAL SENSE BYTES
0 A VALID bit set to zero indicates that the INFORMATION field is not defined in this manual or any command stan-
dard.
1 A VALID bit set to one indicates the INFORMATION field contains valid information as defined in this standard or a
command standa rd.
RESPONSE CODE field
The contents of the RESPONSE CODE field indicate the error type and format of the sense data (see 2.4.1). For fixed format sense data, the RESPONSE CODE field shall be set to 70h or 71h.
FILE MARK bit
See the SSC-2 READ and SPACE commands for examples of FILEMARK bit usage.
SCSI Commands Reference Manual, Rev. A 39
EOM (End-of-Medium) bit
See the SSC-2 READ, SPACE, and WRITE commands for examples of end-of-medium (EOM) bit usage.
ILI (Incorrect length indicator) Bit
See the SBC-2 READ LONG, SBC-2 WRITE LONG, and SSC-2 READ commands and for ex amples of incor rect length
indicator (ILI) bit usage.
SENSE KEY, ADDITONAL SENSE CODE, and ADDITIONAL SENSE CODE QUALIFIER fields
The SENSE KEY, ADDITIONAL SENSE CODE, and ADDITIONAL SENSE CODE QUALIFIER fields are described in
4.5.2.1.
INFORMA T ION field
The contents of the INFORMATION field are device-type or command specific and are defined in a command standard.
ADDITIONAL SENSE LENGTH field
The ADDITIONAL SENSE LENGTH field indicates the number of additional sense bytes that follow. The additional sense
length shall be less than or equal to 244 (i.e., limiting the total length of the sense data to 252 bytes). If the sense data is
being returned as parameter data by a REQUEST SENSE command, then the relationship between the ADDITIONAL
SENSE LENGTH field and the CDB ALLOCATION LENGTH field is defined in 2.2.6.
COMMAND-SPECIFIC INFORMATION field
The COMMAND-SPECIFIC INFORMATION field contains information that depends on the command on which the exception condition occurred.
FIELD REPLACEABLE UNIT CODE field
The FIELD REPLACEABLE UNIT CODE field is described in 2.4.1.1.5.
SKSV (Sense-key Specific Valid) bit
1 A sense-key specific valid (SKSV) bit set to one indicates the SENSE KEY SPECIFIC field contains valid informa-
tion as defined in this standard.
0 An SKSV bit set to zero indicates that the SENSE KEY SPECIFIC field is not as defined by this standard.
SENSE KEY SPECIFIC field
The SENSE KEY SPECIFIC field is described in 2.4.1.1.4.
The additional sen se bytes may contain vendor specific data that further defines the nature of the e xception
condition.
2.4.1.3 Current errors
Response codes 70h and 72h (c urrent error) indicate that the sense data r eturned is the result of an error or
exception condition on the task that returned the CHECK CONDITION status or a protocol specific failure condition. This includes errors gener ated du ring pr ocessi ng of th e comm and. It also inc ludes er rors not re lated t o
any command that are detected during processing of a command (e.g., disk servo-mechanism failure, off-track
errors, or power-up test errors).
2.4.1.4 Deferred errors
Response codes 71h and 73h ( defer red error) indicate that the sense data retur ned is the result of an erro r or
exception condition that occurred during processing of a previous command for which GOOD, CONDITION
MET, INTERMEDIATE, and INTERMEDIATE-CONDITION MET status ha s alrea dy bee n retu rned. Such commands are associated w ith the use of the immedi ate bit and with som e forms of caching. Dev ice servers tha t
implement these features shall implement deferred error reporting.
The deferred error may be indicated by returning CHECK CONDITION status to an application client accessed
through a defined I_T nexus as described in this subclause.
40 SCSI Commands Reference Manual, Rev. A
If the task terminates with CHECK CONDITION status and the sense data describes a deferred error, the command for the terminate d task shall not ha ve been pro cessed. After the d evice server detects a deferre d error
condition, it shall return a deferred error according to the following rules:
(a) If no external intervention is necessary to recover a deferred error, a deferred error indication shall not
be returned unless r equired by the error handling parameters of a MODE SELECT command. The
occurrence of the error may be logged;
(b) If it is possible to associate a deferred error with an I_T nexus and with a particular function or a partic-
ular subset of data, and the error is either unr ec over ed or requi red to be r epo rte d by the mode parameters, then a deferred e rror indication shall be returned for a command received on the I_T nexus
associated with the de ferr ed err or. If an application clien t re quest r ec eived on an I_ T nexu s other tha n
the I_T nexus associated with the deferred error attempts to access the particular function or subset of
data associated with the deferred error and the T ST field equals 000 b, then the device server shall
respond to the command with a BUSY or ACA ACTIVE status according to the requirements in SAM-3.
If an application c lient re quest rec eived on an I_T nexu s other than th e I_T nexus as soci ated with th e
deferred error attempts to access the particular function or subset of data associated with the deferred
error and the TST field equals 001b, then the command attempting the access shall not be blocked by
the deferred error an d the cause of the deferred error m ay result in an error being rep orted for the
command attempting the access ;
(c) If the device server is unable to associate a deferred error with an I_T nexus or with a particular subset
of data, the device server shall return a deferred error for one command received on each I_T nexus. If
multiple deferred errors have accumulated for an I_T nexus, only the last error shall be returned;
(d) If the SCSI target de vice is unab le to associate a deferred err or with a particul ar logical unit, it shall
establish a deferred error for every logical unit and shall return the deferred error for one command for
each logical unit received on each appropriate I_T nexus; or
(e) If a task has never entered the enabled task state, and a deferred error occurs, the task shall be termi-
nated with CHECK CONDITION status a nd deferred err or information returned in the sense data. If a
deferred error oc curs after a task has entered the enabled task state and the task is affected by the
error, the task shall be terminated with CHECK CONDITIO N status and the current error in formation
shall be returned in the sense da ta. In this case, if the current error informa tion does not a dequately
define the deferred error condition, a deferred error may be returned after the current error information
has been returned. If a deferred erro r occurs after a task has entered the enabled task state and the
task completes successfully, the device server may choose to return the deferred error information
after the completion of the c urrent com mand in co njunction wi th a subseque nt comman d that has no t
begun processing.
Note. A deferred error may indicate that an operation was unsuccessful long after GOOD status was
returned. If the application client is unable to replicate or recover from other sources the data that is
being written using cached or buffered write operations, then synchronization commands should be
performed before th e critical data is destroyed. This is nec essary for a ctions taken when deferred
errors occur in the s toring of the data. The synchroni zing process should provide t he necessary
commands to allow r eturning CHECK CONDITION status and subseq uent returning of deferred
error sense information after all cached or buffered operations are completed.
SCSI Commands Reference Manual, Rev. A 41
2.4.1.5 Sense key and sense code definitions
The sense keys are defined in table 27.
T able 27 — Sense key descriptions (Sheet 1 of 2)
Sense
Key Description
0h
1h
2h
3h
4h
5h
NO SENSE: Indicates that there is no specific sense key information to be reported. This may
occur for a successful command or for a command that receives CHECK CONDITION status
because one of the FILEMARK, EOM, or ILI bits is set to one.
RECOVERED ERROR: Indicates that the command completed successfully, with some recovery
action performed by the device server. Details may be determined by examining the additional
sense bytes and the INFORMATION field. When multiple recovered errors occur during one
command, the choice of which error to report (e.g., first, last, most severe) is vendor specific.
NOT READY: Indicates that the logical unit is not accessible. Operator intervention may be
required to correct this condition.
MEDIUM ERROR: Indicates that the command terminated with a non-recovered error condition
that may have been caused by a flaw in the medium or an error in the recorded data. This sense
key may also be returned if the device server is unable to distinguish between a flaw in the
medium and a specific hardware failure (i.e., sense key 4h).
HARDWARE ERROR: Indicates that the device server detected a non-recoverable hardware
failure (e.g., controller failure, device failure, or parity error) while performing the command or
during a self test.
ILLEGAL REQUEST: Indicates that:
a) The command was addressed to an incorrect logical unit number (see SAM-3);
b) The command had an invalid task attribute (see SAM-3);
c) The command was addressed to a logical unit whose current configuration prohibits processing
the command;
d) There was an illegal parameter in the CDB; or
e) There was an illegal param eter in the additional parameters supplied as data for some commands
(e.g., PERSISTENT RESERVE OUT).
If the device server detects an invalid parameter in the CDB, it shall terminate the command without altering the medium. If the device server detects an invalid parameter in the additional parameters supplied as data, the device server may have already altered the medium.
6h
7h
UNIT ATTENTION: Indicates that a unit attention condition has been established (e.g., the
removable medium may have been changed, a logical unit reset occurred). See SAM-3.
DA TA PROTECT : Indicates that a command that reads or writes the medium was attempted on a
block that is protected. The read or write operation is not performed.
BLANK CHECK: Indicates that a write-once device or a sequential-access device encountered
8h
blank medium or format-defined end-of-data indication while reading or that a write-once device
encountered a non-blank medium while writing.
9h
Ah
Bh
Ch
VENDOR SPECIFIC: This sense key is available for reporting vendor specific conditions.
COPY ABORTED: Indicates an EXTENDED COPY command was aborted due to an error con-
dition on the source device, the destinati on dev ic e, or both.
ABORTED COMMAND: Indicates that the device server aborted the command. The application
client may be able to recover by trying the command again.
Obsolete
42 SCSI Commands Reference Manual, Rev. A
T able 27 — Sense key descriptions (Sheet 2 of 2)
Sense
Key Description
VOLUME OVERFLOW: Indicates that a buffered SCSI device has reached the end-of-partition
Dh
and data may remain in the buffer that has not been written to the medium. One or more
RECOVER BUFFERED DATA command(s) may be issued to read the unwritten data from the
buffer. (See SSC-2.)
Eh
MISCOMPARE: Indicates that the source data did not match the data read from the medium.
Fh
Reserved
2.4.1.6 Additional Sense and Additional Sense Qualifier codes
Ta ble 28 lists the Additional Se nse (ASC) and Addition al Sense Qualifier (ASC Q) codes. Code value s are in
hexadecimal. ANSI standar d SPC-3 lists a more complete table in error descri ption alphabetical order. This
Table 28 list adequately covers all Seagate drives, however.
Note. Table 28 is for refere nce only, as not all drives covered b y this manual support all of the co des
listed. Codes without sense key references may or may not be supported.
Table 28 — Additional Sense and Additional Sense Qualifier codes
ASC
(byte 12)
00 00 No Additional Sense Information 0
01 00 No Index/Logical Block Signal 4
02 00 No SEEK Complete 4
03 00 Peripheral Device Write Faul t 1, 3, 4
03 86 Write Fault Data Corruption
04 00 Logical Unit Not Ready, Cause Not Reportable 2
ASCQ
(byte 13)
Description
Sense
Key
04 01 Logical Unit Not Ready, Becoming Ready 2
04 02 Logical Unit Not Ready, SMART UNIT Required 2
04 03 Logical Unit Not Ready, Manual Intervention Required 2
04 04 Logical Unit Not Ready, Format in Progress 2
04 09 Logical Unit Not Ready, Self Test in Progress 2
04 0A Logical Unit Not Ready, NVC recovery in progress after and exception event 2
04 11 Logical Unit Not Ready, Notify (Enable Spinup) required 2
04 F0 Logical unit not ready, super certify in progress 2
05 00 ILLEGAL REQUEST 5
06 00 UNIT ATTENTION 6
07 00 Data Protect 7
08 00 Logical Unit Communication Failure 9, B
SCSI Commands Reference Manual, Rev. A 43
ASC
(byte 12)
08 01 Logical Unit Communication Time-Out B
08 02 Logical Unit Communication Parity Error
09 00 Track Following Error 1, 3, 4
09 01 Servo Fault 1, 4
09 04 Head Select Fault 3, 4
09 0D Write to at least one copy of a redundant file failed 1
09 0E Redundant files have < 50% good copies 1
09 F8 Calibration is needed but the QST is set without the Recal Only bit 1
09 FF Servo Cal completed as part of self-test 1
0A 00 Error Log Overflow
0A 01 Failed to write super certify log file 3
0A 02 Failed to read super certify log file 3
0B 00 Aborted Command B
ASCQ
(byte 13)
Description
Sense
Key
0B 01 Warning —Specified Te mpe rature Exceeded 1, 6
0B 02 Warning, Enclosure Degraded 1
0C 00 Write Error 3
0C 01 Write Error Recovered With Auto-Reallocation 1
0C 02 Write Error—Auto Realloc ati on Fai led 3
0C 03 Write Error—Reco mm end Reass ign me nt 3
0C FF Write Error—Too many error recovery revs 3
0D 00 Volume Overflow Constants D
0E 00 Data Miscompare E
10 00 ID CRC Or ECC Error
11 00 Unrecovered Read Error 1, 3
11 01 Read Retries Exhausted
11 02 Error Too Long To Correct
11 04 Unrecovered Read Error—Auto Reallocation Failed 3
11 FF Unrecovered Read Error—T oo ma ny error recovery revs 3
12 00 Address Mark Not Found For ID Field
12 01 Recovered Data Without ECC Using Previous Logical Block ID
12 02 Recovered Data With ECC Using Previous Logical Block ID
44 SCSI Commands Reference Manual, Rev. A
ASC
(byte 12)
14 00 Logical Block Not Found
14 01 Record Not Found 3
15 00 Random Positioning Error
15 01 Mechanical Positioning Error 1, 3, 4
15 02 Positioning Error Detected By Read Of Medium
16 00 Data Synchronization Mark Error 1, 3, 4
17 00 Recovered Data With No Error Correction Applied
17 01 Recovered Data Using Retries 1
17 02 Recovered Data Using Positive Offset 1
17 03 Recovered Data Using Negative Offset 1
17 05 Recovered Data Using Previous Logical Block ID
17 06 Recovered Data Without ECC—Data Auto Reallocated
18 00 Recovered Data With EC C 1
ASCQ
(byte 13)
Description
Sense
Key
18 01 Recovered Data With ECC And Retries Applied 1
18 02 Recovered Data With ECC And/Or Retries, Data Auto-Reallocated 1
18 05 Recovered Data—Recommand Reassignment
18 06 Recovered Data Using ECC and Offsets
18 07 Recovered Data With ECC—Data Rewritten 1
19 00 Defect List Error 1, 4
19 01 Defect List Not Available
19 02 Defect List Error In Primary List
19 03 Defect List Error in Grown List
19 0E Fewer than 50% Defect List Copies
1A 00 Parameter List Length Error 5
1B 00 Synchronous Data Transfer Error
1C 00 Defect List Not Found 1, 4
1C 01 Primary Defect List Not Found
1C 02 Grown Defect List Not Found
1C 83 Seagate Unique Diagnostic Code
1D 00 Miscompare During Verify Operation E
1F 00
Number of Defects Overflows the Allocated Space That The Read Defect Command
Can Handle
1
SCSI Commands Reference Manual, Rev. A 45
ASC
(byte 12)
20 00 Invalid Command Ope rati on C ode 5
20 F3 Invalid linked command operation cod e 5
21 00 Logical Block Address Out Of Range D
24 00 Invalid Field In CDB 5
24 01 Illegal Queue Type for CDB (Low priority commands must be SIMPLE queue) 5
24 F0 Invalid LBA in linked command 5
24 F2 Invalid linked command operation cod e 5
24 F3 Illegal G->P operation request 5
25 00 Logical Unit Not Supported 5
26 00 Invalid Field In Parameter List 5
26 01 Parameter Not Supported 5
26 02 Parameter Va lue Invalid 5
26 03 Invalid Field Parameter—Threshold Parameter 5
ASCQ
(byte 13)
Description
Sense
Key
26 04 Invalid Release of Active Persistent Reserve 5
26 05 Fail to read valid log dump data 5
26 97 Invalid Field Parameter—TMS Firmware Tag
26 98 Invalid Field Parameter—Check Sum
26 99 Invalid Field Parameter—Firmware Tag
27 00 Write Protected 7
29 00 Flashing LED occurred 4
29 00 Power On, Reset, Or Bus Device Reset Occurred 6
29 01 Power-On Reset Occurred 6
29 02 SCSI Bus Reset Occurred 6
29 03 Bus Device Reset Function Occurred 6
29 04 Internal Reset Occurred 6
29 05 Transceiver Mode Changed To Single-Ended 6
29 06 Transceiver Mode Changed To LVD 6
29 07 Write Log Dump data to disk successful OR IT Nexus Loss 6
29 08 Write Log Dump data to disk fail 6
29 09 Write Log Dump Entry information fail 6
29 0A Reserved disc space is full 6
46 SCSI Commands Reference Manual, Rev. A
ASC
(byte 12)
29 0B SDBP test service contained an error, examine status packet(s) for details 6
29 0C SDBP incoming buffer overflow (incoming packet too big) 6
29 CD Flashing LED occurred. (Cold reset) 6
29 CE Flashing LED occurred. (Warm reset) 6
2A 01 Mode Parameters Changed 6
2A 02 Log Parameters Changed 6
2A 03 Reservations preempted 6
2A 04 Reservations Released 6
2A 05 Registrations Preempted 6
2C 00 Command Sequence Error 5
2F 00 Tagged Commands Cleared By Another Initiator 6
31 00 Medium Format Corrupted 3
31 01 Corruption in R/W format request 3
ASCQ
(byte 13)
Description
Sense
Key
31 91 Corrupt World Wide Name (WWN) in drive information file 3
32 00 No Defect Spare Location Available 4
32 01 Defect List Update Error 3, 4, 5
32 02 No Spares Available—Too Many Defects On One Track
32 03 Defect list longer than allocated memory 3
33 00 Flash not read y for access 3
35 00 Unspecified Enclosure Services Failure 4
35 01 Unsupported Enclosure Function 5
35 02 Enclosure Services Unavailable 2
35 03 Enclosure Transfer Failure 4
35 04 Enclosure Transfer Refused 4
37 00 Parameter Rounded 1
3D 00 Invalid Bits In Identify Messa ge
3E 03 Logical Unit Failed Self Test 4
3E 00 Logical Unit Has Not Self Configured Yet
3F 00 Target Operating Conditions Have Changed 6
3F 01 Device internal reset occurred 6
3F 02 Changed Operating Definition 6
SCSI Commands Reference Manual, Rev. A 47
ASC
(byte 12)
3F 05 Device Identifier Changed 6
3F 0F Echo buffer overwritten B
3F 80 Buffer contents have changed 1
3F 90 Invalid APM Parameters
3F 91 World Wide Name (WWN) Mismatch 6
40 01 DRAM Parity Error 1, 4
40 02 Spinup Error recovered with retries 1
42 00 Power-On Or Self-Test Failure 4
42 0A Port A failed loopback test 4
42 0B Port B failed loopback test 4
43 00 Message Reject Error B
44 00 Internal Target Failure 1, 3, 4
44 F2 Data Integrity Check Failed on verify 4
ASCQ
(byte 13)
Description
Sense
Key
44 F6 Data Integrity Check Failed during write 4
44 FF XOR CDB check error 4
45 00 Select/Reselection Failure B
47 00 SCSI Parity Error B
47 03 Information Unit CRC Error B
47 80 Fibre Channel Sequence Error B
48 00 Initiator Detected Error Message Received B
49 00 Invalid Message Rec eiv ed B
4B 00 Data Phase Error B
4B 01 Invalid transfer tag B
4B 02 Too many write data B
4B 03 ACK NAK Timeout B
4B 04 NAK received B
4B 05 Data Offset error B
4B 06 Initiator response timeout B
4C 00 Logical Unit Failed Self-Configuration
4E 00 Overlapped Commands Attempted B
55 01 XOR Cache is Not Available
48 SCSI Commands Reference Manual, Rev. A
ASC
(byte 12)
55 04 PRKT table is full 5
ASCQ
(byte 13)
Description
Sense
Key
1
5B
5B* 01 Threshold Condition Met
5B* 02 Log Counter At Maximum
5B* 03 Log List Codes Exhausted
5C 00 RPL Status Change 6
5C 01 Spindles Synchronized
5C 02 Spindles Not Synchronized
5D 00 Failure Prediction Threshold Exceeded 1, 6
5D FF False Failure Prediction Threshold Exceeded 1, 6
65 00 Voltage Fault 4
80 00 General Firmware Error Qualifier 9
80 86 IOEDC Error on Read 9
80 87 IOEDC Error on Write 9
80 88 Host Parity Check Failed 9
80 89 IOEDC Error on Read Detected by Formatter 9
00
Log Exception
80 8A Host FIFO Parity Error detected by Common Buffer 9
80 8B Host FIFO Parity Error detected by frame buffer logic 9
80 8C Host Data Frame Buffer Parity Error 9
81 00 Reassign Power—Fail Recovery Failed
81 00 LA Check Error, LCM bit = 0 4
81 00 LA Check Error B
B4 00 Unreported Deferred Errors have been logged on log page 34h 6
[1] Can be supported, but is a factory installed option.
SCSI Commands Reference Manual, Rev. A 49
50 SCSI Commands Reference Manual, Rev. A
3.0 Command Refere nce
This clause describes the commands supported by Seagate Disc Drives.
Commands that have been supported prior to this manual being produced and that are now indicated as obso-
lete will be described in this clause as obsolete. However, a description will be provided for such commands.
Commands that have been declared obsolete by the T10 committee and were never supported by Seagate are
not included in this manual. Commands that have not been supported in the past, but may be supported in the
near future will be included in this manual.
This clause contains infor mation about the commands used by Seagate Parallel SCSI, Fibre Channel , and
Serial Attached SCSI disc drives. This clause is organized to provide rapid access to command information.
Two types of commands are supported by the drive: commands for all devices; and commands for direct
access devices. The ind iv id ual Pr oduc t Man ual s for eac h Se aga te mod el dr ive li s t the Comm and s and parameter pages that the particular drive supports.
Commands sorted by command name
OP
Command name
CHANGE DEFINITION 40h x [2] 3.1
COMPARE 39h x [2] 3.2
COPY 18h x [2] 3.3
COPY AND VERIFY 3Ah x [2] 3.4
FORMAT UNIT 04h x x 3.5
INQUIRY 12h x x 3.6
LOCK-UNLOCK CACHE (10) 36h x x 3.7
LOCK-UNLOCK CACHE (16) 92h x x 3.8
LOG SELECT 4Ch x x 3.9
LOG SENSE 4Dh x x 3.10
MODE SELECT (6) 15h x x 3.11
MODE SELECT (10) 55h x x 3.12
MODE SENSE (6) 1Ah x x 3.13
MODE SENSE (10) 5Ah x x 3.14
PERSISTENT RESERVE IN 5Eh x 3.15
PERSISTENT RESERVE OUT 5Fh x 3.16
READ (6) 08h x x 3.19
READ (10) [3] 28h x x 3.20
code
[1]
Command type Length
All
devices
Direct
access
devices
6
byte10byte12byte16byte32byte
clause
Reference
SCSI Commands Reference Manual, Rev. A 51
OP
Command name
READ (12) A8h x x 3.21
READ (16) 88h x x 3.22
READ (32) 7Fh/0009h x x 3.23
READ BUFFER 3Ch x x 3.24
READ CAPACITY (10) 25h x x 3.25
READ CAPACITY (16) 9Eh/10h x x 3.26
READ DEFECT DATA (10) 37h x x 3.27
READ DEFECT DATA (12) B7h x x 3.28
READ LONG (10) 3Eh x x 3.29
READ LONG (16) 9Eh x x 3.30
REASSIGN BLOCKS 07h x x 3.31
RECEIVE DIAGNOSTIC RESULTS 1Ch x x 3.32
RELEASE (6) 17h x [2] x 3.33
RELEASE (10) 57h x [2] x 3.34
REPORT DEVICE IDENTIFIER A3h/05h x x 3.35
REPORT LUNS A0h x 3.36
REQUEST SENSE 03h x x 3.37
RESERVE (6) 16h x [2] x 3.38
RESERVE (10) 56h x [2] x 3.39
REZERO UNIT 01h x [2] x 3.40
SEEK (6) 0Bh x [2] x 3.41
SEEK EXTENDED (10) 2Bh x x 3.42
SEND DIAGNOSTIC 1Dh x x 3.43
SET DEVICE IDENTIFIER A4h/06h x x 3.44
START/STOP UNIT 1Bh x x 3.45
SYNCHRONIZE CACHE (10) 35h x x 3.46
SYNCHRONIZE CACHE (16) 91h x x 3.47
TEST UNIT READY 00h x x 3.48
VERIFY(10) 2Fh x x 3.49
VERIFY (12) AFh x x 3.50
VERIFY (16) 8Fh x x 3.51
VERIFY (32) 7Fh/000Ah x x 3.52
WRITE (6) 0Ah x x 3.53
WRITE (10) 2Ah x x 3.54
WRITE (12) AAh x x 3.55
WRITE (16) 8Ah x x 3.56
WRITE (32) 7Fh/000Bh x x 3.57
WRITE AND VERIFY (10) 2Eh x x 3.58
WRITE AND VERIFY (12) AEh x x 3.59
WRITE AND VERIFY (16) 8Eh x x 3.60
code
[1]
Command type Length
Direct
All
devices
access
devices
6
byte10byte12byte16byte32byte
clause
Reference
52 SCSI Commands Reference Manual, Rev. A
OP
Command name
WRITE AND VERIFY (32) 7Fh/000Ch x x 3.61
WRITE BUFFER 3Bh x x 3.62
WRITE LONG 3Fh x x 3.63
WRITE LONG (16) 9Fh/11h x x 3.64
WRITE SAME (10) 41h x x 3.65
WRITE SAME (16) 93h x x 3.66
WRITE SAME (32) 7Fh/000Dh x x 3.67
code
[1]
Command type Length
Direct
All
devices
access
devices
6
byte10byte12byte16byte32byte
clause
Reference
[1] Command Operation Code a one byte hexidecimal number between 00h and FF hex.
[2] Command has been decla red obsolete by the T10 comm ittee. Howev er, it is included because it may be
implemented on some products.
[3] Formerly called Read Extended.
SCSI Commands Reference Manual, Rev. A 53
3.1 CHANGE DEFINITION command
This command has been declared obso lete by the T10 committee. However, it is included because it
may be implemented on some products.
The CHANGE DEFINITION com mand (see table 29) is used to modify the operating de finition of the device
server(s) with respect to commands from the sending initiator or with respect to commands from all initiators.
Table 29 — CHANGE DEFINITION command
Bit
Byte
0 OPERATION CODE (40h)
3
4
5
6
7
8
9
10
11
7 65432 1 0
Reserved
Reserved SAVE
Reserved DEFINITION PARAMETER
Reserved
Reserved
Reserved
Reserved
PARAMETER DATA LENGTH
CONTROL
If reservations are active , they sh all affect the ex ecution of th e CHAN GE DEFINI TION com mand as follows. If
the SCSI device does not allow different operating definitions for each initiator, a reservation conflict shall occur
when a CHANGE DEFINITION comma nd is recei ved from an in itiator othe r than the one holding a logica l unit
reservation. If any initiator has an extent or element reservation on an SCSI device, no other initiator may affect
the operating definition of the initiator holding the reservation by use of the CHANGE DEFINITION command.
A save contro l bit (SAVE) of zero indic ates that the device serv er shall not save the ope rating definition. A
Save bit of one indicates that the device server shall save the operating definition in non-volatile memory.
The definition parameter field is defined in table 14.
Table 30 — Definition parameter field
Value
Meaning of definition parameter
00h Use current operating definition
03h SCSI-2 operating definition
04h SCSI-3 operating definition
01 - 02h Reserved for historical uses
05 - 3Eh Reserved
3Fh Manufactu rer defa ul t defini ti on
40 - 7Fh Vendor specific
54 SCSI Commands Reference Manual, Rev. A
The current operating definition parameter values establish operating definitions compatible with the applicable
SCSI standard. Definition s suppor ted by a n SCSI devic e are retu rned in th e implemente d operati ng definit ion
page (see 8.4.4 in SCSI-3 Primary Commands Rev 11).
The parameter data length fiel d specifies the length in by tes of the parameter data that shall be tran sferred
from the application client to the dev ice serv er. A parameter data length of zero indicates that no data shall be
transferred. This condition shall not be considered as an error. Parameter data length values greater than zero
indicate the number of bytes of parameter data that shall be transferred.
The parameter data is vendor-specific.
Note. 1 The parameter data may be used to specify a password to validate an operating definition
change.
The CHANGE DEFINITION command causes one of the operating definition modifications listed below:
(a) Change the operating definition of a logical unit relative to the initiator that issued the command: In this
case, the target is capable of maintaining a separate operating definition for each logical unit relative to
each initiator in the system;
(b) C hange the operating defini tion of all logical uni ts in the target relative to the initi ator that issued the
command: In this case, the target is capable of maintaining a unique operating definition, for each initiator in the system, that applies to all logical units in the target;
(c) Change the ope rating defi nition of a logi cal unit r elative to a ll initiators i n the system: In thi s case, the
target is capable of maintaining a separate operati ng defi ni tio n for each logi ca l uni t relati ve to all in iti ators in the system; or
(d) C ha nge the op er ating d e fini tion of all logical units in th e targ et r elati v e to al l ini tia tor s in th e sys te m: I n
this case, the target is capable of maintaining only one operating definition.
Note. 2 This standard does not provide a direct means to determine which of the above four methods has
been implemented. A n indirect means o f determining which met hod is implemented e xists in that
the device server is required to inf orm affecte d initiators of operating definition ch ang es via the unit
attention condition.
Note. 3 The modific ati ons lis ted c) and d) abov e ma y res ult i n inco m patibilities if other initiators are us in g
a different SCSI version.
The operating defini ti on i s mod ifi ed after su cc es sfu l com pl etio n of the command. The application client sh oul d
verify the new operating defi nition by issuing an INQUIRY command requesting the implemented operating
definition page (see 8.4.1 in SCSI -3).
Note. 4 The meth od of changing the o perating definition is vendor-spec ific. Some implem entations may
require that the target’s operating mode be reinitialized as if a power-up or hard reset had occurred.
Other implementations may modify only those operating definitions that are affected by the
CHANGE DEFINITION command.
If the CHANGE DEFINIT ION command is n ot executed successful ly for any reason, the operating definitio n
shall remain the same as it was before the CHANGE DEFINITION command was attempted. If it is impossible
to return to the previous operating definition, a unit attention condition shall be generated.
Note. 5 The pres ent operating defini tion of the target may a lways be interro gated through the I NQUIRY
command. When an SCSI- 3 target has its oper ating defin ition c hanged to an older SCS I opera ting
definition, certain cha nges are needed to promote compatibility with preexisting ol der SCSI initiators.
After a power-on condition or a hard reset condition, the target shall set i ts initial operating definition of the
device server(s) to the las t saved value (if sav ing is implemen ted), or its default value ( if saving is not implemented).
SCSI Commands Reference Manual, Rev. A 55
3.2 COMP ARE command
Obsolete. If received, a CHECK CONDITION status is sent.
3.3 COPY command
Obsolete. If received, a CHECK CONDITION status is sent.
3.4 COPY AND VERIFY command
Obsolete. If received, a CHECK CONDITION status is sent.
56 SCSI Commands Reference Manual, Rev. A
3.5 FORMA T UNIT command
3.5.1 FORMAT UNIT command overview
The FORMAT UNIT command (see table 31) requests that the device server format the mediu m into application client accessible logical blocks as specified in the number of blocks and block length values received in the
last mode parameter b loc k descriptor (see 4.3.4 ) in a MO DE SE LECT c om man d (s ee SP C- 4). In ad dition, the
device server may c ertify the medium and crea te control structures fo r the management of the med ium and
defects. The degree that the medium is altered by this command is vendor-specific.
If a device server receives a F ORMAT UNIT command before rece iving a MODE SELECT command wi th a
mode parameter block descriptor the device serv er shall use t he number of blocks and b lock length a t which
the logical unit is cu rrently forma tted (i.e., no change i s made to the numb er of bloc ks and the blo ck length of
the logical unit during the format operation).
Table 31 — FORMAT UNIT command
Bit
Byte
0 OPERATION CODE (04h)
1
2 Vendor Specific
3 Obsolete
4
5 CONTROL
7 6 5432 1 0
FMT-
PINFO
RTO_REQ LONG-
LIST
FMTDATA CMPLIST DEFECT LIST FORMAT
The simplest form o f the FORM AT UNIT command (i.e., a FORM AT UNIT command with no parameter d ata)
accomplishes medium formatting with little application client control over defect management. The device
server implementation deter mine s the degr ee of defec t manag ement tha t is to be performe d. Addi tional for ms
of this command incr ease the app lication client's contr ol over defe ct managem ent. The ap plication c lient may
specify:
a) defect list(s) to be used;
b) defect locations;
c) that logical unit certification be enabled; and
d) exception handling in the event that defect lists are not accessible.
While performing a format operation, the device server shall respond to commands attempting to enter into the
task set except INQUIRY comm ands, REPORT LUNS commands, an d REQUEST SENSE commands with
CHECK CONDITION status with the sense key set to NOT READY and the additional sense code set to LOGICAL UNIT NOT REA DY, FORMAT IN PROGRESS. Handling of comma nds a lready in th e task s et is ve ndorspecific.
The PROGRESS INDICATION field in parameter data returned in response to a REQUEST SENSE command
(see SPC-4) may be used by the application client at any time during a format operation to poll the logical unit’s
progress. While a format op eration is in prog ress unl ess an error has occurred, a de vice server shall respon d
to a REQUEST SENSE command by returning parameter data containing sense data with the sense key set to
NOT READY and the additional sense code set to LOGICAL UNIT NOT READY, FORMAT IN PROGRESS
with the sense key specific bytes set for progress indication (see SPC-4).
SCSI Commands Reference Manual, Rev. A 57
FMTPINFO (Format Protection Information) bit
A format protection information (FMTPINFO) bit (see table 36) specifies if the device server enables or disables the use of
protection informatio n.
RTO_REQ (Reference Tag Own Request) bit
The reference tag own request (RTO_REQ) bit (see table 36) specifies whether the application client or the device server
has ownership of the LOGICAL BLOCK REFERENCE TAG field in protection information.
Following a successful fo rmat, the P_TYPE fi eld in the READ CAPACITY (16) parameter data (see 1.6.2) indicates the typ e
of protection currently in effect on the logical unit.
When protection information is written during a FORMAT UNIT command (i.e., the FMTPINFO bit is set to one) protection
information shall be written to a default value of FFFFFFFF_FFFFFFFFh.
LONGLIST bit
0 A LONGLIST bit set to zero spe cifie s that th e p aram eter li st, if an y, contains a short parameter lis t heade r as def ined
in table 34.
1 A LONGLIST bit set to one specifies that the parameter list, if any, contains a long parameter list header as defined
in table 35. If the FMTDATA bit is set to zero, the LONGLIST bit shall be ignored.
FMTDAT A (Format Dat a )
0 A format data (FMTDATA) bit set to zero specifies that no parameter list be transferred from the data-out buffer.
1 A FMTDATA bit set to one specifies that the FORMAT UNIT parameter list (see table 33) shall be transferred from
the data-out buffer. The parameter list consists of a parameter list header, followed by an optional initialization pattern descriptor, followed by an optional defect list.
CMPLST (Complete List)
0 A complete list (CMPLST) bit set to zero specifies that the defect list included in the FORMAT UNIT parameter list
shall be used in an addition to the existing list of defects. As a result, the device server shall construct a new GLIST
that contains:
a) the existing GLIST;
b) the DLIST, if it is sent by the application client; and
c) the CLIST, if certification is enabled (i.e., the device server may add any defects it detects during the format
operation).
1 A CMPLST bit set to one specifi es th at th e defect list included in th e FO RMAT UNIT parameter list is a complete lis t
of defects. Any existing defect list except the PLIST shall be ignored by the device server. As a result, the device
server shall construct a new GLIST that contains:
a) the DLIST, if it is sent by the application client; and
b) the CLIST, if certification is enabled (i.e., the device server may add any defects it detects during the format
operation).
Note. If the FMTDATA bit is set to zero, the CMPLIST bit shall be ignored.
DEFECT LIST FORMAT field
The DEFECT LIST FORMAT field specifies the forma t of the addr ess descri ptors in the defect list i f the FMTDATA bit is set to one (see table 32).
Table 32 defines the address descriptor usage for the FORMAT UNIT command.
58 SCSI Commands Reference Manual, Rev. A
Table 32 — FORMAT UNIT command address descriptor usage
Field in the FORMAT UNIT CDB
FMTDATA CMPLST
0 Any 000B Not available M
10
11 O
10
11 O
10
11 O
10
1 1 O See and
10
1 1 O See and
DEFECT LIST
FORMAT
000B
(short block)
011B
(long block)
100b
(bytes
from
index)
DEFECT LIST
LENGTH
parameter list header
field in the
Zero O
Nonzero
Zero
Nonzero
Zero
Nonzero
Comments
a
Type
Vendor-specific defect
O
O
O
O
O See and
O See and
See
See
See
See
See
See
See
See
f
information
b
and
b
and
c
and
b
and
b
and
b
and
c
and
c
and
d
e
d
e
d
e
d
e
10
1 1 O See and
10
1 1 O See and
1 0 110b
11 O
a
M = implementation is mandatory. O = implementation is optional.
b
No DLIST is included in the parameter list.
c A DLIST is included in the parameter list. The device server shall add the DLIST defects to the new GLIST.
d The device server shall add existing GLIST defects to the new GLIST (i.e., use the existing GLIST).
e
The device server shall not add existing GLIST defects to the new GLIST (i.e., discard the existing GLIST).
f All the options described in this table cause a new GLIST to be created during processing of the FORMAT UNIT command as described in the text.
101b
(physical
sector)
(vendor
specific)
All others Reserved.
Zero
Nonzero
Vendor specific O
O See and
O See and
SCSI Commands Reference Manual, Rev. A 59
3.5.2 FORMAT UNIT parameter list
3.5.2.1 FORMAT UNIT parameter list overview
Table 33 defines the FORMAT UNIT parameter list.
Table 33 — FORMAT UNIT parameter list
Bit
Byte
0 to 3 or
0 to 7
PARAMETER LIST HEADER field
7 6 5432 1 0
Parameter List Header (see table 34 or table 35 in 3.5.3)
INitialization Pattern Descriptor (if any) (see table 37, in 3.5.4)
Defect List (if any)
The PARAMETER LIST HEADER is defined in 3.5.3.
INITIALIZATION PATTERN DESCRIPTOR field
The INITIALIZATION PATTERN DESCRIPTOR, if any, is defined in 3.5.4.
DEFECT LIST field
The DEFECT LIST, if any, contains address de scriptors (see Table 32 —) each specify ing a location on th e
medium that the device server shall exclude from the application client accessible part. This is called the
DLIST.
3.5.3 Parameter list header
The parameter list header s (see table 34 and table 35) provide several opti onal format control parameters.
Device servers th at implement these headers provide the applicatio n client addi tional control ove r the use of
the four defect sources, and the format operation. If the ap plication client attempts to se lect any function not
implemented by t he device se rver, the device server s hall termin ate the comm and with CHEC K CONDITION
status with the sense key set to ILLEGA L REQUEST and t he additional s ense code se t to INVALID FIELD IN
PARAMETER LIST.
60 SCSI Commands Reference Manual, Rev. A
The short parameter list h eader (see table 34) is used if the LONGLIST bit is set to zero in the FORMAT UNIT
CDB.
Table 34 — Short parameter list header
Bit
76543210
Byte
0
1
FOV DPRY DCRT STPF IP Obsolete IMMED Vendor
Reserved
PROTECTION FIELDS USAGE
2 (MSB) DEFECT LIST LENGTH
3 (LSB)
The long parameter list header (see table 35) is used if the
LONGLIST bit is set to one in the FORMAT UNIT
CDB.
Table 35 — Long parameter list header
Bit
Byte
0
1
2 Reserved
76543210
Reserved
PROTECTION FIELDS USAGE
FOV DPRY DCRT STPF IP Obsolete IMMED Vendor
specific
specific
3 Reserved
4 (MSB) DEFECT LIST LENGTH
7 (LSB)
The PROTECTION FIE LD USAGE field in combination with th e FMTPINFO bit and the RTO_REQ bit (see
table 36) specifies the requested protection type (see SBC-3).
Table 36 — FMTPINFO bit, RTO_REQ bit, and PROTECTION FIELDS USAGE field
Device server indication Application client specification
f
f
Description
c
(see SBC-3) resulting
d
being set to
SPT
a
PROTECT
b
FMTPINFO RTO_REQ
PROTECTION
FIELD USAGE
xxxb 0 0 0 000b The logical unit shall be formatted to
type 0 protection
in the RTO_ENABLE field
000b.
xxxb 0 0 0 >000b Illegal
e
xxxb 0 0 1 xxxb Illegal
xxxb 0 1 x xxxb Illegal
SCSI Commands Reference Manual, Rev. A 61
Table 36 — FMTPINFO bit, RTO_REQ bit, and PROTECTION FIELDS USAGE field
Device server indication Application client specification
Description
SPT
a
PROTECT
b
FMTPINFO RTO_REQ
PROTECTION
FIELD USAGE
xxxb 1 0 0 000b The logical unit shall be formatted to
type 0 protection
in the RTO_ENABLE field
c
(see SBC-3) resulting
d
being set to
000b.
xxxb 1 0 0 >000b Illegal
xxxb 1 0 1 xxxb Illegal
000b
001b
011b
1
1 0 000b
e
f
The logical unit shall be formatted to
type 1 protection
in the RTO_ENABLE field
g
(see SBC-3) resulting
d
being set to
000b.
000b
001b
1
1 0 >000b
Illegal
e
011b
000b 1
001b 1
1 1 xxxb
1 1 000b
f
Illegal
The logical unit shall be formatted to
g
type 2 protection
in the RTO_ENABLE field
(see SBC-3) resulting
d
being set to
001b.
001b 1
011b 1
1 1 >000b
1 1 000b
Illegal
Illegal
e
e
011b 1
1 1 001b
The logical unit shall be formatted to
g
type 3 protection.
ing in the RTO_ENABLE field
(see SBC-3) result-
d
being
set to 010b.
011b 1 1 1 >001b Illegal
e
010b 1 1 x xxxb Reserved
1xxb 1 1 x xxxb Reserved
a See the Extended INQUIRY Data VPD page (see SPC-4) for the definition of the spt field.
b See the standard INQUIRY data (see SPC-4) for the definition of the protect bit.
c The device server shall format the medium to the block length specified in the mode parameter block descriptor of the
mode parameter header (see SPC-4).
d See the READ CAPACITY command (see 3.25.1) for the definition of the rto_enable field.
e The device server shall terminate the command with CHECK CONDITION status with the sense key set to ILLEGAL
REQUEST and the additional sense code set to INVALID FIELD IN PARAMETER LIST.
f The device server shall terminate the command with CHECK CONDITION status with the sense key set to ILLEGAL
REQUEST and the additional sense code set to INVALID FIELD IN CDB.
g The device server shall format the medium to the block length specified in the mode parameter block descriptor of the
mode parameter header plus eight (e.g., if the block length is 512, then the formatted block length is 520). Following a
successful format, the prot_en bit in the READ CAPACITY (16) parameter data (see 3.26.1) indicates whether protection
information (see SBC-3) is enabled.
62 SCSI Commands Reference Manual, Rev. A
FOV (Format Options Valid) bit
0 A format options valid (FOV) bit set to zero specifies that the device server shall use its default settings for the
DPRY, DCRT, STPF, and IP bits. If the FOV bit is set to zero, the application client shall set these bits to zero. If the
FOV bit is set to ze ro and any of the other bits listed in this paragraph are not set to zero, t he device server s hal l terminate the command with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and the additional sense code set to INVALID FIELD IN PARAMETER LIST.
1 A FOV bit set to one specifies that the device server shall examine the values of the DPRY, DCRT, STPF, and IP
bits. When the FOV bit is set to one, the DPRY, DCRT, STPF, and IP bits are defined as follows.
DPRY (Disable Primary) bit
0 A disable primary (DPRY) bit set to zero spec ifi es that the device server shall not use p a rt s of the me dium identified
as defective in the PLIST for appli cation client accessib le lo gic al bloc ks . If the de vi ce s erv er is no t able to loc ate the
PLIST or it is not able to determine whether a PLIST exists, it shall take the action specified by the STPF bit.
1 A DPRY bit set to one specifies that the device server shall not use the PLIST to identify defective areas of the
MEDIUM. The PLIST shall not be deleted.
DCRT (disable certification) bit
0 A disable certification (DC RT) bit s et to zero spe cifies that the dev ice server sh all perfo rm a vendo r-speci fic med ium
certification operation to generate a CLIST.
1 A DCRT bit set to one specifies that the device server shall not perform any vendor-specific medium certification
process or format verification operation.
STPF bit
The stop format (STPF) bit controls the behavior of the device server if one of the following events occurs:
a) The device server h as been re queste d to us e the PLI ST (i. e., the DPRY bit is set to zero) or th e GLIST (i.e., th e
CMPLST bit is set to zero) and the device server is not able to locate the list or determine whether the list exists;
or
b) The device server h as been re queste d to us e the PLI ST (i. e., the DPRY bit is set to zero) or th e GLIST (i.e., th e
CMPLST bit is set to zero), and the device server encounters an error while accessing the defect list.
STPF (Stop Format) bit
0 A STPF bit set to zero specifies that, if one or both of these events occurs, the device server shall continue to pro-
cess the FORMAT UNIT command. The device server shall return CHECK CONDITION status at the completion of
the FORMAT UNIT comma nd w ith the se ns e k ey se t to RE COVERED ERRO R a nd t he a dd itio na l s ens e c od e set to
either DEFECT LIST NOT FOUND if the condition described in item a) occurred, or DEFECT LIST ERROR if the
condition described in item b) occurred.
1 A STPF bit set to one specifies that, if one or both of these events occurs, the device server shall terminate the
FORMAT UNIT command with CHECK CONDITION status and the sense key shall be set to MEDIUM ERROR with
the additional sen se co de s et t o ei ther DEFECT LIST NOT FOUND i f the co ndi tio n de sc rib ed i n item a) occurred, or
DEFECT LIST ERROR if the condition described in item b) occurred.
Note. The use of the F MTDATA bit, the CMPLST bit, and the paramete r list header al low the appli cation
client to control the sou rce of the defect lists used by the FORMAT UNIT command. Setting the
DEFECT LIST LENGTH field to zero allows the application clie nt to control the use of PLIST and
CLIST without having to specify a DLIST.
IP (initialization pattern) bit
An initialization pattern (IP) bit set to zero specifies that an initialization pattern descriptor is not included and that
0
the device server shall use its default initialization pattern.
1 An IP bit set to one specifies that an initialization pattern descriptor (see 3.5.4) is included in the FORMAT UNIT
parameter list followi ng the p ara me ter lis t head er.
SCSI Commands Reference Manual, Rev. A 63
IMMED (Immediate) bit
0 An immediate (IMMED) bit set to zero specifies that the device server shall return status after the format operation
has completed.
1 An IMMED bit value set to one specifies that the device server shall return status after the entire parameter list has
been transferred.
DEFECT LIST LENGTH field
The DEFECT LIST LENGTH field specifies the total length in bytes of the defect list (i.e., the address descriptors) that follows and does not include the initialization pattern descriptor, if any. The formats for the address descriptor(s) are shown in
Table 32 —.
Short block format address descriptors and long block format address descriptors should be in ascending
order. Bytes from index format address descriptor s and physi cal sector format ad dress desc riptors shall be in
ascending order. More than one physical or l ogical block may be affected by eac h address descriptor. If the
address descriptor s a re not i n th e required order, the device server shall ter minate the command with CH ECK
CONDITION status with the sense key set to ILLEGAL REQUEST and the additional sense code set to
INVALID FIELD IN PARAMETER LIST.
3.5.4 Initialization pattern descriptor
The initialization pattern de scriptor specifies that the device server initial ize logical blocks to a spec ified pattern. The initializa tion pattern descriptor (see table 37) is sent to the dev ice server as part of the FORMAT
UNIT parameter list.
Table 37 — Initialization pattern descriptor
Bit
Byte
0 IP MODIFIER SI Reserved
1 INITIALIZATION PATTERN TYPE
2 (MSB) INITIALIZATION PATTERN LENGTH (N - 3)
3 (LSB)
4 INITIALIZATION PATTERN
N
76543210
64 SCSI Commands Reference Manual, Rev. A
IP MODIFIER (Initilization Pattern Modifier) field
The initialization pattern modifier (IP MODIFIER) field (see table 38) specifies the type and location of a header that modifies the initialization pattern.
Table 38 — Initialization pattern modifier (IP MODIFIER) field
Code
00b No header. The device server shall not modify the initialization pattern.
01b
10b
11b Reserved.
SI (Security Initialize) bit
Description
The device server shall overwrite the initialization pattern to write the LBA in the first four bytes of each
logical block. The LBA
bytes, the least significant four bytes shall be written ending with the least significant byte.
The device server shall overwrite the initialization pattern to write the LBA in the first four bytes of each
physical block contained within the logical block. The lowest numbered logical block or part thereof that
occurs within the physical block is used. The LBA
LBA is larger than fou r bytes the lea st signi ficant fou r bytes sh all be wri tten endin g with the le ast signi ficant
byte.
shall be written with the most significant byte first. If the LBA is larger than four
shall be written with the mo st sign ificant byte first. If the
A security initialize (SI) bit set to one specifies that the device server shall attempt to write the initialization pattern to all areas o f the me diu m i nc lu din g th os e th at m ay ha ve bee n reassigned (i.e., are in a de fec t l is t). A n S I
bit set to one shall take precedence over any other FORMAT UNIT CDB field. The initialization pattern shall be
written using a secu rity er asure wr ite tech nique. A ppli cation clie nts may choo se to u se thi s comman d mu ltiple
times to fully erase the previous data. Such security erasure write technique procedures are outside the scope
of the standard. The exact requiremen ts placed on the security erasure write tech nique are vendor-specific.
The intent of the security erasure write is to render any previous user data unrecoverable by any analog or digital technique.
0
An SI bit set to zero specifies that the device server shall initialize the application client accessible part of the
medium. The device server is not required to initialize other areas of the medium. However, the device server shall
format the medium as defined in the FORMAT UNIT command.
1 When the SI bit is set to one, the device server need not write the initialization pattern over the header and other
header and other parts of the medium not previously accessible to the application client. If the device server is
unable to w rite over an y part of the medium that i s currently accessible to the appli cation clie nt or may be made
accessible to the ap pli ca tio n c lie nt i n the futu re (e .g., by c le ari ng the defect list), it sha ll t erm ina te the command with
CHECK CONDITION status with the sense key set to MEDIUM ERROR and the additional sense code set to the
appropriat e value for the condition. The d evice server sha ll attempt to r ewrite all remai ning parts of the me dium
even if some parts are not able to be rewritten.
SCSI Commands Reference Manual, Rev. A 65
INITIALIZATION PATTERN TYPE field
The INITIALIZATION PATTERN TYPE field (see table 39) specifies the type of pattern the de vice se rver shall
use to initialize eac h l ogi ca l bl oc k within the application cli ent ac ce ss ib le par t of th e me diu m. A ll bytes wit hin a
logical block sha ll be written with the initi alization pattern. The initializa tion pattern i s modified b y the I P
FIER field as described in table 38.
MODI-
Table 39 — INITIALIZATI ON PATTERN TYPE field
Code
00h Use a default initialization p at tern
01h Repeat the pattern specified in the INITIALIZATION PATTERN field as required to fill the logical
02h - 7Fh Reserved
80h - FFh Vendor-specific
a
If the INITIALIZATION PATTERN LENGTH field is not set to zero, the device server shall terminate the
Description
b
block
a
command with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and the
additional sense code set to INVALID FIELD IN PARAMETER LIST.
b
If the INITIALIZATION PATTERN LENGTH field is set to zero, the device server shall terminate the
command with CHECK CONDITION status with the sense key set to ILLEGAL REQUEST and the
additional sense code set to INVALID FIELD IN PARAMETER LIST.
INITIALIZATION PATTERN LENGTH field
The INITIALIZATION PATTERN LENGTH field specifies the number of bytes con tained in the INITIALIZATION
PATTERN field. If t he in itiali zati on pattern length exce eds t he cu rre nt blo ck len gth the devi ce s erver sha ll term i-
nate the command with CHECK CONDITION s tatus with the sense key set to ILLEGAL REQUEST and the
additional sense code set to INVALID FIELD IN PARAMETER LIST.
INITIALIZATION PATTERN field
The INITIALIZATION PATTERN field specifies the initialization pattern. The initialization pattern is modified by
the IP MODIFIER field.
3.5.5 Address descriptor formats
3.5.5.1 Address descriptor formats overview
This subclause des cribes the address des criptor formats used in the FOR MAT UNIT comma nd, the READ
DEFECT DATA commands (see 3.27 and 3.28), and the Translate Address diagnostic pages (see 4.1.3) of the
SEND DIAGNOSTIC command and the RECEIVE DIAGNOSTIC RESULTS command.
The format type of an address descriptor is specified with:
a) the DEFECT LIST FORMAT field in the CDB, for the FORMAT UNIT command and the READ DEFECT DATA
commands;
b) the SUPPLIED FORMAT field, for the Translate Address diagnostic pages; or
c) the TRANSLATE FORMAT field, for the Translate Address diagnostic pages.
66 SCSI Commands Reference Manual, Rev. A
Table 40 defines the types of address descriptors.
Table 40 — Address descriptor formats
Format type
000b Short block format address descriptor 3.5.5.2
011b Long block format address descriptor 3.5.5.3
100b Bytes from index format address descriptor 3.5.5.4
101b Physical sector format address descriptor 3.5.5.5
110b Vendor-specific
All others Reserved
Description
Reference
3.5.5.2 Short block format address descriptor
A format type of 000b specifies the short block format address descriptor defined in table 41.
Table 41 — Short block format address descriptor (000b)
Bit
Byte
0 (MSB) SHORT BLOCK ADDRESS
3 (LSB)
76543210
SHORT BLOCK ADDRESS field
For the FORMAT UNIT command, the SHORT BLOCK ADDRESS field contains the fou r-byte LBA o f a defe ct. F or
the READ DEFECT DATA commands, the
value. For the Translate Address diagnostic pages, the
SHORT BLOCK ADDRESS fi eld contains a vendor-specif ic four-byte
SHORT BLOCK ADDRESS field contains a four-byte LBA or
a vendor-specific four byte value that is greater than the capacity of the medium.
3.5.5.3 Long block format address descriptor
A format type of 011b specifies the long block format address descriptor defined in table 42.
Table 42 — Long block format address descriptor (011b)
Bit
Byte
0 (MSB) LONG BLOCK ADDRESS
7 (LSB)
LONG BLOCK ADDRESS field
76543210
For the FORMAT UNIT command, the LONG BLOCK ADDRESS field contains the eight-by te logical block
address of a defect. For th e READ DE FECT DATA commands, the LONG BLOCK ADDR ESS fi eld co ntains a
vendor-specific eight-byt e value. For the Translate Address diagn ostic pages, the LONG BL OCK ADDRESS
field contains a four-byte LBA or a vendor-specific four byte value that is greater than the capacity of the
medium.
SCSI Commands Reference Manual, Rev. A 67
3.5.5.4 Bytes from index format address descriptor
A format type of 100b specif ies the byte s from index address des criptor define d in table 43. For the FORMAT
UNIT command and the REA D DEFECT DATA comman ds, this descriptor specifies th e location of a defect
that is either the l ength of one track or is no m ore than eight bytes long . For the Translate Addr ess di agnos tic
pages, this descriptor specifies the location of a track or the first byte or last byte of an area.
Table 43 — Bytes from index format address descriptor (100b)
Bit
Byte
0 (MSB) CYLINDER NUMBER
2 (LSB)
3 HEAD NUMBER
4 (MSB) BYTES FROM INDEX
7 (LSB)
CYLINDER NUMBER field
76543210
The CYLINDER NUMBER field contains the cylinder number.
HEAD NUMBER field
The HEAD NUMBER field contains the head number.
BYTES FROM INDEX field
The BYTES FROM INDEX field contains the number of bytes from the index (e.g., from the start of the track) to the location
being described. A BYTES FROM INDEX field set to FFFFFFFFh specifies that the entire track is being described.
For sorting bytes fr om ind e x format add re ss des cr ipto r s, the c ylin der nu mbe r is the m os t s ign ifica nt part of th e
address and the bytes from ind ex is the least sign ificant part of the addr ess. More than one logical blo ck may
be described by this descriptor.
68 SCSI Commands Reference Manual, Rev. A
3.5.5.5 Physical sector format address descriptor
A format type of 101b specifies the physical sector address descriptor defined in table 44. For the FORMAT
UNIT command and the READ DEFECT DATA commands, this descriptor specifies the location of a defect
that is either the length of one track or the length of one sector. For the Translate Address diagnostic pages,
this descriptor specifies the location of a track or a sector.
T able 44 — Physical sector format address descriptor (101b)
Bit
Byte
0 (MSB) CYLINDER NUMBER
2 (LSB)
3 HEAD NUMBER
4 (MSB) SECTOR NUMBER
7 (LSB)
CYLINDER NUMBER field
The CYLINDER NUMBER field contains the cylinder number.
HEAD NUMBER field
The HEAD NUMBER field contains the head number.
SECTOR NUMBER field
The SECTOR NUMBER field contains the sector number. A SECTOR NUMBER field set to FFFFFFFFh specifies that the
entire track is being described.
76543210
For sorting physica l sector format add ress descriptors , the cylinder numb er is the most signi ficant part of the
address and the sector numb er is the lea st s ig nifi cant part of the add re ss . More th an one logical block may be
described by this descriptor.
SCSI Commands Reference Manual, Rev. A 69
3.6 INQUIRY command
3.6.1 INQUIRY command introduction
The INQUIRY command (see table 45) requests that information reg arding the logical unit and SCS I target
device be sent to the application clie nt.
Table 45 — INQUIRY command
Bit
Byte
0
1
2
3
4
5
EVPD (Enable Vital Product Data) bit
76543210
OPERATION CODE (12h)
Reserved Obsolete
Formerly
CMDDT
P AGE CODE
(MSB) ALLOCATION LENGTH
CONTROL
EVPD
(LSB)
An enable vital product data (EVPD) bit set to one specifies that the device server shall return the vital product
data specified by the PAGE CODE field (see 3.6.4).
0
If the EVPD bit is set to zero, the device server shall return the standard INQUIRY data (see 3.6.2). If the PAGE
CODE field is not set to zero when the EVPD bit is set to zero, the com mand sh all be te rmina ted with CHECK CONDITION status, with the sense key set to ILLEGAL REQUE S T, and the additional sense code set to INVALID FIELD
IN CDB.
1 When the EVPD bit is set to one, the PAGE CODE field specifies which page of vital product data information the
device server shall return (see 4.4).
CMDDT (Command Support Data) bit
This bit has been declared Obsolete by T10. See SBC-2 for a description of this bit.
If both the EVPD and CMDDT bits are one, the target shall return CHECK CONDITION status with the sense key set to
ILLEGAL REQUEST and an additional sense code of Invalid Field in CDB. When the EVPD bit is one, the Page or OPERATION CODE field specifies which page of vital product data information the target shall return.
ALLOCATION LENGTH field
The ALLOCA T ION LENGTH field is defined in 2.1.4.5. If EVPD is set to zero, the a llocatio n leng th sho uld be at l east f ive, so
that the ADDITIONAL LENGTH field in the parameter data (see 3.6.2) is returned. If EVPD is set to one, the allocation
length should be should be at least four, so that the PAGE LENGTH field in the parameter data (see 4.4) is returned.
In response to an INQUI RY comma nd r ec ei ve d by an in co rrec t l ogical unit, the SCSI target devi ce s ha ll ret ur n
the INQUIRY data with the perip heral qualif ier set to the value defi ned i n 3.6.2 . Th e INQU IRY comma nd sh all
return CHECK CONDITIO N status only when the device server is unable to return the reque sted INQUIRY
data.
If an INQUIRY command is re ceived from an in itiator port with a pending unit atte ntion condition (i .e., before
the device server reports CHECK CONDITION status), the device server shall perform the INQUIRY command
and shall not clear the unit attention condition (see SAM-3).
70 SCSI Commands Reference Manual, Rev. A
The INQUIRY data should be returned even though the device server is not ready for other commands. The
standard INQUIRY data should b e available without in curring any media access delays. If the device server
does store some of the standard INQUIRY data or VPD data on the media, it may return ASCII spaces (20h) in
ASCII fields and zeros in other fields until the data is available from the media.
The INQUIRY data may change as the SCSI target device and its logical units perform their initialization
sequence. (E.g., logic al units may provide a minimu m command set from nonvol atile memory until they loa d
the final firmware from th e media. After the firmware has been loaded, more options may be supported and
therefore different INQUIRY data may be returned.)
If the INQUIRY data changes for any reason, the dev ice server shall establish a unit atten tio n con di tion for the
initiator port asso ciated with every I_T nexus (see SAM- 3), with the additional sense code se t to INQUIRY
DATA HAS CHANGED.
The INQUIRY command may be used by an application client after a hard reset or power on condition to determine the device types for system configuration.
SCSI Commands Reference Manual, Rev. A 71
3.6.2 Standard INQUIRY data
The standard INQUIRY data (see table 46) shall contain at least 36 bytes
Table 46 — Standard INQUIRY data format
Bit
Byte
0
1
2
3
4
5
6
7
8
15
16
31
32
76543210
PERIPHERAL QUALIFIER PERIPHERAL DEVICE TYPE
RMB Reserved
VERSION
Obsolete Obsolete NORMACA HISUP RESPONSE DATA FORMAT
ADDITIONAL LENGTH (N-4)
SCCS ACC TPGS 3PC Reserved PROTECT
BQUE ENCSERV VS MULTIP MCHNGR Obsolete Obsolete
Obsolete Obsolete
(MSB) T10 VENDOR IDENTIFICATION
(MSB) PRODUCT IDENTIFICATION
(MSB) PRODUCT REVISION LEVEL
WBUS16
a
a
SYNC
LINKED Obsolete CMDQUE VS
a
ADDR16
(LSB)
(LSB)
a
35
36
43
44
55
56
57
58
59
72
73
74
95
DRIVE SERIAL NUMBER
Vendor Unique
Seagate fills this field with 00h.
Reserved
Reserved
(MSB) VERSION DESCRIPTOR 1
(MSB) VERSION DESCRIPTOR 8
Reserved
Vendor specific parameters
CLOCKING
.
.
(LSB)
a
QAS
a
IUS
(LSB)
(LSB)
a
72 SCSI Commands Reference Manual, Rev. A
Table 46 — Standard INQUIRY data format
Bit
Byte
96
n
76543210
Copyright Notice (Vendor specific)
a The meanings of these fields are specific to SPI-5 (see 3.6.3). For SCSI transport protocols other than the
SCSI Parallel Interface, these fields are reserved.
PERIPHERAL QUALIFIER and PERIPHERAL DEVICE TYPE fields
The PERIPHERAL QUALIFIER field and PERIPHERAL DEVICE T YPE fi el d id ent ify the peri pheral device connected to the
logical unit. If the SCSI target device is not capable of supporting a peripheral device connected to this logical unit, the
device server shall set these fields to 7Fh (i.e., PERIPHERAL QUALIFIER field set to 011b and PERIPHERAL DEVICE
TYPE field set to 1Fh).
The peripheral qualifier is defined in table 47 and the peripheral device type is defined in table 48.
Table 47 — PERIPHERAL QUALIFIER
Qualifier
000b
001b
Description
A peripheral device h av ing the specified periphe r al d ev ice ty pe is connected to this logi ca l u nit. If the
device server is unabl e to determine whether or no t a peripheral de vice is co nnected, it also shall use
this peripheral qualifier. Th is perip her al qu ali f ie r doe s not mea n tha t the pe rip hera l de vic e c onn ec ted
to the logical unit is ready for access.
A peripheral device having the specified peripheral device type is not connected to this logical unit.
However, the device server is capable of supporting the specified peripheral device type on this logical unit.
010b Reserved
The device server is no t c ap a ble of supporting a peripheral device on th is lo gic al un it. For this p erip h-
011b
100b - 111b Vendor specific
eral qualifier the pe ripheral de vice type sha ll be set to 1Fh. All other peripheral d evice typ e values are
reserved for this peripheral qualifier.
SCSI Commands Reference Manual, Rev. A 73
Table 48. PERIPHERAL DEVICE TYPE
Code
00h SBC-2 Direct access block device (e.g., magnetic disk)
01h SSC-2 Sequential-access device (e.g., magnetic tape)
02h SSC Printer device
03h SPC-2 Processor device
04h SBC Write-once device (e.g., some optical disks)
05h MMC-4 CD/DVD device
06h Scanner dev ic e (obs ole te)
07h SBC Optical memory device (e.g., some optical disks)
08h SMC-2 Medium changer device (e.g., jukeboxes)
09h Communications device (obsolete)
0Ah - 0Bh Obsolete
0Ch SCC-2 Storage array controller device (e.g., RAID)
0Dh SES Enclosure services device
0Eh RBC Simplified direct-access device (e.g., magnetic disk)
0Fh OCRW Optical card reader/writer device
Doc.
a
Description
10h BCC Bridge Controller Commands
11h OSD Object-based Storage Device
12h ADC Automation/Drive Interface
13h - 1Dh Reserved
1Eh Well known logical unit
1Fh Unknown or no dev ice type
a
All standards are subject to revision, and parties to agreements based on the standard are encouraged to investigate
the possibility of applying the most recent editions of the listed standards.
b
All well known logical units use the same peripheral d evice type code.
RMB (Removable Media) bit
b
0 A removable medium (RMB) bit set to zero indicates that the medium is not removable.
1 A RMB bit set to one indicates that the medium is removable.
74 SCSI Commands Reference Manual, Rev. A
VERSION field
The VERSION field indicates the implemented version of the standard and is defined in table 49.
Table 49. VERSION field codes
Code Description
00h The device does not claim conformance to any standard.
02h Obsolete
03h The device complies to ANSI INCITS 301-1997 (SPC).
04h The device complies to ANSI INCITS 351-2001 (SPC-2).
05h The device complies to the standard.
Code Description Code Description
01h Obsolete (SCSI=001b) 06h - 07h Reserved
08h - 0Ch Obsolete (ECMA=001b) 0Dh - 3Fh Reserved
40h - 44h Obsolete (ISO=01b) 45h - 47h Reserved
48h - 4Ch Obsolete (ISO=01b & ECMA=001b) 4Dh - 7Fh Reserved
80h - 84h Obsolete (ISO=10b) 85h - 87h Reserved
88h - 8Ch Obsolete (ECMA=001b) 8Dh - FFh Reserved
NORMACA (Normal ACA Supported
1 The Normal ACA Supported (NORMACA) bit set to one indicates that the device server supports a NACA bit set to
one in the CDB
CONTROL byte and supports the ACA task attribute (see SAM-3).
0 A NORMACA bit set to zero indicates that the device server does not support a NACA bit set to one and does not
support the ACA task attribute.
HISUP (Hierarchical Support) bit
0 A hierarchical support (HISUP) bit set to zero indicates the SCSI target device does not use the hierarchical
addressing model to assign LUNs to logical units.
1 A HISUP bit set to one indicates the SCSI target device uses the hierarchical addressing model to assign LUNs to
logical units.
RESPONSE DATA FORMAT field
A RESPONSE DATA FORMAT field value of two indicates that the data shall be in the format defined in the standard.
Response data format values less than two are obsolete. Response data format values greater than two are reserved.
ADDITIONAL LENGTH field
The ADDITIONAL LENGTH field indicates the length in bytes of the remaining standard INQUIRY data. The relationship
between the ADDITIONAL LENGTH field and the CDB ALLOCATION LENGTH field is defined in 2.1.4.5.
SCCS (SCC Supported) bit
1 An SCC Supported (SCCS) bit set to one indic ates that the SC SI targ et devic e cont ain s an embedd ed storag e array
controller component. See SCC-2 for details about storage array controller devices.
0 An SCCS bit set to zero indi cates that the SCSI target devic e does not contain an embedded s torage
array controller component.
ACC (Access Controls Coordinator) bit
1 An Access Controls Coordinator (ACC) bit set to one indicates that the SCSI target device contains an access con-
trols coordinator that may be addressed through this logical unit.
SCSI Commands Reference Manual, Rev. A 75
0 An ACC bit set to zero indicates that no access controls coordinator may be addressed through this logical unit. If
the SCSI target device contains an access controls coordinator that may be addressed through any logical unit
other than the ACCESS CONTROLS well known logical unit, then the ACC bit shall be set to one for LUN 0.
TPGS (Target Port Group Support) field
The contents of the target port group support (TPGS) field (see table 50) indicate the support for asymmetric logical unit
access.
Table 50. Taret Port GroupSupport codes
Code Description
The SCSI target device does not support asymmetric logical unit access or supports a form of asymmetric
00b
01b
access that is vend or s pe ci fic . Nei t he r th e REPOR T TARGET GROUPS nor the SET TARGET GROUPS commands is supported.
Only implicit asymmetric logical unit access (see SPC-4 clause 5.8.2.7) is supported. The SCSI target device
is capable of changing target port asymmetric access states without a SET TARGET PORT GROUPS command. The REPORT TARGET PORT GROUPS command is supported and the SET TARGET PORT
GROUPS command is not supported.
Only explicit asymmetric logical unit access (i.e., the TPGS
10b
11b
3PC (Third-Party Copy) bit
target device only changes target port asymmetric access states as requested with the SET TARGET PORT
GROUPS command. Both the REPORT TARGET PORT GROUPS command and the SET TARGET PORT
GROUPS command are supported.
Both explicit and implicit asymmetric logical unit access are supported. Both the REPORT TARGET PORT
GROUPS command and the SET TARGET PORT GROUPS commands are supported.
field contains 10b or 11b) is supported. The SCSI
1 A Third-Party Copy (3PC) bit set to one indicates that the SCSI target device supports third-party copy commands
such as the EXTENDED COPY command.
0 A 3PC bit set to zero indicates that the SCSI target device does not support such commands.
PROTECT bit
0 A PROTECT bit set to zero indicates that the logical unit does not support protection information (i.e. type 0) (see
SPC-4 7.6.4 and SBC-3).
1 A PROTECT bit set to one indicate s th at th e logical unit support s ty pe 1 prot ec tion , ty pe 2 p r ote ction, or type 3 pro-
tection (see SBC-3). The SPT field (see 4.4.5) indicates which type of protection the logical unit supports.
BQUE (Basic Queuing) bit
The BQUE bit c ombines with the CMDQ U E bi t to i ndi cate whether the log ic al un it supports the fu ll t as k ma nagement model
or the basic task management model as described in table 51.
ENCSERV (Enclosure Services) bit
1 An Enclosure Services (ENCSERV) bit set to one indicates that the SCSI target device contains an embedded
enclosure services component. See SES for details about enclosure services, including a device model for an
embedded enclosure serv ice s devic e.
0 An ENCSERV bit set to zero indicates that the SCSI target device does not contain an embedded enclosure ser-
vices component.
MULTIP (Multi Port) bit
1 A Multi Port (MULTIP) bit set to one indicates that this is a multi-port (two or more ports) SCSI target device and
conforms to the SCSI multi-port device requirements found in the applicable standards (e.g., SAM-3, a SCSI transport protocol standard and possibly provisions of a command standard).
0 A MULTIP bit set to zero indicates that this SCSI target device has a single port and does not implement the multi-
port requirements.
76 SCSI Commands Reference Manual, Rev. A
MCHNGR (Medium Changer) bit
1 A medium changer (MCHNGR) bit set to one indicates that the SCSI target device supports commands to control an
attached media changer. See SMC-2 for details about medium changers, including a device model for an attached
medium changer device. The MCHNGR bit is valid only when the RMB bit is equal to one.
0 A MCHNGR bit set to zero indicates that the SCSI target device does not support commands to control an attached
media changer.
LINKED (Linked Command) bit
1 A linked command (LINKED) bit set to one indicate s that the de vice server sup ports li nked comm ands (see SAM-3).
0 A LINKED bit set to zero indicates the device server does not support linked commands.
CMDQUE (Command Queuing) bit
The CMDQUE bit and BQUE bit indicate whether the logical unit supports the full task management model (see SAM-3) or
the basic task management model (see SAM-3) as described in table 51.
Table 51. BQue and CmdQue bit combinations
BQue CmdQue
00Obsolete
0 1 Full task management model supported
1 0 Basic task management model supported
1 1 Illegal combination of BQUE and CMDQUE bits
VENDOR IDENTIFICATION field
The T10 VENDOR IDENTIFICATION field contains eight bytes of left-aligned ASCII data (see 4.4.2) identifying the vendor
of the product. The T10 vendor identification shall be one assigned by INCITS. Bytes 8 through 15 contain the ASCII characters thet represent “SEAGATE ” (53h 45h 41h 47h 41h 54h 45h 20h (space)).
PRODUCT IDENTIFICATION
The PRODUCT IDENTIFICATION field contains sixteen bytes of left-aligned ASCII data (see 4.4.2) defined by Seagate.
Bytes 16 through 31 indicate the drive model with 20h (space) used as a filler. The table below is and example of drive test
data returned by the drive. Bytes 16 and 17 will contain 53 54 for all drive models.
Bte 18 throught 26 values that may be returned by a Seagate 15K5 parallel SCSI drive:
ST3300655LW 5354333330303635354C57
ST3300655LC 53 54 33 33 30 30 36 35 35 4C 43
ST3146855LW 5354333135363835354C57
ST3146855LC 53 54 33 31 35 36 38 35 35 4C 43
ST373455LW 53 54 33 37 33 34 35 35 4C 57 20
ST373455LC 53 54 33 37 33 34 35 35 4C 43 20
Description
Refer to the applicable Seagate product manual to get the actual test string.
PRODUCT REVISION LEVEL field
The PRODUCT REVISION LEVEL field contains four bytes of left-aligned ASCII data defined by Seagate. Bytes 32
through 35 contain the
four ASCII digits representing the last four digits of the product Fir mware Release number. This
information is also given in the Vital Product Data page C0h, together with servo RAM and ROM release numbers.
VERSION DESCRIPTOR fields
The VERSION DESCRIPTOR fields provide for identifying up to eight standards to which the SCSI target device claims
conformance. The value in each VERSION DESCRIPTOR field shall be selected from the Version Descriptor Values Table
in the current SPC standard. All version descriptor values not listed in table 52 are reserved. Technical Committee T10 of
INCITS maintains an electronic copy of the information in the Version Descriptor Values Table on its world wide web site
(http://www.t10.org/). In the event that the T10 world wide web site is no longer active, access may be possible via the
INCITS world wide web site (http://www.incits.org), the ANSI world wide web site (http://www.ansi.org), the IEC site (http://
SCSI Commands Reference Manual, Rev. A 77
www.iec .ch /), the ISO site (http://www.iso.c h/) , or the ISO /IEC JTC 1 we b si te (ht tp:/ /w ww.jtc1.org/). It is recommended that
the first version descriptor be used for the SCSI architecture standard, followed by the physical transport standard if any,
followed by the SCSI transport protocol standard, followed by the appropriate SPC version, followed by the device type
command set, follo we d b y a se co nda ry c om m and se t if any. Refer to the latest SPC version for a c ompl ete list of descriptor
values.
Copyright Notice field
Seagate uses bytes 96 - 143 to provide a copyright notice that begins “Copyright (c) XXXX Seagate All rights reserved,”
where “XXXX” indicates the year the drive’s firmware code was built (for example: 2005).
3.6.3 SCSI Parallel Interface specific INQUIRY data
Portions of bytes 6 and 7 and all of byte 56 of th e standard INQUIRY data sh all be used onl y by SCSI targe t
devices that implement the SCSI Parallel Interface. These fields are noted in table 46. For details on how the
SPI-specific fields relate to the SCSI Parallel Interface see SPI-n (where n is 2 or greater). Table 52 shows just
the SPI-specific standar d INQUIRY fiel ds. The de finitions of the SCS I Par allel I nterface specific field s shall b e
as follows.
T able 52 — SPI-specific standard INQUIRY bits
Bit
Byte
6 SEE table 46 ADDR16
7 SEE table 46 WBUS16 SYNC SEE table 46 Obsolete SEE table 46
56 Reserved CLOCKING QAS IUS
ADDR16 (wide SCSI address 16) bit
76543210
.
.
.
1 A wide SCSI address 16 (ADDR16) bit of one indicates that the SCSI target device supports 16-bit wide SCSI
addresses.
0 A value of zero indicates that the SCSI target device does not support 16-bit wide SCSI addresses.
WBUS16 (wide bus 16) bit
1 A wide bus 16 (WBUS16) bit of one indicates that the SCSI target device supports 16-bit wide data transfers.
0 A value of zero indicates that the SCSI target device does not support 16-bit wide data transfers.
SYNC (synchronous transfer) bit
1 A synchronous transfer (S YNC) bit o f one ind icates tha t the SC SI targ et devi ce su pport s syn chronous dat a tran sfer.
0 A value of zero indicates the SCSI target device does not support synchronous data transfer.
The obsolete bit 2 in byte 7 indicates whether the SCSI target device supports an obsolete data transfers management mechanism defined in SPI-2.
78 SCSI Commands Reference Manual, Rev. A
Table 53 defines the relationships between the ADDR16 and WBUS16 bits.
Table 53. ADDR and WBUS bit relationships
addr16 wbus16 Description
008 bit wide data path on a single cable with 8 SCSI IDs supported
0116 bit wide data path on a single cable with 8 SCSI IDs supported
1116 bit wide data path on a single cable with 16 SCSI IDs supported
CLOCKING field
The CLOCKING field shall not apply to asynchronous transfers and is defined in table 54.
Table 54. CLOCKING codes
Code
00b Indicates the target port supports only ST
01b Indicates the target port supports only DT
10b Reserved
11b Indicates the target port supports ST and DT
QAS (Quick Arbitration And Selection Supported) bit
Description
1 A quick arbitration and selection supported (QAS) bit of one indicates that the target port supports quick arbitration
and selection.
0 A value of zero indicates that the target port does not support quick arbitration and selection.
IUS (information units supported) bit
1 An information units su ppo rted (IU S) bit of one indicates that the SCSI target devic e supports information u nit trans -
fers.
0 A value of zero indicates that the SCSI target device does not support information unit transfers.
The acronyms ST a nd DT an d the terms 'quick a rbitration and sele ction' and 'informa tion units' ar e define d in
SPI-5.
3.6.4 Vital product data
The application clie nt re que sts the vi tal pro duc t data information by setting the EVPD bi t to one and sp ec ify ing
the page code of a vital product data. See
4.4 for details about vital product data. The information returned con-
sists of configuration data (e.g., vendor identification, product identification, model, serial number), manufacturing data (e.g., plant and date of manufacture ), field repla ceable uni t data and othe r vendor spe cific or d evice
specific data. If the device s erver does n ot impleme nt the requ ested page, the command sha ll be ter minated
with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code
set to INVALID FIELD IN CDB.
The device server sho uld have the a bility to process the INQU IRY command eve n when an erro r occurs that
prohibits normal command com pletion. In such a case, CHECK CONDITION status shoul d be returned for
commands other than INQUIRY or REQUEST SENSE. The sense data returned may contain the field replaceable unit code. The vital product data may be obtained for the failing device using the INQUIRY command.
the standard defines a format that allows device-indep endent application client s oftware to display the vital
product data returned by t he INQUIRY command. The contents of the data may be vendor specifi c, and may
be unusable without detailed information about the device.
SCSI Commands Reference Manual, Rev. A 79
the standard does not define the locati on or method of storin g the vital product data. The retrie val of the data
may require completion of i nitial ization op erations within the devic e, that may ind uce del ays be fore the data is
available to the app licatio n clien t. Time-critical req uiremen ts are an imp lementatio n consider ation an d are no t
addressed in the standard.
3.7 LOCK-UNLOCK Cache (10) command
Obsolete. If received, a CHECK CONDITION status is sent.
3.8 LOCK-UNLOCK Cache (16) command
Obsolete. If received, a CHECK CONDITION status is sent.
80 SCSI Commands Reference Manual, Rev. A
Loading...