Seagate Barracuda ST31000640FC User Manual

Product Manual  
Barracuda ES.2 FC  
ST31000640FC  
100498209  
Rev. B  
June 2008  
Barracuda ES.2 FC Product Manual, Rev. B  
i
ii  
Barracuda ES.2 FC Product Manual, Rev. B  
Contents  
5.2.7  
Barracuda ES.2 FC Product Manual, Rev. B  
i
9.5.2  
ii  
Barracuda ES.2 FC Product Manual, Rev. B  
10.0  
Barracuda ES.2 FC Product Manual, Rev. B  
iii  
iv  
Barracuda ES.2 FC Product Manual, Rev. B  
1.0  
Scope  
This manual describes Seagate Technology® LLC, Barracuda ES.2 FC (Fibre Channel) disc drives.  
Barracuda ES.2 FC drives support the Fibre Channel Arbitrated Loop and SCSI Fibre Channel Protocol speci-  
fications to the extent described in this manual. The Fibre Channel Interface Manual (part number 100293070)  
describes the general Fibre Channel Arbitrated Loop characteristics of this and other Seagate Fibre Channel  
drives.  
Barracuda ES.2 FC Product Manual, Rev. B  
1
   
2
Barracuda ES.2 FC Product Manual, Rev. B  
2.0  
Standards, compliance and reference documents  
The drive has been developed as a system peripheral to the highest standards of design and construction. The  
drive depends upon its host equipment to provide adequate power and environment in order to achieve opti-  
mum 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 regu-  
lation. In particular, the drive must be securely mounted in order to guarantee the specified performance char-  
acteristics. Mounting by bottom holes must meet the requirements of Section 8.4.  
2.1  
Standards  
The Barracuda ES.2 FC family complies with Seagate standards as noted in the appropriate sections of this  
manual and the Seagate Fibre Channel Interface Manual, part number 100293070.  
The Barracuda ES.2 FC disc drive is a UL recognized component per UL1950, CSA certified to CAN/CSA  
C22.2 No. 950-95, and VDE or TUV certified to EN60950.  
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 Table 2, DC power requirements.  
Barracuda ES.2 FC Product Manual, Rev. B  
3
                                 
2.2  
Compliance  
2.2.1  
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 sys-  
tem represents the most popular characteristics for test platforms. The system configurations include:  
• Typical current use microprocessor  
• Keyboard  
• Monitor/display  
• Printer  
• External modem  
• 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 89/336/EEC of 03 May 1989 as amended by Directive 92/31/EEC of 28 April 1992 and  
Directive 93/68/EEC of 22 July 1993.  
Australian C-Tick  
If this model has the C-Tick Marking it complies with the Australia/New Zealand Standard AS/NZS3548 1995  
and meets the Electromagnetic Compatibility (EMC) Framework requirements of Australia’s Spectrum Man-  
agement Agency (SMA).  
Korean MIC  
If this model has the Korean Ministry of Information and Communication (MIC) logo, it complies with paragraph  
1 of Article 11 of the Electromagnetic Compatibility (EMC) Control Regulation and meets the Electromagnetic  
Compatibility Framework requirements of the Radio Research Laboratory (RRL) Ministry of Information and  
Communication Republic of Korea.  
This drive has been tested and complies with the Electromagnetic Interference/Electromagnetic Susceptibiliity  
(EMI/EMS) for Class B products.  
Taiwanese BSMI  
If this model has the Chinese National Standard (CNS) 13438 marking, it complies with Chinese National Stan-  
dard (CNS) 13438 and meets the Electromagnetic Compatibility (EMC) Framework requirements of the Tai-  
wanese Bureau of Standards, Metrology, and Inspection (BSMI).  
4
Barracuda ES.2 FC Product Manual, Rev. B  
   
2.3  
Reference documents  
SCSI Commands Reference Manual  
Fibre Channel Interface Manual  
Seagate part number: 100293068  
Seagate part number: 100293070  
ANSI Fibre Channel Documents  
X3.230-1994  
X3.297.1997  
X3.303.1998  
X3.272-1996  
FC Physical and Signaling Interface (FC-PH)  
FC-PH-2 Fibre Channel Physical and Signaling Interface-2  
FC-PH-3 Fibre Channel Physical and Signaling Interface-3  
FC Arbitrated Loop (FC-AL)  
X3.269-1996  
Fibre Channel Protocol for SCSI (FCP)  
NCITS TR-19  
NCITS TR-20  
SFF-8045  
Private Loop SCSI Direct Attach (PLDA)  
Fabric Loop Attachment (FC-FLA)  
Specification for 40-pin SCA-2 Connector with Parallel Selection  
Specification for 40-pin SCA-2 Connector with Bidirectional  
Enclosure Services Interface  
SFF-8067  
ANSI Small Computer System Interface (SCSI) Documents  
X3.131-1994  
(SCSI-2)  
X3.270-1996  
NCITS 305-199X  
(SCSI-3) Architecture Model  
(SCSI-3) Enclosure Services  
Specification for Acoustic Test Requirement and Procedures  
Seagate part number: 30553-001  
Package Test Specification  
Package Test Specification  
Seagate P/N 30190-001 (under 100 lb.)  
Seagate P/N 30191-001 (over 100 lb.)  
In case of conflict between this document and any referenced document, this document takes precedence.  
Barracuda ES.2 FC Product Manual, Rev. B  
5
               
6
Barracuda ES.2 FC Product Manual, Rev. B  
3.0  
General description  
Barracuda ES.2 FC drives provide high performance, high capacity data storage for a variety of systems  
including engineering workstations, network servers, mainframes, and supercomputers. Barracuda ES.2 FC  
drives support 4-Gbit Fibre Channel which can transfer data at up to 800 Mbytes per second and 1600 Mbytes  
per second in dual-loop configurations.  
Barracuda ES.2 FC drives support the Fibre Channel Arbitrated Loop (FC-AL) and SCSI Fibre Channel Proto-  
col as described in the ANSI specifications, this document, and the Fibre Channel Interface Manual which  
describes the general interface characteristics of this drive. Barracuda ES.2 FC drives are classified as intelli-  
gent peripherals and provide level 2 conformance (highest level) with the ANSI SCSI-1 standard.  
Note. Never disassemble the HDA and do not attempt to service items in the sealed enclosure (heads,  
media, actuator, etc.) as this requires special facilities. The drive does not contain user-replaceable  
parts. Opening the HDA for any reason voids your warranty.  
Cheetah drives use a dedicated landing zone at the innermost radius of the media to eliminate the possibility of  
destroying or degrading data by landing in the data zone. The heads automatically go to the landing zone when  
power is removed from the drive.  
An automatic shipping lock prevents potential damage to the heads and discs that results from movement dur-  
ing shipping and handling. The shipping lock disengages and the head load process begins when power is  
applied to the drive.  
The drives also use a high-performance actuator assembly with a low-inertia, balanced, patented, straight arm  
design that provides excellent performance with minimal power dissipation.  
Barracuda ES.2 FC Product Manual, Rev. B  
7
     
