Debian 8 jessie: The root filesystem on /dev/sda1 requires a manual fsck
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
I was working in Atom on a small webpage and suddendly it would not let me save my file, saying that read-only mode was turned on. I tried to update in the terminal but that would not let me either, so I rebooted hoping that would fix the issue. Instead I ran into more problems.
The first error was in the BIOS: HP error 501
.
I pressed enter to continue and this screen popped up:
Loading, please wait...
/dev/sda1: recovering journal
/dev/sda1 contains a file system with errors, check forced.
/dev/sda1:
Deleted inode 1048599 has zero dtime. FIXED.
/dev/sda1: Inodes that were part of a corrupted orphan linked list found.
/dev/sda1: UNEXPECTED INCONSISTENCY:; RUN fsck MANUALLY
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda1 requires a manual fsck
modprobe: module ehci-orion not found in modules.dep
BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs) _
Now I am stuck on the (initramfs)
command prompt.
How can I get back to my system and files?
debian initramfs bios
 |Â
show 4 more comments
up vote
-1
down vote
favorite
I was working in Atom on a small webpage and suddendly it would not let me save my file, saying that read-only mode was turned on. I tried to update in the terminal but that would not let me either, so I rebooted hoping that would fix the issue. Instead I ran into more problems.
The first error was in the BIOS: HP error 501
.
I pressed enter to continue and this screen popped up:
Loading, please wait...
/dev/sda1: recovering journal
/dev/sda1 contains a file system with errors, check forced.
/dev/sda1:
Deleted inode 1048599 has zero dtime. FIXED.
/dev/sda1: Inodes that were part of a corrupted orphan linked list found.
/dev/sda1: UNEXPECTED INCONSISTENCY:; RUN fsck MANUALLY
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda1 requires a manual fsck
modprobe: module ehci-orion not found in modules.dep
BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs) _
Now I am stuck on the (initramfs)
command prompt.
How can I get back to my system and files?
debian initramfs bios
1
HP Error 501
appears to describe a corrupt or missing EFI system partition. Is this a new error? Have you been able to boot Linux without seeing this error before? If so, and judging from the output offsck
, you might have a failing hard drive. A quick search ofHP Error 501
seems to note that disablingHP Quicklook
in the BIOS tends to fix that error though, so that may not be the case
â Fox
Apr 30 '17 at 6:22
@Fox Yes this is the first time that this error popped up. So how would I reboot again to get into BIOS. Because I am stuck on the initramfs command and typing in reboot does nothing
â omegaD
Apr 30 '17 at 7:30
The(initramfs)
prompt is an actual shell prompt. Ifreboot
the command doesn't work, you might tryinit 6
. Failing that, Alt+SysRq+REISUB is a key sequence to reboot in Linux, which might work here
â Fox
Apr 30 '17 at 7:37
@Fox so init 6 came up with "must be run as PID 1." Do you think I should just put in the bootable DVD?
â omegaD
Apr 30 '17 at 20:21
As a last attempt before that, you might trytelinit 6
, which is whatinit 6
would actually call. Though at this point, it doesn't seem that anything is mounted, and holding the power button is probably as reasonable as anything
â Fox
Apr 30 '17 at 20:24
 |Â
