Ubuntu 14.04 boot hangs at “EXT4-fs: mounted filesystem without journal”












0















I have just made a new Ubuntu 14.04 installation on a new SSD Drive for my server.
Previously I had a Ubuntu 12.04 installation that worked fine, but I have now changed harddrive to an SSD.
The installation process completes without any problem. I do a manual partitioning with one boot partition (100Mb), one swap (2Gb) and the rest (ca. 60 Gb) for root partition.



When the system then boots it goes normal for some time and then stops at the point showed i picture:



(EXT4-fs (sdg1): mounted filesystem without journal. Opts: (null)).



Ubuntu 14.04 - Boot log



What can I do to fix it? What is wrong? Why does it not boot?










share|improve this question
















bumped to the homepage by Community 5 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Maybe it can't access your filesystem?

    – Dillmo
    Apr 20 '14 at 21:17











  • Well all it has to access is what was written during installation and that went though without any problems.

    – user271638
    Apr 20 '14 at 21:55
















0















I have just made a new Ubuntu 14.04 installation on a new SSD Drive for my server.
Previously I had a Ubuntu 12.04 installation that worked fine, but I have now changed harddrive to an SSD.
The installation process completes without any problem. I do a manual partitioning with one boot partition (100Mb), one swap (2Gb) and the rest (ca. 60 Gb) for root partition.



When the system then boots it goes normal for some time and then stops at the point showed i picture:



(EXT4-fs (sdg1): mounted filesystem without journal. Opts: (null)).



Ubuntu 14.04 - Boot log



What can I do to fix it? What is wrong? Why does it not boot?










share|improve this question
















bumped to the homepage by Community 5 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Maybe it can't access your filesystem?

    – Dillmo
    Apr 20 '14 at 21:17











  • Well all it has to access is what was written during installation and that went though without any problems.

    – user271638
    Apr 20 '14 at 21:55














0












0








0


0






I have just made a new Ubuntu 14.04 installation on a new SSD Drive for my server.
Previously I had a Ubuntu 12.04 installation that worked fine, but I have now changed harddrive to an SSD.
The installation process completes without any problem. I do a manual partitioning with one boot partition (100Mb), one swap (2Gb) and the rest (ca. 60 Gb) for root partition.



When the system then boots it goes normal for some time and then stops at the point showed i picture:



(EXT4-fs (sdg1): mounted filesystem without journal. Opts: (null)).



Ubuntu 14.04 - Boot log



What can I do to fix it? What is wrong? Why does it not boot?










share|improve this question
















I have just made a new Ubuntu 14.04 installation on a new SSD Drive for my server.
Previously I had a Ubuntu 12.04 installation that worked fine, but I have now changed harddrive to an SSD.
The installation process completes without any problem. I do a manual partitioning with one boot partition (100Mb), one swap (2Gb) and the rest (ca. 60 Gb) for root partition.



When the system then boots it goes normal for some time and then stops at the point showed i picture:



(EXT4-fs (sdg1): mounted filesystem without journal. Opts: (null)).



Ubuntu 14.04 - Boot log



What can I do to fix it? What is wrong? Why does it not boot?







boot server






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 8 '14 at 12:41









Malte Skoruppa

9,03343856




9,03343856










asked Apr 20 '14 at 21:08









user271638user271638

111




111





bumped to the homepage by Community 5 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 5 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Maybe it can't access your filesystem?

    – Dillmo
    Apr 20 '14 at 21:17











  • Well all it has to access is what was written during installation and that went though without any problems.

    – user271638
    Apr 20 '14 at 21:55



















  • Maybe it can't access your filesystem?

    – Dillmo
    Apr 20 '14 at 21:17











  • Well all it has to access is what was written during installation and that went though without any problems.

    – user271638
    Apr 20 '14 at 21:55

















Maybe it can't access your filesystem?

– Dillmo
Apr 20 '14 at 21:17





Maybe it can't access your filesystem?

– Dillmo
Apr 20 '14 at 21:17













Well all it has to access is what was written during installation and that went though without any problems.

– user271638
Apr 20 '14 at 21:55





Well all it has to access is what was written during installation and that went though without any problems.

– user271638
Apr 20 '14 at 21:55










1 Answer
1






active

oldest

votes


















0














Had the same problem. What I found was the server was actually coming up. I could ssh to it and found the issue is caused by the graphic Nvidia card.



I did:



sudo apt-get install nvidia-current-updates-dev



And this did it. You might give it a try.






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',
    autoActivateHeartbeat: false,
    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%2f451630%2fubuntu-14-04-boot-hangs-at-ext4-fs-mounted-filesystem-without-journal%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









    0














    Had the same problem. What I found was the server was actually coming up. I could ssh to it and found the issue is caused by the graphic Nvidia card.



    I did:



    sudo apt-get install nvidia-current-updates-dev



    And this did it. You might give it a try.






    share|improve this answer




























      0














      Had the same problem. What I found was the server was actually coming up. I could ssh to it and found the issue is caused by the graphic Nvidia card.



      I did:



      sudo apt-get install nvidia-current-updates-dev



      And this did it. You might give it a try.






      share|improve this answer


























        0












        0








        0







        Had the same problem. What I found was the server was actually coming up. I could ssh to it and found the issue is caused by the graphic Nvidia card.



        I did:



        sudo apt-get install nvidia-current-updates-dev



        And this did it. You might give it a try.






        share|improve this answer













        Had the same problem. What I found was the server was actually coming up. I could ssh to it and found the issue is caused by the graphic Nvidia card.



        I did:



        sudo apt-get install nvidia-current-updates-dev



        And this did it. You might give it a try.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 8 '14 at 12:26









        PSZPSZ

        1




        1






























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f451630%2fubuntu-14-04-boot-hangs-at-ext4-fs-mounted-filesystem-without-journal%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

            GameSpot

            connect to host localhost port 22: Connection refused

            Getting a Wifi WPA2 wifi connection