I belive this is caused by a missing passthu device drivers. Does  /usr/openv/volmgr/bin/scan report the pass-thru device driver:

thanks for your response Nicolai..

Yes it does list the passthru drive see below. but what it doesnt list is device name..

Device Name  : "-"
Passthru Name: "/dev/sg4"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULTRIUM-TD3     93GE"
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD3     "
Product Rev: "93GE"
Serial Number: "F0A1D28004"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD3     F0A1D28004"
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x10000
------------------------------------------------------------
Device Name  : "-"
Passthru Name: "/dev/sg3"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULTRIUM-TD3     93GE"
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD3     "
Product Rev: "93GE"
Serial Number: "F0A1D28000"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD3     F0A1D28000"
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x10000
 

any idea?

Here is your issue:

Device Name  : "-"

Your device paths are not showing up!!

Run through the device configuration again.

Yes - this look funny. I got some SUSE 11 as well on 64bit - No issues.

Found this T/N  regarding the "-" device name : http://www.symantec.com/docs/TECH75396

If this server is replacing a older 6.5.0 to 6.5.4 server - bring Netbackup to 6.5.5 for SuSE 11 support: http://www-secure.symantec.com/connect/forums/suse-11-device-name

Thanks Guys. Think upgrading to 6.5.5 is the only way to go.. i have followed these technote but no joy.. rebooted the media server few times but no luck.. Strangely when i run this mt command it shows no medium fount instead of input/output error?

rdx-gfihkg:/ # mt -f /dev/nst1 status
mt: /dev/nst1: rmtioctl failed: No medium found
rdx-gfihkg:/ # mt -f /dev/nst0 status
mt: /dev/nst0: rmtioctl failed: No medium found
rdx-gfihkg:/ # mt -f /dev/nst1 status
mt: /dev/nst1: rmtioctl failed: No medium found
rdx-gfihkg:/ # mt -f /dev/nst2 status
mt: /dev/nst2: rmtopen failed: No such file or directory
rdx-gfihkg:/ # lsmod | grep -w st
st                     39020  0
scsi_mod              178280  15 osst,st,qla2xxx,scsi_transport_fc,ses,scsi_tgt,sr_mod,sg,sd_mod,libata,mptspi,mptscsih,scsi_transport_spi,megaraid_sas
rdx-gfihkg:/ #
 

My whole setup is 6.5.3.1; i know its old but its been in there for like 5 years and stable and i am planning on upgrading them to 7.5.0.1... i need to plan thoroughly as i have one master and 5 media servers across 5 different remote sites in Asia..

Seems your server has lost connectivity to the devices.

Check /var/log/messages for errors.
Check physical connections.
Check robot for errors. Reboot robot.
Reboot server.

Run 'cat /proc/scsi/scsi' to check if devices are visible at OS level.

Thanks Marianne..

no it hasnt.. i have rebooted the server; checked all the logs; robot, drives are all in a good order; server can see the both robot and the drives.. can't think of anything else.. think its a compatibility issue as am running OS SLES 11 and its supports NBU 6.5.5 the minimum..

Host: scsi0 Channel: 00 Id: 32 Lun: 00
  Vendor: DP       Model: BACKPLANE        Rev: 1.07
  Type:   Enclosure                        ANSI  SCSI revision: 05
Host: scsi0 Channel: 02 Id: 00 Lun: 00
  Vendor: DELL     Model: PERC H700        Rev: 2.10
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: TSSTcorp Model: DVD+-RW TS-L633J Rev: D250
  Type:   CD-ROM                           ANSI  SCSI revision: 05
Host: scsi5 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: ULTRIUM-TD3      Rev: 93GE
  Type:   Sequential-Access                ANSI  SCSI revision: 03
Host: scsi6 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: ULTRIUM-TD3      Rev: 93GE
  Type:   Sequential-Access                ANSI  SCSI revision: 03
Host: scsi6 Channel: 00 Id: 00 Lun: 01
  Vendor: ADIC     Model: Scalar i500      Rev: 590G
  Type:   Medium Changer                   ANSI  SCSI revision: 03
 

Try to download and install updated Device Mappings files:

http://www.symantec.com/docs/TECH162165

Have done that already Marianne but no joy hence rever the changes..
I have the compatible device mapping files as per the HCL which are already latest than the 1.103?

rdx-gfihkg:~ # /usr/openv/volmgr/bin/tpext -get_dev_mappings_ver
device mappings version in the EMM database is 1.66.8.5
device mappings version from the local file is 1.66.8.5
Local device mappings file is up-to-date
 

Strange.... TechNote 162165 as well as 195399 were updated recently:

both mention version 1.103.

Back to your current problem - 

Please provide output of /usr/openv/volmgr/bin/scan

i know.. it is quite strange i noticed that too..

i have pasted the scan output up in the thread already so if you can have a look..

Is scan still showing Device Name as "-"          ?

Yes revaroo.. no joy..

No OS device entry is OS -> device issue.

I was interested the changer portion of scan output.

here it is Marianne.. interestingly the changer does have its device name..

rdx-gfihkg:~ # /usr/openv/volmgr/bin/scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name  : "-"
Passthru Name: "/dev/sg3"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULTRIUM-TD3     93GE"
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD3     "
Product Rev: "93GE"
Serial Number: "F0A1D28000"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD3     F0A1D28000"
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x10000
------------------------------------------------------------
Device Name  : "-"
Passthru Name: "/dev/sg4"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     ULTRIUM-TD3     93GE"
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD3     "
Product Rev: "93GE"
Serial Number: "F0A1D28004"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD3     F0A1D28004"
Device Type    : SDT_TAPE
NetBackup Drive Type: 16
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x10000
------------------------------------------------------------
Device Name  : "/dev/sg5"
Passthru Name: "/dev/sg5"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "ADIC    Scalar i500     590G"
Vendor ID  : "ADIC    "
Product ID : "Scalar i500     "
Product Rev: "590G"
Serial Number: "ADICA0C0161123_LLA"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "ADIC    A0C0161123_LLA          "
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 2
Number of Slots  : 33
Number of Media Access Ports: 6
Drive 1 Serial Number      : "F0A1D28000"
Drive 2 Serial Number      : "F0A1D28004"
Flags : 0x0
Reason: 0x0
 

hmm, I see the device name still showing as -

Have you checked your hba drivers are upto-date?

Yes revaroo.. am upgrading to 6.5.5 and see how it goes..

Don't fight windmills friends. If Symantec say 6.5.5 is required for SuSe 11 then 6.5.5 IS REQUIRED :-)

Spartacus81: Can you test if 6.5.6 works for you in a test environment ?