In your mtx command output one thing I don't see is the Data Transfer Unit
(i.e. tape drive) associated with the tape library.
For my tape library I get:
[root@bkupsvr3 ~]# mtx -f /dev/xchg0 status
Storage Changer /dev/xchg0:4 Drives, 179 Slots ( 2 Import/Export )
Data Transfer Element 0:Full (Storage Element 162 Loaded):VolumeTag = 000162L5
Data Transfer Element 1:Full (Storage Element 120 Loaded):VolumeTag = 000120L5
Data Transfer Element 2:Full (Storage Element 105 Loaded):VolumeTag = 000105L5
Data Transfer Element 3:Full (Storage Element 166 Loaded):VolumeTag = 000166L5
Storage Element 1:Full :VolumeTag=000001L5
Storage Element 2:Full :VolumeTag=000002L5
Storage Element 3:Full :VolumeTag=000003L5
Storage Element 4:Full :VolumeTag=000004L5
Storage Element 5:Full :VolumeTag=000005L5
Storage Element 6:Full :VolumeTag=000006L5
So I wondering does the library either not show drives or is there an issue
with the library seeing the tape drive.
I would investigate and make sure that the drive and library are connected
properly.
The output of "lsscsi -g" does who the tape drive?
-----Original Message-----
From: Richard Couture <r...@linuxcabal.org>
Sent: Friday, January 11, 2019 1:59 PM
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] mtx and mtx-changer not functioning
How odd
[root@LTOMag ~]# mt -f /dev/st0 offline
[root@LTOMag ~]# mtx -f /dev/sg3 unload 1 0 Data Transfer Element 0 is Empty
Now says the tape drive is empty
HOWEVER
[root@LTOMag ~]# mtx -f /dev/sg3 status
Storage Changer /dev/sg3:1 Drives, 30 Slots ( 5 Import/Export ) Data
Transfer Element 0:Empty
Storage Element 1:Empty:VolumeTag=
Storage Element 2:Full :VolumeTag=000002L7
Storage Element 3:Full :VolumeTag=000003L7
Storage Element 4:Full :VolumeTag=000004L7
Storage Element 5:Full :VolumeTag=000005L7
Storage Element 6:Full :VolumeTag=000006L7
Storage Element 7:Full :VolumeTag=000007L7
Storage Element 8:Full :VolumeTag=000008L7
Storage Element 9:Full :VolumeTag=000009L7
Storage Element 10:Full :VolumeTag=000010L7
Storage Element 11:Full :VolumeTag=000011L7
Storage Element 12:Full :VolumeTag=000012L7
Storage Element 13:Full :VolumeTag=000013L7
Storage Element 14:Full :VolumeTag=000014L7
Storage Element 15:Full :VolumeTag=000015L7
Storage Element 16:Full :VolumeTag=000016L7
Storage Element 17:Full :VolumeTag=000017L7
Storage Element 18:Full :VolumeTag=000018L7
Storage Element 19:Full :VolumeTag=000019L7
Storage Element 20:Full :VolumeTag=000020L7
Storage Element 21:Full :VolumeTag=000021L7
Storage Element 22:Full :VolumeTag=000022L7
Storage Element 23:Full :VolumeTag=000023L7
Storage Element 24:Full :VolumeTag=000024L7
Storage Element 25:Full :VolumeTag=000025L7
Storage Element 26 IMPORT/EXPORT:Full :VolumeTag=CLN005CU
Storage Element 27 IMPORT/EXPORT:Full :VolumeTag=CLN004CU
Storage Element 28 IMPORT/EXPORT:Full :VolumeTag=CLN003CU
Storage Element 29 IMPORT/EXPORT:Full :VolumeTag=CLN002CU
Storage Element 30 IMPORT/EXPORT:Empty:VolumeTag=
syas that the tape was not returned to slot 1
and just for fun
[root@LTOMag ~]# mtx -f /dev/sg3 unload
Data Transfer Element 0 is Empty
[root@LTOMag ~]# mtx -f /dev/sg3 next
Loading media from Storage Element 2 into drive 0...mtx: Request Sense:
Long Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=70 (Current)
mtx: Request Sense: Sense Key=Illegal Request
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 21
mtx: Request Sense: Additional Sense Qualifier = 01
mtx: Request Sense: Field in Error = 07
mtx: Request Sense: BPV=yes
mtx: Request Sense: Error in CDB=yes
mtx: Request Sense: SKSV=yes
mtx: Request Sense: Field Pointer = 00 02 MOVE MEDIUM from Element Address 4097
to 256 Failed
And physically checking; No tape in Slot 1, it remains in the drive
Richard
On 1/11/19 1:01 PM, Jeffrey R. Lang wrote:
> I have run into tape libraries that require the tape to be unloaded from the
> drive before performing an unload command.
>
> The mtx-changer script supports this feature. You need to change the
> .../etc/mtx-changer.conf file, specifically the line
>
> # Set to 1 if you want to do offline before unload
> offline=0
>
> In the example from below
>
> mtx -f /dev/sg3 load 1 0
> mtx -f /dev/sg3 unload 1 0
>
> add a command to unload the tape from the drive between the two lines
>
> mt -f <tape device> offline
>
> -----Original Message-----
> From: Sebastian Suchanek <bac...@suchanek.de>
> Sent: Friday, January 11, 2019 12:53 PM
> To: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] mtx and mtx-changer not functioning
>
> ◆ This message was sent from a non-UWYO address. Please exercise caution when
> clicking links or opening attachments from external sources.
>
>
> Am 11.01.2019 um 14:49 schrieb Richard Couture:
>
>>> Does mtx work when you explicitly specify the slots? I.e.:
>>>
>>> mtx -f /dev/sg3 load 1 0
>>> mtx -f /dev/sg3 unload 1 0
>>
>> No
>
> Then, in my opinion, the problem is somewhere outside of Bacula.
> My best guess is that either your library and your version of mtx are
> incompatible or your library is broken (e.g. faulty firmware).
>
>
> Best regards
>
> Sebastian
>
>
>
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
LinuxCabal Asociación Civil
Ing. Richard Couture
Novell CNE, ECNE, MCNE
HP/Compaq ASE
Tel.: (+52) (333) 145-2638
Cel.: (+52) (044) 333 377-7505
Web: http://www.LinuxCabal.org
E-Mail: r...@linuxcabal.org
Hosted en la nube Cloud Sigma - www.CloudSigma.com
AVISO DE CONFIDENCIALIDAD: Este correo electrónico, incluyendo en su caso, los
archivos adjuntos al mismo, pueden contener información de carácter
confidencial y/o privilegiada, y se envían a la atención única y exclusivamente
de la persona y/o entidad a quien va dirigido. La copia, revisión, uso,
revelación y/o distribución de dicha información confidencial sin la
autorización por escrito de LinuxCabal está prohibida. Si usted no es el
destinatario a quien se dirige el presente correo, favor de contactar al
remitente respondiendo al presente correo y eliminar el correo original
incluyendo sus archivos, así como cualesquiera copia del mismo. Mediante la
recepción del presente correo usted reconoce y acepta que en caso de
incumplimiento de su parte y/o de sus representantes a los términos antes
mencionados, LinuxCabal tendrá derecho a los daños y perjuicios que esto le
cause.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
