Document Audience:INTERNAL
Document ID:I0645-1
Title:Seagate Disk Drives support configuration
Copyright Notice:Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Update Date:2004-01-07

---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                            FIELD INFORMATION NOTICE
                  (For Authorized Distribution by SunService)
FIN #: I0645-1
Synopsis: Seagate Disk Drives support configuration
Create Date: 01/30/01
Keywords: 

Seagate Disk Drives support configuration

Top FIN/FCO Report: Yes
Products Reference: Seagate Disk Drives
Product Category: Storage / Disk
Product Affected: 
Mkt_ID   Platform   Model   Description   	         Serial Number
------   --------   -----   -----------   		 -------------
Systems Affected
----------------
  -      E3500      ALL     Ultra Enterprises 3500             -

X-Options Affected
------------------
  -      A5200      ALL     StorEdge 5200 Array                -
  -      T3         ALL     StorEdge T3 Array                  -  
X6720A      -         -	    FC-AL 18.2GB 10kRPM 1" DISK        -	
X6728A      -         -     FC-AL HOT SWAP 18.2GB 10K-RPM      - 
X6724A      -         -     OPT INT DISK 36.4GB/10K FCAL       -
Parts Affected: 
Part Number   Description     			Model
-----------   -----------     			-----
540-4191-01   DRV,ASY,18G10K,1"FC,W/SPUD&PLT      -
540-4440-01   ASSY,18GB,10K,1"FC,LP,W/SLED        -
540-4673-01   DR ASY,18G10K1"FC,SPD&PLT,V2.0      -
540-4525-01   DRV,ASSY,36GB,10K,1"FC,W/SPD&P      - 
540-4367-01   ASSY,36GB,10K,1"FC,LP,W/SLED        -
References: 
BugId:   4173215
PatchId: 105310-14 105356-09 105357-04 105375-25 107469-08 
ESC: 528117 528348 528827
Issue Description: 
Seagate ST318304FC and ST336704FC drives will not boot and will not be
recognized by host systems running Solaris 2.5.1, 2.6, and early 
versions of 7 (prior to 11/99) without the correct version of the
sf driver patch being installed. 

These new generation drives were released as second source 18GB and 36GB 
FCAL disk drives.  These drives are meant to be interchangeable with older 
generation Seagate drives.  The FRU part number for the old and new drives 
is the same. 

FRU         Capacity  Old Drive    New Drive
========     ======   ==========   ========== 
540-4191-02   18Gb    ST318203FC   ST318304FC
540-4440-01   18Gb    ST318203FC   ST318304FC
540-4673-01   18Gb    ST318203FC   ST318304FC
540-4192-01   36Gb    ST136403FC   ST336704FC
540-4367-01   36Gb    ST136403FC   ST336704FC
              

Because these new version disk drives are now being supplied as FRU's,
there is the possibility that they may be installed in systems which
do not have the correct sf driver support.  In this case, they will not
be recognized by the operating system. 

The following versions of Solaris will experience this problem:
2.5.1, 2.6, 7 (before 11/99).  Solaris 7 11/99 and Solaris 8 are NOT affected. 

The problem with these new Seagate drives is that they return sense data
with a length which is not recognized by earlier versions of the sf device 
driver.  This results in a "Lost Frame (write)" message and "SCSI transport 
failed: reason 'incomplete'".   There is no data loss, but the disk drive
is not recognized by the OS and any attempts to write a label to the disk 
produce an error.

The problem has been solved by modifying the sf device driver.  The fix is
available in the following patches:

	Solaris 2.5.1  105310-08 or later
	Solaris 2.6    105375-10 or later
	Solaris 7      107469-01 or later
	
The appropriate patch should be installed on the system boot disk.  If the
disk being replaced is the boot disk, a workaround is available to allow
installation of the OS and the sf driver patch.  See the Corrective Action
section.
Implementation: 
---
        |   |   MANDATORY (Fully Pro-Active)
         ---    
         
  
         ---
        | X |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        |   |   REACTIVE (As Required)
         ---
Corrective Action: 
An Authorized Enterprise Field Service Representative may avoid the
above mentioned problems by following the recommendations as shown
below.

A. When installing one of the new Seagate ST318304FC or ST336704F drives as 
   a NON-BOOT disk, apply the appropriate sf driver patch to the OS.  This 
   will allow the drive to be recognized and to operate normally.

	Solaris 2.5.1   105310-08 or later
	Solaris 2.6     105375-10 or later (requires 105356-xx 105357-xx)
	Solaris 7       107469-01 or later
	Solaris 7-11/99 No patch needed
	Solaris 8       No patch needed
	
B. When installing one of the new Seagate ST318304FC or ST336704F
   drives as the BOOT disk, follow the workaround procedure for 
   Solaris 2.5.1 or Solaris 2.6 below.  There is no workaround for 
   Solaris 7.  This OS must be upgraded to Solaris 7-11/99 or later 
   in order for these drives to be used as the boot disk.