show 4 more comments
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
I was working in Atom on a small webpage and suddendly it would not let me save my file, saying that read-only mode was turned on. I tried to update in the terminal but that would not let me either, so I rebooted hoping that would fix the issue. Instead I ran into more problems.
The first error was in the BIOS: HP error 501
.
I pressed enter to continue and this screen popped up:
Loading, please wait...
/dev/sda1: recovering journal
/dev/sda1 contains a file system with errors, check forced.
/dev/sda1:
Deleted inode 1048599 has zero dtime. FIXED.
/dev/sda1: Inodes that were part of a corrupted orphan linked list found.
/dev/sda1: UNEXPECTED INCONSISTENCY:; RUN fsck MANUALLY
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda1 requires a manual fsck
modprobe: module ehci-orion not found in modules.dep
BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs) _
Now I am stuck on the (initramfs)
command prompt.
How can I get back to my system and files?
debian initramfs bios
I was working in Atom on a small webpage and suddendly it would not let me save my file, saying that read-only mode was turned on. I tried to update in the terminal but that would not let me either, so I rebooted hoping that would fix the issue. Instead I ran into more problems.
The first error was in the BIOS: HP error 501
.
I pressed enter to continue and this screen popped up:
Loading, please wait...
/dev/sda1: recovering journal
/dev/sda1 contains a file system with errors, check forced.
/dev/sda1:
Deleted inode 1048599 has zero dtime. FIXED.
/dev/sda1: Inodes that were part of a corrupted orphan linked list found.
/dev/sda1: UNEXPECTED INCONSISTENCY:; RUN fsck MANUALLY
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda1 requires a manual fsck
modprobe: module ehci-orion not found in modules.dep
BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs) _
Now I am stuck on the (initramfs)
command prompt.
How can I get back to my system and files?
debian initramfs bios
debian initramfs bios
edited Jun 21 '17 at 11:39
sourcejedi
20.4k42888
20.4k42888
asked Apr 30 '17 at 3:07
omegaD
92
92
1
HP Error 501
appears to describe a corrupt or missing EFI system partition. Is this a new error? Have you been able to boot Linux without seeing this error before? If so, and judging from the output offsck
, you might have a failing hard drive. A quick search ofHP Error 501
seems to note that disablingHP Quicklook
in the BIOS tends to fix that error though, so that may not be the case
â Fox
Apr 30 '17 at 6:22
@Fox Yes this is the first time that this error popped up. So how would I reboot again to get into BIOS. Because I am stuck on the initramfs command and typing in reboot does nothing
â omegaD
Apr 30 '17 at 7:30
The(initramfs)
prompt is an actual shell prompt. Ifreboot
the command doesn't work, you might tryinit 6
. Failing that, Alt+SysRq+REISUB is a key sequence to reboot in Linux, which might work here
â Fox
Apr 30 '17 at 7:37
@Fox so init 6 came up with "must be run as PID 1." Do you think I should just put in the bootable DVD?
â omegaD
Apr 30 '17 at 20:21
As a last attempt before that, you might trytelinit 6
, which is whatinit 6
would actually call. Though at this point, it doesn't seem that anything is mounted, and holding the power button is probably as reasonable as anything
â Fox
Apr 30 '17 at 20:24
 |Â
show 4 more comments
1
HP Error 501
appears to describe a corrupt or missing EFI system partition. Is this a new error? Have you been able to boot Linux without seeing this error before? If so, and judging from the output offsck
, you might have a failing hard drive. A quick search ofHP Error 501
seems to note that disablingHP Quicklook
in the BIOS tends to fix that error though, so that may not be the case
â Fox
Apr 30 '17 at 6:22
@Fox Yes this is the first time that this error popped up. So how would I reboot again to get into BIOS. Because I am stuck on the initramfs command and typing in reboot does nothing
â omegaD
Apr 30 '17 at 7:30
The(initramfs)
prompt is an actual shell prompt. Ifreboot
the command doesn't work, you might tryinit 6
. Failing that, Alt+SysRq+REISUB is a key sequence to reboot in Linux, which might work here
â Fox
Apr 30 '17 at 7:37
@Fox so init 6 came up with "must be run as PID 1." Do you think I should just put in the bootable DVD?
â omegaD
Apr 30 '17 at 20:21
As a last attempt before that, you might trytelinit 6
, which is whatinit 6
would actually call. Though at this point, it doesn't seem that anything is mounted, and holding the power button is probably as reasonable as anything
â Fox
Apr 30 '17 at 20:24
1
1
HP Error 501
appears to describe a corrupt or missing EFI system partition. Is this a new error? Have you been able to boot Linux without seeing this error before? If so, and judging from the output of fsck
, you might have a failing hard drive. A quick search of HP Error 501
seems to note that disabling HP Quicklook
in the BIOS tends to fix that error though, so that may not be the caseâ Fox
Apr 30 '17 at 6:22
HP Error 501
appears to describe a corrupt or missing EFI system partition. Is this a new error? Have you been able to boot Linux without seeing this error before? If so, and judging from the output of fsck
, you might have a failing hard drive. A quick search of HP Error 501
seems to note that disabling HP Quicklook
in the BIOS tends to fix that error though, so that may not be the caseâ Fox
Apr 30 '17 at 6:22
@Fox Yes this is the first time that this error popped up. So how would I reboot again to get into BIOS. Because I am stuck on the initramfs command and typing in reboot does nothing
â omegaD
Apr 30 '17 at 7:30
@Fox Yes this is the first time that this error popped up. So how would I reboot again to get into BIOS. Because I am stuck on the initramfs command and typing in reboot does nothing
â omegaD
Apr 30 '17 at 7:30
The
(initramfs)
prompt is an actual shell prompt. If reboot
the command doesn't work, you might try init 6
. Failing that, Alt+SysRq+REISUB is a key sequence to reboot in Linux, which might work hereâ Fox
Apr 30 '17 at 7:37
The
(initramfs)
prompt is an actual shell prompt. If reboot
the command doesn't work, you might try init 6
. Failing that, Alt+SysRq+REISUB is a key sequence to reboot in Linux, which might work hereâ Fox
Apr 30 '17 at 7:37
@Fox so init 6 came up with "must be run as PID 1." Do you think I should just put in the bootable DVD?
â omegaD
Apr 30 '17 at 20:21
@Fox so init 6 came up with "must be run as PID 1." Do you think I should just put in the bootable DVD?
â omegaD
Apr 30 '17 at 20:21
As a last attempt before that, you might try
telinit 6
, which is what init 6
would actually call. Though at this point, it doesn't seem that anything is mounted, and holding the power button is probably as reasonable as anythingâ Fox
Apr 30 '17 at 20:24
As a last attempt before that, you might try
telinit 6
, which is what init 6
would actually call. Though at this point, it doesn't seem that anything is mounted, and holding the power button is probably as reasonable as anythingâ Fox
Apr 30 '17 at 20:24
 |Â
