Hello, śr., 10 lis 2021 o 17:04 Jeffrey Di Domenico <jdidomen...@integrafin.co.uk> napisał(a):
> Hi, > > Yeah see the below output from lsscsi > > lsscsi -g > > [8:0:0:0] tape HP Ultrium 5-SCSI Y6PW /dev/st1 /dev/sg40 > [9:0:0:0] tape HP Ultrium 5-SCSI Y6PW /dev/st0 /dev/sg38 > [9:0:0:1] mediumx HP MSL G3 Series 9.40 /dev/sch0 /dev/sg39 > > So, from I can see you have a following devices you should use: - autochanger device: /dev/sg39 - storage device #0 /dev/nst0 - storage device #1 /dev/nst1 For the mtx command you should always use an "autochanger device" as described above. Others simply won't work. > If i do use st0 and st1 > ??? Why? > [root@union bacula]# ./mtx-changer /dev/st1 listall > cannot open SCSI device '/dev/st1' - No medium found > [root@union bacula]# ./mtx-changer /dev/st0 listall > 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 = 20 > mtx: Request Sense: Additional Sense Qualifier = 00 > mtx: Request Sense: BPV=no > mtx: Request Sense: Error in CDB=no > mtx: Request Sense: SKSV=no > READ ELEMENT STATUS Command Failed > [root@union bacula]# > You should make sure that the following command will run without any issues: mtx -f /dev/sg39 status Then you can move to Bacula configuration. If this command won't work for you then Bacula won't work either. You should check kernel logs or events at the tape library to check what is going on. Then simply solve it. best regards -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
