<div dir="ltr">Thanks for the help!<div><br></div><div>I managed to fix it :-)</div><div><br></div><div>I made a device from the hosted engine file with losetup and for the LVM again.</div><div>From there I was able to fsck my partition. And answered a lot of y to the list of inconsistences.</div><div><span style="line-height:1.5">I removed the loop back devices.</span></div><div><span style="line-height:1.5">I turned off maintenance mode and hosted engine started :-)</span><br></div><div><span style="line-height:1.5">Few hours later , restore of the pgsql db and scratching my head, v</span><span style="line-height:1.5">ery happy it is running again without any VMS being offline meanwhile :)</span></div><div><br></div><div><span style="line-height:1.5">I will defintely save the way to start hosted-engine with cd iso, as this seems less error sensitive and easier to do.</span><br></div><div><br></div><div><br><br></div><div>Thanks!</div><div><br></div><br><div class="gmail_quote"><div dir="ltr">Op vr 15 apr. 2016 om 11:35 schreef Simone Tiraboschi <<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>>:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Apr 15, 2016 at 11:02 AM, Paul Groeneweg | Pazion<br>
<<a href="mailto:paul@pazion.nl" target="_blank">paul@pazion.nl</a>> wrote:<br>
> Thanks!<br>
><br>
> I managed to get the console through:<br>
><br>
> hosted-engine --add-console-password<br>
> /bin/remote-viewer vnc://localhost:5900<br>
><br>
> Turns out, there seems to be some corruption on the partition:<br>
> <a href="http://screencast.com/t/6iR0U3QuI" rel="noreferrer" target="_blank">http://screencast.com/t/6iR0U3QuI</a><br>
><br>
> Is there a way to boot from CD, so I can start rescue mode?<br>
<br>
Yes,<br>
you have to set global maintenance mode to avoid VM start attempts on<br>
other hosts.<br>
<br>
You have to poweroff the engine VM with:<br>
hosted-engine --vm-shutdown/--vm-poweroff (probably the second one in<br>
your case)<br>
Then you have to create a copy of<br>
/var/run/ovirt-hosted-engine-ha/vm.conf and you have to manually edit<br>
it in order to attach the ISO image and change the boot order.<br>
At that point you can start the engine VM with your custom configuration with:<br>
hosted-engine --vm-start --vm-conf=my_custom_vm.conf<br>
<br>
Good luck!<br>
<br>
> Op vr 15 apr. 2016 om 10:58 schreef Martin Sivak <<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>>:<br>
>><br>
>> Hi,<br>
>><br>
>> you can access the console using vnc or use virsh to get access to the<br>
>> serial console.<br>
>><br>
>> Check the following commands on the host where the VM is currently<br>
>> running:<br>
>><br>
>> virsh -r list<br>
>> virsh -r console HostedEngine<br>
>> virsh -r vncdisplay HostedEngine<br>
>><br>
>> Those should give you enough pointers to connect to the VM.<br>
>><br>
>> Regards<br>
>><br>
>> Martin Sivak<br>
>><br>
>><br>
>><br>
>> On Fri, Apr 15, 2016 at 10:14 AM, Paul Groeneweg | Pazion<br>
>> <<a href="mailto:paul@pazion.nl" target="_blank">paul@pazion.nl</a>> wrote:<br>
>> ><br>
>> > Tonight my server with NFS hosted-engine mount crashed.<br>
>> > Now all is back online ,except the hosted engine. I can't ping or ssh<br>
>> > the<br>
>> > machine<br>
>> ><br>
>> > when I do hosted-engine --vm-status, I get:<br>
>> ><br>
>> > ..........<br>
>> > --== Host 2 status ==--<br>
>> ><br>
>> > Status up-to-date : True<br>
>> > Hostname : <a href="http://geisha-3.pazion.nl" rel="noreferrer" target="_blank">geisha-3.pazion.nl</a><br>
>> > Host ID : 2<br>
>> > Engine status : {"reason": "failed liveliness<br>
>> > check",<br>
>> > "health": "bad", "vm": "up", "detail": "up"}<br>
>> > Score : 3400<br>
>> > stopped : False<br>
>> > Local maintenance : False<br>
>> > crc32 : d71d7c6b<br>
>> > Host timestamp : 4404<br>
>> > ............<br>
>> ><br>
>> > I tried restarting all services/nfs mounts, start hosted engine on other<br>
>> > hosts, but all the same host up, but liveliness failed and unable to<br>
>> > access<br>
>> > the network/IP.<br>
>> ><br>
>> > I imagine it is stuck at the console requiring a fsck check maybe?<br>
>> > Is there a way to access the boot display directly?<br>
>> ><br>
>> > Any help is highly appreciated!<br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Users mailing list<br>
>> > <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
>> > <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
>> ><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
</blockquote></div></div>