hi,
my netbackup (NB45MP6_HP_Linux_Solaris_265010 with Mappings_4.5_269174)
doesnt recognize the attached sun/l9 robotic lib with its drive.
i think the problems are about how nb wants the devices under /dev/ - i ran
/usr/openv/volmgr/bin/make_scsi_dev which should create devicenodes or links to
existing devnodes under /dev/sg/ and /dev/st/ - but it doesnt.
(maybe because there are no /dev/rmt devices??)
first of all - a little output...
the devices are connected - the l9 with its robot and drive
h0c0t0l0 for the robot
h0c0t1l0 for the drive
devices ################################################################################
nas01 /root # cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: HP Model: C7145-8000 Rev: 206S
Type: Medium Changer ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: QUANTUM Model: DLT8000 Rev: 023B
Type: Sequential-Access ANSI SCSI revision: 02
########################################################################################
this is what the devfsd looks like after rebooting.
calling /usr/openv/volmgr/bin/make_scsi_dev doesnt change anything - except that it
erases everything in /dev/sg/ and /dev/st/.
before make_scsi_dev ###################################################################
nas01 /root # ls -la /dev/st* /dev/sg* /dev/rm*
lr-xr-xr-x 1 root root 36 Aug 24 13:45 /dev/sg0 -> scsi/host0/bus0/target0/lun0/generic
lr-xr-xr-x 1 root root 36 Aug 24 13:45 /dev/sg1 -> scsi/host0/bus0/target1/lun0/generic
lr-xr-xr-x 1 root root 31 Aug 24 13:45 /dev/st0 -> scsi/host0/bus0/target1/lun0/mt
lr-xr-xr-x 1 root root 32 Aug 24 13:45 /dev/st0a -> scsi/host0/bus0/target1/lun0/mta
lr-xr-xr-x 1 root root 32 Aug 24 13:45 /dev/st0l -> scsi/host0/bus0/target1/lun0/mtl
lr-xr-xr-x 1 root root 32 Aug 24 13:45 /dev/st0m -> scsi/host0/bus0/target1/lun0/mtm
lr-xr-xr-x 1 root root 4 Aug 24 13:45 /dev/stderr -> fd/2
lr-xr-xr-x 1 root root 4 Aug 24 13:45 /dev/stdin -> fd/0
lr-xr-xr-x 1 root root 4 Aug 24 13:45 /dev/stdout -> fd/1
/dev/rmt:
total 0
drwxr-xr-x 1 root root 0 Aug 24 13:45 .
drwxr-xr-x 1 root root 0 Jan 1 1970 ..
/dev/sg:
total 0
drwxr-xr-x 1 root root 0 Aug 24 13:48 .
drwxr-xr-x 1 root root 0 Jan 1 1970 ..
/dev/st:
total 0
drwxr-xr-x 1 root root 0 Aug 24 13:48 .
drwxr-xr-x 1 root root 0 Jan 1 1970 ..
tape & robot are working ###############################################################
nas01 /usr/openv/volmgr/bin # mtx -f /dev/sg0 status
Storage Changer /dev/sg0:1 Drives, 9 Slots ( 0 Import/Export )
Data Transfer Element 0:Empty
Storage Element 1:Full :VolumeTag=DT5178
Storage Element 2:Full :VolumeTag=DT5177
Storage Element 3:Full :VolumeTag=DT5180
Storage Element 4:Full :VolumeTag=DT5176
Storage Element 5:Empty:VolumeTag=
Storage Element 6:Empty:VolumeTag=
Storage Element 7:Empty:VolumeTag=
Storage Element 8:Empty:VolumeTag=
Storage Element 9:Full :VolumeTag=CLN502
nas01 /usr/openv/volmgr/bin # scsitape -f /dev/sg1 read
########################################################################################
with the devfsd above nb (jnbSA) doesnt find anything - no drive, no robot.
netbackup "media manager device configuration guide" (.pdf at )
says that make_scsi_dev should create entries for robots under /dev/sg/
so i did a "ln -s /dev/sg0 /dev/sg/h0c0t0l0" (naming conventions from the .pdf above, page 123).
after that nb detects a robot (HP C7145-8000 206S) with the limitation "unable to determine robot type".
nb also detects that this robot has a drive attached at "address 1" but that there
are "no configuration details available" because "the drive is attached to another host".
nb device guide says on page 124-125 that make_scsi_dev should create entries for drives under /dev/st/,
so next thing was a "ln -s /dev/sg1 /dev/st/nh0c0t1l0".
no success - nb still finds a robot with a drive "which is attached to another host"
after removing /dev/st/nh0c0t1l0 and doing a "ln -s /dev/sg1 /dev/sg/h0c0t1l0" nb
detects 2 drives and a robot with one internal drive (as above).
the drives are unusable "general auto-detecton anomaly. no configuration device file exists".
with only the robot (wo drive) configured i can do a inventory robot (so much for the
unknown device) - and btw: this robot was successfully used with solaris8 and nb3.4 .
im sitting on this for the last few days doing permutations on various
dev-configuration possibilities - no success - so any help would be *really* appreciated.
regards, christoph a. mikusch
my netbackup (NB45MP6_HP_Linux_Solaris_265010 with Mappings_4.5_269174)
doesnt recognize the attached sun/l9 robotic lib with its drive.
i think the problems are about how nb wants the devices under /dev/ - i ran
/usr/openv/volmgr/bin/make_scsi_dev which should create devicenodes or links to
existing devnodes under /dev/sg/ and /dev/st/ - but it doesnt.
(maybe because there are no /dev/rmt devices??)
first of all - a little output...
the devices are connected - the l9 with its robot and drive
h0c0t0l0 for the robot
h0c0t1l0 for the drive
devices ################################################################################
nas01 /root # cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: HP Model: C7145-8000 Rev: 206S
Type: Medium Changer ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: QUANTUM Model: DLT8000 Rev: 023B
Type: Sequential-Access ANSI SCSI revision: 02
########################################################################################
this is what the devfsd looks like after rebooting.
calling /usr/openv/volmgr/bin/make_scsi_dev doesnt change anything - except that it
erases everything in /dev/sg/ and /dev/st/.
before make_scsi_dev ###################################################################
nas01 /root # ls -la /dev/st* /dev/sg* /dev/rm*
lr-xr-xr-x 1 root root 36 Aug 24 13:45 /dev/sg0 -> scsi/host0/bus0/target0/lun0/generic
lr-xr-xr-x 1 root root 36 Aug 24 13:45 /dev/sg1 -> scsi/host0/bus0/target1/lun0/generic
lr-xr-xr-x 1 root root 31 Aug 24 13:45 /dev/st0 -> scsi/host0/bus0/target1/lun0/mt
lr-xr-xr-x 1 root root 32 Aug 24 13:45 /dev/st0a -> scsi/host0/bus0/target1/lun0/mta
lr-xr-xr-x 1 root root 32 Aug 24 13:45 /dev/st0l -> scsi/host0/bus0/target1/lun0/mtl
lr-xr-xr-x 1 root root 32 Aug 24 13:45 /dev/st0m -> scsi/host0/bus0/target1/lun0/mtm
lr-xr-xr-x 1 root root 4 Aug 24 13:45 /dev/stderr -> fd/2
lr-xr-xr-x 1 root root 4 Aug 24 13:45 /dev/stdin -> fd/0
lr-xr-xr-x 1 root root 4 Aug 24 13:45 /dev/stdout -> fd/1
/dev/rmt:
total 0
drwxr-xr-x 1 root root 0 Aug 24 13:45 .
drwxr-xr-x 1 root root 0 Jan 1 1970 ..
/dev/sg:
total 0
drwxr-xr-x 1 root root 0 Aug 24 13:48 .
drwxr-xr-x 1 root root 0 Jan 1 1970 ..
/dev/st:
total 0
drwxr-xr-x 1 root root 0 Aug 24 13:48 .
drwxr-xr-x 1 root root 0 Jan 1 1970 ..
tape & robot are working ###############################################################
nas01 /usr/openv/volmgr/bin # mtx -f /dev/sg0 status
Storage Changer /dev/sg0:1 Drives, 9 Slots ( 0 Import/Export )
Data Transfer Element 0:Empty
Storage Element 1:Full :VolumeTag=DT5178
Storage Element 2:Full :VolumeTag=DT5177
Storage Element 3:Full :VolumeTag=DT5180
Storage Element 4:Full :VolumeTag=DT5176
Storage Element 5:Empty:VolumeTag=
Storage Element 6:Empty:VolumeTag=
Storage Element 7:Empty:VolumeTag=
Storage Element 8:Empty:VolumeTag=
Storage Element 9:Full :VolumeTag=CLN502
nas01 /usr/openv/volmgr/bin # scsitape -f /dev/sg1 read
########################################################################################
with the devfsd above nb (jnbSA) doesnt find anything - no drive, no robot.
netbackup "media manager device configuration guide" (.pdf at )
says that make_scsi_dev should create entries for robots under /dev/sg/
so i did a "ln -s /dev/sg0 /dev/sg/h0c0t0l0" (naming conventions from the .pdf above, page 123).
after that nb detects a robot (HP C7145-8000 206S) with the limitation "unable to determine robot type".
nb also detects that this robot has a drive attached at "address 1" but that there
are "no configuration details available" because "the drive is attached to another host".
nb device guide says on page 124-125 that make_scsi_dev should create entries for drives under /dev/st/,
so next thing was a "ln -s /dev/sg1 /dev/st/nh0c0t1l0".
no success - nb still finds a robot with a drive "which is attached to another host"
after removing /dev/st/nh0c0t1l0 and doing a "ln -s /dev/sg1 /dev/sg/h0c0t1l0" nb
detects 2 drives and a robot with one internal drive (as above).
the drives are unusable "general auto-detecton anomaly. no configuration device file exists".
with only the robot (wo drive) configured i can do a inventory robot (so much for the
unknown device) - and btw: this robot was successfully used with solaris8 and nb3.4 .
im sitting on this for the last few days doing permutations on various
dev-configuration possibilities - no success - so any help would be *really* appreciated.
regards, christoph a. mikusch