User Manual

ManualsBrandsSeagate Bulk ManualsSeagate Bulk Hard Drives & Storage4TB ENT CAP 3.5 HDD SATA 7200 RPM 128MB 3.5IN

100293068, Rev. J

October 2016

Fibre Channel (FC)

Serial Attached SCSI (SAS)

SCSI Commands

Reference Manual

Summary of content (518 pages)

PAGE 1
SCSI Commands Reference Manual Fibre Channel (FC) Serial Attached SCSI (SAS) 100293068, Rev.
PAGE 2
© 2016 Seagate Technology LLC. All rights reserved. Publication number: 100293068, Rev. J October 2016 Seagate, Seagate Technology and the Spiral logo are registered trademarks of Seagate Technology LLC in the United States and/or other countries. SeaTools is a trademarks of Seagate Technology LLC or one of its affiliated companies in the United States and/or other countries. All other trademarks or registered trademarks are the property of their respective owners.
PAGE 3
Contents 1. Definitions, Symbols, Abbreviations, Keywords, And Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 1.1 1.2 1.3 1.4 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Symbols and abbreviations . . . . . . .
PAGE 4
Contents 3.9 MODE SELECT(6) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10 MODE SELECT (10) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11 MODE SENSE(6) command. . . . . . .
PAGE 5
Contents 3.28 REASSIGN BLOCKS command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.28.1 REASSIGN BLOCKS command overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.28.2 REASSIGN BLOCKS parameter list . . . . . . . . . . . . .
PAGE 6
Contents 3.50 STREAM CONTROL command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.50.1 STREAM CONTROL command overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.50.2 STREAM CONTROL parameter data . . . . . . . . . . . . . . .
PAGE 7
Contents 4. Zone Block Commands (ZBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 4.1 4.2 4.3 4.4 4.5 Commands for zoned block devices overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CLOSE ZONE command (94h/01h). . . . . . . . .
PAGE 8
Contents 5.3 Mode parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.1 Mode parameters overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.
PAGE 9
Contents 5.4 Vital product data parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Vital product data parameters overview and page codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 ASCII Information VPD page (01h - 7Fh) . . . . . . . . . . . .
PAGE 10
Tables Table 1. Table 2. Table 3. Table 4. Table 5. Table 6. Table 7. Table 8. Table 9. Table 10. Table 11. Table 12. Table 13. Table 14. Table 15. Table 16. Table 17. Table 18. Table 19. Table 20. Table 21. Table 22. Table 23. Table 24. Table 25. Table 26. Table 27. Table 28. Table 29. Table 30. Table 31. Table 32. Table 33. Table 34. Table 35. ISO v American Numbering Conventions ......................................................................................................................
PAGE 11
Tables Table 36. Table 37. Table 38. Table 39. Table 40. Table 41. Table 42. Table 43. Table 44. Table 45. Table 46. Table 47. Table 48. Table 49. Table 50. Table 51. Table 52. Table 53. Table 54. Table 55. Table 56. Table 57. Table 58. Table 59. Table 60. Table 61. Table 62. Table 63. Table 64. Table 65. Table 66. Table 67. Table 68. Table 69. Table 70. FORMAT UNIT command address descriptor usage ..................................................................................................
PAGE 12
Tables Table 71. Table 72. Table 73. Table 74. Table 75. Table 76. Table 77. Table 78. Table 79. Table 80. Table 81. Table 82. Table 83. Table 84. Table 85. Table 86. Table 87. Table 88. Table 89. Table 90. Table 91. Table 92. Table 93. Table 94. Table 95. Table 96. Table 97. Table 98. Table 99. Table 100. Table 101. Table 102. Table 103. Table 104. Table 105. Mode page policies ................................................................................................................................
PAGE 13
Tables Table 106. Table 107. Table 108. Table 109. Table 110. Table 111. Table 112. Table 113. Table 114. Table 115. Table 116. Table 117. Table 118. Table 119. Table 120. Table 121. Table 122. Table 123. Table 124. Table 125. Table 126. Table 127. Table 128. Table 129. Table 130. Table 131. Table 132. Table 133. Table 134. Table 135. Table 136. Table 137. Table 138. Table 139. Table 140. READ BUFFER descriptor ...............................................................................................
PAGE 14
Tables Table 141. Table 142. Table 143. Table 144. Table 145. Table 146. Table 147. Table 148. Table 149. Table 150. Table 151. Table 152. Table 153. Table 154. Table 155. Table 156. Table 157. Table 158. Table 159. Table 160. Table 161. Table 162. Table 163. Table 164. Table 165. Table 166. Table 167. Table 168. Table 169. Table 170. Table 171. Table 172. Table 173. Table 174. Table 175. RELEASE (10) parameter list ..........................................................................................
PAGE 15
Tables Table 176. Table 177. Table 178. Table 179. Table 180. Table 181. Table 182. Table 183. Table 184. Table 185. Table 186. Table 187. Table 188. Table 189. Table 190. Table 191. Table 192. Table 193. Table 194. Table 195. Table 196. Table 197. Table 198. Table 199. Table 200. Table 201. Table 202. Table 203. Table 204. Table 205. Table 206. Table 207. Table 208. Table 209. Table 210. Supported security protocols SECURITY PROTOCOL IN parameter data .....................................................
PAGE 16
Tables Table 211. Table 212. Table 213. Table 214. Table 215. Table 216. Table 217. Table 218. Table 219. Table 220. Table 221. Table 222. Table 223. Table 224. Table 225. Table 226. Table 227. Table 228. Table 229. Table 230. Table 231. Table 232. Table 233. Table 234. Table 235. Table 236. Table 237. Table 238. Table 239. Table 240. Table 241. Table 242. Table 243. Table 244. Table 245. VRPROTECT field with BYTCHK field set to 01b or 11b - byte-by-byte comparison requirements ........
PAGE 17
Tables Table 246. Table 247. Table 248. Table 249. Table 250. Table 251. Table 252. Table 253. Table 254. Table 255. Table 256. Table 257. Table 258. Table 259. Table 260. Table 261. Table 262. Table 263. Table 264. Table 265. Table 266. Table 267. Table 268. Table 269. Table 270. Table 271. Table 272. Table 273. Table 274. Table 275. Table 276. Table 277. Table 278. Table 279. Table 280. REPORT ZONE command ..................................................................................................
PAGE 18
Tables Table 281. Table 282. Table 283. Table 284. Table 285. Table 286. Table 287. Table 288. Table 289. Table 290. Table 291. Table 292. Table 293. Table 294. Table 295. Table 296. Table 297. Table 298. Table 299. Table 300. Table 301. Table 302. Table 303. Table 304. Table 305. Table 306. Table 307. Table 308. Table 309. Table 310. Table 311. Table 312. Table 313. Table 314. Table 315. Background Scan parameter format .....................................................................................
PAGE 19
Tables Table 316. Table 317. Table 318. Table 319. Table 320. Table 321. Table 322. Table 323. Table 324. Table 325. Table 326. Table 327. Table 328. Table 329. Table 330. Table 331. Table 332. Table 333. Table 334. Table 335. Table 336. Table 337. Table 338. Table 339. Table 340. Table 341. Table 342. Table 343. Table 344. Table 345. Table 346. Table 347. Table 348. Table 349. Table 350. SCOPE field ..........................................................................................................
PAGE 20
Tables Table 351. Table 352. Table 353. Table 354. Table 355. Table 356. Table 357. Table 358. Table 359. Table 360. Table 361. Table 362. Table 363. Table 364. Table 365. Table 366. Table 367. Table 368. Table 369. Table 370. Table 371. Table 372. Table 373. Table 374. Table 375. Table 376. Table 377. Table 378. Table 379. Table 380. Table 381. Table 382. Table 383. Table 384. Table 385. Temperature log page parameter codes .................................................................................
PAGE 21
Tables Table 386. Table 387. Table 388. Table 389. Table 390. Table 391. Table 392. Table 393. Table 394. Table 395. Table 396. Table 397. Table 398. Table 399. Table 400. Table 401. Table 402. Table 403. Table 404. Table 405. Table 406. Table 407. Table 408. Table 409. Table 410. Table 411. Table 412. Table 413. Table 414. Table 415. Table 416. Table 417. Table 418. Table 419. Table 420. Format Parameters page (03h) .........................................................................................
PAGE 22
Tables Table 421. Table 422. Table 423. Table 424. Table 425. Table 426. Table 427. Table 428. Table 429. Table 430. Table 431. Table 432. Table 433. Table 434. Table 435. Table 436. Table 437. Table 438. Table 439. Table 440. Table 441. Table 442. Table 443. Table 444. Table 445. Table 446. Table 447. Table 448. Table 449. Table 450. Table 451. Table 452. Table 453. Table 454. Table 455. Transceiver Controls descriptor (12Gb Link Rate) .....................................................................
PAGE 23
Tables Table 456. Table 457. Table 458. Table 459. Table 460. Table 461. Table 462. Table 463. Table 464. Table 465. Table 466. Table 467. Table 468. Table 469. Table 470. Table 471. Table 472. Table 473. Table 474. Table 475. Table 476. Table 477. Table 478. Table 479. Table 480. Table 481. Table 482. Table 483. Table 484. Table 485. SPT field ...................................................................................................................................................................
PAGE 24
www.seagate.com 1. Definitions, Symbols, Abbreviations, Keywords, And Conventions Definitions, Symbols, Abbreviations, Keywords, And Conventions This clause contains the definitions, symbols, abbreviations, keywords and, conventions used throughout this manual. These items are from the American National Standards Institute T10 committee standards.
PAGE 25
www.seagate.com 1.1 Definitions, Symbols, Abbreviations, Keywords, And Conventions 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.
PAGE 26
www.seagate.com Definitions, Symbols, Abbreviations, Keywords, And Conventions Copy target device The name given by the EXTENDED COPY command to a source or destination logical unit (i.e., a copy 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.
PAGE 27
www.seagate.com Definitions, Symbols, Abbreviations, Keywords, And Conventions 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.
PAGE 28
www.seagate.com Definitions, Symbols, Abbreviations, Keywords, And Conventions Internet protocol number A coded value assigned to identify protocols that layer on the Internet protocol (see RFC 791). The Internet protocol number assigned to the transmission control protocol (TCP, see RFC 793) is six. The Internet Assigned Numbers Authority maintains a list of Internet protocol number assignments at http://www.iana.org/assignments/protocol-numbers.
PAGE 29
www.seagate.com Definitions, Symbols, Abbreviations, Keywords, And Conventions 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 within a device that stores data as magnetic field changes that do not require device power to exist). Null-padded A type of field in which unused bytes are placed at the end of the field (i.e.
PAGE 30
www.seagate.com Definitions, Symbols, Abbreviations, Keywords, And Conventions 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 AND 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.
PAGE 31
www.seagate.com Definitions, Symbols, Abbreviations, Keywords, And Conventions 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-5. 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 device server.
PAGE 32
www.seagate.com Definitions, Symbols, Abbreviations, Keywords, And Conventions Unit attention condition A state that a logical unit maintains while it has asynchronous status information to report to the initiator ports associated with one or more I_T nexuses. See SAM-5. Universal time (UT) The time at longitude zero, colloquially known as Greenwich Mean Time. See http://aa.usno.navy.mil/faq/docs/UT.html.
PAGE 33
www.seagate.com 1.2 Definitions, Symbols, Abbreviations, Keywords, And Conventions Symbols and abbreviations See Table 1 for abbreviations of standards bodies (e.g., ISO).
PAGE 34
www.seagate.
PAGE 35
www.seagate.com 1.3 Definitions, Symbols, Abbreviations, Keywords, And Conventions Keywords Expected A keyword used to describe the behavior of the hardware or software in the design models assumed by this manual. Other hardware and software design models may also be implemented. Ignored A keyword used to describe an unused bit, byte, word, field or code value.
PAGE 36
www.seagate.com 1.4 Definitions, Symbols, Abbreviations, Keywords, And Conventions Conventions Certain words and terms used in this manual have a specific meaning beyond the normal English meaning. These words and terms are defined either in this clause or in the text where they first appear. Names of commands, 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.
PAGE 37
www.seagate.com 2. General Concepts General Concepts This manual defines behaviors that are common to all Seagate SCSI device models. This manual defines the SCSI commands that are basic to more than one disk drive model and the SCSI commands that may apply to any SCSI Interface, including Fibre Channel and Serial Attached SCSI (SAS). 2.1 2.1.1 Command Descriptor Block (CDB) CDB usage and structure A command is communicated by sending a command descriptor block (CDB) to the device server.
PAGE 38
www.seagate.com 2.1.2 General Concepts 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-byte CDB. Table 5 shows the format of a 16-byte CDB for commands that provide for a long LBA.
PAGE 39
www.seagate.com Table 4 Bit Byte General Concepts Typical CDB for 12-byte commands 7 6 5 4 0 1 2 3 2 1 OPERATION CODE Miscellaneous CDB information SERVICE ACTION (if required) (MSB) ... LOGICAL BLOCK ADDRESS (if required) 5 6 (LSB) (MSB) TRANSFER LENGTH (If required) PARAMETER LIST LENGTH (if required) ALLOCATION LENGTH (if required) ... 9 10 Miscellaneous CDB information 11 CONTROL Table 5 Bit Byte 7 6 5 4 3 OPERATION CODE 1 Miscellaneous CDB information 2 1 0 (MSB) ...
PAGE 40
www.seagate.com 2.1.3 General Concepts The variable length CDB formats The first byte of a variable length CDB shall contain the operation code 7Fh.
PAGE 41
www.seagate.
PAGE 42
www.seagate.com 2.2 General Concepts 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 provide for modification of their operation based on a service action (see 2.2.2). In such cases, the operation 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.
PAGE 43
www.seagate.com 2.2.3 General Concepts LOGICAL BLOCK ADDRESS The logical block addresses on a logical unit or within a volume or partition shall begin with block zero and be contiguous up to the last logical block of that logical unit or within that volume or partition. A six-byte CDB may contain a 21-bit LOGICAL BLOCK ADDRESS field. The ten-byte and the twelve-byte CDBs may contain 32-bit LOGICAL BLOCK ADDRESS fields.
PAGE 44
www.seagate.com 2.2.7 General Concepts CONTROL The CONTROL byte has the same definition for all commands. All CDBs shall contain a CONTROL byte (see table 10). The location of the CONTROL byte within a CDB depends on the CDB format (see 2.1.2 and 2.1.3). Table 10 Bit CONTROL byte 7 6 Vendor Specific 5 4 Reserved 3 2 1 0 NACA Obsolete Obsolete All SCSI transport protocol standards shall define the functionality needed for a logical unit to implement the NACA bit.
PAGE 45
www.seagate.com 2.3 General Concepts Parameter Rounding Certain parameters sent to a SCSI target port with various commands contain a range of values. Targets may choose to implement only selected values from this range. When the target receives 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 received to a supported value.
PAGE 46
www.seagate.com 2.4 General Concepts Sense data 2.4.1 Sense data introduction Sense data shall be returned in the same I_T_L_Q nexus transaction as a CHECK CONDITION status and as parameter data in response to the REQUEST SENSE command. Sense 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 format based on the value of the D_SENSE bit in the Control mode page.
PAGE 47
www.seagate.com General Concepts 2.4.1.1 Descriptor format sense data 2.4.1.1.1 Descriptor format sense data overview The descriptor format sense data for response codes 72h (current errors) and 73h (deferred errors) is defined in table 12. Table 12 Descriptor format sense data Bit Byte 7 0 Reserved 1 6 5 4 3 2 1 0 RESPONSE CODE (72h or 73h) Reserved SENSE KEY 2 ADDITIONAL SENSE CODE 3 ADDITIONAL SENSE CODE QUALIFIER 4 ...
PAGE 48
www.seagate.com General Concepts SENSE DATA DESCRIPTORS field Sense data descriptors (see table 13) 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 13 Sense data descriptor format Bit Byte 7 6 5 4 3 0 DESCRIPTOR TYPE 1 ADDITIONAL LENGTH (n-1) 2 2 1 0 (MSB) ...
PAGE 49
www.seagate.com 2.4.1.1.2 General Concepts Information sense data descriptor The information sense data descriptor (see table 15) provides information that is device-type or command specific and is defined in a command standard. Table 15 Information sense data descriptor format Bit Byte 7 6 5 4 3 0 DESCRIPTOR TYPE (00h) 1 ADDITIONAL LENGTH (0Ah) 2 VALID (1b) 1 0 Reserved 3 4 2 Reserved (MSB) ...
PAGE 50
www.seagate.com General Concepts 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 occurred.
PAGE 51
www.seagate.com General Concepts The definition of the SENSE KEY SPECIFIC field (see table 18) is determined by the value of the SENSE KEY field (see 2.4.1.1.1). Table 18 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 Actual retry count 2.4.1.1.4.3 NO SENSE or NOT READY Progress indication 2.4.1.1.4.4 COPY ABORTED Segment pointer 2.4.1.1.4.
PAGE 52
www.seagate.com 2.4.1.1.4.3 General Concepts 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 20. Table 20 Actual retry count sense key specific data Bit Byte 7 0 SKSV (1b) 1 (MSB) 6 5 4 3 2 1 0 Reserved ACTUAL RETRY COUNT 2 (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.
PAGE 53
www.seagate.com 2.4.1.1.4.5 General Concepts Segment pointer sense key specific data If the sense key is COPY ABORTED, the SENSE KEY SPECIFIC field shall be as shown in table 22. Table 22 Segment pointer sense key specific data Bit Byte 7 6 5 4 3 0 SKSV (1b) Reserved SD Reserved BPV 1 (MSB) 2 1 0 BIT POINTER FIELD POINTER 2 (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.
PAGE 54
www.seagate.com 2.4.1.1.5 General Concepts Field replaceable unit sense data descriptor The field replaceable unit sense data descriptor (see table 24) provides information about a component that has failed.
PAGE 55
www.seagate.com General Concepts SENSE KEY field The SENSE KEY field indicates the operation for which this progress indication sense data descriptor provides a progress indication. A list of sense key values is in 2.4.1.5. ADDITIONAL SENSE CODE field The ADDITIONAL SENSE CODE (ASC) field indicates the operation for which this progress indication sense data descriptor provides a progress indication. A list of additional sense codes is in 2.4.1.6.
PAGE 56
www.seagate.com 2.4.1.2 General Concepts Fixed format sense data The fixed format sense data for response codes 70h (current errors) and 71h (deferred errors) is defined in table 27. Table 27 Fixed format sense data Bit Byte 7 0 VALID 6 5 4 3 2 1 0 RESPONSE CODE (70h OR 71h) 1 Obsolete 2 FILEMARK 3 (MSB) EOM ILI ... Reserved SENSE KEY INFORMATION 6 (LSB) 7 ADDITIONAL SENSE LENGTH (n-7) 8 (MSB) ...
PAGE 57
www.seagate.com General Concepts 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. INFORMATION field The contents of the INFORMATION field is device-type or command specific and is defined within the appropriate standard for the device type or command of interest. targets shall implement the INFORMATION field.
PAGE 58
www.seagate.com 2.4.1.4 General Concepts Deferred errors Response codes 71h and 73h (deferred error) indicate that the sense data returned is the result of an error or exception condition that occurred during processing of a previous command for which GOOD, CONDITION MET, INTERMEDIATE, and INTERMEDIATE-CONDITION MET status has already been returned. Such commands are associated with the use of the immediate bit and with some forms of caching.
PAGE 59
www.seagate.com 2.4.1.5 General Concepts Sense key and sense code definitions The sense keys are defined in table 28. Table 28 Sense key descriptions Sens e Key 0h 1h 2h 3h 4h 5h 6h 7h 8h 9h Ah Bh Ch Dh Eh Fh Description 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.
PAGE 60
www.seagate.com 2.4.1.6 General Concepts Additional Sense and Additional Sense Qualifier codes Table 29 lists the Additional Sense (ASC) and Additional Sense Qualifier (ASCQ) codes. Code values are in hexadecimal. ANSI standard SPC-5 lists a more complete table. NOTE Table 29 Table 29 is for reference only, as not all drives covered by this manual support all of the codes listed. Codes without sense key references may or may not be supported.
PAGE 61
www.seagate.
PAGE 62
www.seagate.
PAGE 63
www.seagate.
PAGE 64
www.seagate.
PAGE 65
www.seagate.com 3. Direct Access Block commands (SPC-5 and SBC-4) Direct Access Block commands (SPC-5 and SBC-4) This clause describes the commands supported by Seagate Disk Drives. Commands that have been supported prior to this manual being produced and that are now indicated as obsolete will be described in this clause as obsolete. However, a description will be provided for such commands.
PAGE 66
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) Command type Command name OP code [1] All devices Direct access devices Clause Reference READ CAPACITY (10) 25h x 3.22 READ CAPACITY (16) 9Eh/10h x 3.23 READ DEFECT DATA (10) 37h x 3.24 READ DEFECT DATA (12) B7h x 3.25 3Eh x 3.26 READ LONG (16) [2] 9Eh/11h x 3.27 REASSIGN BLOCKS 07h x 3.28 RECEIVE DIAGNOSTIC RESULTS 1Ch x 3.29 17h x 3.30 57h x 3.31 A3h/05h x 3.32 A0h x 3.
PAGE 67
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) Command type Command name OP code [1] All devices Direct access devices Clause Reference VERIFY(10) 2Fh x 3.55 VERIFY (12) AFh x 3.56 VERIFY (16) 8Fh x 3.57 VERIFY (32) 7Fh/000Ah x 3.58 WRITE (6) 0Ah x 3.59 WRITE (10) 2Ah x 3.60 WRITE (12) AAh x 3.61 WRITE (16) 8Ah x 3.62 WRITE (32) 7Fh/000Bh x 3.63 WRITE AND VERIFY (10) 2Eh x 3.64 WRITE AND VERIFY (12) AEh x 3.
PAGE 68
www.seagate.com 3.1 Direct Access Block commands (SPC-5 and SBC-4) BACKGROUND CONTROL command The BACKGROUND CONTROL command (see table 31) is used to request that the device server start or stop host initiated advanced background operations (see 5.3.8), if any. This command uses the SERVICE ACTION IN (16) CDB format (see SBC-4 - Annex A.2). Table 31 BACKGROUND CONTROL command Bit Byte 7 0 1 2 3 4 ...
PAGE 69
www.seagate.com 3.2 Direct Access Block commands (SPC-5 and SBC-4) CHANGE DEFINITION command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. The CHANGE DEFINITION command (see table ) is used to modify the operating definition of the device server(s) with respect to commands from the sending initiator or with respect to commands from all initiators.
PAGE 70
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) PARAMETER DATA LENGTH field The parameter data length field specifies the length in bytes of the parameter data that shall be transferred from the application client to the device server. 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.
PAGE 71
www.seagate.com 3.3 Direct Access Block commands (SPC-5 and SBC-4) FORMAT UNIT command 3.3.1 FORMAT UNIT command overview The FORMAT UNIT command (see table 35) requests that the device server format the medium into application client accessible logical blocks as specified in the number of blocks and block length values received in the last mode parameter block descriptor (see 5.3.4) in a MODE SELECT command (see 3.9 and 3.10).
PAGE 72
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) FMTPINFO (Format Protection Information) field The format protection information (FMTPINFO) field (see table 41) in combination with the PROTECTION FIELD USAGE field (see 3.3.3) specifies whether or not the device server enables or disables the use of protection information. When protection information is written during a FORMAT UNIT command (i.e.
PAGE 73
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) Table 36 defines the address descriptor usage for the FORMAT UNIT command.
PAGE 74
www.seagate.com Table 36 Direct Access Block commands (SPC-5 and SBC-4) FORMAT UNIT command address descriptor usage (Sheet 2 of 2) Field in the FORMAT UNIT CDB FMTDATA CMPLST DEFECT LIST FORMAT DEFECT LIST LENGTH field in the parameter list header 0 Type [a] Comments [f] O See [b] and [d] O See [b] and [e] O See [c] and [d] O See [c] and [e] Zero 1 1 0 101b (physical sector) Nonzero 1 0 1 1 110b (vendor specific) O Vendor specific O All others [a] Reserved.
PAGE 75
www.seagate.com 3.3.2 3.3.2.1 Direct Access Block commands (SPC-5 and SBC-4) FORMAT UNIT parameter list FORMAT UNIT parameter list overview Table 38 defines the FORMAT UNIT parameter list. Table 38 Bit Byte FORMAT UNIT parameter list 7 6 5 4 3 2 1 0 Parameter List Header (see table 39 or table 40 in 3.3.3) Initialization Pattern Descriptor (if any) (see table 42, in 3.3.4) Defect List (if any) PARAMETER LIST HEADER field The PARAMETER LIST HEADER is defined in 3.3.3.
PAGE 76
www.seagate.com 3.3.3 Direct Access Block commands (SPC-5 and SBC-4) Parameter list header The parameter list headers (see table 39 and table 40) provide several optional format control parameters. Device servers that implement these headers provide the application client additional control over the use of the four defect sources, and the format operation.
PAGE 77
www.seagate.com Table 41 Direct Access Block commands (SPC-5 and SBC-4) FMTPINFO field and PROTECTION FIELDS USAGE field (Sheet 1 of 2) Device server indication Application client specification Description SPT [a] PROTECT [b] FMTP INFO PROTECTION FIELD USAGE xxxb 0 00b 000b The logical unit shall be formatted to type 0 protection [c] (see SBC-4) resulting in the P_TYPE field [d] being set to 000b.
PAGE 78
www.seagate.com Table 41 Direct Access Block commands (SPC-5 and SBC-4) FMTPINFO field and PROTECTION FIELDS USAGE field (Sheet 2 of 2) Device server indication Application client specification Description SPT [a] PROTECT [b] FMTP INFO PROTECTION FIELD USAGE [a] See the Extended INQUIRY Data VPD page (see 5.4.9) for the definition of the SPT field. [b] See the standard INQUIRY data (see 3.6.2) for the definition of the PROTECT bit.
PAGE 79
www.seagate.com NOTE Direct Access Block commands (SPC-5 and SBC-4) The use of the FMTDATA bit, the CMPLST bit, and the parameter list header allow the application client to control the source of the defect lists used by the FORMAT UNIT command. Setting the DEFECT LIST LENGTH field to zero allows the application client to control the use of PLIST and CLIST without having to specify a DLIST.
PAGE 80
www.seagate.com 3.3.4 Direct Access Block commands (SPC-5 and SBC-4) Initialization pattern descriptor The initialization pattern descriptor specifies that the device server initialize logical blocks to a specified pattern. The initialization pattern descriptor (see table 42) is sent to the device server as part of the FORMAT UNIT parameter list.
PAGE 81
www.seagate.com 3.3.5 Direct Access Block commands (SPC-5 and SBC-4) Address descriptor formats 3.3.5.1 Address descriptor formats overview This subclause describes the address descriptor formats used in the FORMAT UNIT command, the READ DEFECT DATA commands (see 3.24 and 3.25), and the Translate Address diagnostic pages (see 5.1.3) of the SEND DIAGNOSTIC command and the RECEIVE DIAGNOSTIC RESULTS command.
PAGE 82
www.seagate.com 3.3.5.3 Direct Access Block commands (SPC-5 and SBC-4) Extended bytes from index address descriptor A format type of 001b specifies the extended bytes from index address descriptor defined in table 46.
PAGE 83
www.seagate.com 3.3.5.4 Direct Access Block commands (SPC-5 and SBC-4) Extended physical sector address descriptor A format type of 010b specifies the extended physical sector address descriptor defined in table 47.
PAGE 84
www.seagate.com 3.3.5.5 Direct Access Block commands (SPC-5 and SBC-4) Long block format address descriptor A format type of 011b specifies the long block format address descriptor defined in table 48. Table 48 Long block format address descriptor (011b) Bit Byte 7 0 (MSB) 6 5 ... 4 3 2 1 0 LONG BLOCK ADDRESS 7 (LSB) LONG BLOCK ADDRESS field For the FORMAT UNIT command, the LONG BLOCK ADDRESS field contains the eight-byte logical block address of a defect.
PAGE 85
www.seagate.com 3.3.5.7 Direct Access Block commands (SPC-5 and SBC-4) Physical sector format address descriptor A format type of 101b specifies the physical sector address descriptor defined in table 50. 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.
PAGE 86
www.seagate.com 3.4 Direct Access Block commands (SPC-5 and SBC-4) GET LBA STATUS command 3.4.1 GET LBA STATUS command overview The GET LBA STATUS command (see table 51) requests that the device server transfer parameter data describing the logical block provisioning status (see SBC-4) for the specified LBA and zero or more subsequent LBAs to the Data-In Buffer. The device server may or may not process this command as an uninterrupted sequence of actions (e.g.
PAGE 87
www.seagate.com 3.4.2 Direct Access Block commands (SPC-5 and SBC-4) GET LBA STATUS parameter data 3.4.2.1 GET LBA STATUS parameter data overview The GET LBA STATUS parameter data (see table 52) contains an eight-byte header followed by one or more LBA status descriptors. Table 52 GET LBA STATUS parameter data Bit Byte 7 6 0 ... 3 4 ... 7 5 4 3 2 1 0 PARAMETER DATA LENGTH (n-3) Reserved LBA status descriptors 8 ... 23 (MSB) LBA status descriptor [first] (LSB) ... n-15 ...
PAGE 88
www.seagate.com 3.4.2.2 Direct Access Block commands (SPC-5 and SBC-4) LBA status descriptor The LBA status descriptor (see table 53) contains LBA status information for one or more LBAs. LBA status descriptor format Table 53 Bit Byte 7 0 ... 7 8 ... 11 12 13 ...
PAGE 89
www.seagate.com 3.5 Direct Access Block commands (SPC-5 and SBC-4) GET STREAM STATUS command The GET STREAM STATUS command (see table 55) requests that the device server transfer parameter data describing the status of streams (see SBC-4) for the logical unit to the Data-In Buffer. The device server may or may not process this command as an uninterrupted sequence of actions (e.g.
PAGE 90
www.seagate.com 3.5.1 Direct Access Block commands (SPC-5 and SBC-4) GET STREAM STATUS parameter data The GET STREAM STATUS parameter data (see table 56) contains an eight-byte header followed by zero or more stream status descriptors. Table 56 GET STREAM STATUS parameter data Bit Byte 7 0 ... 3 4 5 6 7 6 5 4 3 2 1 0 PARAMETER DATA LENGTH (n-7) Reserved (MSB) NUMBER OF OPEN STREAMS (LSB) stream status descriptors 8 ... 15 (MSB) stream status descriptor [first] (LSB) ... n-7 ...
PAGE 91
www.seagate.com 3.5.1.1 Direct Access Block commands (SPC-5 and SBC-4) Stream status descriptor The stream status descriptor (see table 57) contains stream status information for one open stream. Table 57 Stream status descriptor format Bit Byte 7 0 1 2 3 4 ... 7 6 5 4 3 2 1 0 Reserved (MSB) STREAM IDENTIFIER (LSB) Reserved STREAM IDENTIFIER field The STREAM IDENTIFIER field contains the stream identifier of an open stream. 3.5.1.
PAGE 92
www.seagate.com 3.6 Direct Access Block commands (SPC-5 and SBC-4) INQUIRY command 3.6.1 INQUIRY command introduction The INQUIRY command (see table 58) requests that information regarding the logical unit and SCSI target device be sent to the application client.
PAGE 93
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) ALLOCATION LENGTH field The ALLOCATION LENGTH field is defined in 2.2.6. If EVPD is set to zero, the allocation length should be at least five, 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 5.4) is returned.
PAGE 94
www.seagate.com 3.6.
PAGE 95
www.seagate.com Table 59 Direct Access Block commands (SPC-5 and SBC-4) Standard INQUIRY data format Bit Byte 7 6 5 4 3 2 1 0 Vendor specific parameters 96 (MSB) Copyright Notice (Vendor specific) n (LSB) PERIPHERAL QUALIFIER and PERIPHERAL DEVICE TYPE fields The PERIPHERAL QUALIFIER field and PERIPHERAL DEVICE TYPE field identify the peripheral device connected to the logical unit.
PAGE 96
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) . Table 61 PERIPHERAL DEVICE TYPE Code Doc. [a] Description 00h SBC-4 Direct access block device (e.g., magnetic disk) 01h SSC-3 Sequential-access device (e.g., magnetic tape) 02h SSC 03h SPC-2 04h SBC 05h MMC-5 Printer device Processor device Write-once device (e.g., some optical disks) CD/DVD device Scanner device (obsolete) 06h 07h SBC 08h SMC-3 Optical memory device (e.g.
PAGE 97
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) VERSION field The VERSION field indicates the implemented version of the SPC standard and is defined in table 62 . Table 62 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 ANSI INCITS 408-2005 (SPC-3).
PAGE 98
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) ACC (Access Controls Coordinator) bit 1 An Access Controls Coordinator (ACC) bit set to one indicates that the SCSI target device contains an access controls coordinator that may be addressed through this logical unit. 0 An ACC bit set to zero indicates that no access controls coordinator may be addressed through this logical unit.
PAGE 99
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) If the logical unit supports the BQUE bit, the CMDQUE bit and BQUE bit indicate whether the logical unit supports the full task management model as described in table 64.
PAGE 100
www.seagate.com 3.6.3 Direct Access Block commands (SPC-5 and SBC-4) Vital product data The application client requests the vital product data information by setting the EVPD bit to one and specifying the page code of a vital product data. See 5.4 for details about vital product data. The information returned consists of configuration data (e.g., vendor identification, product identification, model, serial number), manufacturing data (e.g.
PAGE 101
www.seagate.com 3.7 Direct Access Block commands (SPC-5 and SBC-4) LOG SELECT command The LOG SELECT command (see table 65) provides a means for an application client to manage statistical information maintained by the SCSI target device about the SCSI target device or its logical units. Device servers that implement the LOG SELECT command shall also implement the LOG SENSE command. Structures in the form of log parameters within log pages are defined as a way to manage the log data.
PAGE 102
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) PC (Page Control) field The page control (PC) field specifies which data counter parameter values (i.e., when the FORMAT AND LINKING field (see 5.2.2) contains 00b or 10b) shall be processed by a device server in response to a LOG SELECT command as described in table 66. The PC field shall be ignored for list parameters (i.e., when the FORMAT AND LINKING field contains 01b or 11b).
PAGE 103
www.seagate.com 3.7.1 Direct Access Block commands (SPC-5 and SBC-4) Processing LOG SELECT when the parameter list length is zero If the PARAMETER LIST LENGTH field is set to zero (i.e., when there is no parameter data being sent with a LOG SELECT command), the SCSI target device responds by processing the log parameter values as described in this subclause.
PAGE 104
www.seagate.com Table 68 Direct Access Block commands (SPC-5 and SBC-4) PCR bit, SP bit, and PC field meanings when parameter list length is zero (Sheet 1 of 2) PCR bit SP bit PC field Description 0b 0b 0xb 0b 1b 00b 0b 1b 01b 0b xb 10b 0b xb 11b 1b 0b xxb This is not an error. The device server shall make no changes to any log parameter values and shall not save any values to non-volatile media.
PAGE 105
www.seagate.
PAGE 106
www.seagate.com 3.8 Direct Access Block commands (SPC-5 and SBC-4) LOG SENSE command The LOG SENSE command (see table 69) provides a means for the application client to retrieve statistical or other operational information maintained by the SCSI target device about the SCSI target device or its logical units. It is a complementary command to the LOG SELECT command. See clause 4.2 of this manual for more information on returned log pages.
PAGE 107
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) PAGE CODE and SUBPAGE CODE Fields The PAGE CODE field and SUBPAGE CODE field specify which log page of data is being requested. If the log page code and subpage combination is reserved or not implemented, 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.
PAGE 108
www.seagate.com 3.9 Direct Access Block commands (SPC-5 and SBC-4) MODE SELECT(6) command The MODE SELECT(6) command (see table 70) provides a means for the application client to specify medium, logical unit, or peripheral device parameters to the device server. Device servers that implement the MODE SELECT(6) command shall also implement the MODE SENSE(6) command.
PAGE 109
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) SP (save pages) bit 0 A save pages (SP) bit set to zero specifies that the device server shall perform the specified MODE SELECT operation, and shall not save any mode pages.
PAGE 110
www.seagate.com 3.10 Direct Access Block commands (SPC-5 and SBC-4) MODE SELECT (10) command The MODE SELECT(10) command (see table 72) provides a means for the application client to specify medium, logical unit, or peripheral device parameters to the device server. See the MODE SELECT(6) command (see 3.9) for a description of the fields and operation of this command.
PAGE 111
www.seagate.com 3.11 Direct Access Block commands (SPC-5 and SBC-4) MODE SENSE(6) command 3.11.1 MODE SENSE(6) command introduction The MODE SENSE(6) command (see table 73) provides a means for a device server to report parameters to an application client. It is a complementary command to the MODE SELECT(6) command. Device servers that implement the MODE SENSE(6) command shall also implement the MODE SELECT(6) command.
PAGE 112
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) An application client may request any one or all of the supported mode pages from the device server. If an application client issues a MODE SENSE command with a page code or subpage code value not implemented by the logical unit, 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.
PAGE 113
www.seagate.com 3.11.1.3 Direct Access Block commands (SPC-5 and SBC-4) Default values A PC field value of 10b requests that the device server return the default values of the mode parameters. Unsupported parameters shall be set to zero. Default values should be accessible even if the logical unit is not ready. 3.11.1.4 Saved values A PC field value of 11b requests that the device server return the saved values of the mode parameters.
PAGE 114
www.seagate.com 3.12 Direct Access Block commands (SPC-5 and SBC-4) MODE SENSE(10) command The MODE SENSE(10) command (see table 75) provides a means for a device server to report parameters to an application client. It is a complementary command to the MODE SELECT(10) command. Device servers that implement the MODE SENSE(10) command shall also implement the MODE SELECT(10) command.
PAGE 115
www.seagate.com 3.13 Direct Access Block commands (SPC-5 and SBC-4) PERSISTENT RESERVE IN command 3.13.1 PERSISTENT RESERVE IN command introduction The PERSISTENT RESERVE IN command (see table 76) is used to obtain information about persistent reservations and reservation keys (i.e., registrations) that are active within a device server. This command is used in conjunction with the PERSISTENT RESERVE OUT command (see 3.14).
PAGE 116
www.seagate.com 3.13.2 Direct Access Block commands (SPC-5 and SBC-4) READ KEYS service action The READ KEYS service action requests that the device server return a parameter list containing a header and a list of each currently registered I_T nexus’ reservation key. If multiple I_T nexuses have registered with the same key, then that key value shall be listed multiple times, once for each such registration. For more information on READ KEYS see SPC-5.
PAGE 117
www.seagate.com 3.13.3 3.13.3.1 Direct Access Block commands (SPC-5 and SBC-4) READ RESERVATION service action READ RESERVATION service action introduction The READ RESERVATION service action requests that the device server return a parameter list containing a header and the persistent reservation, if any, that is present in the device server. For more information on READ RESERVATION see SPC-5. 3.13.3.
PAGE 118
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) When a persistent reservation is held, the format for the parameter data provided in response to a PERSISTENT RESERVE IN command with the READ RESERVATION service action is shown in table 80. Table 80 PERSISTENT RESERVE IN parameter data for READ RESERVATION with reservation Bit Byte 7 0 (MSB) 6 5 4 ... 3 2 1 PRGENERATION 3 4 (LSB) (MSB) ... ADDITIONAL LENGTH (0000-0010h) 7 8 0 (LSB) (MSB) ...
PAGE 119
www.seagate.com 3.13.3.3 Direct Access Block commands (SPC-5 and SBC-4) Persistent reservations scope The SCOPE field (see table 81) shall be set to LU_SCOPE, specifying that the persistent reservation applies to the entire logical unit.
PAGE 120
www.seagate.com 3.13.4 Direct Access Block commands (SPC-5 and SBC-4) REPORT CAPABILITIES service action The REPORT CAPABILITIES service action requests that the device server return information on persistent reservation features. The format for the parameter data provided in response to a PERSISTENT RESERVE IN command with the REPORT CAPABILITIES service action is shown in table 83.
PAGE 121
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) PTPL_C (Persist Through Power Loss Capable) bit 1 A Persist Through Power Loss Capable (PTPL_C) bit set to one indicates that the device server supports the persist through power loss capability see SPC-5 for persistent reservations and the APTPL bit in the PERSISTENT RESERVE OUT command parameter data. 0 An PTPL_C bit set to zero indicates that the device server does not support the persist through power loss capability.
PAGE 122
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) PERSISTENT RESERVATION TYPE MASK field The PERSISTENT RESERVATION TYPE MASK field (see table 85) contains a bit map that indicates the persistent reservation types that are supported by the device server.
PAGE 123
www.seagate.com 3.13.5 Direct Access Block commands (SPC-5 and SBC-4) READ FULL STATUS service action The READ FULL STATUS service action requests that the device server return a parameter list describing the registration and persistent reservation status of each currently registered I_T nexus for the logical unit. For more information on READ FULL STATUS see SPC-5.
PAGE 124
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) The format of the full status descriptors is shown in table 87. Each full status descriptor describes one or more registered I_T nexuses. The device server shall return persistent reservations status information for every registered I_T nexus. Table 87 PERSISTENT RESERVE IN full status descriptor format Bit Byte 7 0 ... 7 8 ... 11 12 13 14 ... 17 18 19 20 ... 23 24 ...
PAGE 125
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) ALL_TG_PT (All Target Ports) bit 0 An All Target Ports (ALL_TG_PT) bit set to zero indicates that this full status descriptor represents a single I_T nexus. 1 An ALL_TG_PT bit set to one indicates that: a) This full status descriptor represents all the I_T nexuses that are associated with both: 1. The initiator port specified by the TRANSPORTID field; and 2.
PAGE 126
www.seagate.com 3.14 Direct Access Block commands (SPC-5 and SBC-4) PERSISTENT RESERVE OUT command 3.14.1 PERSISTENT RESERVE OUT command introduction The PERSISTENT RESERVE OUT command (see table 88) is used to request service actions that reserve a logical unit for the exclusive or shared use of a particular I_T nexus. The command uses other service actions to manage and remove such persistent reservations.
PAGE 127
www.seagate.com 3.14.2 Direct Access Block commands (SPC-5 and SBC-4) PERSISTENT RESERVE OUT service actions When processing the PERSISTENT RESERVE OUT service actions, the device server shall increment the PRGENERATION value as specified in 3.13.2. The PERSISTENT RESERVE OUT command service actions are defined in table 89. Table 89 Code PERSISTENT RESERVE OUT service action codes Name Description PRGENERATION field incremented (see 3.13.
PAGE 128
www.seagate.com 3.14.3 Direct Access Block commands (SPC-5 and SBC-4) Basic PERSISTENT RESERVE OUT parameter list The parameter list format shown in table 90 shall be used by the PERSISTENT RESERVE OUT command with any service action except the REGISTER AND MOVE service action. All fields shall be sent, even if the field is not required for the specified service action and scope values. Table 90 PERSISTENT RESERVE OUT parameter list Bit Byte 7 0 ... 7 8 ... 15 16 ... 19 20 21 22 23 24 ...
PAGE 129
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) SERVICE ACTION RESERVATION KEY field The SERVICE ACTION RESERVATION KEY field contains information needed for the following service actions: REGISTER, REGISTER AND IGNORE EXISTING KEY, PREEMPT, PREEMPT AND ABORT, and REPLACE LOST RESERVATION. The SERVICE ACTION RESERVATION KEY field is ignored for the following service actions: RESERVE, RELEASE, and CLEAR.
PAGE 130
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) TRANSPORTID PARAMETER DATA LENGTH field The TRANSPORTID PARAMETER DATA LENGTH field specifies the number of bytes of TRANSPORTIDs that follow.
PAGE 131
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) Table 92 summarizes which fields are set by the application client and interpreted by the device server for each service action and scope value.
PAGE 132
www.seagate.com 3.14.4 Direct Access Block commands (SPC-5 and SBC-4) Parameter list for the PERSISTENT RESERVE OUT command with REGISTER AND MOVE service The parameter list format shown in table 94 shall be used by the PERSISTENT RESERVE OUT command with REGISTER AND MOVE service action. Table 94 PERSISTENT RESERVE OUT command with REGISTER AND MOVE service Bit Byte 7 0 (MSB) 6 5 4 ... 3 2 1 RESERVATION KEY 7 8 (LSB) (MSB) ...
PAGE 133
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) APTPL (Activate Persist Through Power Loss) bit 1 The Activate Persist Through Power Loss (APTPL) bit set to one is optional. If a device server that does not support an APTPL bit set to one receives that value, it shall return CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN PARAMETER LIST.
PAGE 134
www.seagate.com 3.15 Direct Access Block commands (SPC-5 and SBC-4) READ (6) command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. The READ (6) command (see table 95) requests that the device server read the specified logical block(s) and transfer them to the data-in buffer. Each logical block read includes user data and, if the medium is formatted with protection information enabled, protection information.
PAGE 135
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) The device server shall check the protection information read from the medium before returning status for the command as described in table 96.
PAGE 136
www.seagate.com 3.16 Direct Access Block commands (SPC-5 and SBC-4) READ (10) command The READ (10) command (see table 97) requests that the device server read the specified logical block(s) and transfer them to the data-in buffer. Each logical block read includes user data and, if the medium is formatted with protection information enabled, protection information.
PAGE 137
www.seagate.
PAGE 138
www.seagate.
PAGE 139
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) DPO (Disable Page Out) bit 0 A Disable Page Out (DPO) bit set to zero specifies that the retention priority shall be determined by the RETENTION PRIORITY fields in the Caching mode page (see 5.3.9). 1 A DPO bit set to one specifies that the device server shall assign the logical blocks accessed by this command the lowest retention priority for being fetched into or retained by the cache.
PAGE 140
www.seagate.com 3.17 Direct Access Block commands (SPC-5 and SBC-4) READ (12) command The READ (12) command (see table 99) requests that the device server read the specified logical block(s) and transfer them to the data-in buffer. Each logical block read includes user data and, if the medium is formatted with protection information enabled, protection information.
PAGE 141
www.seagate.com 3.18 Direct Access Block commands (SPC-5 and SBC-4) READ (16) command The READ (16) command (see table 100) requests that the device server read the specified logical block(s) and transfer them to the data-in buffer. Each logical block read includes user data and, if the medium is formatted with protection information enabled, protection information.
PAGE 142
www.seagate.com 3.19 Direct Access Block commands (SPC-5 and SBC-4) READ (32) command The READ (32) command (see table 102) requests that the device server read the specified logical block(s) and transfer them to the data-in buffer. Each logical block read includes user data and, if the medium is formatted with protection information enabled, protection information.
PAGE 143
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) See the READ (10) command for the definitions of the GROUP NUMBER field, the RDPROTECT field, the DPO bit, the FUA bit, the RARC bit, the LOGICAL BLOCK ADDRESS field, and the TRANSFER LENGTH field.
PAGE 144
www.seagate.com 3.20 Direct Access Block commands (SPC-5 and SBC-4) READ BUFFER (10) command 3.20.1 READ BUFFER (10) command introduction The READ BUFFER (10) command (see table 103) is used in conjunction with the WRITE BUFFER command as a diagnostic function for testing memory in the SCSI device and the integrity of the service delivery subsystem. This command shall not alter the medium. Table 103 READ BUFFER (10) command Bit Byte 7 0 1 2 3 ... 5 6 ...
PAGE 145
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) ALLOCATION LENGTH field If the MODE field is not set to one, the ALLOCATION LENGTH field is defined in 2.2.6. CONTROL byte The CONTROL byte is defined in Clause 2.2.7. 3.20.2 Combined header and data mode (00h) The four-byte READ BUFFER header (see table 105) is followed by data bytes from the buffer. Table 105 READ BUFFER header Bit Byte 7 0 1 ... 3 4 ...
PAGE 146
www.seagate.com 3.20.5 Direct Access Block commands (SPC-5 and SBC-4) Descriptor mode (03h) In this mode, a maximum of four bytes of READ BUFFER descriptor information is returned. The device server shall return the descriptor information for the buffer specified by the BUFFER ID field (see the description of the buffer ID in 3.20.4). If there is no buffer associated with the specified buffer ID, the device server shall return all zeros in the READ BUFFER descriptor.
PAGE 147
www.seagate.com 3.20.6 Direct Access Block commands (SPC-5 and SBC-4) Echo buffer mode (0Ah) In this mode the device server transfers data to the application client from the echo buffer that was written by the most recent WRITE BUFFER command with the mode field set to echo buffer received on the same I_T nexus. The READ BUFFER command shall return the same number of bytes of data as received in the prior WRITE BUFFER command with the mode field set to echo buffer, limited by the allocation length.
PAGE 148
www.seagate.com 3.20.8 Direct Access Block commands (SPC-5 and SBC-4) Error history mode (1Ch) 3.20.8.1 Error history overview This mode is used to manage and retrieve error history (see SPC-5).
PAGE 149
www.seagate.com 3.20.8.2 Direct Access Block commands (SPC-5 and SBC-4) Error history directory Whenever allowed by established error history I_T nexus constraints (see 3.20.8.1), if any, all error history device server actions return an error history directory (see table 112). Some error history device server actions also discard the existing error history snapshot (see SPC-5) and create a new error history snapshot (see table 110).
PAGE 150
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) The error history directory is defined in table 112. Table 112 Error history directory Bit Byte 7 0 (MSB) 6 5 4 3 2 1 0 . ... T10 VENDOR IDENTIFICATION (LSB) 7 8 VERSION Reserved 9 EHS_RETRIEVED EHS_SOURCE CLR_SUP 10 Reserved ... 29 30 (MSB) DIRECTORY LENGTH (n-31) 31 (LSB) Error history directory list 32 Error history directory entry [first] (see table 115) ... . 39 ...
PAGE 151
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) EHS_RETRIEVED (error history retrieved) field The error history retrieved (EHS_RETRIEVED) field (see table 113) indicates whether a clear error history device server action has been requested for the error history snapshot. EHS_RETRIEVED field shall be set to 00b or 10b when the error history snapshot is created.
PAGE 152
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) The error history directory list contains an error history directory entry (see table 115) for each supported buffer ID in the range of 00h to EFh. The first entry shall be for buffer ID 00h and the entries shall be in order of ascending buffer IDs. The supported buffer IDs are not required to be contiguous. There shall not be any entries for buffer IDs greater than or equal to F0h.
PAGE 153
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) BUFFER SOURCE field If the SUPPORTED BUFFER ID field is set to 10h to EFh, the BUFFER SOURCE field (see table 117) indicates the source field the error history buffer indicated by the SUPPORTED BUFFER ID field. If the SUPPORTED BUFFER ID field is set to 10h to EFh, the BUFFER SOURCE field should be ignored by the application client.
PAGE 154
www.seagate.com 3.21 Direct Access Block commands (SPC-5 and SBC-4) READ BUFFER (16) command The READ BUFFER (16) command (see table 118) requests that the device server perform the actions defined for the READ BUFFER (10) command (see 3.20). Table 118 READ BUFFER (16) command Bit Byte 0 1 2 ... 9 10 ...
PAGE 155
www.seagate.com 3.22 Direct Access Block commands (SPC-5 and SBC-4) READ CAPACITY (10) command 3.22.1 READ CAPACITY (10) overview The READ CAPACITY (10) command (see table 119) requests that the device server transfer 8 bytes of parameter data describing the capacity and medium format of the direct-access block device to the data-in buffer. This command may be processed as if it has a HEAD OF QUEUE task attribute.
PAGE 156
www.seagate.com 3.22.2 Direct Access Block commands (SPC-5 and SBC-4) READ CAPACITY (10) parameter data The READ CAPACITY (10) parameter data is defined in table 120. Any time the READ CAPACITY (10) parameter data changes, the device server should establish a unit attention condition as described in SBC-4. Table 120 READ CAPACITY (10) parameter data Bit Byte 7 0 (MSB) 6 5 ... 4 3 2 1 RETURNED LOGICAL BLOCK ADDRESS 3 4 0 (LSB) (MSB) ...
PAGE 157
www.seagate.com 3.23 Direct Access Block commands (SPC-5 and SBC-4) READ CAPACITY (16) command 3.23.1 READ CAPACITY (16) command overview The READ CAPACITY (16) command (see table 121) requests that the device server transfer parameter data describing the capacity and medium format of the direct-access block device to the data-in buffer. This command is mandatory if the logical unit supports protection information and optional otherwise (see SBC-4).
PAGE 158
www.seagate.com 3.23.2 Direct Access Block commands (SPC-5 and SBC-4) READ CAPACITY (16) parameter data The READ CAPACITY (16) parameter data is defined in table 122. Any time the READ CAPACITY (16) parameter data changes, the device server should establish a unit attention condition as described in SPC-5. Table 122 READ CAPACITY (16) parameter data Bit Byte 7 6 0 ... 7 8 ... 11 12 13 14 15 16 ...
PAGE 159
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) P_TYPE (Protection Type) field and PROT_EN bit The protection type (P_TYPE) field and the PROT_EN bit (see table 124) indicate the logical unit’s current type of protection.
PAGE 160
www.seagate.com 3.24 Direct Access Block commands (SPC-5 and SBC-4) READ DEFECT DATA (10) command 3.24.1 READ DEFECT DATA (10) command overview The READ DEFECT DATA (10) command (see table 126) requests that the device server transfer the medium defect data to the data-in buffer. Table 126 Bit Byte 0 1 2 3 ...
PAGE 161
www.seagate.com 3.24.2 Direct Access Block commands (SPC-5 and SBC-4) READ DEFECT DATA (10) parameter data The READ DEFECT DATA (10) parameter data (see table 127) contains a four-byte header, followed by zero or more address descriptors. Table 127 Bit Byte READ DEFECT DATA (10) parameter data 7 6 5 4 0 3 2 1 0 Reserved 1 Reserved 2 PLISTV GLISTV DEFECT LIST FORMAT (MSB) DEFECT LIST LENGTH (N - 3) 3 (LSB) Defect List (if any) 4 ...
PAGE 162
www.seagate.com 3.25 Direct Access Block commands (SPC-5 and SBC-4) READ DEFECT DATA (12) command 3.25.1 READ DEFECT DATA (12) command overview The READ DEFECT DATA (12) command (see table 128) requests that the device server transfer the medium defect data to the data-in buffer. Table 128 Bit Byte 0 1 2 ... 5 6 ...
PAGE 163
www.seagate.com 3.25.2 Direct Access Block commands (SPC-5 and SBC-4) READ DEFECT DATA (12) parameter data The READ DEFECT DATA (12) parameter data (see table 129) contains an eight byte header, followed by zero or more address descriptors. Table 129 Bit Byte 0 1 2 3 4 ... 7 READ DEFECT DATA (12) parameter data 7 6 Reserved 5 4 3 Reserved PLISTV GLISTV Reserved Reserved 2 1 0 DEFECT LIST FORMAT (MSB) DEFECT LIST LENGTH (N - 7) (LSB) Defect List (if any) 8 ...
PAGE 164
www.seagate.com 3.26 Direct Access Block commands (SPC-5 and SBC-4) READ LONG (10) command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. The READ LONG (10) command (see table 130) requests that the device server transfer data from a single logical block to the data-in buffer.
PAGE 165
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) LOGICAL BLOCK ADDRESS field See 2.2.3 for the definition of the LOGICAL BLOCK ADDRESS field. PBLOCK bit If there is more than one logical block per physical block (i.e., the LOGICAL BLOCKS PER PHYSICAL BLOCK EXPONENT field in the READ CAPACITY (16) data is set to a non-zero value), then the device server shall support the physical block (PBLOCK) bit.
PAGE 166
www.seagate.com 3.27 Direct Access Block commands (SPC-5 and SBC-4) READ LONG (16) command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. The READ LONG (16) command (see table 131) requests that the device server transfer data from a single logical block to the data-in buffer.
PAGE 167
www.seagate.com 3.28 Direct Access Block commands (SPC-5 and SBC-4) REASSIGN BLOCKS command 3.28.1 REASSIGN BLOCKS command overview The REASSIGN BLOCKS command (see table 132) requests that the device server reassign defective logical blocks to another area on the medium set aside for this purpose. The device server should also record the location of the defective logical blocks in the GLIST, if supported. This command shall not alter the contents of the PLIST.
PAGE 168
www.seagate.com 3.28.2 Direct Access Block commands (SPC-5 and SBC-4) REASSIGN BLOCKS parameter list The REASSIGN BLOCKS parameter list (see table 133) contains a four-byte parameter list header followed by a defective LBA list containing one or more LBAs. Table 133 REASSIGN BLOCKS parameter list Bit Byte 7 6 5 4 3 2 1 0 1 0 0 ... Parameter list header (see table 134 or table 135) 3 4 ...
PAGE 169
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) DEFECTIVE LBA LIST field The DEFECTIVE LBA LIST field contains a list of defective LBAs. Each LBA is a four-byte field if the LONGLBA bit is set to zero or an eight-byte field if the LONGLBA bit is set to one. The LBAs shall be in ascending order.
PAGE 170
www.seagate.com 3.29 Direct Access Block commands (SPC-5 and SBC-4) RECEIVE DIAGNOSTIC RESULTS command The RECEIVE DIAGNOSTIC RESULTS command (see table 136) requests analysis data be sent to the application client Data-In Buffer after completion of a SEND DIAGNOSTIC command (see 3.46), or, optionally, SCSI-3 Enclosure Services (SES) pages be sent to the initiator. Support for SES is indicated in the drive product manual.
PAGE 171
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) ALLOCATION LENGTH field The ALLOCATION LENGTH field (see 2.2.6) shall specify the number of bytes the initiator has allocated for returned data. An ALLOCATION LENGTH of zero indicates that no data shall be transferred. Any other value indicates the maximum number of bytes that shall be transferred.
PAGE 172
www.seagate.
PAGE 173
www.seagate.com 3.30 Direct Access Block commands (SPC-5 and SBC-4) RELEASE (6) command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. The RELEASE(6) command (see table 139) is used to release a previously reserved logical unit. This subclause describes only those instances where the RELEASE(6) command differs from the RELEASE(10) command.
PAGE 174
www.seagate.com 3.31 Direct Access Block commands (SPC-5 and SBC-4) RELEASE (10) command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. 3.31.1 RELEASE (10) command introduction The RELEASE(10) command (see table 140) is used to release a previously reserved logical unit.
PAGE 175
www.seagate.com 3.31.2 Direct Access Block commands (SPC-5 and SBC-4) Logical unit release Logical unit reservation release is mandatory if the RELEASE(10) command is implemented. This command shall cause the device server to terminate all non-third-party logical unit reservations that are active from the initiator to the specified logical unit. 3.31.3 Third-party release Third-party reservation release is optional if the RELEASE(10) command is implemented.
PAGE 176
www.seagate.com 3.32 Direct Access Block commands (SPC-5 and SBC-4) REPORT IDENTIFYING INFORMATION The REPORT IDENTIFYING INFORMATION command requests that the device server send device identification information to the application client. The device server shall return the same identifying information regardless of the I_T nexus being used to retrieve the identifying information.
PAGE 177
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) INFORMATION TYPE field The INFORMATION TYPE field (see table 143) specifies the type of information to be reported. Table 143 INFORMATION TYPE Code Description 0000000b Peripheral device identifying information 0000010b Length Reference 0 to 64 bytes Table 33 Peripheral device text identifying information. 65 to 512bytes Table 33 1111111b Identifying information supported.
PAGE 178
www.seagate.com 3.32.1 Direct Access Block commands (SPC-5 and SBC-4) IDENTIFYING INFORMATION SUPPORTED parameter data The REPORT IDENTIFYING INFORMATION parameter data format used when the INFORMATION TYPE field is set to 1111111b is shown in table 145. Table 145 Bit Byte REPORT IDENTIFYING INFORMATION SUPPORTED parameter data 7 6 5 4 3 2 1 0 0 Reserved 1 2 (MSB) IDENTIFYING INFORMATION LENGTH (n - 3) 3 (LSB) Identifying information descriptor list 4 ...
PAGE 179
www.seagate.com 3.33 Direct Access Block commands (SPC-5 and SBC-4) REPORT LUNS command The REPORT LUNS command (see table 147) requests that the peripheral device logical unit inventory accessible to the I_T nexus be sent to the application client. The logical unit inventory is a list that shall include the logical unit numbers of all logical units having a PERIPHERAL QUALIFIER value of 000b (see table 60).
PAGE 180
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) The REPORT LUNS parameter data should be returned even though the device server is not ready for other commands. The report of the logical unit inventory should be available without incurring any media access delays.
PAGE 181
www.seagate.com 3.34 Direct Access Block commands (SPC-5 and SBC-4) REPORT SUPPORTED OPERATION CODES command REPORT SUPPORTED OPERATION CODES command overview 3.34.1 The REPORT SUPPORTED OPERATION CODES command (see table 150) requests the device server to return information on commands the addressed logical unit supports. This command uses the MAINTENANCE IN CDB format (see SPC-5).
PAGE 182
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) REPORTING OPTIONS field The REPORTING OPTIONS field specifies the information to be returned in the parameter data. Table 151 REPORTING OPTIONS field Code Descriptions Parameter Data Reference 000b A list of all operation codes and service actions supported by the logical unit shall be returned in the all_commands parameter data format. The REQUESTED OPERATION CODE CDB field and REQUESTED SERVICE ACTION CDB field shall be ignored. 3.34.
PAGE 183
www.seagate.com 3.34.2 Direct Access Block commands (SPC-5 and SBC-4) All_commands parameter data format The REPORT SUPPORTED OPERATION CODES all_commands parameter data format begins with a four-byte header that contains the length in bytes of the parameter data followed by a list of supported commands. Each command descriptor contains information about a single supported command CDB (i.e., one operation code and service action combination, or one non-service-action operation code).
PAGE 184
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) OPERATION CODE field The OPERATION CODE field contains the operation code of a command supported by the logical unit and shall be set to the value defined in table 153. SERVICE ACTION field The SERVICE ACTION field contains a supported service action of the supported operation code indicated by the OPERATION CODE field.
PAGE 185
www.seagate.com 3.34.3 Direct Access Block commands (SPC-5 and SBC-4) One_command parameter data format The REPORT SUPPORTED OPERATION CODES one_command parameter data format contains information about the CDB and a usage map for bits in the CDB for the command specified by the REPORTING OPTIONS, REQUESTED OPERATION CODE, and REQUESTED SERVICE ACTION fields in the REPORT SUPPORTED OPERATION CODES CDB.
PAGE 186
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) CDB SIZE field The CDB SIZE field contains the size of the CDB USAGE DATA field in the parameter data, and the number of bytes in the CDB for command being queried (i.e., the command specified by the REPORTING OPTIONS, REQUESTED OPERATION CODE, and REQUESTED SERVICE ACTION fields in the REPORT SUPPORTED OPERATION CODES CDB). CDB USAGE DATA field The CDB USAGE DATA field contains information about the CDB for the command being queried.
PAGE 187
www.seagate.com 3.34.4 3.34.4.1 Direct Access Block commands (SPC-5 and SBC-4) Command timeouts descriptor Overview The command timeouts descriptor (see table 157) returns timeout information for commands supported by the logical unit based on the time from the start of processing for the command to its reported completion. Values returned in the command timeouts descriptor do not include times that are outside the control of the device server (e.g.
PAGE 188
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) NOMINAL COMMAND PROCESSING TIMEOUT field A non-zero value in the NOMINAL COMMAND PROCESSING TIMEOUT field indicates the minimum amount of time in seconds the application client should wait prior to querying for the progress of the command identified by the parameter data that contains this command timeouts descriptor. A value of zero in the NOMINAL COMMAND PROCESSING TIMEOUT field indicates that no timeout is indicated.
PAGE 189
www.seagate.com 3.35 Direct Access Block commands (SPC-5 and SBC-4) REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS commands The REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS command (see table 159) requests the device server to return on task management functions (see SAM-5) the addressed logical unit supports. This command uses the MAINTENANCE IN CDB format (see SPC-5).
PAGE 190
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) The REPORT SUPPORTED TASK MANAGEMENT FUNCTIONS basic parameter data format is shown in table 160.
PAGE 191
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) QTS (QUERY TASK Supported) bit 1 A QTS bit set to one indicates the QUERY TASK task management function (see SAM-5) is supported by the logical unit. 0 A QTS bit set to zero indicates the QUERY TASK task management function is not supported. TRS (TARGET RESET Supported) bit 1 A TRS bit set to one indicates the TARGET RESET task management function (See SAM-2) is supported by the logical unit.
PAGE 192
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) CTSTS (CLEAR TASK SET Timeout Selector) bit 1 A CTSTS bit set to one indicates that the value in the TASK MANAGEMENT FUNCTIONS SHORT TIMEOUT field applies to the CLEAR TASK SET task management function. 0 A CTSTS bit set to zero indicates that the value in the TASK MANAGEMENT FUNCTIONS LONG TIMEOUT field applies to the CLEAR TASK SET task management function.
PAGE 193
www.seagate.com 3.36 Direct Access Block commands (SPC-5 and SBC-4) REPORT TIMESTAMP command The REPORT TIMESTAMP command (see table 162) requests the device server to return the current value of a device clock (see SPC-5). This command uses the MAINTENANCE IN CDB format (see SPC-5). Table 162 REPORT TIMESTAMP command Bit Byte 7 6 5 0 4 3 2 1 0 OPERATION CODE (A3h) 1 Reserved SERVICE ACTION (0Fh) 2 ... Reserved 5 6 (MSB) ...
PAGE 194
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) The format for the parameter data returned by the REPORT TIMESTAMP command is shown in table 163. Table 163 REPORT TIMESTAMP parameter data format Bit Byte 7 0 (MSB) 6 5 3 2 1 0 TIMESTAMP PARAMETER DATA LENGTH (0Ah) 1 2 4 (LSB) Reserved 3 TIMESTAMP ORIGIN Reserved 4 ...
PAGE 195
www.seagate.com 3.37 Direct Access Block commands (SPC-5 and SBC-4) REQUEST SENSE command The REQUEST SENSE command (see table 164) requests that the device server transfer sense data to the application client. Table 164 REQUEST SENSE command Bit Byte 7 6 5 4 3 0 OPERATION CODE (03h) 1 Reserved 2 1 0 DESC 2 Reserved 3 4 ALLOCATION LENGTH 5 CONTROL DESC (Descriptor Format) bit The descriptor format (DESC) bit specifies which sense data format shall be returned.
PAGE 196
www.seagate.com 3.38 Direct Access Block commands (SPC-5 and SBC-4) RESERVE(6) command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. The RESERVE(6) command (see table 165) is used to reserve a logical unit. This subclause describes only those instances where the RESERVE(6) command differs from the RESERVE(10) command.
PAGE 197
www.seagate.com 3.39 Direct Access Block commands (SPC-5 and SBC-4) RESERVE (10) command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. 3.39.1 RESERVE (10) command introduction The RESERVE(10) command (see table 166) is used to reserve a logical unit.
PAGE 198
www.seagate.com 3.39.3 Direct Access Block commands (SPC-5 and SBC-4) Third-party reservation Third-party reservations are mandatory if the RESERVE(10) command is implemented. The third-party reservation for the RESERVE(10) command allows an application client to reserve a logical unit within a logical unit for another SCSI device. This is intended for use in multiple initiator systems that use the COPY or EXTENDED COPY command.
PAGE 199
www.seagate.com 3.40 Direct Access Block commands (SPC-5 and SBC-4) REZERO UNIT command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products.
PAGE 200
www.seagate.com 3.41 Direct Access Block commands (SPC-5 and SBC-4) SANITIZE command 3.41.1 SANITIZE command introduction The SANITIZE command (see table 169) requests that the device server perform a sanitize operation. This command shall be processed as if it has a HEAD OF QUEUE task attribute. Table 169 Bit Byte SANITIZE command (48h) 7 6 5 IMMED ZNR AUSE 0 4 3 2 1 0 OPERATION CODE (48h) 1 SERVICE ACTION 2 ...
PAGE 201
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) PARAMETER LIST LENGTH field The PARAMETER LIST LENGTH field specifies the length in bytes of the parameter data that shall be sent from the application client to the device server. A PARAMETER LIST LENGTH field set to zero specifies that no data shall be transferred. CONTROL byte The CONTROL byte is described in clause 2.2.7. 3.41.2 SANITIZE service actions The SANITIZE command service actions are defined in (see table 170).
PAGE 202
www.seagate.com 3.41.3 Direct Access Block commands (SPC-5 and SBC-4) SANITIZE command with OVERWRITE service action 3.41.3.1 OVERWRITE service action introduction The OVERWRITE service action (see table 170) performs a sanitize operation using the overwrite method (see SBC-4). 3.41.3.2 OVERWRITE service action parameter list The parameter list format for the OVERWRITE service action is shown in Table 171.
PAGE 203
www.seagate.
PAGE 204
www.seagate.com 3.42 Direct Access Block commands (SPC-5 and SBC-4) SECURITY PROTOCOL IN command 3.42.1 Command description The SECURITY PROTOCOL IN command (see table 173) is used to retrieve security protocol information or the results of one or more SECURITY PROTOCOL OUT commands. Table 173 Bit Byte SECURITY PROTOCOL IN command 7 6 5 4 3 0 OPERATION CODE (A2h) 1 SECURITY PROTOCOL 2 INC_512 5 6 1 0 SECURITY PROTOCOL SPECIFIC 3 4 2 Reserved Reserved (MSB) ...
PAGE 205
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) INC_512 (512 Increment) 0 0An INC_512 bit set to zero specifies that the ALLOCATION LENGTH field (see 2.2.6) expresses the number of bytes to be transferred. 1 1A 512 increment (INC_512) bit set to one specifies that the ALLOCATION LENGTH field (see 2.2.6) expresses the maximum number of bytes available to receive data in increments of 512 bytes (e.g., a value of one means 512 bytes, two means 1,024 bytes, etc.).
PAGE 206
www.seagate.com 3.42.2 Direct Access Block commands (SPC-5 and SBC-4) Security protocol information description 3.42.2.1 Overview The purpose of security protocol information security protocol (i.e., the SECURITY PROTOCOL field set to 00h in a SECURITY PROTOCOL IN command) is to transfer security protocol related information from the logical unit.
PAGE 207
www.seagate.com 3.42.2.3 Direct Access Block commands (SPC-5 and SBC-4) Supported security protocols list description If the SECURITY PROTOCOL field is set to 00h and the SECURITY PROTOCOL SPECIFIC field is set to 0000h in a SECURITY PROTOCOL IN command, the parameter data shall have the format shown in table 176. Table 176 Bit Byte Supported security protocols SECURITY PROTOCOL IN parameter data 7 6 5 4 3 2 1 0 0 ...
PAGE 208
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) 3.42.2.4 Certificate data description 3.42.2.4.1 Certificate overview A certificate is either an X.509 Public Key Certificate or an X.509 Attribute Certificate depending on the capabilities of the logical unit. If the SECURITY PROTOCOL field is set to 00h and the SECURITY PROTOCOL SPECIFIC field is set to 0001h in a SECURITY PROTOCOL IN command, the parameter data shall have the format shown in table 177.
PAGE 209
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) 3.42.2.5 Security compliance information description 3.42.2.5.1 Security compliance information overview The security compliance information parameter data contains information about security standards that apply to this SCSI target device.
PAGE 210
www.seagate.com 3.42.2.5.2 Direct Access Block commands (SPC-5 and SBC-4) Compliance descriptor overview The format of a compliance descriptor in the security compliance information SECURITY PROTOCOL IN parameter data is shown in table 177. Table 179 Compliance descriptor format Bit Byte 7 0 (MSB) 6 5 4 2 Compliance Descriptor Type 1 2 1 0 (LSB) Reserved 3 4 3 (MSB) ... COMPLIANCE DESCRIPTOR LENGTH (n-3) 7 (LSB) 8 ...
PAGE 211
www.seagate.com 3.42.2.5.3 Direct Access Block commands (SPC-5 and SBC-4) FIPS 140 compliance descriptor The FIPS 140 compliance descriptor (see table 181) contains information that may be used to locate information about a FIPS 140 certificate associated with the SCSI target device. The SCSI target device may or may not be operating in the mode specified by that certificate.
PAGE 212
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) REVISION field The REVISION field (see table 182) is an ASCII data field (see SPC-5) that indicates the FIPS 140 revision that applies to the SCSI target device. Table 182 REVISION field Code Related standard 32h FIPS 140-2 33h FIPS 140-3 all others OVERALL SECURITY LEVEL field The OVERALL SECURITY LEVEL field is an ASCII data field (see SPC-5) that indicates the FIPS 140 overall security level that is reported by NIST.
PAGE 213
www.seagate.com 3.43 Direct Access Block commands (SPC-5 and SBC-4) SECURITY PROTOCOL OUT command The SECURITY PROTOCOL OUT command (see table 183) is used to send data to the logical unit. The data sent specifies one or more operations to be performed by the logical unit. The format and function of the operations depends on the contents of the SECURITY PROTOCOL field (see table 184).
PAGE 214
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) INC_512 (512 Increment) 0 A INC_512 bit set to zero specifies that the TRANSFER LENGTH field indicates the number of bytes to be transferred. 1 INC_512 bit set to one specifies that the TRANSFER LENGTH field (see 2.2.4) expresses the number of bytes to be transferred in increments of 512 bytes (e.g., a value of one means 512 bytes, two means 1,024 bytes, etc.). Pad bytes shall be appended as needed to meet this requirement.
PAGE 215
www.seagate.com 3.44 Direct Access Block commands (SPC-5 and SBC-4) SEEK command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. Table 185 SEEK command (0Bh) Bit Byte 7 6 5 4 0 1 3 2 1 0 OPERATION CODE (0Bh) LUN MSB 2 3 LOGICAL BLOCK ADDRESS LSB 4 Reserved 5 CONTROL The Seek command (see table 185) requests that the disk drive seek to the specified logical block address.
PAGE 216
www.seagate.com 3.45 Direct Access Block commands (SPC-5 and SBC-4) SEEK EXTENDED command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. Table 186 SEEK command (2Bh) Bit Byte 7 6 5 4 0 1 3 2 1 0 OPERATION CODE (2Bh) LUN Reserved 2 ... LOGICAL BLOCK ADDRESS (MSB) ...
PAGE 217
www.seagate.com 3.46 Direct Access Block commands (SPC-5 and SBC-4) SEND DIAGNOSTIC command The SEND DIAGNOSTIC command (see table 187) requests the device server to perform diagnostic operations on the SCSI target device, on the logical unit, or on both. Logical units that support this command shall implement, at a minimum, the default self-test feature (i.e., the SELFTEST bit equal to one and a parameter list length of zero).
PAGE 218
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) PF (page format) bit 1 A page format (PF) bit set to one specifies that the SEND DIAGNOSTIC parameters and any parameters returned by a following RECEIVE DIAGNOSTIC RESULTS command with the PCV bit set to zero shall contain a single diagnostic page as defined in 5.1.1. 0 A PF bit set to zero specifies that all SEND DIAGNOSTIC parameters are vendor specific.
PAGE 219
www.seagate.com 3.47 Direct Access Block commands (SPC-5 and SBC-4) SET IDENTIFYING INFORMATION command The SET IDENTIFYING INFORMATION command (see table 189) requests that the device server set identifying information in the logical unit to the value received in the SET IDENTIFYING INFORMATION parameter list. The SET IDENTIFYING INFORMATION command is an extension to the SET PERIPHERAL DEVICE/COMPONENT DEVICE IDENTIFIER service action of the MAINTENANCE OUT command defined in SCC-2.
PAGE 220
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) INFORMATION TYPE field The INFORMATION TYPE specifies the identifying information type to be set. Table 190 INFORMATION TYPE code list Code Description 0000000b Peripheral device identifying information.
PAGE 221
www.seagate.com 3.48 Direct Access Block commands (SPC-5 and SBC-4) SET TIMESTAMP command The SET TIMESTAMP command (see table 192) requests the device server to initialize a device clock (see SPC-5) if the SCSIP bit is set to one in the Control Extension mode page (see 5.3.13). If the SCSIP bit is set to zero, the device server shall terminate the SET TIMESTAMP command with CHECK CONDITION status, with the sense key set to ILLEGAL REQUEST, and the additional sense code set to INVALID FIELD IN CDB.
PAGE 222
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) The format for the parameter data returned by the SET TIMESTAMP command is shown in table 193. Table 193 SET TIMESTAMP parameter data format Bit Byte 7 6 5 4 3 2 1 0 0 ... Reserved 3 4 ... TIMESTAMP 9 10 Reserved 11 Reserved TIMESTAMP field The TIMESTAMP field specifies the value to which a device clock shall be initialized (see SPC-5).
PAGE 223
www.seagate.com 3.49 Direct Access Block commands (SPC-5 and SBC-4) START STOP UNIT command The START STOP UNIT command (see table 194) requests that the device server change the power condition of the logical unit (see SBC-4) or load or eject the medium. This includes specifying that the device server enable or disable the direct-access block device for medium access operations by controlling power conditions and timers.
PAGE 224
www.seagate.com Table 195 Direct Access Block commands (SPC-5 and SBC-4) POWER CONDITION field and POWER CONDITION MODIFIER field POWER POWER CONDITION POWER CONDITION CONDITION Name MODIFIER value FORCE_IDLE_0 Ah FORCE_STANDBY_0 Bh All other combinations Description 0h Force the idle_a condition timer to be set to zero (see SPC-5). 1h Force the idle_b condition timer to be set to zero (see SPC-5). 2h Force the idle_c condition timer to be set to zero (see SPC-5).
PAGE 225
www.seagate.com 3.50 Direct Access Block commands (SPC-5 and SBC-4) STREAM CONTROL command 3.50.1 STREAM CONTROL command overview The STREAM CONTROL command (see table 196) requests the device server to open a stream and return the stream identifier in the return parameter data or close the stream specified in the STR_ID field in the CDB. This command uses the SERVICE ACTION IN (16) CDB format (see SBC-4 - Annex A.2).
PAGE 226
www.seagate.com 3.50.2 Direct Access Block commands (SPC-5 and SBC-4) STREAM CONTROL parameter data The STREAM CONTROL parameter data is defined in table 198. Table 198 Bit Byte STREAM CONTROL parameter data 7 6 0 1 ... 5 4 3 2 1 0 PARAMETER LENGTH (07h) Reserved 3 4 5 6 7 ASSIGNED_STR_ID Reserved PARAMETER LENGTH field The PARAMETER LENGTH field indicates the length of the parameter data and shall be set as shown in table104 for the STREAM CONTROL parameter data.
PAGE 227
www.seagate.com 3.51 Direct Access Block commands (SPC-5 and SBC-4) SYNCHRONIZE CACHE (10) command The SYNCHRONIZE CACHE (10) command (see table 199) requests that the device server ensure that the specified logical blocks have their most recent data values recorded in non-volatile cache and/or on the medium. Logical blocks include user data and, if the medium is formatted with protection information enabled, protection information.
PAGE 228
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) If the IMMED bit is set to one and the synchronize cache operation has not completed, then the SYNC_PROG field in the Caching mode page (see 5.3.9) defines device server behavior (see table 200). Table 200 SYNC_ PROG field description Code Description 00b The device server shall not terminate commands due to the synchronize cache operation and shall not provide pollable sense data.
PAGE 229
www.seagate.com 3.52 Direct Access Block commands (SPC-5 and SBC-4) SYNCHRONIZE CACHE (16) command The SYNCHRONIZE CACHE (16) command (see table 201) requests that the device server ensure that the specified logical blocks have their most recent data values recorded in non-volatile cache and/or on the medium. Logical blocks include user data and, if the medium is formatted with protection information enabled, protection information.
PAGE 230
www.seagate.com 3.53 Direct Access Block commands (SPC-5 and SBC-4) TEST UNIT READY command The TEST UNIT READY command (see table 202) provides a means to check if the logical unit is ready. This is not a request for a self-test. If the logical unit is able to accept an appropriate medium-access command without returning CHECK CONDITION status, this command shall return a GOOD status. If the logical unit is unable to become operational or is in a state such that an application client action (e.g.
PAGE 231
www.seagate.com 3.54 Direct Access Block commands (SPC-5 and SBC-4) UNMAP command 3.54.1 UNMAP command overview The UNMAP command (see table 204) requests that the device server cause one or more LBAs to be unmapped. The UNMAP command is one of the possible commands that shall be implemented by device servers supporting thin provisioning (see SBC-4). Table 204 UNMAP command Bit Byte 7 6 5 4 3 0 OPERATION CODE (42h) 1 Reserved 2 1 0 ANCHOR 2 ...
PAGE 232
www.seagate.com 3.54.2 Direct Access Block commands (SPC-5 and SBC-4) UNMAP parameter list The UNMAP parameter list (see table 205) contains the data sent by an application client along with an UNMAP command. Included in the data are an UNMAP parameter list header and block descriptors for LBA extents to be processed by the device server for the UNMAP command. The LBAs specified in the block descriptors may contain overlapping extents, and may be in any order.
PAGE 233
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) Table 206 defines an UNMAP block descriptor. Table 206 UNMAP block descriptor Bit Byte 7 0 (MSB) 6 ..... 5 4 3 2 1 UNMAP LOGICAL BLOCK ADDRESS 7 8 0 (LSB) (MSB) .... NUMBER OF LOGICAL BLOCKS 11 (LSB) 12 ..... Reserved 15 UNMAP LOGICAL BLOCK ADDRESS The UNMAP LOGICAL BLOCK ADDRESS field contains the first LBA of the UNMAP block descriptor to be unmapped.
PAGE 234
www.seagate.com 3.55 Direct Access Block commands (SPC-5 and SBC-4) VERIFY (10) command The VERIFY (10) command (see table 207) requests that the device server verify the specified logical block(s) on the medium. Each logical block includes user data and may include protection information, based on the VRPROTECT field and the medium format. Table 207 Bit Byte 0 1 2 ...
PAGE 235
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) BYTCHK field If the byte check (BYTCHK) field is set to 00b, then: a) no Data-Out Buffer transfer shall occur; b) for any mapped LBA specified by the command, the device server shall check the protection information from the verify operation based on the VRPROTECT field as defined in table 208; and c) for any unmapped LBA specified by the command, the verify operation shall complete without error.
PAGE 236
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) VERIFICATION LENGTH field The VERIFICATION LENGTH field specifies the number of contiguous logical blocks that shall be verified, starting with the logical block specified by the LOGICAL BLOCK ADDRESS field. If the BYTCHK field is set to one, the VERIFICATION LENGTH field also specifies the number of logical blocks that the device server shall transfer from the data-out buffer.
PAGE 237
www.seagate.
PAGE 238
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) If the BYTCHK field is set to 01b or 11b, then the device server shall check the protection information read from the medium based on the VRPROTECT field as described in table 209.
PAGE 239
www.seagate.
PAGE 240
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) If the BYTCHK field is set to 01b or 11b, then the device server shall check the protection information transferred from the data-out buffer based on the VRPROTECT field as described in table 210.
PAGE 241
www.seagate.
PAGE 242
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) If the BYTCHK field is set to 01b or 11b, then the device server shall perform a byte-by-byte comparison of protection information transferred from the data-out buffer with protection information read from the medium based on the VRPROTECT field as described in table 211.
PAGE 243
www.seagate.
PAGE 244
www.seagate.com 3.56 Direct Access Block commands (SPC-5 and SBC-4) VERIFY (12) command The VERIFY (12) command (see table 212) requests that the device server verify the specified logical block(s) on the medium. Each logical block includes user data and may include protection information, based on the VRPROTECT field and the medium format. Table 212 Bit Byte VERIFY (12) command 7 6 5 0 3 2 1 VRPROTECT DPO Reserved BYTCHK LOGICAL BLOCK ADDRESS 5 (LSB) (MSB) ...
PAGE 245
www.seagate.com 3.57 Direct Access Block commands (SPC-5 and SBC-4) VERIFY (16) command The VERIFY (16) command (see table 213) requests that the device server verify the specified logical block(s) on the medium. Each logical block includes user data and may include protection information, based on the VRPROTECT field and the medium format. Table 213 Bit Byte VERIFY (16) command 7 6 5 0 3 2 1 VRPROTECT DPO Reserved BYTCHK LOGICAL BLOCK ADDRESS 9 (LSB) (MSB) ...
PAGE 246
www.seagate.com 3.58 Direct Access Block commands (SPC-5 and SBC-4) VERIFY (32) command The VERIFY (32) command (see table 214) requests that the device server verify the specified logical block(s) on the medium. Each logical block includes user data and may include protection information, based on the VRPROTECT field and the medium format. The VERIFY (32) command shall only be processed if type 2 protection is enabled (see SPC-5). Table 214 Bit Byte 0 1 2 ...
PAGE 247
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) See the VERIFY (10) command (see 3.55) for the definitions of the GROUP NUMBER field, VRPROTECT field, DPO bit, BYTCHK field, LOGICAL BLOCK ADDRESS field, and VERIFICATION LENGTH field. When checking of the LOGICAL BLOCK REFERENCE TAG field is enabled (see table 208, table 209, table 210, and table 211 in 3.
PAGE 248
www.seagate.com 3.59 Direct Access Block commands (SPC-5 and SBC-4) WRITE (6) command This command has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. The WRITE (6) command (see table 215) requests that the device server transfer the specified logical block(s) from the data-out buffer and write them. Each logical block transferred includes user data but does not include protection information.
PAGE 249
www.seagate.com 3.60 Direct Access Block commands (SPC-5 and SBC-4) WRITE (10) command The WRITE (10) command (see table 216) requests that the device server transfer the specified logical block(s) from the data-out buffer and write them. Each logical block transferred includes user data and may include protection information, based on the WRPROTECT field and the medium format.
PAGE 250
www.seagate.
PAGE 251
www.seagate.
PAGE 252
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) FUA bit 0 A Force unit Access (FUA) bit set to zero specifies that the device server shall write the logical blocks to volatile cache (if any), non-volatile cache (if any), or the medium. 1 An FUA bit set to one specifies that the device server shall write the logical blocks to non-volatile cache (if any) or the medium.
PAGE 253
www.seagate.com 3.61 Direct Access Block commands (SPC-5 and SBC-4) WRITE (12) command The WRITE (12) command (see table 218) requests that the device server transfer the specified logical block(s) from the data-out buffer and write them. Each logical block transferred includes user data and may include protection information, based on the WRPROTECT field and the medium format.
PAGE 254
www.seagate.com 3.62 Direct Access Block commands (SPC-5 and SBC-4) WRITE (16) command The WRITE (16) command (see table 219) requests that the device server transfer the specified logical block(s) from the data-out buffer and write them. Each logical block transferred includes user data and may include protection information, based on the WRPROTECT field and the medium format.
PAGE 255
www.seagate.com 3.63 Direct Access Block commands (SPC-5 and SBC-4) WRITE (32) command The WRITE (32) command (see table 220) requests that the device server transfer the specified logical block(s) from the data-out buffer and write them. Each logical block transferred includes user data and may include protection information, based on the WRPROTECT field and the medium format.
PAGE 256
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) See the WRITE (10) command (see 3.60) for the definitions of the GROUP NUMBER field, the WRPROTECT field, the DPO bit, the FUA bit, the LOGICAL BLOCK ADDRESS field, and the TRANSFER LENGTH field. When checking of the LOGICAL BLOCK REFERENCE TAG field is enabled (see table 217 in 3.
PAGE 257
www.seagate.com 3.64 Direct Access Block commands (SPC-5 and SBC-4) WRITE AND VERIFY (10) command The WRITE AND VERIFY (10) command (see table 221) requests that the device server transfer the specified logical block(s) from the data-out buffer, write them to the medium, and then verify that they are correctly written. Each logical block includes user data and may include protection information, based on the WRPROTECT field and the medium format.
PAGE 258
www.seagate.com 3.65 Direct Access Block commands (SPC-5 and SBC-4) WRITE AND VERIFY (12) command The WRITE AND VERIFY (12) command (see table 222) requests that the device server transfer the specified logical block(s) from the data-out buffer, write them to the medium, and then verify that they are correctly written. Each logical block includes user data and may include protection information, based on the WRPROTECT field and the medium format.
PAGE 259
www.seagate.com 3.66 Direct Access Block commands (SPC-5 and SBC-4) WRITE AND VERIFY (16) command The WRITE AND VERIFY (16) command (see table 223) requests that the device server transfer the specified logical block(s) from the data-out buffer, write them to the medium, and then verify that they are correctly written. Each logical block includes user data and may include protection information, based on the WRPROTECT field and the medium format.
PAGE 260
www.seagate.com 3.67 Direct Access Block commands (SPC-5 and SBC-4) WRITE AND VERIFY (32) command The WRITE AND VERIFY (32) command (see table 224) requests that the device server transfer the specified logical block(s) from the data-out buffer, write them to the medium, and then verify that they are correctly written. Each logical block includes user data and may include protection information, based on the WRPROTECT field and the medium format.
PAGE 261
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) See the WRITE AND VERIFY (10) command (see 3.64) for the definitions of the GROUP NUMBER field, the WRPROTECT field, the DPO bit, the BYTCHK field, the LOGICAL BLOCK ADDRESS field, and the TRANSFER LENGTH field.
PAGE 262
www.seagate.com 3.68 Direct Access Block commands (SPC-5 and SBC-4) WRITE ATOMIC (16) command The WRITE ATOMIC (16) command (see table 225) requests that the device server. a) transfer logical block data from the Data-Out Buffer; and b) perform one or more atomic write operations (see SBC-4) of the LBAs specified by this command. Table 225 Bit Byte 0 1 2 ...
PAGE 263
www.seagate.com 3.69 Direct Access Block commands (SPC-5 and SBC-4) WRITE ATOMIC (32) command The WRITE ATOMIC (32) command (see table 226) requests that the device server perform the actions defined for the WRITE ATOMIC (16) command (see 3.68). The device server shall process a WRITE ATOMIC (32) command only if type 2 protection is enabled.
PAGE 264
www.seagate.com 3.70 Direct Access Block commands (SPC-5 and SBC-4) WRITE BUFFER command 3.70.1 WRITE BUFFER command introduction The WRITE BUFFER command (see table 227) is used in conjunction with the READ BUFFER command for: a) b) c) d) testing logical unit buffer memory; testing the integrity of the service delivery subsystem; downloading microcode; and downloading application client error history (see SPC-5).
PAGE 265
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) The function of this command and the meaning of fields within the CDB depend on the contents of the MODE field. The MODE field is defined in table 228.
PAGE 266
www.seagate.com 3.70.2 NOTE Direct Access Block commands (SPC-5 and SBC-4) Combined header and data mode (00h) This mode is not recommended. In this mode, data to be transferred is preceded by a four-byte header. The four-byte header consists of all reserved bytes. The BUFFER ID and the BUFFER OFFSET fields shall be zero. The MODE SPECIFIC field is reserved. The PARAMETER LIST LENGTH field specifies the maximum number of bytes that shall be transferred from the Data-Out Buffer.
PAGE 267
www.seagate.com 3.70.7 Direct Access Block commands (SPC-5 and SBC-4) Download microcode with offsets and activate mode (06h) In this mode, microcode shall be transferred to the device server using one or more WRITE BUFFER commands and activated (see SPC-5). The MODE SPECIFIC field is reserved. The BUFFER ID field specifies a buffer within the logical unit. The vendor assigns buffer ID codes to buffers within the logical unit. A buffer ID value of zero shall be supported.
PAGE 268
www.seagate.com 3.70.10 Direct Access Block commands (SPC-5 and SBC-4) Download microcode with offsets, select activation events, save, and defer activate mode (0Dh) In this mode, microcode shall be transferred to the device server using one or more WRITE BUFFER commands, saved to nonvolatile storage, and considered deferred (see SPC-5).
PAGE 269
www.seagate.com 3.70.12 Direct Access Block commands (SPC-5 and SBC-4) Activate deferred microcode mode (0Fh) In this mode, deferred microcode that has been saved using the download microcode with offsets, select activation events, save, and defer activate (see 3.70.10) or download microcode with offsets, save, and defer activate mode (see 3.70.11), if any, shall be activated and no longer considered deferred (see SPC-5). The MODE SPECIFIC field is reserved.
PAGE 270
www.seagate.com 3.70.15 Direct Access Block commands (SPC-5 and SBC-4) Download application log mode (1Ch) In this mode the device server transfers data from the application client and stores it in an application log. The format of the application log data is as specified in table 230. The MODE SPECIFIC field is reserved. The BUFFER ID field and BUFFER OFFSET field are ignored in this mode.
PAGE 271
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) T10 VENDOR IDENTIFICATION field The T10 VENDOR IDENTIFICATION field contains eight bytes of left-aligned ASCII data identifying the vendor of the product. The T10 vendor identification shall be one assigned by INCITS. A list of assigned T10 vendor identifications is in SPC-5 and on the T10 web site (http://www.T10.org). ERROR TYPE field The ERROR TYPE field (see table 231) specifies the error detected by the application client.
PAGE 272
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) CODE SET field The CODE SET field specifies the code set used for the application log information (see table 232) and shall only apply to information contained in the VENDOR SPECIFIC field. Table 232 CODE SET field Code Description 0h Reserved 1h The application log information is binary 2h The application log information is ASCII printable characters (i.e.
PAGE 273
www.seagate.com 3.71 Direct Access Block commands (SPC-5 and SBC-4) WRITE LONG (10) command The WRITE LONG (10) command (see table 234) requests that the device server mark a logical block or physical block as containing an error, or transfer data for a single logical block from the data-out buffer and write it to the medium. The data written shall be the same length and shall be in the same order as the data returned by the READ LONG (10) command (see 3.26).
PAGE 274
www.seagate.com 3.72 Direct Access Block commands (SPC-5 and SBC-4) WRITE LONG (16) command The WRITE LONG (16) command (see table 235) requests that the device server mark a logical block or physical block as containing an error, or transfer data for a single logical block from the data-out buffer and write it to the medium. The data written shall be the same length and shall be in the same order as the data returned by the READ LONG (16) command (see 3.27).
PAGE 275
www.seagate.com 3.73 Direct Access Block commands (SPC-5 and SBC-4) WRITE SAME (10) command The WRITE SAME(10) command (see table 236) requests that the device server transfer a single logical block from the Data-Out Buffer and for each LBA in the specified range of LBAs: a) perform a write operation using the contents of that logical block; or b) perform an unmap operation. The device server writes (i.e.
PAGE 276
www.seagate.com Table 236 Bit Byte 0 1 2 ... 5 6 7 8 9 Direct Access Block commands (SPC-5 and SBC-4) WRITE SAME (10) command 7 6 WRPROTECT 5 4 3 OPERATION CODE (41h) ANCHOR UNMAP 2 1 0 Obsolete Obsolete Obsolete (MSB) LOGICAL BLOCK ADDRESS (LSB) Reserved (MSB) GROUP NUMBER NUMBER OF BLOCKS (LSB) CONTROL WRPROTECT field See the WRITE (10) command (see 3.60) for the definitions of the WRPROTECT field. LOGICAL BLOCK ADDRESS field See 2.2.
PAGE 277
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) ANCHOR and UNMAP bits If the logical unit supports logical block provisioning management (see SBC-4), then the ANCHOR bit, the UNMAP bit, and the ANC_SUP bit in the Logical Block Provisioning VPD page (see 5.4.13) determine how the device server processes the command as described in Table 237.
PAGE 278
www.seagate.com 3.74 Direct Access Block commands (SPC-5 and SBC-4) WRITE SAME (16) command The WRITE SAME (16) command (see table 238) requests that the device server transfer a single logical block from the data-out buffer and write the contents of that logical block to the specified range of logical block addresses. Each logical block includes user data and may include protection information, based on the WRPROTECT field and the medium format.
PAGE 279
www.seagate.com 3.75 Direct Access Block commands (SPC-5 and SBC-4) WRITE SAME (32) command The WRITE SAME (32) command (see table 239) requests that the device server transfer a single logical block from the data-out buffer and write the contents of that logical block. Each logical block includes user data and may include protection information, based on the WRPROTECT field and the medium format. Table 239 Bit Byte 0 1 2 ... 5 6 7 8 9 10 11 12 ... 19 20 ... 23 24 25 26 27 28 ...
PAGE 280
www.seagate.com Direct Access Block commands (SPC-5 and SBC-4) APPLICATION TAG MASK bit set to one enables the checking of the corresponding bit of the EXPECTED LOGICAL BLOCK APPLICATION TAG field with the corresponding bit of the LOGICAL BLOCK APPLICATION TAG field in every instance of protection information. If the ATO bit is set to one in the Control mode page (see 5.3.
PAGE 281
www.seagate.com 3.77 Direct Access Block commands (SPC-5 and SBC-4) WRITE STREAM (32) command The WRITE STREAM (32) command (see table 240) requests that the device server perform the actions defined for the WRITE (32) command (see 3.63).
PAGE 282
www.seagate.com Zone Block Commands (ZBC) 4. Zone Block Commands (ZBC) 4.1 Commands for zoned block devices overview The commands for host managed zoned block devices are listed in Table 242. Table 242 Commands for host managed zoned block devices Command Operation Code Reference 94h/01h 4.2 CLOSE ZONE FINISH ZONE 94h/02h 4.3 OPEN ZONE 94h/03h 4.4 REPORT ZONES 95h/00h 4.5 RESET WRITER POINTER 94h/04h 4.6 SCSI Commands Reference Manual, Rev.
PAGE 283
www.seagate.com 4.2 Zone Block Commands (ZBC) CLOSE ZONE command (94h/01h) The CLOSE ZONE command (see table 243) requests the device server to perform close zone operations (see ZBC). Table 243 Bit Byte 0 1 2 ... 9 10 ... 13 14 15 CLOSE ZONE command 7 6 5 Reserved 4 3 2 1 0 OPERATION CODE (94h) SERVICE ACTION (01h) (MSB) ZONE ID (LSB) Reserved Reserved CONTROL ALL OPERATION CODE and SERVICE ACTION fields The OPERATION CODE field and the SERVICE ACTION field are defined in 2.
PAGE 284
www.seagate.com 4.3 Zone Block Commands (ZBC) FINISH ZONE command (94h/02h) The FINISH ZONE command (see table 244) requests the device server to perform finish zone operations (see ZBC). The device server returns the initialization pattern for all unwritten LBAs in this zone (see ZBC) in response to a read operation. The device server may write the initialization pattern to the media for unwritten LBAs. Table 244 Bit Byte 0 1 2 ... 9 10 ...
PAGE 285
www.seagate.com 4.4 Zone Block Commands (ZBC) OPEN ZONE command (94h/03h) The OPEN ZONE command (see table 245) requests the device server to perform open zone operations (see ZBC). Table 245 Bit Byte 0 1 2 ... 9 10 ... 13 14 15 OPEN ZONE command 7 6 5 Reserved 4 3 2 1 0 OPERATION CODE (94h) SERVICE ACTION (03h) (MSB) ZONE ID (LSB) Reserved Reserved CONTROL ALL OPERATION CODE and SERVICE ACTION fields A. The OPERATION CODE field and the SERVICE ACTION field are defined in 2.
PAGE 286
www.seagate.com 4.5 Zone Block Commands (ZBC) REPORT ZONES command (95h/00h) The REPORT ZONE command (see table 246) requests the device server to perform open zone operations (see ZBC). Table 246 Bit Byte 0 1 2 ... 9 10 ...
PAGE 287
www.seagate.com Zone Block Commands (ZBC) REPORTING OPTIONS field The REPORTING OPTIONS field (see table 247) specifies the information to be returned in the parameter data. Table 247 REPORT ZONES REPORTING OPTIONS field Code Description 00h List all of the zones in the zoned block device. 01h List the zones with a Zone Condition of EMPTY. 02h List the zones with a Zone Condition of IMPLICITLY OPENED. 03h List the zones with a Zone Condition of EXPLICITLY OPENED.
PAGE 288
www.seagate.com 4.5.1 Zone Block Commands (ZBC) REPORT ZONES parameter data The REPORT ZONES parameter data is defined in table 248. Table 248 REPORT ZONES parameter data Bit Byte 7 0 ... 3 4 5 ... 7 8 ... 15 16 ... 63 (MSB) 6 5 4 3 2 1 0 ZONE LIST LENGTH (n–63) (LSB) Reserved SAME Reserved (MSB) MAXIMUM LBA (LSB) Reserved ZONE DESCRIPTOR LIST 64 ... 127 ... n - 63 ... n Zone descriptor [first] ...
PAGE 289
www.seagate.com Zone Block Commands (ZBC) SAME field The SAME field is defined in table 249. If the ZONE LIST LENGTH field is zero then the SAME field is invalid and should be ignored by the application client. Table 249 SAME field description Code Description 0h The zone type and zone length in each zone descriptor may be different. 1h The zone type and zone length in each zone descriptor are equal to the zone type and zone length indicated in the first zone descriptor in the zone descriptor list.
PAGE 290
www.seagate.com Zone Block Commands (ZBC) ZONE TYPE field The ZONE TYPE field indicates the Zone Type (see ZBC) of zone as described in table 251. Table 251 Zone descriptor ZONE TYPE field Code Description 0h Reserved 1h CONVENTIONAL 2h SEQUENTIAL WRITE REQUIRED 3h SEQUENTIAL WRITE PREFERRED 4h to Fh Reserved The ZONE CONDITION field indicates the Zone Condition (see ZBC) of the zone as described in table 252.
PAGE 291
www.seagate.com 4.6 Zone Block Commands (ZBC) RESET WRITE POINTER command (94h/04h) The RESET WRITE POINTER command (see table 253) requests the device server to perform reset write pointer operations (see ZBC). Table 253 Bit Byte 0 1 2 ... 9 10 ...
PAGE 292
www.seagate.com Parameters for direct access devices 5. Parameters for direct access devices 5.1 Diagnostic parameters 5.1.1 Diagnostic page format and page codes for direct access devices This subclause describes the diagnostic page structure and the diagnostic pages that are applicable to all SCSI devices. Diagnostic pages specific to each device type are described in the command standard that applies to that device type.
PAGE 293
www.seagate.com Table 255 Parameters for direct access devices Diagnostic page codes Page Code 00h 01h - 2Fh Diagnostic Page Name Supported Diagnostic Pages 5.1.2 Defined by SES-3 for: a Enclosure services devices (i.e., SCSI devices with the PERIPHERAL DEVICE TYPE field set to 0Dh in standard INQUIRY data); and b SCSI devices with the ENCSERV bit set to one in standard INQUIRY data (see 3.6.2). 5.1.
PAGE 294
www.seagate.com 5.1.2 Parameters for direct access devices Supported diagnostic pages (00h) The Supported Diagnostic Pages diagnostic page (see table 256) returns the list of diagnostic pages implemented by the device server. This diagnostic page shall be implemented if the device server implements the diagnostic page format option of the SEND DIAGNOSTIC and RECEIVE DIAGNOSTIC RESULTS commands.
PAGE 295
www.seagate.com 5.1.3 Parameters for direct access devices Translate Address input page (40h) Table 257 defines the Translate Address Input diagnostic page retrieved with the RECEIVE DIAGNOSTIC RESULTS command after the Translate Address Output diagnostic page (see 5.1.4) has been sent with the SEND DIAGNOSTIC command. If a Translate Address Output diagnostic page has not yet been processed, the results of a RECEIVE DIAGNOSTIC RESULTS command requesting this diagnostic page are vendor specific.
PAGE 296
www.seagate.com Table 258 Parameters for direct access devices Address Field for Short Logical Block Address Format Bit Byte 7 0 (MSB) 6 5 ... 4 3 2 1 0 LOGICAL BLOCK ADDRESS 3 (LSB) 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 3 2 1 0 Table 259 Address Field for Physical Sector Address Format Bit Byte 7 0 (MSB) 6 5 1 4 CYLINDER NUMBER 2 (LSB) 3 HEAD NUMBER 4 ...
PAGE 297
www.seagate.com 5.1.4 Parameters for direct access devices Translate Address Output diagnostic page (40h) The Translate Address diagnostic pages allow the application client to translate an address in one of the formats supported by the FORMAT UNIT command (see 3.3.5.1) (i.e., a short block format address, a long block format address, a physical sector format address, or a bytes from index format address) into any one of the other formats.
PAGE 298
www.seagate.com 5.1.5 Parameters for direct access devices SCSI Enclosure Services pages (01h - 2Fh) When the drive supports the SCSI Enclosure Service (SES) pages, it does not process the contents of the pages. The drive attempts to transfer the page contents to the enclosure using the Enclosure Services Interface (ESI) as directed by the command. Errors detected in the transfer are returned to the initiator in response to the command.
PAGE 299
www.seagate.com 5.1.6 Parameters for direct access devices Rebuild Assist Input diagnostic page (42h) Application client sends a RECEIVE DIAGNOSTIC RESULTS command to retrieve a Rebuild Assist Input diagnostic page (see table 262), which provides information about whether the rebuild assist mode (see SBC-4) is enabled or not and a device server’s rebuild assist mode capabilities.
PAGE 300
www.seagate.com 5.1.7 Parameters for direct access devices Rebuild Assist Output diagnostic page (42h) An application client sends a SEND DIAGNOSTIC command to send a Rebuild Assist Output diagnostic page (see table 263) that: a) enables or disables rebuild assist mode (see SBC-4); and/or b) puts the logical unit in a simulated failure mode by disabling physical elements in conjunction with rebuild assist mode (see SBC-4).
PAGE 301
www.seagate.com Parameters for direct access devices ENABLED bit 1 a) The ENABLED bit set to one indicates that, after all fields in this diagnostic page have been validated: a self-test of the physical elements in the logical unit may be performed; and b) rebuild assist mode is enabled. 0 a) The ENABLE bit set to zero specifies that: rebuild assist mode shall be disabled; b) the other fields in this page shall be ignored; and c) all physical elements shall be enabled (i.e.
PAGE 302
www.seagate.com 5.2 Parameters for direct access devices Log parameters 5.2.1 Summary of log page codes The page code assignments for the log pages are listed in table 264. Table 264 Log page codes Page Code Subpage Code Log Page Name Reference 0Fh 00h Application Client 5.2.3 15h 00h Background Scan 5.2.4 15h 02h Background Operation 5.2.5 37h 00h Cache Statistics 5.2.6 0Dh 02h Environmental Limits 5.2.7 0Dh 01h Environmental Reporting 5.2.
PAGE 303
www.seagate.com 5.2.2 Parameters for direct access devices Log page structure This subclause describes the log page structure and the log pages that are applicable to all SCSI devices. Log pages specific to each device type are described in the command standard that applies to that device type. The LOG SELECT command (see 3.7) supports the ability to send zero or more log pages. The LOG SENSE command (see 3.8) returns a single log page specified in the PAGE CODE field of the CDB. 5.2.2.
PAGE 304
www.seagate.com Parameters for direct access devices SUBPAGE CODE field The value in the SUBPAGE CODE field is the number of the subpage page being transferred.
PAGE 305
www.seagate.com Parameters for direct access devices 5.2.2.2 Log parameter format 5.2.2.2.1 Introduction Most log pages contain one or more special data structures called log parameters (see table 267). Log parameters may be data counters of a particular event(s), the conditions under which certain operations were performed, or list parameters that contain a character string description of a particular event. Table 267 Log parameter Bit Byte 7 0 1 2 3 4 ...
PAGE 306
www.seagate.com Parameters for direct access devices 5.2.2.2.2 Parameter control byte 5.2.2.2.2.1 Introduction The DU bit, TSD bit, and FORMAT AND LINKING field are collectively referred to as the parameter control byte. These fields are described in this subclause.
PAGE 307
www.seagate.com 5.2.2.2.2.2 Parameters for direct access devices Parameter control byte values for bounded data counter parameters The device server shall return LOG SENSE parameter control byte values and process LOG SELECT parameter control byte values as shown in table 269 for any log parameter that is defined to be a bounded data counter log parameter.
PAGE 308
www.seagate.com 5.2.2.2.2.3 Parameters for direct access devices Parameter control byte values for unbounded data counter parameters The device server shall return LOG SENSE parameter control byte values and process LOG SELECT parameter control byte values as shown in table 270 for any log parameter that is defined to be an unbounded data counter log parameter.
PAGE 309
www.seagate.com 5.2.2.2.2.5 Parameters for direct access devices Parameter control byte values for binary format list log parameters The device server shall return LOG SENSE parameter control byte values and process LOG SELECT parameter control byte values as shown in table 272 for any log parameter that is defined to be a binary format list log parameter.
PAGE 310
www.seagate.com 5.2.3 Parameters for direct access devices Application Client log page (0Fh/00h) The parameter codes for the Application Client log page are listed in Table 274.
PAGE 311
www.seagate.com Parameters for direct access devices Table 276 General usage application client parameter data Bit Byte 7 0 (MSB) 6 5 4 3 2 1 0 PARAMETER CODE 1 (LSB) 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (FCh) 4 ... GENERAL USAGE PARAMETER BYTES 255 PARAMETER CODE field For general usage application client data, the value in the PARAMETER CODE field shall be between 0000h and 0FFFh.
PAGE 312
www.seagate.com 5.2.4 Parameters for direct access devices Background Scan log page (15h/00h) The Background Scan log page (see table 278) returns the background scanning status parameter and zero or more Medium Scan parameters when background scanning is supported. The Background Scan Status parameter provides information about background pre-scan and background medium scan operations. Each Background Scan log entry corresponds to a logical block where an error was detected.
PAGE 313
www.seagate.com Parameters for direct access devices The background Scan Status parameter (see table 279) contains status information about the background pre-scan and background medium scan features. Table 279 Background Scan Status parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE (0000h) 1 (LSB) 2 Parameter control byte – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (0Ch) 4 (MSB) ...
PAGE 314
www.seagate.com Parameters for direct access devices Table 280 defines the BACKGROUND SCAN STATUS field.
PAGE 315
www.seagate.com Parameters for direct access devices A Background Scan parameter (see table 281) describes a defect location on the medium that was encountered by background scanning. Table 281 Background Scan parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE (0001h - 0800h) 1 (LSB) 2 Parameter control byte – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (14h) 4 0 (MSB) ...
PAGE 316
www.seagate.com Parameters for direct access devices Table 282 defines the REASSIGN STATUS field. Table 282 REASSIGN STATUS field LOWIR bit [a] Code Reason 0 1 Original Error [b] 1h Yes Yes Recovered or unrecovered 2h Yes No Recovered The device server performed automatic read reassignment for the LBA (i.e., performed a reassign operation for the LBA and a write operation with recovered logical block data).
PAGE 317
www.seagate.com 5.2.5 Parameters for direct access devices Background Operation log page (15h/02h) 5.2.5.1 Background Operation log page overview Using the format shown in table273, the Background Operation log page reports parameters that are specific to background operations. Table 283 Background Operation log page Bit Byte 7 6 0 DS (1) SPF (1b) 5 4 3 2 1 0 PAGE CODE (15h) 1 SUBPAGE CODE (02h) 2 (MSB) PAGE LENGTH (n-3) 3 (LSB) Background Operation parameter 4 ...
PAGE 318
www.seagate.com 5.2.5.2 Parameters for direct access devices Background Operation log parameter The Background Operation log parameter of the Background Operation log page has the format defined in table 285. Table 285 Background Operation log parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 0 PARAMETER CODE (0000h) 1 (LSB) 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (4h) 4 BO_STATUS 5 ...
PAGE 319
www.seagate.com 5.2.6 Parameters for direct access devices Cache Statistics page (37h/00h) Log Page code 37h specifies Cache Statistics page. The page format is shown in Table 288. Table 287 Parameter codes Description Resettable or Changeable [a] 0000h This parameter code represents the number of logical blocks that have been sent to a SCSI initiator port. Reset Only 0001h This parameter code represents the number of logical blocks that have been received from a SCSI initiator port.
PAGE 320
www.seagate.com 5.2.7 Parameters for direct access devices Environmental Limits log page (0Dh/02h) 5.2.7.1 Overview Using the format shown in table 290, the Environmental Limits log page provides information about the environmental limits of the logical unit using the parameter codes listed in table 289. The Environmental Reporting log page (see 5.2.8) shall be supported if the Environmental Limits log page is supported.
PAGE 321
www.seagate.com 5.2.7.2 Parameters for direct access devices Temperature Limits log parameter The Temperature Limits log parameter has the format shown in table 291. Table 291 Temperature Limits log parameter Bit Byte 7 0 1 (MSB) 2 3 4 5 6 7 8 9 10 11 6 5 4 3 2 1 PARAMETER CODE (see table 289) 0 (LSB) PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.
PAGE 322
www.seagate.com Parameters for direct access devices value of the HIGH OPERATING TEMPERATURE LIMIT TRIGGER field, then the device server shall report an informational exception condition with the additional sense code set to WARNING - HIGH OPERATING TEMPERATURE LIMIT EXCEEDED.
PAGE 323
www.seagate.com Parameters for direct access devices HIGH CRITICAL RELATIVE HUMIDITY LIMIT TRIGGER field The HIGH CRITICAL RELATIVE HUMIDITY LIMIT TRIGGER field indicates the maximum relative humidity at this sensor for which the logical unit should be operated. If the EWASC bit is set to one in the Information Exceptions Control mode page (see SBC-4, SSC-4, or SMC-3) and the associated current relative humidity (see 5.2.7.
PAGE 324
www.seagate.com 5.2.8 Parameters for direct access devices Environmental Reporting log page (0Dh/01h) 5.2.8.1 Overview Using the format shown in table 295, the Environmental Reporting log page provides information about the environmental conditions of the logical unit using the parameter codes listed in table 294. Table 294 Environmental Reporting log page parameter codes Parameter code Description Resettable or Changeable [a] Reference Support 0000h - 00FFh Temperature Report [c] Never 5.2.
PAGE 325
www.seagate.com 5.2.8.2 Parameters for direct access devices Temperature Report log parameter The Temperature Report log parameter has the format shown in table 296. Table 296 Temperature Report log parameter Bit Byte 7 0 1 (MSB) 2 3 4 5 6 7 8 9 10 11 6 5 4 3 2 1 PARAMETER CODE (see table 289) 0 (LSB) PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.
PAGE 326
www.seagate.com 5.2.8.3 Parameters for direct access devices Relative Humidity Report log parameter The Relative Humidity Report log parameter has the format shown in table 297. Table 297 Relative Humidity Report log parameter Bit Byte 7 0 1 2 3 4 5 6 7 8 9 10 11 (MSB) 6 5 4 3 2 1 PARAMETER CODE (see table 289) 0 (LSB) PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.
PAGE 327
www.seagate.com Parameters for direct access devices RELATIVE HUMIDITY field The RELATIVE HUMIDITY field indicates the most recently detected relative humidity for the humidity sensor associated with this log parameter. LIFETIME MAXIMUM RELATIVE HUMIDITY field The LIFETIME MAXIMUM RELATIVE HUMIDITY field indicates the maximum relative humidity detected by the humidity sensor associated with this log parameter since the time of manufacture.
PAGE 328
www.seagate.com 5.2.9 Parameters for direct access devices Error counter log pages (WRITE, READ, and VERIFY) This subclause defines the error counter log pages (see table 299). Table 299 Error counter log page codes Page Code Loge Page Name 03h / 00h Read Error Counter 05h / 00h Verify Error Counter 02h / 00h Write Error Counter Table 300 defines the parameter codes for the error counter log pages.
PAGE 329
www.seagate.com Parameters for direct access devices The exact definition of the error counters is not part of this manual. These counters should not be used to compare products because the products may define errors differently. Table 301 Error counter log page Bit Byte 7 6 0 DS (1) SPF (0) 1 2 5 4 3 2 1 0 PAGE CODE (see table 299) SUBPAGE CODE (00h) (MSB) PAGE LENGTH (n-3) 3 (LSB) Error counter log parameter 4 (MSB) PARAMETER CODE (see table 300) ... ...
PAGE 330
www.seagate.com 5.2.10 Parameters for direct access devices Factory Log page (3Eh/00h) Log page code 3Eh specifies factory status parameters (see table 302). Table 302 Factory Log page (3Eh) Bit Byte 7 6 0 DS SPF (0b) 1 5 4 3 2 1 0 PAGE CODE (3Eh) SUBPAGE CODE(00h) 2 (MSB) PAGE LENGTH 3 4 (MSB) PARAMETER CODE [1] [2] ... ... PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) ... PARAMETER LENGTH ... (LSB) PARAMETER VALUE ... ... ... (LSB) ...
PAGE 331
www.seagate.com 5.2.11 Parameters for direct access devices Format Status log page (08h/00h) 5.2.11.1 Format Status log page overview Using the format shown table 175, the Format Status log page reports information about the most recent successful format operation and the state of the direct access block device since that operation was performed. The parameter codes for the Format Status log page are listed in table 303.
PAGE 332
www.seagate.com Parameters for direct access devices If the most recent format operation failed or the information for a Format Status log parameter is not available, then the device server shall return FFh in each byte of the log parameter data (i.e., bytes four to n of the log parameter), if any, for the Format Status log parameter (e.g., if the PARAMETER LENGTH field is set to 04h, then the log parameter data shall be set to FFFF_FFFFh).
PAGE 333
www.seagate.com 5.2.11.3 Parameters for direct access devices Grown Defects During Certification log parameter The Grown Defects During Certification log parameter for the Format Status log page has the format defined in table 306. Table 306 Grown Defects During Certification log parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE (0001h) 1 (LSB) 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (08h) 4 0 (MSB) ...
PAGE 334
www.seagate.com 5.2.11.4 Parameters for direct access devices Total Blocks Reassigned During Format log parameter The Grown Defects During Certification log parameter for the Format Status log page has the format defined in table 307. Table 307 Total Blocks Reassigned During Format log parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE (0002h) 1 (LSB) 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (08h) 4 0 (MSB) ...
PAGE 335
www.seagate.com 5.2.11.5 Parameters for direct access devices Total New Blocks Reassigned log parameter The Total New Blocks Reassigned log parameter for the Format Status log page has the format defined in table 308. Table 308 Total New Blocks Reassigned log parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE (0003h) 1 (LSB) 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (08h) 4 0 (MSB) ...
PAGE 336
www.seagate.com 5.2.11.6 Parameters for direct access devices Power On Minutes Since Format log parameter The Power On Minutes Since Format log parameter for the Format Status log page has the format defined in table 309. Table 309 Power On Minutes Since Format log parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE (0004h) 1 (LSB) 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (08h) 4 0 (MSB) ...
PAGE 337
www.seagate.com 5.2.12 Parameters for direct access devices Informational Exceptions log page (2Fh/00h) The Informational Exceptions log page (see table 310) provides a place for reporting detail about informational exceptions. The page code for the Informational Exceptions log page is 2Fh. Table 310 defines the parameter codes.
PAGE 338
www.seagate.com Parameters for direct access devices The informational exceptions general parameter data page has the format shown in table 312. Table 312 Informational exceptions general parameter data Bit Byte 7 0 1 2 3 4 5 6 7 8 9 ... 11 (MSB) 6 5 4 3 2 1 PARAMETER CODE (0000h) 0 (LSB) PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.
PAGE 339
www.seagate.com 5.2.13 Parameters for direct access devices Logical Block Provisioning log page (0Ch/00h) 5.2.13.1 Logical Block Provisioning log page overview Using the format defined in table182, the Logical Block Provisioning log page reports the logical block provisioning status of the logical unit. The parameter codes for the Logical Block Provisioning log page are listed in table 313.
PAGE 340
www.seagate.com Parameters for direct access devices 5.2.13.2 Available LBA Mapping Resource Count log parameter 5.2.13.2.
PAGE 341
www.seagate.com 5.2.13.2.2 Parameters for direct access devices RESOURCE COUNT field The RESOURCE COUNT field indicates an estimate of the number of LBA resources expressed as a number of threshold sets for the threshold resource indicated by the parameter code value. The nominal number of LBA resources is calculated as follows: LBA resources = resource count × threshold set size where: resource count is the value in the RESOURCE COUNT field; and is the number of LBAs in each threshold set (i.e.
PAGE 342
www.seagate.com Parameters for direct access devices 5.2.13.4 Available Provisioning Resource Percentage log parameter 5.2.13.4.
PAGE 343
www.seagate.com 5.2.13.5 Parameters for direct access devices De-duplicated LBA Resource Count log parameter The De-duplicated LBA Resource Count log parameter of the Logical Block Provisioning log page (see table 320) contains information about de-duplicated LBA resources. Table 320 De-duplicated LBA Resource Count log parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE (0100h) 1 (LSB) 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.
PAGE 344
www.seagate.com 5.2.13.6 Parameters for direct access devices Compressed LBA Resource Count log parameter The Compressed LBA Resource Count log parameter of the Logical Block Provisioning log page (see table 321) contains information about compressed LBA resources. Table 321 Compressed LBA Resource Count log parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE (0101h) 1 (LSB) 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.
PAGE 345
www.seagate.com 5.2.13.7 Parameters for direct access devices Total Efficiency LBA Resource Count log parameter The Total Efficiency LBA Resource Count log parameter of the Logical Block Provisioning log page (see table 322) contains information about the combined effects of all LBA resource efficiencies (e.g., the result of the combination of de-duplicated LBA resources and compressed LBA resources).
PAGE 346
www.seagate.com 5.2.14 Parameters for direct access devices Non-Medium Error log page (06h/00h) 5.2.14.1 Overview The Non-Medium Error log page (page code 06h) provides for counting the occurrences of recoverable error events other than write, read, or verify failures. No discrimination among the various types of events is provided by parameter code (see table 323). Vendor specific discrimination may be provided through Seagate specific parameter codes.
PAGE 347
www.seagate.com 5.2.14.2 Parameters for direct access devices Non-Medium Error Count log parameter The Non-Medium Error Count log parameter has the format shown in table 325. Table 325 Non-Medium Error Count log parameter Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE 1 (LSB) 2 PARAMETER CONTROL BYTE – bounded data counter log parameter (see 5.2.2.2.2.2) 3 PARAMETER LENGTH (n - 3) 4 0 (MSB) ...
PAGE 348
www.seagate.com 5.2.15 Parameters for direct access devices Pending Defects log page (15h/01h) 5.2.15.1 Pending Defects log page overview Using the format defined in table 198, the Pending Defects log page reports an unsorted list of logical blocks for which the device server has detected an unrecovered medium error. The parameter codes for the Pending Defects log page are listed in table 326.
PAGE 349
www.seagate.com 5.2.15.2 Parameters for direct access devices Pending Defect Count log parameter The Pending Defect Count log parameter has the format defined in table 328 and indicates the number of Pending Defect log parameters that are available. Table 328 Pending Defect Count log parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE (0000h) 1 (LSB) 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (04h) 4 0 (MSB) ...
PAGE 350
www.seagate.com 5.2.15.3 Parameters for direct access devices Pending Defect log parameter A Pending Defect log parameter has the format defined in table 329. If no unrecovered errors have occurred then no Pending Defect log parameters shall be present.
PAGE 351
www.seagate.com 5.2.16 Parameters for direct access devices Power Condition Transitions log page (1Ah/00h) 5.2.16.1 Overview Using the format shown in table 330, the Power Condition Transitions log page (page code 1Ah) provides a count of the occurrences of power condition transition events using the parameter codes listed in table 330.
PAGE 352
www.seagate.com 5.2.16.2 Parameters for direct access devices Power Condition Transitions log page (1Ah) The Power Condition Transitions log page (see table 331) provides a count of the occurrences of power condition transition events. A device server that implements the Power Condition Transitions log page shall implement one or more of the defined parameters.
PAGE 353
www.seagate.com Table 332 Parameters for direct access devices Power Condition Transitions log parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 PARAMETER CODE (see table 330) 1 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (04h) 4 0 (LSB) (MSB) ... 7 PARAMETER VALUE (LSB) All Power Condition Transitions log page counters are saturating counters (see table 270). A count is incremented by one for each transition (see table 272).
PAGE 354
www.seagate.com 5.2.17 Parameters for direct access devices Protocol-Specific Port log page (18h/00h) The Protocol-Specific Port log page for SAS defined in Table 333 is used to return information about phy events concerning the SAS target device’s phy(s). A phy is defined as an object in a device that is used to interface to other devices.
PAGE 355
www.seagate.com Table 334 Parameters for direct access devices Protocol-Specific Port log parameter for SAS Bit Byte 7 0 (MSB) 6 5 2 1 0 (LSB) PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) 3 4 3 PARAMETER CODE (relative target port identifier) 1 2 4 PARAMETER LENGTH (y-3) Reserved PROTOCOL IDENTIFIER (6h) 5 Reserved 6 GENERATION CODE 7 NUMBER OF PHYS SAS PHY LOG DESCRIPTOR LIST 8 ... SAS PHY LOG DESCRIPTOR (first) (see table 335) 8+m ... ...
PAGE 356
www.seagate.
PAGE 357
www.seagate.com Table 335 Parameters for direct access devices SAS phy log descriptor Bit Byte 7 6 5 4 3 2 1 0 52 ... PHY EVENT DESCRIPTOR (first) (see table 339) 63 ... ... m-11 ... PHY EVENT DESCRIPTOR (last) (see table 339) M PHY IDENTIFIER field The PHY IDENTIFIER field specifies the phy identifier of the phy that is to perform or to stop performing a phy test function (i.e., the selected phy).
PAGE 358
www.seagate.com Parameters for direct access devices REASON field The REASON field indicates the reason sent by the target device for the last link reset sequence and is defined in Table 337. Table 337 Reason field definition Code Description 0h Unknown reason 1h Power on 2h Hard reset (e.g., the port containing this phy received a HARD_RESET primitive during the hard reset sequence) (see SPL-3 r02, Section 4.4.2), or SMP PHY CONTROL function HARD RESET phy operation (see SPL-3 r02, Section 9.4.
PAGE 359
www.seagate.com Parameters for direct access devices ATTACHED SSP INITIATOR PORT bit 1 An ATTACHED SSP INITIATOR PORT bit set to one indicates that an SSP initiator port is present in the attached device. 0 An ATTACHED SSP INITIATOR PORT bit set to zero indicates that an SSP initiator port is not present in the attached device. ATTACHED STP INITIATOR PORT bit 1 An ATTACHED STP INITIATOR PORT bit set to one indicates that an STP initiator port is present in the attached device.
PAGE 360
www.seagate.com Parameters for direct access devices LOSS OF DWORD SYNCHRONIZATION COUNT field The LOSS OF DWORD SYNCHRONIZATION COUNT field indicates the number of times the phy has restarted the link reset sequence because it lost dword synchronization (see SPL-3 r02, Section 5.13) (i.e., the SP state machine transitioned from SP15:SAS_PHY_Ready or SP22:SATA_PHY_Ready to SP0:OOB_COMINIT (see SPL-4). The count shall stop at the maximum value.
PAGE 361
www.seagate.com 5.2.18 Parameters for direct access devices Self-Test Results log page (10h/00h) The Self-Test Results log page (see table 340) provides the results from the 20 most recent self-tests (see 3.46). Results from the most recent self-test or the self-test currently in progress shall be reported in the first self-test log parameter; results from the second most recent self-test shall be reported in the second self-test log parameter; etc.
PAGE 362
www.seagate.com Parameters for direct access devices PARAMETER CODE field The PARAMETER CODE field identifies the log parameter being transferred. The PARAMETER CODE field for the results of the most recent self-test shall contain 0001h; the PARAMETER CODE field for the results of the second most recent test shall contain 0002h; etc. PARAMETER LENGTH field The PARAMETER LENGTH field shall contain 10h.
PAGE 363
www.seagate.com Parameters for direct access devices ACCUMULATED POWER ON HOURS field The ACCUMULATED POWER ON HOURS field contains the total hours for the device server has been powered on since manufacturing at the time the self-test is completed. If the test is still in progress, the content of the ACCUMULATED POWER ON HOURS field shall be zero.
PAGE 364
www.seagate.com 5.2.19 5.2.19.1 Parameters for direct access devices Solid State Media log page (11h/00h) Overview Using the format shown in Table 344, the Solid State media log page (PAGE CODE 11h) reports parameters that are specific to SCSI target devices that contain solid state media. The parameter codes for the Solid State Media log page are listed in Table 343.
PAGE 365
www.seagate.com 5.2.19.2 Parameters for direct access devices Percentage Used Endurance Indicator log parameter The Percentage Used Endurance Indicator log parameter has the format shown in Table 345. Table 345 Percentage Used Endurance Indicator log parameter format Bit Byte 7 0 (MSB) 6 5 4 3 2 1 0 PARAMETER CODE (0001h) 1 (LSB) 2 PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.5) 3 PARAMETER LENGTH (04h) 4 ...
PAGE 366
www.seagate.com 5.2.20 5.2.20.1 Parameters for direct access devices Start-Stop Cycle Counter log page (0Eh/00h) Overview Using the format shown in table 347, the Start-Stop Cycle Counter log page (page code 0Eh) provides information about manufacturing dates and cycle counts since date of manufacture using the parameter codes listed in table 346.
PAGE 367
www.seagate.com Table 347 Start-Stop Cycle Counter log page (Sheet 2 of 2) Bit Byte 7 28 ... 31 32 (MSB) 33 34 35 36 ... 39 40 41 42 43 44 ... 47 48 49 50 51 52 ... 55 Parameters for direct access devices 6 5 4 3 2 1 SPECIFIED CYCLE COUNT OVER DEVICE LIFETIME (4-BYTE BINARY NUMBER) (MSB) PARAMETER CODE 0004h ACCUMULATED START-STOP CYCLES 0 (LSB) (LSB) PARAMETER CONTROL BYTE – binary format list log parameter (see 5.2.2.2.2.
PAGE 368
www.seagate.com Parameters for direct access devices The parameter value in the accumulated start-stop cycles log parameter (parameter code 0004h) shall contain a four-byte binary value that indicates how many stop-start cycles the SCSI target device has detected since its date of manufacture. The accumulated start-stop cycles parameter shall not be saveable by the application client using the LOG SELECT command (i.e., the log parameter DS bit shall be set to one).
PAGE 369
www.seagate.com 5.2.21 Parameters for direct access devices Supported Log Pages log page (00h/00h) The Supported Log Pages log page (see table 348) returns the list of log pages implemented by the logical unit. Logical units that implement the LOG SENSE command shall implement this log page. Table 348 Supported log pages Bit Byte 7 6 0 1 2 3 4 ...
PAGE 370
www.seagate.com 5.2.22 Parameters for direct access devices Supported Log Pages and Subpages log page (00h/FFh) For the LOG SENSE command, the Supported Log Pages and Subpages log page (see table 349) returns the list of log pages and subpages implemented by the logical unit. If log subpages are supported this page shall be supported. This log page is not defined for the LOG SELECT command.
PAGE 371
www.seagate.com 5.2.23 Parameters for direct access devices Temperature log page (0Dh/00h) 5.2.23.1 Overview The Temperature log page provides information about the current operating temperature of the SCSI Target Device using the parameter codes listed in table 351.
PAGE 372
www.seagate.com Parameters for direct access devices PARAMETER CODE field The PARAMETER CODE field is described in 5.2.2.2.2, and shall be set as shown in table 352 for the Temperature log parameter. PARAMETER LENGTH field The PARAMETER LENGTH field is described in 5.2.2.2.2, and shall be set as shown in table 352 for the Temperature log parameter. TEMPERATURE field The TEMPERATURE field indicates the temperature of the SCSI target device in degrees Celsius at the time the LOG SENSE command is performed.
PAGE 373
www.seagate.com 5.2.24 Parameters for direct access devices Utilization log page (0Eh/01h) 5.2.24.1 Utilization log page overview Using the format shown intable 359, the Utilization log page reports estimates of the rate at which device wear factors (e.g., damage to the recording medium) are being used. The parameter codes for the Utilization log page are defined in table 353.
PAGE 374
www.seagate.com 5.2.24.2 Parameters for direct access devices Workload Utilization log parameter The Workload Utilization log parameter for the Utilization log page has the format defined in table 355. Table 355 Workload Utilization log parameter format Bit Byte 7 0 1 (MSB) 2 3 4 5 6 5 4 3 2 1 PARAMETER CODE (0000h) 0 (LSB) PARAMETER CONTROL BYTE – bounded data counter log parameter (see 5.2.2.2.2.
PAGE 375
www.seagate.com 5.2.24.3 Parameters for direct access devices Utilization Usage Rate Based on Date and Time The Utilization Rate Based on Date and Time log parameter for the Utilization log page has the format defined in table208. If the current date and time has not been initialized by a SET TIMESTAMP command (see SPC-5), then the Utilization Rate Based on Date and Time log parameter shall not be returned in the Utilization log page (see table 355).
PAGE 376
www.seagate.com 5.3 Parameters for direct access devices Mode parameters 5.3.1 Mode parameters overview This subclause describes the mode parameter headers, block descriptors, and mode pages used with MODE SELECT command (see 3.9 and 3.10) and MODE SENSE command (see 3.11 and 3.12) that are applicable to all SCSI devices. Subpages are identical to mode pages except that they include a SUBPAGE CODE field that further differentiates the mode page contents.
PAGE 377
www.seagate.com Table 359 [a] Parameters for direct access devices Mode page codes and subpage codes Page code Subpage code Mode Page Name Reference 19h 02h Share Port Control 5.3.28 19h 03h Enhanced Phy Control 5.3.29 19h E5h Transceiver Control (Out) - SAS 5.3.30 19h E6h Transceiver Control (In) - SAS 5.3.31 04h 00h Rigid Drive Geometry Parameters page (Obsolete) 5.3.32 00h not applicable Seagate specific Unit Attention parameters for HDD 5.3.
PAGE 378
www.seagate.com 5.3.2 Parameters for direct access devices Mode parameter list format The mode parameter list shown in table 360 contains a header, followed by zero or more block descriptors, followed by zero or more variable-length mode pages. Parameter lists are defined for each device type. Table 360 Mode parameter list Bit Byte 7 6 5 4 3 2 1 0 MODE PARAMETER HEADER BLOCK DESCRIPTOR(S) MODE PAGE(S) OR VENDOR SPECIFIC (E.G., PAGE CODE SET TO ZERO) 5.3.
PAGE 379
www.seagate.com Parameters for direct access devices MODE DATA LENGTH field When using the MODE SENSE command, the MODE DATA LENGTH field indicates the length in bytes of the following data that is available to be transferred. The mode data length does not include the number of bytes in the MODE DATA LENGTH field. When using the MODE SELECT command, this field is reserved. MEDIUM TYPE field The contents of the MEDIUM TYPE field are unique for each device type.
PAGE 380
www.seagate.com 5.3.4 Parameters for direct access devices Mode parameter block descriptors 5.3.4.1 Mode block descriptors overview If the device server returns a mode parameter block descriptor, it shall return a short LBA mode parameter block descriptor (see 5.3.4.2) in the mode parameter data in response to: a) a MODE SENSE (6) command; or b) a MODE SENSE (10) command with the LLBAA bit set to zero.
PAGE 381
www.seagate.com Parameters for direct access devices If the logical unit does not support changing its capacity by changing the NUMBER OF LOGICAL BLOCKS field using the MODE SELECT command (see 3.9 and 3.10), the value in the NUMBER OF LOGICAL BLOCKS field is ignored.
PAGE 382
www.seagate.com 5.3.4.3 Parameters for direct access devices Long LBA mode parameter block descriptor Table 364 defines the block descriptor for direct-access block devices used with the MODE SELECT (10) command and MODE SENSE (10) command when the LONGLBA bit is set to one in the mode parameter header (see 5.3.3). Table 364 Long LBA mode parameter block descriptor Bit Byte 7 0 (MSB) 6 ... 5 4 3 1 0 NUMBER OF LOGICAL BLOCKS 7 (LSB) 8 ... 11 12 2 Reserved (MSB) ...
PAGE 383
www.seagate.com a) Parameters for direct access devices If the NUMBER OF LOGICAL BLOCKS field is set to zero, the logical unit shall retain its current capacity if the logical block length has not changed. If the NUMBER OF LOGICAL BLOCKS field is set to zero and the content of the LOGICAL BLOCK LENGTH field (i.e., new logical block length) is different than the current logical block length, the logical unit shall be set to its maximum capacity when the new logical block length takes effect (i.e.
PAGE 384
www.seagate.com 5.3.5 Parameters for direct access devices Mode page and subpage formats and page codes The page_0 mode page format is defined in table 365. Table 365 Page_0 mode page format Bit Byte 7 6 0 1 2 ... n PS SPF (0b) 5 4 3 2 1 0 2 1 0 PAGE CODE PAGE LENGTH (N-1) MODE PARAMETERS The SUB_PAGE mode page format is defined in table 366. Table 366 SUB_PAGE mode page format Bit Byte 7 6 0 1 2 3 4 ...
PAGE 385
www.seagate.com Parameters for direct access devices PS (parameters saveable) bit 1 When using the MODE SENSE command, a parameters saveable (PS) bit set to one indicates that the mode page may be saved by the logical unit in a nonvolatile, vendor specific location. 0 A PS bit set to zero indicates that the device server is not able to save the supported parameters. When using the MODE SELECT command, the PS bit is reserved. DS bit The DS bit is described in 5.2.2.
PAGE 386
www.seagate.com 5.3.6 Parameters for direct access devices Application Tag mode page (0Ah/02h) The Application Tag mode page (see table 367) specifies the Application Tag that a device server configured for protection information (see 5.3.6) shall use for each LBA range if the ATO bit in the Control mode page (see 5.3.12) is set to one. The mode page policy (see 5.4.14) for this page shall be shared.
PAGE 387
www.seagate.com 5.3.6.1 Parameters for direct access devices Application Tag descriptor The application tag descriptor format is described in Table 368. Table 368 Application Tag descriptor format Bit Byte 7 0 1 ... 5 6 7 8 ... 15 16 ...
PAGE 388
www.seagate.com 5.3.7 Parameters for direct access devices Background Control mode page (1Ch/01h) The Background Control mode page (see table 369) is a subpage of the Informational Exception Control mode page (see 5.3.18) and provides controls over background operations. The mode page policy (see 5.4.14) for this subpage shall be shared.
PAGE 389
www.seagate.com Parameters for direct access devices EN_BMS (Enable Background Medium Scan) bit 0 An enable background medium scan (EN_BMS) bit set to zero specifies that background medium scan is disabled. 1 An EN_BMS bit set to one specifies that background medium scan operations are enabled. If the EN_PS bit is also set to one then a background medium scan operation shall not start until after the pre-scan operation is halted or completed.
PAGE 390
www.seagate.com 5.3.8 Parameters for direct access devices Background Operation Control mode page (0Ah/06h) The Background Operation Control mode page (see table 370) provides controls of device server background operation. Table 370 Background Operation Control mode page Bit Byte 7 6 0 1 2 3 4 5 ...
PAGE 391
www.seagate.com 5.3.9 Parameters for direct access devices Caching Mode page (08h) The Caching Mode page for MODE SENSE/MODE SELECT defines the parameters that affect the use of the cache (see table 372).
PAGE 392
www.seagate.com Parameters for direct access devices CAP (Caching Analysis Permitted) bit 1 The Caching Analysis Permitted (CAP) bit, when set to one, enables caching analysis. 0 A zero indicates caching analysis is disabled. Caching analysis results are placed in the SCSI logging information table. See individual drive’s Product Manual, Volume 1, SCSI Bus Conditions and Miscellaneous Features Supported table.
PAGE 393
www.seagate.com Parameters for direct access devices FSW (FORCE SEQUENTIAL WRITE) bit 1 The Force Sequential Write (FSW) bit, when set to one, indicates that multiple block writes are to be transferred over the SCSI bus and written to the media in an ascending, sequential, logical block order. 0 When the FSW bit equals zero, the target is allowed to reorder the sequence of writing addressed logical blocks in order to achieve a faster command completion.
PAGE 394
www.seagate.com 5.3.10 Parameters for direct access devices Command Duration Limit A mode page (0Ah/03h) The Command Duration Limit A mode page (see table 373) provides controls for command duration limit (see SAM-5) that are applicable to all device types, for commands for which the REPORT SUPPORTEDOPERATION CODES command parameter data CDLP field (see 3.34) indicates the Command Duration Limit A mode page. The mode page policy (see 3.9) for this mode page should be per I_T nexus.
PAGE 395
www.seagate.com Parameters for direct access devices EXAMPLE – A duration limit descriptor value of 001b selects the command duration limit contained in the first command duration limit descriptor, a duration limit descriptor value of 010b selects the command duration limit contained in the second command duration limit descriptor, and a duration limit descriptor value of 111b selects the command duration limit contained in the seventh command limit duration descriptor.
PAGE 396
www.seagate.com 5.3.11 Parameters for direct access devices Command Duration Limit B mode page (0Ah/04h) The Command Duration Limit B mode page (see table 376) provides controls for command duration limit (see SAM-5) that are applicable to all device types, for commands for which the REPORT SUPPORTEDOPERATION CODES command parameter data CDLP field (see 3.34) indicates the Command Duration Limit B mode page. The mode page policy (see 3.9) for this mode page should be per I_T nexus.
PAGE 397
www.seagate.com 5.3.12 Parameters for direct access devices Control mode page (0Ah) The Control mode page (see table 377) provides controls over SCSI features that are applicable to all device types (e.g., task set management and error logging). If a field in this mode page is changed while there is a task already in the task set, it is vendor specific whether the old or new value of the field applies to that task. The mode page policy (see 3.9) for this mode page shall be shared, or per I_T nexus.
PAGE 398
www.seagate.com Parameters for direct access devices TMF_ONLY (Allow Task Management Functions Only) bit 0 The allow task management functions only (TMF_ONLY) bit set to zero specifies that the device server shall process tasks with the ACA task attribute received on the faulted I_T nexus when an ACA condition has been established (see SAM-5).
PAGE 399
www.seagate.com Parameters for direct access devices NUAR bit 1 A no unit attention on release (NUAR) bit set to one specifies that the device server shall not establish a unit attention condition as described in 5.13.11.2.2. 0 A NUAR bit set to zero specifies that the device server shall establish a unit attention condition as described in SPC-5.
PAGE 400
www.seagate.com Table 381 Parameters for direct access devices Unit attention interlocks control (UA_INTLCK_CTRL) field Code Definition 00b The logical unit shall clear any unit attention condition reported in the same I_T_L_Q nexus transaction as a CHECK CONDITION status and shall not establish a unit attention condition when a task is terminated with BUSY, TASK SET FULL, or RESERVATION CONFLICT status.
PAGE 401
www.seagate.com Parameters for direct access devices EAERP (Error AER Permission) bit (obsolete) 1 An Error AER Permission (EAERP) bit of one specifies that the target may issue an asynchronous event report upon detecting a deferred error condition instead of waiting to report the deferred error on the next command. 0 An EAERP bit of zero specifies that the target shall not report deferred error conditions via an asynchronous event reporting.
PAGE 402
www.seagate.com Parameters for direct access devices RWWP bit 0 A reject write without protection (RWWP) bit set to zero specifies that the device server shall process write commands that are specified to include user data without protection information (e.g., a WRITE(10) command with the WRPROTECT field set to 000b (see 3.60)).
PAGE 403
www.seagate.com 5.3.13 Parameters for direct access devices Control Extension mode page (0Ah/01h) The Control Extension mode page (see table 383) is a subpage of the Control mode page (see 5.3.12) and provides controls over SCSI features that are applicable to all device types. The mode page policy (see 5.4.14) for this mode page shall be shared.
PAGE 404
www.seagate.com Parameters for direct access devices The PS bit, SPF bit, PAGE CODE field, SUBPAGE CODE field, and PAGE LENGTH field are described in 5.3.5. TCMOS (Timestamp Changeable By Methods Outside this manual) bit 1 A timestamp changeable by methods outside this manual (TCMOS) bit set to one specifies that the timestamp may be initialized by methods outside the scope of this manual.
PAGE 405
www.seagate.com 5.3.14 Parameters for direct access devices Disconnect-Reconnect mode page (02h) for FC The Disconnect-Reconnect mode page for FCP (see table 384) allows the application client to modify the behavior of the service delivery subsystem. This subclause specifies the parameters that are used by FCP devices and defines how FCP devices interpret the parameters. The application client communicates with the device server to determine what values are most appropriate for a device server.
PAGE 406
www.seagate.com Parameters for direct access devices BUFFER FULL RATIO field The BUFFER FULL RATIO field indicates to the device server, during read operations, how full the buffer should be prior to requesting an interconnect tenancy. Device servers that do not implement the requested ratio should round down to the nearest implemented ratio as defined in 2.3.
PAGE 407
www.seagate.com Parameters for direct access devices EMDP bit The enable modify data pointers (EMDP) bit indicates whether or not the target FCP_Port may use the random buffer access capability to reorder FCP_DATA IUs for a single SCSI command. If the EMDP bit is set to zero, the target FCP_Port shall generate continuously increasing relative offset values for each FCP_DATA IU for a single SCSI command.
PAGE 408
www.seagate.com 5.3.15 Parameters for direct access devices Disconnect-Reconnect mode page (02h) for SAS The Disconnect-Reconnect mode page for SAS provides the application client the means to tune the performance of the service delivery subsystem. Table 385 defines the parameters which are applicable to SSP. If any field in the Disconnect-Reconnect mode page is not implemented, the value assumed for the functionality of the field shall be zero (i.e.
PAGE 409
www.seagate.com Parameters for direct access devices BUS INACTIVITY TIME LIMIT field The value in the BUS INACTIVITY TIME LIMIT field contains the maximum period that an SSP target port is permitted to maintain a connection without transferring a frame to the SSP initiator port. This value shall be the number of 100 ms increments between frames that the SSP target port transmits during a connection. When this number is exceeded, the SSP target port shall prepare to close the connection (i.e.
PAGE 410
www.seagate.com 5.3.16 Parameters for direct access devices Format Parameters page (03h) This mode page has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. The Format Parameters page implementation is defined in Table 386. This table summarizes the function and defines the default or changeability status for each bit. The actual implementation of reserving spare areas for defect management takes place during the FORMAT UNIT command.
PAGE 411
www.seagate.com Parameters for direct access devices ALTERNATE SECTORS PER ZONE field The ALTERNATE SECTORS PER ZONE field indicates the number of spare sectors to be reserved for the defined defect management zone. A value of zero indicates that no sectors are to be reserved in each zone for defect management. This is to accommodate hosts that want to manage the defects themselves.
PAGE 412
www.seagate.com Parameters for direct access devices SSEC bit set and HSEC bits A HSEC bit set to one indicates that the target shall use hard sector formatting. The HSEC bit and the SSEC bit are mutually exclusive in MODE SELECT commands.
PAGE 413
www.seagate.com 5.3.17 Parameters for direct access devices IO Advice Hints Grouping mode page (0Ah/05h) The IO Advice Hints Grouping mode page(see table 387) provides the application client with the means to obtain or modify the IO advice hints of the logical unit and the group number associated with those IO advice hints. The mode page policy (see SPC-5) for this page shall be shared. Table 387 IO Advice Hints Grouping mode page Bit Byte 7 6 0 1 2 3 4 ...
PAGE 414
www.seagate.com Parameters for direct access devices IO ADVICE HINTS MODE field The IO ADVICE HINTS MODE field specifies the mode of the logical block markup descriptor and is described in table 389. Table 389 IO ADVICE HINTS MODE field Code Description 00b The logical block markup descriptor is valid (see 2.2.8). 01b The logical block markup descriptor is invalid (see 2.2.8).
PAGE 415
www.seagate.com 5.3.18 Parameters for direct access devices Informational Exceptions Control mode page (1Ch) The Informational Exceptions Control mode page (see table 390) defines the methods used by the device server to control the reporting and the operations of specific informational exception conditions. This page shall only apply to informational exceptions that report an additional sense code of FAILURE PREDICTION THRESHOLD EXCEEDED or an additional sense code of WARNING to the application client.
PAGE 416
www.seagate.com Parameters for direct access devices EWASC (Enable Warning) bit 0 If the enable warning (EWASC) bit is set to zero, the device server shall disable reporting of the warning. The MRIE field is ignored when DEXCPT is set to one and EWASC is set to zero. 1 If the EWASC bit is set to one, warning reporting shall be enabled. The method for reporting the warning when the EWASC bit is set to one is determined from the MRIE field.
PAGE 417
www.seagate.com Table 391 Parameters for direct access devices Method of reporting informational exceptions (MRIE) field MRIE 0h 1h 2h Description No reporting of informational exception condition: The device server shall not report information exception conditions.
PAGE 418
www.seagate.com Parameters for direct access devices The device server shall use the values in the INTERVAL TIMER field and the REPORT COUNT field based on the value in the MRIE field as shown in table 392.
PAGE 419
www.seagate.com 5.3.19 Parameters for direct access devices Logical Block Provisioning mode page (1Ch/02h) 5.3.19.1 Introduction The Logical Block Provisioning mode page (see table 393) specifies the parameters that a device server that supports logical block provisioning threshold values (see SBC-4) shall use to report logical block provisioning threshold notifications (see SBC-4). The mode page policy (see SPC-5) for this page shall be shared.
PAGE 420
www.seagate.com 5.3.19.2 Parameters for direct access devices Threshold descriptor format The threshold descriptor format is defined in table 394. Table 394 Threshold descriptor format Bit Byte 7 6 0 1 2 3 4 ... n ENABLED Reserved 5 4 3 THRESHOLD TYPE THRESHOLD RESOURCE 2 1 0 THRESHOLD ARMING Reserved (MSB) THRESHOLD COUNT (LSB) ENABLED bit 1 an ENABLED bit set to one specifies that the threshold is enabled. 0 an ENABLED bit set to zero specifies that the threshold is disabled.
PAGE 421
www.seagate.com Parameters for direct access devices THRESHOLD ARMING field The THRESHOLD ARMING field (see table 396) specifies the arming method used for operation of this threshold. Table 396 THRESHOLD ARMING field Code Description Reference 000b The threshold operates as an armed decreasing threshold. SBC-4 001b The threshold operates as an armed increasing threshold. SBC-4 All others Reserved THRESHOLD RESOURCE field The THRESHOLD RESOURCE field specifies the resource of this threshold.
PAGE 422
www.seagate.com 5.3.20 Parameters for direct access devices Power Condition mode page (1Ah) The Power Condition mode page provides an application client with methods to control the power condition of a logical unit (see SPC-5).
PAGE 423
www.seagate.com Parameters for direct access devices PM_BG_PRECEDENCE field The PM_BG_PRECEDENCE field (see table 398) specifies the interactions between background functions (see SPC-5) and power management. The behavior of the idle and standby condition timers controlled by this mode page is defined in the power condition overview and the power condition state machine (see SPC-5).
PAGE 424
www.seagate.com Parameters for direct access devices STANDBY_Y bit 1 If the STANDBY_Y bit is set to one, then the standby_y condition timer is enabled. 0 If the STANDBY_Y bit is set to zero, then the device server shall ignore the standby_y condition timer. IDLE_C bit 1 If the IDLE_C bit is set to one, then the idle_c condition timer is enabled. 0 If the IDLE_C bit is set to zero, then the device server shall ignore the idle_c condition timer.
PAGE 425
www.seagate.com Parameters for direct access devices CCF_IDLE field The Check Condition From idle_c processing control (CCF_IDLE) field is defined in Table 399. Table 399 CCF_IDLE field Code 00b Restricted [a] 01b If the transition was from an idle_c power condition, returning CHECK CONDITION status is disabled. [b] 10b If the transition was from an idle_c power condition, returning CHECK CONDITION status is enabled.
PAGE 426
www.seagate.com 5.3.21 Parameters for direct access devices Power Consumption Mode page (1Ah/01h) The Power Consumption mode page (see table 402) provides a method to set the power consumption level while in the active power condition (see SPC-5) to: a) a relative power consumption level (see SPC-5); or b) a maximum power consumption level (see SPC-5) that is based on the contents of the power consumption descriptors in the Power Consumption VPD page (see 5.4.16)). The mode page policy (see 5.4.
PAGE 427
www.seagate.com Parameters for direct access devices ACTIVE LEVEL field The ACTIVE LEVEL field (see table 403) specifies the relative active power consumption level, in any. Table 403 ACTIVE LEVEL field Code Description 00b The active power consumption level is specified by the POWER CONSUMPTION IDENTIFIER field.
PAGE 428
www.seagate.com 5.3.22 Parameters for direct access devices Read-Write Error Recovery mode page (01h) The Read-Write Error Recovery mode page (see table 404) specifies the error recovery parameters the device server shall use during any command that performs a read or write operation to the medium (e.g., READ commands, WRITE commands, and WRITE AND VERIFY commands).
PAGE 429
www.seagate.com Parameters for direct access devices TB (Transfer Block) bit 0 A transfer block (TB) bit set to zero specifies that the device server shall not transfer a logical block to the data-in buffer if the logical block is not recovered within the recovery limits specified. 1 A TB bit set to one specifies that the device server shall transfer a logical block to the data-in buffer before returning CHECK CONDITION status if the logical block is not recovered within the recovery limits specified.
PAGE 430
www.seagate.com Parameters for direct access devices The combinations of the error recovery bits (i.e., the EER bit, the PER bit, the DTE bit, and the DCR bit) are explained in table 405. Table 405 EER 0 PER 0 Combined error recovery bit descriptions (Sheet 1 of 3) DTE 0 DCR Description 0 The device server shall perform the full number of retries as specified in the READ RETRY COUNT field for read operations, the WRITE RETRY COUNT field for write operations, and the VERIFY RETRY COUNT field (see 5.3.
PAGE 431
www.seagate.com Table 405 EER 0 PER 1 Parameters for direct access devices Combined error recovery bit descriptions (Sheet 2 of 3) DTE 1 DCR Description 0 The device server shall perform the full number of retries as specified in the READ RETRY COUNT field for read operations, the WRITE RETRY COUNT field for write operations, and the VERIFY RETRY COUNT field (see 5.3.35) for verify operations and shall perform error correction in an attempt to recover the data.
PAGE 432
www.seagate.com Table 405 EER 1 PER 1 Parameters for direct access devices Combined error recovery bit descriptions (Sheet 3 of 3) DTE 0 DCR Description 0 The device server shall perform the fewest possible number of retries and perform error correction in an attempt to recover the data. The device server shall terminate a command performing a read or write operation with CHECK CONDITION status before the transfer count is exhausted only if an unrecoverable error is detected.
PAGE 433
www.seagate.com 5.3.23 Parameters for direct access devices Logical Unit Control mode page (18h) for FC The Fibre Channel Logical Unit Control mode page (see table 406) contains those parameters that select FCP logical unit operation options. The implementation of any parameter and its associated functions is optional. The mode page follows the MODE SENSE and MODE SELECT command rules.
PAGE 434
www.seagate.com 5.3.24 Parameters for direct access devices Logical Unit mode page (18h) for SAS The SAS Protocol-Specific Logical Unit mode page (see SPL-2) contains parameters that affect SSP target port operation on behalf of the logical unit. The mode page policy (see 5.4.14) for the Protocol-Specific Logical Unit mode page short format subpage shall be either shared or per target port. If a SAS target device has multiple SSP target ports, the mode page policy should be per target port.
PAGE 435
www.seagate.com 5.3.25 Parameters for direct access devices Port Control Mode page (19h) for FC The Fibre Channel Interface Control page controls options relevant to Fibre Channel protocol. It is intended for the control of features unique to Fibre Channel protocol that are not suitable for control by login or other techniques defined for Fibre Channel. Both the current and saved values of Mode page 19h, byte 3, are changeable using the Mode Select command.
PAGE 436
www.seagate.com Parameters for direct access devices PROTOCOL IDENTIFIER field The value in the PROTOCOL IDENTIFIER field defines the SCSI transport protocol to which the mode page applies. For a MODE SENSE command (see 3.11), the device server shall set the PROTOCOL IDENTIFIER field to one of the values shown in Clause 5.3.23 to indicate the SCSI transport protocol used by the target port through which the MODE SENSE command is being processed. For a MODE SELECT command (see 3.
PAGE 437
www.seagate.com Parameters for direct access devices DSA (Disable Soft Address) 1 The target does not select a soft address if there is a conflict for the Select_ID address available in the SCA connector during loop initialization. If there is a Select_ID address conflict, the target enters the non-participation state. If the target detects loop initialization while in the non-participation state, the target again attempts to get the Select_ID address.
PAGE 438
www.seagate.com 5.3.26 Parameters for direct access devices Protocol-Specific Port mode page (19h) for SAS This clause describes the Protocol-Specific Port mode page implemented by products that are SAS-3 compliant. The Protocol-Specific Port mode page contains parameters that affect SSP target port operation.
PAGE 439
www.seagate.com Parameters for direct access devices CONTINUE AWT BIT 0 A CONTINUE AWT bit set to zero specifies that the SAS port shall stop the Arbitration Wait Time timer and set the Arbitration Wait Time timer to zero when it receives an OPEN_REJECT (RETRY). 1 A CONTINUE AWT bit set to one specifies that the SAS port shall not stop the Arbitration Wait Time timer and shall not set the Arbitration Wait Time timer to zero when the SAS port receives an OPEN_REJECT (RETRY).
PAGE 440
www.seagate.com 5.3.27 Parameters for direct access devices Phy Control And Discover subpage (19h/01h) The Phy Control And Discover subpage contains SAS phy-specific parameters. The mode page policy (see 5.4.14) for this subpage shall be shared. Parameters in this subpage shall affect only the referenced phy. Table defines the format of the subpage for SAS.
PAGE 441
www.seagate.com Parameters for direct access devices SAS PHY MODE DESCRIPTOR fields A SAS phy mode descriptor shall be included for each phy in the SAS target device (not just the SAS target port), starting with the lowest numbered phy and ending with the highest numbered phy. Table 413 defines the SAS phy mode descriptor.
PAGE 442
www.seagate.com Parameters for direct access devices PHY IDENTIFIER field The PHY IDENTIFIER field indicates the phy identifier (see SPL-3) of the phy for which information is being returned. ATTACHED DEVICE TYPE field The ATTACHED DEVICE TYPE field indicates the device type attached to this phy and is defined in Table 336.
PAGE 443
www.seagate.com Parameters for direct access devices HARDWARE MAXIMUM PHYSICAL LINK RATE field The HARDWARE MAXIMUM PHYSICAL LINK RATE field indicates the maximum physical link rate supported by the phy. The values are defined in table 347. If the phy is a virtual phy, this field should be set to the maximum physical link rate supported by the expander device. Table 414 Code The HARDWARE MINIMUM & MAXIMUM PHYSICAL LINK RATE field values Description 0h to 7h Reserved 8h 1.5 Gbps 9h 3.0 Gbps Ah 6.
PAGE 444
www.seagate.com 5.3.28 Parameters for direct access devices Shared Port Control mode page (19h/02h) The Port Control Mode Page contains parameters that affect SAS target port operation. If the mode page is implemented by one logical unit in a SCSI target device, then it shall be implemented by all logical units in the SCSI target device that support the MODE SELECT or MODE SENSE commands. The mode page policy (see 5.4.14) for this mode page shall be shared.
PAGE 445
www.seagate.com 5.3.29 Parameters for direct access devices Enhanced Phy Control mode page (19h/03h) The Enhanced Phy Control mode page contains parameters that affect SAS target phy operation. If the mode page is implemented by one logical unit in a SCSI target device, then it shall be implemented by all logical units in the SCSI target device that support the MODE SELECT or MODE SENSE commands. The mode page policy (see 5.4.14) for this mode page shall be shared.
PAGE 446
www.seagate.com Parameters for direct access devices Table 418 defines the enhanced phy control mode descriptor. Table 418 Bit Byte 0 1 2 3 4 ... 7 8 ... 11 12 ...
PAGE 447
www.seagate.com Parameters for direct access devices ATTACHED PHY CAPABILITIES field The ATTACHED PHY CAPABILITIES field indicates the incoming SNW-3 phy capabilities bits received in the last SNW-3 as defined in SPL-4. If the last link reset sequence did not include SNW-3 or was a SATA link reset sequence, then the ATTACHED PHY CAPABILITIES field shall be set to 00000000h.
PAGE 448
www.seagate.com 5.3.30 Parameters for direct access devices SAS – Transceiver Control (Out) subpage (19h/E5h) 5.3.30.1 Introduction The Transceiver Control (Out) subpage (see table 419) of the SAS Protocol-Specific Port mode page is used to adjust the transceiver parameter values of a phy.
PAGE 449
www.seagate.com Table 419 Bit Byte Parameters for direct access devices SAS Transceiver Control (Out) subpage 7 ... 128 ... 144 6 5 4 3 2 1 0 CONTROLLABLE LINK RATE = 0Ah ... Phy Transceiver Controls mode descriptor (second) PHY IDENTIFIER = 1 CONTROLLABLE LINK RATE = 0Bh ... 00 The PARAMETERS SAVEABLE (PS) bit is defined in SPC-5. The SUBPAGE FORMAT (SPF) bit is defined in SPC-5 and shall be set to the value defined in table 419.
PAGE 450
www.seagate.com 5.3.30.2 Parameters for direct access devices Transceiver Controls Mode descriptors Detail for the mode descriptor(s) for transceiver controls can be found in Table 420 and Table 421. Each field is defined below the table. All supported link rates and controls shall be listed in page E5h. Table 420 Bit Byte Transceiver Controls Mode descriptor (1.
PAGE 451
www.seagate.com Parameters for direct access devices PHY IDENTIFIER field SAS devices may have more than one target port. If a target device has 2 operational target ports (2 phys - primary and secondary port), then this field shall be set to either 0h for the primary port or 1h for the secondary port. This field is unchangeable. CONTROLLABLE LINK RATE field The Controllable Link Rate field shall contain the controllable link rate for the phy. Table 422 lists the supported values Controllable Link Rates.
PAGE 452
www.seagate.com Parameters for direct access devices DRIVER EMPHASIS CONTROL or C2 AMPLITUDE CONTROL (12G Mode Only) field This field shall contain either the user input (MODE SELECT) or current (MODE SENSE) driver emphasis setting the 12G mode amplitude C2 setting of the SAS transmitter.
PAGE 453
www.seagate.com Parameters for direct access devices RECEIVER THRESHOLD CONTROL field The Receiver Threshold Control field contains either the user input (MODE SELECT) or current (MODE SENSE) receiver threshold setting of the target device SAS phy.
PAGE 454
www.seagate.com Parameters for direct access devices RESET bit This bit controls the TX to C1, C2 and C3, and controls the reset function of IREC bits (see table 427). Table 428 RESET and IREC bit function RESET (Mode Select) IREC (Mode Select) 0 0 0 1 1 0 0 1 IREC Completed Mode Sense data after Mode Select was executed with different RESET bit and IREC bit settings.
PAGE 455
www.seagate.com 5.3.31 5.3.31.1 Parameters for direct access devices SAS – Transceiver Control (In) subpage (19h/E6h) Introduction The Transceiver Control (In) subpage of the SAS Protocol-Specific Port mode page (see table 429) is used to return the transceiver parameter values of a phy. The Transceiver Control subpage shall not be returned for a MODE SENSE command to return all pages. It shall only be returned to a MODE SENSE command, specifically, for the Transceiver Control subpage (19h/E6h).
PAGE 456
www.seagate.com Parameters for direct access devices ... ... 128 Phy Transceiver Controls mode descriptor (second) PHY IDENTIFIER = 1 CONTROLLABLE LINK RATE = 0Bh ... ... 144 00 The PARAMETERS SAVEABLE (PS) bit is defined in SPC-5. The SUBPAGE FORMAT (SPF) bit is defined in SPC-5 and shall be set to the value defined in table 429. The PAGE CODE field is defined in SPC-5 and shall be set to the value defined in table 429.
PAGE 457
www.seagate.com 5.3.31.2 Parameters for direct access devices Transceiver Controls Mode descriptors Detail for the mode descriptor(s) for transceiver controls can be found in Table 430 and Table 431. Each field is defined below the table. All supported link rates and controls shall be listed in page E5h. Table 430 Bit Byte Transceiver Controls descriptor (1.
PAGE 458
www.seagate.com Table 431 Bit Byte Parameters for direct access devices Transceiver Controls descriptor (1.
PAGE 459
www.seagate.com Parameters for direct access devices MAX DRIVER SLEW RATE CONTROL or C3 CONTROL (12G Mode Only) field This field shall contain the max allowable driver slew rate setting of the target device SAS phy. This field is changeable but not savable. DRIVER STRENGTH CONTROL CHANGE PER STEP or C1 CONTROL (12G Mode Only) field This field shall contain the approximate voltage change (in mV unit) for each increment or decrement of driver strength control setting. The field is unchangeable.
PAGE 460
www.seagate.com 5.3.32 Parameters for direct access devices Rigid Drive Geometry Parameters page (04h) This mode page has been declared obsolete by the T10 committee. However, it is included because it may be implemented on some products. The Rigid Drive Geometry Parameters page implementation is defined in Table 433 . This table summarizes the function and defines the default value.
PAGE 461
www.seagate.com Parameters for direct access devices PAGE CODE field The PAGE CODE field is defined in SPC-5 and shall be set to the value defined in table 433. PAGE LENGTH field The PAGE LENGTH field is defined in SPC-5 and shall be set to the value defined in table 433. NUMBER OF CYLINDERS field The NUMBER OF CYLINDERS field defines the number of physical cylinders used for data storage. This may or may not include spare cylinders set aside for flaw reallocation.
PAGE 462
www.seagate.com 5.3.33 Parameters for direct access devices Seagate Specific Unit Attention parameters page (00h) for HDD The Seagate Specific Unit Attention parameters page is the last page to be reported by the drive.
PAGE 463
www.seagate.com Parameters for direct access devices PM (Performance Mode) bit The PM (Performance Mode) bit is used to control the drive’s cache management algorithm to allow best performance in different types of systems. It is the initiator’s responsibility to determine which setting is best for that system. 1 A PM value of 1 indicates that the number of cache segments is fixed to the value set in mode page 08h.
PAGE 464
www.seagate.com Parameters for direct access devices SCSI-2 bit 1 When set to one, the SCSI-2 bit changes the following SCSI-3 features from their SCSI-3 definition to the SCSI-2 definition: a) Control Mode Page (0Ah) Length from 0Ah to 06h; and b) Caching Page (08h) Length from 12h to 0Ah. 0 When S2 is set to zero, all features remain as specified in other portions of this specification. DAR (Deferred Auto Reallocation) bit 1 Deferred reallocation is enabled.
PAGE 465
www.seagate.com 5.3.34 Parameters for direct access devices Seagate Specific Unit Attention parameters page (00h) for SSD The Seagate Specific Unit Attention parameters page is the last page to be reported by the drive.
PAGE 466
www.seagate.com Parameters for direct access devices IL (INQUIRY Length) bit 1 When the INQUIRY Length (IL) bit is set to one, the standard INQUIRY data available to a host is limited to the 36 bytes required by the SCSI-2 specification. 0 When the IL bit is set to zero, 148 bytes of standard INQUIRY data are available. The Additional Length field in byte 4 of the INQUIRY data is updated to reflect the actual number of additional bytes available.
PAGE 467
www.seagate.com 5.3.35 Parameters for direct access devices Verify Error Recovery mode page (07h) The Verify Error Recovery mode page (see table 436) specifies the error recovery parameters the device server shall use during the VERIFY command and the verify operation of the WRITE AND VERIFY command. Table 436 Verify Error Recovery mode page Bit Byte 7 6 0 1 PS SPF (0b) 2 Reserved 3 4 5 ...
PAGE 468
www.seagate.com 5.4 Parameters for direct access devices Vital product data parameters 5.4.1 Vital product data parameters overview and page codes This subclause describes the vital product data (VPD) page structure and the VPD pages (see table 437) that are applicable to all SCSI devices. These VPD pages are returned by an INQUIRY command with the EVPD bit set to one (see 3.6) and contain vendor specific product information about a logical unit and SCSI target device.
PAGE 469
www.seagate.com 5.4.2 Parameters for direct access devices ASCII Information VPD page (01h - 7Fh) The ASCII Information VPD page (see table 438) contains information for the field replaceable unit code returned in the sense data (see 2.4). Table 438 ASCII Information VPD page Bit Byte 7 0 1 2 3 4 5 ... m m+1 ...
PAGE 470
www.seagate.com 5.4.3 Parameters for direct access devices Block Device Characteristics VPD page (B1h) The Block Device Characteristics VPD page (see table 439) contains parameters indicating characteristics of the logical unit. Table 439 Block Device Characteristics VPD page Bit Byte 7 0 1 2 3 4 5 6 7 8 9 ...
PAGE 471
www.seagate.
PAGE 472
www.seagate.com Table 444 Parameters for direct access devices Nominal Form Factor Field Code Definition 0h Nominal form factor is not reported 1h 5.25 inch 2h 3.5 inch 3h 2.5 inch 4h 1.8 inch 5h Less than 1.8 inch All others Reserved ZONED field The ZONED field indicates the type of zoned block capabilities implemented by the device server as defined in table 445.
PAGE 473
www.seagate.com 5.4.4 Parameters for direct access devices Block Device Characteristics Extension VPD page (B5h) The Block Device Characteristics Extension VPD page (see table 446) contains parameters indicating characteristics of the logical unit. Table 446 Block Device Characteristics Extension VPD page Bit Byte 7 0 1 2 3 4 5 6 7 8 ... 11 12 ... 15 16 ...
PAGE 474
www.seagate.com Parameters for direct access devices UTILIZATION UNITS field The UTILIZATION UNITS field (see table 448) indicates the units of measure for the values, if any, in the UTILIZATION A field and the UTILIZATION B field.
PAGE 475
www.seagate.com 5.4.5 Parameters for direct access devices Block Limits VPD page (B0h) The Block Limits VPD page (see table 450) provides the application client with the means to obtain certain operating parameters of the logical unit. Table 450 Bit Byte 0 1 2 3 4 5 6 7 8 ... 11 12 ... 15 16 ... 19 20 ... 23 24 ... 27 28 ... 31 32 ... 35 36 ... 43 44 ... 47 48 ... 51 52 ...
PAGE 476
www.seagate.com Table 450 Parameters for direct access devices Block Limits VPD page (Sheet 2 of 2) Bit Byte 7 56 ... 59 60 ... 63 (MSB) 6 5 4 3 2 1 0 MAXIMUM ATOMIC TRANSFER LENGTH WITH ATOMIC BOUNDARY (LSB) (MSB) MAXIMUM ATOMIC BOUNDARY SIZE (LSB) PERIPHERAL QUALIFIER field and the PERIPHERAL DEVICE TYPE field The PERIPHERAL QUALIFIER field and the PERIPHERAL DEVICE TYPE field are defined in SPC-5.
PAGE 477
www.seagate.
PAGE 478
www.seagate.com Parameters for direct access devices MAXIMUM UNMAP LBA COUNT field The MAXIMUM UNMAP LBA COUNT field set to a non-zero value indicates the maximum number of LBAs that may be unmapped by an UNMAP command (see 3.54). If the number of LBAs that may be unmapped by an UNMAP command is constrained only by the amount of data that may be contained in the UNMAP parameter list (see 3.54.2), then the device server shall set the MAXIMUM UNMAP LBA COUNT field to FFFF_FFFFh.
PAGE 479
www.seagate.com Parameters for direct access devices ATOMIC ALIGNMENT field The ATOMIC ALIGNMENT field indicates the required alignment of the starting LBA in an atomic write command. If the ATOMIC ALIGNMENT field is set to 0000_0000h, then there is no alignment requirement for atomic write commands.
PAGE 480
www.seagate.com 5.4.6 Parameters for direct access devices Block Limits Extension VPD page (B7h) The Block Limits Extension VPD page (see table 452) provides the application client with the means to obtain certain operating parameters of the logical unit. Table 452 Block Limits Extension VPD page Bit Byte 7 0 1 2 3 4 5 6 7 8 9 10 ... 13 14 ...
PAGE 481
www.seagate.com 5.4.7 Parameters for direct access devices Date Code page (C1h) Table 453 ETF Log Date Code page (C1h) Bit Byte 7 6 5 4 3 PERIPHERAL QUALIFIER 0 1 1 PAGE CODE (C1h) 00h 3 PAGE LENGTH (10h) (MSB) ... ETF LOG DATE IN ASCII 11 12 (LSB) (MSB) ... COMPILE DATE CODE 19 (LSB) 20 LAST SPINDOWN POWER CYCLE COUNT 21 22 0 PERIPHERAL DEVICE TYPE 2 4 2 (MSB) ...
PAGE 482
www.seagate.com 5.4.8 Parameters for direct access devices Device Behavior page (C3h) The Device Behavior page (see table ) will be used by the regression tests to determine what behavior should be expected from a particular firmware package. Table 454 Device Behavior page (C3h) Bit Byte 7 0 6 5 4 3 PERIPHERAL QUALIFIER 2 0 PERIPHERAL DEVICE TYPE 1 PAGE CODE (C3h) 2 Reserved 3 PAGE LENGTH 4 VERSION NUMBER 5 BEHAVIOR CODE 6 BEHAVIOR CODE VERSION NUMBER 7 ...
PAGE 483
www.seagate.com 5.4.9 Parameters for direct access devices Extended INQUIRY Data VPD page (86h) The Extended INQUIRY Data VPD page (see table 455) provides the application client with a means to obtain information about the logical unit. Table 455 Extended INQUIRY Data VPD page Bit Byte 7 0 1 2 3 6 5 4 3 PERIPHERAL QUALIFIER 2 1 0 APP_CHK REF_CHK PERIPHERAL DEVICE TYPE PAGE CODE (86h) (MSB) PAGE LENGTH (3Ch) 4 ACTIVATE MICROCODE SPT 5 6 7 8 9 10 11 12 13 14 ...
PAGE 484
www.seagate.com Table 456 Parameters for direct access devices ACTIVATE MICROCODE field Value Meaning 00b The actions of the device server may or may not be as defined for values 01b or 10b.
PAGE 485
www.seagate.com Parameters for direct access devices UASK_SUP (Unit Attention Sense Key Supported) bit 1 A unit attention condition sense key specific data supported (UASK_SUP) bit set to one indicates that the device server returns sense-key specific data for the UNIT ATTENTION sense key (see 2.4.1.1.4.6). 0 A UASK_SUP bit set to zero indicates that the device server does not return sense-key specific data for the UNIT ATTENTION sense key.
PAGE 486
www.seagate.
PAGE 487
www.seagate.com Parameters for direct access devices EXTENDED SELF-TEST COMPLETION MINUTES field The EXTENDED SELF-TEST COMPLETION MINUTES field contains advisory data that is the time in minutes that the device server requires to complete an extended self-test provided the device server is not interrupted by subsequent commands and no errors occur during processing of the self-test.
PAGE 488
www.seagate.com 5.4.10 Table 458 Parameters for direct access devices Firmware Numbers page (C0h) Firmware Numbers page (C0h) Bit Byte 7 0 6 5 4 3 PERIPHERAL QUALIFIER 2 1 0 PERIPHERAL DEVICE TYPE 1 PAGE CODE (C0h) 2 00h 3 PAGE LENGTH 4 ... 11 SCSI FIRMWARE RELEASE NUMBER 12 ... 19 SERVO FIRMWARE RELEASE NUMBER 20 ... 27 SAP BLOCK POINT NUMBERS (MAJOR/MINOR) 28 ... 31 SERVO FIRMWARE RELEASE DATE 32 ... 35 SERVO ROM RELEASE DATE 36 ... 43 SAP FIRMWARE RELEASE NUMBER 44 ...
PAGE 489
www.seagate.com Parameters for direct access devices SCSI FIRMWARE RELEASE NUMBER field The SCSI FIRMWARE RELEASE NUMBER fields contain ASCII data. The least significant ASCII character of the Drive firmware number shall appear as the last byte of the field. SERVO FIRMWARE RELEASE NUMBER field The SERVO FIRMWARE RELEASE NUMBER fields contain ASCII data. The least significant ASCII character of the Drive firmware number shall appear as the last byte of the field.
PAGE 490
www.seagate.com 5.4.11 Parameters for direct access devices Device Identification VPD page (83h) The Device Identification VPD page (see table ) provides the means to retrieve zero or more identification descriptors applying to the logical unit. Logical units may have more than one identification descriptor (e.g., if several types or associations of identifier are supported).
PAGE 491
www.seagate.com Parameters for direct access devices Identification Descriptor field Each IDENTIFICATION DESCRIPTOR (see table 460) contains information identifying the logical unit, physical device, or access path used by the command and returned parameter data. Table 460 Identification Descriptor Bit Byte 7 6 PIV Reserved 0 5 4 3 2 PROTOCOL IDENTIFIER 1 1 0 CODE SET ASSOCIATION IDENTIFIER TYPE 2 Reserved 3 IDENTIFIER LENGTH (n – 3) 4 ...
PAGE 492
www.seagate.com Parameters for direct access devices PIV (Protocol Identifier Valid) bit 0 A protocol identifier valid (PIV) bit of zero indicates the PROTOCOL IDENTIFIER field should be ignored. If the ASSOCIATION field contains a value of 1h or 2h then a PIV bit set to one indicates the PROTOCOL IDENTIFIER field contains a valid protocol identifier selected from the values shown in table 461. If the ASSOCIATION field contains a value other than 1h or 2h then the PIV bit should be ignored.
PAGE 493
www.seagate.com Parameters for direct access devices IDENTIFIER TYPE field The IDENTIFIER TYPE field specifies the format and assignment authority for the identifier, as described in tables 463 and 464. Table 463 IDENTIFIER Type field Value Description 0h No assignment authority was used and consequently there is no guarantee that the identifier is globally unique (i.e., the identifier is vendor specific). 1h The first 8 bytes of the IDENTIFIER field are a Vendor ID.
PAGE 494
www.seagate.com Parameters for direct access devices IDENTIFIER LENGTH field The IDENTIFIER LENGTH field specifies the length in bytes of the IDENTIFIER field. If the ALLOCATION LENGTH field of the command descriptor block is too small to transfer all of the identifier, the identifier length shall not be adjusted to reflect the truncation. IDENTIFIER field The IDENTIFIER field contains the identifier as described by the Association, Identifier Type, CODE SET, and IDENTIFIER LENGTH fields.
PAGE 495
www.seagate.com 5.4.12 Parameters for direct access devices Jumper Settings page (C2h) The Jumper Settings VPD page is obsolete and not supported on newer products.
PAGE 496
www.seagate.com Parameters for direct access devices Drive ID field The Drive ID is shown below in Table 466. Bit 3 is the most significant bit and bit 0 is the least significant bit.
PAGE 497
www.seagate.com 5.4.13 Parameters for direct access devices Logical Block Provisioning VPD page (82h) The Logical Block Provisioning VPD page (see table 467) provides the application client with logical block provisioning related operating parameters of the logical unit. Table 467 Logical Block Provisioning VPD page Bit Byte 7 0 1 2 3 4 5 6 7 8 ...
PAGE 498
www.seagate.com Parameters for direct access devices LBPWS bit 1 A logical block provisioning write same (LBPWS) bit set to one indicates that the device server supports the use of the WRITE SAME (16) command (see 3.74) to unmap LBAs. 0 An LBPWS bit set to zero indicates that the device server does not support the use of the WRITE SAME (16) command to unmap LBAs.
PAGE 499
www.seagate.com Parameters for direct access devices PROVISIONING TYPE field The PROVISIONING TYPE field is defined in table 470. Table 470 Provisioning Type field Code Description 000b The device server does not report a provisioning type. 001b The logical unit is resource provisioned (see SBC-4). 010b The logical unit is thin provisioned (see SBC-4).
PAGE 500
www.seagate.com 5.4.14 Parameters for direct access devices Mode Page Policy VPD page (87h) The Mode Page Policy VPD page (see table 472) indicates which mode page policy (see table 3.9) is in effect for each mode page supported by the logical unit. Table 472 Mode Page Policy VPD page Bit Byte 7 0 1 2 3 6 5 4 3 PERIPHERAL QUALIFIER 2 1 0 PERIPHERAL DEVICE TYPE PAGE CODE (87h) (MSB) PAGE LENGTH (n-3) (LSB) Mode page policy descriptor list 4 ... 7 ... n-3 ...
PAGE 501
www.seagate.com Parameters for direct access devices POLICY PAGE CODE field and POLICY SUBPAGE CODE field The POLICY PAGE CODE field and POLICY SUBPAGE CODE field indicate the mode page and subpage to which the descriptor applies. If the first mode page policy descriptor in the list contains a POLICY PAGE CODE field set to 3Fh and a POLICY SUBPAGE CODE field set to FFh, then the descriptor applies to all mode pages and subpages not described by other mode page policy descriptors.
PAGE 502
www.seagate.com 5.4.15 Parameters for direct access devices Power Conditions Vital Product Data page (8Ah) The Power Condition VPD page (see table 475) indicates which power conditions (see SPC-5) are supported by the logical unit and provides information about how those power conditions operate.
PAGE 503
www.seagate.com Parameters for direct access devices IDLE_B power conditions support bit 1 This bit set to one indicates that the logical unit supports the idle_b power condition as described in this subclause. 0 A IDLE_B bit set to zero indicates that the logical unit does not support the idle_b power condition. IDLE_A power conditions support bit 1 This bit set to one indicates that the logical unit supports the idle_a power condition as described in this subclause.
PAGE 504
www.seagate.com 5.4.16 Parameters for direct access devices Power Consumption Vital Product Data page (8Dh) The Power Consumption VPD page (see table 476) provides an application client with a list of the available settings to limit the maximum power consumption of the logical unit while in the active power condition (see SPC-5).
PAGE 505
www.seagate.com Parameters for direct access devices PAGE CODE and PAGE LENGTH fields The PAGE CODE field and PAGE LENGTH field are defined in SPC-5, and shall be set to the value shown in table 476 for the Power Consumption VPD page. Each power consumption descriptor (see table 477) describes one maximum power consumption level that the application client may establish for use by the active power condition (see SPC-5) using the Power Consumption mode page (see 5.3.20) as described in SPC-5.
PAGE 506
www.seagate.com 5.4.17 Parameters for direct access devices SCSI Ports VPD page (88h) The SCSI Ports VPD page (see table 479) contains designation descriptors for all the SCSI ports in a SCSI target device. The SCSI Ports VPD page only reports information on SCSI ports known to the device server processing the INQUIRY command. The REPORT LUNS well-known logical unit (see 3.33) may be used to return information on all SCSI ports in the SCSI device (i.e., all target ports and all initiator ports).
PAGE 507
www.seagate.com Parameters for direct access devices PAGE CODE and PAGE LENGTH fields The PAGE CODE field and PAGE LENGTH field are defined in SPC-5, and shall be set to the value shown in table 479 for the SCSI Ports VPD page. Each SCSI port designation descriptor (see table 480) identifies a SCSI port. The SCSI port designation descriptors may be returned in any order.
PAGE 508
www.seagate.com Parameters for direct access devices RELATIVE PORT IDENTIFIER field The RELATIVE PORT IDENTIFIER field (see table 481) contains the relative port identifier of the SCSI port to which the SCSI port designation descriptor applies.
PAGE 509
www.seagate.com 5.4.18 Parameters for direct access devices Supported Vital Product Data pages (00h) This clause contains a list of the vital product data page codes supported by the target or logical unit (see table 483). If a target supports any vital product data pages, it also shall support this vital product data page.
PAGE 510
www.seagate.com 5.4.19 Parameters for direct access devices Unit Serial Number page (80h) The Unit Serial Number page provides a product serial number for the target or logical unit. See Table 484 following. Table 484 Unit Serial Number page (80h) Bit Byte 7 0 6 5 4 3 PERIPHERAL QUALIFIER 2 1 0 PERIPHERAL DEVICE TYPE 1 PAGE CODE (80h) 2 Reserved 3 PAGE LENGTH 4 ...
PAGE 511
www.seagate.com 5.4.20 Parameters for direct access devices Zoned Block Device Characteristics VPD page (B6h) The Zoned Block Device Characteristics VPD page (see table 485) provides a list of parameters that are specific to zoned block devices. Table 485 Bit Byte Zoned Block Device Characteristics VPD page 7 0 6 5 4 3 PERIPHERAL QUALIFIER 1 2 1 0 PERIPHERAL DEVICE TYPE PAGE CODE (B6h) 2 PAGE LENGTH (003Ch) 3 4 Reserved URSWRZ 5 ... Reserved 7 8 (MSB) ...
PAGE 512
www.seagate.com Parameters for direct access devices PERIPHERAL QUALIFIER and PERIPHERAL DEVICE TYPE fields The PERIPHERAL QUALIFIER field and PERIPHERAL DEVICE TYPE field are defined in standard INQUIRY data (see 3.6.2). PAGE CODE and PAGE LENGTH fields The PAGE CODE field and PAGE LENGTH field are defined in SPC-5 and shall be set to the values shown in table 485 for the Zoned Block Device Characteristics VPD page.
PAGE 513
Index A Abbreviations 33 ABPF.
PAGE 514
Index Direct access block commands 65 Disable Discovery Fibre Channel Interface Control page 435, Disable Loop Master Fibre Channel Interface Control page 435, Disable Page Out bit 139 Disable Prefetch Transfer Length Caching Parameters page 392 Disable Soft Address Fibre Channel Interface Control page 435, Disable Target Fabric Discovery Fibre Channel Interface Control page 435, Disable Target Initiated Port Enable Fibre Channel Interface Control page 435, Disable Target Oriented Loop Initialization Fibre
PAGE 515
Index Mode parameters 376 Caching Parameters page 391 Control Extension mode page 403 Control mode page 397 Disconnect-Reconnect mode page for FCP 405 Disconnect-Reconnect mode page for SAS 408 General block descriptor format 380 MODE DATA LENGTH field 379 Mode parameter header 378 Mode parameter header formats 378 Mode parameter list format 378 Page_0 Mode page format 384 Power Condition mode page 422 Sub_page mode page format 384 Verify Error Recovery mode page 467 Mode Select command 45 MODE SELECT(10) c
PAGE 516
Index READ (32)command 142 READ (6) command 134 READ DEFECT DATA command READ DEFECT DATA (10) command 160 READ DEFECT DATA (12) command 162 READ FULL STATUS 123 READ LONG command READ LONG (10) command 164 READ LONG (16) command 166 READ RESERVATION 117 READ RETRY COUNT Read-Write Error Recovery Mode page 428 READ RETRY COUNT field 432 Read-Write Error Recovery mode page 428 REASSIGN BLOCKS command 167 Rebuild Assist Input diagnostic page 299 Rebuild Assist Output diagnostic page 300 RECEIVE DIAGNOSTIC RES
PAGE 517
Index WRITE AND VERIFY (12) command 258 WRITE AND VERIFY (16) command 259 WRITE AND VERIFY (32) command 260 WRITE ATOMIC (32) command 263 WRITE BUFFER command 264 WRITE command WRITE (10) command 249 WRITE (12) command 253 WRITE (16) command 254 WRITE (32) command 255 WRITE (6) command 248 WRITE LONG command WRITE LONG (10) command 273 WRITE LONG (16) command 274 WRITE RETRY COUNT Read-Write Error Recovery Mode page 428 WRITE RETRY COUNT field 432 WRITE STREAM (16) command 280 SCSI Commands Reference Manua
PAGE 518
Seagate Technology LLC AMERICAS Seagate Technology LLC 10200 South De Anza Boulevard, Cupertino, California 95014, United States, 408-658-1000 ASIA/PACIFIC Seagate Singapore International Headquarters Pte. Ltd. 7000 Ang Mo Kio Avenue 5, Singapore 569877, 65-6485-3888 EUROPE, MIDDLE EAST AND AFRICA Seagate Technology SAS 16-18 rue du Dôme, 92100 Boulogne-Billancourt, France, 33 1-4186 10 00 Publication Number: 100293068, Rev.