Ryan,

    This may sound too simplistic and you may already have done it, but 
have you verified that the update process did not inadvertently change any 
of the SG config files (ie. /kernel/drv/sg.conf , /etc/devlink.tab, and 
the files in /usr/openv/volmgr/bin/driver).  It sounds like the system is 
using the default files or data from them and not ones you would have 
created when you did the 3.2 install.

-- Tony Guzzi
Solutions Engineer, AssuredRestore team
Storability, Inc.
118 Turnpike Road
Southborough, MA 01772



Date: Wed, 23 May 2001 16:04:35 -0500
From: RYAN ANDERSON <RYAN_ANDERSON AT udlp DOT com>
Organization: United Defense LP
To: Veritas NBU <veritas-bu AT mailman.eng.auburn DOT edu>
Subject: [Veritas-bu] Drives useable; not recognized

In upgrading NetBackup from 3.2 to 3.4 on Solaris 2.6 there was a part
where the install script discovered only 6 of our 10 DLT7K drives. After
the upgrade, I had to readd in the 4 drives with SCSI ids over 7 via
tpconfig. 

Since then the drives have worked fine and are useable by Media Manager.
However, doing a simple sgscan doesn't see them, and upon restarting
NetBackup I get these messages:

avrd[562]: Unable to find sg device
/devices/pci@6,4000/scsi@3/sg@8,0:raw, using open() for scanning
avrd[562]: Unable to find sg device
/devices/pci@6,4000/scsi@3/sg@9,0:raw, using open() for scanning
avrd[562]: Unable to find sg device
/devices/pci@6,4000/scsi@4/sg@a,0:raw, using open() for scanning
avrd[562]: Unable to find sg device
/devices/pci@6,4000/scsi@4/sg@b,0:raw, using open() for scanning


The only discrepancy I find is that it appears from the output of the
undocumented command 'vmglob -listall' that the drives it doesn't
initially recognize don't have serial numbers listed. 

What is the workaround to have my DLT drives recognized?


Thanks,

RCA
--
Ryan Anderson          | United Defense L.P.
ryan_anderson AT udlp DOT com | pager 763.572.6684