3.1  
Standard features  
Cheetah NS FC drives have the following standard features:  
• Perpendicular recording technology  
• 4-Gbit Fibre Channel interface  
• Integrated dual port FC-AL controller  
• Concurrent dual port transfers  
• Support for FC arbitrated loop, private and public attachment  
• Differential copper FC drivers and receivers  
• Downloadable firmware using the FC-AL interface  
• Supports SCSI enclosure services via interface connector  
• 128-deep task set (queue)  
• Supports up to 32 initiators  
• Drive selection ID and configuration options are set on the FC-AL backpanel or through interface com-  
mands. Jumpers are not used on the drive.  
• Supports SCSI Enclosure Services through the interface connector  
• Fibre Channel worldwide name uniquely identifies the drive and each port  
• User-selectable logical block size (512, 520, 524, or 528 bytes per logical block)  
• Selectable frame sizes from 256 to 2,112 bytes  
• Industry standard 3.5-inch low profile form factor dimensions  
• Programmable logical block reallocation scheme  
• Flawed logical block reallocation at format time  
• Programmable auto write and read reallocation  
• Reed-Solomon error correction code  
• Sealed head and disc assembly (HDA)  
• No preventive maintenance or adjustments required  
• Dedicated head landing zone  
• Embedded servo design  
• Automatic shipping lock  
• Self-diagnostics performed when power is applied to the drive  
• Zone bit recording (ZBR)  
• Vertical, horizontal, or top down mounting  
• Dynamic spindle brake  
• 16 Mbyte data buffer (see Section 4.5).  
• Reallocation of defects on command (Post Format)  
3.2  
Media description  
The media used on the drive has an aluminum substrate coated with a thin film magnetic material, overcoated  
with a proprietary protective layer for improved durability and environmental protection.  
8
Barracuda ES.2 FC Product Manual, Rev. B  
                                 
3.3  
Performance  
• Programmable multi-segmentable cache buffer  
• 800 Mbytes/sec maximum instantaneous data transfers  
• 7,200 RPM spindle. Average latency = 4.16 msec  
• Command queuing of up to 128 commands  
• Background processing of queue  
• Supports start and stop commands (spindle stops spinning)  
• Adaptive seek velocity; improved seek performance  
3.4  
Reliability  
• Annualized Failure Rate (AFR) of 0.73%  
• Mean Time Between Failures (MTBF) of 1,200,000 hours  
• Self-Monitoring Analysis and Reporting Technology (S.M.A.R.T.)  
• 5-year warranty  
3.5  
Formatted capacities  
Standard OEM models are formatted to 512 bytes per block. The sector size is selectable at format time. Users  
having the necessary equipment may modify the data block size before issuing a format command and obtain  
different formatted capacities than those listed.  
To provide a stable target capacity environment and at the same time provide users with flexibility if they  
choose, Seagate recommends product planning in one of two modes:  
1. Seagate designs specify capacity points at certain sector sizes that Seagate guarantees current and future  
products will meet. We recommend customers use this capacity in their project planning, as it ensures a  
stable operating point with backward and forward compatibility from generation to generation. The current  
guaranteed operating points for this product are:  
ST31000640FC  
Sector Size  
512  
Decimal  
1,953,525,168  
1,923,076,930  
1,882,972,562  
1,876,331,330  
520  
524  
528  
2. Seagate drives also may be used at the maximum available capacity at a given sector size, but the excess  
capacity above the guaranteed level will vary between 10K and 15K families and from generation to gener-  
ation, depending on how each sector size actually formats out for zone frequencies and splits over servo  
bursts. This added capacity potential may range from 0.1 to 1.3 percent above the guaranteed capacities  
listed above. Using the drives in this manner gives the absolute maximum capacity potential, but the user  
must determine if the extra capacity potential is useful, or whether their assurance of backward and for-  
ward compatibility takes precedence.  
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 Parameter List table in the SCSI Commands Reference Manual. Refer to the Parameter list block  
descriptor number of blocks field. A value of zero in the number of blocks field indicates that the drive shall not  
Barracuda ES.2 FC Product Manual, Rev. B  
9
                   
change the capacity it is currently formatted to have. A number in the number of blocks field that is less than  
the maximum number of LBAs changes the total drive capacity to the value in the block descriptor 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  
You may order the following items which are incorporated at the manufacturing facility during production or  
packaged before shipping. Some of the options available are (not an exhaustive list of possible options):  
• Other capacities can be ordered depending on sparing scheme and sector size requested.  
• Single-unit shipping pack. The drive is normally shipped in bulk packaging to provide 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.  
3.8  
User-installed accessories  
The following accessories are available. All kits may be installed in the field.  
• Evaluation kit, part number 73473641.  
This kit provides an adapter card (“T-card”) to allow cable connections for two FC ports and DC power.  
• Single-unit shipping pack.  
10  
Barracuda ES.2 FC Product Manual, Rev. B  
       
4.0  
Performance characteristics  
This section provides detailed information concerning performance-related characteristics and features of Bar-  
racuda ES.2 FC drives.  
4.1  
Internal drive characteristics  
ST31000640FC  
Drive capacity*  
Read/write data heads  
Tracks per inch  
Peak bits per inch  
Areal density  
1,000  
8
150,000  
1,090k  
164  
Gbytes (formatted, rounded off value)  
TPI  
BPI  
2
Gbits/inch  
Internal data rate  
Disc rotation speed  
Avg rotational latency  
1,287  
7,200  
4.16  
Mbits/sec (variable with zone)  
rpm  
msec  
*One Gbyte equals one billion bytes when referring to hard drive capacity. Accessible capacity may vary depending on operating environment  
and formatting.  
4.2  
Seek performance  
See Section 9.5, "FC-AL physical interface" on page 56 and the Fibre Channel Interface Manual (part number  
77767496) for additional timing details.  
4.2.1  
Access time  
1 2  
,
Not including controller overhead (msec)  
Read  
7.4  
Write  
8.5  
Average  
Typical  
Typical  
Typical  
Single track  
Full stroke  
0.4  
1.0  
14.3  
15.4  
1.  
2.  
Typical access times are measured under nominal conditions of temperature, voltage,  
and horizontal orientation as measured on a representative sample of drives.  
Access to data = access time + latency time.  
4.2.2  
Format command execution time (minutes)  
ST31000640FC  
Maximum (with verify)  
400  
200  
Maximum (without verify)  
Execution time measured from receipt of the last byte of the Command Descriptor Block (CDB) to the request  
for a Status Byte Transfer to the Initiator (excluding connect/disconnect).  
Barracuda ES.2 FC Product Manual, Rev. B  
11  
                                                 
