On 10/23/15 01:21 PM, rahs wrote: >>> root@hq-bareos-01:~# /usr/lib/bareos/scripts/mtx-changer /dev/sg3 load 1 >>> /dev/st0 0 >>> >>> >>> Loading media from Storage Element 1 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=Unit Attention >>> mtx: Request Sense: FileMark=no >>> mtx: Request Sense: EOM=no >>> mtx: Request Sense: ILI=no >>> mtx: Request Sense: Additional Sense Code = 29 >>> mtx: Request Sense: Additional Sense Qualifier = 02 >>> mtx: Request Sense: BPV=no >>> mtx: Request Sense: Error in CDB=no >>> mtx: Request Sense: SKSV=no >>> MOVE MEDIUM from Element Address 1001 to 1 Failed
The above is a problem with mtx as long as you don't solve that things will never be working. This has nothing to do with Bareos in any way. Its either a controller problem or a firmware problem on the changer. As long as mtx is not able to load things into the right slot without raising a low level SCSI error anything else makes no sense to try. Given mtx is kind of stable code (didn't see updates in ages) and the whole SCSI protocol for this is also ancient and proven I would ask your vendor to solve this problem. I wouldn't be surprised its a actual firmware problem in the robot. We have seen some Tandberg changers also do strange things. -- Marco van Wieringen [email protected] Bareos GmbH & Co. KG Phone: +49-221-63069389 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz, M. v. Wieringen -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
