Failed to connect to lvmetad

up vote
6
down vote

favorite

After upgrading to ubuntu 16.10 I get this warning in my boot.log file

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

Volume group "ubuntu-vg" not found

Cannot process volume group ubuntu-vg

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

Reading all physical volumes.  This may take a while...

Found volume group "ubuntu-vg" using metadata type lvm2

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

2 logical volume(s) in volume group "ubuntu-vg" now active /dev/mapper/ubuntu--vg-root: clean, 1180656/30154752 files, 16007858/120604672 blocks

Seems to be an issue that is related to disk encryption. The system startup properly and I do not see any bad behaviour, however do anybody have an idea how to fix

asked Oct 14 '16 at 18:26

hako

3113

add a comment |

up vote
6
down vote

favorite

After upgrading to ubuntu 16.10 I get this warning in my boot.log file

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

Volume group "ubuntu-vg" not found

Cannot process volume group ubuntu-vg

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

Reading all physical volumes.  This may take a while...

Found volume group "ubuntu-vg" using metadata type lvm2

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

2 logical volume(s) in volume group "ubuntu-vg" now active /dev/mapper/ubuntu--vg-root: clean, 1180656/30154752 files, 16007858/120604672 blocks

Seems to be an issue that is related to disk encryption. The system startup properly and I do not see any bad behaviour, however do anybody have an idea how to fix

asked Oct 14 '16 at 18:26

hako

3113

add a comment |

up vote
6
down vote

favorite

After upgrading to ubuntu 16.10 I get this warning in my boot.log file

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

Volume group "ubuntu-vg" not found

Cannot process volume group ubuntu-vg

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

Reading all physical volumes.  This may take a while...

Found volume group "ubuntu-vg" using metadata type lvm2

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

2 logical volume(s) in volume group "ubuntu-vg" now active /dev/mapper/ubuntu--vg-root: clean, 1180656/30154752 files, 16007858/120604672 blocks

Seems to be an issue that is related to disk encryption. The system startup properly and I do not see any bad behaviour, however do anybody have an idea how to fix

asked Oct 14 '16 at 18:26

hako

3113

After upgrading to ubuntu 16.10 I get this warning in my boot.log file

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

Volume group "ubuntu-vg" not found

Cannot process volume group ubuntu-vg

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

Reading all physical volumes.  This may take a while...

Found volume group "ubuntu-vg" using metadata type lvm2

WARNING: Failed to connect to lvmetad. Falling back to device scanning.

2 logical volume(s) in volume group "ubuntu-vg" now active /dev/mapper/ubuntu--vg-root: clean, 1180656/30154752 files, 16007858/120604672 blocks

Seems to be an issue that is related to disk encryption. The system startup properly and I do not see any bad behaviour, however do anybody have an idea how to fix

16.10

asked Oct 14 '16 at 18:26

hako

3113

asked Oct 14 '16 at 18:26

hako

3113

asked Oct 14 '16 at 18:26

hako

3113

asked Oct 14 '16 at 18:26

hako

3113

asked Oct 14 '16 at 18:26

hako

3113

add a comment |

1 Answer
1

active

oldest

votes

up vote
3
down vote

I get the same warning on Ubuntu 16.10 with encrypted LVM. I have not found a solution but, for what it's worth, it appears related to the Debian bug reported on 16 Nov 2016.

My server works fine so I'm hoping it's a minor bug that will be fixed in upcoming Ubuntu releases.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844487

Dear Maintainer,

I am using Debian Scratch with encrypted root partition. The last
kernel version where it worked was 4.6.0. For kernels 4.7.0 and 4.8.0
it prints on the boot repeatedly and forever following messages:

WARNING: Failed to connect to lvmetad. Falling back to device

scanning. Volume group "martin-vg" not found Cannot process volume
group martin-vg

In 4.6.0 these messages are shown too, but only twice and then it
prompts for a password:

Please unlock disk sda5_crypt:

answered Feb 6 '17 at 1:49

iangetz

1313

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',
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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f837143%2ffailed-to-connect-to-lvmetad%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
3
down vote

I get the same warning on Ubuntu 16.10 with encrypted LVM. I have not found a solution but, for what it's worth, it appears related to the Debian bug reported on 16 Nov 2016.

My server works fine so I'm hoping it's a minor bug that will be fixed in upcoming Ubuntu releases.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844487

Dear Maintainer,

I am using Debian Scratch with encrypted root partition. The last
kernel version where it worked was 4.6.0. For kernels 4.7.0 and 4.8.0
it prints on the boot repeatedly and forever following messages:

WARNING: Failed to connect to lvmetad. Falling back to device

scanning. Volume group "martin-vg" not found Cannot process volume
group martin-vg

In 4.6.0 these messages are shown too, but only twice and then it
prompts for a password:

Please unlock disk sda5_crypt:

answered Feb 6 '17 at 1:49

iangetz

1313

add a comment |

up vote
3
down vote

I get the same warning on Ubuntu 16.10 with encrypted LVM. I have not found a solution but, for what it's worth, it appears related to the Debian bug reported on 16 Nov 2016.

My server works fine so I'm hoping it's a minor bug that will be fixed in upcoming Ubuntu releases.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844487

Dear Maintainer,

I am using Debian Scratch with encrypted root partition. The last
kernel version where it worked was 4.6.0. For kernels 4.7.0 and 4.8.0
it prints on the boot repeatedly and forever following messages:

WARNING: Failed to connect to lvmetad. Falling back to device

scanning. Volume group "martin-vg" not found Cannot process volume
group martin-vg

In 4.6.0 these messages are shown too, but only twice and then it
prompts for a password:

Please unlock disk sda5_crypt:

answered Feb 6 '17 at 1:49

iangetz

1313

add a comment |

up vote
3
down vote

I get the same warning on Ubuntu 16.10 with encrypted LVM. I have not found a solution but, for what it's worth, it appears related to the Debian bug reported on 16 Nov 2016.

My server works fine so I'm hoping it's a minor bug that will be fixed in upcoming Ubuntu releases.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844487

Dear Maintainer,

I am using Debian Scratch with encrypted root partition. The last
kernel version where it worked was 4.6.0. For kernels 4.7.0 and 4.8.0
it prints on the boot repeatedly and forever following messages:

WARNING: Failed to connect to lvmetad. Falling back to device

scanning. Volume group "martin-vg" not found Cannot process volume
group martin-vg

In 4.6.0 these messages are shown too, but only twice and then it
prompts for a password:

Please unlock disk sda5_crypt:

answered Feb 6 '17 at 1:49

iangetz

1313

I get the same warning on Ubuntu 16.10 with encrypted LVM. I have not found a solution but, for what it's worth, it appears related to the Debian bug reported on 16 Nov 2016.

My server works fine so I'm hoping it's a minor bug that will be fixed in upcoming Ubuntu releases.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844487

Dear Maintainer,

I am using Debian Scratch with encrypted root partition. The last
kernel version where it worked was 4.6.0. For kernels 4.7.0 and 4.8.0
it prints on the boot repeatedly and forever following messages:

WARNING: Failed to connect to lvmetad. Falling back to device

scanning. Volume group "martin-vg" not found Cannot process volume
group martin-vg

In 4.6.0 these messages are shown too, but only twice and then it
prompts for a password:

Please unlock disk sda5_crypt:

answered Feb 6 '17 at 1:49

iangetz

1313

answered Feb 6 '17 at 1:49

iangetz

1313

answered Feb 6 '17 at 1:49

iangetz

1313

answered Feb 6 '17 at 1:49

iangetz

1313

add a comment |

draft saved

draft discarded

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Krdytkyu