On 02/12/16 09:58 PM, Leon Ingleright wrote: ... > Connecting to Storage daemon I2M-AWS-Offsite-Storage at > i2m-bcm.include-im.com:9103 ... > Sending label command for Volume "I2M-AWS-BCM-Catalog-Backup-1" Slot 4 ... > generic_tape_device.c:140 Unable to open device "I2M-AWS-TD0" > (/dev/tape/by-path/ip-172.30.0.99:3260-iscsi-iqn.1997-05.com.amazon:sgw-f4896c9d-tapedrive-01-lun-0-nst): > ERR=No medium found > ansi_label.c:319 ANSI Volume label name "I2M-AWS-BCM-Catalog-Backup-1" longer > than 6 chars. > 3912 Failed to label Volume: ERR=generic_tape_device.c:140 Unable to open > device "I2M-AWS-TD0" > (/dev/tape/by-path/ip-172.30.0.99:3260-iscsi-iqn.1997-05.com.amazon:sgw-f4896c9d-tapedrive-01-lun-0-nst): > ERR=No medium found > > Label command failed for Volume I2M-AWS-BCM-Catalog-Backup-1. > Do not forget to mount the drive!!! > * > > --and came up with the same error. > > I haven't been able to find much of anything on this situation in > searches...most of the remotely similar problems were with physical tape > drives with completely different configurations, and none of them exactly > matched the output I'm getting here. > > I've searched through various logs and also did a 200-level debug output from > the Bareos storage daemon, but there is nothing obvious telling me what the > problem is. > > In the interest of not flooding this message with any more screen output than > I already have, I will provide files/outputs to anyone who specifies what > they would like to see. Hopefully someone out there has possibly dealt with > this or may have an idea as to what's going on. You seem to have several problems, first of all the drive index are not right as when mtx loads something into your virtual drive it uses the drive index and then it tries using it and gets "No Medium found". I would also start with one drive and get that working. Further more don't use ANSI labels they are limited (to 6 chars as you see) and only needed if you ever think about sharing volumes with other commercial (mostly IBM) backup software.
So I think your puzzle is to get the drive mappings right e.g. what drive index maps to what "logical tape drive" on the OS. -- 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.