4.2.3  
General performance characteristics  
Sustainable disc transfer rate*:  
Minimum  
56 Mbytes/sec  
116 Mbytes/sec  
Maximum  
Fibre Channel Interface maximum instantaneous transfer rate  
400 Mbytes/sec* per port  
(dual port = 800 Mbytes/sec*)  
Logical block sizes  
Default is 512-byte data blocks  
Sector sizes variable to 512, 520, 524 and 528 bytes.  
Read/write consecutive sectors on a track  
Yes  
Flaw reallocation performance impact (for flaws reallocated at format time Negligible  
using the spare sectors per sparing zone reallocation scheme.)  
*Assumes no errors and no relocated logical blocks. Rate measured from the start of the first logical block transfer to or  
from the host.  
4.3  
Start/stop time  
The drive accepts the commands listed in the Fibre Channel Interface Manual less than 3 seconds after DC  
power has been applied.  
If the drive receives a NOTIFY (ENABLE SPINUP) primitive through either port and has not received a START  
STOP UNIT command with the START bit equal to 0, the drive becomes ready for normal operations within 30  
seconds (excluding the error recovery procedure).  
If the drive receives a START STOP UNIT command with the START bit equal to 0 before receiving a NOTIFY  
(ENABLE SPINUP) primitive, the drive waits for a START 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 30 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 the spindle. Stop time is 30 sec-  
onds (maximum) from removal of DC power.  
There is no power control switch on the drive.  
4.4  
Prefetch/multi-segmented cache control  
The drive provides a prefetch (read look-ahead) and multi-segmented cache control algorithms that in many  
cases can enhance system performance. Cache refers to the drive buffer storage space when it is used in  
cache operations. To select this feature, the host sends the Mode Select command with the proper values in  
the applicable bytes in page 08h. Prefetch and cache operations are independent features from the standpoint  
that each is enabled and disabled independently using the Mode Select command; however, in actual opera-  
tion, the prefetch feature overlaps cache operation somewhat as described in sections 4.5.1 and 4.5.2.  
12  
Barracuda ES.2 FC Product Manual, Rev. B  
               
All default cache and prefetch mode parameter values (Mode Page 08h) for standard OEM versions of this  
drive family are given in Section 9.3.2  
4.5  
Cache operation  
Note. Refer to the Fibre Channel Interface Manual for more detail concerning the cache bits.  
Of the 16 Mbytes physical buffer space in the drive, approximately 13,000 kbytes can be used as a cache. The  
buffer is divided into logical segments from which data is read and to which data is written.  
The drive keeps track of the logical block addresses of the data stored in each segment of the buffer. If the  
cache is enabled (see RCD bit in the FC Interface Manual), data requested by the host with a read command  
is retrieved from the buffer, if possible, before any disc access is initiated. If cache operation is not enabled, the  
buffer is still used, but only as circular buffer segments during disc medium read operations (disregarding  
Prefetch operation for the moment). That is, the drive does not check in the buffer segments for the requested  
read data, but goes directly to the medium to retrieve it. The retrieved data merely passes through some buffer  
segment on the way to the host. All data transfers to the host are in accordance with buffer-full ratio rules. See  
the explanation provided with the information about Mode Page 02h (disconnect/reconnect control) in the Fibre  
Channel Interface Manual.  
The following is a simplified description of the prefetch/cache operation:  
Case A—read command is received and all of the requested logical blocks are already in the cache:  
1. Drive transfers the requested logical blocks to the initiator.  
Case B—A Read command requests data, and at least one requested logical block is not in any segment of  
the cache:  
1. The drive fetches the requested logical blocks from the disc and transfers them into a segment, and then  
from there to the host in accordance with the Mode Select Disconnect/Reconnect parameters, page 02h.  
2. If the prefetch feature is enabled, refer to section 4.5.2 for operation from this point.  
Each cache segment is actually a self-contained circular buffer whose length is an integer number of logical  
blocks. The drive dynamically creates and removes segments based on the workload. The wrap-around capa-  
bility of the individual segments greatly enhances the cache’s overall performance.  
Note. The size of each segment is not reported by Mode Sense command page 08h, bytes 14 and 15.  
The value 0XFFFF is always reported regardless of the actual size of the segment. Sending a size  
specification using the Mode Select command (bytes 14 and 15) does not set up a new segment  
size. If the STRICT bit in Mode page 00h (byte 2, bit 1) is set to one, the drive responds as it does  
for any attempt to change an unchangeable parameter.  
4.5.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 read caching is enabled (RCD=0), then data written to the medium is retained in the cache to be made avail-  
able for future read cache hits. The same buffer space and segmentation is used as set up for read functions.  
The buffer segmentation scheme is set up or changed independently, having nothing to do with the state of  
RCD. When a write command is issued, if RCD=0, the cache is first checked to see if any logical blocks that  
are to be written are already stored in the cache from a previous read or write command. If there are, the  
respective cache segments are cleared. The new data is cached for subsequent Read commands.  
If the number of write data logical blocks exceed the size of the 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.  
Barracuda ES.2 FC Product Manual, Rev. B  
13  
                 
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 gen-  
erated.  
The Synchronize Cache command may be used to force the drive to write all cached write data to the medium.  
Upon completion of a Synchronize Cache command, all data received from previous write commands will have  
been written to the medium.  
Table 16 show the mode default settings for these drives.  
4.5.2  
Prefetch operation  
If the Prefetch feature is enabled, data in contiguous logical blocks on the disc immediately beyond that which  
was requested by a Read command are retrieved and stored in the buffer for immediate transfer from the  
buffer to the host on subsequent Read commands that request those logical blocks (this is true even if cache  
operation is disabled). Though the prefetch operation uses the buffer as a cache, finding the requested data in  
the buffer is a prefetch hit, not a cache operation hit.  
To enable Prefetch, use Mode Select page 08h, byte 12, bit 5 (Disable Read Ahead - DRA bit). DRA bit = 0  
enables prefetch.  
The drive does not use the Max Prefetch field (bytes 8 and 9) or the Prefetch Ceiling field (bytes 10 and 11).  
When prefetch (read look-ahead) is enabled (enabled by DRA = 0), the drive enables prefetch of contiguous  
blocks from the disc when it senses that a prefetch hit will likely occur. The drive disables prefetch when it  
decides that a prefetch hit is not likely to occur.  
14  
Barracuda ES.2 FC Product Manual, Rev. B  
 
5.0  
Reliability specifications  
The following reliability specifications assume correct host and drive operational interface, including all inter-  
face timings, power supply voltages, environmental requirements and drive mounting constraints.  
Less than 10 errors in 108 seeks  
Seek error rate:  
1
Read Error Rates  
Less than 10 errors in 1012 bits transferred (OEM default settings)  
Less than 1 sector in 1015 bits transferred  
Less than 1 sector in 1021 bits transferred  
Recovered Data  
Unrecovered Data  
Miscorrected Data  
Less than 1 error in 1012 bits transferred with minimum receive eye.  
Less than 1 error in 1014 bits transferred with typical receive eye.  
Interface error rate:  
MTBF  
1,200,000 hours  
0.73%  
Annualized Failure Rate (AFR):  
Preventive maintenance:  
None required  
1. Error rate specified with automatic retries and data correction with ECC enabled and all flaws reallocated.  
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 Section 6.2  
• 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  
Recoverable Errors  
Recovereable errors are those detected and corrected by the drive, and do not require user intervention.  
Recoverable Data errors will use correction, although ECC on-the-fly is not considered for purposes of recov-  
ered error specifications.  
Recovered Data error rate is determined using read bits transferred for recoverable errors occurring during a  
read, and using write bits transferred for recoverable errors occurring during a write.  
5.1.2  
Unrecoverable Errors  
16  
Unrecoverable Data Errors (Sense Key = 03h) are specified at less than 1 sector in error per 10 bits trans-  
ferred. Unrecoverable Data Errors resulting from the same cause are treated as 1 error for that block.  
Barracuda ES.2 FC Product Manual, Rev. B  
15  
                                   
