anthony.guzzi AT storability DOT com wrote:
> 
> 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.

This is an older post, but I just fixed it with the inputs I got from
the list. Indeed, the /kernel/drv/sg.conf and /etc/devlink.tab didn't
have any targets above 6 in them. I copied
/usr/openv/volmgrm/bin/driver/sg.links.all to sg.links and sg.conf.all
to sg.conf and reran sg.install. That didn't work, so I just appended
the sg.links.all file to /etc/devlink.tab and copied over sg.conf (from
NBU) to /kernel/drv/sg.conf, did a reboot and all is working fine now.


Thanks,

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