XenServer 7.2 and ESOS 1.3.5

[Samir Hanna Verza]

Hi,

I was using ESOS 0.9 on one DELL R720 with PERC H710 and two H810 one for each MD1200 drawer connected to servers using XenServer 7.2 with QLE 2464. It was working fine with dev_disk.

As I needed to change from RAID10 to RAID5 one of the drawers for saving legacy, I decided to upgrade the OS to the latest version. We set up the RAIDs again and generated the flash drive with version 1.3.5. However to our surprise we are not able to insert the LUNs in the XenServer, only the LUN of the PERC H710 has gone up, but when we try to mount a disk to a VM in this LUN of a VDI error.

We try to switch to vdisk_blockio and others but when the LUN rises on the XenServer of the VDI error.

What I might be doing wrong, the most basic thing I did was the group, add the initiator, add the dev_disk on LUN 0. In XenServer it finds the HBA asks to format but of the VDI error when adding the disk in a VM, already with the PERC H810 the XenServer finds the LUN, but when I command add of the error creating the HBA hardware.

I will add the photos because I do not know what to do anymore, we already tried to get the ESOS version back to 0.9 but it continued to generate the same problem.

Thanks in advance

[Samir Hanna Verza]

[Marc Smith]

So, it's a new volume (LUN) you're trying to present to the XenServer
instances? The dev_disk handler is for pass-through I/O and
vdisk_blockio is the "virtual disk block I/O" handler. They are
different, and you shouldn't switch between them, at least not with
real data on the underlying device.

The XenServer GUI doesn't give much information to go on, it'd
probably be best to see the logs on the XenServer shell... probably
most of what's under /var/log/. I'd be nice to try creating / adding
the SR from the command line as well, this may give more information
then what you're seeing in the GUI.

--Marc

> --
> You received this message because you are subscribed to the Google Groups
> "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to esos-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Samir Hanna Verza]

Follow the log below, what am I doing wrong? I exported as dev_disk to xen, thanks!

==> audit.log <==

Feb  3 11:05:19 sx2 xapi: [20180203T13:05:19.775Z|audit|sx2|1555 UNIX /var/lib/xcp/xapi|SR.set_virtual_allocation D:210810fdc901|audit] ('trackid=160db5826045345f8604960999e1cbdd' 'LOCAL_SUPERUSER' '__sm__backend' 'ALLOWED' 'OK' 'API' 'SR.set_virtual_allocation' (('self' 'STR1' '8689edd5-7cfd-cafa-8ea6-e3ec42adf8fc' 'OpaqueRef:1c127723-9345-dcd0-e592-83347c569774')))

Feb  3 11:05:19 sx2 xapi: [20180203T13:05:19.776Z|audit|sx2|1556 UNIX /var/lib/xcp/xapi|SR.set_physical_size D:12637d54b78a|audit] ('trackid=160db5826045345f8604960999e1cbdd' 'LOCAL_SUPERUSER' '__sm__backend' 'ALLOWED' 'OK' 'API' 'SR.set_physical_size' (('self' 'STR1' '8689edd5-7cfd-cafa-8ea6-e3ec42adf8fc' 'OpaqueRef:1c127723-9345-dcd0-e592-83347c569774')))

Feb  3 11:05:19 sx2 xapi: [20180203T13:05:19.778Z|audit|sx2|1557 UNIX /var/lib/xcp/xapi|SR.set_physical_utilisation D:548397c4f3ad|audit] ('trackid=160db5826045345f8604960999e1cbdd' 'LOCAL_SUPERUSER' '__sm__backend' 'ALLOWED' 'OK' 'API' 'SR.set_physical_utilisation' (('self' 'STR1' '8689edd5-7cfd-cafa-8ea6-e3ec42adf8fc' 'OpaqueRef:1c127723-9345-dcd0-e592-83347c569774')))

Feb  3 11:05:30 sx2 xapi: [20180203T13:05:30.511Z|audit|sx2|1394 INET :::80|VDI.create R:758cb23e96bc|audit] ('trackid=f026ac6c9960cd4b85fa89761611e114' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 22];  ]' 'API' 'VDI.create' (('name_label' 'New virtual disk' '' '') ('name_description' '' '' '') ('SR' 'STR1' '8689edd5-7cfd-cafa-8ea6-e3ec42adf8fc' 'OpaqueRef:1c127723-9345-dcd0-e592-83347c569774')))

