Problem with tape library

1,452 views
Skip to first unread message

rahs

unread,
Oct 20, 2015, 9:00:28 AM10/20/15
to bareos-users
Tape library HP MSL G3 2024, 2 LTO 6250 drives, connected via LSI 9280-8e
Debian 8.2
Bareos 14.2.1+20141017gitc6c5b56-3+deb8u1
mtx 1.3.12-9

lsscsi -g
[0:2:0:0] disk LSI RAID SAS 6G 0/1 2.13 /dev/sda /dev/sg0
[7:1:27:0] tape HP Ultrium 6-SCSI 338W /dev/st0 /dev/sg1
[7:1:28:0] tape HP Ultrium 6-SCSI 338W /dev/st1 /dev/sg2
[7:1:28:1] mediumx HP MSL G3 Series 6.10 /dev/sch0 /dev/sg3

bareos-sd config:

Autochanger {
Name = MSL2024
Device = Drive-0
Device = Drive-1
Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a %d"
Changer Device = /dev/sg3
}

Device {
Name = Drive-0
Media Type = LTO-6
Archive Device = /dev/st0
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes
AutoChanger = yes
Maximum Concurrent Jobs = 1
Drive Index = 0
Maximum Changer Wait = 180
}

Device {
Name = Drive-1
Media Type = LTO-6
Archive Device = /dev/st1
AutomaticMount = yes # when device opened, read it
AlwaysOpen = yes
AutoChanger = yes
Maximum Concurrent Jobs = 1
Drive Index = 1
Maximum Changer Wait = 180
}


root@hq-bareos-01:~# /usr/lib/bareos/scripts/mtx-changer /dev/sg3 listall /dev/st0 0
D:0:E
D:1:E
S:1:F:AIK282L6
S:2:E
S:3:E
S:4:E
S:5:E
S:6:E
S:7:E
S:8:E
S:9:E
S:10:E
S:11:E
S:12:E
S:13:E
S:14:E
S:15:E
S:16:E
S:17:E
S:18:E
S:19:E
S:20:E
S:21:E
S:22:E
S:23:E
I:24:F:CLNU02L1
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
root@hq-bareos-01:~# /usr/lib/bareos/scripts/mtx-changer /dev/sg3 listall /dev/st0 0
D:0:F:1:AIK282L6
D:1:E
S:1:E
S:2:E
S:3:E
S:4:E
S:5:E
S:6:E
S:7:E
S:8:E
S:9:E
S:10:E
S:11:E
S:12:E
S:13:E
S:14:E
S:15:E
S:16:E
S:17:E
S:18:E
S:19:E
S:20:E
S:21:E
S:22:E
S:23:E
I:24:F:CLNU02L1
root@hq-bareos-01:~# btape Drive-0
Tape block granularity is 1024 bytes.
btape: butil.c:301-0 Using device: "Drive-0" for writing.
btape: btape.c:480-0 open device "Drive-0" (/dev/st0): OK
*status
Bareos status: file=0 block=0
Device status: BOT ONLINE IM_REP_EN file=0 block=0
btape: btape.c:2149-0 Device status: 645. ERR=
*
*autochanger

Ah, I see you have an autochanger configured.
To test the autochanger you must have a blank tape
that I can write on in Slot 1.

Do you wish to continue with the Autochanger test? (y/n): y


=== Autochanger test ===

3301 Issuing autochanger "loaded" command.
Slot 1 loaded. I am going to unload it.
3302 Issuing autochanger "unload 1 0" command.
unload status=Bad 268435457
3992 Bad autochanger command: /usr/lib/bareos/scripts/mtx-changer /dev/sg3 unload 1 /dev/st0 0
3992 result="Unloading drive 0 into Storage Element 1...mtx: Request Sense: Long Report=yes
": ERR=Child exited with code 1
3303 Issuing autochanger "load 1 0" command.
3993 Bad autochanger command: /usr/lib/bareos/scripts/mtx-changer /dev/sg3 load 1 /dev/st0 0
3993 result="Loading media from Storage Element 1 into drive 0...mtx: Request Sense: Long Report=yes
": ERR=Child exited with code 1
You must correct this error or the Autochanger will not work.
*