5.1.3  
Seek errors  
A seek error is defined as a failure of the drive to position the heads to the addressed track. After detecting an  
initial seek error, the drive automatically performs an error recovery process. If the error recovery process fails,  
a seek positioning error (Error code = 15h or 02h) will be reported with a Hardware error (04h) in the Sense  
8
Key. Recoverable seek errors are specified at Less than 10 errors in 10 seeks. Unrecoverable seek errors  
(Sense Key = 04h) are classified as drive failures.  
5.1.4  
Interface errors  
An interface error is defined as a failure of the receiver on a port to recover the data as transmitted by the  
device port connected to the receiver. The error may be detected as a running disparity error, illegal code, loss  
of word sync, or CRC error. The total error rate for a loop of devices is the sum of the individual device error  
rates.  
5.2  
Reliability and service  
You can enhance the reliability of disk 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 8.2 provides recommended air-flow information.  
5.2.1  
Annualized Failure Rate (AFR) and Mean Time Between Failures (MTBF)  
These drives shall achieve an AFR of 0.73% (MTBF of 1,200,000 hours) when operated in an environment that  
ensures the HDA case temperatures do not exceed the values specified in Section 6.4.1.  
Operation at case temperatures outside the specifications in Section 6.4.1 may increase the AFR (decrease  
the MTBF).  
AFR and MTBF statistics are poplulation statistics that are not relevant to individual units. AFR and MTBF  
specifications are based on the following assumptions for Enterprise Storage System environments:  
• 8,760 power-on hours per year  
• 250 average on/off cycles per year  
• Operating at nominal voltages  
• System provides adequate cooling to ensure the case temperatures specified in Section 6.4.1 are not  
exceeded.  
5.2.2  
Preventive maintenance  
No routine scheduled preventive maintenance is required.  
5.2.3  
Hot plugging the drive  
Inserting and removing the drive on the FC-AL will interrupt loop operation. The interruption occurs when the  
receiver of the next device in the loop must synchronize to a different input signal. FC error detection mecha-  
nisms, character sync, running disparity, word sync, and CRC are able to detect any error. Recovery is initiated  
based on the type of error.  
The disc drive defaults to the FC-AL Monitoring state, Pass-through state, when it is powered-on by switching  
the power or hot plugged. The control line to an optional port bypass circuit (external to the drive), defaults to  
the Enable Bypass state. If the bypass circuit is present, the next device in the loop will continue to receive the  
output of the previous device to the newly inserted device. If the bypass circuit is not present, loop operation is  
temporarily disrupted until the next device starts receiving the output from the newly inserted device and  
regains synchronization to the new input.  
16  
Barracuda ES.2 FC Product Manual, Rev. B  
                                                 
The Pass-through state is disabled while the drive performs self test of the FC interface. The control line for an  
external port bypass circuit remains in the Enable Bypass state while self test is running. If the bypass circuit is  
present, loop operation may continue. If the bypass circuit is not present, loop operation will be halted while the  
self test of the FC interface runs.  
When the self test completes successfully, the control line to the bypass circuit is disabled and the drive enters  
the FC-AL Initializing state. The receiver on the next device in the loop must synchronize to output of the newly  
inserted drive.  
If the self-test fails, the control line to the bypass circuit remains in the Enable Bypass state.  
Note. It is the responsibility of the systems integrator to assure that no temperature, energy, voltage haz-  
ard, or ESD potential hazard is presented during the hot connect/disconnect operation. Discharge  
the static electricity from the drive carrier prior to inserting it into the system.  
Caution. The drive motor must come to a complete stop prior to changing the plane of operation. This time is  
required to insure data integrity.  
5.2.4  
S.M.A.R.T.  
S.M.A.R.T. is an acronym for Self-Monitoring Analysis and Reporting Technology. This technology is intended  
to recognize conditions that indicate imminent drive failure and is designed to provide sufficient warning of a  
failure to allow you to back up the data before an actual failure occurs.  
Note. The drive’s firmware monitors specific attributes for degradation over time but can’t predict instanta-  
neous drive failures.  
Each monitored attribute has been selected to monitor a specific set of failure conditions in the operating per-  
formance 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 DEX-  
CPT bit disables all S.M.A.R.T. functions. When enabled, S.M.A.R.T. collects on-line data as the drive performs  
normal read and write operations. When the PERF bit is set, the drive is considered to be in “On-line Mode  
Only” and will not perform off-line functions.  
You can measure off-line attributes and force the drive to save the data by using the Rezero Unit command.  
Forcing S.M.A.R.T. resets the timer so that the next scheduled interrupt is in two hours.  
You can interrogate the drive through the host to determine the time remaining before the next scheduled mea-  
surement and data logging process occurs. To accomplish this, issue a Log Sense command to log page 0x3E.  
This allows you to control when S.M.A.R.T. interruptions occur. Forcing S.M.A.R.T. with the RTZ command  
resets the timer.  
Performance impact  
S.M.A.R.T. attribute data is saved to the disc so that the events that caused a predictive failure can be recre-  
ated. The drive measures and saves parameters once every two hours subject to an idle period on the FC-AL  
bus. The process of measuring off-line attribute data and saving data to the disc is uninterruptable. The maxi-  
mum on-line only processing delay is summarized below:  
Maximum processing delay  
On-line only delay  
Fully-enabled delay  
DEXCPT = 0, PERF = 1  
DEXCPT = 0, PERF = 0  
42 milliseconds  
S.M.A.R.T. delay times  
163 milliseconds  
Barracuda ES.2 FC Product Manual, Rev. B  
17  
     
Reporting control  
Reporting is controlled by the MRIE bits in the Informational Exceptions Control mode page (1Ch). Subject to  
the reporting method, the firmware will issue to the host an 01-5Dxx sense code. 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 their interval. If the number of errors exceeds the threshold before  
the interval expires, the error rate is considered to be unacceptable. If the number of errors does not exceed  
the threshold before the interval expires, the error rate is considered to be acceptable. In either case, the inter-  
val 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 firm-  
ware keeps a running count of the number of times the error rate for each attribute is unacceptable. To accom-  
plish 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 pre-  
dictive 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.2.5  
Thermal monitor  
Barracuda ES.2 FC 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.  
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 tem-  
perature 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 speci-  
fied limit in compliance with the SCSI standard. The drive temperature is reported in the FRU code field of  
mode sense data. You can use this information to determine if the warning is due to the temperature exceeding  
the drive threatening temperature or the user-specified temperature.  
This feature is controlled by the Enable Warning (EWasc) bit, and the 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 68°C which is the  
maximum temperature limit according to the drive specification. The second trip point is user-selectable using  
the Log Select command. The reference temperature parameter in the temperature log page (see Table 1) can  
18  
Barracuda ES.2 FC Product Manual, Rev. B  
 
