Ubuntu 18.04 LTS only boots with Recovery Mode with Linux 4.7.2 After Upgrade

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











up vote
0
down vote

favorite












Upon performing an upgrade from Ubuntu 17 to Ubuntu 18.04 LTS, my PC was in standby mode, thereby interrupting the last 1/4 portion of the upgrade. When trying to boot in Grub loader: "Advanced Options"; "Linux 4.7.2", the machine loads the drive and asks for password. Then the screen just goes blank. If I boot into 4.7.2 recovery mode, I am able to access Ubuntu 18.04 and login.



Grub configuration is at i8042.reset nomodeset. Previously it was set to quiet splash. Neither has solved the boot issue.



What can I do to solve the interrupted upgrade process (to where the upgrade did not successfully complete during running in Ubuntu 17), and to where I can boot into Ubuntu without recovery mode?



lsb_release -a `


outputs: `



LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic



uname -a


outputs:
4.7.2-040702-generic #201608201334 SMP Sat Aug 20 17:37:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux



Is there anything I can do to where Ubuntu 18.04 can boot normally? Without having to choose Recovery Mode? How can I correct this issue?







share|improve this question























    up vote
    0
    down vote

    favorite












    Upon performing an upgrade from Ubuntu 17 to Ubuntu 18.04 LTS, my PC was in standby mode, thereby interrupting the last 1/4 portion of the upgrade. When trying to boot in Grub loader: "Advanced Options"; "Linux 4.7.2", the machine loads the drive and asks for password. Then the screen just goes blank. If I boot into 4.7.2 recovery mode, I am able to access Ubuntu 18.04 and login.



    Grub configuration is at i8042.reset nomodeset. Previously it was set to quiet splash. Neither has solved the boot issue.



    What can I do to solve the interrupted upgrade process (to where the upgrade did not successfully complete during running in Ubuntu 17), and to where I can boot into Ubuntu without recovery mode?



    lsb_release -a `


    outputs: `



    LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic



    uname -a


    outputs:
    4.7.2-040702-generic #201608201334 SMP Sat Aug 20 17:37:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux



    Is there anything I can do to where Ubuntu 18.04 can boot normally? Without having to choose Recovery Mode? How can I correct this issue?







    share|improve this question





















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Upon performing an upgrade from Ubuntu 17 to Ubuntu 18.04 LTS, my PC was in standby mode, thereby interrupting the last 1/4 portion of the upgrade. When trying to boot in Grub loader: "Advanced Options"; "Linux 4.7.2", the machine loads the drive and asks for password. Then the screen just goes blank. If I boot into 4.7.2 recovery mode, I am able to access Ubuntu 18.04 and login.



      Grub configuration is at i8042.reset nomodeset. Previously it was set to quiet splash. Neither has solved the boot issue.



      What can I do to solve the interrupted upgrade process (to where the upgrade did not successfully complete during running in Ubuntu 17), and to where I can boot into Ubuntu without recovery mode?



      lsb_release -a `


      outputs: `



      LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic



      uname -a


      outputs:
      4.7.2-040702-generic #201608201334 SMP Sat Aug 20 17:37:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux



      Is there anything I can do to where Ubuntu 18.04 can boot normally? Without having to choose Recovery Mode? How can I correct this issue?







      share|improve this question











      Upon performing an upgrade from Ubuntu 17 to Ubuntu 18.04 LTS, my PC was in standby mode, thereby interrupting the last 1/4 portion of the upgrade. When trying to boot in Grub loader: "Advanced Options"; "Linux 4.7.2", the machine loads the drive and asks for password. Then the screen just goes blank. If I boot into 4.7.2 recovery mode, I am able to access Ubuntu 18.04 and login.



      Grub configuration is at i8042.reset nomodeset. Previously it was set to quiet splash. Neither has solved the boot issue.



      What can I do to solve the interrupted upgrade process (to where the upgrade did not successfully complete during running in Ubuntu 17), and to where I can boot into Ubuntu without recovery mode?



      lsb_release -a `


      outputs: `



      LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic



      uname -a


      outputs:
      4.7.2-040702-generic #201608201334 SMP Sat Aug 20 17:37:03 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux



      Is there anything I can do to where Ubuntu 18.04 can boot normally? Without having to choose Recovery Mode? How can I correct this issue?









      share|improve this question










      share|improve this question




      share|improve this question









      asked Apr 28 at 22:11









      user1780064

      11




      11




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          Try the following steps in this order:



          sudo rm /var/lib/dpkg/lock
          sudo dpkg --configure -a
          # only continue if the above results in zero packages left to configure.
          sudo apt-get dist-upgrade





          share|improve this answer





















          • this might brak his systems we dont wven know what is going on.
            – vfbsilva
            Apr 29 at 1:57










          • @vfbsilva Their system is already broken :P Also, dpkg --configure -a is safe. If it works it works. If it doesn't it doesn't. I won't make things worse. HOWEVER dist-upgrade would potentially mess things up if packages are left unconfigured which is why I said don't continue if it doesn't fully configure.
            – jdwolf
            Apr 29 at 3:47











          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: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440654%2fubuntu-18-04-lts-only-boots-with-recovery-mode-with-linux-4-7-2-after-upgrade%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote













          Try the following steps in this order:



          sudo rm /var/lib/dpkg/lock
          sudo dpkg --configure -a
          # only continue if the above results in zero packages left to configure.
          sudo apt-get dist-upgrade





          share|improve this answer





















          • this might brak his systems we dont wven know what is going on.
            – vfbsilva
            Apr 29 at 1:57










          • @vfbsilva Their system is already broken :P Also, dpkg --configure -a is safe. If it works it works. If it doesn't it doesn't. I won't make things worse. HOWEVER dist-upgrade would potentially mess things up if packages are left unconfigured which is why I said don't continue if it doesn't fully configure.
            – jdwolf
            Apr 29 at 3:47















          up vote
          0
          down vote













          Try the following steps in this order:



          sudo rm /var/lib/dpkg/lock
          sudo dpkg --configure -a
          # only continue if the above results in zero packages left to configure.
          sudo apt-get dist-upgrade





          share|improve this answer





















          • this might brak his systems we dont wven know what is going on.
            – vfbsilva
            Apr 29 at 1:57










          • @vfbsilva Their system is already broken :P Also, dpkg --configure -a is safe. If it works it works. If it doesn't it doesn't. I won't make things worse. HOWEVER dist-upgrade would potentially mess things up if packages are left unconfigured which is why I said don't continue if it doesn't fully configure.
            – jdwolf
            Apr 29 at 3:47













          up vote
          0
          down vote










          up vote
          0
          down vote









          Try the following steps in this order:



          sudo rm /var/lib/dpkg/lock
          sudo dpkg --configure -a
          # only continue if the above results in zero packages left to configure.
          sudo apt-get dist-upgrade





          share|improve this answer













          Try the following steps in this order:



          sudo rm /var/lib/dpkg/lock
          sudo dpkg --configure -a
          # only continue if the above results in zero packages left to configure.
          sudo apt-get dist-upgrade






          share|improve this answer













          share|improve this answer



          share|improve this answer











          answered Apr 29 at 1:41









          jdwolf

          2,362116




          2,362116











          • this might brak his systems we dont wven know what is going on.
            – vfbsilva
            Apr 29 at 1:57










          • @vfbsilva Their system is already broken :P Also, dpkg --configure -a is safe. If it works it works. If it doesn't it doesn't. I won't make things worse. HOWEVER dist-upgrade would potentially mess things up if packages are left unconfigured which is why I said don't continue if it doesn't fully configure.
            – jdwolf
            Apr 29 at 3:47

















          • this might brak his systems we dont wven know what is going on.
            – vfbsilva
            Apr 29 at 1:57










          • @vfbsilva Their system is already broken :P Also, dpkg --configure -a is safe. If it works it works. If it doesn't it doesn't. I won't make things worse. HOWEVER dist-upgrade would potentially mess things up if packages are left unconfigured which is why I said don't continue if it doesn't fully configure.
            – jdwolf
            Apr 29 at 3:47
















          this might brak his systems we dont wven know what is going on.
          – vfbsilva
          Apr 29 at 1:57




          this might brak his systems we dont wven know what is going on.
          – vfbsilva
          Apr 29 at 1:57












          @vfbsilva Their system is already broken :P Also, dpkg --configure -a is safe. If it works it works. If it doesn't it doesn't. I won't make things worse. HOWEVER dist-upgrade would potentially mess things up if packages are left unconfigured which is why I said don't continue if it doesn't fully configure.
          – jdwolf
          Apr 29 at 3:47





          @vfbsilva Their system is already broken :P Also, dpkg --configure -a is safe. If it works it works. If it doesn't it doesn't. I won't make things worse. HOWEVER dist-upgrade would potentially mess things up if packages are left unconfigured which is why I said don't continue if it doesn't fully configure.
          – jdwolf
          Apr 29 at 3:47













           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440654%2fubuntu-18-04-lts-only-boots-with-recovery-mode-with-linux-4-7-2-after-upgrade%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?