Workaround Procedure for Solaris 2.5.1
======================================

This procedure will enable 2.5.1 Hardware: 11/97 to be installed onto
ST318304FC or ST336704FC drives.  It requires the use of OECD 02/2000
(P/N 704-7076-10) and 2.5.1 Hardware: 11/97 CD's and the availability
of patch 105310-08 (or later), either from a CD or from a host
connected to the network.

1) Load OECD 02/2000 and from OBP:

   ok boot cdrom

2) Proceed through OECD 02/2000 installation as follows:

   Would you like to use this installer?   [y,n,?] y
   The default root disk is /dev/dsk/c0t4d0.
   The Solaris installer needs to format 
   /dev/dsk/c0t4d0 to install Solaris.

   WARNING: ALL INFORMATION ON THE DISK WILL BE ERASED!

   Do you want to format /dev/dsk/c0t4d0?  [y,n,?,q] n

   The following disks were found on your system.
   1) /dev/dsk/c0t4d0
   2) /dev/dsk/c0t5d0
   3) /dev/dsk/c0t6d0
   4) /dev/dsk/c0t7d0
   q) Quit

   Select a disk to place the Solaris installer software, or
   select q) to exit the installer.

   WARNING: ALL INFORMATION ON THE DISK WILL BE ERASED!

   Please make a selection. > 3

   Enter a swap partition size between 320Mb and 17269Mb, default = 512Mb [?] 

   You have selected /dev/dsk/c0t6d0 with a swap size of 512
   to be used by the Solaris installer.

   WARNING: ALL INFORMATION ON THE DISK WILL BE ERASED!

   Is this OK  [y,n,?,q] y

   The Solaris installer will use disk partition, /dev/dsk/c0t6d0s1.
   After files are copied, the system will automatically reboot, and
   installation will continue.
   Please Wait...

   Copying mini-root to local disk....done.

   Copying platform specific files....done.

   Preparing to reboot and continue installation.
   syncing file systems... done
   rebooting...
   Resetting... 
   Software Power ON
   Clock board TOD does not match TOD on any IO board.
   Clock board TOD does not match TOD on any IO board.

   5-slot Sun Enterprise E3500, No Keyboard
   OpenBoot 3.2.26, 1024 MB memory installed, Serial #9619378.
   Copyright 2000 Sun Microsystems, Inc.  All rights reserved
   Ethernet address 8:0:20:92:c7:b2, Host ID: 8092c7b2.

*** As the banner comes up issue a break (Stop-A) to get back to OBP.***

3) At OBP, boot the disk device you were going to install onto
   but choose partition b with boot options -s:

   ok boot /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020378963b8,0:b -s
   Boot device: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020378963b8,0:b  
   File and args: -s
   SunOS Release 5.7 Version Generic_106541-08 [UNIX(R) System V Release 4.0]
   Copyright (c) 1983-1999, Sun Microsystems, Inc.
   
   

   INIT: SINGLE USER MODE
   # df -k
   Filesystem            kbytes    used   avail capacity  Mounted on
   /tmp                  972224     184  972040     1%    /tmp
   /proc                      0       0       0     0%    /proc
   /tmp/devices          972224     184  972040     1%    /devices
   /tmp/dev              972224     184  972040     1%    /dev
  /devices/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020378963b8,0:b
                      494235  289217  155595    66%    /
   fd                         0       0       0     0%    /dev/fd

4) Remount / to be writable:

   # mount -o remount,rw /

   # mount 
   /tmp on /tmp read/write/setuid on Mon Jan  8 16:45:07 2001
   /proc on /proc read/write/setuid on Mon Jan  8 16:45:07 2001
   /devices on /tmp/devices read/write/setuid on Mon Jan  8 16:45:07 2001
   /dev on /tmp/dev read/write/setuid on Mon Jan  8 16:45:07 2001
   /dev/fd on fd read/write/setuid on Mon Jan  8 16:45:07 2001
   / on /devices/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020378963b8,0:b 
   read/write/setuid/largefiles on Mon Jan  8 16:45:44 2001

5) Set up TERM environment variable to allow vi editing.

6) Modify /sbin/run_install to stop system rebooting
   before correct sf driver patch can be loaded:

   # cd /sbin
   # vi run_install
   ...

   fi
   reboot -q > /dev/null <--- Comment this line out
   exec /bin/sh          <--- Add this line
     exit 0
   else
     while true;
     do
       exec sh
     done
   #

7) Issue CTRL-D to continue installation process:

   # ^D
   INIT: New run level: 2
   syslog service starting.

8) Complete installation questions:

   Welcome to the Web Start Solaris Command Line installation!

   The following questions will gather information about this system.
   This information will be used to configure:

        Network
        Name Service
        Date and Time
        Root Password
        Power Management

    

   Please enter a host name, which identifies this system on the network.  
   The name must be unique within the domain in which it resides; 
   creating a duplicate host name will cause problems on the network after 
   you install Solaris.

   ... 
