sg.install error

[Jung-kuk_Lim]

Hi. all

setting the tape device in solaris 10.

[ntyfb:/usr/openv/volmgr/bin/driver]uname -a
SunOS ntyfb 5.10 Generic_138888-08 sun4u sparc SUNW,SPARC-Enterprise

then, I am fount tape device in OS

[ntyfb:/usr/openv/volmgr/bin/driver]iostat -En
c0t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MBB2147RC Revision: 3703 Serial No:
Size: 146.80GB <146800115712 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c0t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MBB2147RC Revision: 3703 Serial No:
Size: 146.80GB <146800115712 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c0t4d0 Soft Errors: 2 Hard Errors: 0 Transport Errors: 0
Vendor: MATSHITA Product: DVD-RAM UJ875AS Revision: 1.00 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis: 0
rmt/0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: IBM Product: ULT3580-TD4 Revision: 94D4 Serial No:
rmt/1 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: IBM Product: ULT3580-TD4 Revision: 94D4 Serial No:

[ntyfb:/usr/openv/volmgr/bin/driver]cfgadm -alv
Ap_Id Receptacle Occupant Condition Information
When Type Busy Phys_Id
SB0 connected configured ok powered-on, assigned
Jul 23 19:13 System_Brd n /devices/pseudo/dr@0:SB0
SB0::cpu0 connected configured ok cpuid 0, 1, 2, 3, 4, 5, 6, and 7, speed 2520 MHz, ecache 5 MBytes
Jul 23 19:13 cpu n /devices/pseudo/dr@0:SB0::cpu0
SB0::memory connected configured ok base address 0x0, 4194304 KBytes total, 577632 KBytes permanent
Jul 23 19:13 memory n /devices/pseudo/dr@0:SB0::memory
SB0::pci0 connected configured ok device /pci@0,600000, referenced
Jul 23 19:13 io n /devices/pseudo/dr@0:SB0::pci0
SB0::pci1 connected configured ok device /pci@1,700000, referenced
Jul 23 19:13 io n /devices/pseudo/dr@0:SB0::pci1
SB0::pci8 connected configured ok device /pci@8,4000, referenced
Jul 23 19:13 io n /devices/pseudo/dr@0:SB0::pci8
SB1 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB1
SB2 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB2
SB3 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB3
SB4 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB4
SB5 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB5
SB6 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB6
SB7 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB7
SB8 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB8
SB9 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB9
SB10 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB10
SB11 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB11
SB12 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB12
SB13 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB13
SB14 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB14
SB15 disconnected unconfigured unknown
Jul 23 19:13 n /devices/pseudo/dr@0:SB15
c0 connected configured unknown
unavailable scsi-bus n /devices/pci@0,600000/pci@0/pci@0/scsi@0:scsi
c0::dsk/c0t0d0 connected configured unknown FUJITSU MBB2147RC
unavailable disk n /devices/pci@0,600000/pci@0/pci@0/scsi@0:scsi::dsk/c0t0d0
c0::dsk/c0t1d0 connected configured unknown FUJITSU MBB2147RC
unavailable disk n /devices/pci@0,600000/pci@0/pci@0/scsi@0:scsi::dsk/c0t1d0
c0::dsk/c0t4d0 connected configured unknown MATSHITA DVD-RAM UJ875AS
unavailable CD-ROM n /devices/pci@0,600000/pci@0/pci@0/scsi@0:scsi::dsk/c0t4d0

and install the sg.install

[ntyfb:/usr/openv/volmgr/bin/driver]./sg.install

Copied files to /kernel/drv to /kernel/drv/sparcv9.

Doing add_drv of the sg driver

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

WARNING: /usr/sbin/add_drv failed.
There may be no SCSI devices on this machine

so, I find the this solution at symantec knowledge documents that OS patch.

