Unable to boot Arch Linux
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Stupidly, I was in the middle of running updates when my laptop ran out of power and upon trying to boot later that day, I was unable to. I got a kernel panic error and I thought I would just boot on a live USB, mount my system, chroot, and run "mkinitcpio -p linux" and be done with it. Maybe run a full system update for good measure. Unfortunately, this didn't solve the problem. Instead I get . I have never heard of nor created a new_root directory so that is confusing as well.
Puzzled, I get back onto my USB. I check my fstab but everything appears in order. I try dry running mkinitcpio with no tags and I get the error "'/lib/modules/4.13.8-2-ARCH' is not a valid kernel module directory". Why wouldn't this work, but mkinitcpio -p linux run without an error? I tried running "mkinitcpio -k 4.13.8-2-ARCH" and that completed. I looked inside the lib/modules directory and I saw that the directory in there was "4.12.13-1-ARCH".
So my question is why is mkinitcpio looking for different directories depending on what tags you use and what can I do to fix these issues.
arch-linux boot fstab mkinitcpio
add a comment |Â
up vote
0
down vote
favorite
Stupidly, I was in the middle of running updates when my laptop ran out of power and upon trying to boot later that day, I was unable to. I got a kernel panic error and I thought I would just boot on a live USB, mount my system, chroot, and run "mkinitcpio -p linux" and be done with it. Maybe run a full system update for good measure. Unfortunately, this didn't solve the problem. Instead I get . I have never heard of nor created a new_root directory so that is confusing as well.
Puzzled, I get back onto my USB. I check my fstab but everything appears in order. I try dry running mkinitcpio with no tags and I get the error "'/lib/modules/4.13.8-2-ARCH' is not a valid kernel module directory". Why wouldn't this work, but mkinitcpio -p linux run without an error? I tried running "mkinitcpio -k 4.13.8-2-ARCH" and that completed. I looked inside the lib/modules directory and I saw that the directory in there was "4.12.13-1-ARCH".
So my question is why is mkinitcpio looking for different directories depending on what tags you use and what can I do to fix these issues.
arch-linux boot fstab mkinitcpio
1
All the systemd missing libs errors give the hint that you might want to reinstall systemd which also will automatically triggermkinitcpio -p linux
. new_root is just an internal thingy used when the actual gets actually mounted while the initramfs root is still active. At worst, use a initramfs from another computer with archlinux (initramfs-linux.img
)
â cylgalad
Sep 25 '17 at 7:35
ldconfig
ended up being my friend. thanks for pointing me down the right path. I'm kind of a newbie and this is the first time I've really messed up my machine.
â Mike
Sep 27 '17 at 22:24
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Stupidly, I was in the middle of running updates when my laptop ran out of power and upon trying to boot later that day, I was unable to. I got a kernel panic error and I thought I would just boot on a live USB, mount my system, chroot, and run "mkinitcpio -p linux" and be done with it. Maybe run a full system update for good measure. Unfortunately, this didn't solve the problem. Instead I get . I have never heard of nor created a new_root directory so that is confusing as well.
Puzzled, I get back onto my USB. I check my fstab but everything appears in order. I try dry running mkinitcpio with no tags and I get the error "'/lib/modules/4.13.8-2-ARCH' is not a valid kernel module directory". Why wouldn't this work, but mkinitcpio -p linux run without an error? I tried running "mkinitcpio -k 4.13.8-2-ARCH" and that completed. I looked inside the lib/modules directory and I saw that the directory in there was "4.12.13-1-ARCH".
So my question is why is mkinitcpio looking for different directories depending on what tags you use and what can I do to fix these issues.
arch-linux boot fstab mkinitcpio
Stupidly, I was in the middle of running updates when my laptop ran out of power and upon trying to boot later that day, I was unable to. I got a kernel panic error and I thought I would just boot on a live USB, mount my system, chroot, and run "mkinitcpio -p linux" and be done with it. Maybe run a full system update for good measure. Unfortunately, this didn't solve the problem. Instead I get . I have never heard of nor created a new_root directory so that is confusing as well.
Puzzled, I get back onto my USB. I check my fstab but everything appears in order. I try dry running mkinitcpio with no tags and I get the error "'/lib/modules/4.13.8-2-ARCH' is not a valid kernel module directory". Why wouldn't this work, but mkinitcpio -p linux run without an error? I tried running "mkinitcpio -k 4.13.8-2-ARCH" and that completed. I looked inside the lib/modules directory and I saw that the directory in there was "4.12.13-1-ARCH".
So my question is why is mkinitcpio looking for different directories depending on what tags you use and what can I do to fix these issues.
arch-linux boot fstab mkinitcpio
arch-linux boot fstab mkinitcpio
asked Sep 25 '17 at 2:35
Mike
11
11
1
All the systemd missing libs errors give the hint that you might want to reinstall systemd which also will automatically triggermkinitcpio -p linux
. new_root is just an internal thingy used when the actual gets actually mounted while the initramfs root is still active. At worst, use a initramfs from another computer with archlinux (initramfs-linux.img
)
â cylgalad
Sep 25 '17 at 7:35
ldconfig
ended up being my friend. thanks for pointing me down the right path. I'm kind of a newbie and this is the first time I've really messed up my machine.
â Mike
Sep 27 '17 at 22:24
add a comment |Â
1
All the systemd missing libs errors give the hint that you might want to reinstall systemd which also will automatically triggermkinitcpio -p linux
. new_root is just an internal thingy used when the actual gets actually mounted while the initramfs root is still active. At worst, use a initramfs from another computer with archlinux (initramfs-linux.img
)
â cylgalad
Sep 25 '17 at 7:35
ldconfig
ended up being my friend. thanks for pointing me down the right path. I'm kind of a newbie and this is the first time I've really messed up my machine.
â Mike
Sep 27 '17 at 22:24
1
1
All the systemd missing libs errors give the hint that you might want to reinstall systemd which also will automatically trigger
mkinitcpio -p linux
. new_root is just an internal thingy used when the actual gets actually mounted while the initramfs root is still active. At worst, use a initramfs from another computer with archlinux (initramfs-linux.img
)â cylgalad
Sep 25 '17 at 7:35
All the systemd missing libs errors give the hint that you might want to reinstall systemd which also will automatically trigger
mkinitcpio -p linux
. new_root is just an internal thingy used when the actual gets actually mounted while the initramfs root is still active. At worst, use a initramfs from another computer with archlinux (initramfs-linux.img
)â cylgalad
Sep 25 '17 at 7:35
ldconfig
ended up being my friend. thanks for pointing me down the right path. I'm kind of a newbie and this is the first time I've really messed up my machine.â Mike
Sep 27 '17 at 22:24
ldconfig
ended up being my friend. thanks for pointing me down the right path. I'm kind of a newbie and this is the first time I've really messed up my machine.â Mike
Sep 27 '17 at 22:24
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f394231%2funable-to-boot-arch-linux%23new-answer', 'question_page');
);
Post as a guest
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
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
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
1
All the systemd missing libs errors give the hint that you might want to reinstall systemd which also will automatically trigger
mkinitcpio -p linux
. new_root is just an internal thingy used when the actual gets actually mounted while the initramfs root is still active. At worst, use a initramfs from another computer with archlinux (initramfs-linux.img
)â cylgalad
Sep 25 '17 at 7:35
ldconfig
ended up being my friend. thanks for pointing me down the right path. I'm kind of a newbie and this is the first time I've really messed up my machine.â Mike
Sep 27 '17 at 22:24