After upgrading to latest mhVTL code my library and drives disappear.

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

After upgrading to latest mhVTL code my library and drives disappear.

DJMC117
I am setting up Veeam version 9 with mhVTL.
Initially when I configured the mhVTL I was able to see the devices from windows device manager and was also able to configure the libary in Veeam. My backups failed an error "empty MTF media".
I then upgraded the mhVTL as discussed in the post when using with Veeam 9, since then I cannot see the devices in device manager nor the veeam server.

The target is connected ok in the iSCSI properties and I have tried removing it and adding it back again but still unable to see the devices.

Has anyone else had this issue after upgrading the mhVTL? I have tried with both Windows 2008R2 and 2012R2.
My current setup is:

Veeam 9 Update 2.
Veeam server is Windows 2012R2.
mhVTL version 1.5.4-6dd65a
mhvtl GIU is 1.4.7-9f3bde0
Reply | Threaded
Open this post in threaded view
|

Re: After upgrading to latest mhVTL code my library and drives disappear.

Mark Harvey
Administrator
Any chance of setting VERBOSE = 3 in /etc/mhvtl/mhvtl.conf
Restarting mhVTL and then reproducing the error. Upload the syslog (typically/var/log/messages) for further analysis. 

Is there any diagnostic utilities with veeam that might help narrow what the error message means

Cheers

Sent from my autocorrecting iPhone

On 12 Nov. 2016, at 00:48, DJMC117 [via mhVTL - A Linux Virtual Tape Library] <[hidden email]> wrote:

I am setting up Veeam version 9 with mhVTL.
Initially when I configured the mhVTL I was able to see the devices from windows device manager and was also able to configure the libary in Veeam. My backups failed an error "empty MTF media".
I then upgraded the mhVTL as discussed in the post when using with Veeam 9, since then I cannot see the devices in device manager nor the veeam server.

The target is connected ok in the iSCSI properties and I have tried removing it and adding it back again but still unable to see the devices.

Has anyone else had this issue after upgrading the mhVTL? I have tried with both Windows 2008R2 and 2012R2.
My current setup is:

Veeam 9 Update 2.
Veeam server is Windows 2012R2.
mhVTL version 1.5.4-6dd65a
mhvtl GIU is 1.4.7-9f3bde0


To start a new topic under mhVTL - A Linux Virtual Tape Library, email [hidden email]
To unsubscribe from mhVTL - A Linux Virtual Tape Library, click here.
NAML
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: After upgrading to latest mhVTL code my library and drives disappear.

DJMC117

Hi Mark
Thanks for your reply, I'll get the logs to you in a day or so.
I don't think the problem is with Veeam, after the upgrade windows doesn't see the library.

D

On 12 Nov 2016 04:38, "Mark Harvey [via mhVTL - A Linux Virtual Tape Library]" <[hidden email]> wrote:
Any chance of setting VERBOSE = 3 in /etc/mhvtl/mhvtl.conf
Restarting mhVTL and then reproducing the error. Upload the syslog (typically/var/log/messages) for further analysis. 

Is there any diagnostic utilities with veeam that might help narrow what the error message means

Cheers

Sent from my autocorrecting iPhone

On 12 Nov. 2016, at 00:48, DJMC117 [via mhVTL - A Linux Virtual Tape Library] <[hidden email]> wrote:

I am setting up Veeam version 9 with mhVTL.
Initially when I configured the mhVTL I was able to see the devices from windows device manager and was also able to configure the libary in Veeam. My backups failed an error "empty MTF media".
I then upgraded the mhVTL as discussed in the post when using with Veeam 9, since then I cannot see the devices in device manager nor the veeam server.

The target is connected ok in the iSCSI properties and I have tried removing it and adding it back again but still unable to see the devices.

Has anyone else had this issue after upgrading the mhVTL? I have tried with both Windows 2008R2 and 2012R2.
My current setup is:

Veeam 9 Update 2.
Veeam server is Windows 2012R2.
mhVTL version 1.5.4-6dd65a
mhvtl GIU is 1.4.7-9f3bde0


To start a new topic under mhVTL - A Linux Virtual Tape Library, email [hidden email]
To unsubscribe from mhVTL - A Linux Virtual Tape Library, click here.
NAML
Regards from Australia
Mark Harvey



To unsubscribe from After upgrading to latest mhVTL code my library and drives disappear., click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: After upgrading to latest mhVTL code my library and drives disappear.

