Ubuntu 17.10 doesn't boot. Plymouth and intramfs prompt error [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
1
down vote
favorite
This question already has an answer here:
Boot drops to a (initramfs) prompts/busybox
5 answers
I recently installed some Plymouth themes by using this command:
sudo apt-get install plymouth-theme-*
Then I changed theme to ubuntu-budgie
using this command and selecting the theme:
sudo update-alternatives --config default.plymouth
And then I updated configuration using this command:
sudo update-initramfs -u
And finally I rebooted my system and what I see, it shows me the bootup screen, then automatically reboots the system and then takes me to some black screen prompt mentioned BusyBox and initramfs in it. What should I do now? I can't boot into my system.
boot 17.10 plymouth initramfs busybox
marked as duplicate by David Foerster, karel, WinEunuuchs2Unix, muru, Eric Carvalho Jan 28 at 12:29
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
1
down vote
favorite
This question already has an answer here:
Boot drops to a (initramfs) prompts/busybox
5 answers
I recently installed some Plymouth themes by using this command:
sudo apt-get install plymouth-theme-*
Then I changed theme to ubuntu-budgie
using this command and selecting the theme:
sudo update-alternatives --config default.plymouth
And then I updated configuration using this command:
sudo update-initramfs -u
And finally I rebooted my system and what I see, it shows me the bootup screen, then automatically reboots the system and then takes me to some black screen prompt mentioned BusyBox and initramfs in it. What should I do now? I can't boot into my system.
boot 17.10 plymouth initramfs busybox
marked as duplicate by David Foerster, karel, WinEunuuchs2Unix, muru, Eric Carvalho Jan 28 at 12:29
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
1
down vote
favorite
up vote
1
down vote
favorite
This question already has an answer here:
Boot drops to a (initramfs) prompts/busybox
5 answers
I recently installed some Plymouth themes by using this command:
sudo apt-get install plymouth-theme-*
Then I changed theme to ubuntu-budgie
using this command and selecting the theme:
sudo update-alternatives --config default.plymouth
And then I updated configuration using this command:
sudo update-initramfs -u
And finally I rebooted my system and what I see, it shows me the bootup screen, then automatically reboots the system and then takes me to some black screen prompt mentioned BusyBox and initramfs in it. What should I do now? I can't boot into my system.
boot 17.10 plymouth initramfs busybox
This question already has an answer here:
Boot drops to a (initramfs) prompts/busybox
5 answers
I recently installed some Plymouth themes by using this command:
sudo apt-get install plymouth-theme-*
Then I changed theme to ubuntu-budgie
using this command and selecting the theme:
sudo update-alternatives --config default.plymouth
And then I updated configuration using this command:
sudo update-initramfs -u
And finally I rebooted my system and what I see, it shows me the bootup screen, then automatically reboots the system and then takes me to some black screen prompt mentioned BusyBox and initramfs in it. What should I do now? I can't boot into my system.
This question already has an answer here:
Boot drops to a (initramfs) prompts/busybox
5 answers
boot 17.10 plymouth initramfs busybox
boot 17.10 plymouth initramfs busybox
asked Jan 27 at 16:11
user787956
marked as duplicate by David Foerster, karel, WinEunuuchs2Unix, muru, Eric Carvalho Jan 28 at 12:29
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 David Foerster, karel, WinEunuuchs2Unix, muru, Eric Carvalho Jan 28 at 12:29
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 |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
Seems that any partition got corrupted somehow. Probably this can solve your problem:
- There must be some message telling the name of the partition that got corrupted. If not, try executing
exit
command (when it shows you that screen again, may the message with corrupted partition appear). Execute this:
(initramfs) fsck <name-of-the-partition> -y
It'll start checking the partition and after the checking is done, reboot the system by executing
reboot
.
Done, most are the chances that system will now boot without any errors. Let me know this solves your problem or not.
Whoa. It really worked! Now I can boot into my system. Thanks.
â user787956
Jan 27 at 16:26
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
Seems that any partition got corrupted somehow. Probably this can solve your problem:
- There must be some message telling the name of the partition that got corrupted. If not, try executing
exit
command (when it shows you that screen again, may the message with corrupted partition appear). Execute this:
(initramfs) fsck <name-of-the-partition> -y
It'll start checking the partition and after the checking is done, reboot the system by executing
reboot
.
Done, most are the chances that system will now boot without any errors. Let me know this solves your problem or not.
Whoa. It really worked! Now I can boot into my system. Thanks.
â user787956
Jan 27 at 16:26
add a comment |Â
up vote
5
down vote
accepted
Seems that any partition got corrupted somehow. Probably this can solve your problem:
- There must be some message telling the name of the partition that got corrupted. If not, try executing
exit
command (when it shows you that screen again, may the message with corrupted partition appear). Execute this:
(initramfs) fsck <name-of-the-partition> -y
It'll start checking the partition and after the checking is done, reboot the system by executing
reboot
.
Done, most are the chances that system will now boot without any errors. Let me know this solves your problem or not.
Whoa. It really worked! Now I can boot into my system. Thanks.
â user787956
Jan 27 at 16:26
add a comment |Â
up vote
5
down vote
accepted
up vote
5
down vote
accepted
Seems that any partition got corrupted somehow. Probably this can solve your problem:
- There must be some message telling the name of the partition that got corrupted. If not, try executing
exit
command (when it shows you that screen again, may the message with corrupted partition appear). Execute this:
(initramfs) fsck <name-of-the-partition> -y
It'll start checking the partition and after the checking is done, reboot the system by executing
reboot
.
Done, most are the chances that system will now boot without any errors. Let me know this solves your problem or not.
Seems that any partition got corrupted somehow. Probably this can solve your problem:
- There must be some message telling the name of the partition that got corrupted. If not, try executing
exit
command (when it shows you that screen again, may the message with corrupted partition appear). Execute this:
(initramfs) fsck <name-of-the-partition> -y
It'll start checking the partition and after the checking is done, reboot the system by executing
reboot
.
Done, most are the chances that system will now boot without any errors. Let me know this solves your problem or not.
answered Jan 27 at 16:18
![](https://i.stack.imgur.com/ibOUJ.png?s=32&g=1)
![](https://i.stack.imgur.com/ibOUJ.png?s=32&g=1)
V. Ag.
394314
394314
Whoa. It really worked! Now I can boot into my system. Thanks.
â user787956
Jan 27 at 16:26
add a comment |Â
Whoa. It really worked! Now I can boot into my system. Thanks.
â user787956
Jan 27 at 16:26
Whoa. It really worked! Now I can boot into my system. Thanks.
â user787956
Jan 27 at 16:26
Whoa. It really worked! Now I can boot into my system. Thanks.
â user787956
Jan 27 at 16:26
add a comment |Â