Seagate ST9300405SS, ST9300605SS, ST9450305SS, ST9450405SS, ST9600105SS User Manual

...

Download

Product Manual

Savvio® 10K.5 SAS

Standard Models

ST9900805SS ST9600205SS ST9450405SS ST9300605SS

Self-Encrypting Drive Models

ST9900705SS ST9600105SS ST9450305SS ST9300505SS

SED FIPS 140-2 Models

ST9900605SS ST9600005SS ST9450205SS ST9300405SS

100628561 Rev. D March 2011

Revision history

Revision Date Sheets affected or comments

Rev. A 10/22/10 Initial release. Rev. B 11/22/10 43. (drive weight) Rev. C 02/14/11 44 & 60-62. Rev. D 03/1

8/11 26

, 38-39 & 46.

LLC in the United St ates and/or other countries. Savvio and SeaTools are either trademarks or regis tered trademarks of Seagate Te chnology LLC or one of its affiliated companies in the United States and/or other countries. The FIPS logo is a certification mark of NIST, which does not imply product endorsement by NIST, the U.S., or Canadian governments. All other trademarks or registered trade marks are the property of their respective owners.

No part of this publication may be reproduced in any form without written permission of Seagate Technology LLC. Call 877-PUB-TEK1 (877-782-8351) to request permission.

One gigabyte, or GB, equals one billion bytes and one terabyte, or TB, equals one trillion bytes. Your computer's operating system may use a different standard of measurement and report a lower capacity. In addition, some of the listed capacity is used for formatting and other functions, and thus will not be available for data storage. Seagate reserves the right to change, without notice, product offerings or specifications.

Contents

1.0 Seagate Technology support services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2.0 Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

3.0 Applicable standards and reference documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.1 Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.1.1 Electromagnetic compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.1.2 Electromagnetic compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.1.3 European Union Restriction of Hazardous Substances (RoHS) . . . . . . . . . . . . . 4

3.1.4 China Restriction of Hazardous Substances (RoHS) Directive . . . . . . . . . . . . . . 5

3.2 Reference documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4.0 General description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4.1 Standard features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.2 Media description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.3 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.4 Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.5 Formatted capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.6 Programmable drive capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.7 Factory-installed options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5.0 Performance characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.1 Internal drive characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.2 Seek performance characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.2.1 Access time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5.2.2 Format command execution time for 512-byte sectors (minutes) . . . . . . . . . . . 10

5.2.3 General performance characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.3 Start/stop time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.4 Prefetch/multi-segmented cache control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.5 Cache operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.5.1 Caching write data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

5.5.2 Prefetch operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

6.0 Reliability specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

6.1 Error rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

6.1.1 Recoverable Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

6.1.2 Unrecoverable Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

6.1.3 Seek errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6.1.4 Interface errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6.2 Reliability and service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6.2.1 Annualized Failure Rate (AFR) and Mean Time Between Failure (MTBF) . . . . 14

6.2.2 Preventive maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6.2.3 Hot plugging the drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6.2.4 S.M.A.R.T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

6.2.5 Thermal monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

6.2.6 Drive Self Test (DST). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6.2.7 Product warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

7.0 Physical/electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

7.1 PowerChoiceTM power management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

7.1.1 PowerChoice reporting methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

7.2 AC power requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

7.3 DC power requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

7.3.1 Conducted noise immunity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

7.3.2 Power sequencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

7.3.3 Current profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Savvio 10K.5 SAS Product Manual, Rev. D i

7.4 Power dissipation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7.5 Environmental limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

7.5.1 Temperature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

7.5.2 Relative humidity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

