Seagate Pulsar2 ST100FM0012 User Manual

Product Manual  
®
Pulsar .2 SAS  
Standard Models  
Self-Encrypting Drive Models  
ST800FM0002  
ST800FM0032  
ST400FM0002  
ST400FM0042  
ST200FM0002  
ST200FM0042  
ST100FM0002  
ST100FM0052  
ST800FM0012  
ST800FM0042  
SED FIPS140-2 Models  
ST800FM0022  
100666271  
Rev. C  
March 2013  
CONTENTS  
5.3.6  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
I
CONTENTS  
10.2  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
II  
CONTENTS  
11.7  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
III  
FIGURES  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
IV  
Seagate Technology Support Services  
For information regarding online support and services, visit http://www.seagate.com/about/contact-us/technical-support/  
Available services include:  
Presales & Technical support  
Global Support Services telephone numbers & business hours  
Authorized Service Centers  
Warranty terms will vary based on type of warranty chosen: “Managed Life” or “Usage Based”. Consult your Seagate sales  
representative for warranty terms and conditions.  
For information regarding data recovery services, visit http://www.seagate.com/services-software/data-recovery-services/  
For Seagate OEM and Distribution partner portal, visit http://www.seagate.com/partners  
Pulsar.2 SAS Product Manual, Rev. C  
1
 
1.0 SCOPE  
®
This manual describes Seagate Technology® LLC, Pulsar .2 SAS (Serial Attached SCSI) drives.  
Pulsar.2 drives support the SAS Protocol specifications to the extent described in this manual. The SAS Interface 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 manual. The data 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  
Unless otherwise stated, the information in this manual applies to standard and Self-Encrypting Drive models.  
Standard models  
Standard SED models  
FIPS 140-2 LEVEL 2  
ST800FM0002  
ST800FM0032  
ST400FM0002  
ST400FM0042  
ST200FM0002  
ST200FM0042  
ST100FM0002  
ST100FM0052  
ST800FM0012  
ST800FM0042  
ST800FM0022  
Note. Previous generations of Seagate Self-Encrypting Drive models were called Full Disk Encryption (FDE) models before a differ-  
entiation between drive-based encryption and other forms of encryption was necessary.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
2
   
2.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 of safety, power distribution, shielding,  
audible noise control, and temperature regulation. In particular, the drives must be securely mounted to guarantee the specified  
2.1  
STANDARDS  
The Pulsar.2 family complies with Seagate standards as noted in the appropriate sections of this manual and the Seagate SAS Interface  
Manual, part number 100293071.  
The drives are recognized in accordance with UL 60950 and CSA 60950 as tested by UL(CSA) and EN60950 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.  
2.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  
subassembly and is not subject to Subpart B of Part 15 of the FCC Rules and Regulations nor the Radio Interference Regulations 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.  
2.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 10 through 12, DC  
power requirements.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
3
                                 
2.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 tested in a representative 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 and 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 Standard, CNS13438.  
2.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 chemical  
substance restrictions, and our suppliers document their compliance with our requirements by providing material content declarations for  
all parts and materials for the 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 ongoing compliance with the RoHS Directive and all laws and regulations which  
restrict chemical content in electronic products. These systems include standard operating 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.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
4
         
2.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 substance content of the part (at the homogenous 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.  
2.2  
REFERENCE DOCUMENTS  
SCSI Commands Reference Manual  
Seagate part number: 100293068  
SAS Interface Manual  
ANSI SAS Documents  
Seagate part number: 100293071  
SFF-82232.5” Drive Form Factor with Serial Connector  
SFF-8460HSS Backplane Design Guidelines  
SFF-8470Multi Lane Copper Connector  
SFF-8482SAS Plug Connector  
ANSI INCITS.xxx Serial Attached SCSI (SAS-2) Standard (T10/1760-D)  
ISO/IEC 14776-xxxSCSI Architecture Model-3 (SAM-4) Standard (T10/1683-D)  
ISO/IEC 14776-xxxSCSI Primary Commands-3 (SPC-4) Standard (T10/1731-D)  
ISO/IEC 14776-xxxSCSI Block Commands-3 (SBC-3) Standard (T10/1799-D)  
ANSI Small Computer System Interface (SCSI) Documents  
X3.270-1996(SCSI-3) Architecture Model  
Trusted Computing Group (TCG) Documents (apply to Self-Encrypting Drive models only)  
TCG Storage Architecture Core Specification, Rev. 1.0  
TCG Storage Security Subsystem Class Enterprise Specification, Rev. 1.0  
Self-Encrypting Drives Reference Manual  
JEDEC Standards  
Seagate part number: 100515636  
JESD218 - Solid-State Drive (SSD) Requirements and Endurance Test Method  
JESD219 - Solid-State Drive (SSD) Endurance Workloads  
In case of conflict between this document and any referenced document, this document takes precedence.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
5
               
3.0  
GENERAL DESCRIPTION  
Pulsar.2 drives provide high performance, high capacity data storage for a variety of systems with a Serial Attached SCSI (SAS) interface.  
The Serial Attached SCSI interface is designed to meet next-generation computing demands for performance, scalability, flexibility and  
high-density storage requirements.  
Pulsar.2 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. Pulsar.2 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 drives. This allows users to continue to leverage existing investment in SCSI  
while gaining a 6Gb/s serial data 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  
standards defined by the Trusted Computing Group (see www.trustedcomputinggroup.org).  
Note. Never disassemble and do not attempt to service items in the enclosure. The drive does not contain user-replaceable parts.  
Opening for any reason voids the drive warranty.  
3.1  
STANDARD FEATURES  
Pulsar.2 SAS drives have the following standard features:  
• 1.5 / 3.0 / 6.0 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, 528, 4096, 4160, 4192, or 4224 bytes per logical block)  
• Industry standard SFF 2.5-inch dimensions  
• ECC maximum burst correction length of 96 bits  
• No preventive maintenance or adjustments required  
• Self diagnostics performed when power is applied to the drive  
• Vertical, horizontal, or top down mounting  
• Drive Self Test (DST)  
• Background Media Scan (BMS)  
• Parallel flash access channels  
• Power loss data protection  
• Thin Provisioning with Block Unmap Support  
• Silent operation  
• Lifetime Endurance Management (available on certain models)  
Pulsar.2 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  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
6
           
3.2  
MEDIA DESCRIPTION  
The media used on the drive consists of Multi Layer Cell (MLC) NAND Flash for improved reliability and performance.  
3.3  
PERFORMANCE  
• Programmable multi-segmentable cache buffer  
• 600MB/s maximum instantaneous data transfers.  
• Background processing of queue  
• Non-Volatile Write Cache  
Note. There is no significant performance difference between Self-Encrypting Drive and standard (non-Self-Encrypting Drive) mod-  
els.  
3.4  
RELIABILITY  
• Annualized Failure Rate (AFR) of 0.44%  
• Mean time between failures (MTBF) of 2,000,000 hours  
• Incorporates industry-standard Self-Monitoring Analysis and Reporting Technology (S.M.A.R.T.)  
• "Managed Life" or "Usage Based" warranty options [1]  
[1]  
Warranty terms will vary based on type of warranty chosen: “Managed Life” or “Usage Based” Consult your Seagate sales representative for war-  
ranty terms and conditions.  
3.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 UNIT 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 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. The Capacity stated is identical  
when the drive is formatted with or without PI enabled.  
Table 1: Formatted Capacity LBA Count  
CAPACITY (LBAS)  
800GB  
400GB  
200GB  
100GB  
LBA  
SIZE  
DECIMAL  
HEX  
DECIMAL  
HEX  
DECIMAL  
HEX  
DECIMAL  
HEX  
1,562,824,368  
1,529,743,600  
1,509,354,136  
1,487,666,080  
195,353,046  
192,307,693  
190,839,695  
189,393,940  
5D26CEB0h  
781,422,768  
764,871,800  
754,677,072  
743,833,040  
97,677,846  
96,153,847  
95,419,848  
94,696,970  
2E9390B0h  
390,721,968  
382,435,904  
1749F1B0h  
195,371,568  
191,217,952  
BA52230h  
512  
5B2E08F0h  
59F6EA98h  
58ABFBA0h  
BA4D9D6h  
B7661EDh  
B5FFB8Fh  
B49EC14h  
2D970478h  
2CFB7550h  
2C55FDD0h  
5D27216h  
5BB30F7h  
5AFFDC8h  
5A4F60Ah  
16CB8240h  
B65C120h  
520  
524  
377,338,536 167DBAA8h 188,669,272 B3EDD58h  
371,916,520  
48,840,246  
48,076,924  
47,709,924  
47,348,485  
162AFEE8h  
2E93E36h  
2DD987Ch  
2D7FEE4h  
2D27B05h  
185,958,264  
24,421,446  
24,038,462  
23,854,962  
23,674,243  
B157F78h  
174A446h  
16ECC3Eh  
16BFF72h  
1693D83h  
528  
4096  
4160  
4192  
4224  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
7
                     
3.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.  
3.7  
FACTORY-INSTALLED OPTIONS  
OEMs 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 LBA size requested.  
• Single-unit shipping pack. The drive is normally shipped in bulk packaging to provide maximum protection against transit damage. Units  
shipped individually require additional protection as provided by the single 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.  
3.8  
THIN PROVISIONING  
3.8.1  
Logical Block Provisioning  
The drive is designed with a feature called Thin Provisioning. Thin Provisioning is a technique which does not require Logical Blocks to be  
associated to Physical Blocks on the storage medium until such a time as needed. The use of Thin Provisioning is a major factor in SSD  
products because it reduces the amount of wear leveling and garbage collection that must be performed. The result is an increase in the  
products endurance. For more details on Logical Block Provisioning and Thin Provisioning, Reference the SBC-3 document provided by  
the T-10 committee.  
3.8.2  
Thin Provisioning capabilities  
The level of Thin Provisioning support may vary by product model. Devices that support Thin Provisioning are allowed to return a default  
data pattern for read requests made to Logical Blocks that have not been mapped to Physical Blocks by a previous WRITE command.  
In order to determine if Thin Provisioning is supported and what features of it are implemented requires the system to send a READ  
CAPACITY 16 (9Eh) command to the drive. Thin Provisioning and the READ CAPACITY 16 (9Eh) command is defined in the Seagate  
SCSI Command Reference 100293068..  
Table 2 Thin Provisioning Product Configuration  
Product Configuration  
Non-SED  
LBPME  
LBPRZ  
Supported  
Supported  
Supported  
Not Supported  
SED  
A logical block provisioning management enabled (LBPME) bit set to one indicates that the logical unit implements logical block  
provisioning management. An LBPME bit set to zero indicates that the logical unit is fully provisioned and does not implement logical block  
provisioning management.  
A logical block provisioning read zeros (LBPRZ) bit set to one indicates that, for an unmapped LBA specified by a read operation, the  
device server sends user data with all bits set to zero to the data-in buffer. An LBPRZ bit set to zero indicates that, for an unmapped LBA  
specified by a read operation, the device server may send user data with all bits set to any value to the data-in buffer.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
8
                 
3.8.3  
UNMAP  
The UNMAP command requests that the device server break the association of a specific Logical Block address from a Physical Block,  
thereby freeing up the Physical Block from use and no longer requiring it to contain user data. An unmapped block will respond to a READ  
command with data that is determined by the setting of the LBPRZ bit in the READ CAPACITY parameter data.  
3.8.4  
FORMAT UNIT command  
A device which supports Thin Provisioning will be capable of performing a SCSI FORMAT UNIT command which allocates Logical Blocks  
Addresses that are not linked to Physical Block Locations. A FORMAT command will cause all LBAs to become unmapped.  
3.8.5  
Protection Information (PI) and Security (SED)  
The requirements in this section apply to any device which supports LBA unmapping.  
In SCSI devices, umapped LBAs are defined as part of the Thin Provisioning model. Support of the Thin Provisioning model is indicated by  
the LBPME bit having a value of '1' in the READ CAPACITY (16) parameter data.  
When a region of LBA's are erased via cryptographic erase, as part of the erase, the drive shall unmap those LBAs.  
If the host attempts to access an unmapped or trimmed LBA, the drive shall return scrambled data. For a given LBA, the data shall be  
identical from access to access, until that LBA is either updated with actual data from the host or that LBA is cryptographically erased. The  
drive shall report a value of '0' in the LBPRZ field returned in the READ CAPACITY (16) parameter data.  
If the host attempts to access an unmapped LBA on a drive that has been formatted with Protection Information (PI), the drive shall return  
scrambled PI data for that LBA. Depending on the value of the RDPROTECT field in the data-access command CDB, this may result in the  
drive returning a standard PI error to the host.  
If the host reduces the addressable capacity of the drive via a MODE SELECT command, the drive shall unmap or trim any LBA within the  
inaccessible region of the device.  
Additionally, an UNMAP command is not permitted on a locked band.  
Table 3 PI and SED Drive Configuration  
DRIVE CONFIGURATION  
Standard  
Enabled  
SED  
PI Setting  
Disabled  
Disabled  
Enabled  
PROT_EN bit  
LBPME bit  
0
1
1
1
1
1
0
1
0
1
1
LBPRZ bit  
0
PI Check Requested  
N/A  
Yes  
No  
N/A  
Yes  
No  
DATA Returned for  
Thin Provisioned LBA  
0x00  
0x00  
0x00  
Random  
None  
None  
None  
Random  
PI Returned for  
Thin Provisioned LBA  
Scrambled  
PI data  
None  
0xFF  
0xFF  
PI Check Performed  
N/A  
No  
No  
No  
No  
No  
N/A  
No  
Yes  
Yes  
No  
No  
Error reported to Host  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
9
                         