[ntyfb:/usr/openv/volmgr/bin/driver]showrev -p | grep 138075
Patch: 137137-09 Obsoletes: 120741-01, 120986-12, 120992-02, 121008-02, 121274-01, 121414-01, 122029-01, 122083-02, 122172-06, 122174-03, 122356-01, 122358-01, 122517-04, 122525-03, 123186-03, 123809-02, 123932-02, 124999-01, 125416-06, 126133-04, 126145-01, 126304-01, 126653-01, 126661-02, 126674-01, 127714-03, 127735-02, 127739-03, 127866-05, 127868-01, 127886-06, 127888-11, 127892-06, 127914-01, 127959-02, 127968-01, 127970-01, 128294-02, 128400-05, 128408-01, 128410-01, 128413-01, 128493-01, 128548-08, 136885-04, 137042-01, 137045-01, 137050-01, 137086-01, 137091-01, 137099-01, 137109-01, 137111-08, 137119-01, 137127-01, 137135-01, 137139-01, 137280-02, 137287-01, 138042-05, 138048-05, 138050-01, 138051-01, 138052-01, 138054-01, 138056-02, 138060-04, 138064-03, 138066-01, 138068-01, 138070-03, 138072-02, 138074-01, 138075-02, 138108-01, 138125-01, 138127-01, 138225-02, 138229-02, 138233-01, 138237-01, 138243-02, 138249-01, 138251-01, 138257-01, 138259-01, 138265-01, 138271-04, 138273-01, 138277-01, 138279-01, 138280-01, 138284-04, 138305-01, 138306-01, 138308-02, 138310-01, 138312-01, 138314-01, 138315-01, 138316-01, 138363-01, 138365-01, 138379-01, 138390-02, 138394-01, 138401-01, 138899-01 Requires: 118731-01, 118822-24, 118833-36, 118918-24, 119254-58, 119374-09, 119578-30, 120011-14, 120900-04, 121133-02, 125503-02, 126897-02, 127127-11, 127755-01, 138866-01 Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWcsl, SUNWcar, SUNWcakr, FJSVvplr, FJSVhea, SUNWkvm, SUNWckr, SUNWcsd, SUNWcpcu, FJSVcpcu, SUNWib, SUNWfmd, FJSVfmd, SUNWesu, SUNWmdb, FJSVmdb, SUNWmdbr, FJSVmdbr, SUNWpiclu, FJSVpiclu, SUNWzfskr, SUNWsmapi, SUNWzfsr, SUNWzfsu, SUNWzoneu, SUNWs8brandr, SUNWcslr, SUNWs9brandr, SUNWssad, SUNWmdr, SUNWmdu, SUNWopenssl-libraries, SUNWwbsup, SUNWipfh, SUNWipfu, SUNWtoo, SUNWusb, SUNWtavor, SUNWudapltu, SUNWnfsckr, SUNWrsgk, SUNWnfscu, SUNWiscsitgtr, SUNWiscsitgtu, SUNWnfssu, SUNWarc, SUNWarcr, SUNWxcu4, SUNWpmu, SUNWpmr, SUNWdmgtu, SUNWnisu, SUNWypu, SUNWcpr, SUNWefc, SUNWpppd, SUNWfruip, SUNWdtrc, SUNWluxd, SUNWnxge, SUNWus, SUNWcry, SUNWrsg, SUNWpcu, SUNWefcl, SUNWhea, SUNWnfsskr, SUNWnfssr, SUNWpd, SUNWpdu, SUNWrds, SUNWs8brandu, SUNWs9brandu, SUNWsshcu, SUNWsshdu, SUNWsshu

patch is not problem.

give me the other solution and hint.

thanks.

I am very tired..

[Anton_Panyushki · Accepted solution]

Ok, that is how we do it from A to Z.

I suppose the following steps are performed on the media server where new devices are attached to and SAN zoning is correct.

1. Remove or rename old /kernel/drv/sg.conf  file.

2. Unload sg kernel driver with modunload.

3.Remove all tape devices: rm /dev/rmt/*.

4. Configure HBAs and create new tape devices
# cfgadm –c configure <ctrl#>
# devfsadm –c tape
After completing this step you should have tape drives files in your /dev/rmt/.

5. Create sg.conf file:
# cd /usr/openv/volmgr/bin/driver
# /usr/openv/volmgr/bin/sg.build all –mt 1 -ml 1 (if you have VTL attached to your media server, increase max LUN number.)

6. Installnewly configured sg driver:
# /usr/openv/volmgr/bin/driver/sg.install

7. Check if NetBackup "sees" newly attached devices
# /usr/openv/volmgr/bin/sgscan all (Parse sgscan output with grep or save it into file for further analysis)
You should make sure that the number of your tape drives matches your zoning.

8. Start NetBackup
# /etc/init.d/netbackup start on the media server where you made changes.

9. Run device configuration wizard to populate EMM with new devices.


Please feel free to critisize me.

[BMU]

this is how i do it  which is slightly the same as anton , i just give more target and luns ..

rm /dev/sg/*
/usr/sbin/rem_drv sg
rm -f /kernel/drv/sg.conf
cd /usr/openv/volmgr/bin/driver ; /usr/openv/volmgr/bin/sg.build sg.links -mt 5 -ml 5 -sl ./sg.links
cd /usr/openv/volmgr/bin/driver ; /usr/openv/volmgr/bin/sg.build sg.conf -mt 5 -ml 5 -sc ./sg.conf
cd /usr/openv/volmgr/bin/driver ; ./sg.install


Then i run /usr/openv/volmgr/bin/sgscan

don't forget to get the latest mappings for lto4 then load them into emm as astated here

http://seer.entsupport.symantec.com/docs/328211.htm

[Yasuhisa_Ishika]

Run "ls -l /dev/rmt/[0-9]" and identify target id and lun of each drive. You can identify them from symbolic link taget. It shows /devices/..../st@X,Y; X stands for target id, and Y stands for lun. When you run sg.build, supply most higest target id with -mt option, and most highest lun with -ml option. If tartget id isn't shown by numeric form, supply 6(default) as mt instead.