Hello Steve,
Sorry, incomplete email again...
Yes, it looks we have something here.
From one of your previous emails, we have the error "3999 Device "AutochangerOdin" not found or could not be opened." when Bacula issues the label command for the tapes.
This "not found or could not be opened" message usually refers to the wrong "device name" configured for an "Archive Device" or "Changer Device".
The below two messages in the debug output also indicates this problem:
odin-sd: dircmd.c:817-0 Try changer device Drive-1
odin-sd: dircmd.c:842-0 Device AutochangerOdin drive wrong: want=0 got=0 skipping
From another post, you have only one tape library with one tape drive, but two paths for each of them:
root@odin:/etc/bacula# lsscsi -g
[0:2:0:0] disk DELL PERC H730 Mini 4.27 /dev/sda /dev/sg0
[1:0:0:0] tape IBM ULT3580-HH6 G9P1 /dev/st0 /dev/sg2
[1:0:0:1] mediumx IBM 3573-TL E.30 /dev/sch0 /dev/sg3
[1:0:1:0] tape IBM ULT3580-HH6 G9P1 /dev/st1 /dev/sg4
[1:0:1:1] mediumx IBM 3573-TL E.30 /dev/sch1 /dev/sg5
[6:2:0:0] disk DELL PERC H830 Adp 4.27 /dev/sdb /dev/sg1
[12:0:0:0] cd/dvd PLDS DVD-ROM DS-8DBSH MD52 /dev/sr0 /dev/sg6
This seems to me you have a tape library/drive configured with physical multipath (zoning, two HBAs, etc.) for fail over?
If so, you don't have multipath configured in this linux system? This explains that your system sees two different device names for each one of your tape library and tape drive.
If this is the case, I'm afraid you will have problems to use the "/dev/tape/by-id" or "/dev/nst" device names for the tape drives. Maybe it would be better, in this case, to use "/dev/tape/by-path". Even better, to not have this physical multipath if you are not going to use it with the tape library...
Hope this helps.
Best regards,
Ana