4.0  
PERFORMANCE CHARACTERISTICS  
This section provides detailed information concerning performance-related characteristics and features of Pulsar.2 drives.  
Note. Data provided is based on format at 512-bytes.  
4.1  
INTERNAL DRIVE CHARACTERISTICS  
Drive capacity  
800400  
200100  
GB (formatted, rounded off value)  
Flash Memory Type  
Emulated LBA Size  
Native Programmable  
Page Size  
Default Transfer  
Alignment Offset  
NAND MLC  
512, 520, 524, 528, 4096, 4160, 4192, or 4224  
8192 User Bytes  
0
4.2  
PERFORMANCE CHARACTERISTICS  
See Section 11.4.1, "SAS physical interface" and the SAS Interface Manual (part number 100293071) for additional timing details.  
4.2.1  
Access time  
Access measurements are taken with nominal power at 25°C ambient temperature. All times are measured using drive diagnostics. The  
specifications in the table below are defined as follows:  
Page-to-page access time is an average of all possible page-to-page accesses in both directions for a sequentially preconditioned  
drive.  
Average access time is a true statistical random average of at least 5000 measurements of accesses between programmable  
pages on a randomly preconditioned drive.  
Table 4 Typical Access Time (μsec)  
400, 200, 100 GB 1,2  
1 2  
,
800GB  
READ  
WRITE  
READ  
227  
60  
WRITE  
120  
Average  
293  
62  
137  
136  
3
Page to Page  
Typical  
120  
Average Latency  
273  
206  
1.  
2.  
3.  
Execution time measured from receipt of the Command to the Response.  
Assumes no errors.  
Typical access times are measured under nominal conditions of temperature, voltage, and horizontal orientation as measured on a  
representative sample of drives.  
Note. These drives are designed to provide the highest possible performance under typical conditions.  
However, due to the nature of Flash memory technologies there are many factors that can result in  
values different than those stated in this specification  
2.  
4.2.2  
FORMAT UNIT command execution time for 512-byte LBA’s (minutes)  
The device may be formatted as either a Thin Provisioned device or a Fully Provisioned device. The default format is Thin Provisioned and  
is recommended for most applications. Thin Provisioning provides the most flexibility for the device to manage the flash medium to  
maximize endurance.  
Table 5 Maximum FORMAT UNIT Times (minutes)  
Format Mode  
DCRT Bit IP Bit 800GB 400GB 200GB 100GB  
CONFIGURATION  
Non-SED  
Non-SED  
Non-SED  
Non-SED  
SED  
(Default) Thin Provisioned  
(Default) Thin Provisioned  
Fully Provisioned  
DCRT = 0  
DCRT = 1  
DCRT = 0  
DCRT = 1  
DCRT = 0  
DCRT = 1  
DCRT = 0  
DCRT = 1  
IP = 0  
IP = 0  
IP = 1  
IP = 1  
IP = 0  
IP = 0  
IP = 1  
IP = 1  
5
5
5
5
5
5
5
5
430  
280  
5
130  
100  
N/A  
N/A  
N/A  
N/A  
70  
60  
Fully Provisioned  
50  
30  
(Default) Thin Provisioned  
(Default) Thin Provisioned  
Fully Provisioned  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
N/A  
SED  
5
SED  
430  
280  
SED  
Fully Provisioned  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
10  
                           
4.2.3  
Performance  
Table 6 Performance (Managed Life Warranty)  
ST800FM00  
02  
ST800FM00  
12  
NOTE  
S
ST400FM00  
02  
ST200FM00  
02  
ST100FM00  
02  
ST800FM00  
22  
600MB/s  
Maximum Burst Transfer Rate  
Peak sequential 128KB read/write  
[1]  
370/200  
370/140  
370/190  
370/35  
data transfer rate (MB/s max)  
Sustained sequential 128KB read/  
[1]  
370/200  
370/70  
write data transfer rate (MB/s)  
Peak 4KB random read/write  
[2]  
48,000/15,000  
48,000/11,000  
48,000/12,000  
48,000/2800  
command rate (IOPs)  
Sustained 4KB random read/write  
[2]  
48,000/15,000  
48,000/5500  
command rate (IOPs)  
Sustainable 4KB Random combined  
[3]  
23,000  
22,000  
IOPS for 5 year Endurance  
(65%/35% R/W, 70% Duty Cycle)  
Table 7 Performance (Usage Based Warranty)  
ST800FM00  
NOTE  
S
32  
ST800FM00  
42  
ST400FM00  
42  
ST200FM00  
42  
ST100FM00  
52  
600MB/s  
Maximum Burst Transfer Rate  
Peak sequential 128KB read/write  
[1]  
370/200  
370/200  
370/190  
370/190  
data transfer rate (MB/s max)  
Sustained sequential 128KB read/  
[1]  
write data transfer rate (MB/s)  
Peak 4KB random read/write  
[2]  
48,000/15,000  
48,000/15,000  
48,000/12,000  
48,000/12,000  
command rate (IOPs)  
Sustained 4KB random read/write  
[2]  
command rate (IOPs)  
Sustainable 4KB Random combined  
[3]  
23,000  
22,000  
IOPS for 5 year Endurance  
(65%/35% R/W, 70% Duty Cycle)  
[1]  
[2]  
[3]  
Testing performed at Queue Depth = 32, Sequentially Preconditioned drive, using IOMeter 2006.7.27.  
Testing performed at Queue Depth = 32, Randomly Preconditioned drive, using IOMeter 2006.7.27.  
Testing performed at Queue Depth = 32, Non-Preconditioned drive, using IOMeter 2006.7.27.  
IOMeter is licensed under the Intel Open Source License and the GNU General Public License. Intel does not endorse any IOM-  
eter results.  
Peak performance is defined as the typical best case performance that the product will be able to achieve when the product is  
preconditioned as mentioned and host commands are aligned on 4KB boundaries.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
11  
   
