Two problems in one? Failed to load lvmetad and you don't have enough free space
so today I turned on my 18.04 machine for the first time in a month, clicked "okay" to the updater, and seconds later was given a message that said, "You don't have enough free space to install this." Weird, because I have a 1TB hard drive, and I have used maybe 150gb of it. I did apt autoremove, and still had the error, so I started looking up my problem. I tried to install gparted, but failed because there was not enough space. I restarted my computer. On reboot, I encountered a new error: "Failed to load lvmetad, begin device scanning." This led to a halt in the boot process. I have looked each of these problems up, and they seem to be tightly interlaced. To solve the lvmetad problem, it seems that I need to upgrade some files. To solve the space problem, I need to install gparted.
I have followed more than a handful of guides on trying to fix both of these, but to no avail. From these guides, I have come to realize that my boot partition is only ~487mb, and that seems to be the problem. I have tried to figure out if it was possible to boot from the LVM, but I couldn't figure that out. I believe that the root of the problem lies in the especially small boot partition. Any help to get my machine back up and running is greatly appreciated.
Update: I have tried reinstalling using an ISO, but the boot from that also crashes.
Here's my df output:
Just as a note, it is saying that /dev/mapper/ubuntu--vg-root is full, but before upgrading to 18.04, it was maybe 15% full.
Update:So now I ran du | sort -n (because the more complicated version wasn't working for me, and I got (I hope it's not still upside down):
This to me says that /var/log just dumped something in there. Can I just rm everything in there? I feel like that's too simple and too dangerous of an answer.
Update: I removed all .gz files, however no space was freed in /dev/mapper/ubuntu--vg-root.
boot 18.04 filesystem lvm
asked Jan 9 at 18:50
rchurch4rchurch4
1062
|
show 2 more comments
so today I turned on my 18.04 machine for the first time in a month, clicked "okay" to the updater, and seconds later was given a message that said, "You don't have enough free space to install this." Weird, because I have a 1TB hard drive, and I have used maybe 150gb of it. I did apt autoremove, and still had the error, so I started looking up my problem. I tried to install gparted, but failed because there was not enough space. I restarted my computer. On reboot, I encountered a new error: "Failed to load lvmetad, begin device scanning." This led to a halt in the boot process. I have looked each of these problems up, and they seem to be tightly interlaced. To solve the lvmetad problem, it seems that I need to upgrade some files. To solve the space problem, I need to install gparted.
I have followed more than a handful of guides on trying to fix both of these, but to no avail. From these guides, I have come to realize that my boot partition is only ~487mb, and that seems to be the problem. I have tried to figure out if it was possible to boot from the LVM, but I couldn't figure that out. I believe that the root of the problem lies in the especially small boot partition. Any help to get my machine back up and running is greatly appreciated.
Update: I have tried reinstalling using an ISO, but the boot from that also crashes.
Here's my df output:
Just as a note, it is saying that /dev/mapper/ubuntu--vg-root is full, but before upgrading to 18.04, it was maybe 15% full.
Update:So now I ran du | sort -n (because the more complicated version wasn't working for me, and I got (I hope it's not still upside down):
This to me says that /var/log just dumped something in there. Can I just rm everything in there? I feel like that's too simple and too dangerous of an answer.
Update: I removed all .gz files, however no space was freed in /dev/mapper/ubuntu--vg-root.
boot 18.04 filesystem lvm
asked Jan 9 at 18:50
rchurch4rchurch4
1062
gparteddoes not use any space on /boot, so you seem to be muddling you possible problems. Let's find out: Please edit your question to include the complete output ofdf.
– user535733
Jan 9 at 19:19
sorry for the delay @user535733 I've only just gotten back to this problem.
– rchurch4
7 hours ago
Your boot partition seems be a healthy and normal 38%. It does not look like the problem to me. Next, show us the biggest disk space hogs on your filesystem.
– user535733
6 hours ago
I've edited the post above to reflect the new output. The logs are full, which to me says that it just continually wrote logs of something bad that was happening, and that this isn't the true problem.
– rchurch4
6 hours ago
How convenient: That's where I was leading you. Delete all the runaway log files except one to free space. Then read that one to learn the real problem. It really does not matter which one since it's probably the same problem over and over and over....
– user535733
6 hours ago
|
show 2 more comments
so today I turned on my 18.04 machine for the first time in a month, clicked "okay" to the updater, and seconds later was given a message that said, "You don't have enough free space to install this." Weird, because I have a 1TB hard drive, and I have used maybe 150gb of it. I did apt autoremove, and still had the error, so I started looking up my problem. I tried to install gparted, but failed because there was not enough space. I restarted my computer. On reboot, I encountered a new error: "Failed to load lvmetad, begin device scanning." This led to a halt in the boot process. I have looked each of these problems up, and they seem to be tightly interlaced. To solve the lvmetad problem, it seems that I need to upgrade some files. To solve the space problem, I need to install gparted.
I have followed more than a handful of guides on trying to fix both of these, but to no avail. From these guides, I have come to realize that my boot partition is only ~487mb, and that seems to be the problem. I have tried to figure out if it was possible to boot from the LVM, but I couldn't figure that out. I believe that the root of the problem lies in the especially small boot partition. Any help to get my machine back up and running is greatly appreciated.
Update: I have tried reinstalling using an ISO, but the boot from that also crashes.
Here's my df output:
Just as a note, it is saying that /dev/mapper/ubuntu--vg-root is full, but before upgrading to 18.04, it was maybe 15% full.
Update:So now I ran du | sort -n (because the more complicated version wasn't working for me, and I got (I hope it's not still upside down):
This to me says that /var/log just dumped something in there. Can I just rm everything in there? I feel like that's too simple and too dangerous of an answer.
Update: I removed all .gz files, however no space was freed in /dev/mapper/ubuntu--vg-root.
boot 18.04 filesystem lvm
asked Jan 9 at 18:50
rchurch4rchurch4
1062
so today I turned on my 18.04 machine for the first time in a month, clicked "okay" to the updater, and seconds later was given a message that said, "You don't have enough free space to install this." Weird, because I have a 1TB hard drive, and I have used maybe 150gb of it. I did apt autoremove, and still had the error, so I started looking up my problem. I tried to install gparted, but failed because there was not enough space. I restarted my computer. On reboot, I encountered a new error: "Failed to load lvmetad, begin device scanning." This led to a halt in the boot process. I have looked each of these problems up, and they seem to be tightly interlaced. To solve the lvmetad problem, it seems that I need to upgrade some files. To solve the space problem, I need to install gparted.
I have followed more than a handful of guides on trying to fix both of these, but to no avail. From these guides, I have come to realize that my boot partition is only ~487mb, and that seems to be the problem. I have tried to figure out if it was possible to boot from the LVM, but I couldn't figure that out. I believe that the root of the problem lies in the especially small boot partition. Any help to get my machine back up and running is greatly appreciated.
Update: I have tried reinstalling using an ISO, but the boot from that also crashes.
Here's my df output:
Just as a note, it is saying that /dev/mapper/ubuntu--vg-root is full, but before upgrading to 18.04, it was maybe 15% full.
Update:So now I ran du | sort -n (because the more complicated version wasn't working for me, and I got (I hope it's not still upside down):
This to me says that /var/log just dumped something in there. Can I just rm everything in there? I feel like that's too simple and too dangerous of an answer.
Update: I removed all .gz files, however no space was freed in /dev/mapper/ubuntu--vg-root.
boot 18.04 filesystem lvm
boot 18.04 filesystem lvm
asked Jan 9 at 18:50
rchurch4rchurch4
1062
asked Jan 9 at 18:50
rchurch4rchurch4
1062
edited 6 hours ago
rchurch4
asked Jan 9 at 18:50
rchurch4rchurch4
1062
asked Jan 9 at 18:50
rchurch4rchurch4
1062
asked Jan 9 at 18:50
rchurch4rchurch4
1062
1062
gparteddoes not use any space on /boot, so you seem to be muddling you possible problems. Let's find out: Please edit your question to include the complete output ofdf.
– user535733
Jan 9 at 19:19
sorry for the delay @user535733 I've only just gotten back to this problem.
– rchurch4
7 hours ago
Your boot partition seems be a healthy and normal 38%. It does not look like the problem to me. Next, show us the biggest disk space hogs on your filesystem.
– user535733
6 hours ago
I've edited the post above to reflect the new output. The logs are full, which to me says that it just continually wrote logs of something bad that was happening, and that this isn't the true problem.
– rchurch4
6 hours ago
How convenient: That's where I was leading you. Delete all the runaway log files except one to free space. Then read that one to learn the real problem. It really does not matter which one since it's probably the same problem over and over and over....
– user535733
6 hours ago
|
show 2 more comments
gparteddoes not use any space on /boot, so you seem to be muddling you possible problems. Let's find out: Please edit your question to include the complete output ofdf.
– user535733
Jan 9 at 19:19
sorry for the delay @user535733 I've only just gotten back to this problem.
– rchurch4
7 hours ago
Your boot partition seems be a healthy and normal 38%. It does not look like the problem to me. Next, show us the biggest disk space hogs on your filesystem.
– user535733
6 hours ago
I've edited the post above to reflect the new output. The logs are full, which to me says that it just continually wrote logs of something bad that was happening, and that this isn't the true problem.
– rchurch4
6 hours ago
How convenient: That's where I was leading you. Delete all the runaway log files except one to free space. Then read that one to learn the real problem. It really does not matter which one since it's probably the same problem over and over and over....
– user535733
6 hours ago
gparted does not use any space on /boot, so you seem to be muddling you possible problems. Let's find out: Please edit your question to include the complete output of df.– user535733
Jan 9 at 19:19
gparted does not use any space on /boot, so you seem to be muddling you possible problems. Let's find out: Please edit your question to include the complete output of df.– user535733
Jan 9 at 19:19
sorry for the delay @user535733 I've only just gotten back to this problem.
– rchurch4
7 hours ago
sorry for the delay @user535733 I've only just gotten back to this problem.
– rchurch4
7 hours ago
Your boot partition seems be a healthy and normal 38%. It does not look like the problem to me. Next, show us the biggest disk space hogs on your filesystem.
– user535733
6 hours ago
Your boot partition seems be a healthy and normal 38%. It does not look like the problem to me. Next, show us the biggest disk space hogs on your filesystem.
– user535733
6 hours ago
I've edited the post above to reflect the new output. The logs are full, which to me says that it just continually wrote logs of something bad that was happening, and that this isn't the true problem.
– rchurch4
6 hours ago
I've edited the post above to reflect the new output. The logs are full, which to me says that it just continually wrote logs of something bad that was happening, and that this isn't the true problem.
– rchurch4
6 hours ago
How convenient: That's where I was leading you. Delete all the runaway log files except one to free space. Then read that one to learn the real problem. It really does not matter which one since it's probably the same problem over and over and over....
– user535733
6 hours ago
How convenient: That's where I was leading you. Delete all the runaway log files except one to free space. Then read that one to learn the real problem. It really does not matter which one since it's probably the same problem over and over and over....
– user535733
6 hours ago
|
show 2 more comments
0
active
oldest
votes
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%2f1108381%2ftwo-problems-in-one-failed-to-load-lvmetad-and-you-dont-have-enough-free-space%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1108381%2ftwo-problems-in-one-failed-to-load-lvmetad-and-you-dont-have-enough-free-space%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
gparteddoes not use any space on /boot, so you seem to be muddling you possible problems. Let's find out: Please edit your question to include the complete output ofdf.– user535733
Jan 9 at 19:19
sorry for the delay @user535733 I've only just gotten back to this problem.
– rchurch4
7 hours ago
Your boot partition seems be a healthy and normal 38%. It does not look like the problem to me. Next, show us the biggest disk space hogs on your filesystem.
– user535733
6 hours ago
I've edited the post above to reflect the new output. The logs are full, which to me says that it just continually wrote logs of something bad that was happening, and that this isn't the true problem.
– rchurch4
6 hours ago
How convenient: That's where I was leading you. Delete all the runaway log files except one to free space. Then read that one to learn the real problem. It really does not matter which one since it's probably the same problem over and over and over....
– user535733
6 hours ago