DJMC117
In reply to this post by Mark Harvey
Hi Mark,
Sorry for the delay in getting this to you.
Just to recap... Before upgrade the MHVTL could be seen by both windows and Veeam. After upgrade it is not seen by either. It no longer appears in windows device manager.

Thanks
D

On Sat, Nov 12, 2016 at 4:38 AM, Mark Harvey [via mhVTL - A Linux Virtual Tape Library] <[hidden email]> wrote:
Any chance of setting VERBOSE = 3 in /etc/mhvtl/mhvtl.conf
Restarting mhVTL and then reproducing the error. Upload the syslog (typically/var/log/messages) for further analysis. 

Is there any diagnostic utilities with veeam that might help narrow what the error message means

Cheers

Sent from my autocorrecting iPhone

On 12 Nov. 2016, at 00:48, DJMC117 [via mhVTL - A Linux Virtual Tape Library] <[hidden email]> wrote:

I am setting up Veeam version 9 with mhVTL.
Initially when I configured the mhVTL I was able to see the devices from windows device manager and was also able to configure the libary in Veeam. My backups failed an error "empty MTF media".
I then upgraded the mhVTL as discussed in the post when using with Veeam 9, since then I cannot see the devices in device manager nor the veeam server.

The target is connected ok in the iSCSI properties and I have tried removing it and adding it back again but still unable to see the devices.

Has anyone else had this issue after upgrading the mhVTL? I have tried with both Windows 2008R2 and 2012R2.
My current setup is:

Veeam 9 Update 2.
Veeam server is Windows 2012R2.
mhVTL version 1.5.4-6dd65a
mhvtl GIU is 1.4.7-9f3bde0


To start a new topic under mhVTL - A Linux Virtual Tape Library, email [hidden email]
To unsubscribe from mhVTL - A Linux Virtual Tape Library, click here.
NAML
Regards from Australia
Mark Harvey



To unsubscribe from After upgrading to latest mhVTL code my library and drives disappear., click here.
NAML


