Upgrade to Bionic kills lvmetad
Tonight I upgraded to Bionic. The upgrade was fraught with problems, mainly due to a mixture of PAM and Postgresql where configuring postgresql asks for my PAM password and then ignores me completely forcing me to abort the upgrade mid configure.
My system appears to be mostly working now, but on boot I am told that lvmetad cannot be connected to and there follows a long delay while something is scanned. Disabling lvmetad removes the warning but not the delay.
Can anyone help? I see hints of other articles about this, but when I open the page in the search terms there is nothing useful there.
I see there was a bug reported in May about this which is now apparently fixed.
In my kernel log I see some lines like:
Sep 19 17:13:16 Shikamaru kernel: [ 1815.417699] lvm2-activation[22035]: segfault at d0 ip 00007fbc88f74856 sp 00007ffe47454da0 error 4 in liblvm2app.so.2.2[7fbc88f63000+101000]
I haven't seen these recently though and I am still getting the error.
Messing around following clues on the internet, I typed lvm lvs and got the following output that might give some more clues:
WARNING: Running as a non-root user. Functionality may be unavailable.
/run/lvm/lvmetad.socket: access failed: Permission denied
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.145 (2017-11-03) and kernel driver (unknown version).
However running it with sudo worked. Is it possible that the error during boot has a similar cause?
upgrade 18.04
edited Dec 8 at 20:02
kenorb
4,27913749
asked Sep 19 at 17:57
AlastairG
1115
|
show 4 more comments
Tonight I upgraded to Bionic. The upgrade was fraught with problems, mainly due to a mixture of PAM and Postgresql where configuring postgresql asks for my PAM password and then ignores me completely forcing me to abort the upgrade mid configure.
My system appears to be mostly working now, but on boot I am told that lvmetad cannot be connected to and there follows a long delay while something is scanned. Disabling lvmetad removes the warning but not the delay.
Can anyone help? I see hints of other articles about this, but when I open the page in the search terms there is nothing useful there.
I see there was a bug reported in May about this which is now apparently fixed.
In my kernel log I see some lines like:
Sep 19 17:13:16 Shikamaru kernel: [ 1815.417699] lvm2-activation[22035]: segfault at d0 ip 00007fbc88f74856 sp 00007ffe47454da0 error 4 in liblvm2app.so.2.2[7fbc88f63000+101000]
I haven't seen these recently though and I am still getting the error.
Messing around following clues on the internet, I typed lvm lvs and got the following output that might give some more clues:
WARNING: Running as a non-root user. Functionality may be unavailable.
/run/lvm/lvmetad.socket: access failed: Permission denied
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.145 (2017-11-03) and kernel driver (unknown version).
However running it with sudo worked. Is it possible that the error during boot has a similar cause?
upgrade 18.04
edited Dec 8 at 20:02
kenorb
4,27913749
asked Sep 19 at 17:57
AlastairG
1115
You could try reinstalling LVM? segfaults are nasty…
– Ken Sharp
Sep 20 at 7:05
How do I reinstall? Will the OS let me do apt remove, or is lvm2 a dependency and so I will be unable to remove it without first removing lots of other stuff?
– AlastairG
Sep 20 at 7:34
2
sudo apt install lvm2 --reinstallNothing should be removed.
– Ken Sharp
Sep 20 at 7:39
Didn't work. Thanks for the suggestion though. Any more?
– AlastairG
Sep 20 at 17:39
1
The only other thing I can think of is to run afsckon the drive. There is a bug report which appear to be the same issue: bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1767747 but as usual there's no solution.
– Ken Sharp
Sep 20 at 19:02
|
show 4 more comments
Tonight I upgraded to Bionic. The upgrade was fraught with problems, mainly due to a mixture of PAM and Postgresql where configuring postgresql asks for my PAM password and then ignores me completely forcing me to abort the upgrade mid configure.
My system appears to be mostly working now, but on boot I am told that lvmetad cannot be connected to and there follows a long delay while something is scanned. Disabling lvmetad removes the warning but not the delay.
Can anyone help? I see hints of other articles about this, but when I open the page in the search terms there is nothing useful there.
I see there was a bug reported in May about this which is now apparently fixed.
In my kernel log I see some lines like:
Sep 19 17:13:16 Shikamaru kernel: [ 1815.417699] lvm2-activation[22035]: segfault at d0 ip 00007fbc88f74856 sp 00007ffe47454da0 error 4 in liblvm2app.so.2.2[7fbc88f63000+101000]
I haven't seen these recently though and I am still getting the error.
Messing around following clues on the internet, I typed lvm lvs and got the following output that might give some more clues:
WARNING: Running as a non-root user. Functionality may be unavailable.
/run/lvm/lvmetad.socket: access failed: Permission denied
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.145 (2017-11-03) and kernel driver (unknown version).
However running it with sudo worked. Is it possible that the error during boot has a similar cause?
upgrade 18.04
edited Dec 8 at 20:02
kenorb
4,27913749
asked Sep 19 at 17:57
AlastairG
1115
Tonight I upgraded to Bionic. The upgrade was fraught with problems, mainly due to a mixture of PAM and Postgresql where configuring postgresql asks for my PAM password and then ignores me completely forcing me to abort the upgrade mid configure.
My system appears to be mostly working now, but on boot I am told that lvmetad cannot be connected to and there follows a long delay while something is scanned. Disabling lvmetad removes the warning but not the delay.
Can anyone help? I see hints of other articles about this, but when I open the page in the search terms there is nothing useful there.
I see there was a bug reported in May about this which is now apparently fixed.
In my kernel log I see some lines like:
Sep 19 17:13:16 Shikamaru kernel: [ 1815.417699] lvm2-activation[22035]: segfault at d0 ip 00007fbc88f74856 sp 00007ffe47454da0 error 4 in liblvm2app.so.2.2[7fbc88f63000+101000]
I haven't seen these recently though and I am still getting the error.
Messing around following clues on the internet, I typed lvm lvs and got the following output that might give some more clues:
WARNING: Running as a non-root user. Functionality may be unavailable.
/run/lvm/lvmetad.socket: access failed: Permission denied
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.145 (2017-11-03) and kernel driver (unknown version).
However running it with sudo worked. Is it possible that the error during boot has a similar cause?
upgrade 18.04
upgrade 18.04
edited Dec 8 at 20:02
kenorb
4,27913749
asked Sep 19 at 17:57
AlastairG
1115
edited Dec 8 at 20:02
kenorb
4,27913749
asked Sep 19 at 17:57
AlastairG
1115
edited Dec 8 at 20:02
kenorb
4,27913749
edited Dec 8 at 20:02
kenorb
4,27913749
edited Dec 8 at 20:02
kenorb
4,27913749
4,27913749
asked Sep 19 at 17:57
AlastairG
1115
asked Sep 19 at 17:57
AlastairG
1115
asked Sep 19 at 17:57
AlastairG
1115
1115
You could try reinstalling LVM? segfaults are nasty…
– Ken Sharp
Sep 20 at 7:05
How do I reinstall? Will the OS let me do apt remove, or is lvm2 a dependency and so I will be unable to remove it without first removing lots of other stuff?
– AlastairG
Sep 20 at 7:34
2
sudo apt install lvm2 --reinstallNothing should be removed.
– Ken Sharp
Sep 20 at 7:39
Didn't work. Thanks for the suggestion though. Any more?
– AlastairG
Sep 20 at 17:39
1
The only other thing I can think of is to run afsckon the drive. There is a bug report which appear to be the same issue: bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1767747 but as usual there's no solution.
– Ken Sharp
Sep 20 at 19:02
|
show 4 more comments
You could try reinstalling LVM? segfaults are nasty…
– Ken Sharp
Sep 20 at 7:05
How do I reinstall? Will the OS let me do apt remove, or is lvm2 a dependency and so I will be unable to remove it without first removing lots of other stuff?
– AlastairG
Sep 20 at 7:34
2
sudo apt install lvm2 --reinstallNothing should be removed.
– Ken Sharp
Sep 20 at 7:39
Didn't work. Thanks for the suggestion though. Any more?
– AlastairG
Sep 20 at 17:39
1
The only other thing I can think of is to run afsckon the drive. There is a bug report which appear to be the same issue: bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1767747 but as usual there's no solution.
– Ken Sharp
Sep 20 at 19:02
You could try reinstalling LVM? segfaults are nasty…
– Ken Sharp
Sep 20 at 7:05
You could try reinstalling LVM? segfaults are nasty…
– Ken Sharp
Sep 20 at 7:05
How do I reinstall? Will the OS let me do apt remove, or is lvm2 a dependency and so I will be unable to remove it without first removing lots of other stuff?
– AlastairG
Sep 20 at 7:34
How do I reinstall? Will the OS let me do apt remove, or is lvm2 a dependency and so I will be unable to remove it without first removing lots of other stuff?
– AlastairG
Sep 20 at 7:34
2
2
sudo apt install lvm2 --reinstall Nothing should be removed.– Ken Sharp
Sep 20 at 7:39
sudo apt install lvm2 --reinstall Nothing should be removed.– Ken Sharp
Sep 20 at 7:39
Didn't work. Thanks for the suggestion though. Any more?
– AlastairG
Sep 20 at 17:39
Didn't work. Thanks for the suggestion though. Any more?
– AlastairG
Sep 20 at 17:39
1
1
The only other thing I can think of is to run a
fsck on the drive. There is a bug report which appear to be the same issue: bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1767747 but as usual there's no solution.– Ken Sharp
Sep 20 at 19:02
The only other thing I can think of is to run a
fsck on the drive. There is a bug report which appear to be the same issue: bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1767747 but as usual there's no solution.– Ken Sharp
Sep 20 at 19:02
|
show 4 more comments
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%2f1076700%2fupgrade-to-bionic-kills-lvmetad%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
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.
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%2f1076700%2fupgrade-to-bionic-kills-lvmetad%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
You could try reinstalling LVM? segfaults are nasty…
– Ken Sharp
Sep 20 at 7:05
How do I reinstall? Will the OS let me do apt remove, or is lvm2 a dependency and so I will be unable to remove it without first removing lots of other stuff?
– AlastairG
Sep 20 at 7:34
2
sudo apt install lvm2 --reinstallNothing should be removed.– Ken Sharp
Sep 20 at 7:39
Didn't work. Thanks for the suggestion though. Any more?
– AlastairG
Sep 20 at 17:39
1
The only other thing I can think of is to run a
fsckon the drive. There is a bug report which appear to be the same issue: bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1767747 but as usual there's no solution.– Ken Sharp
Sep 20 at 19:02