[Mtx-general] Painfully (obvious?) newbie question on MTX and X80(exabyte)
Brought to you by:
elgreen,
robertnelson
|
From: Bruntel, M. L, S. <mbr...@at...> - 2003-07-30 16:17:10
|
Hi using mtx version 1.2.17rel on solaris 5.8 (using amanda...)=20
Here's the question: how to reference stuff...
I Have (finally) succesfully gotten the drive/robot up=20
It does a inquiry and comes up with the following definition:
Storage Changer /dev/changer:3 Drives, 86 Slots ( 5 Import/Export )
Data Transfer Element 0:Full (Storage Element 6 Loaded):VolumeTag =3D =
A0000005
Data Transfer Element 1:Full (Storage Element 40 Loaded)
Data Transfer Element 2:Full (Storage Element 51 Loaded)
Storage Element 1:Full=20
Storage Element 2:Full :VolumeTag=3DIPO0028
..... A whole more... until I get to:
Storage Element 81:Full :VolumeTag=3DIPO0009
Storage Element 82 IMPORT/EXPORT:Empty
Storage Element 83 IMPORT/EXPORT:Empty
Storage Element 84 IMPORT/EXPORT:Empty
Storage Element 85 IMPORT/EXPORT:Empty
Storage Element 86 IMPORT/EXPORT:Empty
Some definitions: (according to the X80 manual from Exabyte (page 180 =
of the HW Manual)
shows the list of element assignments.
MTX shows:
Drive 0 as DTE 0
Drive 1 as DTE 1
Drive 2 as DTE 2
Exabyte shows
Drive 0 as Element 451
Drive 1 as Element 452
Drive 2 as Element 453
Similarly=20
MTX shows:
Import/Export Port1 as Storage Element 82
Import/Export Port2 as Storage Element 83
Import/Export Port3 as Storage Element 84
Import/Export Port4 as Storage Element 85
Import/Export Port5 as Storage Element 86
But Exabyte shows:
Import/Export Port1 as Element 401
Import/Export Port2 as Element 402
Import/Export Port3 as Element 403
Import/Export Port4 as Element 404
Import/Export Port5 as Element 405
Question 1
Fairly obvious (to me at least:)
trying to unload tape from drive 0
$>>mtx -f $CHANGER unload 6 0 (changer is /dev/scsi/changer/c1t0d0 )
Unloading Data Transfer Element into Storage Element 6...mtx: Request =
Sense: Long Report=3Dyes
mtx: Request Sense: Valid Residual=3Dno
mtx: Request Sense: Error Code=3D70 (Current)
mtx: Request Sense: Sense Key=3DIllegal Request
mtx: Request Sense: FileMark=3Dno
mtx: Request Sense: EOM=3Dno
mtx: Request Sense: ILI=3Dno
mtx: Request Sense: Additional Sense Code =3D 3B
mtx: Request Sense: Additional Sense Qualifier =3D 83
mtx: Request Sense: BPV=3Dno
mtx: Request Sense: Error in CDB=3Dno
mtx: Request Sense: SKSV=3Dno
MOVE MEDIUM from Element Address 451 to 5 Failed
mtx -f $CHANGER unload 6 451
illegal <drive-number> argument 'Segmentation Fault(coredump)
amanda@tape: /pkgs/amanda-stuff/amanda-2.4.4p1 $> =20
This (TO ME at least tells me that it LIKES the way MTX addresses the =
unit, as opposed to Exabyte's addressing scheme.
However: why is it failing?
|