Ubuntu 16.04 had been working well for over a year. After a standard update, re-boot freezes on purple screen











up vote
0
down vote

favorite












Ubuntu 16.04 had been working well for over a year. Then, after a standard software update, as it was very slow I shut down and tried to re-boot.



I was led first to the blank purple screen. Eventually I got the menu to select recovery linux versions. I tried Linux 4.15.0-39-generic and that tried to boot, getting to a black and white screen ending with
---[end Kernel panic - not syncing: VFS: unable to mount root fs on unknown block(0,0)



I tried getting to the Grub prompt but had no success trying to boot manually, using the sugggestions in thread After update in Ubuntu 16.04 I ended up in GNU GRUB and appear to be stuck there






16.04 boot grubrescue







share|improve this question






















  • try booting into an older kernel version, and see if that works
    – ARG
    Nov 20 at 10:51















up vote
0
down vote

favorite












Ubuntu 16.04 had been working well for over a year. Then, after a standard software update, as it was very slow I shut down and tried to re-boot.



I was led first to the blank purple screen. Eventually I got the menu to select recovery linux versions. I tried Linux 4.15.0-39-generic and that tried to boot, getting to a black and white screen ending with
---[end Kernel panic - not syncing: VFS: unable to mount root fs on unknown block(0,0)



I tried getting to the Grub prompt but had no success trying to boot manually, using the sugggestions in thread After update in Ubuntu 16.04 I ended up in GNU GRUB and appear to be stuck there






16.04 boot grubrescue







share|improve this question






















  • try booting into an older kernel version, and see if that works
    – ARG
    Nov 20 at 10:51













up vote
0
down vote

favorite









up vote
0
down vote

favorite











Ubuntu 16.04 had been working well for over a year. Then, after a standard software update, as it was very slow I shut down and tried to re-boot.



I was led first to the blank purple screen. Eventually I got the menu to select recovery linux versions. I tried Linux 4.15.0-39-generic and that tried to boot, getting to a black and white screen ending with
---[end Kernel panic - not syncing: VFS: unable to mount root fs on unknown block(0,0)



I tried getting to the Grub prompt but had no success trying to boot manually, using the sugggestions in thread After update in Ubuntu 16.04 I ended up in GNU GRUB and appear to be stuck there






16.04 boot grubrescue







share|improve this question













Ubuntu 16.04 had been working well for over a year. Then, after a standard software update, as it was very slow I shut down and tried to re-boot.



I was led first to the blank purple screen. Eventually I got the menu to select recovery linux versions. I tried Linux 4.15.0-39-generic and that tried to boot, getting to a black and white screen ending with
---[end Kernel panic - not syncing: VFS: unable to mount root fs on unknown block(0,0)



I tried getting to the Grub prompt but had no success trying to boot manually, using the sugggestions in thread After update in Ubuntu 16.04 I ended up in GNU GRUB and appear to be stuck there






16.04 boot grubrescue




16.04 boot grubrescue






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 20 at 10:48









Hugh

11




11












  • try booting into an older kernel version, and see if that works
    – ARG
    Nov 20 at 10:51


















  • try booting into an older kernel version, and see if that works
    – ARG
    Nov 20 at 10:51
















try booting into an older kernel version, and see if that works
– ARG
Nov 20 at 10:51




try booting into an older kernel version, and see if that works
– ARG
Nov 20 at 10:51










1 Answer
1






active

oldest

votes

















up vote
0
down vote













I got the right verion of the vmlinuz file in the boot directory. Then I tried



grub> set root=(hd0,2)
grub> linux (hd0,2)/boot/vmlinuz-4.4.0-89-generic root=/dev/sda2
grub> initrd (hd0,2)/boot/initrd.img-4.4.0-89-generic
grub> boot



where instead of the above values I used the full path to my vlinuz and initrd files. This, also ansuring to point to sda2, finaly got back to a good boot with all files intact etc






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%2f1094481%2fubuntu-16-04-had-been-working-well-for-over-a-year-after-a-standard-update-re%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 got the right verion of the vmlinuz file in the boot directory. Then I tried



    grub> set root=(hd0,2)
    grub> linux (hd0,2)/boot/vmlinuz-4.4.0-89-generic root=/dev/sda2
    grub> initrd (hd0,2)/boot/initrd.img-4.4.0-89-generic
    grub> boot



    where instead of the above values I used the full path to my vlinuz and initrd files. This, also ansuring to point to sda2, finaly got back to a good boot with all files intact etc






    share|improve this answer

























      up vote
      0
      down vote













      I got the right verion of the vmlinuz file in the boot directory. Then I tried



      grub> set root=(hd0,2)
      grub> linux (hd0,2)/boot/vmlinuz-4.4.0-89-generic root=/dev/sda2
      grub> initrd (hd0,2)/boot/initrd.img-4.4.0-89-generic
      grub> boot



      where instead of the above values I used the full path to my vlinuz and initrd files. This, also ansuring to point to sda2, finaly got back to a good boot with all files intact etc






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        I got the right verion of the vmlinuz file in the boot directory. Then I tried



        grub> set root=(hd0,2)
        grub> linux (hd0,2)/boot/vmlinuz-4.4.0-89-generic root=/dev/sda2
        grub> initrd (hd0,2)/boot/initrd.img-4.4.0-89-generic
        grub> boot



        where instead of the above values I used the full path to my vlinuz and initrd files. This, also ansuring to point to sda2, finaly got back to a good boot with all files intact etc






        share|improve this answer












        I got the right verion of the vmlinuz file in the boot directory. Then I tried



        grub> set root=(hd0,2)
        grub> linux (hd0,2)/boot/vmlinuz-4.4.0-89-generic root=/dev/sda2
        grub> initrd (hd0,2)/boot/initrd.img-4.4.0-89-generic
        grub> boot



        where instead of the above values I used the full path to my vlinuz and initrd files. This, also ansuring to point to sda2, finaly got back to a good boot with all files intact etc







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 20 at 12:50









        Hugh

        11




        11






























            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%2f1094481%2fubuntu-16-04-had-been-working-well-for-over-a-year-after-a-standard-update-re%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

            How to change which sound is reproduced for terminal bell?

            Image
            3 Recently upgrade to 18.10 from 18.04, and using the terminal is becoming annoying: the new alert sound is a drip ( /usr/share/sounds/gnome/default/alerts/drip.ogg ), and the previous one is still located at ( /usr/share/sounds/ubuntu/stereo/bell.ogg ). My issue is that at the gnome-terminal, when autocompleting or pressing left BOTH sounds are reproduced, at the same time. I want to just have ubuntu/stereo/bell.ogg active, not both . At the moment I have been only able to reduce the volume of the alerts (but still both are played), or turn the alerts down (but I dislike both "solutions"). gnome-terminal 18.10 teminal-bell share | improve this question
            Read more

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

            Image
            up vote 5 down vote favorite 2 I would like to make it so that the vertical space below the title of each chapter is the same when using the Bjornstrup package (i.e. so that the descenders do not affect the spacing - as shown by the red arrow in the picture below). I think I'm fairly happy with the spacing around "A chapter", so I'd really like titles without descenders (e.g. "Contents") to have the same vertical spacing as "A chapter" below the title. I would also like to remove the large "0" in the contents title. Any help appreciated, as always. documentclass[11pt,a4paper]{book} % Packages[![enter image description here][1]][1] usepackage[left=3.5cm, right=3.5cm, top=4.3cm, bottom=4.25cm]{geometry} usepackage[utf8]{inputenc} usepackage{libertine} usepackage[libertine]{newtx
            Read more

            Can I use Tabulator js library in my java Spring + Thymeleaf project?

            Image
            0 I want to add Tabulator js to my java project. I added tabulator.min.js, tabulator.min.css to resources folder. After that added to my html page these dependencies as recommending in readme.md. <link rel="stylesheet" th:href="@{/css/tabulator.min.css}"> <script type="text/javascript" th:src="@{/js/tabulator.min.js}"></script> Now my tables view all elements, that I have in the html page, but not correct. In the documentation of Tabulator is example how to create header and table, var table = new Tabulator("#example-table", { columns:[ {title:"Name", field:"name", sorter:"string", width:200, editor:true}, {title:"Age", field:"age", sorter:"
            Read more