Issues after update 16.04 - 18.04 LTS











up vote
0
down vote

favorite












Apologies in advance for the long introduction but I figured it would be better to give as much background as possible. I recently tried upgrading my HP Z420 workstation from 16.04 to 18.04 LTS. While updating, Ubuntu froze at the instance shown



here



I then rebooted after which I consistently got a kernel panic, as shown



here



I then booted from a live CD and ran bootrepair, with output shown info



This solved the Kernel Panic. However, now I only get a blank screen (same color as in Grub2).



When I enter Grub and select an earlier kernel, Ubuntu 18.04 loads but I only get a command line login, not a GUI. At the command I tried re-running apt-get update but this also gave errors relating to metadata, see



here



I am at a total loss how to get things up and running again, any help would be much appreciated.



Thanks!



UPDATE: according to janmyszkier's answer I checked the HDD for errors using the Disks utility (extended self-test) and, reassuringly, no issues were found.










share|improve this question




























    up vote
    0
    down vote

    favorite












    Apologies in advance for the long introduction but I figured it would be better to give as much background as possible. I recently tried upgrading my HP Z420 workstation from 16.04 to 18.04 LTS. While updating, Ubuntu froze at the instance shown



    here



    I then rebooted after which I consistently got a kernel panic, as shown



    here



    I then booted from a live CD and ran bootrepair, with output shown info



    This solved the Kernel Panic. However, now I only get a blank screen (same color as in Grub2).



    When I enter Grub and select an earlier kernel, Ubuntu 18.04 loads but I only get a command line login, not a GUI. At the command I tried re-running apt-get update but this also gave errors relating to metadata, see



    here



    I am at a total loss how to get things up and running again, any help would be much appreciated.



    Thanks!



    UPDATE: according to janmyszkier's answer I checked the HDD for errors using the Disks utility (extended self-test) and, reassuringly, no issues were found.










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Apologies in advance for the long introduction but I figured it would be better to give as much background as possible. I recently tried upgrading my HP Z420 workstation from 16.04 to 18.04 LTS. While updating, Ubuntu froze at the instance shown



      here



      I then rebooted after which I consistently got a kernel panic, as shown



      here



      I then booted from a live CD and ran bootrepair, with output shown info



      This solved the Kernel Panic. However, now I only get a blank screen (same color as in Grub2).



      When I enter Grub and select an earlier kernel, Ubuntu 18.04 loads but I only get a command line login, not a GUI. At the command I tried re-running apt-get update but this also gave errors relating to metadata, see



      here



      I am at a total loss how to get things up and running again, any help would be much appreciated.



      Thanks!



      UPDATE: according to janmyszkier's answer I checked the HDD for errors using the Disks utility (extended self-test) and, reassuringly, no issues were found.










      share|improve this question















      Apologies in advance for the long introduction but I figured it would be better to give as much background as possible. I recently tried upgrading my HP Z420 workstation from 16.04 to 18.04 LTS. While updating, Ubuntu froze at the instance shown



      here



      I then rebooted after which I consistently got a kernel panic, as shown



      here



      I then booted from a live CD and ran bootrepair, with output shown info



      This solved the Kernel Panic. However, now I only get a blank screen (same color as in Grub2).



      When I enter Grub and select an earlier kernel, Ubuntu 18.04 loads but I only get a command line login, not a GUI. At the command I tried re-running apt-get update but this also gave errors relating to metadata, see



      here



      I am at a total loss how to get things up and running again, any help would be much appreciated.



      Thanks!



      UPDATE: according to janmyszkier's answer I checked the HDD for errors using the Disks utility (extended self-test) and, reassuringly, no issues were found.







      boot 18.04 upgrade






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 27 at 9:06

























      asked Nov 23 at 15:58









      DasTochNietNormaal

      11




      11






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          I would suggest taking a backup of your drive as a safe measure.
          Then, you should be able to walk into the currently installed instance with a method called "chroot" (short for change root) which is described here:
          https://help.ubuntu.com/community/LiveCdRecovery



          once you have chroot-ed into your original install, you should be able to run apt-get update and apt-get upgrade commands from within, fixing the package issues you had initially.



          However, chances are, the installer broke because you had IO issues with your laptop disk (if it's HDD I've seen this happening multiple times) so might be a good thing to check your disk right after creating a backup.






          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1095422%2fissues-after-update-16-04-18-04-lts%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            I would suggest taking a backup of your drive as a safe measure.
            Then, you should be able to walk into the currently installed instance with a method called "chroot" (short for change root) which is described here:
            https://help.ubuntu.com/community/LiveCdRecovery



            once you have chroot-ed into your original install, you should be able to run apt-get update and apt-get upgrade commands from within, fixing the package issues you had initially.



            However, chances are, the installer broke because you had IO issues with your laptop disk (if it's HDD I've seen this happening multiple times) so might be a good thing to check your disk right after creating a backup.






            share|improve this answer

























              up vote
              0
              down vote













              I would suggest taking a backup of your drive as a safe measure.
              Then, you should be able to walk into the currently installed instance with a method called "chroot" (short for change root) which is described here:
              https://help.ubuntu.com/community/LiveCdRecovery



              once you have chroot-ed into your original install, you should be able to run apt-get update and apt-get upgrade commands from within, fixing the package issues you had initially.



              However, chances are, the installer broke because you had IO issues with your laptop disk (if it's HDD I've seen this happening multiple times) so might be a good thing to check your disk right after creating a backup.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                I would suggest taking a backup of your drive as a safe measure.
                Then, you should be able to walk into the currently installed instance with a method called "chroot" (short for change root) which is described here:
                https://help.ubuntu.com/community/LiveCdRecovery



                once you have chroot-ed into your original install, you should be able to run apt-get update and apt-get upgrade commands from within, fixing the package issues you had initially.



                However, chances are, the installer broke because you had IO issues with your laptop disk (if it's HDD I've seen this happening multiple times) so might be a good thing to check your disk right after creating a backup.






                share|improve this answer












                I would suggest taking a backup of your drive as a safe measure.
                Then, you should be able to walk into the currently installed instance with a method called "chroot" (short for change root) which is described here:
                https://help.ubuntu.com/community/LiveCdRecovery



                once you have chroot-ed into your original install, you should be able to run apt-get update and apt-get upgrade commands from within, fixing the package issues you had initially.



                However, chances are, the installer broke because you had IO issues with your laptop disk (if it's HDD I've seen this happening multiple times) so might be a good thing to check your disk right after creating a backup.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 23 at 16:03









                janmyszkier

                50827




                50827






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1095422%2fissues-after-update-16-04-18-04-lts%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Quarter-circle Tiles

                    build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

                    Mont Emei