Sustained performance is defined as the worst case performance that the product will be able to achieve when the product is  
preconditioned as mentioned and host commands are aligned on 4KB boundaries. For models that support Lifetime Endurance  
Management, write values also take into account the worst case performance throttling that may occur to ensure the product meets  
specified reliability specifications.  
Due to the nature of Flash memory technologies there are many factors that can result in values different than those stated in this  
specification. Some discrepancies can be caused by bandwidth limitations in the host adapter, operating system, or driver limitations. It is  
not the intent of this manual to cover all possible causes of performance discrepancies.  
When evaluating performance of SSD devices, it is recommended to measure performance of the device in a method that resembles the  
targeted application using real world data and workloads. Test time should also be adequately large to ensure that sustainable metrics and  
measures are obtained.  
4.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 15 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 STOP 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 15 seconds (excluding the error recovery 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 START STOP UNIT command may be used to command the drive to stop. Stop time is 3 seconds (maximum) from removal of DC  
power. SCSI stop time is 3 seconds. There is no power control switch on the drive.  
4.4  
CACHE CONTROL  
All default cache mode parameter values (Mode Page 08h) for standard OEM versions of this drive family are given in Table 20 and 21.  
4.4.1  
Caching write data  
Write caching is a write operation by the drive that makes use of a drive buffer storage area where the data to be written to the medium is  
stored while the drive performs the WRITE command.  
If the number of write data logical blocks exceed the size of the segment 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.  
Data that has not been written to the medium is protected by a back up power source which provides the ability of the data to be written to  
non-volatile medium in the event of an unexpected power loss.  
The SYNCHRONIZE CACHE command may be used to force the drive to write all cached write data to the medium. Upon completion of a  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
12  
           
5.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.  
1
Read Error Rates  
Unrecovered Data  
Miscorrected Data  
Less than 1 LBA in 1016 bits transferred  
Less than 1 LBA in 1021 bits transferred  
Less than 1 error in 1012 bits transferred  
2,000,000 hours  
Interface error rate:  
Mean Time Between Failure (MTBF):  
Annualized Failure Rate (AFR):  
Preventive maintenance:  
0.44%  
None required  
Typical Data Retention with  
3 months  
2
Power removed (at 40C)  
Endurance Rating:  
Method 1: Full drive writes per day 10  
Method 2: TBW (per JEDEC JESD218 800GB = 17,800 TB  
400GB = 8800 TB  
200GB = 4400 TB  
100GB = 2200 TB  
1. Error rate specified with automatic retries and data correction with ECC enabled and all flaws reallocated.  
2. As NAND Flash devices age with use, the capability of the media to retain a programmed value begins to deteriorate.  
This deterioration is affected by the number of times a particular memory cell is programmed and subsequently erased.  
When a device is new, it has a powered off data retention capability of up to several years. With use the retention ca-  
pability of the device is reduced. Temperature also has an effect on how long a Flash component can retain its pro-  
grammed value with power removed. At high temperature the retention capabilities of the device are reduced. Data  
retention is not an issue with power applied to the SSD. The SSD drive contains firmware and hardware features that  
can monitor and refresh memory cells when power is applied.  
3. Endurance rating is the expected amount of host data that can be written by product when subjected to a specified work-  
load at a specified operating and storage temperature. For the specific workload to achieve this level of endurance,  
please reference JEDEC Specification JESD218. TBW is defined as 1x10^12 Bytes.  
5.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 6.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.  
5.1.1  
Unrecoverable Errors  
An unrecoverable data error is defined as a failure of the drive to recover data from the media. These errors occur due to read 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.  
5.1.2  
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.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
13  
                                       
5.2  
ENDURANCE MANAGEMENT  
Customer satisfaction with Solid State Drives can be directly related to the internal algorithms which an SSD uses to manage the limited  
number of Program-Erase (PE) cycles that NAND Flash can withstand. These algorithms consist of Wearleveling, Garbage Collection,  
Write Amplification, Unmap, Data Retention, Lifetime Endurance Management.  
5.2.1  
Wear Leveling  
Wear Leveling is a technique used by the drive to ensure that all Flash cells are written to or exercised as evenly as possible to avoid any  
hot spots where some cells are used up faster than other locations. Wear Leveling is automatically managed by the drive and requires no  
user interaction. The Seagate algorithm is tuned to operate only when needed to ensure reliable product operation.  
5.2.2  
Garbage Collection  
Garbage Collection is a technique used by the drive to consolidate valid user data into a common cell range freeing up unused or obsolete  
locations to be erased and used for future storage needs. Garbage Collection is automatically managed by the drive and requires no user  
interaction. The Seagate algorithm is tuned to operate only when needed to ensure reliable product operation.  
5.2.3  
Write Amplification  
While Write Amplification is not an algorithm, it is a major characteristic of SSD's that must be accounted for by all the algorithms that the  
SSD implements. The Write Amplification Factor of an SSD is defined as the ratio of Host/User data requested to be written to the actual  
amount of data written by the SSD internal to account for the user data and the housekeeping activities such as Wear Leveling and  
Garbage Collection. The Write Amplification Factor of an SSD can also be directly affected by the characteristics of the host data being  
sent to the SSD to write. The best Write Amplification Factor is achieved for data that is written in sequential LBA's that are aligned on 4KB  
boundaries. The worst case Write Amplification Factor typically occurs for randomly written LBA's of transfer sizes that are less than 4KB  
and that originate on LBA's that are not on 4KB boundaries.  
5.2.4  
UNMAP  
A new SCSI command has been added to the SSD as part of the Thin Provisioning feature set. Use of the UNMAP command reduces the  
Write Amplification Factor of the drive during housekeeping tasks such as Wear Leveling and Garbage Collection. This is accomplished  
because the drive does not need to retain data which has been classified by the host as obsolete.  
5.2.5  
Data Retention  
Data Retention is another major characteristic of SSD's that must be accounted for by all the algorithms that the SSD implements. While  
powered up, the Data Retention of SSD cells are monitored and rewritten if the cell levels decay to an unexpected level. Data Retention  
when the drive is powered off is affected by Program and Erase (PE) cycles and the temperature of the drive when stored.  
5.2.6  
Lifetime Endurance Management (Available on select models)  
write workload could be such that the drive experiences a high Write Amplification Factor that could lead to potential wear out prior to the  
drive achieving it's expected field life. Additionally, the Data Retention spec of the SSD needs to be considered to ensure the spec is met  
once the drive is worn out. Seagate has implemented a Lifetime Endurance Management technique which helps OEMS and user to avoid  
early wear out. By monitoring the write workload being sent to the drive, the drive can add additional response time to WRITE commands  
to provide a sustainable level of performance that is capable of being sustained for the life of the drive. Most users may never see this  
added response time in their applications.  
5.2.7  
SSD Percentage Used Endurance Indicator  
An application can interrogate the drive through the host to determine an estimate of the percentage of device life that has been used. To  
accomplish this, issue a LOG SENSE command to log page 0x11. This allows applications to read the contents of the Percentage Used  
Endurance Indicator parameter code. The Percentage Used Endurance Indicator is defined in the T10 document SBC-3 available from the  
T10 committee.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
14  
                             
5.3  
RELIABILITY AND SERVICE  
Integrators can enhance the reliability of Pulsar.2 drives by ensuring that the drive receives adequate cooling. Section 6.0 provides  
temperature measurements and other information that may be used to enhance the service life of the drive. Section 10.2 provides  
recommended air-flow information.  
5.3.1  
Annualized Failure Rate (AFR) and Mean Time Between Failure (MTBF)  
The production drive shall achieve an AFR of 0.44% (MTBF of 2,000,000 hours) when operated in an environment that ensures the case  
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.  
the specifications in Section 6.5 will increase the product AFR and decrease the MTBF.  
5.3.2  
Preventive maintenance  
No routine scheduled preventive maintenance is required.  
5.3.3  
Hot plugging the drive  
When a drive 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 hazard, or ESD potential hazard  
is presented during the hot connect/disconnect operation. Discharge the static electricity from the drive carrier prior to insert-  
ing it into the system.  
5.3.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 administrators to back up the data before  
an actual failure occurs.  
Note. The drive’s firmware monitors specific attributes for degradation over time but can’t predict instantaneous 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.  
An application 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.  
An application can interrogate the drive through the host to determine the time remaining before the next scheduled measurement and  
data logging process occurs. To accomplish this, issue a LOG SENSE command to log page 0x3E. This allows applications to control  
when S.M.A.R.T. interruptions occur. Forcing S.M.A.R.T. with the REZERO UNIT command resets the timer.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
15  
                     
Performance impact  
S.M.A.R.T. attribute data is saved to the media so that the events that caused a predictive 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 media is interruptible. 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 errors occur and signals a predictive failure if the rate of degraded errors increases to an  
unacceptable level. To determine rate, error events are logged and compared to the number of total operations for a given attribute. The  
interval defines the number of operations over which to measure the rate. The counter that keeps track of the current number 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.  
Error rate is the number of errors per operation. The algorithm that S.M.A.R.T. uses to record rates of error is to set thresholds for the  
number of errors and appropriate 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 each time the error  
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.  
5.3.5  
Thermal monitor  
Pulsar.2 drives implement a temperature warning system which:  
1. Signals the host if the temperature exceeds a value which would threaten the drive.  
2. Signals the host if the temperature exceeds a user-specified value. (i.e., the reference temperature 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  
threshold. The temperature is measured at power-up and then at ten-minute intervals 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. Administrators 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 reporting mechanism is controlled by the Method of Reporting  
Informational Exceptions field (MRIE) on the Informational Exceptions Control (IEC) mode page (1Ch).  
The current algorithm implements two temperature trip points. The first trip point is set at 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 8) can be used to set this trip point. The default value for this drive is listed in the table, however,  
applications can set it to any value in the range defined. If a temperature is specified that is greater than the maximum allowed in this field,  
the temperature is rounded down to the maximum allowed. A sense code is sent to the host to indicate the rounding of the parameter field.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
16  
 
Table 8 Temperature Log Page (0Dh)  
Parameter Code  
Description  
800/400/200/100GB  
Primary Temperature  
Drive Temperature  
65°C  
0000h  
Default Setting  
Reference Temperature  
0001h  
Changeable Range  
0 to 65°C  
5.3.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 every logical block address (LBA) of the  
drive. The short test is time-restricted and limited in length—it does not scan the entire media contents, but does some fundamental tests  
and scans portions of the media.  
If DST encounters an error during either of these tests, it reports a "diagnostic failed" condition. If the drive fails the test, remove it from  
service and return it to Seagate for service.  
5.3.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 drive parameters are not modified to test the drive more stringently, and the recovery capabilities 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 recovery processes required to recover the data.  
The following conditions are considered DST failure conditions:  
• Read error after recovery attempts are exhausted  
• Write error after recovery attempts are exhausted  
Recovered errors will not be reported as diagnostic failures.  
5.3.6.2  
Implementation  
This section provides all of the information necessary to implement the DST function on this drive.  
5.3.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 UNIT, or another  
DST. It is the responsibility of the host application to determine the “not ready” cause.  
5.3.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.  
5.3.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 two segments: an electrical test segment and a read/verify scan 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 contents, 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 "diagnostic failed" condition. This option provides a quick confidence test of the drive.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
17  
 
Extended test (Function Code: 010b)  
The objective of the extended test option is to empirically test critical drive components. The read operation tests the media contents. The  
integrity of the media is checked through a read/verify scan of the media.  
The anticipated length of the Extended test is reported through the Control Mode page.  
5.3.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 beginning of the self-test results log parameter 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 Self-Test 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. The self-  
test results 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.  
5.3.6.2.5  
Abort  
There are several ways to abort a diagnostic. Applications can use a SCSI Bus Reset or a Bus Device Reset message to abort the  
diagnostic.  
Applications 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).  
5.3.7  
Product warranty  
Warranty terms will vary based on type of warranty chosen: “Managed Life” or “Usage Based”. Consult your Seagate sales representative  
for warranty terms and conditions.  
Managed Life Warranty  
This warranty is term based and includes the Lifetime Endurance Management feature stated in section 6.2.6.  
Usage Based Warranty  
This warranty is based on the shorter of term and endurance usage of the drive.  
Shipping  
When transporting or shipping a drive, use only a Seagate-approved container. Keep the 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.  
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.  
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 Seagate 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.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
18  
             
6.0  
PHYSICAL/ELECTRICAL SPECIFICATIONS  
This section provides information relating to the physical and electrical characteristics of the drive.  
6.1  
POWER SPECIFICATIONS  
The drive receives DC power (+5V and +12V) through the standard SAS interface.  
6.1.1  
Power consumption  
Power requirements for the drives are listed in the tables beginning on page 21. Typical power measurements are based on an average of  
drives tested, under nominal conditions, using +5V and +12V input voltage at 60°C ambient temperature.  
• Startup power  
Startup power is measured from the time of power-on to the time that the drive reaches operating condition and can process media  
access commands.  
• Peak operating mode  
During peak operating mode, the drive is tested in various read and write access patterns to simulate the worst-case power consump-  
tion.  
• Idle mode power  
Idle mode power is measured with the drive powered up and ready for media access commands, with no media access commands  
having been received from the host.  
6.2  
AC POWER REQUIREMENTS  
None.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
19  
                                   
6.3  
DC POWER REQUIREMENTS  
Table 9 800GB standard model DC power requirements  
PARAMETER  
Regulation  
Voltage  
800GB (6.0GB)  
±5%  
±5%  
+5V  
+12V  
CURRENT (A)  
CURRENT (A)  
POWER (W)  
DC  
Average idle current  
Maximum starting current  
(peak DC) DC  
0.42  
0.19  
4.38  
3σ  
3σ  
3σ  
0.79  
0.60  
0.45  
0.49  
0.71  
0.20  
(peak AC) AC  
Delayed start (max) DC  
Peak operating current (random read):  
Typical DC  
4.65  
DC  
3σ  
0.49  
0.51  
0.90  
0.29  
0.31  
0.61  
5.93  
6.27  
Maximum DC  
Maximum (peak) DC  
Peak operating current (random write)  
Typical DC  
3σ  
DC  
3σ  
0.49  
0.52  
0.95  
0.57  
0.59  
1.13  
9.29  
9.68  
Maximum DC  
Maximum (peak) DC  
Peak operating current (sequential read)  
Typical DC  
3σ  
DC  
3σ  
0.58  
0.62  
1.01  
0.44  
0.46  
0.76  
8.18  
8.62  
Maximum DC  
Maximum (peak) DC  
Peak operating current (sequential write)  
Typical DC  
3σ  
DC  
3σ  
0.48  
0.52  
0.85  
0.51  
0.55  
1.13  
8.52  
9.20  
Maximum DC  
Maximum (peak) DC  
3σ  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
20  
             
Table 10 400GB standard model DC power requirements  
PARAMETER  
Regulation  
Voltage  
400GB (6.0GB)  
±5%  
±5%  
+5V  
+12V  
CURRENT (A)  
CURRENT (A)  
POWER (W)  
DC  
Average idle current  
Maximum starting current  
(peak DC) DC  
0.41  
0.12  
3.49  
3σ  
3σ  
3σ  
0.50  
0.54  
0.45  
0.35  
0.60  
0.13  
(peak AC) AC  
Delayed start (max) DC  
Peak operating current (random read):  
Typical DC  
3.81  
DC  
3σ  
0.47  
0.51  
0.95  
0.20  
0.21  
0.48  
4.75  
5.07  
Maximum DC  
Maximum (peak) DC  
Peak operating current (random write)  
Typical DC  
3σ  
DC  
3σ  
0.47  
0.52  
0.93  
0.44  
0.46  
1.11  
7.63  
8.12  
Maximum DC  
Maximum (peak) DC  
Peak operating current (sequential read)  
Typical DC  
3σ  
DC  
3σ  
0.55  
0.60  
1.00  
0.31  
0.32  
0.59  
6.47  
6.84  
Maximum DC  
Maximum (peak) DC  
Peak operating current (sequential write)  
Typical DC  
3σ  
DC  
3σ  
0.46  
0.52  
0.91  
0.44  
0.48  
1.14  
7.58  
8.36  
Maximum DC  
Maximum (peak) DC  
3σ  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
21  
       
Table 11 200GB standard model DC power requirements  
PARAMETER  
Regulation  
Voltage  
200GB (6.0GB)  
±5%  
±5%  
+5V  
+12V  
CURRENT (A)  
CURRENT (A)  
POWER (W)  
DC  
Average idle current  
0.43  
0.11  
3.47  
Maximum starting current  
(peak DC) DC  
(peak AC) AC  
3σ  
3σ  
3σ  
0.51  
0.61  
0.45  
0.31  
1.26  
0.12  
Delayed start (max) DC  
Peak operating current (random read):  
Typical DC  
3.69  
DC  
3σ  
0.48  
0.51  
0.86  
0.19  
0.20  
0.47  
4.68  
5.15  
Maximum DC  
Maximum (peak) DC  
Peak operating current (random write)  
Typical DC  
3σ  
DC  
3σ  
0.47  
0.51  
0.82  
0.41  
0.42  
0.98  
7.27  
7.59  
Maximum DC  
Maximum (peak) DC  
Peak operating current (sequential read)  
Typical DC  
3σ  
DC  
3σ  
0.55  
0.59  
0.80  
0.28  
0.29  
0.57  
6.11  
6.43  
Maximum DC  
Maximum (peak) DC  
Peak operating current (sequential write)  
Typical DC  
3σ  
DC  
3σ  
0.47  
0.51  
0.76  
0.41  
0.42  
0.95  
7.27  
7.59  
Maximum DC  
Maximum (peak) DC  
3σ  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
22  
       
Table 12 100GB standard model DC power requirements  
PARAMETER  
Regulation  
Voltage  
100GB (6.0GB)  
±5%  
±5%  
+5V  
+12V  
CURRENT (A)  
CURRENT (A)  
POWER (W)  
DC  
Average idle current  
0.43  
0.12  
3.59  
Maximum starting current  
(peak DC) DC  
(peak AC) AC  
3σ  
3σ  
3σ  
0.48  
1.53  
0.45  
0.32  
0.61  
0.13  
Delayed start (max) DC  
Peak operating current (random read):  
Typical DC  
2.38  
DC  
3σ  
0.50  
0.51  
0.88  
0.18  
0.20  
0.47  
4.66  
4.95  
Maximum DC  
Maximum (peak) DC  
Peak operating current (random write)  
Typical DC  
3σ  
DC  
3σ  
0.49  
0.51  
0.80  
0.36  
0.39  
0.89  
6.77  
7.23  
Maximum DC  
Maximum (peak) DC  
Peak operating current (sequential read)  
Typical DC  
3σ  
DC  
3σ  
0.56  
0.59  
0.89  
0.26  
0.29  
0.56  
5.92  
6.43  
Maximum DC  
Maximum (peak) DC  
Peak operating current (sequential write)  
Typical DC  
3σ  
DC  
3σ  
0.50  
0.52  
0.83  
0.35  
0.38  
0.94  
6.70  
7.16  
Maximum DC  
Maximum (peak) DC  
3σ  
[1]  
[2]  
Measured with average reading DC ammeter. Instantaneous +12V current peaks will exceed these values. Power supply at nominal voltage. N (num-  
ber of drives tested) = 6, 60 Degrees C ambient.  
For +12 V, a –10% tolerance is allowed during initial start but must return to ±5% before reaching ready state. 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.  
See +12V current profile in Figure 6 (for 400GB models) and Figure 7 (for 200GB models).  
See +12V current profile in Figure 8 (for 100GB models).  
This condition occurs after OOB and Speed Negotiation completes but before the drive has received the Notify Spinup primitive.  
See paragraph 6.3.1, "Conducted noise immunity." Specified voltage tolerance includes ripple, noise, and transient response.  
[3]  
[4]  
[5]  
[6]  
General DC power requirement notes.  
1. Minimum current loading for each supply voltage is not less than 1.7% of the maximum operating 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 start, are measured after a 10-minute warm up.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
23  
       
6.3.1  
Conducted noise immunity  
Noise is specified as a periodic and random distribution of frequencies covering a defined frequency. 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.  
6.3.2  
Power sequencing  
The drive does not require power sequencing. The drive protects against inadvertent writing during power-up and down.  
6.3.3  
Current profiles  
The +12V and +5V current profiles for the Pulsar.2 drives are shown below.  
Figure 1.  
Current profiles for 800GB models  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
24  
               
Figure 2.  
Current profiles for 400GB models  
Figure 3.  
Current profiles for 200GB models  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
25  
   
Figure 4.  
Current profiles for 100GB models  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
26  
 
6.4  
POWER DISSIPATION  
800GB models in 6Gb operation  
Typical power dissipation under idle conditions in 6Gb operation is 4.38 watts 14.95 BTUs per hour).  
for a drive in your 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.  
800GB (at 6Gb) DC current and power vs. input/output operations per second  
400GB models in 6Gb operation  
Typical power dissipation under idle conditions in 6Gb operation is 3.49 watts 11.91 BTUs per hour).  
for a drive in your 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.  
400GB (at 6Gb) DC current and power vs. input/output operations per second  
200GB models in 6Gb operation  
Typical power dissipation under idle conditions in 6Gb operation is 3.47 watts (11.84 BTUs per hour).  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
27  
       
for a drive in your 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 7.  
200GB (at 6Gb) DC current and power vs. input/output operations per second  
100GB models in 6Gb operation  
Typical power dissipation under idle conditions in 6Gb operation is 3.59 watts 12.25 BTUs per hour).  
for a drive in your 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.  
100GB (at 6Gb) DC current and power vs. input/output operations per second  
ENVIRONMENTAL LIMITS  
6.5  
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.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
28  
           
6.5.1  
a. Operating  
The drive meets the operating specifications over a 41°F to 140°F (5°C to 60°C) drive case temperature range with a maximum  
Temperature  
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). Occasional excursions in operating temperature between the  
rated MTBF temperature and the maximum drive operating case temperature may occur without impact to the rated MTBF  
temperature. However continual or sustained operation at case temperatures beyond the rated MTBF temperature will degrade the  
drive MTBF and reduce product reliability.  
is provided, 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 9 and 10 for temperature checkpoint.  
b. Non-operating  
–40° to 158°F (–40° to 70°C) package ambient with a maximum gradient of 36°F (20°C) per hour. This specification assumes that the  
drive is packaged in the shipping container designed by Seagate for use with drive.  
Figure 9.  
Temperature check point location - 15mm drives  
Figure 10.  
Temperature check point location - 7mm drives  
Note. Images may not represent actual product, for reference only.  
6.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.  
6.5.3  
a. Operating  
–200 to +10,000 feet (–60.96 to +3048 meters)  
Effective altitude (sea level)  
b. Non-operating  
–200 to +40,000 feet (–60.96 to +12,192 meters)  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
29  
                             
6.5.4  
Shock and vibration  
Shock and vibration limits specified in this document 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, resonances 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  
6.5.4.1  
Shock  
a. Operating—normal  
The drive, as installed for normal operation, shall operate error free while subjected to intermittent shock not exceeding:  
1000 Gs at a maximum duration of 0.5ms (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.  
Note. This specification does not cover connection issues that may result from testing at this level.  
b. Non-operating  
The limits of non-operating shock shall apply to all conditions of handling 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.  
1000 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 11.  
Recommended mounting  
Note. Image may not represent actual product, for reference only.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
30  
                 
6.5.4.2  
Vibration  
a. Operating—normal  
The drive as installed for normal operation, shall comply with the complete specified performance while subjected to vibration:  
Vibration may be applied in the X, Y, or Z axis.  
Operating normal translational random shaped profile  
20 - 2000 Hz  
11.08 GRMS  
Note. This specification does not cover connection issues that may result from testing at this level.  
b. Operating—abnormal  
Equipment as installed for normal operation shall not incur physical damage while subjected to periodic vibration:  
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 shaped profile  
20 - 2000 Hz  
11.08 GRMS  
Note. This specification does not cover connection issues that may result from testing at this level.  
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 vibration.  
Vibration may be applied in the X, Y, or Z axis.  
Non-operating translational random shaped profile  
20 - 2000 Hz  
11.08 GRMS  
6.5.5  
Air cleanliness  
The drive is designed to operate in a typical office environment with minimal environmental control.  
6.5.6  
Corrosive environment  
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 exposing any electronic components 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 damaging. In  
addition, electronic components 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.  
6.5.7  
Electromagnetic susceptibility  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
31  
                         
6.6  
MECHANICAL SPECIFICATIONS  
Weight:  
0.353 pounds 160 grams  
Note. These dimensions conform to the Small Form Factor Standard documented in SFF-8201 and  
SFF-8223 found at www.sffcommittee.org.  
Figure 12.  
Mounting configuration dimensions (800GB models)  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
32  
           
Weight:  
0.220 pounds 100 grams  
Note. These dimensions conform to the Small Form Factor Standard documented in SFF-8201 and  
SFF-8223 found at www.sffcommittee.org  
Figure 13.  
Mounting configuration dimensions (400, 200 & 100GB models)  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
33  
   
7.0 ABOUT FIPS  
The Federal Information Processing Standard (FIPS) Publication 140-2 is a U.S. Government Computer Security Standard used to  
accredit cryptographic modules. It is titled 'Security Requirements for Cryptographic Modules (FIPS PUB 140-2)' and is issued by the  
National Institute of Standards and Technology (NIST).  
Purpose  
This standard specifies the security requirements that will be satisfied by a cryptographic module utilized within a security system  
protecting sensitive but unclassified information. The standard provides four increasing, qualitative levels of security: Level 1, Level 2,  
Level 3 and Level 4. These levels are intended to cover the wide range of potential applications and environments in which cryptographic  
modules may be employed.  
Validation Program  
Products that claim conformance to this standard are validated by the Cryptographic Module Validation Program (CMVP) which is a joint  
effort between National Institute of Standards and Technology (NIST) and the Communications Security Establishment (CSE) of the  
Government of Canada. Products validated as conforming to FIPS 140-2 are accepted by the Federal agencies of both countries for the  
protection of sensitive information (United States) or Designated Information (Canada).  
In the CMVP, vendors of cryptographic modules use independent, accredited testing laborites to have their modules tested. National  
Voluntary Laboratory Accreditation Program (NVLAP) accredited laboratories perform cryptographic module compliance/conformance  
testing.  
Seagate Enterprise SED  
to satisfy FIPS 140-2 Level 2 requirements. In order to operate in FIPS Approved Mode of Operation, these SEDs require security  
initialization. For more information, refer to 'Security Rules' section in the 'Security Policy' document uploaded on the NIST website. To  
Security Level 2  
Security Level 2 enhances the physical security mechanisms of a Security Level 1 cryptographic module by adding the requirement for  
tamper-evidence, which includes the use of tamper-evident coatings or seals on removable covers of the module. Tamper-evident coat-  
ings or seals are placed on a cryptographic module so that the coating or seal must be broken to attain physical access to the critical  
security parameters (CSP) within the module. Tamper-evident seals (example shown in Figure 14, page 34) are placed on covers to  
protect against unauthorized physical access. In addition Security Level 2 requires, at a minimum, role-based authentication in which a  
cryptographic module authenticates the authorization of an operator to assume a specific role and perform a corresponding set of ser-  
vices.  
Figure 14. Example of FIPS tamper evidence labels.  
Note. Image is for reference only, do not represent actual drive.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
34  
             
8.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  
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 the appropriate command payloads.  
8.1  
DATA ENCRYPTION  
Encrypting drives use one in-line encryption engine for each port, employing AES-256 data encryption 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 and cannot be disabled.  
The 32-byte Data Encryption Key (DEK) is a random number which is generated by the drive, never 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  
8.2  
CONTROLLED ACCESS  
The drive has two security providers (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.  
8.2.1  
Admin SP  
available using the SID (Secure ID) password or the MSID (Manufacturers Secure ID) password.  
8.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).  
8.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 can only be read by the  
host electronically over the interface. 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.  
8.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 numbers as Authentication Keys (passwords) for the drive’s Admin and Locking SPs.  
8.4  
DRIVE LOCKING  
bands.  
The variable "LockOnReset" should be set to "PowerCycle" to ensure that the data bands will be locked if power is lost. In addition  
"ReadLockEnabled" and "WriteLockEnabled" must be set to true in the locking table in order for the bands "LockOnReset" setting of  
"PowerCycle" to actually lock access to the band when a "PowerCycle" event occurs. 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 allowing the drive to accept any attempt to download  
new firmware. The drive owner must use the SID credential to lock the firmware download port before firmware updates will be rejected.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
35  
                                                                                     
8.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 allocate Band1 by specifying a start LBA and an LBA range. The real estate for this  
band is taken from the Global Band. An additional 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 band ending at LBA (x) and the next beginning at LBA (x+1).  
Each data band has its own drive-generated encryption key and its own user-supplied password. The host may change the Encryption Key  
8.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 particular band. Once changed, 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.  
8.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.  
8.8  
POWER REQUIREMENTS  
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. See the tables in  
8.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 16:  
• SECURITY PROTOCOL OUT (B5h)  
• SECURITY PROTOCOL IN (A2h)  
8.10  
SANITIZE - CRYPTOGRAPHIC ERASE  
This command cryptographically erases all user data on the drive by destroying the current data encryption key and replacing it with a new  
data encryption key randomly generated by the drive. Sanitize CRYPTOGRAPHIC ERASE is a SCSI CDB Op code 48h and selecting the  
service action code 3 (CRYPTOGRAPHIC ERASE).  
8.11  
REVERTSP  
SED models will support the RevertSP feature which 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. In order to execute the RevertSP method the unique PSID (Physical Secure ID)  
printed on the drive label must be provided. PSID is not electronically accessible and can only be manually read from the drive label or  
scanned in via the 2D barcode.  
8.12  
SANITIZE FEATURE SET ON SED DRIVES  
The drive shall support the Sanitize Feature Set as defined in ANSI/INCITS ACS-2 with the exceptions and/or modifications described in  
this section.  
The drive shall not support the OVERWRITE EXT and BLOCK ERASE EXT sub-commands.  
Support of the SANITIZE FREEZE LOCK EXT command shall be determined on a customer-specific basis. OEM drives shall support the  
command.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
36  
                                 
9.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 system 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 9.4)  
• Auto-Reallocation (see Section 9.5)  
The read error rates and specified storage capacities are not dependent on host (initiator) defect management routines.  
9.1  
DRIVE INTERNAL DEFECTS/ERRORS  
During the initial drive manufacturing test 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). At factory format time, these known defects are also  
deallocated, that is, marked as retired and the location listed in the defects reallocation table. The “P” list is not 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.  
The drive uses a vendor unique format to report defects via the READ DEFECT DATA command pending T10 standardization of a format  
for Solid State Devices. This format defect type is defined as 110b in the SCSI FORMAT UNIT command. The definition of the 110b format  
is defined in the following table.  
Table 13 SSD Physical format address descriptor  
Bit  
7
6
5
4
3
2
1
0
Byte  
0
1
2
3
4
5
6
7
(MSB)  
MEDIA ID  
(LSB)  
CHANNEL  
DIE  
(MSB)  
BLOCK  
(LSB)  
RESERVED  
VENDOR UNIQUE  
The MEDIA ID field contains an identifier for the flash controller for devices that utilize more than one flash controller.  
The CHANNEL field contains the channel number within the corresponding Flash Controller.  
The DIE field contains the die number within channel.  
The BLOCK field contains the block number within the die.  
The VENDOR UNIQUE field may contain vendor unique information.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
37  
               