syslog (567K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: After upgrading to latest mhVTL code my library and drives disappear.

Mark Harvey
Administrator
Thanks for the syslog (/var/log/messages)...

the syslogd rate limiter is in action, however it is showing the following
Nov 25 10:40:20 tape1 kernel: [   11.676295] ch0: dt 0x1e2: ch0: ID/LUN unknown
Nov 25 10:40:20 tape1 vtllibrary[1245]: decode_element_status(): Element Status Page
Nov 25 10:40:20 tape1 vtllibrary[1245]: decode_element_status():   Element Type code            : 4 (Drive)
Nov 25 10:40:20 tape1 vtllibrary[1245]: decode_element_status():   Primary Vol Tag              : No
Nov 25 10:40:20 tape1 vtllibrary[1245]: decode_element_status():   Alt Vol Tag                  : Yes
Nov 25 10:40:20 tape1 vtllibrary[1245]: decode_element_status():   Element descriptor length    : 36
Nov 25 10:40:20 tape1 vtllibrary[1245]: decode_element_status():   Byte count of descriptor data: 36
Nov 25 10:40:20 tape1 vtllibrary[1245]: decode_element_status(): Element Descriptor(s) : Num of Elements 1
Nov 25 10:40:20 tape1 vtllibrary[1245]: dump_element_desc():  Debug.... i = 0, len = 36
Nov 25 10:40:20 tape1 vtllibrary[1245]: dump_element_desc():   Element Address             : 483
Nov 25 10:40:20 tape1 vtllibrary[1245]: dump_element_desc():   Status                      : 0x08
Nov 25 10:40:20 tape1 vtllibrary[1245]: dump_element_desc():   Medium type                 : 0
Nov 25 10:40:20 tape1 vtllibrary[1245]: dump_element_desc():  Identification Descriptor
Nov 25 10:40:20 tape1 vtllibrary[1245]: dump_element_desc():   Code Set                     : 0x02
Nov 25 10:40:20 tape1 vtllibrary[1245]: dump_element_desc():   Identifier type              : 0x00
Nov 25 10:40:20 tape1 vtllibrary[1245]: dump_element_desc():   Identifier length            : 20
Nov 25 10:40:20 tape1 vtllibrary[1245]: dump_element_desc():   ASCII data                   : 80000114            
Nov 25 10:40:20 tape1 vtllibrary[1245]: smc_read_element_status(): Element count: 1, Elem byte count: 44 (0x002c), alloc_len: 255, returning 52
Nov 25 10:40:20 tape1 vtllibrary[1245]: completeSCSICommand(): OP s/n: (75), sz: 52, sam_status: 0
Nov 25 10:40:20 tape1 vtllibrary[1245]: CDB (76) (delay 5): b8 04 01 e4 00 01 00 00 00 ff 00 00
Nov 25 10:40:20 tape1 rsyslogd-2177: imuxsock begins to drop messages from pid 1245 due to rate-limiting
Nov 25 10:40:20 tape1 kernel: [   11.679512] ch0: dt 0x1e3: ch0: ID/LUN unknown
Nov 25 10:40:20 tape1 kernel: [   11.680323] ch0: dt 0x1e4: ch0: ID/LUN unknown
Nov 25 10:40:20 tape1 kernel: [   11.680325] ch0: INITIALIZE ELEMENT STATUS, may take some time ...

Looks like the device specified in the target configuration does not match the device name (/dev/sgxx) allocated by the kernel for the mhVTL devices.

Nov 25 10:40:20 tape1 tgtd: work_timer_start(150) use signal based scheduler
Nov 25 10:40:20 tape1 tgtd: bs_init(316) use signalfd notification
Nov 25 10:40:20 tape1 tgtd: device_mgmt(245) sz:17 params:path=-,bstype=sg
Nov 25 10:40:20 tape1 tgtd: chk_sg_device(344) stat() failed errno: 2
Nov 25 10:40:20 tape1 tgtd: bs_sg_open(446) Not recognized - as an SG device

Nov 25 10:40:21 tape1 vtllibrary[1244]: add_lu(): Wrote add 110 5 0 0#012 (14 bytes)
Nov 25 10:40:21 tape1 vtllibrary[1244]: add_lu(): Child anounces 'lu [5:0:0] created'.
Nov 25 10:40:21 tape1 kernel: [   12.678860] ch0: ... finished
Nov 25 10:40:21 tape1 kernel: [   12.678871] ch 3:5:0:0: Attached scsi changer ch0
Nov 25 10:40:21 tape1 kernel: [   12.680601] ch 3:5:0:0: Attached scsi generic sg8 type 8
Nov 25 10:40:27 tape1 ntpdate[775]: adjust time server 91.189.89.198 offset 0.147179 sec
Nov 25 10:40:43 tape1 ntpdate[1306]: adjust time server 91.189.89.198 offset 0.141481 sec
Nov 25 10:42:08 tape1 tgtd: conn_close(103) connection closed, 0x1248d58 1
Nov 25 10:44:51 tape1 tgtd: conn_close(103) connection closed, 0x1248d58 1

hmm... I wonder how the mhvtl-gui sets up the path for stgt.. I'll have to setup a config and have a quick look.

For now, can I ask for the output of "lsscsi -g" from the 'tape1' linux host.
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: After upgrading to latest mhVTL code my library and drives disappear.

Mark Harvey
Administrator
My test bed (only two devices added to the iSCSI target) looks like:

[root@mhfedora httpd]# cat /etc/tgt/targets.conf.mhvtl 
default-driver iscsi

<target iqn.1994-05.com.redhat:185ce16b55ad:mhvtl:tgt:1>
	backing-store /dev/sg2
	backing-store /dev/sg3
        bs-type sg
        device-type pt
</target>

[root@mhfedora httpd]# lsscsi -g
[0:0:0:0]    disk    ATA      VBOX HARDDISK    1.0   /dev/sda   /dev/sg0 
[2:0:0:0]    cd/dvd  VBOX     CD-ROM           1.0   /dev/sr0   /dev/sg1 
[3:0:0:0]    mediumx STK      L700             0105  /dev/sch0  /dev/sg10
[3:0:1:0]    tape    IBM      ULT3580-TD5      0105  /dev/st0   /dev/sg2 
[3:0:2:0]    tape    IBM      ULT3580-TD5      0105  /dev/st1   /dev/sg3 
[3:0:3:0]    tape    IBM      ULT3580-TD4      0105  /dev/st2   /dev/sg4 
[3:0:4:0]    tape    IBM      ULT3580-TD4      0105  /dev/st3   /dev/sg5 
[3:0:8:0]    mediumx STK      L80              0105  /dev/sch1  /dev/sg11
[3:0:9:0]    tape    STK      T10000B          0105  /dev/st4   /dev/sg6 
[3:0:10:0]   tape    STK      T10000B          0105  /dev/st5   /dev/sg7 
[3:0:11:0]   tape    STK      T10000B          0105  /dev/st6   /dev/sg8 
[3:0:12:0]   tape    STK      T10000B          0105  /dev/st7   /dev/sg9 
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: After upgrading to latest mhVTL code my library and drives disappear.

DJMC117
Hi Mark,
Thanks for your reply.
See output from  /etc/tgt/targets.conf.mhvtl and lsscsi below as requested.

Which version of the MHVTL have you deployed and can you see the devices from windows 2012R2?

Thanks,
D

root@tape1:~#
root@tape1:~# cat /etc/tgt/targets.conf.mhvtl
default-driver iscsi

<target iqn.2011-04.com.nia:tape1:mhvtl:stgt:1>
        backing-store /dev/sg5
        backing-store /dev/sg3
        backing-store /dev/sg4
        bs-type sg
        device-type pt
</target>

root@tape1:~#
root@tape1:~# lsscsi -g
[1:0:0:0]    cd/dvd  NECVMWar VMware IDE CDR10 1.00  /dev/sr0  /dev/sg0
[2:0:0:0]    disk    VMware   Virtual disk     1.0   /dev/sda  /dev/sg1
[2:0:1:0]    disk    VMware   Virtual disk     1.0   /dev/sdb  /dev/sg2
[3:5:0:0]    mediumx HP       MSL6000 Series   1068  /dev/sch0  /dev/sg8
[3:5:0:1]    tape    HP       Ultrium 6-SCSI   N11G  /dev/st0  /dev/sg3
[3:5:0:2]    tape    HP       Ultrium 6-SCSI   N11G  /dev/st1  /dev/sg4
[3:5:0:3]    tape    HP       Ultrium 6-SCSI   N11G  /dev/st2  /dev/sg5
[3:5:0:4]    tape    HP       Ultrium 6-SCSI   N11G  /dev/st3  /dev/sg6
[3:5:0:5]    tape    HP       Ultrium 6-SCSI   N11G  /dev/st4  /dev/sg7
root@tape1:~#
root@tape1:~# ^C
root@tape1:~#


On Sun, Nov 27, 2016 at 4:58 AM, Mark Harvey [via mhVTL - A Linux Virtual Tape Library] <[hidden email]> wrote:
My test bed (only two devices added to the iSCSI target) looks like:

[root@mhfedora httpd]# cat /etc/tgt/targets.conf.mhvtl 
default-driver iscsi

<target iqn.1994-05.com.redhat:185ce16b55ad:mhvtl:tgt:1>
	backing-store /dev/sg2
	backing-store /dev/sg3
        bs-type sg
        device-type pt
</target>

[root@mhfedora httpd]# lsscsi -g
[0:0:0:0]    disk    ATA      VBOX HARDDISK    1.0   /dev/sda   /dev/sg0 
[2:0:0:0]    cd/dvd  VBOX     CD-ROM           1.0   /dev/sr0   /dev/sg1 
[3:0:0:0]    mediumx STK      L700             0105  /dev/sch0  /dev/sg10
[3:0:1:0]    tape    IBM      ULT3580-TD5      0105  /dev/st0   /dev/sg2 
[3:0:2:0]    tape    IBM      ULT3580-TD5      0105  /dev/st1   /dev/sg3 
[3:0:3:0]    tape    IBM      ULT3580-TD4      0105  /dev/st2   /dev/sg4 
[3:0:4:0]    tape    IBM      ULT3580-TD4      0105  /dev/st3   /dev/sg5 
[3:0:8:0]    mediumx STK      L80              0105  /dev/sch1  /dev/sg11
[3:0:9:0]    tape    STK      T10000B          0105  /dev/st4   /dev/sg6 
[3:0:10:0]   tape    STK      T10000B          0105  /dev/st5   /dev/sg7 
[3:0:11:0]   tape    STK      T10000B          0105  /dev/st6   /dev/sg8 
[3:0:12:0]   tape    STK      T10000B          0105  /dev/st7   /dev/sg9 
Regards from Australia
Mark Harvey



To unsubscribe from After upgrading to latest mhVTL code my library and drives disappear., click here.
NAML