Here is the part referring to the last attempt of sr-probe
[14338] 2012-12-08 13:28:01.795411 Setting LVM_DEVICE to
/dev/disk/by-scsid/3600c0ff000134320d6dab75001000000
[14338] 2012-12-08 13:28:01.804276 Setting LVM_DEVICE to
/dev/disk/by-scsid/3600c0ff000134320d6dab75001000000
[14338] 2012-12-08 13:28:01.833284 LVMCache created for
VG_XenStorage-
[14338] 2012-12-08 13:28:01.833563 lock: closed /var/lock/sm/sr
[14338] 2012-12-08 13:28:01.833669 LVMCache created for
VG_XenStorage-
[14338] 2012-12-08 13:28:01.833913 sr_probe {'subtask_of':
'OpaqueRef:c9a23e90-3535-9bd2-e901-d50a860501d8', 'sr_sm_config': {},
'args': [], 'host_ref'$
[14338] 2012-12-08 13:28:01.834056 mpath cmd: list maps
[14338] 2012-12-08 13:28:01.846616 mpath output: multipathd>
multipathd>
[14338] 2012-12-08 13:28:01.846820 Refreshing LUN
3600c0ff000134320d6dab75001000000
[14338] 2012-12-08 13:28:01.846965 ['ls', '/sys/class/scsi_host',
'-1', '--color=never']
[14338] 2012-12-08 13:28:01.858676 pread SUCCESS
[14338] 2012-12-08 13:28:01.859584 Full rescan of HostID 0
[14338] 2012-12-08 13:28:04.062037 Refreshing channel 0:0:0
[14338] 2012-12-08 13:28:04.063085 Dom0 disks: ['/dev/sda']
[14338] 2012-12-08 13:28:04.063183 ['/usr/bin/sg_luns', '-q',
'/dev/disk/by-scsibus/3600508b1001cd7d63a2561e9f119d5a9-0:0:0:0']
[14338] 2012-12-08 13:28:04.085292 FAILED in util.pread: (rc 9)
stdout: '', stderr: 'Report Luns command not supported (support
mandatory in SPC-3)
'
[14338] 2012-12-08 13:28:04.085482 Failed to detect or query LUN
on Channel 0:0:0
[14338] 2012-12-08 13:29:04.722586 ***** generic exception:
sr_probe: EXCEPTION SR.SROSError, Error reporting error, unknown key
Device not appeared yet
File "/opt/xensource/sm/SRCommand.py", line 96, in run
return self._run_locked(sr)
File "/opt/xensource/sm/SRCommand.py", line 143, in _run_locked
return self._run(sr, target)
File "/opt/xensource/sm/SRCommand.py", line 269, in _run
txt = sr.probe()
File "/opt/xensource/sm/LVMoHBASR", line 162, in probe
self.mpathmodule.refresh(self.SCSIid,0)
File "/opt/xensource/sm/mpath_dmp.py", line 179, in refresh
raise xs_errors.XenError('Device not appeared yet')
File "/opt/xensource/sm/xs_errors.py", line 52, in __init__
raise SR.SROSError(1, "Error reporting error, unknown key %s" % key)
[14338] 2012-12-08 13:29:04.722979 lock: closed /var/lock/sm/sr
*From:*xen-api-boun...@lists.xen.org
[mailto:xen-api-boun...@lists.xen.org] *On Behalf Of *George Shuklin
*Sent:* Friday, December 07, 2012 10:34 PM
*To:* xen-...@lists.xensource.com
*Subject:* Re: [Xen-API] XCP and HBA storage problem.
Ok, now it at least visible what happens.
next step: look to the /var/log/SMlog after sr-probe.
PS Please, reply to maillist, i'm not a personal support service.
On 07.12.2012 11:56, Yatsko Mykhailo wrote:
Well, I can’t even probe the device.
xe sr-probe type=lvmohba returns
Error code: SR_BACKEND_FAILURE_107
Error parameters: , The SCSIid parameter is missing or incorrect,
<?xml version="1.0" ?>
If I set the SCSIid - xe sr-probe type=lvmohba device-config:SCSIid=*****
Error code: SR_BACKEND_FAILURE_1
Error parameters: , Error reporting error, unknown key Device not
appeared yet,
And xe sr-create shared=true type=lvmohba name-label=LUN9
device-config:SCSIid=**** returns the same
Error code: SR_BACKEND_FAILURE_1
Error parameters: , Error reporting error, unknown key Device not
appeared yet,
As for software iSCSI – I can easily fire it up through XenCenter with
multipathing and all the stuff I need, but using HBA capabilities is
quite critical to me. If it may help, the device I use is HP
StorageWorks P2000 G3 with 4 1Gbit Ethernet storage ports per
controller. The wiring is OK, I doublechecked it. Also I even tried to
connect the storage directly to the servers to get rid of possible
failure point at the switch.
*From:*xen-api-boun...@lists.xen.org
<mailto:xen-api-boun...@lists.xen.org>
[mailto:xen-api-boun...@lists.xen.org] *On Behalf Of *George Shuklin
*Sent:* Thursday, December 06, 2012 10:25 PM
*To:* xen-...@lists.xensource.com <mailto:xen-...@lists.xensource.com>
*Subject:* Re: [Xen-API] XCP and HBA storage problem.
Well, may be output of the xe sr-create should be attached? Guessing
'what is wrong' is kinda useless activity without logs or command output.
On 06.12.2012 20:08, Yatsko Mykhailo wrote:
Certainly. And lvmoiscsi works fine. I need to fire it up as lvmohba,
which causes troubles.
/З повагою,
Яцко Михайло Володимирович
Системний адміністратор
Adelina Holding LLC
Відділ технічної підтримки
_________________________________
03065, м. Киів, бул. Лепсе//, 4
E-mail: myat...@adelina.com.ua <mailto:myat...@adelina.com.ua>
Web: www.adelina.com.ua <http://www.adelina.com.ua>
//Моб//.: +380501440657
//Факс//: +38 (032) 235 17 75/
*From:*xen-api-boun...@lists.xen.org
<mailto:xen-api-boun...@lists.xen.org>
[mailto:xen-api-boun...@lists.xen.org] *On Behalf Of *George Shuklin
*Sent:* Thursday, December 06, 2012 5:21 PM
*To:* xen-api@lists.xen.org <mailto:xen-api@lists.xen.org>
*Subject:* Re: [Xen-API] XCP and HBA storage problem.
Did you try to performs xe sr-create with type=lvmoiscsi?
05.12.2012 14:45, Yatsko Mykhailo пишет:
Hi everyone.
I am a complete newbie to Xen. I run the following config:
HP ProLiant DL360 G7 server, 2 absolutely identical items, running
latest XCP. They are joined in a pool. Also there is a HP
StorageWorks P2000 G3 storage array. This is the config I have
troubles with.
Currently we are planning to migrate to Xen-based solutions from
VMWare-based. We have other 2 servers (also identical to those
mentioned above), which make use of the same storage device.
VMWare servers connect to the storage over HBA.
XCP ones do not recognize LUNs (though there is one made specially
for them and not in use by any other machine) when adding a HBA
storage, but work fine if adding it as software iSCSI. There are
no restrictions as for access at the storage side, no passwords etc.
Any piece of advice would be highly appreciated.
/З повагою//,
//Яцко Михайло Володимирович//
//Системний адміністратор//
Adelina Holding LLC
//Відділ технічної підтримки//
___________________//______________
03065, м. Киів, бул. Лепсе//, 4
E-mail: myat...@adelina.com.ua <mailto:myat...@adelina.com.ua>
Web: www.adelina.com.ua <http://www.adelina.com.ua>
//Моб//.: +380501440657
//Факс//: +38 (032) 235 17 75/
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org <mailto:Xen-api@lists.xen.org>
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
