sg driver failed to Attache

[Mourad]

Hi All,

       I have a issue with tape driver and media changer which are not discovered by Netbackup, I followed the device configuration guide, many times, without success, I checked on Symantec forum, web, nothing helped me.

My configuration is the following :

Server : Sun Fire X4170 M2
OS : Solaris 10 x86, 8/11,  147441-13.
Tape Library : SUN SL48 SAS, 1 x LTO4.
Netbackup Server 7.1.

So when building the sg driver I'm getting the following error :

-bash-3.2# cd /usr/openv/volmgr/bin/driver

-bash-3.2# /usr/openv/volmgr/bin/sg.build all -mt 15 -ml 1

The file ./st.conf should be appended to /kernel/drv/st.conf.

A reboot may be necessary to create any new device files.

Created file ./sg.conf.

Created file ./sg.links.

-bash-3.2#

-bash-3.2#  /usr/bin/rm -f /kernel/drv/sg.conf

-bash-3.2#  /usr/openv/volmgr/bin/driver/sg.install

        Copied files to /kernel/drv/amd64.

Doing add_drv of the sg driver

devfsadm: driver failed to attach: sg

Warning: Driver (sg) successfully added to system but failed to attach

Removing old /dev/sg entries.

Editing /etc/devlink.tab...

Copying original /etc/devlink.tab to /etc/devlink.tab.06-09-12-21:33:06.

Added entry in /etc/devlink.tab file.

Made links in /dev/sg

-bash-3.2# 

-bash-3.2# 

-bash-3.2#  /usr/openv/volmgr/bin/sgscan tape

-bash-3.2#

The tape driver and media changed are seen on the OS level :

-bash-3.2# cfgadm -al 

Ap_Id                          Type         Receptacle   Occupant     Condition

c0                             scsi-bus     connected    configured   unknown

c0::dsk/c0t0d0                 disk         connected    configured   unknown

c2                             scsi-sas     connected    unconfigured unknown

c3                             scsi-sas     connected    configured   unknown

c3::rmt/0                      tape         connected    configured   unknown

c3::scsi/changer/c3t500143801  med-changer  connected    configured   unknown

sata0/0                        sata-port    empty        unconfigured ok

sata0/1                        sata-port    empty        unconfigured ok

sata0/2                        sata-port    empty        unconfigured o

thank you in advance for any help.

Regards.

[Marianne]

Did you disable MPxIO as per Device Config Guide? We have seen a similar case about 2 weeks ago on this forum where robot was only discovered after mpxio was disabled.

[Mourad]

Hi Marianne,

          Yes, I did, (and rebooted with -r many times)

#
# You can describe a list of target port WWNs and LUN numbers which will
# not be configured. LUN numbers will be interpreted as decimal. White
# spaces and ',' can be used in the list of LUN numbers.
#
# pwwn-lun-blacklist=
# "target-port-wwn,lun-list"
#
# To prevent LUNs 1 and 2 from being configured for target
# port 510000f010fd92a1 and target port 510000e012079df1, set:
#
# pwwn-lun-blacklist=
# "510000f010fd92a1,1,2",
# "510000e012079df1,1,2";
mpxio-disable="yes";

Regards.

[Mourad]

Hi,

I have more input from my configuration which shows that the tape drive is managed by the st driver, but when displaying the device path, it's not like st@target,LUN !!! and when building the sg driver we specify -mt target -ml lun, and in my case the target is something like a WWN for the FC devices !!!

-bash-3.2# ls -lh /dev/rmt/0
lrwxrwxrwx   1 root     root          85 Jun  9 22:11 /dev/rmt/0 -> ../../devices/pci@0,0/pci8086,340e@7/pci1000,30b0@0/iport@8/tape@w500143801403b8c3,0:

-bash-3.2# grep iport /etc/path_to_inst
"/pci@0,0/pci8086,340e@7/pci1000,30b0@0/iport@v0" 1 "mpt_sas"
"/pci@0,0/pci8086,340e@7/pci1000,30b0@0/iport@8" 2 "mpt_sas"
"/pci@0,0/pci8086,340e@7/pci1000,30b0@0/iport@8/tape@w500143801403b8c3,0" 0 "st"
"/pci@0,0/pci8086,340e@7/pci1000,30b0@0/iport@8/medium-changer@w500143801403b8c3,1" 1 "sgen"

Regards.

[Mourad]

Hi,

Since few days, I found the following doc which is similar to my case, it states that the SAS 6G HBA are not compatible with the mpt_sas OS driver. and it says that the workaround is to disable the MPXIO, which is disabled in my configuration.
 

http://www.symantec.com/business/support/index?page=content&id=TECH140072

Regards.

[Mourad]

Hi,

May be it's a license issue, Do I need SAN license (Netbackup Enteprise) to use the SAS tape library ???

Regards.

[Marianne]

Only Library based tape drive license is needed in addition to NBU server license.

Certain Solaris patch levels 'break' sg driver - see http://www.symantec.com/docs/TECH56850