Tandberg LTO4 HH on LSI-Controller

[Sven Gehr]

Hi@all,

not a bareos-problem. I need help to use my streamer with linux. After this I will use it with bareos.

y server is installed with ubuntu-server 12.04-lts 64bit) an I have plug in a lsi sas-controller:

[lspci]
...
02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2004 PCI-Express Fusion-MPT SAS-2 [Spitfire] (rev 03)

for my streamer:
[lsscsi -g]
...
[1:0:0:0] tape TANDBERG LTO-4 HH U619 /dev/st0 /dev/sg2


[ 2.682781] scsi0 : LSI SAS based MegaRAID driver
[ 2.702345] scsi 0:2:0:0: Direct-Access LSI MR9260-8i 2.13 PQ: 0 ANSI: 5
[ 4.373528] mpt2sas0: LSISAS2004: FWVersion(15.00.00.00), ChipRevision(0x03), BiosVersion(07.29.00.00)

...

[ 2.587266] megasas: 06.504.01.00-rc1 Mon. Oct. 1 17:00:00 PDT 2012
[ 2.587286] megasas: 0x1000:0x0079:0x1000:0x9261: bus 5:slot 0:func 0
[ 2.587979] mpt2sas version 14.100.00.00 loaded
[ 2.588048] megasas: FW now in Ready state
[ 2.588127] megaraid_sas 0000:05:00.0: irq 75 for MSI/MSI-X
[ 2.588999] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (16433624 kB)
[ 2.589076] mpt2sas 0000:02:00.0: irq 76 for MSI/MSI-X
[ 2.589103] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 76
[ 2.589110] mpt2sas0: iomem(0x00000000f0440000), mapped(0xffffc90011bc8000), size(16384)
[ 2.589116] mpt2sas0: ioport(0x000000000000b000), size(256)
[ 2.610877] megasas_init_mfi: fw_support_ieee=0
[ 2.610884] megasas: INIT adapter done
[ 2.874581] mpt2sas0: sending diag reset !!
[ 3.993477] mpt2sas0: diag reset: SUCCESS
[ 4.141307] mpt2sas0: Allocated physical memory: size(3379 kB)
[ 4.141313] mpt2sas0: Current Controller Queue Depth(1483), Max Controller Queue Depth(1720)
[ 4.141318] mpt2sas0: Scatter Gather Elements per IO(128)
[ 4.373528] mpt2sas0: LSISAS2004: FWVersion(15.00.00.00), ChipRevision(0x03), BiosVersion(07.29.00.00)
[ 4.373534] mpt2sas0: Protocol=(Initiator), Capabilities=(Raid,TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[ 4.373612] mpt2sas0: sending port enable !!
[ 5.906127] mpt2sas0: host_add: handle(0x0001), sas_addr(0x500062b0002b0294), phys(8)
[ 12.029622] mpt2sas0: port enable: SUCCESS
[ 12.031105] scsi 1:0:0:0: SSP: handle(0x0009), sas_addr(0x500110a001549d14), phy(3), device_name(0x0000000000000000)

...

[ 12.031095] scsi 1:0:0:0: Sequential-Access TANDBERG LTO-4 HH U619 PQ: 0 ANSI: 5


I will get the status of the drive:

mt-st -f /dev/st0 status

File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x46 (LTO-4).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN

Allway looks good but how can I make a simple backup with tar? In my bacula book I found:


tar cvf /dev/st0 /my_directory

but this give me the error:

...
/root/backup/Datext/06-12-13_15-12/GZSKREUZ.DB
/root/backup/Datext/06-12-13_15-12/TERMINE.YG5
/root/backup/Datext/06-12-13_15-12/GZSABRZAZEILEN.XG0
/root/backup/Datext/06-12-13_15-12/KDNWEGE.YG0
/root/backup/Datext/06-12-13_15-12/BELEG2.XH1
tar: /dev/st0: Kann write nicht ausführen: Eingabe-/Ausgabefehler
tar: Error is not recoverable: exiting now

I found the following webside:

http://gloeckner.blogspot.de/2012/10/tandberg-lto4-sas-auf-debian-linux-60.html

here was the tool 'buffer' used to make a backup but I understand this. How can I do a simple backup/restore with linux to test my streamer?

with best
sven

[Gerhard Sulzberger]

Hi Sven,

We have a Tandberg T24 with an HH-LTO5 dirve but the commands should be nearly the same.

rave backup # mt -f /dev/tape/by-id/scsi-3500110a00152f34e-nst status
drive type = 114
drive status = 1476395008
sense key error = 0
residue count = 0
file number = 1
block number = 0
rave backup # tar cvf /dev/tape/by-id/scsi-3500110a00152f34e-nst text2.txt
text2.txt
rave backup # tar cvf /dev/tape/by-id/scsi-3500110a00152f34e-nst text3.txt
text3.txt
rave backup # mt -f /dev/tape/by-id/scsi-3500110a00152f34e-nst status
drive type = 114
drive status = 1476395008
sense key error = 0
residue count = 0
file number = 3
block number = 0

mt -f /dev/tape/by-id/scsi-3500110a00152f34e-nst rewind # zurückspulen, Band befindet sich an Sicherung 1
mt -f /dev/tape/by-id/scsi-3500110a00152f34e-nst fsf 1 # Band um eine Datei weiter spulen, d.h. zweite Sicherung
mt -f /dev/tape/by-id/scsi-3500110a00152f34e-nst bsf 1 # Band um eine Datei weiter spulen, d.h. erste Sicherung
mt -f /dev/tape/by-id/scsi-3500110a00152f34e-nst status # Statusübersicht
tar tvf /dev/tape/by-id/scsi-3500110a00152f34e-nst # Tar die Sicherung auslesen (name des Files an dieser position)
tar xf /dev/tape/by-id/scsi-3500110a00152f34e-nst # Tar das File rücksichern ( betrifft das file auf dem das Band im Moment steht)

I used the scsi path, but I think you also can use /dev/nst0 insead.

Hope this will help.

[Sven Gehr]

ok, I try it with the scsi-path.

get status looks to me good:


root@kvm01:~# mt -f /dev/tape/by-id/scsi-3500110a001549d16
scsi-3500110a001549d16 scsi-3500110a001549d16-nst
root@kvm01:~# mt -f /dev/tape/by-id/scsi-3500110a001549d16-nst status
SCSI 2 tape drive:

File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x46 (LTO-4).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN

but when I try to make a test-backup:

root@kvm01:/# tar cvf /dev/tape/by-id/scsi-3500110a001549d16-nst /root/backup
tar: Entferne führende „/“ von Elementnamen
/root/backup/
/root/backup/Datext/

...
...

/root/backup/Datext/06-12-13_15-12/GZSKREUZ.DB
tar: /dev/tape/by-id/scsi-3500110a001549d16-nst: Kann write nicht ausführen: Eingabe-/Ausgabefehler

[Tony Albers]

Hi Sven,

1. Try the tandberg tools and check that the drive is ok:

http://www.tandbergdata.com/us/index.cfm/products/tape-drives/lto-drives/lto-4-hh/

2. Update your drive firmware and try again. I have seen a huge number of I/O errors being corrected with new firmware versions.

/tony

2014/1/7 Sven Gehr <sven...@gmail.com>

--
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 bareos-users...@googlegroups.com.
To post to this group, send email to bareos...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Tony Albers]