Feb  3 11:05:38 sx2 xapi: [20180203T13:05:38.494Z|audit|sx2|1568 INET :::80|handler:http/connect_console D:a10e620aaf5e|audit] ('trackid=f026ac6c9960cd4b85fa89761611e114' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'HTTP' 'http/connect_console' (('ref' 'Control domain on host: sx2' 'b59ef6dc-16d6-42c5-a6ff-e5626a4bdf16' 'OpaqueRef:c6c3c193-20a2-fce0-ab23-104b440cf084')))

Feb  3 11:05:38 sx2 xapi: [20180203T13:05:38.494Z|audit|sx2|1568 INET :::80|check:http/connect_console/host_console D:9a1d8cf55d67|audit] ('trackid=f026ac6c9960cd4b85fa89761611e114' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'HTTP' 'http/connect_console/host_console' (('ref' 'Control domain on host: sx2' 'b59ef6dc-16d6-42c5-a6ff-e5626a4bdf16' 'OpaqueRef:c6c3c193-20a2-fce0-ab23-104b440cf084')))

Feb  3 11:06:25 sx2 xapi: [20180203T13:06:25.993Z|audit|sx2|1394 INET :::80|SR.probe R:363c7f9e2ec4|audit] ('trackid=f026ac6c9960cd4b85fa89761611e114' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:SR_BACKEND_FAILURE_107: [ ; The SCSIid parameter is missing or incorrect; <?xml version=\"1.0\" ?> <Devlist> #011<BlockDevice> #011#011<path>/dev/sdb</path> #011#011<numpaths>1</numpaths> #011#011<SCSIid>1SanDisk</SCSIid> #011#011<vendor>SanDisk</vendor> #011#011<serial>4C531146420411101034</serial> #011#011<size>8002732032</size> #011#011<adapter>9</adapter> #011#011<channel>0</channel> #011#011<id>0</id> #011#011<lun>0</lun> #011#011<hba>usb-storage</hba> #011</BlockDevice> #011<Adapter> #011#011<host>host8</host> #011#011<name>qla2xxx</name> #011#011<manufacturer>QLogic Fibre Channel HBA Driver</manufacturer> #011#011<id>8</id> #011#011<fc_host> #011#011#011<node_name>0x2001001b322eb699</node_name> #011#011#011<port_name>0x2101001b322eb699</port_name> #011#011#011<port_state>Linkdown</port_state> #011#011#011<speed>unknown</speed> #011#011#011<supported_speeds>1 Gbit, 2 Gbit, 4 Gbit</supported_speeds> #011#011</fc_host> #011</Adapter> #011<Adapter> #011#011<host>host9</host> #011#011<name>usb-storage</name> #011#011<manufacturer>USB Mass Storage driver for Linux</manufacturer> #011#011<id>9</id> #011</Adapter> #011<Adapter> #011#011<host>host1</host> #011#011<name>qla2xxx</name> #011#011<manufacturer>QLogic Fibre Channel HBA Driver</manufacturer> #011#011<id>1</id> #011#011<fc_host> #011#011#011<node_name>0x2000001b320eb699</node_name> #011#011#011<port_name>0x2100001b320eb699</port_name> #011#011#011<port_state>Online</port_state> #011#011#011<speed>4 Gbit</speed> #011#011#011<supported_speeds>1 Gbit, 2 Gbit, 4 Gbit</supported_speeds> #011#011</fc_host> #011</Adapter> #011<Adapter> #011#011<host>host0</host> #011#011<name>megaraid_sas</name> #011#011<manufacturer>Avago MegaRAID SAS Driver</manufacturer> #011#011<id>0</id> #011</Adapter> </Devlist>   ]' 'API' 'SR.probe' (('host' 'sx2' 'a92c608a-e0bd-45de-a7b9-7ab82303550e' 'OpaqueRef:cbc9993b-d6b9-d3ed-e91b-99abbc2eebc9')))

Feb  3 11:06:43 sx2 xapi: [20180203T13:06:43.826Z|audit|sx2|1394 INET :::80|VDI.create R:1f3517c58504|audit] ('trackid=f026ac6c9960cd4b85fa89761611e114' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 22];  ]' 'API' 'VDI.create' (('name_label' 'New virtual disk' '' '') ('name_description' '' '' '') ('SR' 'STR1' '8689edd5-7cfd-cafa-8ea6-e3ec42adf8fc' 'OpaqueRef:1c127723-9345-dcd0-e592-83347c569774')))

Feb  3 11:10:19 sx2 xapi: [20180203T13:10:19.572Z|audit|sx2|1614 INET :::80|handler:http/rrd_updates D:3a2746c21879|audit] ('trackid=c6f9a5c2c26745c8355dedb717a9eeae' 'LOCAL_SUPERUSER' '' 'ALLOWED' 'OK' 'HTTP' 'http/rrd_updates' ())

Feb  3 11:11:42 sx2 xapi: [20180203T13:11:42.862Z|audit|sx2|1619 INET :::80|VDI.create R:aeb8c3c4df30|audit] ('trackid=f026ac6c9960cd4b85fa89761611e114' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 22];  ]' 'API' 'VDI.create' (('name_label' 'New virtual disk' '' '') ('name_description' '' '' '') ('SR' 'STR1' '8689edd5-7cfd-cafa-8ea6-e3ec42adf8fc' 'OpaqueRef:1c127723-9345-dcd0-e592-83347c569774')))