9.2  
DRIVE ERROR RECOVERY PROCEDURES  
When an error occurs during drive operation, the drive performs error recovery procedures to attempt to recover the data. The error  
recovery procedures used are not user changeable.  
9.3  
SAS SYSTEM ERRORS  
Information on the reporting of operational errors across the interface is given in the SAS Interface Manual. The SSP Response returns  
information to the host about numerous kinds of errors. 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.  
9.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 reads across the entire addressable space of the media while the drive is idle. In RAID arrays, BMS allows hot  
spare drives to be scanned for defects prior to being put 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  
and reallocated.  
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-initiated media scanning activity.  
Since the background scan functions are only done during idle periods, BMS causes a negligible impact to system performance. The BMS  
scan is performed 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-servicing activity from BMS  
only impacts the first command that interrupted BMS, this results in a typical delay of about 1ms.  
9.5  
AUTO-REALLOCATION  
Auto-Reallocation allows the drive to reallocate unreadable locations on a subsequent write command if the recovery process deems the  
location to be defective. The drive performs auto-reallocation on every WRITE command. With each write to a Logical LBA, the drive  
writes the data to a different physical media location. Physical locations that return unrecoverable errors are retired during future WRITE  
attempts and associated recovery process.  
This is in contrast to the system having to use the REASSIGN BLOCKS command to reassign a location that was unreadable and then  
generate a WRITE command to rewrite the data. This operation requires that AWRE and ARRE are enabled—this is the default setting  
from the Seagate factory.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
38  
             
9.6  
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 drive, transfers  
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 LBA’s 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.  
9.6.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 and WRTPROTECT 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 WRTPROTECT 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 of  
Protection Information (e.g. 0xFFFFFFFF) 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.  
9.6.2  
Setting and determining the current Type Level  
A drive is initialized to a type of PI by using the FORMAT UNIT command on a PI capable drive. 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. A drive can only be formatted  
to a single PI Type. It can be changed at anytime to a new Type but requires a FORMAT UNIT command 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 UNIT CDB command: 04 90 00 00 00 00, parameter data: 00 A0 00 00  
Type 2 PI FORMAT UNIT CDB command: 04 D0 00 00 00 00, parameter data: 00 A0 00 00  
9.6.3  
Identifying a Protection Information drive  
The Standard INQUIRY data provides a bit to indicate if PI is support by the drive. Vital 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 Commands - 3 (SBC-3) Draft Standard documentation.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
39  
                         
10.0 INSTALLATION  
Pulsar.2 drive installation is a plug-and-play process. There are no jumpers 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 the drive must be mounted. Mount the drive to the  
carrier or 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. The drive can be mounted in any orientation.  
Note. SAS drives are designed to be attached to the host system without I/O or power cables. If the intent is 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 the host system using the instructions provided by the host system. This connects the  
drive directly to the system’s SAS connector. The SAS connector is normally located on a SAS backpanel. See Section 11.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. Reformatting the drive is only required if the application  
requires a different logical block size.  
Figure 15.  
Physical interface  
10.1  
DRIVE ORIENTATION  
The drive may be mounted in any orientation. All drive performance characterizations, however, have been done with the drive in  
horizontal (level) and vertical (drive on its side) orientations, which are the two preferred mounting orientations.  
10.2  
COOLING  
Cabinet cooling must be designed by the customer so that the temperature of the drive will not exceed temperature conditions specified in  
The rack, cabinet, or drawer environment for the drive must provide heat removal from the assembly. The system designer should confirm  
Forced air flow may be required to keep temperatures at or below the temperatures specified in Section 6.5.1 in which case the drive  
should be oriented, or air flow directed, so that the least amount of air flow resistance is created while providing air flow. 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.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
40  
                           
more fans, either forcing or drawing air as shown in the illustrations. Conduction, convection, or other forced air-flow patterns are  
Abo e nit  
nder nit  
Note Air lo s in the direction sho n (bac to ront)  
or in re erse direction ( ront to bac )  
Abo e nit  
nder nit  
Note Air lo s in the direction sho n or  
in re erse direction (side to side)  
Figure 16.  
Air flow  
Note. Image may not represent actual product, for reference only.  
10.3 DRIVE MOUNTING  
Mount the drive using the bottom or side mounting holes. If mounting the drive using the bottom holes, ensure 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 following 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.  
10.4  
GROUNDING  
Signal ground (PCBA) and case 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 drive with no electrically isolating shock mounts. If it is desired for the system chassis to  
not be connected to the drive 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 designers 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.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
41  
                               
11.0 INTERFACE REQUIREMENTS  
This section partially describes the interface requirements as implemented on Pulsar.2 drives. Additional information is provided in the SAS  
Interface Manual (part number 100293071).  
11.1  
SAS FEATURES  
This section lists the SAS-specific features supported by Pulsar.2 drives.  
11.1.1 Task management functions  
Table 14 SAS task management functions supported  
TASK NAME  
SUPPORTED  
Yes  
Abort Task  
Abort task set  
Clear ACA  
Yes  
Yes  
Clear task set  
I_T Nexus Reset  
Logical Unit Reset  
Query Task  
Yes  
Yes  
Yes  
Yes  
Query Task Set  
Query Asynchronous Event  
Yes  
Yes  
11.1.2 Task management responses  
Table 15 Task management response codes  
FUNCTION NAME  
Function complete  
Invalid frame  
RESPONSE CODE  
00  
02  
04  
05  
08  
09  
Function not supported  
Function failed  
Function succeeded  
Invalid logical unit  
11.2  
DUAL PORT SUPPORT  
Pulsar.2 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 Pulsar.2 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.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
42  
                                     
11.3  
SCSI COMMANDS SUPPORTED  
Table 16 lists the SCSI commands supported by Pulsar.2 drives.  
Table 16 Supported commands  
COMMAND NAME  
COMMAND CODE  
SUPPORTED  
CHANGE DEFINITION  
FORMAT UNIT [1]  
40h  
04h  
N
Y
N
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
N
N
N
Y
N
Y
N
Y
Y
Y
N
N
Y
Y
DPRY bit supported  
DCRT bit supported  
STPF bit supported  
IP bit supported  
DSP bit supported  
IMMED bit supported  
VS (vendor specific)  
INQUIRY  
12h  
Block Limits page (B0h)  
Block Device Characteristics page (B1h)  
Date Code page (C1h)  
Device Behavior page (C3h)  
Device Identification page (83h)  
Extended Inquiry Data page (86h)  
Firmware Numbers page (C0h)  
Jumper Settings page (C2h)  
Power Conditions page (8Ah)  
Supported Vital Product Data page (00h)  
Thin Provisioning page (B2h)  
Unit Serial Number page (80h)  
Vendor Unique page (D1h)  
Vendor Unique page (D2h)  
LOG SELECT  
4Ch  
PCR bit  
DU bit  
DS bit  
TSD bit  
ETC bit  
TMC bit  
LP bit  
LOG SENSE  
4Dh  
Application Client Log page (0Fh)  
Background Scan Results log page (15h)  
Buffer Over-run/Under-run page (01h)  
Cache Statistics page (37h)  
Factory Log page (3Eh)  
Information Exceptions Log page (2Fh)  
Last n Deferred Errors or Asynchronous Events page (0Bh)  
Last n Error Events page (07h)  
Non-medium Error page (06h)  
Pages Supported list (00h)  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
43  
   
Table 16 Supported commands  
COMMAND NAME  
COMMAND CODE  
SUPPORTED  
Protocol-Specific Port log pages (18h)  
Read Error Counter page (03h)  
Read Reverse Error Counter page (04h)  
Self-test Results page (10h)  
Solid State Media log page (11h)  
Start-stop Cycle Counter page (0Eh)  
Temperature page (0Dh)  
Y
Y
N
Y
Y
Y
Y
Vendor Unique page (3Ch)  
Verify Error Counter page (05h)  
Write error counter page (02h)  
MODE SELECT (6) (same pages as MODE SENSE (6))  
MODE SELECT (10) (same pages as MODE SENSE (6))  
MODE SENSE (6)  
Y
Y
Y
15h  
55h  
1Ah  
Y
Caching Parameters page (08h)  
Control Mode page (0Ah)  
Y
Y
Disconnect/Reconnect (02h)  
Error Recovery page (01h)  
Format page (03h)  
Y
Y
N
Information Exceptions Control page (1Ch)  
Background Scan mode subpage (1Ch/01h)  
Notch and Partition Page (0Ch)  
Protocol-Specific LUN mode page (18h)  
Protocol-Specific Port page (19h)  
Power Condition page (1Ah)  
Rigid Disc Drive Geometry page (04h)  
Unit Attention page (00h)  
Y
Y
N
Y
Y
Y
N
Y
Verify Error Recovery page (07h)  
Xor Control page (10h)  
Y
N
MODE SENSE (10) (same pages as MODE SENSE (6))  
PERSISTENT RESERVE IN  
PERSISTENT RESERVE OUT  
PRE-FETCH (10)  
5Ah  
5Eh  
5Fh  
34h  
08h  
28h  
Y
Y
Y
N
READ (6)  
Y
READ (10)  
Y
DPO bit supported  
Y
FUA bit supported  
Y
READ (12)  
A8h  
N
READ (16)  
88h  
Y
READ (32)  
7Fh/0009h  
3Ch  
Y
READ BUFFER (modes 0, 2, 3, Ah And Bh supported)  
READ CAPACITY (10)  
Y (non-SED drives only)  
25h  
Y
READ CAPACITY (16)  
9Eh/10h  
37h  
Y
READ DEFECT DATA (10)  
READ DEFECT DATA (12)  
READ LONG (10)  
Y
B7h  
Y
3Eh  
Y (non-SED drives only)  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
44  
Table 16 Supported commands  
COMMAND NAME  
COMMAND CODE  
SUPPORTED  
READ LONG (16)  
REASSIGN BLOCKS  
RECEIVE DIAGNOSTIC RESULTS  
Supported Diagnostics pages (00h)  
Translate page (40h)  
RELEASE (6)  
9Eh/11h  
07h  
Y (non-SED drives only)  
Y
1Ch  
Y
Y
N
17h  
57h  
A0h  
03h  
Y
RELEASE (10)  
Y
REPORT LUNS  
Y
REQUEST SENSE  
Actual Retry Count bytes  
Extended Sense  
Field Pointer bytes  
RESERVE (6)  
Y
Y
Y
Y
16h  
56h  
Y
3rd Party Reserve  
Extent Reservation  
RESERVE (10)  
Y
N
Y
3rd Party Reserve  
Extent Reservation  
REZERO UNIT  
Y
N
01h  
48h  
Y
SANITIZE  
Y (SED models only)  
Overwrite  
N
Block Erase  
N
Cryptographic Erase  
SECURITY PROTOCOL IN  
SECURITY PROTOCOL OUT  
SEEK (6)  
---/03h  
A2h  
Y (SED models only)  
Y (SED models only)  
B5h  
Y (SED models only)  
0Bh  
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
N
SEEK (10)  
2Bh  
SEND DIAGNOSTICS  
Supported Diagnostics pages (00h)  
Translate page (40h)  
START UNIT/STOP UNIT  
SYNCHRONIZE CACHE  
SYNCHRONIZE CACHE (16)  
TEST UNIT READY  
UNMAP  
1Dh  
1Bh  
35h  
91h  
00h  
42H  
2Fh  
VERIFY (10)  
BYTCHK bit  
VERIFY (12)  
AFh  
VERIFY (16)  
AFh  
VERIFY (32)  
7Fh/000Ah  
0Ah  
WRITE (6)  
WRITE (10)  
2Ah  
DPO bit  
FUA bit  
WRITE (12)  
AAh  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
45  
Table 16 Supported commands  
COMMAND NAME  
COMMAND CODE  
SUPPORTED  
WRITE (16)  
8Ah  
Y
WRITE (32)  
7Fh/000Bh  
2Eh  
Y
WRITE AND VERIFY (10)  
DPO bit  
Y
Y
WRITE AND VERIFY (12)  
WRITE AND VERIFY (16)  
WRITE AND VERIFY (32)  
WRITE BUFFER (modes 0, 2, supported)  
WRITE BUFFER  
AEh  
N
8Eh  
Y
7Fh/000Ch  
3Bh  
Y
Y (non-SED drives only)  
3Bh  
Firmware Download option (modes 4, 5, 7)  
WRITE LONG (10)  
WRITE LONG (16)  
WRITE SAME (10)  
PBdata  
Y (non-SED drives only)  
Y (SED drives only)  
3Fh  
Y
Y
Y
N
N
Y
Y
N
N
N
9Fh/11h  
41h  
LBdata  
WRITE SAME (16)  
WRITE SAME (32)  
XDREAD  
93h  
7Fh/000Dh  
52h  
XDWRITE  
50h  
XPWRITE  
51h  
[1] Pulsar.2 drives can format to 512, 520, 524, 528, 4096, 4160, 4192 and 4224 bytes per logical block.  
[2] Warning. Power loss during a firmware upgrade can result in firmware corruption. This usually makes the drive inoperable.  
[3] Reference MODE SENSE command 1Ah for mode pages supported.  
[4] Y = Yes. Command is supported.  
N = No. Command is not supported.  
A = Support is available on special request.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
46  
     
