initramfs - ERROR: device '/dev/mapper/vg0-root' not found, Skipping fsck
up vote
0
down vote
favorite
Upon booting my Dell XPS 15 9560 running Arch, I am being dropped into an emergency shell because my devices aren't being found
starting version 239
A password is required to access the luks volume:
mount: /new_root: special device /dev/mapper/vg0-root does not exist.
ERROR: device '/dev/mapper/vg0-root' not found, Skipping fsck.
mount: /new_root: special device /dev/mapper/vg0-root does not exist.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#
Output of lvm pvs
[rootfs ]# lvm pvs
WARNING: Not using lvmetad bacause config setting use_lvmetad=0
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache)
PV VG Fmt Attr PSize PFree
/dev/mapper/luks vg0 lvm2 a-- <237.74g 0
Output of lvm lvs
[rootfs ]# lvm lvs
WARNING: Not using lvmetad bacause config setting use_lvmetad=0
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache)
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root vg0 -wi------- <221.74g
swap vg0 -wi------- 16.00g
That output is really confusing because it shows that vg0-root and vg0-swap both exist, but they just don't appear under dev, including after doing a cryptsetup luksOpen /dev/nvme0n1p3 luks
My guess would be that I'm missing a hook with my mkinitcpio.conf, but this is my mkinitcpio.conf
HOOKS=(base udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck)
Which I don't believe is any different from 5 days ago, the last time it booted just fine. I did run a pacman -Syu earlier today, but I'm not sure how I would find out what exactly broke here.
mkinitcpio -p linux works without errors when chrooted into the drive from a arch usb
edit:
added root=/dev/mapper/luks to my GRUB_CMDLINE_LINUX, and now get the error mount: /new_root: unknown filesystem type LVM2_member'
lvm vgchange -ay vg0
mount /dev/mapper/vg0-root /new_root
exit
Allowed me to boot into my system, but this should be happening automatically with the lvm2 hook and upon restarting, I have to do it again.
arch-linux initramfs mkinitcpio
asked Oct 1 at 3:13
Sly Cedix
414
add a comment |
up vote
0
down vote
favorite
Upon booting my Dell XPS 15 9560 running Arch, I am being dropped into an emergency shell because my devices aren't being found
starting version 239
A password is required to access the luks volume:
mount: /new_root: special device /dev/mapper/vg0-root does not exist.
ERROR: device '/dev/mapper/vg0-root' not found, Skipping fsck.
mount: /new_root: special device /dev/mapper/vg0-root does not exist.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#
Output of lvm pvs
[rootfs ]# lvm pvs
WARNING: Not using lvmetad bacause config setting use_lvmetad=0
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache)
PV VG Fmt Attr PSize PFree
/dev/mapper/luks vg0 lvm2 a-- <237.74g 0
Output of lvm lvs
[rootfs ]# lvm lvs
WARNING: Not using lvmetad bacause config setting use_lvmetad=0
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache)
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root vg0 -wi------- <221.74g
swap vg0 -wi------- 16.00g
That output is really confusing because it shows that vg0-root and vg0-swap both exist, but they just don't appear under dev, including after doing a cryptsetup luksOpen /dev/nvme0n1p3 luks
My guess would be that I'm missing a hook with my mkinitcpio.conf, but this is my mkinitcpio.conf
HOOKS=(base udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck)
Which I don't believe is any different from 5 days ago, the last time it booted just fine. I did run a pacman -Syu earlier today, but I'm not sure how I would find out what exactly broke here.
mkinitcpio -p linux works without errors when chrooted into the drive from a arch usb
edit:
added root=/dev/mapper/luks to my GRUB_CMDLINE_LINUX, and now get the error mount: /new_root: unknown filesystem type LVM2_member'
lvm vgchange -ay vg0
mount /dev/mapper/vg0-root /new_root
exit
Allowed me to boot into my system, but this should be happening automatically with the lvm2 hook and upon restarting, I have to do it again.
arch-linux initramfs mkinitcpio
asked Oct 1 at 3:13
Sly Cedix
414
From the chroot, read your pacman.log for the update. Also, check the output ofpacman -Q linux && uname -r.
– jasonwryan
Oct 1 at 4:57
I was on 14.18.10, downgraded to 14.18.5 to check if it was a kernel issue, but the issue remains after downgrading to the last kernel it worked on. I have found a bandaid fix that I've added to the bottom of the OP if that gives any insight into what the issue is.
– Sly Cedix
Oct 1 at 5:21
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Upon booting my Dell XPS 15 9560 running Arch, I am being dropped into an emergency shell because my devices aren't being found
starting version 239
A password is required to access the luks volume:
mount: /new_root: special device /dev/mapper/vg0-root does not exist.
ERROR: device '/dev/mapper/vg0-root' not found, Skipping fsck.
mount: /new_root: special device /dev/mapper/vg0-root does not exist.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#
Output of lvm pvs
[rootfs ]# lvm pvs
WARNING: Not using lvmetad bacause config setting use_lvmetad=0
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache)
PV VG Fmt Attr PSize PFree
/dev/mapper/luks vg0 lvm2 a-- <237.74g 0
Output of lvm lvs
[rootfs ]# lvm lvs
WARNING: Not using lvmetad bacause config setting use_lvmetad=0
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache)
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root vg0 -wi------- <221.74g
swap vg0 -wi------- 16.00g
That output is really confusing because it shows that vg0-root and vg0-swap both exist, but they just don't appear under dev, including after doing a cryptsetup luksOpen /dev/nvme0n1p3 luks
My guess would be that I'm missing a hook with my mkinitcpio.conf, but this is my mkinitcpio.conf
HOOKS=(base udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck)
Which I don't believe is any different from 5 days ago, the last time it booted just fine. I did run a pacman -Syu earlier today, but I'm not sure how I would find out what exactly broke here.
mkinitcpio -p linux works without errors when chrooted into the drive from a arch usb
edit:
added root=/dev/mapper/luks to my GRUB_CMDLINE_LINUX, and now get the error mount: /new_root: unknown filesystem type LVM2_member'
lvm vgchange -ay vg0
mount /dev/mapper/vg0-root /new_root
exit
Allowed me to boot into my system, but this should be happening automatically with the lvm2 hook and upon restarting, I have to do it again.
arch-linux initramfs mkinitcpio
asked Oct 1 at 3:13
Sly Cedix
414
Upon booting my Dell XPS 15 9560 running Arch, I am being dropped into an emergency shell because my devices aren't being found
starting version 239
A password is required to access the luks volume:
mount: /new_root: special device /dev/mapper/vg0-root does not exist.
ERROR: device '/dev/mapper/vg0-root' not found, Skipping fsck.
mount: /new_root: special device /dev/mapper/vg0-root does not exist.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#
Output of lvm pvs
[rootfs ]# lvm pvs
WARNING: Not using lvmetad bacause config setting use_lvmetad=0
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache)
PV VG Fmt Attr PSize PFree
/dev/mapper/luks vg0 lvm2 a-- <237.74g 0
Output of lvm lvs
[rootfs ]# lvm lvs
WARNING: Not using lvmetad bacause config setting use_lvmetad=0
WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache)
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root vg0 -wi------- <221.74g
swap vg0 -wi------- 16.00g
That output is really confusing because it shows that vg0-root and vg0-swap both exist, but they just don't appear under dev, including after doing a cryptsetup luksOpen /dev/nvme0n1p3 luks
My guess would be that I'm missing a hook with my mkinitcpio.conf, but this is my mkinitcpio.conf
HOOKS=(base udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck)
Which I don't believe is any different from 5 days ago, the last time it booted just fine. I did run a pacman -Syu earlier today, but I'm not sure how I would find out what exactly broke here.
mkinitcpio -p linux works without errors when chrooted into the drive from a arch usb
edit:
added root=/dev/mapper/luks to my GRUB_CMDLINE_LINUX, and now get the error mount: /new_root: unknown filesystem type LVM2_member'
lvm vgchange -ay vg0
mount /dev/mapper/vg0-root /new_root
exit
Allowed me to boot into my system, but this should be happening automatically with the lvm2 hook and upon restarting, I have to do it again.
arch-linux initramfs mkinitcpio
arch-linux initramfs mkinitcpio
asked Oct 1 at 3:13
Sly Cedix
414
asked Oct 1 at 3:13
Sly Cedix
414
edited Oct 1 at 5:20
asked Oct 1 at 3:13
Sly Cedix
414
asked Oct 1 at 3:13
Sly Cedix
414
asked Oct 1 at 3:13
Sly Cedix
414
414
From the chroot, read your pacman.log for the update. Also, check the output ofpacman -Q linux && uname -r.
– jasonwryan
Oct 1 at 4:57
I was on 14.18.10, downgraded to 14.18.5 to check if it was a kernel issue, but the issue remains after downgrading to the last kernel it worked on. I have found a bandaid fix that I've added to the bottom of the OP if that gives any insight into what the issue is.
– Sly Cedix
Oct 1 at 5:21
add a comment |
From the chroot, read your pacman.log for the update. Also, check the output ofpacman -Q linux && uname -r.
– jasonwryan
Oct 1 at 4:57
I was on 14.18.10, downgraded to 14.18.5 to check if it was a kernel issue, but the issue remains after downgrading to the last kernel it worked on. I have found a bandaid fix that I've added to the bottom of the OP if that gives any insight into what the issue is.
– Sly Cedix
Oct 1 at 5:21
From the chroot, read your pacman.log for the update. Also, check the output of
pacman -Q linux && uname -r.– jasonwryan
Oct 1 at 4:57
From the chroot, read your pacman.log for the update. Also, check the output of
pacman -Q linux && uname -r.– jasonwryan
Oct 1 at 4:57
I was on 14.18.10, downgraded to 14.18.5 to check if it was a kernel issue, but the issue remains after downgrading to the last kernel it worked on. I have found a bandaid fix that I've added to the bottom of the OP if that gives any insight into what the issue is.
– Sly Cedix
Oct 1 at 5:21
I was on 14.18.10, downgraded to 14.18.5 to check if it was a kernel issue, but the issue remains after downgrading to the last kernel it worked on. I have found a bandaid fix that I've added to the bottom of the OP if that gives any insight into what the issue is.
– Sly Cedix
Oct 1 at 5:21
add a comment |
2 Answers
2
active
oldest
votes
up vote
2
down vote
accepted
What I did to fix this
Switched to systemd initramfs by changing all busybox hooks to their systemd equivalents, and changed the grub DEFAULT_CMDLINE_LINUX to reflect the syntax of sd-encrypt and sd-lvm2.
I then reset my lvm.conf
sudo rm /etc/lvm/lvm.conf && sudo pacman -S lvm2
answered Oct 2 at 18:31
Sly Cedix
414
add a comment |
up vote
0
down vote
I had a similar issue, the logical volumes were showing as inactive while doing lvscan.
The only change I did before in the /etc/lvm/lvm.conf was to disable use_lvmetad.
To recover from this scenario I have ran:
rm /etc/lvm/lvm.conf && pacman -S lvm2
but I think it is worth trying to re-enable use_lvmetad and regenerate ram disk:
So:
- make sure the
use_lvmetad=1in/etc/lvm/lvm.conf
if you are changing the option to
use_lvmetad=1, regenerate ramdisk:
mkinitcpio -p linux
edited yesterday
JigglyNaga
3,648829
answered yesterday
wlodi
1
New contributor
wlodi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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',
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%2f472489%2finitramfs-error-device-dev-mapper-vg0-root-not-found-skipping-fsck%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
What I did to fix this
Switched to systemd initramfs by changing all busybox hooks to their systemd equivalents, and changed the grub DEFAULT_CMDLINE_LINUX to reflect the syntax of sd-encrypt and sd-lvm2.
I then reset my lvm.conf
sudo rm /etc/lvm/lvm.conf && sudo pacman -S lvm2
answered Oct 2 at 18:31
Sly Cedix
414
add a comment |
up vote
2
down vote
accepted
What I did to fix this
Switched to systemd initramfs by changing all busybox hooks to their systemd equivalents, and changed the grub DEFAULT_CMDLINE_LINUX to reflect the syntax of sd-encrypt and sd-lvm2.
I then reset my lvm.conf
sudo rm /etc/lvm/lvm.conf && sudo pacman -S lvm2
answered Oct 2 at 18:31
Sly Cedix
414
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
What I did to fix this
Switched to systemd initramfs by changing all busybox hooks to their systemd equivalents, and changed the grub DEFAULT_CMDLINE_LINUX to reflect the syntax of sd-encrypt and sd-lvm2.
I then reset my lvm.conf
sudo rm /etc/lvm/lvm.conf && sudo pacman -S lvm2
answered Oct 2 at 18:31
Sly Cedix
414
What I did to fix this
Switched to systemd initramfs by changing all busybox hooks to their systemd equivalents, and changed the grub DEFAULT_CMDLINE_LINUX to reflect the syntax of sd-encrypt and sd-lvm2.
I then reset my lvm.conf
sudo rm /etc/lvm/lvm.conf && sudo pacman -S lvm2
answered Oct 2 at 18:31
Sly Cedix
414
answered Oct 2 at 18:31
Sly Cedix
414
answered Oct 2 at 18:31
Sly Cedix
414
answered Oct 2 at 18:31
Sly Cedix
414
414
add a comment |
add a comment |
up vote
0
down vote
I had a similar issue, the logical volumes were showing as inactive while doing lvscan.
The only change I did before in the /etc/lvm/lvm.conf was to disable use_lvmetad.
To recover from this scenario I have ran:
rm /etc/lvm/lvm.conf && pacman -S lvm2
but I think it is worth trying to re-enable use_lvmetad and regenerate ram disk:
So:
- make sure the
use_lvmetad=1in/etc/lvm/lvm.conf
if you are changing the option to
use_lvmetad=1, regenerate ramdisk:
mkinitcpio -p linux
edited yesterday
JigglyNaga
3,648829
answered yesterday
wlodi
1
New contributor
wlodi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
I had a similar issue, the logical volumes were showing as inactive while doing lvscan.
The only change I did before in the /etc/lvm/lvm.conf was to disable use_lvmetad.
To recover from this scenario I have ran:
rm /etc/lvm/lvm.conf && pacman -S lvm2
but I think it is worth trying to re-enable use_lvmetad and regenerate ram disk:
So:
- make sure the
use_lvmetad=1in/etc/lvm/lvm.conf
if you are changing the option to
use_lvmetad=1, regenerate ramdisk:
mkinitcpio -p linux
edited yesterday
JigglyNaga
3,648829
answered yesterday
wlodi
1
New contributor
wlodi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
I had a similar issue, the logical volumes were showing as inactive while doing lvscan.
The only change I did before in the /etc/lvm/lvm.conf was to disable use_lvmetad.
To recover from this scenario I have ran:
rm /etc/lvm/lvm.conf && pacman -S lvm2
but I think it is worth trying to re-enable use_lvmetad and regenerate ram disk:
So:
- make sure the
use_lvmetad=1in/etc/lvm/lvm.conf
if you are changing the option to
use_lvmetad=1, regenerate ramdisk:
mkinitcpio -p linux
edited yesterday
JigglyNaga
3,648829
answered yesterday
wlodi
1
New contributor
wlodi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I had a similar issue, the logical volumes were showing as inactive while doing lvscan.
The only change I did before in the /etc/lvm/lvm.conf was to disable use_lvmetad.
To recover from this scenario I have ran:
rm /etc/lvm/lvm.conf && pacman -S lvm2
but I think it is worth trying to re-enable use_lvmetad and regenerate ram disk:
So:
- make sure the
use_lvmetad=1in/etc/lvm/lvm.conf
if you are changing the option to
use_lvmetad=1, regenerate ramdisk:
mkinitcpio -p linux
edited yesterday
JigglyNaga
3,648829
answered yesterday
wlodi
1
New contributor
wlodi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
JigglyNaga
3,648829
edited yesterday
JigglyNaga
3,648829
edited yesterday
JigglyNaga
3,648829
3,648829
answered yesterday
wlodi
1
New contributor
wlodi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered yesterday
wlodi
1
answered yesterday
wlodi
1
1
New contributor
wlodi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
wlodi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
wlodi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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.
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%2funix.stackexchange.com%2fquestions%2f472489%2finitramfs-error-device-dev-mapper-vg0-root-not-found-skipping-fsck%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
From the chroot, read your pacman.log for the update. Also, check the output of
pacman -Q linux && uname -r.– jasonwryan
Oct 1 at 4:57
I was on 14.18.10, downgraded to 14.18.5 to check if it was a kernel issue, but the issue remains after downgrading to the last kernel it worked on. I have found a bandaid fix that I've added to the bottom of the OP if that gives any insight into what the issue is.
– Sly Cedix
Oct 1 at 5:21