Technical article 126841

How to setup and configure a HP StorageWorks Ultrium LTO-2 448, LTO-3 920 and LTO-4 1760 / 1840 SAS Tape Drive connected to LSI SAS3800X SAS controller on SCO OpenServer 5.0.7 / OpenServer 6.0.0 & UnixWare 7.1.4?

OpenServer 6.0.0OpenServer 5.0.7UnixWare 7.1.4

Written · Last revised

Problem

How to setup and configure a HP StorageWorks LTO Ultrium LTO-2 448 SAS Tape Drive connected to LSI SAS3800X SAS controller on SCO OpenServer 5.0.7 / OpenServer 6.0.0 & Unixware 7.1.4?

HARDWARE: HP StorageWorks Ultrium LTO-2 448 SAS Tape Drive
          HP StorageWorks Ultrium LTO-3 920 SAS Tape Drive
          HP StorageWorks Ultrium LTO-4 1760 SAS Tape Drive
          HP StorageWorks Ultrium LTO-4 1840 SAS Tape Drive
          LSI Logic 1064 SAS chip Integrated Controller
          LSI Logic 1067 SAS chip Integrated Controller
          LSI Logic 1068 SAS chip Integrated Controller
          LSI Logic SAS3800X SAS Controller
NOTE:     SAS is nothing but an advanced SCSI technology.

Therefore, it should be treated as a SCSI device under SCO UNIX. All SAS drives attached to a SAS controller will have a unique SCSI-ID which is automatically allocated to it by the SAS controller.

There is no manual SCSI-ID configuration facility on SAS drives.

Solution

In the example below, the HP StorageWorks Ultrium LTO-2 448 SAS Tape drive is connected to a LSI 1068 SAS chip Integrated Controller on a Fujitsu Siemens Primergy TX150-S5 Server.

For SCO OpenServer 5.0.7
------------------------
Please Note:

The BTLD driver "lsil" ver. 1.04.09 is available to download from:

http://www.sco.com/support/update/download/release.php?rid=192

(The latest OSR507 lsil BTLD is on the btld1.img image)

Boot the server and check what SAS device the LSI 1068 SAS IC BIOS detects. Look for the HP SAS Tape Drive.

In our example, the LSI 1068 SAS Chip found:

SLOT ID LUN VENDOR PRODUCT        REVISION SIZE/NV
---- -- --- ------ -------        -------- -------
 0   0   0  ATA    WDC WD800 TD   1E01     74 GB
 0   3   0  HP     Ultrium 2-SCSI T00V
 0          LSI    SAS1068-IR     1.18.40  NV25:15

Therefore, the Device IDs for the HP SAS Tape drive are:

Controller     = LSI (lsil BTLD)
controller No. = 0
BUS            = 0
Target ID      = 3
LUN            = 0

This information will be required when we run the "mkdev tape" command.

As root, run "mkdev tape" and select:

1. Configure a SCSI or Enhanced IDE tape drive

followed by
1. Install a SCSI Tape Drive

For the other responses below, see the response next to the <RETURN> (ENTER).

Enter the prefix of the SCSI host adapter that supports this device or press <Return> for the default: 'wd'

Enter h for a list of host adapters or enter
q to quit:  lsil <RETURN>

Which 'lsil' SCSI host adapter supports this device? Select 0-29, or enter q to quit: 0 <RETURN>

What SCSI Bus is this device attached to? Press <Return> to use the default:0 Select 0-n, or h for help, or q to quit: 0 <RETURN>

What is the Target ID for this device? Select 0-15, or h for help, or q to quit: 3 <RETURN>

What is the LUN of this device? Press <Return> to use the default: 0 Select 0-7, or h for help, or q to quit: 0 <RETURN>

You are about to add the following SCSI device:

      Host              Adapter
Type  Adapter  Device   Number  ID      LUN     Bus
-------------------------------------------------------
SCSI  lsil     tape     0       3       0       0
Update SCSI configuration? (y/n) y <RETURN>

The SCSI configuration file has been updated.

Updating system configuration ...
System files have been successfully updated.
Configuring Tape Driver ...( Stp )

Enter Vendor Identification string or press <Return> to use default or enter q to return to main menu: HP <RETURN>

