01-11-2011 10:30 AM
I'm on Solaris 10 master, NetBackup 7.0.1. My media server on which I'm having an issue is Solaris 10, NetBackup 7.0.1 Advanced Disk (PureDisk). I replaced a tape drive yesterday and then ran the sg.install. When I run the sgscan command it finds all the tape drives but not the disk drives - local or SAN attached. I've never seen this happen to disk before. Any ideas?
cfgadm sees both tape and disk
c1 fc-private connected configured unknown
c1::500000e01066d351,0 disk connected configured unknown
c1::500000e010670831,0 disk connected configured unknown
c2 fc-fabric connected configured unknown
c2::500507630061457b,0 tape connected configured unknown
c2::5005076300616ff2,0 tape connected configured unknown
c2::5005076300617c17,0 tape connected configured unknown
c2::5005076300617d51,0 tape connected configured unknown
c2::500507630061eedd,0 tape connected configured unknown
c2::5005076313600e16,0 tape connected configured unknown
c2::5005076313600e64,0 tape connected configured unknown
c2::5005076313601021,0 tape connected configured unknown
c2::50050763136010c8,0 tape connected configured unknown
c2::50050763136011f5,0 tape connected configured unknown
c2::5005076313601214,0 tape connected configured unknown
c2::5005076313601287,0 tape connected configured unknown
c2::50050763136012a4,0 tape connected configured unknown
c2::5005076313601ead,0 tape connected configured unknown
c2::5005076313606f7b,0 tape connected configured unknown
c2::5005076313607556,0 tape connected configured unknown
c2::500507631360780a,0 tape connected configured unknown
c2::5005076313607cd3,0 tape connected configured unknown
c2::500507631360a57e,0 tape connected configured unknown
c2::500507631360a9b2,0 tape connected configured unknown
c3 fc connected unconfigured unknown
c4 fc-fabric connected configured unknown
c4::50060e8003a80100,0 disk connected configured unknown
c4::50060e8003a80100,1 disk connected configured unknown
c4::50060e8003a80100,2 disk connected configured unknown
c4::50060e8003a80100,3 disk connected configured unknown
c4::50060e8003a80100,4 disk connected configured unknown
c4::50060e8003a80100,5 disk connected configured unknown
c4::50060e8003a80100,6 disk connected configured unknown
c4::50060e8003a80100,7 disk connected configured unknown
c4::50060e8003a80100,8 disk connected configured unknown
c4::50060e8003a80100,9 disk connected configured unknown
c5 fc-fabric connected configured unknown
c5::50060e8003a80110,0 disk connected configured unknown
c5::50060e8003a80110,1 disk connected configured unknown
c5::50060e8003a80110,2 disk connected configured unknown
c5::50060e8003a80110,3 disk connected configured unknown
c5::50060e8003a80110,4 disk connected configured unknown
c5::50060e8003a80110,5 disk connected configured unknown
c5::50060e8003a80110,6 disk connected configured unknown
c5::50060e8003a80110,7 disk connected configured unknown
c5::50060e8003a80110,8 disk connected configured unknown
c5::50060e8003a80110,9 disk connected configured unknown
format sees the disk
AVAILABLE DISK SELECTIONS:
0. c6t50060E80000000000000A801000000A8d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB>
/scsi_vhci/ssd@g50060e80000000000000a801000000a8
1. c6t50060E80000000000000A801000000C0d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB>
/scsi_vhci/ssd@g50060e80000000000000a801000000c0
2. c6t50060E80000000000000A801000000D8d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB>
/scsi_vhci/ssd@g50060e80000000000000a801000000d8
3. c6t50060E80000000000000A80100000030d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB>
/scsi_vhci/ssd@g50060e80000000000000a80100000030
4. c6t50060E80000000000000A80100000018d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB>
/scsi_vhci/ssd@g50060e80000000000000a80100000018
5. c6t50060E80000000000000A80100000000d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB>
/scsi_vhci/ssd@g50060e80000000000000a80100000000
6. c6t50060E80000000000000A80100000090d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB>
/scsi_vhci/ssd@g50060e80000000000000a80100000090
7. c6t50060E80000000000000A80100000078d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB>
/scsi_vhci/ssd@g50060e80000000000000a80100000078
8. c6t50060E80000000000000A80100000060d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB>
/scsi_vhci/ssd@g50060e80000000000000a80100000060
9. c6t50060E80000000000000A80100000048d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB>
/scsi_vhci/ssd@g50060e80000000000000a80100000048
10. c6t500000E01066D350d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/scsi_vhci/ssd@g500000e01066d350
11. c6t500000E010670830d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/scsi_vhci/ssd@g500000e010670830
sg.conf has proper entries for disk and tape:
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500000e01066d351";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500000e010670831";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50060e8003a80100";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50060e8003a80110";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313600e16";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313601ead";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076300617d51";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507631360a9b2";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507630061457b";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313601287";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076300616ff2";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313601021";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50050763136012a4";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50050763136010c8";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50050763136011f5";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076300617c17";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313600e64";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507631360a57e";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313607cd3";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313606f7b";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313601214";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507630061eedd";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313607556";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507631360780a";
but sgscan does not see disk:
/dev/sg/c0tw500507630061457bl0: Tape (/dev/rmt/21): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076300616ff2l0: Tape (/dev/rmt/6): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076300617c17l0: Tape (/dev/rmt/11): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076300617d51l0: Tape (/dev/rmt/2): "IBM ULTRIUM-TD2"
/dev/sg/c0tw500507630061eeddl0: Tape (/dev/rmt/17): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313600e16l0: Tape (/dev/rmt/0): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313600e64l0: Tape (/dev/rmt/12): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313601021l0: Tape (/dev/rmt/7): "IBM ULTRIUM-TD2"
/dev/sg/c0tw50050763136010c8l0: Tape (/dev/rmt/9): "IBM ULTRIUM-TD2"
/dev/sg/c0tw50050763136011f5l0: Tape (/dev/rmt/10): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313601214l0: Tape (/dev/rmt/16): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313601287l0: Tape (/dev/rmt/5): "IBM ULTRIUM-TD2"
/dev/sg/c0tw50050763136012a4l0: Tape (/dev/rmt/8): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313601eadl0: Tape (/dev/rmt/4): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313606f7bl0: Tape (/dev/rmt/15): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313607556l0: Tape (/dev/rmt/18): "IBM ULTRIUM-TD2"
/dev/sg/c0tw500507631360780al0: Tape (/dev/rmt/19): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313607cd3l0: Tape (/dev/rmt/14): "IBM ULTRIUM-TD2"
/dev/sg/c0tw500507631360a57el0: Tape (/dev/rmt/20): "IBM ULTRIUM-TD2"
/dev/sg/c0tw500507631360a9b2l0: Tape (/dev/rmt/1): "IBM ULTRIUM-TD2"
here's the steps I took to update:
1. devfsadm –C
2. cfgadm -al -o show_FCP_dev
3. cfgadm -c configure c2
4. mv /usr/openv/volmgr/bin/sg.conf /usr/openv/volmgr/bin/sg.conf.old
5. /usr/openv/volmgr/bin/sg.build all -mt 20 -ml 0
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
6. mv /etc/devlink.tab /etc/devlink.tab.old
7. cp /usr/openv/volmgr/bin/sg.links /etc/devlink.tab
8. mv /kernel/drv/sg.conf /kernel/drv/sg.conf.05122005
9. cp /usr/openv/volmgr/bin/sg.conf /kernel/drv/
10. devlinks
11. rem_drv sg
12. cd /dev/sg
13. rm *
14. /usr/openv/volmgr/bin/driver/sg.install
Copied files to /kernel/drv and to /kernel/drv/sparcv9.
Doing add_drv of the sg driver
Leaving existing sg configuration.
If you wish to update the configuration you need to
rm -f /kernel/drv/sg.conf
and rerun /usr/openv/volmgr/bin/driver/sg.install.
15. /usr/openv/volmgr/bin/sgscan
/dev/sg/c0tw500507630061457bl0: Tape (/dev/rmt/21): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076300616ff2l0: Tape (/dev/rmt/6): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076300617c17l0: Tape (/dev/rmt/11): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076300617d51l0: Tape (/dev/rmt/2): "IBM ULTRIUM-TD2"
/dev/sg/c0tw500507630061eeddl0: Tape (/dev/rmt/17): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313600e16l0: Tape (/dev/rmt/0): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313600e64l0: Tape (/dev/rmt/12): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313601021l0: Tape (/dev/rmt/7): "IBM ULTRIUM-TD2"
/dev/sg/c0tw50050763136010c8l0: Tape (/dev/rmt/9): "IBM ULTRIUM-TD2"
/dev/sg/c0tw50050763136011f5l0: Tape (/dev/rmt/10): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313601214l0: Tape (/dev/rmt/16): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313601287l0: Tape (/dev/rmt/5): "IBM ULTRIUM-TD2"
/dev/sg/c0tw50050763136012a4l0: Tape (/dev/rmt/8): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313601eadl0: Tape (/dev/rmt/4): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313606f7bl0: Tape (/dev/rmt/15): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313607556l0: Tape (/dev/rmt/18): "IBM ULTRIUM-TD2"
/dev/sg/c0tw500507631360780al0: Tape (/dev/rmt/19): "IBM ULTRIUM-TD2"
/dev/sg/c0tw5005076313607cd3l0: Tape (/dev/rmt/14): "IBM ULTRIUM-TD2"
/dev/sg/c0tw500507631360a57el0: Tape (/dev/rmt/20): "IBM ULTRIUM-TD2"
/dev/sg/c0tw500507631360a9b2l0: Tape (/dev/rmt/1): "IBM ULTRIUM-TD2"
16. Run the Configure Storage Devices wizard in NetBackup.
Solved! Go to Solution.
01-11-2011 12:19 PM
I find the steps that you follow to rebuild the sg drivers 'different' to say the least.
sg.links should not be copied 'as is' to /etc/devlink.tab - the sg.install step will APPEND entries to devlink.tab. Extract from Device Config Guide (text version also in /usr/openv/volmgr):
The NetBackup sg.install script does the following:
* Installs and loads the sg driver.
* Copies the /usr/openv/volmgr/bin/driver/sg.conf file to /kernel/drv/sg.conf.
* Creates the /dev/sg directory and nodes.
* Appends the /usr/openv/volmgr/bin/driver/sg.links file to the /etc/devlink.tab file.
I have always followed these steps (found in Device Config Guide as well as this TN: http://www.symantec.com/docs/TECH71073) :
# cd /usr/openv/volmgr/bin/driver
# /usr/openv/volmgr/bin/sg.build all -mt <32> -ml <1> ### Check device paths to determine number of targets and luns###
Install the new sg driver configuration:
# /usr/bin/rm -f /kernel/drv/sg.conf
# /usr/openv/volmgr/bin/driver/sg.install
# /usr/openv/volmgr/bin/sgscan
01-11-2011 12:19 PM
I find the steps that you follow to rebuild the sg drivers 'different' to say the least.
sg.links should not be copied 'as is' to /etc/devlink.tab - the sg.install step will APPEND entries to devlink.tab. Extract from Device Config Guide (text version also in /usr/openv/volmgr):
The NetBackup sg.install script does the following:
* Installs and loads the sg driver.
* Copies the /usr/openv/volmgr/bin/driver/sg.conf file to /kernel/drv/sg.conf.
* Creates the /dev/sg directory and nodes.
* Appends the /usr/openv/volmgr/bin/driver/sg.links file to the /etc/devlink.tab file.
I have always followed these steps (found in Device Config Guide as well as this TN: http://www.symantec.com/docs/TECH71073) :
# cd /usr/openv/volmgr/bin/driver
# /usr/openv/volmgr/bin/sg.build all -mt <32> -ml <1> ### Check device paths to determine number of targets and luns###
Install the new sg driver configuration:
# /usr/bin/rm -f /kernel/drv/sg.conf
# /usr/openv/volmgr/bin/driver/sg.install
# /usr/openv/volmgr/bin/sgscan
01-11-2011 01:11 PM
That worked Marianne! I'll update my directions.