==> blktap <==

==> boot.log <==

[^[[32m  OK  ^[[0m] Reached target Remote File Systems (Pre).^M

[^[[32m  OK  ^[[0m] Reached target Remote File Systems.^M

         Starting Permit User Sessions...^M

[^[[32m  OK  ^[[0m] Started Login Service.^M

[^[[32m  OK  ^[[0m] Started Move kernel messages to tty2.^M

[^[[32m  OK  ^[[0m] Started Permit User Sessions.^M

         Starting Wait for Plymouth Boot Screen to Quit...^M

[^[[32m  OK  ^[[0m] Started Job spooling tools.^M

         Starting Job spooling tools...^M

         Starting Terminate Plymouth Boot Screen...^M

==> btmp <==

==> cluster <==

==> cron <==

Feb  3 11:01:15 sx2 crond[3365]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 12% if used.)

Feb  3 11:01:15 sx2 crond[3365]: (CRON) INFO (running with inotify support)

Feb  3 11:10:01 sx2 CROND[11765]: (root) CMD (/usr/lib64/sa/sa1 1 1)

==> daemon.log <==

Feb  3 11:09:19 sx2 mpathalert: [debug|sx2|2 ||mscgen] mpathalert=>xapi [label="host.get_all_records"];

Feb  3 11:10:01 sx2 systemd[1]: Started Session 2 of user root.

Feb  3 11:10:01 sx2 systemd[1]: Starting Session 2 of user root.

Feb  3 11:11:19 sx2 mpathalert: [debug|sx2|2 ||mscgen] mpathalert=>xapi [label="PBD.get_all_records"];

Feb  3 11:11:19 sx2 mpathalert: [debug|sx2|2 ||mscgen] mpathalert=>xapi [label="host.get_all_records"];

Feb  3 11:11:24 sx2 systemd[1]: Started Session 3 of user root.

Feb  3 11:11:24 sx2 systemd[1]: Starting Session 3 of user root.

Feb  3 11:11:42 sx2 multipathd: dm-2: remove map (uevent)

Feb  3 11:11:42 sx2 multipathd: dm-2: devmap not registered, can't remove

Feb  3 11:11:42 sx2 multipathd: dm-2: remove map (uevent)

==> dmesg <==

[   65.433735] tg3 0000:02:00.1 side-6582-eth3: renamed from eth3

[   65.481904] Adding 1048572k swap on /dev/sda6.  Priority:-1 extents:1 across:1048572k

[   65.534859] tg3 0000:02:00.0 side-1222-eth2: renamed from eth2

[   65.690897] tg3 0000:01:00.1 side-2859-eth1: renamed from eth1

[   65.854738] tg3 0000:01:00.0 side-2545-eth0: renamed from eth0

[   66.161992] EXT4-fs (sda5): mounting ext3 file system using the ext4 subsystem

[   66.191955] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)

[   66.491436] systemd-journald[1046]: Received request to flush runtime journal from PID 1

[   67.146095] device-mapper: multipath: version 1.10.0 loaded

[   68.148223] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)

==> installer <==

==> interface-rename.log <==

INFO     [2018-02-03 11:00:07] nic 'side-2859-eth1->(90:b1:1c:1c:c5:e1,0000:01:00.1)' in the same location as before. Renaming to eth1

INFO     [2018-02-03 11:00:07] Considering 'side-1222-eth2->(90:b1:1c:1c:c5:e2,0000:02:00.0)'

INFO     [2018-02-03 11:00:07] nic 'side-1222-eth2->(90:b1:1c:1c:c5:e2,0000:02:00.0)' in the same location as before. Renaming to eth2

INFO     [2018-02-03 11:00:07] Considering 'side-6582-eth3->(90:b1:1c:1c:c5:e3,0000:02:00.1)'

INFO     [2018-02-03 11:00:07] nic 'side-6582-eth3->(90:b1:1c:1c:c5:e3,0000:02:00.1)' in the same location as before. Renaming to eth3

INFO     [2018-02-03 11:00:07] Succesfully renamed link side-2545-eth0 to eth0

INFO     [2018-02-03 11:00:08] Succesfully renamed link side-2859-eth1 to eth1

INFO     [2018-02-03 11:00:08] Succesfully renamed link side-1222-eth2 to eth2

INFO     [2018-02-03 11:00:08] Succesfully renamed link side-6582-eth3 to eth3

INFO     [2018-02-03 11:00:08] All done

==> kern.log <==

Feb  3 11:11:41 sx2 kernel: [  765.703630] sd 1:0:0:0: [sdc] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

Feb  3 11:11:41 sx2 kernel: [  765.703648] sd 1:0:0:0: [sdc] tag#1 Sense Key : Aborted Command [current]

Feb  3 11:11:41 sx2 kernel: [  765.703664] sd 1:0:0:0: [sdc] tag#1 Add. Sense: Internal target failure

Feb  3 11:11:41 sx2 kernel: [  765.703669] sd 1:0:0:0: [sdc] tag#1 CDB: Write(16) 8a 00 00 00 00 00 00 00 88 02 00 00 08 00 00 00

Feb  3 11:11:41 sx2 kernel: [  765.703673] blk_update_request: I/O error, dev sdc, sector 34818

Feb  3 11:11:41 sx2 kernel: [  765.706133] sd 1:0:0:0: [sdc] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

Feb  3 11:11:41 sx2 kernel: [  765.706169] sd 1:0:0:0: [sdc] tag#2 Sense Key : Aborted Command [current]

Feb  3 11:11:41 sx2 kernel: [  765.706175] sd 1:0:0:0: [sdc] tag#2 Add. Sense: Internal target failure

Feb  3 11:11:41 sx2 kernel: [  765.706180] sd 1:0:0:0: [sdc] tag#2 CDB: Write(16) 8a 00 00 00 00 00 00 00 80 02 00 00 08 00 00 00

Feb  3 11:11:41 sx2 kernel: [  765.706183] blk_update_request: I/O error, dev sdc, sector 32770

==> lastlog <==

Em sexta-feira, 2 de fevereiro de 2018 23:45:47 UTC-2, Samir Hanna Verza escreveu:

[Marc Smith]

I'm assuming "sdc" is the SCSI disk block device of the LUN you
presented from ESOS? Can you confirm... this is a brand new RAID
volume on the ESOS side, never used before, correct? If so, when you
swapped between dev_disk and vdisk_blockio this could cause problems,
especially if a disk label was written using one, then attempting to
access via another. Unmap the LUN, then do a complete write of zeros
(eg, using dd) from the ESOS side, then map the LUN again but use
vdisk_blockio and keep the default block size of 512.

--Marc

>
> ==> lastlog <==
>
>
>
>
>
>
>
>
>
> Em sexta-feira, 2 de fevereiro de 2018 23:45:47 UTC-2, Samir Hanna Verza
> escreveu:
>>
>> Hi,
>>
>> I was using ESOS 0.9 on one DELL R720 with PERC H710 and two H810 one for
>> each MD1200 drawer connected to servers using XenServer 7.2 with QLE 2464.
>> It was working fine with dev_disk.
>>
>> As I needed to change from RAID10 to RAID5 one of the drawers for saving
>> legacy, I decided to upgrade the OS to the latest version. We set up the
>> RAIDs again and generated the flash drive with version 1.3.5. However to our
>> surprise we are not able to insert the LUNs in the XenServer, only the LUN
>> of the PERC H710 has gone up, but when we try to mount a disk to a VM in
>> this LUN of a VDI error.
>>
>> We try to switch to vdisk_blockio and others but when the LUN rises on the
>> XenServer of the VDI error.
>>
>> What I might be doing wrong, the most basic thing I did was the group, add
>> the initiator, add the dev_disk on LUN 0. In XenServer it finds the HBA asks
>> to format but of the VDI error when adding the disk in a VM, already with
>> the PERC H810 the XenServer finds the LUN, but when I command add of the
>> error creating the HBA hardware.
>>
>> I will add the photos because I do not know what to do anymore, we already
>> tried to get the ESOS version back to 0.9 but it continued to generate the
>> same problem.
>>
>> Thanks in advance
>

[Samir Hanna Verza]

That's it!

Working fine again!!! Thank you!

Best regards!!

Em sexta-feira, 2 de fevereiro de 2018 23:45:47 UTC-2, Samir Hanna Verza escreveu: