volume group problem for booting
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I've installed Ubuntu 18.04 newly into ASUS model 502V notebook where window 10 resided originally with an option of encryption and LVM with DVD ROM. After normal operation thereafter, I got the following display message once had tried to boot the system.
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, 188107/7675904 files, 3234687/30682112 blocks
It's my knowledge that CMOS has USB option for booting.
Previously it appeared there so that I managed to set the priority properly.
However this time I can't get the usb option after tried to reboot or plugging in external DVD ROM or USB. There displays only the residing ubuntu(P0: ..... ) in any case. It doesn't return to reboot function. How to get in to have new boot option in CMOS environment? It doesn't matter either to use existing P0 or new boot?
Thanks in advance.
boot lvm
edited Mar 22 at 15:45
Jeff
812719
asked Mar 22 at 13:11
서형석서형석
1
add a comment |
I've installed Ubuntu 18.04 newly into ASUS model 502V notebook where window 10 resided originally with an option of encryption and LVM with DVD ROM. After normal operation thereafter, I got the following display message once had tried to boot the system.
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, 188107/7675904 files, 3234687/30682112 blocks
It's my knowledge that CMOS has USB option for booting.
Previously it appeared there so that I managed to set the priority properly.
However this time I can't get the usb option after tried to reboot or plugging in external DVD ROM or USB. There displays only the residing ubuntu(P0: ..... ) in any case. It doesn't return to reboot function. How to get in to have new boot option in CMOS environment? It doesn't matter either to use existing P0 or new boot?
Thanks in advance.
boot lvm
edited Mar 22 at 15:45
Jeff
812719
asked Mar 22 at 13:11
서형석서형석
1
Do you know or not know what you are doing when it comes encryption? I gotta admit first time I ever switched to linux I saw that : cim.mcgill.ca/~anqixu/blog/wp-content/uploads/2018/06/… and I though, "damn that looks sexy let's try it out!", ten years later, as a more experienced ubuntu user, I wouldn't for the life of me be able to come up with a good reason to use this for a computer that's going to be personal (only used by one person) and also won't be used for transfering military data. honestly I could be a fugitive cybercriminal and I still wouldn't
– tatsu
Mar 22 at 13:23
basically : is redoing the installation not an option?
– tatsu
Mar 22 at 13:25
For security reason I chose the encryption following a guide. I've looked through google search. There most of the cases seemed to be possible to reboot. But I can't.
– 서형석
Mar 22 at 14:09
well windows is what's messing with thing here, it introduces a whole lot of unknowns, you have know if windows is in Legacy/UEFI mode and same for our ubuntu, you have to first disable fast boot in the bios and in windows, inside an admin powershell typepowercfg -h off. try this then try installing again. what's likely happening is that windows is messing with your ability to write to the drive when it's not booted. And encryption boot, fragile as it is, needs everything to be perfect.
– tatsu
Mar 22 at 15:15
It needed patience, finally solved the issue. Thanks.
– 서형석
Mar 24 at 7:24
add a comment |
I've installed Ubuntu 18.04 newly into ASUS model 502V notebook where window 10 resided originally with an option of encryption and LVM with DVD ROM. After normal operation thereafter, I got the following display message once had tried to boot the system.
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, 188107/7675904 files, 3234687/30682112 blocks
It's my knowledge that CMOS has USB option for booting.
Previously it appeared there so that I managed to set the priority properly.
However this time I can't get the usb option after tried to reboot or plugging in external DVD ROM or USB. There displays only the residing ubuntu(P0: ..... ) in any case. It doesn't return to reboot function. How to get in to have new boot option in CMOS environment? It doesn't matter either to use existing P0 or new boot?
Thanks in advance.
boot lvm
edited Mar 22 at 15:45
Jeff
812719
asked Mar 22 at 13:11
서형석서형석
1
I've installed Ubuntu 18.04 newly into ASUS model 502V notebook where window 10 resided originally with an option of encryption and LVM with DVD ROM. After normal operation thereafter, I got the following display message once had tried to boot the system.
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, 188107/7675904 files, 3234687/30682112 blocks
It's my knowledge that CMOS has USB option for booting.
Previously it appeared there so that I managed to set the priority properly.
However this time I can't get the usb option after tried to reboot or plugging in external DVD ROM or USB. There displays only the residing ubuntu(P0: ..... ) in any case. It doesn't return to reboot function. How to get in to have new boot option in CMOS environment? It doesn't matter either to use existing P0 or new boot?
Thanks in advance.
boot lvm
boot lvm
edited Mar 22 at 15:45
Jeff
812719
asked Mar 22 at 13:11
서형석서형석
1
edited Mar 22 at 15:45
Jeff
812719
asked Mar 22 at 13:11
서형석서형석
1
edited Mar 22 at 15:45
Jeff
812719
edited Mar 22 at 15:45
Jeff
812719
edited Mar 22 at 15:45
Jeff
812719
812719
asked Mar 22 at 13:11
서형석서형석
1
asked Mar 22 at 13:11
서형석서형석
1
asked Mar 22 at 13:11
서형석서형석
1
1
Do you know or not know what you are doing when it comes encryption? I gotta admit first time I ever switched to linux I saw that : cim.mcgill.ca/~anqixu/blog/wp-content/uploads/2018/06/… and I though, "damn that looks sexy let's try it out!", ten years later, as a more experienced ubuntu user, I wouldn't for the life of me be able to come up with a good reason to use this for a computer that's going to be personal (only used by one person) and also won't be used for transfering military data. honestly I could be a fugitive cybercriminal and I still wouldn't
– tatsu
Mar 22 at 13:23
basically : is redoing the installation not an option?
– tatsu
Mar 22 at 13:25
For security reason I chose the encryption following a guide. I've looked through google search. There most of the cases seemed to be possible to reboot. But I can't.
– 서형석
Mar 22 at 14:09
well windows is what's messing with thing here, it introduces a whole lot of unknowns, you have know if windows is in Legacy/UEFI mode and same for our ubuntu, you have to first disable fast boot in the bios and in windows, inside an admin powershell typepowercfg -h off. try this then try installing again. what's likely happening is that windows is messing with your ability to write to the drive when it's not booted. And encryption boot, fragile as it is, needs everything to be perfect.
– tatsu
Mar 22 at 15:15
It needed patience, finally solved the issue. Thanks.
– 서형석
Mar 24 at 7:24
add a comment |
Do you know or not know what you are doing when it comes encryption? I gotta admit first time I ever switched to linux I saw that : cim.mcgill.ca/~anqixu/blog/wp-content/uploads/2018/06/… and I though, "damn that looks sexy let's try it out!", ten years later, as a more experienced ubuntu user, I wouldn't for the life of me be able to come up with a good reason to use this for a computer that's going to be personal (only used by one person) and also won't be used for transfering military data. honestly I could be a fugitive cybercriminal and I still wouldn't
– tatsu
Mar 22 at 13:23
basically : is redoing the installation not an option?
– tatsu
Mar 22 at 13:25
For security reason I chose the encryption following a guide. I've looked through google search. There most of the cases seemed to be possible to reboot. But I can't.
– 서형석
Mar 22 at 14:09
well windows is what's messing with thing here, it introduces a whole lot of unknowns, you have know if windows is in Legacy/UEFI mode and same for our ubuntu, you have to first disable fast boot in the bios and in windows, inside an admin powershell typepowercfg -h off. try this then try installing again. what's likely happening is that windows is messing with your ability to write to the drive when it's not booted. And encryption boot, fragile as it is, needs everything to be perfect.
– tatsu
Mar 22 at 15:15
It needed patience, finally solved the issue. Thanks.
– 서형석
Mar 24 at 7:24
Do you know or not know what you are doing when it comes encryption? I gotta admit first time I ever switched to linux I saw that : cim.mcgill.ca/~anqixu/blog/wp-content/uploads/2018/06/… and I though, "damn that looks sexy let's try it out!", ten years later, as a more experienced ubuntu user, I wouldn't for the life of me be able to come up with a good reason to use this for a computer that's going to be personal (only used by one person) and also won't be used for transfering military data. honestly I could be a fugitive cybercriminal and I still wouldn't
– tatsu
Mar 22 at 13:23
Do you know or not know what you are doing when it comes encryption? I gotta admit first time I ever switched to linux I saw that : cim.mcgill.ca/~anqixu/blog/wp-content/uploads/2018/06/… and I though, "damn that looks sexy let's try it out!", ten years later, as a more experienced ubuntu user, I wouldn't for the life of me be able to come up with a good reason to use this for a computer that's going to be personal (only used by one person) and also won't be used for transfering military data. honestly I could be a fugitive cybercriminal and I still wouldn't
– tatsu
Mar 22 at 13:23
basically : is redoing the installation not an option?
– tatsu
Mar 22 at 13:25
basically : is redoing the installation not an option?
– tatsu
Mar 22 at 13:25
For security reason I chose the encryption following a guide. I've looked through google search. There most of the cases seemed to be possible to reboot. But I can't.
– 서형석
Mar 22 at 14:09
For security reason I chose the encryption following a guide. I've looked through google search. There most of the cases seemed to be possible to reboot. But I can't.
– 서형석
Mar 22 at 14:09
well windows is what's messing with thing here, it introduces a whole lot of unknowns, you have know if windows is in Legacy/UEFI mode and same for our ubuntu, you have to first disable fast boot in the bios and in windows, inside an admin powershell type
powercfg -h off. try this then try installing again. what's likely happening is that windows is messing with your ability to write to the drive when it's not booted. And encryption boot, fragile as it is, needs everything to be perfect.– tatsu
Mar 22 at 15:15
well windows is what's messing with thing here, it introduces a whole lot of unknowns, you have know if windows is in Legacy/UEFI mode and same for our ubuntu, you have to first disable fast boot in the bios and in windows, inside an admin powershell type
powercfg -h off. try this then try installing again. what's likely happening is that windows is messing with your ability to write to the drive when it's not booted. And encryption boot, fragile as it is, needs everything to be perfect.– tatsu
Mar 22 at 15:15
It needed patience, finally solved the issue. Thanks.
– 서형석
Mar 24 at 7:24
It needed patience, finally solved the issue. Thanks.
– 서형석
Mar 24 at 7:24
add a comment |
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%2f1127829%2fvolume-group-problem-for-booting%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%2f1127829%2fvolume-group-problem-for-booting%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
Do you know or not know what you are doing when it comes encryption? I gotta admit first time I ever switched to linux I saw that : cim.mcgill.ca/~anqixu/blog/wp-content/uploads/2018/06/… and I though, "damn that looks sexy let's try it out!", ten years later, as a more experienced ubuntu user, I wouldn't for the life of me be able to come up with a good reason to use this for a computer that's going to be personal (only used by one person) and also won't be used for transfering military data. honestly I could be a fugitive cybercriminal and I still wouldn't
– tatsu
Mar 22 at 13:23
basically : is redoing the installation not an option?
– tatsu
Mar 22 at 13:25
For security reason I chose the encryption following a guide. I've looked through google search. There most of the cases seemed to be possible to reboot. But I can't.
– 서형석
Mar 22 at 14:09
well windows is what's messing with thing here, it introduces a whole lot of unknowns, you have know if windows is in Legacy/UEFI mode and same for our ubuntu, you have to first disable fast boot in the bios and in windows, inside an admin powershell type
powercfg -h off. try this then try installing again. what's likely happening is that windows is messing with your ability to write to the drive when it's not booted. And encryption boot, fragile as it is, needs everything to be perfect.– tatsu
Mar 22 at 15:15
It needed patience, finally solved the issue. Thanks.
– 서형석
Mar 24 at 7:24