11.3.1 INQUIRY data  
Table 17 Pulsar.2 INQUIRY data  
BYTES  
DATA (HEX)  
0-15  
00  
[53  
R#  
00  
00  
00  
00  
00  
54  
R#  
00  
00  
00  
43  
xx** 12  
8B  
30  
S#  
00  
00  
00  
79  
53  
74  
01  
46  
S#  
00  
00  
00  
72  
65  
73  
PP  
4D  
S#  
00  
00  
00  
69  
61  
20  
02  
30  
S#  
00  
00  
00  
67  
67  
72  
53  
30  
S#  
00  
00  
00  
68  
61  
65  
45  
30  
S#  
00  
00  
00  
74  
74  
73  
41  
32]  
S#  
00  
00  
00  
20  
65  
65  
47  
20  
S#  
00  
00  
00  
28  
20  
72  
41  
20  
00  
00  
00  
00  
63  
41  
76  
54  
20  
00  
00  
00  
00  
29  
6C  
65  
45  
20  
00  
00  
00  
00  
20  
6C  
64  
20  
20  
00  
00  
00  
00  
Vendor ID  
Product ID  
16-31  
32-47  
48-63  
64-79  
80-95  
96-111  
112-127  
128-143  
38  
R#  
00  
00  
00  
6F  
30  
R#  
00  
00  
00  
70  
20  
68  
32* *Copyright  
30* 31* 31*  
72 69 67  
20  
20  
notice  
*
**  
Copyright year (changes with actual year).  
SCSI Revision support. See the appropriate SPC release documentation for definitions.  
PP 10 = INQUIRY data for an INQUIRY command received on Port A.  
30 = INQUIRY data for an INQUIRY command received on Port B.  
R# Four ASCII digits representing the last four digits of the product firmware release number.  
S# Eight ASCII digits representing the eight digits of the product serial number.  
[ ]  
Bytes 16 through 26 reflect model of drive. The table above shows the hex values for Model ST800FM0002.  
Refer to the values below for the values of bytes 16 through 26 for a particular model:  
ST800FM0012  
ST800FM0022  
ST800FM0032  
ST800FM0042  
ST400FM0002  
ST400FM0042  
ST200FM0002  
ST200FM0042  
ST100FM0002  
ST100FM0052  
53 54 38 30 30 46 4D 30 30 31 32  
53 54 38 30 30 46 4D 30 30 32 32  
53 54 38 30 30 46 4D 30 30 33 32  
53 54 38 30 30 46 4D 30 30 34 32  
53 54 34 30 30 46 4D 30 30 30 32  
53 54 34 30 30 46 4D 30 30 34 32  
53 54 32 30 30 46 4D 30 30 30 32  
53 54 32 30 30 46 4D 30 30 34 32  
53 54 31 30 30 46 4D 30 30 30 32  
53 54 31 30 30 46 4D 30 30 35 32  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
47  
     
11.3.2 MODE SENSE data  
The MODE SENSE command provides a way for the drive to report its operating parameters to the initiator. The drive maintains four sets  
of mode parameters:  
1. Default values  
Default values are hard-coded in the drive firmware stored in flash E-PROM (nonvolatile memory) on the drive’s PCB. These default  
values can be changed only by downloading a complete set of new firmware into the flash E-PROM. An initiator can request and  
receive from the drive a list of default values and use those in a MODE SELECT command to set up new current and saved values,  
where the values are changeable.  
2. Saved values  
Saved values are stored on the drive’s media using a MODE SELECT command. Only parameter values that are allowed to be  
changed can be changed by this method. Parameters in the saved values list that are not changeable by the MODE SELECT com-  
mand get their values from default values storage.  
When power is applied to the drive, it takes saved values from the media and stores them as current values in volatile memory. It is not  
possible to change the current values (or the saved values) with a MODE SELECT command before the drive is “ready.” An attempt to  
do so results in a “Check Condition” status.  
On drives requiring unique saved values, the required unique saved values are stored into the saved values storage location on the  
media prior to shipping the drive. Some drives may have unique firmware with unique default values also.  
On standard OEM drives, the saved values are taken from the default values list and stored into the saved values storage location on  
the media prior to shipping.  
3. Current values  
Current values are volatile values being used by the drive to control its operation. A MODE SELECT command can be used to change  
the values identified as changeable values. Originally, current values are installed from saved or default values after a power on reset,  
hard reset, or Bus Device Reset message.  
4. Changeable values  
Changeable values form a bit mask, stored in nonvolatile memory, that dictates which of the current values and saved values can be  
changed by a MODE SELECT command. A one (1) indicates the value can be changed. A zero (0) indicates the value is not change-  
able. For example, in Table 19, refer to Mode page 81, in the row entitled “CHG.” These are hex numbers representing the changeable  
values for Mode page 81. Note in columns 5 and 6 (bytes 04 and 05), there is 00h which indicates that in bytes 04 and 05 none of the  
bits are changeable. Note also that bytes 06, 07, 09, 10, and 11 are not changeable, because those fields are all zeros. In byte 02, hex  
value FF equates to the binary pattern 11111111. If there is a zero in any bit position in the field, it means that bit is not changeable.  
Since all of the bits in byte 02 are ones, all of these bits are changeable.  
The changeable values list can only be changed by downloading new firmware.  
Note. Because there are often several different versions of drive control firmware in the total population of drives in the field, the  
MODE SENSE values given in the following tables may not exactly match those of some drives.  
The following tables list the values of the data bytes returned by the drive in response to the MODE SENSE command pages for SCSI  
implementation (see the SAS Interface Manual).  
DEF = Default value. Standard OEM drives are shipped configured this way.  
CHG = Changeable bits; indicates if default value is changeable.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
48  
   
Table 18 MODE SENSE data for 800GB drives  
MODE DATA HEADER:  
01 3e 00 10 01 00 00 10  
BLOCK DESCRIPTOR:  
00 00 00 00 5d 26 ce b0 00 00 00 00 00 00 02 00  
MODE PAGES:  
DEF 81 0a c0 01 5a 00 00 00 0b 00 ff ff  
CHG 81 0a 38 00 00 00 00 00 ff 00 00 00  
DEF 82 0e 00 00 00 00 00 00 00 00 01 3a 00 00 00 00  
CHG 82 0e 00 00 00 00 00 00 00 00 ff ff 00 00 00 00  
DEF 87 0a 00 01 5a 00 00 00 00 00 ff ff  
CHG 87 0a 08 00 00 00 00 00 00 00 ff ff  
DEF 88 12 14 00 ff ff 00 00 ff ff ff ff 80 20 00 00 00 00 00 00  
CHG 88 12 a5 00 00 00 ff ff ff ff 00 00 21 00 00 00 00 00 00 00  
DEF 8a 0a 00 00 00 80 00 00 00 00 7f ff  
CHG 8a 0a 07 f0 00 00 00 00 00 00 00 00  
DEF 18 06 06 00 00 00 00 00  
CHG 18 06 00 00 00 00 00 00  
DEF 99 0e 46 00 07 d0 00 00 00 00 00 00 00 00 00 00  
CHG 99 0e 50 00 ff ff ff ff ff ff 00 00 00 00 00 00  
DEF 59 01 00 64 00 06 00 02 00 00 00 00 10 29 0e 00 50 00 c5 00 00 1b 9a 81 50 06 05 b0 00 00 fe e4 04 00 00 00 00 00 00 00  
88 aa 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 14 1a 0e 00 50 00 c5 00 00 1b 9a 82 50 06 05 b0 01 49 c2  
60 02 00 00 00 00 00 00 00 88 aa 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
CHG 59 01 00 64 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
00 f0 f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
00 00 00 00 00 00 00 00 00 f0 f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
DEF 59 03 00 2c 00 06 00 02 00 00 00 10 80 ac 00 01 00 ac 00 01 80 00 00 00 00 00 09 00 00 01 00 10 80 ac 00 01 80 ac 00 01  
80 bc 00 00 00 00 1a 00  
CHG 59 03 00 2c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
00 00 00 00 00 00 00 00  
DEF 9a 0a 00 02 00 00 00 05 00 00 8c a0  
CHG 9a 0a 00 02 ff ff ff ff 00 00 00 00  
DEF 9c 0a 10 00 00 00 00 00 00 00 00 01  
CHG 9c 0a 9d 0f ff ff ff ff ff ff ff ff  
DEF dc 01 00 0c 01 00 01 50 00 00 00 00 00 00 00 00  
CHG dc 01 00 0c 01 00 ff ff 00 00 00 00 00 00 00 00  
DEF 80 06 00 80 00 00 00 00  
CHG 80 06 b7 80 00 00 00 00  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
49  
 
Table 19 MODE SENSE data for 400GB drives  
MODE DATA HEADER:  
01 3e 00 10 01 00 00 10  
BLOCK DESCRIPTOR:  
00 00 00 00 2e 93 90 b0 00 00 00 00 00 00 02 00  
MODE PAGES:  
DEF 81 0a c0 01 5a 00 00 00 0b 00 ff ff  
CHG 81 0a 38 00 00 00 00 00 ff 00 00 00  
DEF 82 0e 00 00 00 00 00 00 00 00 01 3a 00 00 00 00  
CHG 82 0e 00 00 00 00 00 00 00 00 ff ff 00 00 00 00  
DEF 87 0a 00 01 5a 00 00 00 00 00 ff ff  
CHG 87 0a 08 00 00 00 00 00 00 00 ff ff  
DEF 88 12 14 00 ff ff 00 00 ff ff ff ff 80 20 00 00 00 00 00 00  
CHG 88 12 a5 00 00 00 ff ff ff ff 00 00 21 00 00 00 00 00 00 00  
DEF 8a 0a 00 00 00 80 00 00 00 00 7f ff  
CHG 8a 0a 07 f0 00 00 00 00 00 00 00 00  
DEF 18 06 06 00 00 00 00 00  
CHG 18 06 00 00 00 00 00 00  
DEF 99 0e 46 00 07 d0 00 00 00 00 00 00 00 00 00 00  
CHG 99 0e 50 00 ff ff ff ff ff ff 00 00 00 00 00 00  
DEF 59 01 00 64 00 06 00 02 00 00 00 00 10 09 0e 00 50 00 c5 00 00 1b 32 89 50 06 05 b0 00 00 fe e4 04 00 00 00 00 00 00 00  
88 aa 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 14 1a 0e 00 50 00 c5 00 00 1b 32 8a 50 06 05 b0 01 49 c2  
60 02 00 00 00 00 00 00 00 88 aa 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
CHG 59 01 00 64 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
00 f0 f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
00 00 00 00 00 00 00 00 00 f0 f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
DEF 59 03 00 2c 00 06 00 02 00 00 00 10 80 ac 00 01 80 ac 00 01 00 00 00 00 00 00 09 00 00 01 00 10 80 ac 00 01 80 ac 00 01  
80 bc 00 00 00 00 1a 00  
CHG 59 03 00 2c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
00 00 00 00 00 00 00 00  
DEF 9a 0a 00 02 00 00 00 05 00 00 8c a0  
CHG 9a 0a 00 02 ff ff ff ff 00 00 00 00  
DEF 9c 0a 10 00 00 00 00 00 00 00 00 01  
CHG 9c 0a 9d 0f ff ff ff ff ff ff ff ff  
DEF dc 01 00 0c 01 00 01 50 00 00 00 00 00 00 00 00  
CHG dc 01 00 0c 01 00 ff ff 00 00 00 00 00 00 00 00  
DEF 80 06 00 80 00 00 00 00  
CHG 80 06 b7 80 00 00 00 00  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
50  
   