7.5.3 Effective altitude (sea level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

7.5.4 Shock and vibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

7.5.5 Air cleanliness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

7.5.6 Corrosive environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

7.5.7 Acoustics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

7.5.8 Electromagnetic susceptibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

7.6 Mechanical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

8.0 About FIPS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

9.0 About self-encrypting drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

9.1 Data encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

9.2 Controlled access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

9.2.1 Admin SP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

9.2.2 Locking SP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

9.2.3 Default password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

9.3 Random number generator (RNG). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

9.4 Drive locking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

9.5 Data bands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

9.6 Cryptographic erase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

9.7 Authenticated firmware download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

9.8 Power requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

9.9 Supported commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

9.10 RevertSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

10.0 Defect and error management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

10.1 Drive internal defects/errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

10.2 Drive error recovery procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

10.3 SAS system errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

10.4 Background Media Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

10.5 Media Pre-Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

10.6 Deferred Auto-Reallocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

10.7 Idle Read After Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

10.8 Protection Information (PI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

10.8.1 Levels of PI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

10.8.2 Setting and determining the current Type Level. . . . . . . . . . . . . . . . . . . . . . . . . 51

10.8.3 Identifying a Protection Information drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

11.0 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

11.1 Drive orientation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

11.2 Cooling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

11.3 Drive mounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

11.4 Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

12.0 Interface requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

12.1 SAS features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

12.1.1 task management functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

12.1.2 task management responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

12.2 Dual port support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

12.3 SCSI commands supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

12.3.1 Inquiry data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

12.3.2 Mode Sense data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

12.4 Miscellaneous operating features and conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

ii Savvio 10K.5 SAS Product Manual, Rev. D

12.4.1 SAS physical interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

12.4.2 Physical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

12.4.3 Connector requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

12.4.4 Electrical description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

12.4.5 Pin descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

12.4.6 SAS transmitters and receivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

12.4.7 Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

12.5 Signal characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

12.5.1 Ready LED Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

12.5.2 Differential signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

12.6 SAS-2 Specification compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

12.7 Additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Savvio 10K.5 SAS Product Manual, Rev. D iii

iv Savvio 10K.5 SAS Product Manual, Rev. D

List of Figures

Figure 1. Current profiles for 900GB models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Figure 2. Current profiles for 600GB models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figure 3. Current profiles for 450GB models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Figure 4. Current profiles for 300GB models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 5. 900GB (at 3Gb) DC current and power vs. input/output operations per second . . . . . . . . . . 31

Figure 6. 900GB (at 6Gb) DC current and power vs. input/output operations per second . . . . . . . . . . 32

Figure 7. 600GB (at 3Gb) DC current and power vs. input/output operations per second . . . . . . . . . . 33

Figure 8. 600GB (at 6Gb) DC current and power vs. input/output operations per second . . . . . . . . . . 34

Figure 9. 450GB (at 3Gb) DC current and power vs. input/output operations per second . . . . . . . . . . 35

Figure 10. 450 GB (a t 6G b) DC curr en t an d po wer vs. input/output operations per second . . . . . . . . . . 36

Figure 11. 300 GB (a t 3G b) DC curr en t an d po wer vs. input/output operations per second . . . . . . . . . . 37

Figure 12. 300 GB (a t 6G b) DC curr en t an d po wer vs. input/output operations per second . . . . . . . . . . 38

Figure 13. Location of the HDA temperature check point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Figure 14. Recommended mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Figure 15. Mounting configuration dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Figure 16. Example of FIPS tamper evidence labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Figure 17. Physical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Figure 18. Air flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 19. Physical interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Figure 20. SAS device plug dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Figure 21. SAS device plug dimensions (detail) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Figure 22. SAS transmitters and receivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Savvio 10K.5 SAS Product Manual, Rev. D v

1.0 Seagate Technology support services

SEAGATE ONLINE SUPPORT and SERVICES

For information regarding products and services, visit http://www.seagate.com/www/en-us/about/contact_us/

Available services include:

Presales & Technical support Global Support Services telephone numbers & business hours Authorized Service Centers

For information regarding Warranty Support, visit

http://www.sea

For information regarding Data Recovery Services, visit http://www.i365.com For Seagate OEM & Distribution partner portal, visit https://direct.seagate.com/portal/system For Seagate reseller portal, visit http://spp.seagate.com

gate.com/www/en-us/support/warranty_&_returns_assistance

Savvio 10K.5 SAS Product Manual, Rev. D 1

2.0 Scope

This manual describes Seagate Technology® LLC, Savvio® 10K.5 SAS (Serial Attached SCSI) disc drives. Savvio drives support the SAS Protocol specifications to the extent described in this manual. The SAS Inter-

face Manual (part number 100293071) describes the general SAS characteristics of this and other Seagate SAS drives. The Self-Encrypting Drive Reference Manual, part number 100515636, describes the interface, general operation, and security features available on Self-Encrypting Drive models.

Product data communicated in this manual is specific only to the model numbers listed in this ma nual. The dat a listed in this manual may not be predictive of future generation specifications or requirements. If you are designing a system which will use one of the models listed or future generation products and need further assistance, please contact your Field Applications Engineer (FAE) or our global support services group as shown in Section 1.0.

Unless otherwise stated, the information in this manual applies to standard and Self-Encrypting Drive models.

Standard models Standard SED models SED (FIPS 140-2) models

ST9900805SS ST9900705SS ST9900605SS ST9600205SS ST9600105SS ST9600005SS ST9450405SS ST9450305SS ST9450205SS ST9300605SS ST9300505SS ST9300405SS

Note. Previous generations of Seagate Self-Encrypting Drive models were called Full Disk Encryption

(FDE) models before a differentiation between drive-based encryption and other forms of encryp tion was necessary.

Note. The Self-Encrypting Drive models indicated on the cover of this product manual have provisio ns for

“Security of Data at Rest” based on the standards defined by the Trusted Computing G roup (see www.trustedcomputinggroup.org).

For more information on FIPS 140-2 Level 2 certification see Section 8.0 on page 44.

2 Savvio 10K.5 SAS Product Manual, Rev. D

3.0 Applicable standards and reference documentation

The drives documented in this manual have been developed as system peripherals to the highest standards of design and construction. The drives depend on host equipment to provide adequate power and environment for optimum performance and compliance with applicable industry and governmental regulations. Special attention must be given in the areas o f safety, power distribution, shielding, audible noise control, and temperature regulation. In particular, the drives must be securely mounted to guarantee the specified performance characteristics. Mounting by bottom holes must meet the requirements of Section 11.3.

3.1 Standards

The Savvio family complies with Seagate standards as noted in the a ppropriate sectio ns of this manual and the Seagate SAS Interface Manual, part number 100293071.

The drives are recognized in accordance with UL 60950-1 as tested by UL, CSA 60950-1 as tested by CSA, and EN60950-1 as tested by TUV.

The security features of Self-Encrypting Drive models are based on the “TCG Storage Architecture Core Specification” and the “TCG Storage Workgroup Security Subsystem Class: Enterprise_A” specification with additional vendor-unique features as noted in this product manual.

3.1.1 Electromagnetic compatibility

The drive, as delivered, is designed for system integration and installation into a suitable enclosure prior to use. The drive is supplied as a subasse mbly and is not s ubject to Subpart B o f Part 15 of the F CC Rules and Regulations nor the Radio Interference Reg ula tio ns of the Canadian Department of Communications.

The design characteristics of the drive serve to minimize radiation when installed in an enclosure that provides reasonable shielding. The drive is capable of meeting the Class B limits of the FCC Rules and Regulations of the Canadian Department of Communications when properly packaged; however, it is the user’s responsibility to assure that the drive meets the appropriate EMI requirements in their system. Shielded I/O cables may be required if the enclosure does not provide adequate shielding. If the I/O cables are external to the enclosure, shielded cables should be used, with the shields grounded to the enclosure and to the host controller.

3.1.1.1 Electromagnetic susceptibility

As a component assembly, the drive is not required to meet any susceptibility performance requirements. It is the responsibility of those integrating the drive within their systems to perform those tests required and design their system to ensure that equipment operating in the same system as the drive or external to the system does not adversely affect the performance of the drive. See Tables 2 through 5, DC power requirements.

Savvio 10K.5 SAS Product Manual, Rev. D 3

3.1.2 Electromagnetic compliance

Seagate uses an independent laboratory to confirm compliance with the directives/standards for CE Marking and C-Tick Marking. The drive was teste d in a repr esent ative system for typical applications. The selected system represents the most popular characteristics for test platforms. The system configurations include:

• Typical current use microprocessor

• Keyboard

• Monitor/display

• Printer

•Mouse Although the test system with this Seagate model complies with the directives/standards, we cannot guarantee

that all systems will comply. The computer manufacturer or system integrator shall confirm EMC compliance and provide the appropriate marking for their product.

Electromagnetic compliance for the European Union

If this model has the CE Marking it complies with the European Union requirements of the Electromagnetic Compatibility Directive 2004/108/EC as put into place on 20 July 2007.

Australian C-Tick

If this model has the C-Tick Marking it complies with the Australia/New Zealand Standard AS/NZ CISPR22 an d meets the Electromagnetic Compatibility (EMC) Framework requirements of Australia’s Spectrum Management Agency (SMA).

Korean KCC

If these drives have the Korean Communications Commission (KCC) logo, they comply with KN22 and KN61000.

Taiwanese BSMI

If this model has the Taiwanese certification mark then it complies with Chinese National S t andar d, CNS13438.

3.1.3 European Union Restriction of Hazardous Substances (RoHS)

The European Union Restriction of Hazardous Substances (RoHS) Directive restricts the presence of chemical substances, including Lead (Pb), in electronic products effective July 2006.

A number of parts and materials in Seagate products are procured from external suppliers. We rely on the representations of our suppliers regarding the presence of RoHS substances in these parts and materials. Our supplier contracts require compliance with our ch emical substance restrictions, and our suppliers document their compliance with our requirements by providing material conten t declarations for all p arts and materials for the disc drives documented in this publication. Current supplier declarations include disclosure of the inclusion of any RoHS-regulated substance in such parts or materials.

Seagate also has internal systems in place to ensure on going compliance with the RoHS Directive and all laws and regulations which restrict chemical content in electronic products. These systems include st andard ope rating procedures that ensure that restricted substances are not utilized in our manufacturing operations, laboratory analytical validation testing, and an internal auditing process to ensure that all standard operating procedures are complied with.

4 Savvio 10K.5 SAS Product Manual, Rev. D

3.1.4 China Restriction of Hazardous Substances (RoHS) Directive

This product has an Environmental Protection Use Period (EPUP) of 20 years. The following table contains information mandated by China's "Marking Requirements for Control of Pollution Caused by Electronic Information Products" Standard.

"O" indicates the hazardous and toxic substa nce content of the p art (at the homogenou s material level) is lower than the threshold defined by the China RoHS MCV Standard.

"X" indicates the hazardous and toxic substance content of the part (at the homogenous material level) is over the threshold defined by the China RoHS MCV Standard.

3.2 Reference documents

SCSI Commands Reference Manual Seagate part number: 100293068 SAS Interface Manual Seagate p ANSI SAS Documents

SFF-8223 2.5” Drive Form Factor with Serial Connector SFF-8460 HSS Backplane Design Guidelines SFF-8470 Multi Lane Copper Connector SFF-8482 SAS Plug Connector ANSI INCITS.xxx Serial Attached SCS ISO/IEC 14776-xxx SCSI Architecture Model-3 (SAM-4) Standard (T10/1683-D) ISO/IEC 14776-xxx SCSI Primary Commands-3 (SPC-3) Stand ard (T10/1416- D) ISO/IEC 14776-xxx SCSI Block Commands-3 (SBC-2) Standard (T10/1417-D)

ANSI Small Computer System In

Trusted Computing Group (TCG) Documents (apply

Self-Encrypting Drives Reference Manual Seagate part number: 100515636 In case of conflict between this document and any re

terface (SCSI) Documents

X3.270-1996 (SCSI-3) Architecture Model

to Self-Encrypting Drive models only) TCG Storage Architecture Core Specification, Rev. 1.0 TCG Storage Security Subsystem Class Enterprise Specification, Rev. 1.0

ferenced document, this document takes precedence.

art number: 100293071

I (SAS-2) Stan dard (T10/1760-D)

Savvio 10K.5 SAS Product Manual, Rev. D 5

4.0 General description

Savvio drives provide high performance, high capacity data storage for a variety of systems including engineering workstations, network servers, mainframes, and supercomputers. The Serial Attached SCSI interface is designed to meet next-generation computing demands for performance, scalability, flexibility and high-density storage requirements.

Savvio drives are random access storage devices designed to support the Serial Attached SCSI Protocol as described in the ANSI specifications, this document, and the SAS Interface Manual (part number 100293071) which describes the general interface characteristics of this drive. Savvio drives are classified as intelligent peripherals and provide level 2 conformance (highest level) with the ANSI SCSI-1 standard. The SAS connectors, cables and electrical interface are compatible with Serial ATA (SATA), giving future users the choice of populating their systems with either SAS or SATA hard disc drives. This allows you to continue to leverage your existing investment in SCSI while gaining a 6Gb/s ser ial da ta transfer rate .

The Self-Encrypting Drive models indicated on the cover of this product manual have provisions for “Security of Data at Rest” based on the st andards defined by the Trusted Computing Group (see www.trustedcomputinggroup.org).

Note. Never disassemble the HDA and do not attempt to service items in the sealed enclosure (heads,

media, actuator, etc.) as this requires special facilities. The drive does not contain user-replaceable parts. Opening the HDA for any reason voids your warranty.

Savvio drives use a dedicated load/u nload zo ne at the o utermost radius of the media to eliminate the possibility of destroying or degrading data by landing in the data zone. The heads automatically go to the ramp load/ unload when power is removed from the drive.

An automatic shipping lock prevents potential damage to the heads and discs that results from movement during shipping and handling. The shipping lock disengages and the head load process begins when power is applied to the drive.

The drives also use a high-performance actuator assembly with a low-inertia, balanced, patented, straight arm design that provides excellent performance with minimal power dissipation.

6 Savvio 10K.5 SAS Product Manual, Rev. D

4.1 Standard features

Savvio® 10K.5 SAS drives have the following standard features:

• 1.5 / 3 / 6 Gb Serial Attached SCSI (SAS) interface

• Integrated dual port SAS controller supporting the SCSI protocol

• Support for SAS expanders and fanout adapters

• Firmware downloadable using the SAS interface

• 128 - deep task set (queue)

• Supports up to 32 initiators

• Jumperless configuration

• User-selectable logical block size (512, 520, 524 or 528 bytes per logical block)

• Industry standard SFF 2.5-inch dimensions

• Programmable logical block reallocation scheme

• Flawed logical block reallocation at format time

• Programmable auto write and read reallocation

• Reallocation of defects on command (Post Format)

• ECC maximum burst correction length of 444 bits

• No preventive maintenance or adjustments required

• Dedicated head load/unload zone and automatic shipping lock

• Embedded servo design

• Self diagnostics performed when power is applied to the drive

• Zone bit recording (ZBR)

• Vertical, horizontal, or top down mounting

• Dynamic spindle brake

• 64MB data buffer (see Section 5.5)

• Drive Self Test (DST)

• Background Media Scan (BMS)

• Idle Read After Write (IRAW)

• Power Choice Savvio® 10K.5 SAS Self-Encrypting Drive models have the following additional features:

• Automatic data encryption/decryption

• Controlled access

• Random number generator

• Drive locking

• 16 independent data bands

• Cryptographic erase of user data for a drive that will be repurposed or scrapped

• Authenticated firmware download

4.2 Media description

The media used on the drive has an glass substrate coated with a thin film magnetic material, overcoated with a proprietary protective layer for improved durability and environmental protection.

4.3 Performance

• Programmable multi-segmentable cache buffer

• 600MB/s maximum instantaneous data transfers.

• 10K RPM spindle. Average latency = 3.0ms

• Background processing of queue

• Supports start and stop commands (spindle stops spinning)

• Adaptive seek velocity; improved seek performance

Savvio 10K.5 SAS Product Manual, Rev. D 7

Note. There is no significant performance difference between Self-Encrypting Drive and standard (non-

Self-Encrypting Drive) models.

4.4 Reliability

• Annualized Failure Rate (AFR) of 0.44%

• Mean time between failures (MTBF ) of 2,00 0 ,0 00 hou rs

• Balanced low mass rotary voice coil actuator

• Incorporates industry-standard Self-Monitoring Analysis and Reporting Technology (S.M.A.R.T.)

• 5-year warranty

4.5 Formatted capacities

Standard OEM models are formatted to 512 bytes per block. The block size is selectable at format time and must be a multiple of 4 bytes. Users having the necessary equipment may modify the data block size before issuing a format command and obtain different formatted capacities than those listed.

To provide a stable target capacity environment and at the same time provide users with flexibility if they choose, Seagate recommends product planning in one of two modes:

Seagate designs specify capacity points at certain block sizes that Seagate guarantees current and future products will meet. We recommend customers use this capacity in their project planning, as it ensures a stable operating point with backward and forward compatibility from generation to generation. The current guaranteed operating points for this product are shown below.

Capacity (Blocks)

Sector Size

512 520 524 528

1,758,174,768 68CB9E30h 1,172,123,568 45DD2FB0h 879,097,968 3465F870h 585,937,500 22ECB25Ch 1,720,961,544 6693CA08h 1,147,307,696 446286B0h 860,480,776 3349E508h 573,653,848 22314358h 1,698,023,400 6535C7E8h 1,132,015,600 43792FF0h 849,011,704 329AE3F8h 566,007,800 21BC97F8h 1,673,624,336 63C17B10h 1,115,749,560 4280FCB8h 836,812,168 31E0BD88h 557,874,778 21407E5Ah

900GB 600GB 450GB 300GB

Decimal Hex Decimal Hex Decimal Hex Decimal Hex

4.6 Programmable drive capacity

Using the Mode Select command, the drive can change its capacity to something less than maximum. See the Mode Select (6) parameter list table in the SAS Interface Manual, part number 100293071. A value of zero in the Number of Blocks field indicates that the drive will not change the capacity it is currently formatted to have. A number other than zero and less than the maximum number of LBAs in the Number of Blocks field changes the total drive capacity to the value in the Number of Blocks field. A value greater than the maximum number of LBAs is rounded down to the maximum capacity.

4.7 Factory-installed options

You may order the following items which are incorporated at the manufacturing facility during production or packaged before shipping. Some of the options available are (not an exhaustive list of possible options):

• Other capacities can be ordered depending on sparing scheme and sector size requested.

• Single-unit shipping pack. The drive is normally shipped in bulk packaging to provide ma ximum protection against transit damage. Units shipped individually require additional protection as p rovided by the sin gle unit shipping pack. Users planning single unit distribution should specify this option.

•The Safety and Regulatory Agency Specifications, part number 75789512, is usually included with each standard OEM drive shipped, but extra copies may be ordered.

8 Savvio 10K.5 SAS Product Manual, Rev. D

5.0 Performance characteristics

This section provides detailed information concerning performance-related cha racteristics and featu res of Savvio drives.

5.1 Internal drive characteristics

ST9900805SS ST9600205SS ST9450405SS ST9300605SS ST9900705SS ST9600105SS ST9450305SS ST9300505SS ST9900605SS ST9600005SS ST9450205SS ST9300405SS

Drive capacity 900 600 450 300 GB Read/write data heads 6 4 3 2 Bytes per track 821.4 821.4 821.4 821.4 KBytes Bytes per surface 151,800 151,800 151,800 151,800 MB (unformatted, rounded off value) Tracks per surface (total) 184,799 184,799 184,799 184,799 Tracks Tracks per inch 300 300 300 300 KTPI (average) Peak bits per inch 1686 1686 1686 1686 kBPI Areal density 506 506 506 506 Gb/in Disc rotation speed 10K 10K 10K 10K rpm Avg rotational latency 3.0 3.0 3.0 3.0 ms

5.2 Seek performance characteristics

See Section 12.4.1, "SAS physical interface" on page 67 and the SAS Interface Manual (part number

100293071) for additional timing details.

(formatted, rounded off value)

(avg, rounded off values)

(user accessible)

5.2.1 Access time

Including controller overhead2 (ms)

Not including controller overhead

1,2

(ms)

Read Write Read Write

Average Single track 0.4 0.6 0.2 0.4

900GB models

3,4

Typical

3.9 4.3 3.7 4.1

Full stroke 7.9 8.3 7.7 8.1 Average Single track 0.4 0.6 0.2 0.4 Full stroke 7.3 7.6 7.1 7.4

600, 450, 300GB models Typical

3.6 4.0 3.4 3.8

1. Execution time measured from receipt of the Command to the Response.

2. Assumes no errors and no sector has been relocated.

3. Typical access times are measured under nominal conditions of temperature, voltage, and horizontal orientation as measured on a representative sample of drives.

4. Access time = controller overhead + average seek time and applies to all data transfer commands. Access to data = access time + latency time.

Savvio 10K.5 SAS Product Manual, Rev. D 9

5.2.2 Format command exe cu ti o n tim e fo r 512-b y te secto r s (mi nut es ) 900GB 600GB 450GB 300GB

Maximum (with verify) Maximum (without verify)

234 156 117 78 116 75 58 36

Note. There is approximately a 1.5 increase in time to format a SED drive versus a non-SED drive of the same capacity.

5.2.3 General performance characteristics

Minimum sector interleave 1 to 1 Data buffer to/from disc media (one 512-byte logical block)* 1.00 to 1.91 Gb/s Sustained transfer rate 89 to 160 MiB/s **

93 to 168 MB/s

SAS Interface maximum instant

Logical block sizes

512 (default), 520, 524 or 528. Read/write consecutive sectors on a track Yes Flaw reallocation performance impact (for flaws reallocated at format time using the

spare sectors per sparing zone reallocation scheme.) Average rotational latency 3.0ms

aneous transfer rate 600 MB/s* per port

(dual port = 1200 MB/s*)

Negligible

*Assumes no errors and no relocated logical blocks. Rate measured from the host. ** MiB/s x 1.048 = MB/s

from the start of the first logical block transfer to or

5.3 Start/stop time

The drive accepts the commands listed in the SAS Interface Manual less than 3 seconds after DC power has been applied.

If the drive receives a NOTIFY (ENABLE SPINUP) primitive through either port and has not received a START STOP UNIT command with the START bit equal to 0, the drive becomes ready for normal operations within 30 seconds (excluding the error recovery procedure).

If the drive receives a START STOP UNIT command with the START bit equal to 0 before receiving a NOTIFY (ENABLE SPINUP) primitive, the drive waits for a START ST OP UNIT command with the START bit equal to 1. After receiving a START STOP UNIT command with the START bit equal to 1, the drive waits for a NOTIFY (ENABLE SPINUP) primitive. After receiving a NOTIFY (ENABLE SPINUP) primitive through either port, the drive becomes ready for normal operations within 20 seconds (excluding the error r ecovery procedure).

If the drive receives a START STOP UNIT command with the START bit and IMMED bit equal to 1 and does not receive a NOTIFY (ENABLE SPINUP) primitive within 5 seconds, the drive fails the START STOP UNIT command.

The ST AR T STOP UNIT command may be used to command the drive to stop the spin dle. Stop time is 20 seconds (maximum) from removal of DC power. SCSI stop time is 20 seconds. There is no power control switch on the drive.

10 Savvio 10K.5 SAS Product Manual, Rev. D

5.4 Prefetch/multi-segmented cache control

The drive provides a prefetch (read look-ahead) and multi-segmented cache control algorithms that in many cases can enhance system performance. Cache refers to the drive buffer storage space when it is used in cache operations. To select this feature, the host sends the Mod e Select command with the proper value s in the applicable bytes in page 08h. Prefetch and cache operations are independent features from the standpoint that each is enabled and disabled independently using the Mode Select command; however, in actual operation, the prefetch feature overlaps cache operation somewhat as described in sections 5.5.1 and 5.5.2.

All default cache and prefetch mode parameter values (Mode Page 08h) for standard OEM versions of this drive family are given in Table 12.

5.5 Cache operation

Note. Refer to the SAS Interface Manual for more detail concernin g the cach e bi ts. Of the 64MB physical buffer space in the drive, approximately 30,000KB are available as a data cache. The

remaining buffer space is reserved for internal drive use. The drive keeps track of the logical block addresses of the data stored in each segment of the buffer. If the

cache is enabled (see RCD bit in the SAS Interface Manual ), data requested by the host with a read command is retrieved from the buffer, if possible, before any disc access is initiated. If cache operation is not enabled, the buffer is still used, but only as circular buffer segments during disc medium read operations (disregarding Prefetch operation for the moment). That is, the drive does not check in the buffer segments for the requested read data, but goes directly to the medium to retrieve it. The retrieved data merely passes through some buffer segment on the way to the host. All data transfers to the host are in accordance with buffer-full ratio rules. See the explanation provided with the information about Mode Page 02h (disconnect/reconnect control) in the SAS

Interface Manual.

The following is a simplified description of the prefetch/cache operation: Case A—read command is received and all of the requested logical blocks are already in the cache:

1. Drive transfers the requested logical blocks to the initiator. Case B—A Read command requests data, and at least one requested logical block is not in any segment of

the cache:

1. The drive fetches the requested logical blocks from the disc and transfers them into a segment, and then from there to the host in accordance with the Mode Select Disconnect/Reconnect parameters, page 02h.

2. If the prefetch feature is enabled, refer to sect io n 5.5.2 for operation from this point.

Each cache segment is actually a self-contained circular buffer whose length is an integer number of logical blocks. The drive dynamically creates and removes segments based on the workload. The wrap-around capability of the individual segments greatly enhances the cache’s overall performance.

Note. The size of each segment is not reported by Mode Sense command page 08h, bytes 14 and 15.

The value 0XFFFF is always reported regardless of the actual size of the segment. Sending a size specification using the Mode Select command (bytes 14 and 15) does not set up a new segment size. If the STRICT bit in Mode page 00h (byte 2, bit 1) is set to one, the drive responds as it does for any attempt to change an unchangeable parameter.

Savvio 10K.5 SAS Product Manual, Rev. D 11

5.5.1 Caching write data

Write caching is a write operation by the drive that ma kes use o f a drive b uffer storage area wher e the da ta to be written to the medium is stored while the drive performs the Write command.

If read caching is enabled (RCD=0), then data written to the medium is retained in the cache to be made available for future read cache hits. The same buffer space and segmentation is used as set up for read functions. The buffer segmentation scheme is set up or changed independently, having nothing to do with the state of RCD. When a write command is issued, if RCD=0, the cache is first checked to see if any logical blocks that are to be written are already stored in the cache from a previous read or write command. If there are, the respective cache segments are cleared. The new data is cached for subsequent Read commands.

If the number of write data logical blocks exceed the size of the se gment being written into, when the end of the segment is reached, the data is written into the beginning of the same cache segment, overwriting the data that was written there at the beginning of the operation; however, the drive does not overwrite data that has not yet been written to the medium.

If write caching is enabled (WCE=1), then the drive may return Good status on a write command after the data has been transferred into the cache, but before the data has been written to the medium. If an error occurs while writing the data to the medium, and Good status has already been returned, a deferred error will be generated.

The Synchronize Cache command may be used to force the drive to write all cached write data to the medium. Upon completion of a Synchronize Cache command, all data received from previous write commands will have been written to the medium. Tables 11, 12, 13 and 14 show the mode default settings for the drive.

5.5.2 Prefetch op e r at io n

If the Prefetch feature is enabled, data in contiguous logical blocks on the disc immediately beyond that which was requested by a Read command are retrieved and stored in the buffer for immediate transfer from the buffer to the host on subsequent Read commands that request those logical blocks (this is true even if cache operation is disabled). Though the pr ef etch operation uses the buffer as a cache, finding the requested data in the buffer is a prefetch hit, not a cache operation hit.

To enable Prefetch, use Mode Select page 08h, byte 12, bit 5 (Disable Read Ahead - DRA bit). DRA bit = 0 enables prefetch.

The drive does not use the Max Prefetch field (bytes 8 and 9) or the Prefetch Ceiling field (bytes 10 and 11). When prefetch (read look-ahead) is enabled (enabled by DRA = 0), the drive enables prefetch of contiguous

blocks from the disc when it senses that a prefetch hit will likely occur. The drive disables prefetch when it decides that a prefetch hit is not likely to occur.

12 Savvio 10K.5 SAS Product Manual, Rev. D

6.0 Reliability specifications

The following reliability specifications assume correct host and drive operational interface, including all interface timings, power supply voltages, environmental requirements and drive mounting constraints.

Seek error rate: Less than 10 errors in 10 Read Error Rates

Recovered Data Less than 10 errors in 1012 bits transferred (OEM default settings) Unrecovered Data Less than 1 sector in 10

Miscorrected Data Less than 1 sector in 10 Interface error rate: Less than 1 error in 10 Mean Time Between Failure (MTBF): 2,000,000 hours Annualized Failure Rate (AFR): 0.44% Preventive maintenance: None required

1. Error rate specified with automatic retries and data correction with ECC enabled and all flaws reallocated.

6.1 Error rates

The error rates stated in this manual assume the following:

• The drive is operated in accordance with this manual using DC power as defined in paragraph 7.3, "DC power requirements."

• Errors caused by host system failures are excluded from error rate computations.

• Assume random data.

• Default OEM error recovery settings are applied. This includes AWRE, ARRE, full read retries, full write retries and full retry time.

seeks

bits transferred

6.1.1 Recoverable Errors

Recoverable errors are those detected and corrected by the drive, and do not require user intervention. Recoverable Data errors will use Error Correction when needed. Recovered Data error rate is determined using read bits transferred for recoverab le errors occurring during a

read, and using write bits transferred for recoverable errors occurring during a write.

6.1.2 Unrecoverable Errors

An unrecoverable data error is def ined as a failure of the d rive to recover data from the media. These errors occur due to head/media or write problems. Unrecoverable data errors are only detected during read operations, but not caused by the read. If an unrecoverable data error is detected, a MEDIUM ERROR (03h) in the Sense Key will be reported. Multiple unrecoverable data errors resulting from the same cause are treated as 1 error.

Savvio 10K.5 SAS Product Manual, Rev. D 13

6.1.3 Seek errors

A seek error is defined as a failure of the drive to position the heads to the addressed track. After detecting an initial seek error, the drive automatically performs an error recovery process. If the error recovery process fails, a seek positioning error (Error code = 15h or 02h) will be reported with a Hardware error (04h) in the Sense Key. Recoverable seek errors are specified at Less than 10 errors in 10

seeks. Unrecoverable seek errors

(Sense Key = 04h) are classified as drive failures.

6.1.4 Interface errors

An interface error is defined as a failure of the receiver on a port to recover the data as transmitted by the device port connected to the receiver. The error may be detected as a running disparity error, illegal code, loss of word sync, or CRC error.

6.2 Reliability and service

You can enhance the reliability of Savvio disc drive s by ensuring th at the drive receives adequate co oling. Section 7.0 provides temperature measurements and other information that may be used to enhance the service life of the drive. Section 11.2 provides recommended air-flow information.

6.2.1 Annualized Failure Rate (AFR) and Mean Time Between Failure (MTBF)

The production disc drive shall achieve an AFR of 0.44% (MTBF of 2,000,000 hours) when operated in an environment that ensures the HDA case temperatures do not exceed the values specified in Section 7.5. Operation at case temperatures outside the specifications in Section 7.5 may increase the product AFR (decrease the MTBF). The AFR (MTBF) is a population statistic not relevant to individual units.

The AFR (MTBF) specification is based on the following assumptions for Enterprise Storage System environments:

• 8760 power-on hours per year.

• 250 average on/off cycles per year.

• Operations at nominal voltages.

• Systems will provide adequate cooling to ensure the case temperatures specified in Section 7.5 are not exceeded. Temperatures outside the specifications in Section 7.5 will increase the product AFR and decrease the MTBF.

6.2.2 Preventive maintenance

No routine scheduled preventive maintenance is required.

6.2.3 Hot plugging the drive

When a disc is powered on by switching the power or hot plugged, the drive runs a self test before attempting to communicate on its’ interfaces. When the self test completes successfully, the drive initiates a Link Reset starting with OOB. An attached device should respond to the link reset. If the link reset attempt fails, or any time the drive looses sync, the drive initiated link reset. The drive will initiate link reset once per second but alternates between port A and B. Therefore each port will attempt a link reset once per 2 seconds assuming both ports are out of sync.

If the self-test fails, the drive does not respond to link reset on the failing port. Note. It is the responsibility of the systems integrator to assure that no temperature, energy, voltage haz-

ard, or ESD potential hazard is presented during the hot connect/disconnect operation. Discharge the static electricity from the drive carrier prior to inserting it into the system.

Caution. The drive motor must come to a complete stop prior to changing the plane of operation. This time is

required to insure data integrity.

14 Savvio 10K.5 SAS Product Manual, Rev. D

6.2.4 S.M.A.R.T.

S.M.A.R.T. is an acronym for Self-Monitoring Analysis and Reporting Technology. This technology is intended to recognize conditions that indicate imminent drive failure and is designed to provide sufficient warning of a failure to allow you to back up the data before an actual failure occurs.

Note. The drive’s firmware monitors specific attributes for degrad ation over time but can’t predict inst ant a-

neous drive failures.

Each monitored attribute has been selected to monitor a specific set of failure conditions in the operating performance of the drive and the thresholds are optimized to minimize “false” and “failed” predictions.

Controlling S.M.A.R.T.

The operating mode of S.M.A.R.T. is controlled by the DEXCPT and PERF bits on the Informational Exceptions Control mode page (1Ch). Use the DEXCPT bit to enable or disable the S.M.A.R.T. feature. Setting the DEXCPT bit disables all S.M.A.R.T. functions. When enabled, S.M.A.R.T. collects on-line data as the drive performs normal read and write operations. When the PERF bit is set, the drive is considered to be in “On-line Mode Only” and will not perform off-line functions.

You can measure off-line attributes and force the drive to save the data by using the Rezero Unit command. Forcing S.M.A.R.T. resets the timer so that the next scheduled interrupt is in one hour.

You can interrogate the drive through the host to dete rmine the time rema ining before the next sch eduled measurement and data logging process occurs. To accomplish this, issue a Log Sense command to log page 0x3E. This allows you to control when S.M.A.R.T. interruptions occur. Forcing S.M.A.R.T. with the RTZ command resets the timer.

Performance impact

S.M.A.R.T. attribute data is saved to the disc so that the events that caused a predict ive failure can be recreated. The drive measures and saves parameters once every hour subject to an idle period on the drive interfaces. The process of measuring off-line attribute data and saving data to the disc is interruptable. The maximum on-line only processing delay is summarized below

Maximum processing delay

Fully-enabled delay DEXCPT = 0

S.M.A.R.T. delay times 75 ms

Reporting control

Reporting is controlled by the MRIE bits in the Informational Exceptions Control mode page (1Ch). Subject to the reporting method. For example, if the MRIE is set to one, the firmware will issue to the host an 01-5D00 sense code. The FRU field contains the type of predictive failure that occurred. The error code is preserved through bus resets and power cycles.

Determining rate

S.M.A.R.T. monitors the rate at which erro rs occur and sig nals a pred ictive fai l ure if the ra te of d egrad ed er ro rs increases to an unacceptable level. To determine rate, error events are logged a nd compared to the number of total operations for a given attribute. The interval defines the number of operations o ver whic h to m easur e the rate. The counter that keeps track of the current numbe r of operations is referred to as the Interval Counter.

S.M.A.R.T. measures error rates. All errors for each monitored attribute are recorded. A counter keeps track of the number of errors for the current interval. This counter is referred to as the Failure Counter.

Savvio 10K.5 SAS Product Manual, Rev. D 15

Error rate is the number of errors per operation. The algori thm that S.M.A.R.T. uses to record rates of error is to set thresholds for the number of errors and their interval. If the number of errors exceeds the threshold before the interval expires, the error rate is considered to be unacceptable. If the number of errors does not exceed the threshold before the interval expires, the error rate is considered to be acceptable. In either case, the interval and failure counters are reset and the process starts over .

Predictive failures

S.M.A.R.T. signals predictive failures when the drive is performing unacceptably for a period of time. The firmware keeps a running count of the number of times the error rate for each attribute is unacceptable. To accomplish this, a counter is incremented e ach time the erro r rate is unacceptable and decremented (not to exceed zero) whenever the error rate is acceptable. If the counter continually increments such that it reaches the predictive threshold, a predictive failure is signaled. This counter is referred to as the Failure History Counter. There is a separate Failure History Counter for each attribute.

6.2.5 Thermal monitor

Savvio drives implement a temperature warning system which:

1. Signals the host if the temperature exceeds a value which would threate n the drive.

2. Signals the host if the temperature exceeds a user-specified value.

3. Saves a S.M.A.R.T. data frame on the drive which exceeds the threatening temperature value.

A temperature sensor monitors the drive temperature and issues a warning over the interface when the temperature exceeds a set th reshold. The t emperature is measured a t power-up an d then at te n-minute interv als after power-up.

The thermal monitor system generates a warning code of 01-0B01 when the temperature exceeds the specified limit in compliance with the SCSI standard. The drive temperature is reported in the FRU code field of mode sense data. You can use this information to determine if the warning is due to the temperature exceeding the drive threatening temperature or the user-specified temperature.

This feature is controlled by the Enable Warning (EWasc) bit, and the repor ting mecha nism is controlle d by the Method of Reporting Informational Exceptions field (MRIE) on the Informational Exceptions Control (IEC) mode page (1Ch).

The current algorithm implem ents two temperature trip points. The first trip point is set at 68°C which is the maximum temperature limit according to the drive specification. The second trip point is user-selectable using the Log Select command. The reference temperature parameter in the temperature log page (see Table 1) can be used to set this trip point. The default value for this drive is 68°C, however, you can set it to any value in the range of 0 to 68°C. If you specify a temper ature greater than 68°C in this field, the temperature is rounded down to 68°C. A sense code is sent to the host to indicate the rounding of the parameter field.

Table 1: Temperature Log Page (0Dh)

Parameter Code Description

0000h 0001h

Primary Temperature Reference Temperature

16 Savvio 10K.5 SAS Product Manual, Rev. D

6.2.6 Drive Self Test (DST)

Drive Self Test (DST) is a technology designed to recognize drive fault conditions that qualify the drive as a failed unit. DST validates the functionality of the drive at a system level.

There are two test coverage options implemented in DST:

1. Extended test

2. Short test The most thorough option is the extended test that performs various tests on the drive and scans ev er y lo gic al

block address (LBA) of the drive. The short test is time-restricted and limited in length—it does not scan the entire media surface, but does some fundamental tests and scans portions of the media.

If DST encounters an error during either of these tests, it reports a fault condition. If the drive fails the test, remove it from service and return it to Seagate for service.

6.2.6.1 DST failure definition

The drive will present a “diagnostic failed” condition through the self-tests results value of the diagnostic log page if a functional failure is encountered during DST. The channel and servo parameters are not modified to test the drive more stringently, and the number of retries are not reduced. All retries and recovery processes are enabled during the test. If data is recoverable, no failure condition will be reported regardless of the number of retries required to recover the data.

The following conditions are considered DST failure conditions:

• Seek error after retries are exhausted

• Track-follow error after retries are exhausted

• Read error after retries are exhausted

• Write error after retries are exhausted Recovered errors will not be reported as diagnostic failures.

6.2.6.2 Implementation

This section provides all of the information necessary to implement the DST function on this drive.

6.2.6.2.1 State of the drive prior to testing

The drive must be in a ready state before issuing the Send Diagnostic command. There are multiple reasons why a drive may not be ready, some of which are valid conditions, and not errors. For example, a drive may be in process of doing a format, or another DST. It is the responsibility of the host application to determine the “not ready” cause.

While not technically part of DST, a Not Ready condition also qualifies the drive to be returned to Seagate as a failed drive.

A Drive Not Ready condition is reported by the drive under the following conditions:

• Motor will not spin

• Motor will not lock to speed

• Servo will not lock on track

• Drive cannot read configuration tables from the disc In these conditions, the drive responds to a Test Unit Ready command with an 02/04/00 or 02/04/03 code.

6.2.6.2.2 Invoking DST

To invoke DST, submit the Send Diagnostic command with the appropriate Function Code (001b for the short test or 010b for the extended test) in bytes 1, bits 5, 6, and 7.

Savvio 10K.5 SAS Product Manual, Rev. D 17

6.2.6.2.3 Short and extended tests

DST has two testing options:

1. short

2. extended

These testing options are described in the following two subsections. Each test consists of three segments: an electrical test segment, a servo test segment, and a read/ve rify s can

segment.

Short test (Function Code: 001b)

The purpose of the short test is to provide a time-limited test that tests as much of the drive as possible within 120 seconds. The short test does not scan the entire media surface, but does some fundamental tests and scans portions of the media. A complete read/verify scan is not performed and only factual failures will report a fault condition. This option provides a quick confidence test of the drive.

Extended test (Function Code: 010b)

The objective of the extended test option is to empirically test critical drive componen ts. For example, the seek tests and on-track operations test the positioning mechanism. The read operation tests the read head element and the media surface. The write element is tested through read/write/read operations. The integrity of the media is checked through a read/verify scan of the media. Motor functionality is tested by default as a part of these tests.

The anticipated length of the Extended test is reported through the Control Mode page.

6.2.6.2.4 Log page entries

When the drive begins DST, it creates a new entry in the Self-test Results Log page. The new entry is created by inserting a new self-test parameter block at the b eginning of the self- test result s log parame ter section of the log page. Existing data will be moved to make room for the new parameter block. The drive reports 20 parameter blocks in the log page. If there are more than 20 parameter blocks, the least recent parameter block will be deleted. The new parameter block will be initialized as follows:

1. The Function Code field is set to the same value as sent in the DST command

2. The Self-Test Results Value field is set to Fh

3. The drive will store the log page to non-volatile memory

After a self-test is complete or has been aborted, the drive updates the Self-Test Results Value field in its SelfTest Results Log page in non-volatile memory. The host may use Log Sense to read the results from up to the last 20 self-tests performed by the drive. Th e se lf- te st r esults value is a 4-bit field that reports the results of the test. If the field is set to zero, the drive passed with no errors detected by the DST. If the field is not set to zero, the test failed for the reason reported in the field.

The drive will report the failure condition and LBA (if applicable) in the Self-test Results Log parameter. The Sense key, ASC, ASCQ, and FRU are used to report the failure condition.

6.2.6.2.5 Abort

There are several ways to abort a diagnostic. You can use a SCSI Bus Reset or a Bus Device Reset message to abort the diagnostic.

You can abort a DST executing in background mode by using the abort code in the DST Function Code field. This will cause a 01 (self-test aborted by the application client) code to appear in the self-test results values log. All other abort mechanisms will be reported as a 02 (self-test routine was interrupted by a reset condition).

18 Savvio 10K.5 SAS Product Manual, Rev. D

6.2.7 Product warranty

See Section 1.0 for warranty contact information.

Shipping

When transporting or shipping a drive, use only a Seagate-approved container. Keep your original box. Seagate approved containers are easily identified by the Seagate Approved Package label. Shipping a drive in a non-approved container voids the drive warranty.

Seagate repair centers may refuse receipt of components improperly packaged or obviously damaged in transit. Contact your authorized Seagate distributor to purchase additional boxes. Seagate recommends shipping by an air-ride carrier experienced in handling computer equipment.

Storage

The maximum recommended storage period for the drive in a non-operational environment is 90 days. Drives should be stored in the original unopened Seagat e shipping packaging when ever possible. Once the drive is removed from the Seagate original packaging the recommended maximum period between drive operation cycles is 30 days. During any storage period the drive non-operational temperature, humidity, wet bulb, atmospheric conditions, shock, vibration, magnetic and electrical field specifications should be followed.

Product repair and return information

Seagate customer service centers are the only facilities authorized to service Seagate drives. Seagate does not sanction any third-party repair facilities. Any unauthorized repair or tampering with the factory seal voids the warranty.

Savvio 10K.5 SAS Product Manual, Rev. D 19

7.0 Physical/electrical specifications

This section provides information relating to the physical and electrical characteristics of the drive.

7.1 PowerChoiceTM power management

Drives using the load/unload architecture provide programmable power management to tailor systems for performance and greater energy efficiency.

The table below lists the supporte d PowerChoice mod es. The further you go down in the t abl e, the more power savings you get. For example, Idle_B mode results in greater power savings than Idle_A mode. Standby modes results in the greatest power savings.

PowerChoice modes

Mode Description

Idle_A Reduced electronics

Idle_B Heads unloaded. Disks spinning at full RPM

Idle_C Heads unloaded. Disks spinning at reduced RPM

Standby_Y Heads unloaded. Disks spinning at reduced RPM

Standby_Z Heads unloaded. Motor stopped (disks not spinning)

PowerChoice

can be invoked using one of these two methods:

• Power Condition mode page method—Enable and in itialize th e idle co ndition tim ers an d/o r the standby con dition timers. The timer values are based on the values set in the Power Condition mode page.

• START STOP UNIT command method—Use the START STOP UNIT command (OPERATION CODE 1Bh). This

allows the host to directly transition the drive to any supported PowerChoice mode.

If both the Power Condition mode page and START ST

OP UNIT command methods are used, the START STOP UNIT command request takes precedence over the Power Conditio n mode p age power control and may disable the idle condition and standby condition timers. The REQUEST SENSE command reports the current PowerChoice state if active and also the method by which the drive entered the PowerChoice state.

When the drive receives a command, all power condition timers are suspended if they were enabled via the Power Condition mode page. Once all outstanding commands are processed, the power condition timers are reinitialized to the values defined in the Power Condition mode page.

20 Savvio 10K.5 SAS Product Manual, Rev. D

7.1.1 PowerChoice reporting methods

PowerChoiceTM provides these reporting methods for tracking purposes:

Request Sense command reports

• Current power condition

• Method of entry Note. Processing the Request Sense command does not impact the drive’s power save state.

Mode Sense command reports (mode page 0x1A)

• Idle conditions enabled / disabled

• Idle condition timer values (100ms increments) (def ault, sa ve d, cu rr en t, ch an g eable )

Power Condition Vital Product Data (VPD) Page (VPD page 0x8A)

• Supported power conditions

• Typical recovery time from power conditions (1ms increments)

Start/Stop Cycle Counter Log Page reports (log page 0x0E)

• Specified and accumulated Start/Stops and Load/Unload cycles

Power Condition Tran sitions Log Page reports (log page 0x1A, subpage 0x00)

• Accumulated transitions to Active, Idle_A, Idle_B, Idle_C, Standby_Y, Standby_Z

7.2 AC power requirements

None.

7.3 DC power requirements

The voltage and current requirements for a single drive are shown below. Values indicated apply at the drive connector.

The standard drive models and the SED drive models have identical hardware, however the security and encryption portion of the drive controller ASIC is enabled and functional in the SED models. This represents a small additional drain on the 5V supply of about 30mA and a commensurate increase of about 150mW in power consumption. There is no additional drain on the 12V supply.

Savvio 10K.5 SAS Product Manual, Rev. D 21

Table 2: 900GB standard drive DC power requirements

3.0Gb mode 6.0Gb mode

Notes

Voltage +5V +12V [2] +5V +12V [2] Regulation [6] ±5% ±5% [2] ±5% ±5% [2] Avg idle current DC [1] [8] 0.35 0.22 0.35 0.22 Advanced Idle Current

Idle_A 3σ 0.40 0.24 0.40 0.24 Idle_B 3σ 0.27 0.20 0.27 0.21 Idle_C 3σ 0.27 0.11 0.27 0.11 Standby 3σ 0.26 0.06 0.27 0.06

Transition Current

Idle_A 3σ 1.34 1.62 1.34 1.63 Idle_B 3σ 0.94 1.66 0.85 1.65 Idle_C 3σ 0.91 1.56 0.90 1.56 Standby 3σ 0.93 1.61 0.89 1.64

Maximum starting current

(peak DC) DC 3σ [3] 0.62 1.00 0.63 1.00

(peak AC) AC 3σ [3] 1.06 1.67 0.98 1.67 Delayed motor start (max) DC 3σ [1] [5] 0.45 0.09 0.46 0.07 Peak operating current (random read): Typical DC [1] [7] 0.45 0.48 0.46 0.48

Maximum DC 3σ [1] 0.52 0.51 0.51 0.48

Maximum (peak) DC 3σ 1.33 1.54 1.3 3 1.53 Peak operating current (random write)

Typical DC

Maximum DC 3σ [1] 0.60 0.48 0.60 0.48

Maximum (peak) DC 3σ 1.19 1.60 1.1 3 1.54 Peak operating current (sequential read)

Typical DC

Maximum DC 3σ [1] 0.91 0.25 0.91 0.25

Maximum (peak) DC 3σ 1.18 0.49 1.2 5 0.46 Peak operating current (sequential write)

Typical DC

Maximum DC 3σ [1] 0.97 0.25 0.96 0.25

Maximum (peak) DC 3σ 1.25 0.40 1.1 7 0.42

[1]

(Amps) (Amps) (Amps) (Amps)

0.53 0.45 0.53 0.45

0.82 0.24 0.82 0.24

0.89 0.24 0.89 0.24

22 Savvio 10K.5 SAS Product Manual, Rev. D

Table 3: 600GB standard drive DC power requirements

3.0Gb mode 6.0Gb mode

Notes

Voltage +5V +12V [2] +5V +12V [2] Regulation [6] ±5% ±5% [2] ±5% ±5% [2] Avg idle current DC [1] [8] 0.34 0.17 0.35 0.17 Advanced Idle Current

Idle_A 3σ 0.39 0.18 0.40 0.18 Idle_B 3σ 0.27 0.16 0.27 0.16 Idle_C 3σ 0.27 0.09 0.27 0.09 Standby 3σ 0.27 0.06 0.26 0.06

Transition Current

Idle_A 3σ 1.00 1.58 1.05 1.59 Idle_B 3σ 0.87 1.54 0.86 1.59 Idle_C 3σ 0.87 1.57 0.85 1.63 Standby 3σ 1.01 1.57 0.95 1.58

Maximum starting current

(peak DC) DC 3σ [3] 0.64 0.86 0.64 0.86

(peak AC) AC 3σ [3] 0.97 1.56 0.89 1.55 Delayed motor start (max) DC 3σ [1] [5] 0.47 0.06 0.47 0.06 Peak operating current (random read): Typical DC [1] [7] 0.46 0.45 0.46 0.45

Maximum DC 3σ [1] 0.53 0.46 0.53 0.47

Maximum (peak) DC 3σ 1.24 1.70 1.2 9 1.50 Peak operating current (random write)

Typical DC

Maximum DC 3σ [1] 0.59 0.38 0.60 0.40

Maximum (peak) DC 3σ 1.16 1.54 1.1 8 1.47 Peak operating current (sequential read)

Typical DC

Maximum DC 3σ [1] 0.90 0.20 0.90 0.19

Maximum (peak) DC 3σ 1.14 0.36 1.1 9 0.36 Peak operating current (sequential write)

Typical DC

Maximum DC 3σ [1] 0.98 0.20 0.98 0.20

Maximum (peak) DC 3σ 1.25 0.34 1.1 9 0.34

[1]

(Amps) (Amps) (Amps) (Amps)

0.54 0.34 0.54 0.34

0.80 0.19 0.80 0.19

0.86 0.19 0.86 0.19

Savvio 10K.5 SAS Product Manual, Rev. D 23

Table 4: 450GB standard model DC power requirements

3.0Gb mode 6.0Gb mode

Notes

Voltage +5V +12V [2] +5V +12V [2] Regulation [6] ±5% ±5% [2] ±5% ±5% [2] Avg idle current DC [1] [8] 0.34 0.17 0.34 0.17 Advanced Idle Current

Idle_A 3σ 0.37 0.18 0.37 0.18 Idle_B 3σ 0.25 0.17 0.25 0.16 Idle_C 3σ 0.24 0.09 0.24 0.09 Standby 3σ 0.25 0.06 0.24 0.06

Transition Current

Idle_A 3σ 0.76 1.51 0.81 1.54 Idle_B 3σ 0.87 1.57 0.91 1.57 Idle_C 3σ 0.87 1.56 0.96 1.57 Standby 3σ 0.94 1.64 1.02 1.58

Maximum starting current

(peak DC) DC 3σ [4] 0.57 0.88 0.57 0.87

(peak AC) AC 3σ [4] 1.00 1.60 0.90 1.59 Delayed motor start (max) DC 3σ [1] [5] 0.43 0.08 0.43 0.08 Peak operating current (random read): Typical DC [1] [7] 0.48 0.46 0.48 0.46

Maximum DC 3σ [1] 0.50 0.50 0.52 0.49

Maximum (peak) DC 3σ 1.29 1.50 1.3 4 1.52 Peak operating current (random write)

Typical DC

Maximum DC 3σ [1] 0.59 0.42 0.60 0.41

Maximum (peak) DC 3σ 1.11 1.50 1.0 8 1.51 Peak operating current (sequential read)

Typical DC

Maximum DC 3σ [1] 0.90 0.20 0.91 0.20

Maximum (peak) DC 3σ 1.14 0.30 1.2 1 0.31 Peak operating current (sequential write)

Typical DC

Maximum DC 3σ [1] 0.95 0.21 0.95 0.20

Maximum (peak) DC 3σ 1.20 0.33 1.1 6 0.30

[1]

(Amps) (Amps) (Amps) (Amps)

0.55 0.35 0.56 0.35

0.83 0.20 0.84 0.20

0.90 0.20 0.90 0.20

24 Savvio 10K.5 SAS Product Manual, Rev. D

Table 5: 300GB standard model DC power requirements

3.0Gb mode 6.0Gb mode

Notes

Voltage +5V +12V [2] +5V +12V [2] Regulation [6] ±5% ±5% [2] ±5% ±5% [2] Avg idle current DC [1] [8] 0.34 0.15 0.35 0.15 Advanced Idle Current

Idle_A 3σ 0.37 0.16 0.38 0.16 Idle_B 3σ 0.25 0.14 0.26 0.14 Idle_C 3σ 0.25 0.08 0.26 0.08 Standby 3σ 0.25 0.06 0.26 0.06

Transition Current

Idle_A 3σ 0.99 1.52 1.02 1.55 Idle_B 3σ 0.84 1.52 0.92 1.51 Idle_C 3σ 0.85 1.46 0.84 1.53 Standby 3σ 1.06 1.54 0.92 1.50

Maximum starting current

(peak DC) DC 3σ [4] 0.59 0.85 0.58 0.85

(peak AC) AC 3σ [4] 0.96 1.52 0.93 1.48 Delayed motor start (max) DC 3σ [1] [5] 0.45 0.06 0.46 0.06 Peak operating current (random read): Typical DC [1] [7] 0.46 0.43 0.46 0.43

Maximum DC 3σ [1] 0.49 0.45 0.50 0.46

Maximum (peak) DC 3σ 1.25 1.47 1.2 7 1.51 Peak operating current (random write)

Typical DC 0.54 0.34 0.55 0.34

Maximum DC 3σ 0.56 0.39 0.57 0.39

Maximum (peak) DC 3σ 1.13 1.49 1.1 3 1.49 Peak operating current (sequential read)

Typical DC 0.80 0.17 0.80 0.16

Maximum DC 3σ 0.90 0.18 0.90 0.18

Maximum (peak) DC 3σ 1.13 0.34 1.2 0 0.33 Peak operating current (sequential write)

Typical DC 0.87 0.16 0.87 0.16

Maximum DC 3σ 0.98 0.18 0.99 0.18

Maximum (peak) DC 3σ 1.26 0.32 1.3 0 0.30

(Amps) (Amps) (Amps) (Amps)

[1] Measured with a verage reading DC ammeter. Instantaneous +12V current peaks will exceed these values. Power

supply at nominal voltage. N (number of drives tested) = 6, 35 Degrees C ambient.

[2] For +12 V, a –10% tolerance is allowed during initial spindle start but must return to ±5% before reaching 9,936 RPM.

The ±5% must be maintained after the drive signifies that its power-up sequence has been completed and that the

drive is able to accept selection by the host initiator. [3] See +12V current profile in Figure 1 (for 900GB models) and Figure 2 (for 600GB models). [4] See +12V current profile in Figure 3 (for 450GB models) and Figure 4 (for 300GB models).

Savvio 10K.5 SAS Product Manual, Rev. D 25

[5] This condition occurs after OOB and Speed Negotiation completes but before the drive has received the Notify Spinup

primitive.

[6] See paragraph 7.3.1, "Conducte d noise immunity." Specified voltage tolerance includes ripple, noise, and transient

response.

[7] Operating condition is defined as random 8 block reads. [8] During idle, the drive heads are relocated every 30 second s to a random location within the band from three-quarters

to maximum track.

General DC power requirement notes.

1. Minimum current loading for each supply voltage is not less th an 1.7% of the maximum ope rating current shown.

2. The +5V and +12V supplies should employ separate ground returns.

3. Where power is provided to multiple drives from a common supply, careful consideration for individual drive power requirements should be noted. Where multiple units are powered on simultaneously, the peak starting current must be available to each device.

4. Parameters, other than spindle start, are me asured after a 10-minute warm up.

5. No terminator power.

7.3.1 Conducted noise immunity

Noise is specified as a periodic and random distribution of freq uencies co vering a defi ned freq uency. Maximum allowed noise values given below are peak-to-peak measurements and apply at the drive power connector.

+5v = 250 mV pp from 100 Hz to 20 MHz. +12v = 450 mV pp from 100 Hz to 100 KHz.

250 mV pp from 100 KHz to 20 MHz. 150 mV pp from 20 MHz to 80 MHz.

7.3.2 Power sequencing

The drive does not require power sequencing. The drive protects against inadvertent writing during power-up and down.

26 Savvio 10K.5 SAS Product Manual, Rev. D

7.3.3 Current profiles

The +12V and +5V current profiles for the Savvio 10K.4 drives are shown below.

Figure 1. Current profiles for 900GB models

Savvio 10K.5 SAS Product Manual, Rev. D 27

Figure 2. Current profiles for 600GB models

28 Savvio 10K.5 SAS Product Manual, Rev. D

Figure 3. Current profiles for 450GB models

Savvio 10K.5 SAS Product Manual, Rev. D 29

Figure 4. Current profiles for 300GB models

Note: All times and currents are typical. See Tables 2 through 5 for maximum current requirements.

30 Savvio 10K.5 SAS Product Manual, Rev. D

7.4 Power dissipation

900 GB models in 3Gb operation

Typical power dissipation under idle conditions in 3Gb operatio n is 4.38 watts (14.95 BTUs per hour). To obtain operating power for typical random read operations, refer to the following I/O rate curve (see Figure

7). Locate the typical I/O rate for a drive in y our system on the horizontal axis and read the corresponding +5 volt current, +12 volt current, and total watts on the vertical axis. To calculate BTUs per hour, multiply watts by

3.4123.

Figure 5. 900GB (at 3Gb) DC current and power vs. input/output operations per second

Savvio 10K.5 SAS Product Manual, Rev. D 31

900GB models in 6Gb operation

Typical power dissipation under idle conditions in 6Gb operation is 4.42 watts (15.07 BTUs per hour). To obtain operating power for typical random read operations, refer to the following I/O rate curve (see Figure

7). Locate the typical I/O rate for a drive in y our system on the horizontal axis and read the corresponding +5

volt current, +12 volt current, and total watts on the vertical axis. To calculate BTUs per hour, multiply watts by

3.4123.

Figure 6. 900GB (at 6Gb) DC current and power vs. input/output operations per second

32 Savvio 10K.5 SAS Product Manual, Rev. D

600 GB models in 3Gb operation

Typica l power dissipation under idle conditions in 3Gb operation is 3.78 watts (12.89 BTUs per hour). To obtain operating power for typical random read operations, refer to the following I/O rate curve (see Figure

3.4123.

Figure 7. 600GB (at 3Gb) DC current and power vs. input/output operations per second

Savvio 10K.5 SAS Product Manual, Rev. D 33

600GB models in 6Gb operation

Typical power dissipation under idle conditions in 6Gb operation is 3.82 watts (13.05 BTUs per hour). To obtain operating power for typical random read operations, refer to the following I/O rate curve (see Figure

7). Locate the typical I/O rate for a drive in y our system on the horizontal axis and read the corresponding +5

volt current, +12 volt current, and total watts on the vertical axis. To calculate BTUs per hour, multiply watts by

3.4123.

Figure 8. 600GB (at 6Gb) DC current and power vs. input/output operations per second

34 Savvio 10K.5 SAS Product Manual, Rev. D

450GB models in 3Gb operation

Typical power dissipation under idle conditions in 3Gb operatio n is 3.73 watts (12.73 BTUs per hour). To obtain operating power for typical random read operations, refer to the following I/O rate curve (see Figure

3.4123.

Figure 9. 450GB (at 3Gb) DC current and power vs. input/output operations per second

Savvio 10K.5 SAS Product Manual, Rev. D 35

450GB models in 6Gb operation

Typical power dissipation under idle conditions in 6Gb operation is 3.75 watts (12.79 BTUs per hour). To obtain operating power for typical random read operations, refer to the following I/O rate curve (see Figure

7). Locate the typical I/O rate for a drive in y our system on the horizontal axis and read the corresponding +5

volt current, +12 volt current, and total watts on the vertical axis. To calculate BTUs per hour, multiply watts by

3.4123.

Figure 10. 450GB (at 6Gb) DC current and power vs. input/output operations per second

36 Savvio 10K.5 SAS Product Manual, Rev. D

300GB models in 3Gb operation

Typica l power dissipation under idle conditions in 3Gb operation is 3.46 watts (11.81 BTUs per hour). To obtain operating power for typical random read operations, refer to the following I/O rate curve (see Figure

3.4123.

Figure 11. 300GB (at 3Gb) DC current and power vs. input/output operations per second

Savvio 10K.5 SAS Product Manual, Rev. D 37

300GB models in 6Gb operation

Typical power dissipation under idle conditions in 6Gb operation is 3.48 watts (11.88 BTUs per hour). To obtain operating power for typical random read operations, refer to the following I/O rate curve (see Figure

7). Locate the typical I/O rate for a drive in y our system on the horizontal axis and read the corresponding +5

volt current, +12 volt current, and total watts on the vertical axis. To calculate BTUs per hour, multiply watts by

3.4123.

Figure 12. 300GB (at 6Gb) DC current and power vs. input/output operations per second

7.5 Environmental limits

Temperature and humidity values experienced by the drive must be such that condensation does not occur on any drive part. Altitude and atmospheric pressure specifications are referenced to a standard day at 58.7°F (14.8°C). Maximum wet bulb temperature is 82°F (28°C).

Note. To maintain optimal performance drives should be run at nominal case temperatures.

7.5.1 Temperature

a. Operating

The drive meets the operating specifications over a 41°F to 131°F (5°C to 55°C) drive case temperature range with a maximum temperature gradient of 36°F (20°C) per hour.

The maximum allowable drive case temperature is 60°C. The MTBF specification for the drive assumes the operating environment is designed to maintain nominal

case temperature. The rated MTBF is based upon a sustained case temperature of 122°F (50°C). Occa sional excursions in operat ing temperature bet ween the rated MTBF temperature and the maximum drive operating case temperature may occur without impact to the rated MTBF temperature. Howeve r continual or sustained operation at case temperatures beyond the rated MTBF temperature will degrade the drive MTBF and reduce product reliability.

Air flow may be required to achieve consistent nominal case temperature values (see Section 9.2). To confirm that the required cooling is provided for the electronics and HDA, place the drive in its final mechanical configuration, and perform random write/read operations. After the temperatures stabilize, measure the case temperature of the drive. See Figure

13 for HDA temperature checkpoint.

38 Savvio 10K.5 SAS Product Manual, Rev. D

b. Non-operating

–40° to 158°F (–40° to 70°C) package ambient with a maximum gradient of spe

cification assumes that the drive is packaged in th e shipping cont ainer de signed by Seagate for use with

drive.

HDA Temp. Check Point

Figure 13. Location of the HDA temperature check point

Note. Image is for reference only, may not represent actual drive.

7.5.2 Relative humidity

The values below assume that no condensation on the drive occurs. a. Operating

5% to 95% non-condensing relative humidity with a maximum gradient of 20% per hour.

b. Non-operating

5% to 95% non-condensing relative humidity.

36°F (20°C) per hour. This

7.5.3 Effective altitude (sea level)

a. Operating

–1,000 to +10,000 feet (–304.8 to +3,048 meters)

b. Non-operating

–1,000 to +40,000 feet (–304.8 to +12,192 meters)

7.5.4 Shock and vibration

Shock and vibration limits specified in this do

cument are measured directly on the drive chassis. If the drive is installed in an enclosure to which the stated shock and/or vibration criteria is applied, resona nces may occur internally to the enclosure resulting in drive movement in excess of the stated limits. If this situation is apparent, it may be necessary to modify the enclosure to minimize drive movement.

The limits of shock and vibration defined within this document are specified with the drive mounted by any of the four methods shown in Figure 14, and in accordance with the restrictions of Section 11.3.

Savvio 10K.5 SAS Product Manual, Rev. D 39

7.5.4.1 Shock

a. Operating—normal

The drive, as installed for normal operation, shall oper a

te error free while subjected to intermittent shock not

exceeding:

• 40 Gs at a maximum duration of 11ms (half sinewave) 25 Gs at a maximum duration of 2ms (half sinewave)

•

Shock may be applied in the X, Y, or Z axis. Shock is not to be repeated more than once every 2 seconds. b. Non-operating

The limits of non-operating shock shall apply to all conditions of h

andling and transportation. This includes

both isolated drives and integrated drives. The drive subjected to nonrepetitive shock not exceeding

the three values below, shall not exhibit device

damage or performance degradation.

• 80 Gs at a maximum duration of 11ms (half sinewave) 400 Gs at a maximum duration of 2ms (half sinewave)

•

• 300 Gs at a maximum duration of 0.5ms (half sinewave)

Shock may be applied in the X, Y, or Z axis.

c. Packaged

Seagate finished drive bulk packs are designed and tested

to meet or exceed applicable ISTA and ASTM standards. Volume finished drives will be shipped from Seagate factories on pallets to minimize freight costs and ease material handling. Seagate finished drive bulk packs may be shipped individually. For less than full shipments, instructions are printed on the bulk pack carton for minimum drive quantities and proper drive placement.

Figure 14. Recommended mounting

Note. Image is for reference only, may not represent actual drive.

40 Savvio 10K.5 SAS Product Manual, Rev. D

7.5.4.2 Vibration

a. Operating—normal

The drive as installed for normal operation, shall comply with the complete specified performance while subjected to continuous vibration not exceeding

5-500 Hz @ 0.5 G (zero to peak) Vibration may be applied in the X, Y, or Z axis. Operating normal translational random flat profile 10 - 500 Hz (translational random flat profile) 0.5 GRMS

b. Operating—abnormal

Equipment as installed for normal operation shall not incur physical damage while subjected to periodic vibration not exceeding:

15 minutes of duration at major resonant frequency 5-500 Hz @ 0.75 G (X, Y, or Z axis)

Vibration occurring at these levels may degrade operational performance during the abnormal vibration period. Specified operational performance will continue when normal operating vibration levels are resumed. This assumes system recovery routines are available.

Operating abnormal translational random flat profile 10 - 500 Hz (translational random flat profile) 1.2 GRMS

c. Non-operating

The limits of non-operating vibration shall apply to all conditions of handling and transportation. This includes both isolated drives and integrated drives.

The drive shall not incur physical damage or degraded performance as a result of continuous vibration not exceeding

Vibration may be applied in the X, Y, or Z axis. Non-operating translational random flat profile 10 - 500 Hz (translational random flat profile) 2.4 GRMS

5-500 Hz @ 3.0 G (zero to peak)

7.5.5 Air cleanlines s

The drive is designed to operate in a typical office environment with minimal environmental control.

7.5.6 Corrosi v e en v iro nment

Seagate electronic drive components pass accelerated corrosion testing equivalent to 10 years exposure to light industrial environments containing sulfurous gases, chlorine and nitric oxide, classes G and H per ASTM B845. However, this accelerated testing cannot duplicate every potential application environment.

Users should use caution exposin g any electronic c omponents to uncontrolled chemical pollutants and corrosive chemicals as electronic drive component reliability can be affected by the installation environment. The silver, copper, nickel and gold films used in Seagate products are especially sensitive to the presence of sulfide, chloride, and nitrate contaminants. Sulfur is found to be the most da maging. In addi tion, electronic comp onent s should never be exposed to condensing water on the surface of the printed circuit board assembly (PCBA) or exposed to an ambient relative humidity greater than 95%. Materials used in cabinet fabrication, such as vulcanized rubber, that can outgas corrosive compounds should be minimized or eliminated. The useful life of any electronic equipment may be extended by replacing materials near circuitry with sulfide-free alternatives.

Savvio 10K.5 SAS Product Manual, Rev. D 41

7.5.7 Acoustics

Sound power during idle mode shall be 3.0 bels typical when measured to ISO 7779 specification. There will not be any discrete tones more than 10 dB above the masking noise on typical drives when mea-

sured according to Seagate specification 30553-001. There will not be any tones more than 24 dB above the masking noise on any drive.

7.5.8 Electromagnetic susceptibility

See Section 3.1.1.1.

42 Savvio 10K.5 SAS Product Manual, Rev. D

7.6 Mechanical specifications

Refer to Figure 15 for detailed mounting configuration dimensions. See Section 11.3, “Drive mounting.”

Weight: 300GB models .465 pounds .211 kilograms 450GB models .477 pounds .216 kilograms 600GB models .475 pounds .215 kilograms 900GB models .451 pounds .205 kilograms

Note. These dimensions conform to the Small Form Factor Standard documented in SFF-8201 and

SFF-8223, found at www.sffcommittee.org.

in mm

Figure 15. Mounting configuration dimensions

Savvio 10K.5 SAS Product Manual, Rev. D 43

8.0 About FIPS

The Federal Information Processing Standard (FIPS) Publication 140-2, FIPS PUB 140-2, is a U.S. government computer security standard used to accredit cryptogr aphic modules. It is titled “Security Require ment s for Cryptographic Modules”. The initial publicat ion was o n M ay 25, 2 001 a nd was la st upd ated Decemb er 3, 2002.

Purpose

The National Institute of Standards and Technology (NIST) issued the FIPS 140 P ublication Series to coordinate the requirements and standards for cryptography modules that include both hardware and software components.

Federal Information Processing Standard (FIPS) 140-2 Level 2 Certification requires drives to go through government agencies certifications to add requirements for physical tamper-evidence and role-based authentication.

Level 2 security

Level 2 improves upon the physical security mechanisms of a Level 1 (lowest level of security) cryptographic module by requiring features that show evidence of tampering, including tamper-evident coatings or seals that must be broken to attain physical access to th e plaintext cryptographic keys and critic al security parameters (CSPs) within the module, or pick-resistant locks on covers or doors to protect against unauthorized physical access.

Figure 16. Example of FIPS tamper evidence labels.

Note. Does not represent actual drive.

44 Savvio 10K.5 SAS Product Manual, Rev. D

9.0 About self-encrypting drives

Self-encrypting drives (SEDs) offer encryption and security services for the protection of stored data, commonly known as “protection of data at rest.” These drives are compliant with the Trusted Computing Group (TCG) Enterprise Storage Specifications as detailed in Section 3.2.

The Trusted Computing Group (TCG) is an organization sponsored and operated by companies in the computer, storage and digital communications industry. Seagate’s SED models comply with the standards published by the TCG.

To use the security features in the drive, the host must be capable of constructing and issuing the following two SCSI commands:

• Security Protocol Out

• Security Protocol In These commands are used to convey the TCG protocol to and from the drive in their command payloads.

9.1 Data encryption

Encrypting drives use one inline encryption engine fo r each port, employing AES- 256 dat a encr yption in Cipher Block Chaining (CBC) mode to encrypt all data prior to being written on the media and to decrypt all data as it is read from the media. The encryption engines are always in operation, ca nnot be disab led, and do not detract in any way from the performance of the drive.

The 32-byte Data Encryption Key (DEK) is a random number which is genera ted by th e drive, n ever leaves the drive, and is inaccessible to the host system. The DEK is itself encrypted when it is stored on the media and when it is in volatile temporary storage (DRAM) external to the encryption engine. A unique data encryption key is used for each of the drive's possible16 data bands (see Section 9.5).

9.2 Controlled access

The drive has two security partitions (SPs) called the "Admin SP" and the "Locking SP." These act as gatekeepers to the drive security services. Security-related commands will not be accepted unless they also supply the correct credentials to prove the requester is authorized to perform the command.

9.2.1 Admin SP

The Admin SP allows the drive's owner to enable or disable firmware download operations (see Section 9.4). Access to the Admin SP is available using the SID (Secure ID) password or the MSID (Makers Secure ID) password.

Savvio 10K.5 SAS Product Manual, Rev. D 45

9.2.2 Locking SP

The Locking SP controls read/write access to the media and the cryptographic erase feature. Access to the Locking SP is available using the BandMasterX or EraseMaster passwords. Since the drive owner can define up to 16 data bands on the drive, each data band has its own password called BandMasterX where X is the number of the data band (0 through 15).

9.2.3 Default password

When the drive is shipped from the factory, all passwords are set to the value of MSID. This 32-byte random value is printed on the drive label and it can be read by the host electronically over the I/O. After receipt of the drive, it is the responsibility of the owner to use the default MSID password as the authority to change all other passwords to unique owner-specified values.

9.3 Random number generator (RNG)

The drive has a 32-byte hardware RNG that it is uses to derive encryption keys or, if requested to do so, to provide random numbers to the host for system use, including using these nu mbers as Authentication Keys ( p asswords) for the drive’s Admin and Locking SPs.

9.4 Drive locking

In addition to changing the passwords, as described in Section 9.2.3, the owner should also set the data access controls for the individual bands.

The variable "LockOnReset" should be set to "PowerCycle" to ensure that the data bands will be locked if power is lost. This scenario occurs if the drive is removed from its cabinet. The drive will not honor any data read or write requests until the bands have been unlocked. This prevents the user data from being accessed without the appropriate credentials when the drive has been removed from its cabinet and installed in another system.

When the drive is shipped from the factory, the firmware download port is unlocked.

9.5 Data bands

When shipped from the factory, the drive is configured with a single data band called Band 0 ( also known as the Global Data Band) which comprises LBA 0 through LBA max. The host may alloca te Band1 by specifying a start LBA and an LBA range. The r eal est a te for this band is t aken from the Global Band. An ad ditional 14 Data Bands may be defined in a similar way (Band2 through Band15) but before these bands can be allocated LBA space, they must first be individually enabled using the EraseMaster password.

Data bands cannot overlap but they can be sequential with one ba nd e ndi ng at LBA (x) and the ne xt b eginnin g at LBA (x+1).

Each data band has its own drive-generated en cryption key and its own user -supplied p assword. The host may change the Encryption Key (see Section 9.6) or the password when required. The bands should be aligned to 4K LBA boundaries.

9.6 Cryptographic erase

A significant feature of SEDs is the ability to perform a cryptographic erase. This involves the host telling the drive to change the data encryption key for a p ar ticu lar ban d. On ce chang ed , the data is no longer recoverable since it was written with one key and will be read using a different key. Since the drive overwrites the old key with the new one, and keeps no history of key changes, the user data can never be recovered. This is tantamount to an instantaneous data erase and is very useful if the drive is to be scrapped or redispositioned.

46 Savvio 10K.5 SAS Product Manual, Rev. D

9.7 Authenticated firmware download

In addition to providing a locking mechanism to prevent unwanted firmware download attempts, the drive also only accepts download files which have been cryptographically signed by the appropriate Seagate Design Center.

Three conditions must be met before the drive will allow the download operation:

1. The download must be an SED file. A standard (base) drive (non-SED) file will be rejected.

2. The download file must be signed and authenticated.

3. As with a non-SED drive, the download file must pass the acceptance criteria for the drive. For example it must be applicable to the correct drive model, and have compatible revision and customer status.

9.8 Power requirements

9.9 Supported commands

The SED models support the following two commands in addition to the commands supported by the standard (non-SED) models as listed in Table 9:

• Security Protocol Out (B5h)

• Security Protocol In (A2h)

9.10 RevertSP

The SED models will support RevertSP feature where it erases all data in all bands on the device and returns the contents of all SPs (Security Providers) on the device to their Original Factory State.

Savvio 10K.5 SAS Product Manual, Rev. D 47

10.0 Defect and error management

Seagate continues to use innovative technologies to manage defects and errors. These technologies are designed to increase data integrity, perform drive self-maintenance, and validate proper drive operation.

SCSI defect and error management involves drive internal defect/error management and SAS sys tem error considerations (errors in communications between the initiator and the drive). In addition, Seagate provides the following technologies used to increase data integrity and drive reliability:

• Background Media Scan (see Section 10.4)

• Media Pre-Scan (see Section 10.5)

• Deferred Auto-Reallocation (see Section 10.6)

• Idle Read After Write (see Section 10.7) The read error rates and specified storage capacities are not dependent on host (initiator) defect management

routines.

10.1 Drive internal defects/errors

During the initial drive format operation at the factory, media defects are identified, tagged as being unusable, and their locations recorded on the drive primary defects list (referred to as the “P’ list and also as the ETF defect list). At factory format time, these known defects are also reallocated, that is, reassigned to a new place on the medium and the location liste d in the defects reallocation table. The “P” list is no t altered after factory formatting. Locations of defects found and reallocated during error recovery procedures after drive shipment are listed in the “G” list (defects growth list). The “P” and “G” lists may be referenced by the initiator using the Read Defect Data command.

Details of the SCSI commands supported by the drive are described in the SAS Interface Manual. Also, more information on the drive Error Recovery philosophy is presented in the SAS Interface Manual.

10.2 Drive error recovery procedures

When an error occurs during drive operation, the drive, if pr ogrammed to do so, performs e rror recover y procedures to attempt to recover the dat a . The error reco very procedur es used depend o n the options previously set in the Error Recovery Parameters mode page. Error recovery and defect management may involve using several SCSI commands described in the SCSI Interface Manual. The drive implements selectable error recovery time limits required in video applications.

The error recovery scheme supported by the drive provides a way to control the to tal error r ecovery time for the entire command in addition to controlling the recovery level for a single LBA. The total amount of time spent in error recovery for a command can be limited using the Recovery Time Limit bytes in the Error Recovery mode page. The total amount of time spent in error recovery for a single LBA can be limited using the Read Retry Count or Write Retry Count bytes in the Error Recovery mode page.

The drive firmware error recovery algorithms consist of 20 levels for read recoveries and six levels for write. Each level may consist of multiple steps, where a step is defined as a recovery function involving a single reread or re-write attempt. The maximum level used by the drive in LBA recovery is determined by the read and write retry counts.

48 Savvio 10K.5 SAS Product Manual, Rev. D

Table 6 equates the read and write retry count with the maximum possible recovery time for read and write recovery of individual LBAs. The times given do not include time taken to perform reallocations. Reallocations are performed when the ARRE bit (for reads) or AWRE bit (for writes) is one, the RC bit is zero, and the recovery time limit for the command has not yet been met. Time needed to perform reallocation is not counted against the recovery time limit.

When the RC bit is one, reallocations are disabled even if the ARRE or AWRE bits are one. The drive will still perform data recovery actions within the limits defined by the Read Retry Count, Write Retry Count, and Recovery Time Limit parameters. However, the drive does not report any unrecovered errors.

Table 6: Read and write retry count maximum recovery times

Maximum recovery time per

Read retry count*

1 124.32 1 53.91 5 621.62 2 79.89 10 1243.23 3 97.86 15 1864.85 4 175.85 20 (default) 2486.47 5 (default) 421.79

LBA (cumulative, msec) Write retry count

0 35.94

Maximum recovery time per LBA (cumulative, msec)

* For read retry count, every tick ~ 5% of total error recovery. Valid range setting is 1-20. e.g. 1 ~ 5% 5 ~ 25% 20 ~ 100% Setting these retry counts to a value below the default setting could result in degradation of the unrecovered

error rate. For example, suppose the read/write recovery page has the RC bit = 0 and if the read retry count is set to 5, this means ~ 25% of error recovery will be executed which consumes 621.62 ms (please refer to the table above). If the limit is reached and a LBA has not yet been recovered (i.e. requires retries beyond 621.62 ms), the command will end with Check Condition status report and unrecoverable read error will be reported.

10.3 SAS system errors

Information on the reporting of operational errors or faults across the interface is given in the SAS Interface Manual. The SSP Response returns information to the host about numerous kinds of errors or faults. The

Receive Diagnostic Results reports the results of diagnostic operations performed by the drive. Status returned by the drive to the initiator is described in the SAS Interface Manual. Status reporting plays a

role in systems error management and its use in that respect is described in sections where the various commands are discussed.

10.4 Background Media Scan

Background Media Scan (BMS) is a self-initiated media scan. BMS is defined in the T10 document SPC-4 available from the T10 committee. BMS performs sequential reads across the entire pack of the media while the drive is idle. In RAID arrays, BMS allows hot spare drives to be scann ed for defects prior to being pu t into service by the host system. On regular duty drives, if the host system makes use of the BMS Log Page, it can avoid placing data in suspect locations on the media. Unreadable and recovered error sites will be logged or reallocated per ARRE/AWRE settings.

Savvio 10K.5 SAS Product Manual, Rev. D 49

With BMS, the host system can consume less power and system overhead by only checking BMS status and results rather than tying up the bus and consuming power in the process of host-i nitiated media scan ning activity.

Since the background scan functions are only done dur ing idle periods, BMS ca uses a negligible imp act to system performance. The first BMS scan for a newly manufactured drive is performed as quickly as possible to verify the media and protect data by setting the “Start time after idle” to 5ms, all subsequent scans begin after 500ms of idle time. Other features that normally use idle time to function will function normally because BMS functions for bursts of 500ms and then suspends activity for 100ms to allow other background functions to operate.

BMS interrupts immediately to service host commands from the interface bus while performing reads. BMS will complete any BMS-initiated error recovery prior to returning to service host-initiated commands. Overhead associated with a return to host-s ervicing activity from BMS only impacts the first command that interrupted BMS, this results in a typical delay of about 1ms.

10.5 Media Pre-Scan

Media Pre-Scan is a feature that allows the drive to repair media errors that would otherwise have been found by the host system during critical data accesses early in the drive’s life. The default setting for Media Pre-Scan is enabled on standard products. Media Pre-Scan checks each write command to determine if the destination LBAs have been scanned by BMS. If the LBAs have been verified, the drive proceeds with the normal write command. If the LBAs have not been verified by BMS, Pre-Scan will convert the write to a write verify to certify that the data was properly written to the disc.

Note. During Pre-Scan write verify commands, write performance may decrease by 50% until Pre-Scan

completes. Write performance testing should be performed after Pre-Sca n is complete. This may be checked by reading the BMS status.

To expedite the scan of the full pack and subsequently exit from the Pre-Scan period, BMS will begin scanning immediately when the drive goes to idle during the Pre-Scan period. In the event that the drive is in a high transaction traffic environment and is unable to complete a BMS scan within 24 power on hours BMS will disable Pre-Scan to restore full performance to the system.

10.6 Deferred Auto-Reallocation

Deferred Auto-Reallocation (DAR) simplifies reallocation algorithms at the system level by allowing the drive to reallocate unreadable locations on a subsequent write command. Sites are marked for DAR during read operations performed by the drive. When a write command is received for an LBA marked for DAR, the auto-reallocation process is invoked and attempts to rewrite the data to the original location. If a verification of this rewrite fails, the sector is re-mapped to a spare location.

This is in contrast to the system having to use the Reassign Command to reassign a location that was unreadable and then generate a write command to rewrite the data. DAR is most effective when AWRE and ARRE are enabled—this is the default setting from the Seagate factory. With AWRE and ARRE disabled DAR is unable to reallocate the failing location and will report an error sense code indicating that a write command is being attempted to a previously failing location.

10.7 Idle Read After Write

Idle Read After Write (IRAW) utilizes idle time to verify the integrity of recently written data. During idle periods, no active system requests, the drive reads recently written data from the media and compares it to valid write command data resident in the drives data buffer. Any sectors that fail the comp ariso n result in the invocation of a rewrite and auto-reallocation process. The process attempts to rewrite the data to the original location. If a verification of this rewrite fails, the sector is re-mapped to a spare location.

50 Savvio 10K.5 SAS Product Manual, Rev. D

10.8 Protection Information (PI)

Protection Information is intended as a standardized approach to system level LRC traditionally provided by systems using 520 byte formatted LBAs. Drives formatted with PI information provide the same, common LBA count (i.e. same capacity point) as non-PI formatted drives. Sequential performance of a PI drive will be reduced by approximately 1.56% due to the extra overhead of PI being transferred from the media that is not calculated as part of the data transferred to the host. To determine the full transfer rate of a PI dr ive, transfer s should be calculated by adding the 8 extra bytes of PI to the transferred LBA length, i.e. 512 + 8 = 520. PI formatted drives are physically formatted to 520 byte sectors that store 512 bytes of customer data with 8 bytes of Protection Information appended to it. The advantage of PI is that the Protection Information bits can be managed at the HBA and HBA driver level. Allowing a system that typically does not support 520 LBA formats to integrate this level of protection.

Protection Information is valid with any supported LBA size. 512 LBA size is used here as common example.

10.8.1 Levels of PI

There are 4 types of Protection Information. Type 0 - Describes a drive that is not formatted with PI information bytes. This allows for legacy support in non-

PI systems. Type 1 - Provides support of PI protection using 10 and 16 byte commands. The RDPROTECT a nd WR TPRO-

TECT bits allow for checking control through the CDB. Eight bytes of Protection Information are transmitted at LBA boundaries across the interface if RDPROTECT and WRTPROTECT bits are nonzero values. Type 1 does not allow the use of 32 byte commands.

Type 2 - Provides checking control and additional expected fields within the 32 byte CDBs. Eight bytes of Protection Information are transmitted at LBA boundaries across the interface if RDPROTECT and W RTPROTECT bits are nonzero values. Type 2 does allow the use of 10 and 16 byte commands with zero values in the RDPROTECT and WRTPROTECT fields. The drive will generate 8 bytes (e.g.0xFFFF) 8 bytes of Protection Information to be stored on the media, but the 8 bytes will not be transferred to the host during a read command.

Type 3 - Seagate products do not support Type 3.

10.8.2 Setting and determining the current Type Level

A drive is initialized to a type of PI by using the format command on a PI capable dri ve . Once a drive is formatted to a PI Type, it may be queried by a Read Capacity (16) command to report the PI type which it is currently formatted to. PI T ypes cannot coexist on a sing le drive. A drive can only be formatted to a single PI Type. It can be changed at anytime to a new Type but requires a low level format which destroys all existing data on the drive. No other vehicle for changing the PI type is provided by the T10 SBC3 specification.

Type 1 PI format CDB command: 04 90 00 00 00 00, Write Buffer: 00 A0 00 00 Type 2 PI format CDB command: 04 D0 00 00 00 00, Write Buffer: 00 A0 00 00

10.8.3 Identifying a Protection Information drive

The St andard Inquiry provides a b it to ind icate if PI is suppor t by th e drive. V ital Product Descriptor (VPD) page 0x86 provides bits to indicate the PI Types supported and which PI fields the drive supports checking.

Note. For further details with respect to PI, please refer to SCSI Block Command s - 3 (SBC-3) Dr af t Stan-

dard documentation.

Savvio 10K.5 SAS Product Manual, Rev. D 51

11.0 Installation

Savvio disc drive installation is a plug-and-play process. There are no jumpers, switches, or terminators on the drive.

SAS drives are designed to be used in a host system that provides a SAS-compatible backplane with bays designed to accommodate the drive. In such systems, the host system typically provides a carrier or tray into which you need to mount the drive. Mount the drive to th e carrier o r tray provided by the host system using four M3 x 0.5 metric screws. When tightening the screws, use a maximum torque of 4.5 in-lb +/- 0.45 in-lb. Do not over-tighten or force the screws. You can mount the drive in any orientation.

Note. SAS drives are designed to be attached to the host system without I/O or power cables. If you

intend to use the drive in a non-backplane host system, connecting the drive using high-quality cables is acceptable as long as the I/O cable length does not exceed 10 meters (32.8 feet).

Slide the carrier or tray into the appropriate bay in your host system using the instructions provided by the host system. This connects the drive directly to your system’s SAS connector. The SAS connector is normally located on a SAS backpanel. See Section 12.4.1 for additional information about these connectors.

Power is supplied through the SAS connector. The drive is shipped from the factory low-level formatted in 512-byte logical blocks. You need to reformat the

drive only if you want to select a different logical block size.

Figure 17. Physical interface

Note. Image is for reference only, may not represent actual drive.

52 Savvio 10K.5 SAS Product Manual, Rev. D

11.1 Drive orientation

The drive may be mounted in any orientation. All drive performance characterizations, however, have been done with the drive in horizontal (discs level) and vertical (drive on its side) orientations, which are the two preferred mounting orientations.

11.2 Cooling

Cabinet cooling must be designed by the customer so that the ambient temperature immediately surrounding the drive will not exceed temperature conditions specified in Section 7.5.1, "Temperature."

The rack, cabinet, or drawer environment for the drive must provide heat removal from the electronics and head and disc assembly (HDA). You should confirm that adequate heat removal is provided using the temperature measurement guidelines described in Section 7.5.1.

Forced air flow may be r equired to keep temper atures a t or be low the t emperat ures s pecified in Section 7.5.1 in which case the drive should be oriented, or air flow directed, so th at the least amount of air flow resistance is created while providing air flow to the electronics an d HDA. Also, the shortest possible path between the air inlet and exit should be chosen to minimize the travel length of air heated by the drive and other heat sources within the rack, cabinet, or drawer environment.

If forced air is determined to be necessary, possible air-flow patterns are shown in Figure 18. The air-flow patterns are created by one or more fans, either forcing or drawing air as shown in the illustrations. Conduction, convection, or other forced air-flow patterns are acceptable as long as the temperature measurement guidelines of Section 7.5.1 are met.

Above unit

Note. Air flows in the direction shown (back to front) or in reverse direction (front to back)

Note. Air flows in the direction shown or in reverse direction (side to side)

Figure 18. Air flow

Under unit

Above unit

Under unit

Note. Image of the HDA may not represent actual product, for reference only.

Savvio 10K.5 SAS Product Manual, Rev. D 53

11.3 Drive mounting

Mount the drive using the bottom or side mounting holes . If you mount the drive using the bottom holes, e nsure that you do not physically distort the drive by attempting to mount it on a stiff, non-flat surface.

The allowable mounting surface stiffness is 80 lb/in (14.0 N/mm) . The followin g equation and paragraph define the allowable mounting surface stiffness:

K x X = F < 15lb = 67N

where K is the mounting surface stiffness (units in lb/in or N/mm) and X is the out-of-plane surface distortion (units in inches or millimeters). The out-of-plane distortion (X) is determined by defining a plane with three of the four mounting points fixed and evaluating the out-of-plane deflection of the fourth mounting point when a known force (F) is applied to the fourth point.

11.4 Grounding

Signal ground (PCBA) and HDA ground are connected together in the drive and cannot be separated by the user. The equipment in which the drive is mounted is connected directly to the HDA and PCBA with no electrically isolating shock mounts. If it is desired for the system chassis to not be connected to the HDA/PCBA ground, the systems integrator or user must provide a nonconductive (electrically isolating) method of mounting the drive in the host equipment.

Increased radiated emissions may result if you do not provide the maximum surface area ground connection between system ground and drive ground. This is the system designer’s and integrator’s responsibility.

54 Savvio 10K.5 SAS Product Manual, Rev. D

12.0 Interface requirements

This section partially describes the interface requirements as implemented on Savvio drives. Additional information is provided in the SAS Interface Manual (part number 100293071).

12.1 SAS features

This section lists the SAS-specific features supported by Savvio drives.

12.1.1 task management functions

Table 7 lists the SAS task management functions supported.

Table 7: SAS task management functions supported

Task name Supported

Abort Task Yes Clear ACA Yes Clear task set Yes Abort task set Yes Logical Unit Reset Yes Query Task Yes

12.1.2 task management responses

Table 8 lists the SAS response codes returned for task management functions supported.

Table 8: Task management response codes

Function name Re s ponse code

Function complete 00 Invalid frame 02 Function not supported 04 Function failed 05 Function succeeded 08 Invalid logical unit 09

Savvio 10K.5 SAS Product Manual, Rev. D 55

12.2 Dual port support

Savvio SAS drives have two independent ports. These ports may be connected in the same or different SCSI domains. Each drive port has a unique SAS address.

The two ports have the capability of independent port clocking (e.g. both ports can run at 6Gb/s or the first port can run at 6Gb/s while the second port runs at 3Gb/s.) The supported link rates are 1.5, 3.0, or 6.0 Gb/s.

Subject to buffer availability, the Savvio drives support:

• Concurrent port transfers—The drive supports receiving COMMAND, TASK management transfers on both ports at the same time.

• Full duplex—The drive supports sending XFER_RDY, DATA and RESPONSE transfers while receiving frames on both ports.