be used to set this trip point. The default value for this drive is 68°C, however, you can set it to any value in the  
range of 0 to 68°C. If you specify a temperature greater than 68°C in this field, the temperature is rounded  
down to 68°C. A sense code is sent to the host to indicate the rounding of the parameter field.  
Table 1:  
Temperature Log Page (0Dh)  
Parameter Code  
Description  
Primary Temperature  
Reference Temperature  
0000h  
0001h  
5.2.6  
Drive Self Test (DST)  
Drive Self Test (DST) is a technology designed to recognize drive fault conditions that qualify the drive as a  
failed unit. DST validates the functionality of the drive at a system level.  
There are two test coverage options implemented in DST:  
1. Extended test  
2. Short text  
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 surface, but does some fundamental tests and scans portions of the media.  
If DST encounters an error during either of these tests, it reports a fault condition. If the drive fails the test,  
remove it from service and return it to Seagate for service.  
5.2.6.1  
DST failure definition  
The drive will present a “diagnostic failed” condition through the self-tests results value of the diagnostic log  
page if a functional failure is encountered during DST. The channel and servo parameters are not modified to  
test the drive more stringently, and the number of retries are not reduced. All retries and recovery processes  
are enabled during the test. If data is recoverable, no failure condition will be reported regardless of the number  
of retries required to recover the data.  
The following conditions are considered DST failure conditions:  
• Seek error after retries are exhausted  
• Track-follow error after retries are exhausted  
• Read error after retries are exhausted  
• Write error after retries are exhausted  
Recovered errors will not be reported as diagnostic failures.  
5.2.6.2  
Implementation  
This section provides all of the information necessary to implement the DST function on this drive.  
5.2.6.2.1  
State of the drive prior to testing  
The drive must be in a ready state before issuing the Send Diagnostic command. There are multiple reasons  
why a drive may not be ready, some of which are valid conditions, and not errors. For example, a drive may be  
in process of doing a format, or another DST. It is the responsibility of the host application to determine the “not  
ready” cause.  
While not technically part of DST, a Not Ready condition also qualifies the drive to be returned to Seagate as a  
failed drive.  
Barracuda ES.2 FC Product Manual, Rev. B  
19  
 
A Drive Not Ready condition is reported by the drive under the following conditions:  
• Motor will not spin  
• Motor will not lock to speed  
• Servo will not lock on track  
• Drive cannot read configuration tables from the disc  
In these conditions, the drive responds to a Test Unit Ready command with an 02/04/00 or 02/04/03 code.  
5.2.6.2.2  
Invoking DST  
To invoke DST, submit the Send Diagnostic command with the appropriate Function Code (001b for the short  
test or 010b for the extended test) in bytes 1, bits 5, 6, and 7.  
5.2.6.2.3  
Short and extended tests  
DST has two testing options:  
1. short  
2. extended  
These testing options are described in the following two subsections.  
Each test consists of three segments: an electrical test segment, a servo test segment, and a read/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 surface, but does some fundamental tests and  
scans portions of the media. A complete read/verify scan is not performed and only factual failures will report a  
fault condition. This option provides a quick confidence test of the drive.  
Extended test (Function Code: 010b)  
The objective of the extended test option is to empirically test critical drive components. For example, the seek  
tests and on-track operations test the positioning mechanism. The read operation tests the read head element  
and the media surface. The write element is tested through read/write/read operations. The integrity of the  
media is checked through a read/verify scan of the media. Motor functionality is tested by default as a part of  
these tests.  
The anticipated length of the Extended test is reported through the Control Mode page.  
5.2.6.2.4  
Log page entries  
When the drive begins DST, it creates a new entry in the Self-test Results Log page. The new entry is created  
by inserting a new self-test parameter block at the 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 param-  
eter 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.  
20  
Barracuda ES.2 FC Product Manual, Rev. B  
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.2.6.2.5  
Abort  
There are several ways to abort a diagnostic. You can use a SCSI Bus Reset or a Bus Device Reset message  
to abort the diagnostic.  
You can abort a DST executing in background mode by using the abort code in the DST Function Code field.  
This will cause a 01 (self-test aborted by the application client) code to appear in the self-test results values  
log. All other abort mechanisms will be reported as a 02 (self-test routine was interrupted by a reset condition).  
5.2.7  
Product warranty  
Beginning on the date of shipment to the customer and continuing for the period specified in your purchase  
contract, Seagate warrants that each product (including components and subassemblies) that fails to function  
properly under normal use due to defect in materials or workmanship or due to nonconformance to the applica-  
ble specifications will be repaired or replaced, at Seagate’s option and at no charge to the customer, if returned  
by customer at customer’s expense to Seagate’s designated facility in accordance with Seagate’s warranty  
procedure. Seagate will pay for transporting the repair or replacement item to the customer. For more detailed  
warranty information, refer to the standard terms and conditions of purchase for Seagate products on your pur-  
chase documentation.  
The remaining warranty for a particular drive can be determined by calling Seagate Customer Service at  
1-800-468-3472. You can also determine remaining warranty using the Seagate web site (www.seagate.com).  
The drive serial number is required to determine remaining warranty information.  
Shipping  
When transporting or shipping a drive, use only a Seagate-approved container. Keep your original box.  
Seagate approved containers are easily identified by the Seagate Approved Package label. Shipping a drive in  
a non-approved container voids the drive warranty.  
Seagate repair centers may refuse receipt of components improperly packaged or obviously damaged in tran-  
sit. 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.  
Barracuda ES.2 FC Product Manual, Rev. B  
21  
             
22  
Barracuda ES.2 FC Product Manual, Rev. B  
6.0  
Physical/electrical specifications  
This section provides information relating to the physical and electrical characteristics of the drive.  
6.1  
AC power requirements  
None.  
6.2  
DC power requirements  
The voltage and current requirements for a single drive are shown below. Values indicated apply at the drive  
connector. Notes are shown following table 2.  
Table 2:  
DC power requirements  
4 Gbit  
(Amps)  
+5V  
Notes  
(Amps)  
+12V [2]  
±5% [2]  
0.50  
Voltage  
Regulation  
[5]  
±5%  
Avg idle current DCX  
Maximum starting current  
(peak DC) DC  
[1] [6]  
0.75  
3σ [3]  
1.00  
1.15  
0.65  
2.00  
3.23  
0.04  
(peak AC) AC  
3σ [3]  
Delayed motor start (max) DC  
Peak operating current:  
Typical DCX  
3σ [1] [4]  
[1]  
3σ [1]  
3σ  
0.69  
0.71  
1.13  
0.77  
0.82  
1.67  
Maximum DC  
Maximum (peak) DC  
[1] Measured with average reading DC ammeter. Instantaneous +12V current peaks will exceed these val-  
ues. Power supply at nominal voltage. N (number of drives tested) = 6, 35 Degrees C ambient.  
[2] For +12 V, a 10% tolerance is allowed during initial spindle start but must return to ±5% before reaching  
10,000 RPM. The ±5% must be maintained after the drive signifies that its power-up sequence has been  
completed and that the drive is able to accept selection by the host initiator.  
[3] See +12V current profiles in Figure 1.  
[4] This condition occurs when the Motor Start option is enabled and the drive has not yet received a Start  
Motor command.  
[5] See paragraph 6.2.1, "Conducted noise immunity." Specified voltage tolerance includes ripple, noise, and  
transient response.  
[6] During idle, the drive heads are relocated every 60 seconds to a random location within the band from  
Barracuda ES.2 FC Product Manual, Rev. B  
23  
                         