Enter SCSI version that device is conformant to or press <Return> to use default or enter q to return to main menu: <just RETURN>

Enter Response Data Format that device uses or press <Return> to use default or enter q to return to main menu: <Just RETURN>

The following tape drive types are supported:

Select option 4
4.  DAT drive (Compressing and non-Compressing)
Tape Driver Successfully Configured
Default special devices have been created with the
following links:
        /dev/xct0       linked to  /dev/xStp0
        /dev/rct0       linked to  /dev/rStp0    and
        /dev/rmt/0b
        /dev/nrct0      linked to  /dev/nrStp0   and
        /dev/rmt/0bn
In /etc/default/boot:
No current boot string.

Enter new string, "rm" to remove string, or enter q to leave current string as is: q <RETURN>

Then "q" twice to exit the Tape Configuration Programm. Then "y" to relink the kernel.

The /etc/conf/cf.d/mscsi file in our example will look like this:

*ha     attach  number  ID      lun     bus
*
lsil    Sdsk    0       0       0       0
wd      Srom    0       0       0       0
wd      Srom    0       1       0       0
lsil    Stp     0       3       0       0
Reboot the server.
Please Note:

When the server is rebooted, a OpenServer 5.0.7 kernel gets loaded and the hardware is initialized and displayed, you get this WARNING message from the LSI controller at the stage it is initializing the HP SAS Tape:

WARNING: mpt: Device Status Change. SASAddress =
50060B00-0057E2A0, Target Id = 0x00000003 (3)
WARNING: mpt: Connected SAS device information
successfully saved
Thu Aug  9 16:53:14 2007
%Stp-0    -    -  -  Vnd=HP Prd=Ultrium 2-SCSI Rev=T00V

This is NOT a harmful message. This message just indicates that the HP SAS Tape SAS-Identification was successfully stored in the LSI SAS controller.

This message will only appear once. On next reboot, the message will no longer appear.

To test the access of HP StorageWorks Ultrium-2 448 SAS Tape drive:

# dtype /dev/rStp0
%Stp-0    -    -  -  Vnd=HP Prd=Ultrium 2-SCSI Rev=T00V
/dev/rStp0      : cpio old character format
The message:
%Stp-0    -    -  -  Vnd=HP Prd=Ultrium 2-SCSI Rev=T00V
indicates that the OSR507 rStp0 device has successfully
comunicated with the HP StorageWorks Ultrium-2 448 SAS
Drive and it read its identification from the Tape drive
EPROM "Vnd=HP Prd=Ultrium 2-SCSI Rev=T00V".

You can now tar, cpio or dd to the HP SAS Tape Drive.

For SCO OpenServer 6.0.0 & UnixWare 7.1.4
-----------------------------------------
Please Note:

The HBA driver "mpt" ver. 1.04.14 is available to download from SCO Website:

http://www.sco.com/support/update/download/release.php?rid=206

The HP StorageWork Ultrium-2 448 SAS Tape Drive gets auto-detected by the OS. No need to do any manual configuration.

# sdiconfig -l
0:0,112,0: HBA : (mpt,1)LSI Logic 1068 10414
  0,0,0: DISK  : ATA  WDC WD800JD-55MU1E01
  0,3,0: TAPE  : HP   Ultrium 2-SCSI  T00V  <-- OUR DEVICE
2:0,4,0: HBA   : (ahci,1) AHCI SATA
3:0,2,0: HBA   : (ide,1) Generic IDE/ATAPI
  0,0,0: CDROM : HL-DT-STDVDRAM GSA-H10N JH04

Assuming the Tape is the primary Tape device on your system (as the example above), then use /dev/rmt/ctape1 to access the SAS Tape drive.

NOTES:    The SAS speed is 3 GB/sec and the Tape drive itself
          has transfer rate of 173GB/hr (for Ultrium 448),
          432GB/hr (for Ultrium 920), 576GB/hr (for Ultrium 1760) or
          864GB/hr for (Ultrium 1840), so your backup on these
          SAS tape will be faster then a standard SCSI Tape
          Device.

However, that these numbers are only seen under ideal conditions and that normal backup rates will be slower then the above transfer rate values.

From the Xinuos technical article database, record 126841. Reproduced with permission. The original is at www.sco.com/ta/126841, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.