how to make it work?

lst_...@kwsoft.de

unread,
Oct 20, 2015, 10:56:25 AM10/20/15
to bareos...@googlegroups.com

Zitat von rahs <uso...@gmail.com>:

> Tape library HP MSL G3 2024, 2 LTO 6250 drives, connected via LSI 9280-8e

To my knowledge the RAID Controller are not supported with tape
drives. You should use a non RAID HBA to attach the library. We have a
MSL 4048 which works trouble free with Bareos/Linux and a simple LSI
HBA.

Regards

Andreas


rahs

unread,
Oct 21, 2015, 3:24:09 AM10/21/15
to bareos-users, lst_...@kwsoft.de
> To my knowledge the RAID Controller are not supported with tape
> drives. You should use a non RAID HBA to attach the library. We have a
> MSL 4048 which works trouble free with Bareos/Linux and a simple LSI
> HBA.
>
> Regards
>
> Andreas

Standalone tape drive through RAID controller works fine
Recommendations for connecting the tape library on the HP website, I could not find.
Maybe you're right, I'll try to find the HBA adapter


Thanks for replying

Mariusz Tański

unread,
Oct 22, 2015, 5:19:14 AM10/22/15
to bareos-users
maybe isn't a right LOT drive. I have the same problem with my LTO6(8 tapes) when I use /dev/st0, I get the same problem. When I use /dev/st1 and another /dev/sgx, I get right results.

rahs

unread,
Oct 23, 2015, 7:21:24 AM10/23/15
to bareos-users
четверг, 22 октября 2015 г., 12:19:14 UTC+3 пользователь Mariusz Tański написал:
root@hq-bareos-01:~# /usr/lib/bareos/scripts/mtx-changer /dev/sg3 listall 1 /dev/sg1 0
root@hq-bareos-01:~# /usr/lib/bareos/scripts/mtx-changer /dev/sg3 load 1 /dev/sg1 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
root@hq-bareos-01:~# /usr/lib/bareos/scripts/mtx-changer /dev/sg3 listall 1 /dev/sg1 0
root@hq-bareos-01:~# cat /etc/bareos/bareos-sd.d/MSL2024
Autochanger {
Name = MSL2024
Device = Drive-0
Device = Drive-1
Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a %d"
Changer Device = /dev/sg3
}

Device {
Name = Drive-0
Media Type = LTO-6
Archive Device = /dev/sg1
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes
AutoChanger = yes
Maximum Concurrent Jobs = 1
Drive Index = 0
Maximum Changer Wait = 180
}

Device {
Name = Drive-1
Media Type = LTO-6
Archive Device = /dev/sg1
AutomaticMount = yes # when device opened, read it
AlwaysOpen = yes
AutoChanger = yes
Maximum Concurrent Jobs = 1
Drive Index = 1
Maximum Changer Wait = 180
}
root@hq-bareos-01:~# btape Drive-0
Tape block granularity is 1024 bytes.
btape: butil.c:301-0 Using device: "Drive-0" for writing.
23-Oct 14:18 btape: Fatal Error at device.c:287 because:
dev open failed: generic_tape_device.c:139 Unable to open device "Drive-0" (/dev/sg1): ERR=Operation not permitted

23-Oct 14:18 btape JobId 0: Fatal error: butil.c:197 Cannot open "Drive-0" (/dev/sg1)
root@hq-bareos-01:~#
root@hq-bareos-01:~# lsscsi -g
[0:2:0:0] disk LSI RAID SAS 6G 0/1 2.13 /dev/sda /dev/sg0
[7:1:27:0] tape HP Ultrium 6-SCSI 354W /dev/st0 /dev/sg1
[7:1:28:0] tape HP Ultrium 6-SCSI 354W /dev/st1 /dev/sg2
[7:1:28:1] mediumx HP MSL G3 Series 6.20 /dev/sch0 /dev/sg3

Marco van Wieringen

unread,
Nov 8, 2015, 7:03:48 AM11/8/15
to bareos...@googlegroups.com
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 marco.van...@bareos.com
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

Reply all
Reply to author
Forward
0 new messages