three-quarters to maximum track.  
General DC power requirement notes.  
1. Minimum current loading for each supply voltage is not less than 1.2% 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 spindle start, are measured after a 10-minute warm up.  
5. No terminator power.  
6.2.1  
Conducted noise immunity  
Noise is specified as a periodic and random distribution of frequencies covering a band from DC to 10 MHz.  
Maximum allowed noise values given below are peak-to-peak measurements and apply at the drive power  
connector.  
+5 V = 250 mV pp from 0 to 100 kHz to 20 MHz.  
+12 V = 800 mV pp from 100 Hz to 8 KHz.  
450 mV pp from 8 KHz to 20 KHz.  
250 mV pp from 20 KHz to 5 MHz.  
6.2.2  
Power sequencing  
The drive does not require power sequencing. The drive protects against inadvertent writing during power-up  
and down.  
24  
Barracuda ES.2 FC Product Manual, Rev. B  
         
6.2.3  
Current profiles  
The +12V and +5V current profiles for the ST31000640FC model is shown below.  
Note: All times and currents are typical. See Table 2 for maximum current requirements.  
Figure 1. Typical ST31000640FC drive, 4 Gbit, +5V and +12V current profiles  
Barracuda ES.2 FC Product Manual, Rev. B  
25  
     
6.3  
Power dissipation  
Typical power dissipation under idle conditions in 4 Gbit operation is 9.16 watts (31.26 BTUs per hour).  
To obtain operating power for typical random read operations, refer to the following I/O rate curve (see Figure  
2). Locate the typical I/O rate 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 2. DC current and power vs. input/output operations per second at 4 Gbit  
26  
Barracuda ES.2 FC Product Manual, Rev. B  
     
6.4  
Environmental limits  
Temperature and humidity values experienced by the drive must be such that condensation does not occur on  
any drive part. Altitude and atmospheric pressure specifications are referenced to a standard day at 58.7°F  
(14.8°C). Maximum wet bulb temperature is 82°F (28°C). Above 1,000 feet (305 meters), the maximum tem-  
perature is derated linearly to 112°F (44°C) at 10,000 feet (3,048 meters).  
6.4.1  
Temperature  
a. Operating  
The maximum allowable continuous or sustained HDA case temperature for the rated Annualized Failure  
Rate (AFR) is 122°F (50°C) The maximum allowable HDA case temperature is 50°C. Occasional excur-  
sions of HDA case temperatures above 122°F (50°C) or below 41°F (5°C) may occur without impact to the  
specified AFR. Continual or sustained operation at HDA case temperatures outside these limits may  
degrade AFR.  
Provided the HDA case temperatures limits are met, the drive meets all specifications over a 41°F to 131°F  
(5°C to 55°C) drive ambient temperature range with a maximum temperature gradient of 36°F (20°C) per  
hour. Air flow may be needed in the drive enclosure to keep within this range (see Section 8.3). Operation at  
HDA case temperatures outside this range may adversely affect the drives ability to meet specifications. To  
confirm that the required cooling for the electronics and HDA case is provided, place the drive in its final  
mechanical configuration, perform random write/read operations and measure the HDA case temperature  
after it has stabilized.  
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.  
HDA Temp.  
Check Point  
1
.0"  
.5"  
Figure 3. Locations of the HDA temperature check point  
6.4.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.  
Barracuda ES.2 FC Product Manual, Rev. B  
27  
                             
6.4.3  
Effective altitude (sea level)  
a. Operating  
–200 to +10,000 feet (–61 to +3,048 meters)  
b. Non-operating  
–200 to +40,000 feet (–61 to +12,210 meters)  
6.4.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 in accor-  
dance with the restrictions of Section 8.4.  
6.4.4.1  
Shock  
a. Operating—normal  
The drive, as installed for normal operation, shall operate error free while subjected to intermittent shock not  
exceeding 63 Gs at a maximum duration of 2 msec (half sinewave). Shock may be applied in the X, Y, or Z  
axis.  
b. Operating—abnormal  
Equipment, as installed for normal operation, does not incur physical damage while subjected to intermit-  
tent shock not exceeding 40 Gs at a maximum duration of 11 msec (half sinewave). Shock occurring at  
abnormal levels may promote degraded operational performance during the abnormal shock period. Speci-  
fied operational performance will continue when normal operating shock levels resume. Shock may be  
applied in the X, Y, or Z axis. Shock is not to be repeated more than two times per second.  
c. 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 80 Gs at a maximum duration of 11 msec (half  
sinewave) shall not exhibit device damage or performance degradation. Shock may be applied in the X, Y,  
or Z axis.  
The drive subjected to nonrepetitive shock not exceeding 300 Gs at a maximum duration of 2 msec (half  
sinewave) does not exhibit device damage or performance degradation. Shock may be applied in the X, Y,  
or Z axis.  
The drive subjected to nonrepetitve shock not exceeding 150 Gs at a maximum duration of 0.5 msec (half  
sinewave) does not exhibit device damage or performance degradation. Shock may be applied in the X, Y,  
or Z axis.  
d. Packaged  
Disc drives shipped as loose load (not palletized) general freight will be packaged to withstand drops from  
heights as defined in the table below. For additional details refer to Seagate specifications 30190-001  
(under 100 lbs/45 kg) or 30191-001 (over 100 lbs/45 Kg).  
Package size  
Packaged/product weight  
Any  
Drop height  
<600 cu in (<9,800 cu cm)  
600-1800 cu in (9,800-19,700 cu cm)  
>1800 cu in (>19,700 cu cm)  
>600 cu in (>9,800 cu cm)  
60 in (1524 mm)  
48 in (1219 mm)  
42 in (1067 mm)  
36 in (914 mm)  
0-20 lb (0 to 9.1 kg)  
0-20 lb (0 to 9.1 kg)  
20-40 lb (9.1 to 18.1 kg)  
28  
Barracuda ES.2 FC Product Manual, Rev. B  
                       
Drives packaged in single or multipacks with a gross weight of 20 pounds (8.95 kg) or less by Seagate for  
general freight shipment shall withstand a drop test from 48 inches (1,070 mm) against a concrete floor or  
equivalent.  
6.4.4.2  
Vibration  
a. Operating—normal  
The drive as installed for normal operation, shall comply with the complete specified performance while  
subjected to continuous vibration not exceeding  
5 - 22 Hz  
0.25 Gs, Limited displacement  
22 - 350 Hz  
350 - 500 Hz  
0.5 Gs  
0.25 Gs  
Vibration may be applied in the X, Y, or Z axis.  
b. Operating—abnormal  
Equipment as installed for normal operation shall not incur physical damage while subjected to periodic  
vibration not exceeding:  
15 minutes of duration at major resonant frequency  
Vibration occurring at these levels may degrade operational performance during the abnormal vibration  
period. Specified operational performance will continue when normal operating vibration levels are  
resumed. This assumes system recovery routines are available.  
Operating abnormal translational random flat profile  
5 - 500 Hz  
0.75 Gs (0 to peak)  
c. Non-operating  
The limits of non-operating vibration shall apply to all conditions of handling and transportation. This  
includes both isolated drives and integrated drives.  
The drive shall not incur physical damage or degraded performance as a result of continuous vibration not  
exceeding  
5 - 22 Hz  
2 Gs (0 to peak, linear, swept sine, 0.5 octave/min)  
5 Gs (0 to peak, linear, swept sine, 0.5 octave/min)  
2 Gs (0 to peak, linear, swept sine, 0.5 octave/min)  
22 - 350 Hz  
350 - 500 Hz  
Vibration may be applied in the X, Y, or Z axis.  
6.4.5  
Acoustics  
Sound power during idle mode shall be 2.9 bels typical when measured to ISO 7779 specification. Sound  
power while operating shall be 3.2 bels typical when measured to ISO 7779 specification.  
There will not be any discrete tones more than 10 dB above the masking noise on typical drives when mea-  
sured according to Seagate specification 30553-001. There will not be any tones more than 24 dB above the  
masking noise on any drive.  
6.4.6  
Air cleanliness  
The drive is designed to operate in a typical office environment with minimal environmental control.  
6.4.7  
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.  
Barracuda ES.2 FC Product Manual, Rev. B  
29  
                           
