Re: Ovirt 4.2.7 won't start and drops to emergency console

If it's a replicated volume - then you can safely rebuild your bricks and don't even tryhto repair. There is no guarantee that the issue will not reoccur. Best Regards, Strahil NikolovOn Sep 29, 2019 00:22, jeremy_tourville@hotmail.com wrote:
I see evidence that appears to be a problem with gluster. /var/log/messages has multiple occurrences of: WARNING: /dev/gluster_vg1/lv_<name>: Thin's tihin-pool needs inspection. Also, if I run vgs I am returned info for my other volume groups but not gluster_vg1. Lastly, when reviewing journalctl -xb | grep -i timed I see messages from systemd Job dev-gluster_vg1-lv_vmdisks.device/start timed.out. Timed out waiting for device dev-glustet_vg1-lv_vmdisks.device
Thses messages are happening for both /dev/gluster_vg1/lv_datadisks /dev/gluster_vg1/lv_vmdisks
I did review the article here but I am unable to change to VG1. https://mellowhost.com/billing/index.php?rp=/knowledgebase/65/How-to-Repair-...
Can anyone assist with a procedure on how to repair? _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VCHU2Q4RD5QWNM...

Thank you for the reply. Please pardon my ignorance, I'm not very good with GlusterFS. I don't think this is a replicated volume (though I could be wrong) I built a single node hyperconverged hypervisor. I was reviewing my gdeploy file from when I originally built the system. I have the following values: PV = /dev/sda VG1= gluster_vg1 LV1= engine_lv (thick) LV2 = gluster_vg1 thinpool LV3 = lv_vmdisks (thinpooll) LV4 = lv_datadisks (thinpool) So according to the article I read in my OP, it says to deactivate the volumes under the thin pool as the first step. I ran the command lvchange -an /dev/gluster_vg1/lv_datadisks When I do this I am told Volume group "gluster_vg1" not found. Cannot process volume group gluster_vg1. That seems consistent with the timeout error message. How do you fix this if you can't access the volumes? Thoughts?
participants (2)
-
jeremy_tourville@hotmail.com
-
Strahil