Arch Linux Installation Grub Problem
Clash Royale CLAN TAG#URR8PPP
I'm installing arch Linux and I typed in the command
grub-mkconfig -o /boot/grub/grub.cfg
And it responded with
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
What do I do?
arch-linux
edited Dec 24 '16 at 16:21
steve
14k22452
asked Dec 24 '16 at 16:13
KeiraKeira
41113
add a comment |
I'm installing arch Linux and I typed in the command
grub-mkconfig -o /boot/grub/grub.cfg
And it responded with
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
What do I do?
arch-linux
edited Dec 24 '16 at 16:21
steve
14k22452
asked Dec 24 '16 at 16:13
KeiraKeira
41113
1
Edit your/etc/lvm/lvm.confand setuse_lvmetad = 0
– GAD3R
Dec 24 '16 at 17:27
I get that message from my Gentoo Linux when it boots. And I'm quite certain it's because at that point in the boot process lvmetad has not started yet. Perhaps in your case /boot is on an lvm volume. Did you check /boot/grub/grub.cfg to see if it looks sane? Note that if / is on an lvm volume you need to make sure your kernel can boot from lvm.
– Emmanuel Rosa
Dec 24 '16 at 18:35
add a comment |
I'm installing arch Linux and I typed in the command
grub-mkconfig -o /boot/grub/grub.cfg
And it responded with
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
What do I do?
arch-linux
edited Dec 24 '16 at 16:21
steve
14k22452
asked Dec 24 '16 at 16:13
KeiraKeira
41113
I'm installing arch Linux and I typed in the command
grub-mkconfig -o /boot/grub/grub.cfg
And it responded with
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
What do I do?
arch-linux
arch-linux
edited Dec 24 '16 at 16:21
steve
14k22452
asked Dec 24 '16 at 16:13
KeiraKeira
41113
edited Dec 24 '16 at 16:21
steve
14k22452
asked Dec 24 '16 at 16:13
KeiraKeira
41113
edited Dec 24 '16 at 16:21
steve
14k22452
edited Dec 24 '16 at 16:21
steve
14k22452
edited Dec 24 '16 at 16:21
steve
14k22452
14k22452
asked Dec 24 '16 at 16:13
KeiraKeira
41113
asked Dec 24 '16 at 16:13
KeiraKeira
41113
asked Dec 24 '16 at 16:13
KeiraKeira
41113
41113
1
Edit your/etc/lvm/lvm.confand setuse_lvmetad = 0
– GAD3R
Dec 24 '16 at 17:27
I get that message from my Gentoo Linux when it boots. And I'm quite certain it's because at that point in the boot process lvmetad has not started yet. Perhaps in your case /boot is on an lvm volume. Did you check /boot/grub/grub.cfg to see if it looks sane? Note that if / is on an lvm volume you need to make sure your kernel can boot from lvm.
– Emmanuel Rosa
Dec 24 '16 at 18:35
add a comment |
1
Edit your/etc/lvm/lvm.confand setuse_lvmetad = 0
– GAD3R
Dec 24 '16 at 17:27
I get that message from my Gentoo Linux when it boots. And I'm quite certain it's because at that point in the boot process lvmetad has not started yet. Perhaps in your case /boot is on an lvm volume. Did you check /boot/grub/grub.cfg to see if it looks sane? Note that if / is on an lvm volume you need to make sure your kernel can boot from lvm.
– Emmanuel Rosa
Dec 24 '16 at 18:35
1
1
Edit your
/etc/lvm/lvm.conf and set use_lvmetad = 0– GAD3R
Dec 24 '16 at 17:27
Edit your
/etc/lvm/lvm.conf and set use_lvmetad = 0– GAD3R
Dec 24 '16 at 17:27
I get that message from my Gentoo Linux when it boots. And I'm quite certain it's because at that point in the boot process lvmetad has not started yet. Perhaps in your case /boot is on an lvm volume. Did you check /boot/grub/grub.cfg to see if it looks sane? Note that if / is on an lvm volume you need to make sure your kernel can boot from lvm.
– Emmanuel Rosa
Dec 24 '16 at 18:35
I get that message from my Gentoo Linux when it boots. And I'm quite certain it's because at that point in the boot process lvmetad has not started yet. Perhaps in your case /boot is on an lvm volume. Did you check /boot/grub/grub.cfg to see if it looks sane? Note that if / is on an lvm volume you need to make sure your kernel can boot from lvm.
– Emmanuel Rosa
Dec 24 '16 at 18:35
add a comment |
3 Answers
3
active
oldest
votes
This worried me as well. From some digging about on the GRUB Arch Wiki page:
Warning when installing in chroot
When installing GRUB on a LVM system in a chroot environment (e.g. during system installation), you may receive warnings like
/run/lvm/lvmetad.socket: connect failed: No such file or directory
or
WARNING: failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
This is because /run is not available inside the chroot. These warnings will not prevent the system from booting, provided that everything has been done correctly, so you may continue with the installation.
So looks like there's no need to worry.
answered Jan 20 '18 at 13:04
HoundsonHoundson
10115
add a comment |
It doesn't matter, you can ignore it.
It just because lvmetad is not running when you boot your arch from live cd.
answered Dec 24 '16 at 16:50
BarathrumBarathrum
528
add a comment |
Uninstall os-prober
That made it work for me
answered Feb 3 at 22:29
bace1000bace1000
1011
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f332556%2farch-linux-installation-grub-problem%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
This worried me as well. From some digging about on the GRUB Arch Wiki page:
Warning when installing in chroot
When installing GRUB on a LVM system in a chroot environment (e.g. during system installation), you may receive warnings like
/run/lvm/lvmetad.socket: connect failed: No such file or directory
or
WARNING: failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
This is because /run is not available inside the chroot. These warnings will not prevent the system from booting, provided that everything has been done correctly, so you may continue with the installation.
So looks like there's no need to worry.
answered Jan 20 '18 at 13:04
HoundsonHoundson
10115
add a comment |
This worried me as well. From some digging about on the GRUB Arch Wiki page:
Warning when installing in chroot
When installing GRUB on a LVM system in a chroot environment (e.g. during system installation), you may receive warnings like
/run/lvm/lvmetad.socket: connect failed: No such file or directory
or
WARNING: failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
This is because /run is not available inside the chroot. These warnings will not prevent the system from booting, provided that everything has been done correctly, so you may continue with the installation.
So looks like there's no need to worry.
answered Jan 20 '18 at 13:04
HoundsonHoundson
10115
add a comment |
This worried me as well. From some digging about on the GRUB Arch Wiki page:
Warning when installing in chroot
When installing GRUB on a LVM system in a chroot environment (e.g. during system installation), you may receive warnings like
/run/lvm/lvmetad.socket: connect failed: No such file or directory
or
WARNING: failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
This is because /run is not available inside the chroot. These warnings will not prevent the system from booting, provided that everything has been done correctly, so you may continue with the installation.
So looks like there's no need to worry.
answered Jan 20 '18 at 13:04
HoundsonHoundson
10115
This worried me as well. From some digging about on the GRUB Arch Wiki page:
Warning when installing in chroot
When installing GRUB on a LVM system in a chroot environment (e.g. during system installation), you may receive warnings like
/run/lvm/lvmetad.socket: connect failed: No such file or directory
or
WARNING: failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
This is because /run is not available inside the chroot. These warnings will not prevent the system from booting, provided that everything has been done correctly, so you may continue with the installation.
So looks like there's no need to worry.
answered Jan 20 '18 at 13:04
HoundsonHoundson
10115
answered Jan 20 '18 at 13:04
HoundsonHoundson
10115
answered Jan 20 '18 at 13:04
HoundsonHoundson
10115
answered Jan 20 '18 at 13:04
HoundsonHoundson
10115
10115
add a comment |
add a comment |
It doesn't matter, you can ignore it.
It just because lvmetad is not running when you boot your arch from live cd.
answered Dec 24 '16 at 16:50
BarathrumBarathrum
528
add a comment |
It doesn't matter, you can ignore it.
It just because lvmetad is not running when you boot your arch from live cd.
answered Dec 24 '16 at 16:50
BarathrumBarathrum
528
add a comment |
It doesn't matter, you can ignore it.
It just because lvmetad is not running when you boot your arch from live cd.
answered Dec 24 '16 at 16:50
BarathrumBarathrum
528
It doesn't matter, you can ignore it.
It just because lvmetad is not running when you boot your arch from live cd.
answered Dec 24 '16 at 16:50
BarathrumBarathrum
528
edited Dec 24 '16 at 17:17
answered Dec 24 '16 at 16:50
BarathrumBarathrum
528
answered Dec 24 '16 at 16:50
BarathrumBarathrum
528
answered Dec 24 '16 at 16:50
BarathrumBarathrum
528
528
add a comment |
add a comment |
Uninstall os-prober
That made it work for me
answered Feb 3 at 22:29
bace1000bace1000
1011
add a comment |
Uninstall os-prober
That made it work for me
answered Feb 3 at 22:29
bace1000bace1000
1011
add a comment |
Uninstall os-prober
That made it work for me
answered Feb 3 at 22:29
bace1000bace1000
1011
Uninstall os-prober
That made it work for me
answered Feb 3 at 22:29
bace1000bace1000
1011
answered Feb 3 at 22:29
bace1000bace1000
1011
answered Feb 3 at 22:29
bace1000bace1000
1011
answered Feb 3 at 22:29
bace1000bace1000
1011
1011
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f332556%2farch-linux-installation-grub-problem%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
1
Edit your
/etc/lvm/lvm.confand setuse_lvmetad = 0– GAD3R
Dec 24 '16 at 17:27
I get that message from my Gentoo Linux when it boots. And I'm quite certain it's because at that point in the boot process lvmetad has not started yet. Perhaps in your case /boot is on an lvm volume. Did you check /boot/grub/grub.cfg to see if it looks sane? Note that if / is on an lvm volume you need to make sure your kernel can boot from lvm.
– Emmanuel Rosa
Dec 24 '16 at 18:35