ERROR: device '' not found. Skipping fsck (can't boot)
up vote
2
down vote
favorite
I have a Manjaro Linux installation and after a pacman - syu update (potentially updating the kernel) , and restarting my computer, I get the following error message after grub:
[ 4.896409] Initramfs unpacking
failed: read error
:: running early hook [udev]
:: running early hook [lvm2]
:: running hook [udev]
:: Triggering uevents...
:: running hook [plymouth]
:: Loading plymouth... done
:: running hook [plymouth-encrypt]
:: running hook [resume]
ERROR: resume: no device specified for hibernation
ERROR: device '' not found. Skipping fsck
:: mounting '' on real root
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ] #
At the shell, if I type, no letters are appearing on the screen, leading me to believe it is not registering keyboard input. Also note that my hard drive is encrypted. At grub, I have the option for Manjaro Linux kernel 4.9.34-1 x64 and 4.9.33-1-rt23 x64 (and respective fallback initramfs) which I have tried. If there is any more information that I can provide, I am willing to.
boot initramfs manjaro
edited Aug 27 '17 at 1:02
Jeff Schaller
38k1053123
asked Jul 9 '17 at 0:50
Paradox
2841320
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
up vote
2
down vote
favorite
I have a Manjaro Linux installation and after a pacman - syu update (potentially updating the kernel) , and restarting my computer, I get the following error message after grub:
[ 4.896409] Initramfs unpacking
failed: read error
:: running early hook [udev]
:: running early hook [lvm2]
:: running hook [udev]
:: Triggering uevents...
:: running hook [plymouth]
:: Loading plymouth... done
:: running hook [plymouth-encrypt]
:: running hook [resume]
ERROR: resume: no device specified for hibernation
ERROR: device '' not found. Skipping fsck
:: mounting '' on real root
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ] #
At the shell, if I type, no letters are appearing on the screen, leading me to believe it is not registering keyboard input. Also note that my hard drive is encrypted. At grub, I have the option for Manjaro Linux kernel 4.9.34-1 x64 and 4.9.33-1-rt23 x64 (and respective fallback initramfs) which I have tried. If there is any more information that I can provide, I am willing to.
boot initramfs manjaro
edited Aug 27 '17 at 1:02
Jeff Schaller
38k1053123
asked Jul 9 '17 at 0:50
Paradox
2841320
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I have a similar problem. Have you been enable to resolve this?
– k.stm
Jul 23 '17 at 12:23
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have a Manjaro Linux installation and after a pacman - syu update (potentially updating the kernel) , and restarting my computer, I get the following error message after grub:
[ 4.896409] Initramfs unpacking
failed: read error
:: running early hook [udev]
:: running early hook [lvm2]
:: running hook [udev]
:: Triggering uevents...
:: running hook [plymouth]
:: Loading plymouth... done
:: running hook [plymouth-encrypt]
:: running hook [resume]
ERROR: resume: no device specified for hibernation
ERROR: device '' not found. Skipping fsck
:: mounting '' on real root
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ] #
At the shell, if I type, no letters are appearing on the screen, leading me to believe it is not registering keyboard input. Also note that my hard drive is encrypted. At grub, I have the option for Manjaro Linux kernel 4.9.34-1 x64 and 4.9.33-1-rt23 x64 (and respective fallback initramfs) which I have tried. If there is any more information that I can provide, I am willing to.
boot initramfs manjaro
edited Aug 27 '17 at 1:02
Jeff Schaller
38k1053123
asked Jul 9 '17 at 0:50
Paradox
2841320
I have a Manjaro Linux installation and after a pacman - syu update (potentially updating the kernel) , and restarting my computer, I get the following error message after grub:
[ 4.896409] Initramfs unpacking
failed: read error
:: running early hook [udev]
:: running early hook [lvm2]
:: running hook [udev]
:: Triggering uevents...
:: running hook [plymouth]
:: Loading plymouth... done
:: running hook [plymouth-encrypt]
:: running hook [resume]
ERROR: resume: no device specified for hibernation
ERROR: device '' not found. Skipping fsck
:: mounting '' on real root
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ] #
At the shell, if I type, no letters are appearing on the screen, leading me to believe it is not registering keyboard input. Also note that my hard drive is encrypted. At grub, I have the option for Manjaro Linux kernel 4.9.34-1 x64 and 4.9.33-1-rt23 x64 (and respective fallback initramfs) which I have tried. If there is any more information that I can provide, I am willing to.
boot initramfs manjaro
boot initramfs manjaro
edited Aug 27 '17 at 1:02
Jeff Schaller
38k1053123
asked Jul 9 '17 at 0:50
Paradox
2841320
edited Aug 27 '17 at 1:02
Jeff Schaller
38k1053123
asked Jul 9 '17 at 0:50
Paradox
2841320
edited Aug 27 '17 at 1:02
Jeff Schaller
38k1053123
edited Aug 27 '17 at 1:02
Jeff Schaller
38k1053123
edited Aug 27 '17 at 1:02
Jeff Schaller
38k1053123
38k1053123
asked Jul 9 '17 at 0:50
Paradox
2841320
asked Jul 9 '17 at 0:50
Paradox
2841320
asked Jul 9 '17 at 0:50
Paradox
2841320
2841320
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ yesterday
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I have a similar problem. Have you been enable to resolve this?
– k.stm
Jul 23 '17 at 12:23
add a comment |
I have a similar problem. Have you been enable to resolve this?
– k.stm
Jul 23 '17 at 12:23
I have a similar problem. Have you been enable to resolve this?
– k.stm
Jul 23 '17 at 12:23
I have a similar problem. Have you been enable to resolve this?
– k.stm
Jul 23 '17 at 12:23
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I had a similar problem, when trying to bring up a new machine in Arch. My problem was that my initramfs was missing all modules, but you seem to have some, so it's not the identical problem, but I think the solution will be the same.
See your first error is there in the second line of your posted log:
failed: read error
See how it's failing to read your initramfs, so it looks like that got corrupted somehow, and it's given up reading it. You need to rebuild your initramfs.
I did that like this, after I'd booted to a rescue DVD, and mounted my system in /mnt and chrooted into that:
mkinitcpio -p linux
You're best off updating your grub.cfg at this point, I think (though I'm new to grub, so don't quote me on that). This, from the same environment should do that for you:
grub-mkconfig -o /boot/grub/grub.cfg
When I ran that I saw new messages about it finding my kernel and initramfs, so I think I'd managed to run it with an incorrectly populated /boot folder last time. You may not have that problem, but if you've no hand-crafted edits you want to keep, I'd regenerate it just out of habit.
Hope that helps!
answered Aug 24 '17 at 1:56
levi
13
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%2f377260%2ferror-device-not-found-skipping-fsck-cant-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I had a similar problem, when trying to bring up a new machine in Arch. My problem was that my initramfs was missing all modules, but you seem to have some, so it's not the identical problem, but I think the solution will be the same.
See your first error is there in the second line of your posted log:
failed: read error
See how it's failing to read your initramfs, so it looks like that got corrupted somehow, and it's given up reading it. You need to rebuild your initramfs.
I did that like this, after I'd booted to a rescue DVD, and mounted my system in /mnt and chrooted into that:
mkinitcpio -p linux
You're best off updating your grub.cfg at this point, I think (though I'm new to grub, so don't quote me on that). This, from the same environment should do that for you:
grub-mkconfig -o /boot/grub/grub.cfg
When I ran that I saw new messages about it finding my kernel and initramfs, so I think I'd managed to run it with an incorrectly populated /boot folder last time. You may not have that problem, but if you've no hand-crafted edits you want to keep, I'd regenerate it just out of habit.
Hope that helps!
answered Aug 24 '17 at 1:56
levi
13
add a comment |
up vote
0
down vote
I had a similar problem, when trying to bring up a new machine in Arch. My problem was that my initramfs was missing all modules, but you seem to have some, so it's not the identical problem, but I think the solution will be the same.
See your first error is there in the second line of your posted log:
failed: read error
See how it's failing to read your initramfs, so it looks like that got corrupted somehow, and it's given up reading it. You need to rebuild your initramfs.
I did that like this, after I'd booted to a rescue DVD, and mounted my system in /mnt and chrooted into that:
mkinitcpio -p linux
You're best off updating your grub.cfg at this point, I think (though I'm new to grub, so don't quote me on that). This, from the same environment should do that for you:
grub-mkconfig -o /boot/grub/grub.cfg
When I ran that I saw new messages about it finding my kernel and initramfs, so I think I'd managed to run it with an incorrectly populated /boot folder last time. You may not have that problem, but if you've no hand-crafted edits you want to keep, I'd regenerate it just out of habit.
Hope that helps!
answered Aug 24 '17 at 1:56
levi
13
add a comment |
up vote
0
down vote
up vote
0
down vote
I had a similar problem, when trying to bring up a new machine in Arch. My problem was that my initramfs was missing all modules, but you seem to have some, so it's not the identical problem, but I think the solution will be the same.
See your first error is there in the second line of your posted log:
failed: read error
See how it's failing to read your initramfs, so it looks like that got corrupted somehow, and it's given up reading it. You need to rebuild your initramfs.
I did that like this, after I'd booted to a rescue DVD, and mounted my system in /mnt and chrooted into that:
mkinitcpio -p linux
You're best off updating your grub.cfg at this point, I think (though I'm new to grub, so don't quote me on that). This, from the same environment should do that for you:
grub-mkconfig -o /boot/grub/grub.cfg
When I ran that I saw new messages about it finding my kernel and initramfs, so I think I'd managed to run it with an incorrectly populated /boot folder last time. You may not have that problem, but if you've no hand-crafted edits you want to keep, I'd regenerate it just out of habit.
Hope that helps!
answered Aug 24 '17 at 1:56
levi
13
I had a similar problem, when trying to bring up a new machine in Arch. My problem was that my initramfs was missing all modules, but you seem to have some, so it's not the identical problem, but I think the solution will be the same.
See your first error is there in the second line of your posted log:
failed: read error
See how it's failing to read your initramfs, so it looks like that got corrupted somehow, and it's given up reading it. You need to rebuild your initramfs.
I did that like this, after I'd booted to a rescue DVD, and mounted my system in /mnt and chrooted into that:
mkinitcpio -p linux
You're best off updating your grub.cfg at this point, I think (though I'm new to grub, so don't quote me on that). This, from the same environment should do that for you:
grub-mkconfig -o /boot/grub/grub.cfg
When I ran that I saw new messages about it finding my kernel and initramfs, so I think I'd managed to run it with an incorrectly populated /boot folder last time. You may not have that problem, but if you've no hand-crafted edits you want to keep, I'd regenerate it just out of habit.
Hope that helps!
answered Aug 24 '17 at 1:56
levi
13
answered Aug 24 '17 at 1:56
levi
13
answered Aug 24 '17 at 1:56
levi
13
answered Aug 24 '17 at 1:56
levi
13
13
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%2f377260%2ferror-device-not-found-skipping-fsck-cant-boot%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
I have a similar problem. Have you been enable to resolve this?
– k.stm
Jul 23 '17 at 12:23