SL500 - Tape Drive Not Being Detected in Operating System

Asset ID:	1-72-1006989.1
Update Date:	2011-01-18
Keywords:

Solution Type Problem Resolution Sure

Solution 1006989.1 : SL500 - Tape Drive Not Being Detected in Operating System

Applies to:

Sun StorageTek SL500 Modular Library System - Version: Not Applicable and later [Release: N/A and later]
All Platforms
Checked for relevance on 18-Jan-2011.

Symptoms

Tape drive connected to Sun Storage[TM] L500 not getting detected in Operating System.

Changes

{CHANGE}

Cause

{CAUSE}

Solution

Resolution
Normally, Oracle/Storage SL500 Tape drive which comes from factory has SCSI ID of 15.

Upon connecting this drive using loop cable to chain it will cause the SCSI ID conflict and eventually failing to get detected in OBP or Bios itself.

To avoid this scenario, one needs to set the different SCSI ID's for different Tape Drive's before connecting to Host Machine.

This can be accomplished through CLI:

- After logging through the serial port on SL500 console, using "advsrv" login,

ADVSRV>> drive all

###get the drive it will be like <0,1,1,9> ####

ADVSRV>> drive 0,1,1,9 getconfig

####this command shoe current scsi id set to tape drive which is normally 15#####

ADVSRV>> drive 0,1,1,9 setconfig

####this will prompt for the new scsi id to set, set the scsi id in an order except 0(Robotic Arm)####

Note: Normally Robotic Arm comes with scsi id 0 so donot set this id to tape drives.

ADVSRV>>drive 0,1,1,9 getconfig

####check the newly set id reflects########

ADVSRV>>reboot Now connect your SL500 to Host machine which could detect it easily.

@ SL500, drive, detect, scsi id, bios
Previously Published As 87869

Attachments

This solution has no attachment