What am I supposed to so with this, nothing I've tried has worked. [duplicate]
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
-2
down vote
favorite
This question already has an answer here:
How can I debug why Ubuntu boots to BusyBox? [duplicate]
3 answers
Busybox v1. 22. 1 (Ubuntu 1:1. 22. 0-19ubuntu2) built-in shell (ash) enter 'help' for a list of built-in commands.
boot initramfs busybox
marked as duplicate by RoVo, pomsky, Elder Geek, Fabby, Kevin Bowen May 26 at 20:18
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |Â
up vote
-2
down vote
favorite
This question already has an answer here:
How can I debug why Ubuntu boots to BusyBox? [duplicate]
3 answers
Busybox v1. 22. 1 (Ubuntu 1:1. 22. 0-19ubuntu2) built-in shell (ash) enter 'help' for a list of built-in commands.
boot initramfs busybox
marked as duplicate by RoVo, pomsky, Elder Geek, Fabby, Kevin Bowen May 26 at 20:18
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
2
What are you trying to do? What is your question?
â RoVo
May 24 at 13:45
add a comment |Â
up vote
-2
down vote
favorite
up vote
-2
down vote
favorite
This question already has an answer here:
How can I debug why Ubuntu boots to BusyBox? [duplicate]
3 answers
Busybox v1. 22. 1 (Ubuntu 1:1. 22. 0-19ubuntu2) built-in shell (ash) enter 'help' for a list of built-in commands.
boot initramfs busybox
This question already has an answer here:
How can I debug why Ubuntu boots to BusyBox? [duplicate]
3 answers
Busybox v1. 22. 1 (Ubuntu 1:1. 22. 0-19ubuntu2) built-in shell (ash) enter 'help' for a list of built-in commands.
This question already has an answer here:
How can I debug why Ubuntu boots to BusyBox? [duplicate]
3 answers
boot initramfs busybox
asked May 24 at 13:38
M. N
1
1
marked as duplicate by RoVo, pomsky, Elder Geek, Fabby, Kevin Bowen May 26 at 20:18
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by RoVo, pomsky, Elder Geek, Fabby, Kevin Bowen May 26 at 20:18
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
2
What are you trying to do? What is your question?
â RoVo
May 24 at 13:45
add a comment |Â
2
What are you trying to do? What is your question?
â RoVo
May 24 at 13:45
2
2
What are you trying to do? What is your question?
â RoVo
May 24 at 13:45
What are you trying to do? What is your question?
â RoVo
May 24 at 13:45
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
It should be showing you that the file system has uncleaned blocks. The message should be like this:
/dev/sda1 contains a file system with errors, check forced.
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`
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in-commands.
(initramfs)_
Anyways, you should first determine which partition you need to clean. In the above example, /dev/sda1
is the partition. According to the example, now you just need to run:
fsck /dev/sda1
Then press y
key when asked for confirmation. And after that just press Enter
when it asks for any more confirmation.
That's all. After it finishes cleaning the partition, type exit
. And within a few seconds, you will boot up normally.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
It should be showing you that the file system has uncleaned blocks. The message should be like this:
/dev/sda1 contains a file system with errors, check forced.
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`
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in-commands.
(initramfs)_
Anyways, you should first determine which partition you need to clean. In the above example, /dev/sda1
is the partition. According to the example, now you just need to run:
fsck /dev/sda1
Then press y
key when asked for confirmation. And after that just press Enter
when it asks for any more confirmation.
That's all. After it finishes cleaning the partition, type exit
. And within a few seconds, you will boot up normally.
add a comment |Â
up vote
1
down vote
It should be showing you that the file system has uncleaned blocks. The message should be like this:
/dev/sda1 contains a file system with errors, check forced.
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`
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in-commands.
(initramfs)_
Anyways, you should first determine which partition you need to clean. In the above example, /dev/sda1
is the partition. According to the example, now you just need to run:
fsck /dev/sda1
Then press y
key when asked for confirmation. And after that just press Enter
when it asks for any more confirmation.
That's all. After it finishes cleaning the partition, type exit
. And within a few seconds, you will boot up normally.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
It should be showing you that the file system has uncleaned blocks. The message should be like this:
/dev/sda1 contains a file system with errors, check forced.
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`
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in-commands.
(initramfs)_
Anyways, you should first determine which partition you need to clean. In the above example, /dev/sda1
is the partition. According to the example, now you just need to run:
fsck /dev/sda1
Then press y
key when asked for confirmation. And after that just press Enter
when it asks for any more confirmation.
That's all. After it finishes cleaning the partition, type exit
. And within a few seconds, you will boot up normally.
It should be showing you that the file system has uncleaned blocks. The message should be like this:
/dev/sda1 contains a file system with errors, check forced.
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`
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in-commands.
(initramfs)_
Anyways, you should first determine which partition you need to clean. In the above example, /dev/sda1
is the partition. According to the example, now you just need to run:
fsck /dev/sda1
Then press y
key when asked for confirmation. And after that just press Enter
when it asks for any more confirmation.
That's all. After it finishes cleaning the partition, type exit
. And within a few seconds, you will boot up normally.
answered May 24 at 13:52
pro neon
1164
1164
add a comment |Â
add a comment |Â
2
What are you trying to do? What is your question?
â RoVo
May 24 at 13:45