Enter 'y' to apply these values and proceed to the next stage of the installation, or 'n' to return to the beginning and make changes (y/n): y Solaris Web Start will now gather information to install software for Solaris. Please wait while initial values are loaded... Available operating environments: 1. Solaris 2.5.1 Hardware: 11/97 2. Solaris 2.6 5/98 Select the number corresponding to the operating environment you would like to install [1]: 1 You have selected: Solaris OS: Solaris 2.5.1 Hardware: 11/97 Enter 'y' if this is correct, or 'n' if it is incorrect: y Please insert the Solaris 2.5.1 Hardware: 11/97 CD. 9) Insert 2.5.1 Hardware: 11/97 CD and continue installation: Reading CD for Solaris 2.5.1 Hardware: 11/97... Please wait while the system is initializing... To install basic Solaris products into their default directory locations, select Default Install. Custom install provides a choice of which Solaris products to install. For each product, it also provides an option to further customize the products install. Types of install available: 1. Default Install 2. Custom Install Select the number corresponding to the type of install you would like [1]: 2 ...
File System operations: 1. Print the current partition table 2. Modify a disk's partition table 3. Done Select the number corresponding to a file system operation, or 'Done' to proceed with the install [3]: The following items will be installed: Solaris OS: Solaris 2.5.1 Hardware: 11/97 System Locale: English (United States) ( en_US ) Solaris Software Group: Entire Solaris Software Group Enter 'y' to accept these values and start the installation, or 'n' to return to the beginning and make changes (y/n): y Installing... Installing Solaris software group |-1%------------25%------------50%------------75%------------100%| Installing Additional Software |-1%------------25%------------50%------------75%------------100%| Installation details: Product Result More Info 1. Solaris 2.5.1 Hardware: 11/97 Installed Available 2. Additional Software Installed Available 3. Done Enter the number corresponding to the desired selection for more information, or Done to continue [3]: The system needs to reboot to complete installation. 10) As instructed press . NO reboot will be undertaken and you will be able to install the relevant sf patch. # # # df -k Filesystem kbytes used avail capacity Mounted on /tmp 977384 3720 973664 1% /tmp /proc 0 0 0 0% /proc /tmp/devices 977384 3720 973664 1% /devices /tmp/dev 977384 3720 973664 1% /dev fd 0 0 0 0% /dev/fd /devices/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020378963b8,0:b 962571 289221 615596 32% / /dev/dsk/c0t6d0s0 570023 260305 252716 51% /a /dev/dsk/c0t6d0s7 15805887 9 15647820 1% /a/export/home 11) Obtain the following patch from another host on the network through ftp or from a CD: # ./105310-14/installpatch -R /a ./105310-14 WARNING: /usr/sbin/patchadd is being used to install this patch. Checking installed patches... Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch number 105310-14 has been successfully installed. See /a/var/sadm/patch/105310-14/log for details Patch packages installed: SUNWluxal SUNWluxdv SUNWluxop 12) To complete installation issue a reboot: # reboot 13) At this stage you should bring all of the patches on the system up-to-date as would be undertaken for a normal install. Reboot the system after patch installation was successfully completed. --------------- End 2.5.1 Workaround --------------------- Workaround Procedure for Solaris 2.6 ====================================================================== The workaround for Solaris 2.6 is the same as for 2.5.1, except: 1) Use the 2.6-5/98 CD instead of the 2.5.1-11/97 CD. 2) Three 2.6 patches are required to be loaded at Step 11. Install in this order: 105356-09, 105357-04 and 105375-25. Use 'patchadd' to install the patches instead of 'installpatch'. Example: # /a/usr/sbin/patchadd -R /a ./105357-02 -------------- End 2.6 Workaround -------------------------
Comments: 
----------------------------------------------------------------------------
Implementation Footnote: 
i)   In case of MANDATORY FINs, Enterprise Services will attempt to    
     contact all affected customers to recommend implementation of 
     the FIN. 
   
ii)  For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical    
     support teams will recommend implementation of the FIN  (to their  
     respective accounts), at the convenience of the customer. 

iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the   
     need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network 
browser as follows:
 
SunWeb Access:
-------------- 
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/

* From there, select the appropriate link to query or browse the FIN and
  FCO Homepage collections.
 
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/

* From there, select the appropriate link to browse the FIN or FCO index.

Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist.  Edist can be 
  accessed internally at the following URL: http://edist.corp/.
  
* From there, follow the hyperlink path of "Enterprise Services Documenta- 
  tion" and click on "FIN & FCO attachments", then choose the appropriate   
  folder, FIN or FCO.  This will display supporting directories/files for 
  FINs or FCOs.
   
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
---------------------------------------------------------------------------
Statusactive