Failed to connect to lvmetad - Stuck on boot
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 at 12:04
Zanna
49.9k13130237
asked Oct 27 '17 at 14:59
Ravers
16315
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 at 12:04
Zanna
49.9k13130237
asked Oct 27 '17 at 14:59
Ravers
16315
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 at 12:04
Zanna
49.9k13130237
asked Oct 27 '17 at 14:59
Ravers
16315
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 at 12:04
Zanna
49.9k13130237
asked Oct 27 '17 at 14:59
Ravers
16315
edited Dec 10 at 12:04
Zanna
49.9k13130237
asked Oct 27 '17 at 14:59
Ravers
16315
edited Dec 10 at 12:04
Zanna
49.9k13130237
edited Dec 10 at 12:04
Zanna
49.9k13130237
edited Dec 10 at 12:04
Zanna
49.9k13130237
49.9k13130237
asked Oct 27 '17 at 14:59
Ravers
16315
asked Oct 27 '17 at 14:59
Ravers
16315
asked Oct 27 '17 at 14:59
Ravers
16315
16315
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 |
1 Answer
1
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 at 16:06
pim
1,840825
answered Feb 5 at 22:03
Blakethepatton
818
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 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 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 at 12:35
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
1 Answer
1
active
oldest
votes
1 Answer
1
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 at 16:06
pim
1,840825
answered Feb 5 at 22:03
Blakethepatton
818
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 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 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 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 at 16:06
pim
1,840825
answered Feb 5 at 22:03
Blakethepatton
818
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 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 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 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 at 16:06
pim
1,840825
answered Feb 5 at 22:03
Blakethepatton
818
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 at 16:06
pim
1,840825
answered Feb 5 at 22:03
Blakethepatton
818
edited Dec 10 at 16:06
pim
1,840825
edited Dec 10 at 16:06
pim
1,840825
edited Dec 10 at 16:06
pim
1,840825
1,840825
answered Feb 5 at 22:03
Blakethepatton
818
answered Feb 5 at 22:03
Blakethepatton
818
answered Feb 5 at 22:03
Blakethepatton
818
818
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 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 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 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 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 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 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 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 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 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 at 22:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 at 12:35
Nah... I just put linux aside for some weeks and started working on other things.
– Ravers
Feb 7 at 12:35
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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