show 4 more comments
1 Answer
1
active
oldest
votes
up vote
2
down vote
Write fsck /dev/sdax
(depends on the drive infected "sda1,sda2 etc") And then enter Then it will ask you many questions for editing just type Yes and after that restart it.
Why was this answer downvoted? It looks quite correct for me. (The option -y does the same as typing Yes for every question, which I would not recommend.)
â user2233709
Oct 13 '17 at 8:18
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
Write fsck /dev/sdax
(depends on the drive infected "sda1,sda2 etc") And then enter Then it will ask you many questions for editing just type Yes and after that restart it.
Why was this answer downvoted? It looks quite correct for me. (The option -y does the same as typing Yes for every question, which I would not recommend.)
â user2233709
Oct 13 '17 at 8:18
add a comment |Â
up vote
2
down vote
Write fsck /dev/sdax
(depends on the drive infected "sda1,sda2 etc") And then enter Then it will ask you many questions for editing just type Yes and after that restart it.
Why was this answer downvoted? It looks quite correct for me. (The option -y does the same as typing Yes for every question, which I would not recommend.)
â user2233709
Oct 13 '17 at 8:18
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Write fsck /dev/sdax
(depends on the drive infected "sda1,sda2 etc") And then enter Then it will ask you many questions for editing just type Yes and after that restart it.
Write fsck /dev/sdax
(depends on the drive infected "sda1,sda2 etc") And then enter Then it will ask you many questions for editing just type Yes and after that restart it.
edited Jun 21 '17 at 11:23
Archemar
19.2k93467
19.2k93467
answered Jun 21 '17 at 8:51
Ibrahim
212
212
Why was this answer downvoted? It looks quite correct for me. (The option -y does the same as typing Yes for every question, which I would not recommend.)
â user2233709
Oct 13 '17 at 8:18
add a comment |Â
Why was this answer downvoted? It looks quite correct for me. (The option -y does the same as typing Yes for every question, which I would not recommend.)
â user2233709
Oct 13 '17 at 8:18
Why was this answer downvoted? It looks quite correct for me. (The option -y does the same as typing Yes for every question, which I would not recommend.)
â user2233709
Oct 13 '17 at 8:18
Why was this answer downvoted? It looks quite correct for me. (The option -y does the same as typing Yes for every question, which I would not recommend.)
â user2233709
Oct 13 '17 at 8:18
add a comment |Â
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%2f362204%2fdebian-8-jessie-the-root-filesystem-on-dev-sda1-requires-a-manual-fsck%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
HP Error 501
appears to describe a corrupt or missing EFI system partition. Is this a new error? Have you been able to boot Linux without seeing this error before? If so, and judging from the output offsck
, you might have a failing hard drive. A quick search ofHP Error 501
seems to note that disablingHP Quicklook
in the BIOS tends to fix that error though, so that may not be the caseâ Fox
Apr 30 '17 at 6:22
@Fox Yes this is the first time that this error popped up. So how would I reboot again to get into BIOS. Because I am stuck on the initramfs command and typing in reboot does nothing
â omegaD
Apr 30 '17 at 7:30
The
(initramfs)
prompt is an actual shell prompt. Ifreboot
the command doesn't work, you might tryinit 6
. Failing that, Alt+SysRq+REISUB is a key sequence to reboot in Linux, which might work hereâ Fox
Apr 30 '17 at 7:37
@Fox so init 6 came up with "must be run as PID 1." Do you think I should just put in the bootable DVD?
â omegaD
Apr 30 '17 at 20:21
As a last attempt before that, you might try
telinit 6
, which is whatinit 6
would actually call. Though at this point, it doesn't seem that anything is mounted, and holding the power button is probably as reasonable as anythingâ Fox
Apr 30 '17 at 20:24