Users should use caution exposing any electronic components to uncontrolled chemical pollutants and corro-  
sive chemicals as electronic drive component reliability can be affected by the installation environment. The sil-  
ver, 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 vulca-  
nized 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.4.8  
European Union Restriction of Hazardous Substances (RoHS) Directive  
Seagate designs its products to meet environmental protection requirements worldwide, including regulations  
restricting certain chemical substances. A new law, the European Union Restriction of Hazardous Substances  
(RoHS) Directive, restricts the presence of chemical substances, including Lead, Cadmium, Mercury,  
Hexavalent Chromium, PBB and PBDE, in electronic products, effective July 2006. This drive is manufactured  
with components and materials that comply with the RoHS Directive.  
6.4.9  
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.  
“ ”  
O
RoHS MCV  
"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.  
X”  
RoHS MCV  
6.4.10  
Electromagnetic susceptibility  
See Section 2.1.1.1.  
30  
Barracuda ES.2 FC Product Manual, Rev. B  
             
6.5  
Mechanical specifications  
Refer to Figure 4 for detailed physical dimensions. See Section 8.4, “Drive mounting.”  
Height (max):  
Width (max):  
Depth (max):  
Weight (max):  
1.028 in  
26.11 mm  
4.010 in  
101.85 mm  
146.99 mm  
0.694 kilograms  
5.787 in  
1.53 pounds  
B
J
H
L
K
// T -Z-  
REF  
S
-Z-  
[1]  
R REF  
N -X-  
Notes:  
[1]  
Mounting holes are 6-32 UNC 2B, three  
on each side and four on the bottom.  
Max screw penetration into side of drive  
is 0.15 in. (3.81 mm). Max screw  
tightening torque is 6.0 in-lb (3.32 nm)  
with minimum full thread engagement of  
0.12 in. (3.05 mm).  
A
-Z-  
C
M
-X-  
U -X-  
Dimension Table  
Inches  
Millimeters  
P
A
B
C
D
E
F
1.028 max  
5.787 max  
4.000 .010  
3.750 .010  
0.125 .010  
1.750 .010  
1.122 .020  
4.000 .010  
0.250 .010  
1.638 .010  
0.181  
26.10 max  
147.00 max  
101.60 .25  
95.25 .25  
3.18 .25  
44.45 .25  
28.50 .50  
101.60 .25  
6.35 .25  
41.60 .25  
4.60  
H
J
F
[1]  
K
L
M
N
P
R
S
T
.040  
1.02  
1.625 .020  
1.618  
41.28 .50  
41.10  
0.276 .040  
.015 max  
7.00 1.02  
0.38 max  
0.38 max  
U
.015 max  
E
D
Figure 4. Mounting configuration dimensions  
Barracuda ES.2 FC Product Manual, Rev. B  
31  
         
32  
Barracuda ES.2 FC Product Manual, Rev. B  
7.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 FC system error con-  
siderations (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 7.4)  
• Media Pre-Scan (see Section 7.5)  
• Deferred Auto-Reallocation (see Section 7.6)  
• Idle Read After Write (see Section 7.7)  
The read error rates and specified storage capacities are not dependent on host (initiator) defect management  
routines.  
7.1  
Drive internal defects/errors  
During the initial drive format operation at the factory, media defects are identified, tagged as being unusable,  
and their locations recorded on the drive primary defects list (referred to as the “P’ list and also as the ETF  
defect list). At factory format time, these known defects are also reallocated, that is, reassigned to a new place  
on the medium and the location 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 Fibre Channel Interface Manual.  
Also, more information on the drive Error Recovery philosophy is presented in the Fibre Channel Interface  
Manual.  
7.2  
Drive error recovery procedures  
When an error occurs during drive operation, the drive, if programmed to do so, performs error recovery proce-  
dures to attempt to recover the data. The error recovery procedures used depend on the options previously set  
in the Error Recovery Parameters mode page. Error recovery and defect management may involve using sev-  
eral SCSI commands described in the Fibre Channel Interface Manual. The drive implements selectable error  
recovery time limits required in video applications.  
The error recovery scheme supported by the drive provides a way to control the total error recovery time for the  
entire command in addition to controlling the recovery level for a single LBA. The total amount of time spent in  
error recovery for a command can be limited using the Recovery Time Limit bytes in the Error Recovery mode  
page. The total amount of time spent in error recovery for a single LBA can be limited using the Read Retry  
Count or Write Retry Count bytes in the Error Recovery mode page.  
Barracuda ES.2 FC Product Manual, Rev. B  
33  
                 
