Failed to connect to lvmetad - Stuck on bootHow to fix warning failed to connect to lvmetad no such file or directory falling back to internal scanningCan't reach login after Ubuntu 18.04 “Volume group ”ubuntu-vg“ not found”Ubuntu 16.04 -> 18.04 upgrade failed “Failed to connect to lvmetad. Falling back to device scanning”lvmetad error when I turn the computer on or offUbuntu won't boot after power failure - can't connect to lvmetadUbuntu 18.04 - cryptsetup fails to recognize passphrase, unlocking from Live USB worksFailed to connect to lvmetad in Virtual Box VMUbuntu server 16.04 won't boot after installationlvmetad is blocking boot processUpgrade to 16.04 - now won't bootUbuntu won't boot after power failure - can't connect to lvmetadlvmetad and kernel 4.13.0-25 problemFailed to startup : ubuntu--vg-root cleanAfter upgrade 17.10 -> 18.04 I get: Failed to connect to lvmetadLVM partition config causing boot delay because it's “Failing to connect to Lvmetad”Two problems in one? Failed to load lvmetad and you don't have enough free spaceFalling back to device scanning
Is there a way to make cleveref distinguish two environments with the same counter?
What does the Digital Threat scope actually do?
Do black holes violate the conservation of mass?
Should we avoid writing fiction about historical events without extensive research?
Automaton recognizing ambiguously accepted words of another automaton
Was it really inappropriate to write a pull request for the company I interviewed with?
What should I do when a paper is published similar to my PhD thesis without citation?
Can the Witch Sight warlock invocation see through the Mirror Image spell?
What can I do if someone tampers with my SSH public key?
Is there a math expression equivalent to the conditional ternary operator?
Would those living in a "perfect society" not understand satire
Rationale to prefer local variables over instance variables?
What is Tony Stark injecting into himself in Iron Man 3?
What would be the most expensive material to an intergalactic society?
Is there stress on two letters on the word стоят
Converting from "matrix" data into "coordinate" data
What is this tube in a jet engine's air intake?
Is divide-by-zero a security vulnerability?
Having the player face themselves after the mid-game
Are these two graphs isomorphic? Why/Why not?
Professor forcing me to attend a conference, I can't afford even with 50% funding
Why does this boat have a landing pad? (SpaceX's GO Searcher) Any plans for propulsive capsule landings?
ESPP--any reason not to go all in?
Writing text next to a table
Failed to connect to lvmetad - Stuck on boot
How to fix warning failed to connect to lvmetad no such file or directory falling back to internal scanningCan't reach login after Ubuntu 18.04 “Volume group ”ubuntu-vg“ not found”Ubuntu 16.04 -> 18.04 upgrade failed “Failed to connect to lvmetad. Falling back to device scanning”lvmetad error when I turn the computer on or offUbuntu won't boot after power failure - can't connect to lvmetadUbuntu 18.04 - cryptsetup fails to recognize passphrase, unlocking from Live USB worksFailed to connect to lvmetad in Virtual Box VMUbuntu server 16.04 won't boot after installationlvmetad is blocking boot processUpgrade to 16.04 - now won't bootUbuntu won't boot after power failure - can't connect to lvmetadlvmetad and kernel 4.13.0-25 problemFailed to startup : ubuntu--vg-root cleanAfter upgrade 17.10 -> 18.04 I get: Failed to connect to lvmetadLVM partition config causing boot delay because it's “Failing to connect to Lvmetad”Two problems in one? Failed to load lvmetad and you don't have enough free spaceFalling back to device scanning
I upgraded my PC to Ubuntu 17.10, and now that I've restarted my PC I get this message:
Failed to connect to lvmetad.
Falling back to device scanning.
/dev/mapper/ubuntu--vg--root: clean, 500699/15081472 files, 9150222/60315648 blocks
It gets stuck on this.
What's the problem and how can I fix it?
boot upgrade lvm ubuntu-gnome
edited Dec 10 '18 at 12:04
Zanna
51k13137241
asked Oct 27 '17 at 14:59
RaversRavers
163115
add a comment |
I upgraded my PC to Ubuntu 17.10, and now that I've restarted my PC I get this message:
Failed to connect to lvmetad.
Falling back to device scanning.
/dev/mapper/ubuntu--vg--root: clean, 500699/15081472 files, 9150222/60315648 blocks
It gets stuck on this.
What's the problem and how can I fix it?
boot upgrade lvm ubuntu-gnome
edited Dec 10 '18 at 12:04
Zanna
51k13137241
asked Oct 27 '17 at 14:59
RaversRavers
163115
2
Until someone can weigh in on a real solution, I've found booting with an older Kernel works. At boot time, pull up your boot menu (for me, hitting "Esc" or "F9" at the BIOS screen), then select "Ubuntu with Advanced Options" then pick an older Kernel version #.
– chucksense
Oct 27 '17 at 19:37
add a comment |
I upgraded my PC to Ubuntu 17.10, and now that I've restarted my PC I get this message:
Failed to connect to lvmetad.
Falling back to device scanning.
/dev/mapper/ubuntu--vg--root: clean, 500699/15081472 files, 9150222/60315648 blocks
It gets stuck on this.
What's the problem and how can I fix it?
boot upgrade lvm ubuntu-gnome
edited Dec 10 '18 at 12:04
Zanna
51k13137241
asked Oct 27 '17 at 14:59
RaversRavers
163115
I upgraded my PC to Ubuntu 17.10, and now that I've restarted my PC I get this message:
Failed to connect to lvmetad.
Falling back to device scanning.
/dev/mapper/ubuntu--vg--root: clean, 500699/15081472 files, 9150222/60315648 blocks
It gets stuck on this.
What's the problem and how can I fix it?
boot upgrade lvm ubuntu-gnome
boot upgrade lvm ubuntu-gnome
edited Dec 10 '18 at 12:04
Zanna
51k13137241
asked Oct 27 '17 at 14:59
RaversRavers
163115
edited Dec 10 '18 at 12:04
Zanna
51k13137241
asked Oct 27 '17 at 14:59
RaversRavers
163115
edited Dec 10 '18 at 12:04
Zanna
51k13137241
edited Dec 10 '18 at 12:04
Zanna
51k13137241
edited Dec 10 '18 at 12:04
Zanna
51k13137241
51k13137241
asked Oct 27 '17 at 14:59
RaversRavers
163115
asked Oct 27 '17 at 14:59
RaversRavers
163115
asked Oct 27 '17 at 14:59
RaversRavers
163115
163115
2
Until someone can weigh in on a real solution, I've found booting with an older Kernel works. At boot time, pull up your boot menu (for me, hitting "Esc" or "F9" at the BIOS screen), then select "Ubuntu with Advanced Options" then pick an older Kernel version #.
– chucksense
Oct 27 '17 at 19:37
add a comment |
2
Until someone can weigh in on a real solution, I've found booting with an older Kernel works. At boot time, pull up your boot menu (for me, hitting "Esc" or "F9" at the BIOS screen), then select "Ubuntu with Advanced Options" then pick an older Kernel version #.
– chucksense
Oct 27 '17 at 19:37
2
2
Until someone can weigh in on a real solution, I've found booting with an older Kernel works. At boot time, pull up your boot menu (for me, hitting "Esc" or "F9" at the BIOS screen), then select "Ubuntu with Advanced Options" then pick an older Kernel version #.
– chucksense
Oct 27 '17 at 19:37
Until someone can weigh in on a real solution, I've found booting with an older Kernel works. At boot time, pull up your boot menu (for me, hitting "Esc" or "F9" at the BIOS screen), then select "Ubuntu with Advanced Options" then pick an older Kernel version #.
– chucksense
Oct 27 '17 at 19:37
add a comment |
2 Answers
2
active
oldest
votes
I had a very similar experience, not sure if it'll help you though. My computer had some updates installed, needed a reboot but hey, nobody got time for that. Well along came a power outage and forced me to reboot. When I turned on my machine, I got just the same message you saw. Crap. I couldn't even get into virtual terminals 1 or 2 either which was really weird. Anyway, I somehow found your post and read that switching the kernel version made everything work. So I went and tried that out and sure enough, what you said applied to me too.
With my primitive knowledge of linux commands, I did get an idea of how to fix this. So I rebooted into the newest kernel, then switched to the virtual terminal ctrl+alt+f3 <- had to use the third because 1 and 2 weren't working. From here I ran sudo apt-get update && sudo apt-get upgrade -y to get everything up to date. Then ran sudo apt-get autoremove to remove the older kernels. Then I re-installed the current kernel (get the version from uname -r) and then I ran sudo apt-get install --reinstall linux-image-4.13.0-32-generic to reinstall the current kernel and rerun all the building of things that might not have been run since I didn't switch to this kernel properly. Finally, I restarted again.
After the restart I was having the same problem still. Welp, maybe it has to do with my graphics drivers? So I went ahead and purged my nvidia drivers sudo apt-get purge nvidia-* and reinstalled the drivers sudo apt-get install nvidia-387 ~ Granted, I don't know what version of their driver I should be using, nvidia afik doesn't have just a standard package that you can install that follows the latest - but this one installed just fine for me... After that super slow install, I restarted again.
And my computer came back to life. Woohoo. I genuinely hope this helps someone. It took me 4 hours of frustrated pounding to get my desktop back and I really hope I can save someone else from that. Thanks for your post and your update, you gave me the lead that I needed to solve this for myself.
edited Dec 10 '18 at 16:06
pim
1,9191925
answered Feb 5 '18 at 22:03
BlakethepattonBlakethepatton
9118
1
It really seems that nvidia drivers are causing this issue. After purging nvidia I could get on my desktop and use the generic display driver that linux provides.
– Ravers
Feb 6 '18 at 11:47
I hope you haven't been having to manually specify your kernal version for the last 3 months... that sounds painful!
– Blakethepatton
Feb 6 '18 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 '18 at 12:35
add a comment |
The accepted answer helped me quite a lot (thank you!)
Though in my case neither booting with an older kernel nor the nvidia driver could solve it... it just turned out my disk had run full (as I saw with df). I could delete files by booting into recovery mode and from then on boot normally again :)
I hope this hint is useful to anyone stuck in this situation
answered 5 hours ago
sssaschasssascha
1
New contributor
sssascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f969917%2ffailed-to-connect-to-lvmetad-stuck-on-boot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had a very similar experience, not sure if it'll help you though. My computer had some updates installed, needed a reboot but hey, nobody got time for that. Well along came a power outage and forced me to reboot. When I turned on my machine, I got just the same message you saw. Crap. I couldn't even get into virtual terminals 1 or 2 either which was really weird. Anyway, I somehow found your post and read that switching the kernel version made everything work. So I went and tried that out and sure enough, what you said applied to me too.
With my primitive knowledge of linux commands, I did get an idea of how to fix this. So I rebooted into the newest kernel, then switched to the virtual terminal ctrl+alt+f3 <- had to use the third because 1 and 2 weren't working. From here I ran sudo apt-get update && sudo apt-get upgrade -y to get everything up to date. Then ran sudo apt-get autoremove to remove the older kernels. Then I re-installed the current kernel (get the version from uname -r) and then I ran sudo apt-get install --reinstall linux-image-4.13.0-32-generic to reinstall the current kernel and rerun all the building of things that might not have been run since I didn't switch to this kernel properly. Finally, I restarted again.
After the restart I was having the same problem still. Welp, maybe it has to do with my graphics drivers? So I went ahead and purged my nvidia drivers sudo apt-get purge nvidia-* and reinstalled the drivers sudo apt-get install nvidia-387 ~ Granted, I don't know what version of their driver I should be using, nvidia afik doesn't have just a standard package that you can install that follows the latest - but this one installed just fine for me... After that super slow install, I restarted again.
And my computer came back to life. Woohoo. I genuinely hope this helps someone. It took me 4 hours of frustrated pounding to get my desktop back and I really hope I can save someone else from that. Thanks for your post and your update, you gave me the lead that I needed to solve this for myself.
edited Dec 10 '18 at 16:06
pim
1,9191925
answered Feb 5 '18 at 22:03
BlakethepattonBlakethepatton
9118
1
It really seems that nvidia drivers are causing this issue. After purging nvidia I could get on my desktop and use the generic display driver that linux provides.
– Ravers
Feb 6 '18 at 11:47
I hope you haven't been having to manually specify your kernal version for the last 3 months... that sounds painful!
– Blakethepatton
Feb 6 '18 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 '18 at 12:35
add a comment |
I had a very similar experience, not sure if it'll help you though. My computer had some updates installed, needed a reboot but hey, nobody got time for that. Well along came a power outage and forced me to reboot. When I turned on my machine, I got just the same message you saw. Crap. I couldn't even get into virtual terminals 1 or 2 either which was really weird. Anyway, I somehow found your post and read that switching the kernel version made everything work. So I went and tried that out and sure enough, what you said applied to me too.
With my primitive knowledge of linux commands, I did get an idea of how to fix this. So I rebooted into the newest kernel, then switched to the virtual terminal ctrl+alt+f3 <- had to use the third because 1 and 2 weren't working. From here I ran sudo apt-get update && sudo apt-get upgrade -y to get everything up to date. Then ran sudo apt-get autoremove to remove the older kernels. Then I re-installed the current kernel (get the version from uname -r) and then I ran sudo apt-get install --reinstall linux-image-4.13.0-32-generic to reinstall the current kernel and rerun all the building of things that might not have been run since I didn't switch to this kernel properly. Finally, I restarted again.
After the restart I was having the same problem still. Welp, maybe it has to do with my graphics drivers? So I went ahead and purged my nvidia drivers sudo apt-get purge nvidia-* and reinstalled the drivers sudo apt-get install nvidia-387 ~ Granted, I don't know what version of their driver I should be using, nvidia afik doesn't have just a standard package that you can install that follows the latest - but this one installed just fine for me... After that super slow install, I restarted again.
And my computer came back to life. Woohoo. I genuinely hope this helps someone. It took me 4 hours of frustrated pounding to get my desktop back and I really hope I can save someone else from that. Thanks for your post and your update, you gave me the lead that I needed to solve this for myself.
edited Dec 10 '18 at 16:06
pim
1,9191925
answered Feb 5 '18 at 22:03
BlakethepattonBlakethepatton
9118
1
It really seems that nvidia drivers are causing this issue. After purging nvidia I could get on my desktop and use the generic display driver that linux provides.
– Ravers
Feb 6 '18 at 11:47
I hope you haven't been having to manually specify your kernal version for the last 3 months... that sounds painful!
– Blakethepatton
Feb 6 '18 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 '18 at 12:35
add a comment |
I had a very similar experience, not sure if it'll help you though. My computer had some updates installed, needed a reboot but hey, nobody got time for that. Well along came a power outage and forced me to reboot. When I turned on my machine, I got just the same message you saw. Crap. I couldn't even get into virtual terminals 1 or 2 either which was really weird. Anyway, I somehow found your post and read that switching the kernel version made everything work. So I went and tried that out and sure enough, what you said applied to me too.
With my primitive knowledge of linux commands, I did get an idea of how to fix this. So I rebooted into the newest kernel, then switched to the virtual terminal ctrl+alt+f3 <- had to use the third because 1 and 2 weren't working. From here I ran sudo apt-get update && sudo apt-get upgrade -y to get everything up to date. Then ran sudo apt-get autoremove to remove the older kernels. Then I re-installed the current kernel (get the version from uname -r) and then I ran sudo apt-get install --reinstall linux-image-4.13.0-32-generic to reinstall the current kernel and rerun all the building of things that might not have been run since I didn't switch to this kernel properly. Finally, I restarted again.
After the restart I was having the same problem still. Welp, maybe it has to do with my graphics drivers? So I went ahead and purged my nvidia drivers sudo apt-get purge nvidia-* and reinstalled the drivers sudo apt-get install nvidia-387 ~ Granted, I don't know what version of their driver I should be using, nvidia afik doesn't have just a standard package that you can install that follows the latest - but this one installed just fine for me... After that super slow install, I restarted again.
And my computer came back to life. Woohoo. I genuinely hope this helps someone. It took me 4 hours of frustrated pounding to get my desktop back and I really hope I can save someone else from that. Thanks for your post and your update, you gave me the lead that I needed to solve this for myself.
edited Dec 10 '18 at 16:06
pim
1,9191925
answered Feb 5 '18 at 22:03
BlakethepattonBlakethepatton
9118
I had a very similar experience, not sure if it'll help you though. My computer had some updates installed, needed a reboot but hey, nobody got time for that. Well along came a power outage and forced me to reboot. When I turned on my machine, I got just the same message you saw. Crap. I couldn't even get into virtual terminals 1 or 2 either which was really weird. Anyway, I somehow found your post and read that switching the kernel version made everything work. So I went and tried that out and sure enough, what you said applied to me too.
With my primitive knowledge of linux commands, I did get an idea of how to fix this. So I rebooted into the newest kernel, then switched to the virtual terminal ctrl+alt+f3 <- had to use the third because 1 and 2 weren't working. From here I ran sudo apt-get update && sudo apt-get upgrade -y to get everything up to date. Then ran sudo apt-get autoremove to remove the older kernels. Then I re-installed the current kernel (get the version from uname -r) and then I ran sudo apt-get install --reinstall linux-image-4.13.0-32-generic to reinstall the current kernel and rerun all the building of things that might not have been run since I didn't switch to this kernel properly. Finally, I restarted again.
After the restart I was having the same problem still. Welp, maybe it has to do with my graphics drivers? So I went ahead and purged my nvidia drivers sudo apt-get purge nvidia-* and reinstalled the drivers sudo apt-get install nvidia-387 ~ Granted, I don't know what version of their driver I should be using, nvidia afik doesn't have just a standard package that you can install that follows the latest - but this one installed just fine for me... After that super slow install, I restarted again.
And my computer came back to life. Woohoo. I genuinely hope this helps someone. It took me 4 hours of frustrated pounding to get my desktop back and I really hope I can save someone else from that. Thanks for your post and your update, you gave me the lead that I needed to solve this for myself.
edited Dec 10 '18 at 16:06
pim
1,9191925
answered Feb 5 '18 at 22:03
BlakethepattonBlakethepatton
9118
edited Dec 10 '18 at 16:06
pim
1,9191925
edited Dec 10 '18 at 16:06
pim
1,9191925
edited Dec 10 '18 at 16:06
pim
1,9191925
1,9191925
answered Feb 5 '18 at 22:03
BlakethepattonBlakethepatton
9118
answered Feb 5 '18 at 22:03
BlakethepattonBlakethepatton
9118
answered Feb 5 '18 at 22:03
BlakethepattonBlakethepatton
9118
9118
1
It really seems that nvidia drivers are causing this issue. After purging nvidia I could get on my desktop and use the generic display driver that linux provides.
– Ravers
Feb 6 '18 at 11:47
I hope you haven't been having to manually specify your kernal version for the last 3 months... that sounds painful!
– Blakethepatton
Feb 6 '18 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 '18 at 12:35
add a comment |
1
It really seems that nvidia drivers are causing this issue. After purging nvidia I could get on my desktop and use the generic display driver that linux provides.
– Ravers
Feb 6 '18 at 11:47
I hope you haven't been having to manually specify your kernal version for the last 3 months... that sounds painful!
– Blakethepatton
Feb 6 '18 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 '18 at 12:35
1
1
It really seems that nvidia drivers are causing this issue. After purging nvidia I could get on my desktop and use the generic display driver that linux provides.
– Ravers
Feb 6 '18 at 11:47
It really seems that nvidia drivers are causing this issue. After purging nvidia I could get on my desktop and use the generic display driver that linux provides.
– Ravers
Feb 6 '18 at 11:47
I hope you haven't been having to manually specify your kernal version for the last 3 months... that sounds painful!
– Blakethepatton
Feb 6 '18 at 22:35
I hope you haven't been having to manually specify your kernal version for the last 3 months... that sounds painful!
– Blakethepatton
Feb 6 '18 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 '18 at 12:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 '18 at 12:35
add a comment |
The accepted answer helped me quite a lot (thank you!)
Though in my case neither booting with an older kernel nor the nvidia driver could solve it... it just turned out my disk had run full (as I saw with df). I could delete files by booting into recovery mode and from then on boot normally again :)
I hope this hint is useful to anyone stuck in this situation
answered 5 hours ago
sssaschasssascha
1
New contributor
sssascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
The accepted answer helped me quite a lot (thank you!)
Though in my case neither booting with an older kernel nor the nvidia driver could solve it... it just turned out my disk had run full (as I saw with df). I could delete files by booting into recovery mode and from then on boot normally again :)
I hope this hint is useful to anyone stuck in this situation
answered 5 hours ago
sssaschasssascha
1
New contributor
sssascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
The accepted answer helped me quite a lot (thank you!)
Though in my case neither booting with an older kernel nor the nvidia driver could solve it... it just turned out my disk had run full (as I saw with df). I could delete files by booting into recovery mode and from then on boot normally again :)
I hope this hint is useful to anyone stuck in this situation
answered 5 hours ago
sssaschasssascha
1
New contributor
sssascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
The accepted answer helped me quite a lot (thank you!)
Though in my case neither booting with an older kernel nor the nvidia driver could solve it... it just turned out my disk had run full (as I saw with df). I could delete files by booting into recovery mode and from then on boot normally again :)
I hope this hint is useful to anyone stuck in this situation
answered 5 hours ago
sssaschasssascha
1
New contributor
sssascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 5 hours ago
sssaschasssascha
1
New contributor
sssascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 5 hours ago
sssaschasssascha
1
answered 5 hours ago
sssaschasssascha
1
1
New contributor
sssascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
sssascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
sssascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f969917%2ffailed-to-connect-to-lvmetad-stuck-on-boot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Until someone can weigh in on a real solution, I've found booting with an older Kernel works. At boot time, pull up your boot menu (for me, hitting "Esc" or "F9" at the BIOS screen), then select "Ubuntu with Advanced Options" then pick an older Kernel version #.
– chucksense
Oct 27 '17 at 19:37