Table 20 MODE SENSE data for 200GB drives  
MODE DATA HEADER:  
01 3e 00 10 01 00 00 10  
BLOCK DESCRIPTOR:  
00 00 00 00 17 49 f1 b0 00 00 00 00 00 00 02 00  
MODE PAGES:  
DEF 81 0a c0 01 5a 00 00 00 0b 00 ff ff  
CHG 81 0a 38 00 00 00 00 00 ff 00 00 00  
DEF 82 0e 00 00 00 00 00 00 00 00 01 3a 00 00 00 00  
CHG 82 0e 00 00 00 00 00 00 00 00 ff ff 00 00 00 00  
DEF 87 0a 00 01 5a 00 00 00 00 00 ff ff  
CHG 87 0a 08 00 00 00 00 00 00 00 ff ff  
DEF 88 12 14 00 ff ff 00 00 ff ff ff ff 80 20 00 00 00 00 00 00  
CHG 88 12 a5 00 00 00 ff ff ff ff 00 00 21 00 00 00 00 00 00 00  
DEF 8a 0a 00 00 00 80 00 00 00 00 7f ff  
CHG 8a 0a 07 f0 00 00 00 00 00 00 00 00  
DEF 18 06 06 00 00 00 00 00  
CHG 18 06 00 00 00 00 00 00  
DEF 99 0e 46 00 07 d0 00 00 00 00 00 00 00 00 00 00  
CHG 99 0e 50 00 ff ff ff ff ff ff 00 00 00 00 00 00  
DEF 59 01 00 64 00 06 00 02 00 00 00 00 10 09 0e 00 50 00 c5 00 00 1b 3f 1a 50 06 05 b0 00 00 fe e4 05 00 00 00 00 00 00 00  
88 aa 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 14 1a 0e 00 50 00 c5 00 00 1b 3f a2 50 06 05 b0 01 49 c2 60  
00 00 00 00 00 00 00 00 88 aa 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
CHG 59 01 00 64 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
f0 f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
00 00 00 00 00 00 00 00 f0 f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
DEF 59 03 00 2c 00 06 00 02 00 00 00 10 80 ac 00 01 80 ac 00 01 00 00 00 00 00 00 09 00 00 01 00 10 80 ac 00 01 80 ac 00 01  
80 bc 00 00 00 00 1a 00  
CHG 59 03 00 2c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
00 00 00 00 00 00 00 00  
DEF 9a 0a 00 02 00 00 00 05 00 00 8c a0  
CHG 9a 0a 00 02 ff ff ff ff 00 00 00 00  
DEF 9c 0a 10 00 00 00 00 00 00 00 00 01  
CHG 9c 0a 9d 0f ff ff ff ff ff ff ff ff  
DEF dc 01 00 0c 01 00 01 50 00 00 00 00 00 00 00 00  
CHG dc 01 00 0c 01 00 ff ff 00 00 00 00 00 00 00 00  
DEF 80 06 00 80 00 00 00 00  
CHG 80 06 b7 80 00 00 00 00  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
51  
   
Table 21 MODE SENSE values for 100GB drives  
MODE DATA HEADER:  
01 3e 00 10 01 00 00 10  
BLOCK DESCRIPTOR:  
00 00 00 00 0b a5 22 30 00 00 00 00 00 00 02 00  
MODE PAGES:  
DEF 81 0a 00 01 5a 00 00 00 0b 00 ff ff  
CHG 81 0a 08 00 00 00 00 00 ff 00 00 00  
DEF 82 0e 00 00 00 00 00 00 00 00 01 3a 00 00 00 00  
CHG 82 0e 00 00 00 00 00 00 00 00 ff ff 00 00 00 00  
DEF 87 0a c0 01 5a 00 00 00 00 00 ff ff  
CHG 87 0a 38 00 00 00 00 00 00 00 ff ff  
DEF 88 12 14 00 ff ff 00 00 ff ff ff ff 80 20 00 00 00 00 00 00  
CHG 88 12 a5 00 00 00 ff ff ff ff 00 00 21 00 00 00 00 00 00 00  
DEF 8a 0a 00 00 00 80 00 00 00 00 7f ff  
CHG 8a 0a 07 f0 00 00 00 00 00 00 00 00  
DEF 18 06 06 00 00 00 00 00  
CHG 18 06 00 00 00 00 00 00  
DEF 99 0e 46 00 07 d0 00 00 00 00 00 00 00 00 00 00  
CHG 99 0e 50 00 ff ff ff ff ff ff 00 00 00 00 00 00  
DEF 59 01 00 64 00 06 00 02 00 00 00 00 10 29 0e 00 50 00 c5 00 00 1b 8e 91 50 06 05 b0 00 00 fe e4 05 00 00 00 00 00 00 00  
88 aa 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 14 0a 0e 00 50 00 c5 00 00 1b 8e 92 50 06 05 b0 01 49 c2 60  
00 00 00 00 00 00 00 00 88 aa 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
CHG 59 01 00 64 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
f0 f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
00 00 00 00 00 00 00 00 f0 f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
DEF 59 03 00 2c 00 06 00 02 00 00 00 10 80 ac 00 01 80 ac 00 01 00 00 00 00 00 00 09 00 00 01 00 10 80 ac 00 01 80 ac 00 01  
80 bc 00 00 00 00 1a 00  
CHG 59 03 00 2c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  
00 00 00 00 00 00 00 00  
DEF 9a 0a 00 02 00 00 00 05 00 00 8c a0  
CHG 9a 0a 00 02 ff ff ff ff 00 00 00 00  
DEF 9c 0a 10 00 00 00 00 00 00 00 00 01  
CHG 9c 0a 9d 0f ff ff ff ff ff ff ff ff  
DEF dc 01 00 0c 01 00 01 50 00 00 00 00 00 00 00 00  
CHG dc 01 00 0c 01 00 ff ff 00 00 00 00 00 00 00 00  
DEF 80 06 00 80 00 00 00 00  
CHG 80 06 b7 80 00 00 00 00  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
52  
 
11.4  
MISCELLANEOUS OPERATING FEATURES AND CONDITIONS  
Table 22 lists various features and conditions. A “Y” in the support column indicates the feature or condition is supported. An “N” in the  
support column indicates the feature or condition is not supported.  
Table 22 Miscellaneous features  
SUPPORTED  
FEATURE OR CONDITION  
N
N
Y
N
Y
Y
Y
N
Automatic contingent allegiance  
Asynchronous event notification  
Segmented caching  
Zero latency read  
Queue tagging (up to 128 queue tags supported)  
Deferred error handling  
Parameter rounding (controlled by Round bit in MODE SELECT page 0)  
Reporting actual retry count in Extended Sense bytes 15, 16, and 17  
Table 23 Miscellaneous status  
SUPPORTED  
STATUS  
Y
Y
Y
Y
Y
Y
N
N
N
Good  
Check condition  
Condition met/good  
Busy  
Reservation conflict  
Task set full  
ACA active  
ACA active, faulted initiator  
Task Aborted  
11.4.1 SAS physical interface  
Details of the physical, electrical, and logical characteristics are provided within this section. The operational aspects of Seagate’s SAS  
drives are provided in the SAS Interface Manual.  
Figure 17.  
Physical interface  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
53  
                                             
0.80 (6X)  
5.92  
7.62  
4.65  
0.52 0.08 x 45  
2.00 (3X)  
0.45 0.03 (7X)  
0.10 M E  
5.08  
42.73 REF.  
41.13 0.15  
0.20B  
0.30 0.05 (2X)  
C
A
B
1.10  
4.00 0.08  
0.15D  
C OF DATUM D  
L
R0.30 0.08 (4X)  
A
0.30 0.05 (4X)  
B
C
SEE Detail1  
B
33.43 0.05  
15.875  
15.875  
1.27 (14X)  
1.27 (6X)  
0.84 0.05 (22X)  
5.08  
0.15B  
4.90 0.08  
0.35MIN  
P15  
S1  
P1  
S7  
C OF DATUM B  
L
Figure 18.  
SAS device plug dimensions  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
54  
 
Detail A  
6.10  
S14  
S8  
0.30 0.05 x 45 (5X)  
2.25 0.05  
0.40 0.05 X 45 (3X)  
4.85 0.05  
0.10B  
CORING ALLOWED  
IN THIS AREA.  
E
4.40 0.15  
R0.30 0.08  
45  
C
SEE Detail 2  
1.95 0.08  
A
0.35 0.05  
SECTION C - C  
3.90 0.15  
SECTION A - A  
CONTACT SURFACE FLUSH  
TO DATUM A 0.03  
0.08 0.05  
65  
1.90 0.08  
1.23 0.05  
0.08 0.05  
30  
Detail 2  
2.40 0.08  
0.10 A  
SECTION B - B  
D
Figure 19.  
SAS device plug dimensions (detail)  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
55  
 
11.4.2 Physical characteristics  
This section defines physical interface connector.  
11.4.3 Connector requirements  
Contact your preferred connector manufacturer for mating part information. Part numbers for SAS connectors will be provided in a future  
revision of this publication when production parts are available from major connector manufacturers.  
11.4.4 Electrical description  
SAS drives use the device connector for:  
• DC power  
• SAS interface  
• Activity LED  
This connector is designed to either plug directly into a backpanel or accept cables.  
11.4.5 Pin descriptions  
This section provides a pin-out of the SAS device and a description of the functions provided by the pins.  
Table 24 SAS pin descriptions  
PIN  
S1  
SIGNAL NAME  
Port A Ground  
+Port A_in  
SIGNAL TYPE  
PIN  
P1*  
P2*  
P3  
SIGNAL NAME  
NC (reserved 3.3Volts)  
NC (reserved 3.3Volts)  
NC (reserved 3.3Volts)  
Ground  
SIGNAL TYPE  
S2*  
S3*  
S4  
Diff. input pair  
-Port A_in  
Port A Ground  
-Port A_out  
P4  
S5*  
S6*  
S7  
Diff output pair  
P5  
Ground  
+Port A_out  
Port A Ground  
Port B Ground  
+Port B_in  
P6  
Ground  
P7  
5 Volts charge  
5 Volts  
S8  
P8*  
P9*  
P10  
P11*  
P12  
P13  
P14*  
P15*  
S9*  
S10*  
S11  
S12*  
S13*  
S14  
Diff. input pair  
Diff output pair  
5 Volts  
-Port B_in  
Ground  
Port A Ground  
-Port B_out  
Ready LED  
Ground  
Open collector out  
+Port B_out  
Port B Ground  
12 Volts charge  
12 Volts  
12 Volts  
* - Short pin to support hot plugging  
NC - No connection in the drive.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
56  
                           
