<div dir="ltr">Thank you for your advice, yesterday, after 5 hours vm ovirt-engine starts. I suffered all the virtual machines on the old server Xen., except for one large volume. Later, when I can move and it will be to understand what happened to the ISCSI storage.<br></div><br><div class="gmail_quote"><div dir="ltr">пн, 20 февр. 2017 г. в 9:44, Yedidyah Bar David &lt;<a href="mailto:didi@redhat.com">didi@redhat.com</a>&gt;:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, Feb 19, 2017 at 12:42 PM, Денис Мишанин &lt;<a href="mailto:mishanindv@gmail.com" class="gmail_msg" target="_blank">mishanindv@gmail.com</a>&gt; wrote:<br class="gmail_msg">
&gt; Hello.<br class="gmail_msg">
&gt; After restarting the ISCSI storage I can not run ovirt-engine in prodation<br class="gmail_msg">
&gt; use I am looking for help<br class="gmail_msg">
<br class="gmail_msg">
You have this in vdsm.log:<br class="gmail_msg">
<br class="gmail_msg">
Thread-640::DEBUG::2017-02-19<br class="gmail_msg">
13:40:35,756::lvm::288::Storage.Misc.excCmd::(cmd) /usr/bin/taskset<br class="gmail_msg">
--cpu-list 0-23 /usr/bin/sudo -n /usr/sbin/lvm vgs --config &#39; devices<br class="gmail_msg">
{ preferred_names = [<br class="gmail_msg">
&quot;^/dev/mapper/&quot;] ignore_suspended_devices=1 write_cache_state=0<br class="gmail_msg">
disable_after_error_count=3 filter = [<br class="gmail_msg">
&#39;\&#39;&#39;a|/dev/mapper/3600605b00a20bf201e29c6bf236a6651|&#39;\&#39;&#39;,<br class="gmail_msg">
&#39;\&#39;&#39;r|.*|&#39;\&#39;&#39; ] }  global {<br class="gmail_msg">
 locking_type=1  prioritise_write_locks=1  wait_for_locks=1<br class="gmail_msg">
use_lvmetad=0 }  backup {  retain_min = 50  retain_days = 0 } &#39;<br class="gmail_msg">
--noheadings --units b --nosuffix --separator &#39;|&#39; --ignoreskippe<br class="gmail_msg">
dcluster -o uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free,lv_count,pv_count,pv_name<br class="gmail_msg">
c7c466c5-983d-40b2-8f8c-d569755281f5 (cwd None)<br class="gmail_msg">
Thread-640::DEBUG::2017-02-19<br class="gmail_msg">
13:40:35,784::lvm::288::Storage.Misc.excCmd::(cmd) FAILED: &lt;err&gt; = &#39;<br class="gmail_msg">
WARNING: Not using lvmetad because config setting use_lvmetad=0.\n<br class="gmail_msg">
WARNING: To avoid cor<br class="gmail_msg">
ruption, rescan devices to make changes visible (pvscan --cache).\n<br class="gmail_msg">
Volume group &quot;c7c466c5-983d-40b2-8f8c-d569755281f5&quot; not found\n<br class="gmail_msg">
Cannot process volume group c7c466c5-983d-40b2-8f8c-d56<br class="gmail_msg">
9755281f5\n&#39;; &lt;rc&gt; = 5<br class="gmail_msg">
Thread-640::WARNING::2017-02-19<br class="gmail_msg">
13:40:35,785::lvm::376::Storage.LVM::(_reloadvgs) lvm vgs failed: 5 []<br class="gmail_msg">
[&#39;  WARNING: Not using lvmetad because config setting use_lvmetad=0.&#39;,<br class="gmail_msg">
&#39;  WARNING: To<br class="gmail_msg">
avoid corruption, rescan devices to make changes visible (pvscan<br class="gmail_msg">
--cache).&#39;, &#39;  Volume group &quot;c7c466c5-983d-40b2-8f8c-d569755281f5&quot; not<br class="gmail_msg">
found&#39;, &#39;  Cannot process volume group c7c466c5-983d-<br class="gmail_msg">
40b2-8f8c-d569755281f5&#39;]<br class="gmail_msg">
<br class="gmail_msg">
Not sure what might have caused this.<br class="gmail_msg">
<br class="gmail_msg">
Is your iSCSI storage ok after the reboot?<br class="gmail_msg">
<br class="gmail_msg">
You might try to reboot the client (host) or further debug it on<br class="gmail_msg">
kernel/iSCSI level. Check e.g. &#39;lsblk&#39;, iscsiadm, etc.<br class="gmail_msg">
<br class="gmail_msg">
Best,<br class="gmail_msg">
--<br class="gmail_msg">
Didi<br class="gmail_msg">
</blockquote></div>