Ubuntu 17.10 doesn't boot. Plymouth and intramfs prompt error [duplicate]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








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.










share|improve this 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.


















    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.










    share|improve this 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.
















      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.










      share|improve this question














      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      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.






















          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:



          1. 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).


          2. Execute this:



            (initramfs) fsck <name-of-the-partition> -y


          3. 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.






          share|improve this answer




















          • Whoa. It really worked! Now I can boot into my system. Thanks.
            – user787956
            Jan 27 at 16:26
















          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:



          1. 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).


          2. Execute this:



            (initramfs) fsck <name-of-the-partition> -y


          3. 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.






          share|improve this answer




















          • Whoa. It really worked! Now I can boot into my system. Thanks.
            – user787956
            Jan 27 at 16:26














          up vote
          5
          down vote



          accepted










          Seems that any partition got corrupted somehow. Probably this can solve your problem:



          1. 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).


          2. Execute this:



            (initramfs) fsck <name-of-the-partition> -y


          3. 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.






          share|improve this answer




















          • Whoa. It really worked! Now I can boot into my system. Thanks.
            – user787956
            Jan 27 at 16:26












          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:



          1. 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).


          2. Execute this:



            (initramfs) fsck <name-of-the-partition> -y


          3. 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.






          share|improve this answer












          Seems that any partition got corrupted somehow. Probably this can solve your problem:



          1. 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).


          2. Execute this:



            (initramfs) fsck <name-of-the-partition> -y


          3. 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.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 27 at 16:18









          V. Ag.

          394314




          394314











          • 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




          Whoa. It really worked! Now I can boot into my system. Thanks.
          – user787956
          Jan 27 at 16:26


          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491