Turns out I resolved this issue. 

Let me break it down for anyone else that has the issue.


The symptoms presented with the autochanger loading a tape but then saying 
there was no media in the drive. 


It turns out that my /dev/nst devices were not mapped to the drive indexes in 
the 0 though 3 order so /dev/nst0 was not associated with drive 0 

I figured this out by using the btape test using my bareos-sd.conf and manually 
loading and unloading each drive from each of the 4 drives I have until I found 
what drive was associated with each /dev/nst device. 

After doing this I found 
/dev/nst0 was mapped to drive 3 on my device
/dev/nst1 was mapped to drive 0 on my device
/dev/nst2 was mapped to drive 2 on my device
/dev/nst3 was mapped to drive 1 on my device


very weird over all but all 4 of my drives "seem" to function without issue at 
this time now. 


On Sunday, August 10, 2014 9:58:50 AM UTC-6, jesse hart wrote:
> Hello everyone, 
> 
> 
> I am new to Bareos and need some help. I have a mutli drive i500 tape 
> library. I can properly run backups using 1 of the drivers but not multiple 
> drives. I ran the btape tests and all and it can grab tapes and move tapes 
> and everything but for some reason I am running into the following errors and 
> I can not figure out how to get this to properly function. 
> 
> 
> I have turned on the mtx-changer debug and have that log posted below. I am 
> also posting my SD and dir config below. 
> 
> 
> I really dont understand how this shows there is a tape in the drive however, 
> it bareos says there is no media. 
> 
> 
> OK to run? (yes/mod/no): yes
> Job queued. JobId=315
> *
> 10-Aug 10:38 omatapebackup-dir JobId 315: Start Backup JobId 315, 
> Job=Netapp-Finance-Share.2014-08-10_10.38.17_03
> 10-Aug 10:38 omatapebackup-dir JobId 315: Using Device "Drive-0" to write.
> 10-Aug 10:38 omatapebackup-sd JobId 315: 3307 Issuing autochanger "unload 
> slot 51, drive 1" command.
> *
> *
> 10-Aug 10:38 omatapebackup-sd JobId 315: 3304 Issuing autochanger "load slot 
> 51, drive 0" command.
> *
> *
> *
> *
> *
> *
> 10-Aug 10:42 omatapebackup-sd JobId 315: 3305 Autochanger "load slot 51, 
> drive 0", status is OK.
> 10-Aug 10:42 omatapebackup-sd JobId 315: Warning: mount.c:207 Open device 
> "Drive-0" (/dev/nst0) Volume "SD0100" failed: ERR=dev.c:494 Unable to open 
> device "Drive-0" (/dev/nst0): ERR=No medium found
> 
> 10-Aug 10:42 omatapebackup-sd JobId 315: Warning: mount.c:207 Open device 
> "Drive-0" (/dev/nst0) Volume "SD0100" failed: ERR=dev.c:494 Unable to open 
> device "Drive-0" (/dev/nst0): ERR=No medium found
> 
> 10-Aug 10:42 omatapebackup-sd JobId 315: Warning: mount.c:207 Open device 
> "Drive-0" (/dev/nst0) Volume "SD0100" failed: ERR=dev.c:494 Unable to open 
> device "Drive-0" (/dev/nst0): ERR=No medium found
> 
> 10-Aug 10:42 omatapebackup-sd JobId 315: Warning: mount.c:207 Open device 
> "Drive-0" (/dev/nst0) Volume "SD0100" failed: ERR=dev.c:494 Unable to open 
> device "Drive-0" (/dev/nst0): ERR=No medium found
> 
> 10-Aug 10:42 omatapebackup-sd JobId 315: Warning: mount.c:207 Open device 
> "Drive-0" (/dev/nst0) Volume "SD0100" failed: ERR=dev.c:494 Unable to open 
> device "Drive-0" (/dev/nst0): ERR=No medium found
> 
> 10-Aug 10:42 omatapebackup-sd JobId 315: Please mount append Volume "SD0100" 
> or label a new one for:
>     Job:          Netapp-Finance-Share.2014-08-10_10.38.17_03
>     Storage:      "Drive-0" (/dev/nst0)
>     Pool:         Finance
>     Media type:   LTO-4
> *
> 
> 
> 
> 
> 
> 
> 
> I run the mtx-changer script to show the drives and slots and see this 
> 
> 
> # /usr/lib/bareos/scripts/mtx-changer /dev/sg6 listall /dev/st0 0
> D:0:F:51:SD0100
> D:1:E
> D:2:E
> D:3:E
> 
> 
> 
> 
> 
> 
> 
> 
> mtx-changer debug output from mtx.log
> 
> 20140810-10:37:34 Parms: /dev/sg6 loaded 0 /dev/nst0 0
> 20140810-10:37:34 Doing mtx -f /dev/sg6 0 -- to find what is loaded
> 20140810-10:37:35 Parms: /dev/sg6 loaded 0 /dev/nst0 0
> 20140810-10:37:35 Doing mtx -f /dev/sg6 0 -- to find what is loaded
> 20140810-10:37:36 Parms: /dev/sg6 loaded 0 /dev/nst1 1
> 20140810-10:37:36 Doing mtx -f /dev/sg6 1 -- to find what is loaded
> 20140810-10:38:19 Parms: /dev/sg6 loaded 51 /dev/nst0 0
> 20140810-10:38:19 Doing mtx -f /dev/sg6 0 -- to find what is loaded
> 20140810-10:38:20 Parms: /dev/sg6 loaded 51 /dev/nst0 0
> 20140810-10:38:20 Doing mtx -f /dev/sg6 0 -- to find what is loaded
> 20140810-10:38:21 Parms: /dev/sg6 unload 51 /dev/nst1 1
> 20140810-10:38:21 Doing mtx -f /dev/sg6 unload 51 1
> 20140810-10:38:58 Parms: /dev/sg6 load 51 /dev/nst0 0
> 20140810-10:38:58 Doing mtx -f /dev/sg6 load 51 0
> 20140810-10:39:11 Device /dev/nst0 - not ready, retrying...
> 20140810-10:39:12 Device /dev/nst0 - not ready, retrying...
> 20140810-10:39:13 Device /dev/nst0 - not ready, retrying...
> 20140810-10:39:14 Device /dev/nst0 - not ready, retrying...
> above message repeats a ton before stopping. 
> 
> 
> 
> 
> 
> mtx-changer.conf
> 
> 
> cat /etc/bareos/mtx-changer.conf
> #
> # This file is sourced by the mtx-changer script every time it runs.
> #   You can put your site customization here, and when you do an
> #   upgrade, the process should not modify this file.  Thus you
> #   preserve your mtx-changer configuration.
> #
> 
> # Set to 1 if you want to do offline before unload
> offline=0
> 
> # Set to amount of time in seconds to wait after an offline
> offline_sleep=0
> 
> # Set to amount of time in seconds to wait after a load
> load_sleep=0
> 
> # Set to 1 to do an inventory before a status. Not normally needed.
> inventory=0
> 
> # If you have a VXA PacketLoader, it might display a different
> #  Storage Element line, so try setting the following to 1
> vxa_packetloader=0
> 
> # Set to 1 if you want debug info written to a log
> debug_log=1
> 
> 
> # mt status output
> # SunOS     No Additional Sense
> # FreeBSD   Current Driver State: at rest.
> # Linux     ONLINE
> #  Note Debian has a different mt than the standard Linux version.
> #    When no tape is in the drive it waits 2 minutes.
> #    When a tape is in the drive, it prints user unfriendly output.
> #  Note, with Ubuntu Gusty (8.04), there are two versions of mt,
> #    so we attempt to figure out which one.
> #
> 
> OS=`uname`
> case ${OS} in
>   SunOS)
>     ready="No Additional Sense"
>     ;;
>   FreeBSD)
>     ready="Current Driver State: at rest."
>     ;;
>   Linux)
>     ready="ONLINE"
>     if test -f /etc/debian_version ; then
>        mt --version|grep "mt-st" >/dev/null 2>&1
>        if test $? -eq 1 ; then
>           ready="drive status"
>        fi
>     fi
>   ;;
> esac
> 
> 
> 
> 
> 
> 
> bareos-sd.conf
> 
> 
> 
> 
> 
> Autochanger {
>   Name = Auto1
>   Device = Drive-0, Drive-1
>   Changer Device = /dev/sg6
>   Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a %d"
> }
> Device {
>  Name = Drive-0
>  Drive Index = 0
>  Media Type = LTO-4
>  Archive Device = /dev/nst0
>  Autochanger = yes
>  Autoselect = yes
>  LabelMedia = no;
>  AutomaticMount = yes;
>  RemovableMedia = yes;
>  RandomAccess = no;
>  Maximum File Size = 5GB
>  AlwaysOpen = yes;
> }
> Device {
>  Name = Drive-1
>  Drive Index = 1
>  Media Type = LTO-4
>  Archive Device = /dev/nst1
>  Autochanger = yes
>  Autoselect = yes
>  LabelMedia = no;
>  AutomaticMount = yes;
>  RemovableMedia = yes;
>  RandomAccess = no;
>  Maximum File Size = 5GB
>  AlwaysOpen = yes;
> }
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> bareos-dir.conf
> 
> 
> Storage {
>  Name = i500
>  Address = hidden
>  Password = "hidden"
>  Device = Auto1
>  Media Type = LTO-4
>  Autochanger = yes
>  Maximum Concurrent Jobs = 4
> }

-- 
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.

Reply via email to