The drive firmware error recovery algorithms consists of 11 levels for read recoveries and five levels for write.  
Each level may consist of multiple steps, where a step is defined as a recovery function involving a single re-  
read or re-write attempt. The maximum level used by the drive in LBA recovery is determined by the read and  
write retry counts.  
Table 3 equates the read and write retry count with the maximum possible recovery time for read and write  
recovery of individual LBAs. The times given do not include time taken to perform reallocations. Reallocations  
are performed when the ARRE bit (for reads) or AWRE bit (for writes) is one, the RC bit is zero, and the recov-  
ery time limit for the command has not yet been met. Time needed to perform reallocation is not counted  
against the recovery time limit.  
When the RC bit is one, reallocations are disabled even if the ARRE or AWRE bits are one. The drive will still  
perform data recovery actions within the limits defined by the Read Retry Count, Write Retry Count, and  
Recovery Time Limit parameters. However, the drive does not report any unrecovered errors.  
Table 3:  
Read and write retry count maximum recovery times  
Maximum recovery time per  
Maximum recovery time per  
LBA (cumulative, msec)  
Read retry count1 LBA (cumulative, msec)  
Write retry count1  
0
51.87  
0
23.94  
35.91  
55.86  
67.83  
119.79  
147.72  
1
59.85  
1
2
203.49  
231.42  
297.38  
323.62  
355.54  
439.39  
507.39  
539.31  
567.24  
1468.74  
2
3
3
4
4
5
5 (default)  
6
7
8
9
10  
11 (default)  
[1] These values are subject to change.  
Setting these retry counts to a value below the default setting could result in an increased unrecovered  
error rate which may exceed the value given in this product manual. A setting of zero (0) will result in the  
drive not performing error recovery.  
For example, suppose the Read/Write Recovery page has the RC bit set to 0, read retry count set to 4,  
and the recovery time limit field (Mode Sense page 01, bytes 10 and 11) set to FF FF hex (maximum). A  
four LBA Read command is allowed to take up to 297.38 msec recovery time for each of the four LBAs in  
the command. If the recovery time limit is set to 00 C8 hex (200 msec decimal) a four LBA read command  
is allowed to take up to 200 msec for all error recovery within that command. The use of the Recovery  
Time Limit field allows finer granularity on control of the time spent in error recovery. The recovery time  
limit only starts counting when the drive is executing error recovery and it restarts on each command.  
Therefore, each command’s total recovery time is subject to the recovery time limit. Note: A recovery time  
limit of 0 will use the drive’s default value of FF FF. Minimum recovery time limit is achieved by setting the  
Recovery Time Limit field to 00 01.  
34  
Barracuda ES.2 FC Product Manual, Rev. B  
7.3  
FC-AL system errors  
Information on the reporting of operational errors or faults across the interface is given in the Fibre Channel  
Interface Manual. The FCP Response returns information to the host about numerous kinds of errors or faults.  
The Receive Diagnostic Results reports the results of diagnostic operations performed by the drive.  
Status returned by the drive to the initiator is described in the Fibre Channel 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.  
7.4  
Background Media Scan  
Background Media Scan (BMS) is a self-initiated media scan. BMS is defined in the T10 document SPC-4  
available from the T10 committee. BMS performs sequential reads across the entire pack of the media while  
the drive is idle. In RAID arrays, BMS allows hot spare drives to be 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 or  
reallocated per ARRE/AWRE settings.  
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 activ-  
ity.  
Since the background scan functions are only done during idle periods, BMS causes a negligible impact to sys-  
tem performance. The first BMS scan for a newly manufactured drive is performed as quickly as possible to  
verify the media and protect data by setting the “Start time after idle” to 5ms, all subsequent scans begin after  
500ms of idle time. Other features that normally use idle time to function will function normally because BMS  
functions for bursts of 800ms 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 1 ms.  
7.5  
Media Pre-Scan  
Media Pre-Scan is a feature that allows the drive to repair media errors that would otherwise have been found  
by the host system during critical data accesses early in the drive’s life. The default setting for Media Pre-Scan  
is enabled on standard products. Media Pre-Scan checks each write command to determine if the destination  
LBAs have been scanned by BMS. If the LBAs have been verified, the drive proceeds with the normal write  
command. If the LBAs have not been verified by BMS, Pre-Scan will convert the write to a write verify to certify  
that the data was properly written to the disc.  
Note. During Pre-Scan write verify commands, write performance may decrease by 50% until Pre-Scan  
completes. Write performance testing should be performed after Pre-Scan is complete. This may  
be checked by reading the BMS status.  
To expedite the scan of the full pack and subsequently exit from the Pre-Scan period, BMS will begin scanning  
immediately when the drive goes to idle during the Pre-Scan period. In the event that the drive is in a high  
transaction traffic environment and is unable to complete a BMS scan within 24 power on hours BMS will dis-  
able Pre-Scan to restore full performance to the system.  
Barracuda ES.2 FC Product Manual, Rev. B  
35  
           
7.6  
Deferred Auto-Reallocation  
Deferred Auto-Reallocation (DAR) simplifies reallocation algorithms at the system level by allowing the drive to  
reallocate unreadable locations on a subsequent write command. Sites are marked for DAR during read oper-  
ations performed by the drive. When a write command is received for an LBA marked for DAR, the auto-reallo-  
cation process is invoked and attempts to rewrite the data to the original location. If a verification of this rewrite  
fails, the sector is re-mapped to a spare location.  
This is in contrast to the system having to use the Reassign Command to reassign a location that was unread-  
able and then generate a write command to rewrite the data. DAR is most effective when AWRE and ARRE  
are enabled—this is the default setting from the Seagate factory. With AWRE and ARRE disabled DAR is  
unable to reallocate the failing location and will report an error sense code indicating that a write command is  
being attempted to a previously failing location.  
7.7  
Idle Read After Write  
Idle Read After Write (IRAW) utilizes idle time to verify the integrity of recently written data. During idle periods,  
no active system requests, the drive reads recently written data from the media and compares it to valid write  
command data resident in the drives data buffer. Any sectors that fail the comparison result in the invocation of  
a rewrite and auto-reallocation process. The process attempts to rewrite the data to the original location. If a  
verification of this rewrite fails, the sector is re-mapped to a spare location.  
36  
Barracuda ES.2 FC Product Manual, Rev. B  
           
8.0  
Installation  
Barracuda ES.2 FC disc drive installation is a plug-and-play process. There are no jumpers, switches, or termi-  
nators on the drive. Simply plug the drive into the host’s 40-pin Fibre Channel backpanel connector (FC-  
SCA)no cables are required. See Section 9.5 for additional information about this connector.  
Use the FC-AL interface to select drive ID and all option configurations for devices on the loop.  
If multiple devices are on the same FC-AL and physical addresses are used, set the device selection IDs (SEL  
IDs) on the backpanel so that no two devices have the same selection ID. This is called the hard assigned arbi-  
trated loop physical address (AL_PA). There are 125 AL_PAs available (see Table 22). If you set the AL_PA on  
the backpanel to any value other than 0, the device plugged into the backpanel’s SCA connector inherits this  
AL_PA. In the event you don’t successfully assign unique hard addresses (and therefore have duplicate selec-  
tion IDs assigned to two or more devices), the FC-AL generates a message indicating this condition. If you set  
the AL_PA on the backpanel to a value of 0, the system issues a unique soft-assigned physical address auto-  
matically.  
Loop initialization is the process used to verify or obtain an address. The loop initialization process is per-  
formed when power is applied to the drive, when a device is added or removed from the Fibre Channel loop, or  
when a device times out attempting to win arbitration.  
• Set all option selections in the connector prior to applying power to the drive. If you change options after  
applying power to the drive, recycle the drive power to activate the new settings.  
• It is not necessary to low-level format this drive. The drive is shipped from the factory low-level formatted in  
512-byte logical blocks. You need to reformat the drive only if you want to select a different logical block size.  
8.1  
Drive ID/option selection  
All drive options are made through the interface connector (J1). Table 19 provides the pin descriptions for the  
40-pin Fibre Channel single connector (J1).  
8.2  
Drive orientation  
The drive may be mounted in any orientation. All drive performance characterizations, however, have been  
done with the drive in horizontal (discs level) and vertical (drive on its side) orientations, which are the two pre-  
ferred mounting orientations.  
8.3  
Cooling  
The host enclosure must dissipate heat from the drive. You should confirm that the host enclosure is designed  
to ensure that the drive operates within the temperature measurement guidelines described in Section 6.4.1. In  
some cases, forced airflow may be required to keep temperatures at or below the temperatures specified in  
Section 6.4.1.  
Barracuda ES.2 FC Product Manual, Rev. B  
37