11.4.6 SAS transmitters and receivers  
noise.  
Figure 20.  
SAS transmitters and receivers  
11.4.7 Power  
The drive receives power (+5 volts and +12 volts) through the SAS device connector.  
Three +12 volt pins provide power to the drive, 2 short and 1 long. The current return for the +12 volt power supply is through the common  
ground pins. The supply current and return current must be distributed as evenly as possible among the pins.  
Three +5 volt pins provide power to the drive, 2 short and 1 long. The current return for the +5 volt power supply is through the common  
ground pins. The supply current and return current must be distributed as evenly as possible among the pins.  
Current to the drive through the long power pins may be limited by the system to reduce inrush current to the drive during hot plugging.  
11.5  
SIGNAL CHARACTERISTICS  
name information.  
11.5.1 Ready LED Out  
Table 25 Ready LED Out conditions  
NORMAL COMMAND ACTIVITY  
LED STATUS  
0
1
Ready LED Meaning bit mode page 19h  
Drive stopped, not ready, and no activity  
Off  
On  
Off  
On  
Drive stopped, not ready, and activity  
(command executing)  
Drive started, ready, and no activity  
On  
Off  
Off  
On  
Drive started, ready, and activity  
(command executing)  
Drive transitioning from not-ready state to  
ready state or the reverse.  
Blinks steadily  
(50% on and 50% off, 0.5 seconds on and off for 0.5 seconds)  
FORMAT UNIT in progress,  
Toggles on/off  
The Ready LED Out signal is designed to pull down the cathode of an LED. The anode is attached to the proper +3.3 volt supply through  
an appropriate current limiting resistor. The LED and the current limiting resistor are external to the drive. See Table 26 for the output  
characteristics of the LED drive signals.  
Table 26 LED drive signal  
STATE  
TEST CONDITION  
OUTPUT VOLTAGE  
LED off, high  
LED on, low  
0 V VOH 3.6 V  
-100 μA < I < 100 μA  
OH  
I
= 15 mA  
0 VOL 0.225 V  
OL  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
57  
                                 
11.5.2 Differential signals  
The drive SAS differential signals comply with the intra-enclosure (internal connector) requirements of the SAS standard.  
Table 27 defines the general interface characteristics  
Table 27 General interface characteristics  
CHARACTERISTIC  
UNITS  
1.5GB/S  
3.0GB/S  
6.0GB/S  
Bit rate (nominal)  
Mbaud  
ps  
1,500  
666.6  
100  
3,000  
333.3  
100  
6,000  
166.6  
100  
Unit interval (UI)(nominal)  
Impedance (nominal, differential )  
Transmitter transients, maximum  
Receiver transients, maximum  
ohm  
V
1.2  
1.2  
1.2  
V
1.2  
1.2  
1.2  
11.6  
SAS-2 SPECIFICATION COMPLIANCE  
Seagate SAS-2 drives are entirely compatible with the latest SAS-2 Specification (T10/1760-D) Revision 16.  
The most important characteristic of the SAS-2 drive at 6Gb/s is that the receiver is capable of adapting the equalizer to optimize the  
receive margins. The SAS-2 drive has two types of equalizers:  
1. A Decision Feedback Equalizer (DFE) which utilizes the standard SAS-2 training pattern transmitted during the SNW-3 training gap.  
The DFE circuit can derive an optimal equalization characteristic to compensate for many of the receive losses in the system.  
2. A Feed Forward Equalizer (FFE) optimized to provide balanced receive margins over a range of channels bounded by the best and  
worst case channels as defined by the relevant ANSI standard.  
11.7  
ADDITIONAL INFORMATION  
Please contact your Seagate representative for SAS electrical details, if required.  
For more information about the Phy, Link, Transport, and Applications layers of the SAS interface, refer to the Seagate SAS Interface  
Manual, part number 100293071.  
For more information about the SCSI commands used by Seagate SAS drives, refer to the Seagate SCSI Commands Reference Manual,  
part number 100293068.  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
58  
                     
INDEX  
class B limit 3  
NUMERICS  
12 volt  
pins 57  
5 volt pins 57  
6 Gbps 58  
clear ACA function 42  
clear task set function 42  
CMVP 34  
commands supported 43  
condensation 29  
condition met/good status 53  
connector  
A
abort task set function 42  
AC coupling 57  
AC power requirements 19  
ACA active status 53  
ACA active, faulted initiator status 53  
access time  
average latency 10  
average typical 10  
page to page typical 10  
active LED Out signal 57  
Admin SP 35  
illustrated 56  
requirements 56  
cooling 40  
CRC  
error 13  
Cryptographic Erase 36  
Cryptographic erase 36  
Current profiles 24  
customer service 18  
D
AES-256 data encryption 35  
air cleanliness 31  
Data Bands 36  
data bands 35  
data block size  
air flow 40, 41  
illustrated 41  
modifing the 7  
air inlet 40  
Data encryption 35  
Data Encryption Key 35  
Data Retention 13, 14  
DATA Returned for Thin Provisioned LBA 9  
DC power 19, 56  
requirements 20  
Decision Feedback Equalizer 58  
decrypt 35  
default MSID password 35  
defects 37  
altitude 29  
ambient 29  
ambient temperature 19  
ANSI documents  
SCSI 5  
Serial Attached SCSI 5  
asynchronous event notification 53  
audible noise 3  
automatic contingent allegiance 53  
Auto-Reallocation 38  
average idle current 20, 21, 22, 23  
deferred error handling 53  
DEK 35  
description 6  
DFE 58  
B
Background Media Scan 38  
backpanel 56  
dimensions 32  
drive 31  
Band 0 36  
BandMasterX 35  
BMS 38  
drive characteristics 10  
drive failure 15  
Drive Locking 35  
drive mounting 32, 41  
drive select 56  
busy status 53  
dual port support 42  
C
cache control 12  
E
caching write data 12  
Canadian Department of Communications 3  
capacity  
unformatted 10  
case 41  
electrical  
description of connector 56  
signal characteristics 57  
specifications 19  
CBC 35  
CE Marking 4  
check condition status 53  
China RoHS directive 5  
Cipher Block Chaining 35  
electromagnetic compatibility 3  
electromagnetic susceptibility 31  
EMI requirements 3  
encryption engine 35  
encryption key 36  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
59  
INDEX  
Endurance 13  
Endurance Management 14  
environment 40  
guide 5  
interface  
commands supported 43  
error rate 13  
environmental  
limits 28  
errors 13  
requirements 13  
environmental control 31  
EraseMaster 35  
illustrated 53  
physical 53  
requirements 42  
error  
internal defects/errors 37  
internal drive characteristics 10  
management 37  
rates 13  
Error reported to Host 9  
errors 37  
European Union Restriction of Hazardous Substances 4  
J
jumpers 40  
L
F
LBPME bit 9  
LBPRZ bit 9  
Lifetime Endurance Management 14  
Locking SP 35  
LockOnReset 35  
FCC rules and regulations 3  
features 6  
interface 42  
Federal Information Processing Standard 34  
feed forward equalizer 58  
FFE 58  
Logical Block Provisioning 8  
logical block size 6  
FIPS 34  
firmware 6  
M
corruption 46  
maintenance 13  
Manufacturers Secure ID 35  
maximum delayed motor start 20, 21, 22, 23  
maximum start current 20, 21, 22, 23  
media description 7  
firmware download port 35  
Format command execution time 10  
function  
complete, code 00 42  
not supported, code 05 42  
reject, code 04 42  
miscellaneous feature support  
Asynchronous event notification 53  
Automatic contingent allegiance 53  
Deferred error handling 53  
Parameter rounding 53  
Queue tagging 53  
G
Garbage Collection 14  
Global Data Band 36  
Good status 53  
gradient 29  
ground shift noise 57  
grounding 41  
Reporting actual retry count 53  
Segmented caching 53  
Zero latency read 53  
miscellaneous status support  
ACA active 53  
H
heat removal 40  
heat source 40  
ACA active, faulted initiator 53  
Busy 53  
host equipment 41  
hot plugging the drive 15  
humidity 29  
Check condition 53  
Condition met/good 53  
Good 53  
humidity limits 28  
Reservation conflict 53  
Task set full 53  
miscorrected media data 13  
Mode sense  
data, table 48, 49, 50, 51  
mounting 41  
holes 41  
orientations 40  
mounting configuration 32  
I
Identifying a PI drive 39  
Idle mode 19  
Idle mode power 19  
input voltage 19  
inquiry data 47  
installation 40  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
60  
INDEX  
mounting configuration dimensions 32, 33  
MSID 35  
PowerChoice 19  
PowerCycle 35  
MTBF 13, 15  
preventive maintenance 13  
PROT_EN bit 9  
protection information 39  
protection of data at rest 35  
N
NIST website 34  
noise  
Q
audible 3  
noise immunity 24  
non-operating 29, 30, 31  
temperature 29  
non-operating vibration 31  
NVLAP 34  
queue tagging 53  
R
radio interference regulations 3  
Random number generator 35  
read error rates 13, 37  
ReadLockEnabled 35  
receivers 57  
O
office environment 31  
operating 29, 30, 31  
option selection 56  
options 8  
recommended mounting 30  
reference  
documents 5  
out-of-plane distortion 41  
relative humidity 29  
reliability 7  
specifications 13  
P
reliability and service 15  
repair and return information 18  
reporting actual retry count 53  
reservation conflict status 53  
resonance 30  
return information 18  
RevertSP 36  
RNG 35  
packaged 30  
parameter rounding 53  
password 35  
passwords 35  
PCBA 41  
peak operating current 20, 21, 22, 23  
Peak operating mode 19  
peak-to-peak measurements 24  
Performance 11  
RoHS 4, 5  
performance characteristics 10  
detailed 10  
S
performance highlights 7  
physical damage 31  
physical interface 53  
physical specifications 19  
PI Check Performed 9  
PI Check Requested 9  
PI level - Type 0 39  
PI level - Type I 39  
PI level - Type II 39  
PI level - Type III 39  
PI Levels 39  
safety 3  
Sanitize 36  
sanitize feature set 36  
SAS  
interface 56  
physical interface 53  
task management functions 42  
SAS documents 5  
SAS Interface Manual 3, 5  
SAS-2 Specification 58  
SCSI interface  
PI Returned for Thin Provisioned LBA 9  
PI Setting 9  
pin descriptions 56  
power 57  
commands supported 43  
Seagate Technology Support Services 1  
Secure ID 35  
Security Protocol In 35  
Security Protocol Out 35  
security providers 35  
segmented caching 53  
self-encrypting drives 35  
dissipation 27  
requirements, AC 19  
requirements, DC 20  
sequencing 24  
Power consumption 19  
power distribution 3  
Power specifications 19  
Self-Monitoring Analysis and Reporting Technology 7, 15  
Serial Attached SCSI (SAS) Interface Manual 2  
shielding 3  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
61  
INDEX  
shipping 18  
shipping container 29  
shock 30  
and vibration 30  
shock mount 41  
W
warranty 18  
Wear Leveling 14  
Write Amplification 14  
WriteLockEnabled 35  
SID 35  
signal  
Z
characteristics 57  
single-unit shipping pack kit 8  
SMART 7, 15  
SNW-3 training gap 58  
Specification 58  
zero latency read 53  
SSD Physical format address descriptor 37  
standards 3  
start/stop time 12  
Startup power 19  
surface stiffness  
allowable for non-flat surface 41  
system chassis 41  
T
Task Aborted 53  
task management functions 42  
Abort task set 42  
Clear ACA 42  
Clear task set 42  
terminate task 42  
task management response codes 42  
Function complete 00 42  
Function not supported 05 42  
Function reject 04 42  
task set full status 53  
TCG 35  
temperature 29, 40  
limits 28  
non-operating 29  
regulation 3  
See also cooling  
terminate task function 42  
Thin Provisioning 8  
transmitters 57  
transporting the drive 18  
Trusted Computing Group 35  
Type 1 PI format 39  
Type 2 PI format 39  
U
unformatted 7  
Unmap 9, 14  
Unrecoverable Errors 13  
unrecovered media data 13  
V
vibration 30, 31  
voltage 19  
PULSAR.2 SAS PRODUCT MANUAL, REV. C  
62  
Seagate Technology LLC  
AMERICAS Seagate Technology LLC 10200 South De Anza Boulevard, Cupertino, California 95014, United States, 408-658-1000  
ASIA/PACIFIC Seagate Singapore International Headquarters Pte. Ltd. 7000 Ang Mo Kio Avenue 5, Singapore 569877, 65-6485-3888  
EUROPE, MIDDLE EAST AND AFRICA Seagate Technology SAS 16-18 rue du Dôme, 92100 Boulogne-Billancourt, France, 33 1-4186 10 00  
Publication Number: 100666271, Rev. C  
March 2013  

Wadia Digital 270 User Manual
Sony Ericsson Serie T6xx User Manual
Sonic Alert msm85c154hvs User Manual
Seagate SAVVIO ST9450205SS User Manual
Seagate Pulsar2 ST200FM0042 User Manual
Samsung SPINPOINT MP2 HM200JJ User Manual
Samsung SGH E100A User Manual
Samsung SGH T819 User Manual
Omnimount WS 1 User Manual
Nokia 6300 User Manual