I also stumbled upon this:

http://www.tandbergdata.com/knowledge-base/index.cfm/how-do-i-use-the-linux-tar-command-to-backup-using-my-tape-drive-autoloader-or-library/

Check that it's not a weird blocksize issue of some sort. The drive firmware may be locked to a specific blocksize and then it won't accept writes using another blocksize.

/tony

2014/1/7 Tony Albers <tony....@gmail.com>

[Gerhard Sulzberger]

You can find some tips how to test the drive here:
https://groups.google.com/forum/?hl=en#!topic/bareos-users/YoCGZuyKbR0

How much data did you wrote on the tape?

[Sven Gehr]

ok, first time I will test the device with the tanberg-tool. I download it an read the the readme.txt. Here I found the requirements:

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
1. SYSTEM REQUIREMENTS
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Operating Systems: - Linux Kernel 2.6.31 or later (x86/x64)
Java Runtime Environment (JRE) Ver. 1.4.2 or later

The tool need java? I have no gui on the server.

[Sven Gehr]

Am Dienstag, 7. Januar 2014 09:10:35 UTC+1 schrieb tonyalbers:
> I also stumbled upon this:
>
> http://www.tandbergdata.com/knowledge-base/index.cfm/how-do-i-use-the-linux-tar-command-to-backup-using-my-tape-drive-autoloader-or-library/

[lsscsi -g]

...
[1:0:0:0] tape TANDBERG LTO-4 HH U619 /dev/st0 /dev/sg2

which device I need to use.

/dev/st0

or

/dev/sg2

[Sven Gehr]

ok, one step further :-)

I forget the first command. With:

mt -f /dev/st0 setblk 0
mt -f /dev/st0 setblk 0
tar -c -v -b 128 -f /dev/st0 filename

...

tar -x -v -b 128 -f /dev/st0

I can backup/restore a file.

is this environment sufficient to use bareos? I do not want to work with tar but just wanted to test the drive.

My second problem relates th mdtool. I know that it has nothing to do with bareos but I hope that maybe someone can answer.

Is it right that I need to update the firmware the MDTools?

Are the MDTools a gui or console programm?

with best
sven

[Gerhard Sulzberger]

Hi Sven,

**********bareos-sd01 ~/tandberg # apt-get install openjdk-7-jre
**********bareos-sd01 ~/tandberg # tar xzf tdtoollinux64.tar.gz

+ logout and login again via ssh with X-Forwarding

ssh -X **********bareos-sd01

**********bareos-sd01 ~ # cd tandberg/
**********bareos-sd01 ~/tandberg # ls
lib readme.txt scsiintf.log TDTool.jar tdtoollinux64.tar.gz.1 tdtool.sh test
**********bareos-sd01 ~/tandberg # ./tdtool.sh

With the -X option of ssh you can forward the gui to your desktop.
And you also can find this in my post https://groups.google.com/forum/?hl=en#!topic/bareos-users/YoCGZuyKbR0

[Sven Gehr]

ok, it works with openjdk :-)

I can test the drive with the tool and I have install the last firmware.

Now I try to use the device with bareos ....