Press enter for maintenance (or type control-d to continue)












0















I am using windows 10 and configured Ubuntu on virtual machine using Hyper-V for making a shared file server within our small office. I have assigned 2048Mb RAM to Ubuntu file server. I am facing a problem, whenever the physical computer shuts down accidentally (Due to electricity issue) and restarts, the file server is not accessible. When I open the Hyper-V, Ubuntu gives the message in last line



Welcome to emergency mode! After logging in, type "journalct1 -xb" to view
Press enter for maintenance (or press Control-D to continue"




The only problem is that I have to manually RDP the server and click manually the CtrlD to continue otherwise it keeps there and server files are not accessible.



I am not very good in Linux and just first time I am using it with the help of video tutorials.
Kindly help me out to get rid of this situation so in any case when the physical computer restarts, the VM starts completely itself.
Thanks.










share|improve this question




















  • 2





    Maybe you should actually run journalctl -xb for once and see what is failing.

    – muru
    Apr 3 '17 at 7:10






  • 2





    Maybe you should put this ubuntu server on dedicated machine or cloud VPS.

    – Kamil
    Apr 3 '17 at 8:28











  • Getting this error when trying to execute journalctl -xb Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions.

    – Umar saifi
    Apr 3 '17 at 8:33


















0















I am using windows 10 and configured Ubuntu on virtual machine using Hyper-V for making a shared file server within our small office. I have assigned 2048Mb RAM to Ubuntu file server. I am facing a problem, whenever the physical computer shuts down accidentally (Due to electricity issue) and restarts, the file server is not accessible. When I open the Hyper-V, Ubuntu gives the message in last line



Welcome to emergency mode! After logging in, type "journalct1 -xb" to view
Press enter for maintenance (or press Control-D to continue"




The only problem is that I have to manually RDP the server and click manually the CtrlD to continue otherwise it keeps there and server files are not accessible.



I am not very good in Linux and just first time I am using it with the help of video tutorials.
Kindly help me out to get rid of this situation so in any case when the physical computer restarts, the VM starts completely itself.
Thanks.










share|improve this question




















  • 2





    Maybe you should actually run journalctl -xb for once and see what is failing.

    – muru
    Apr 3 '17 at 7:10






  • 2





    Maybe you should put this ubuntu server on dedicated machine or cloud VPS.

    – Kamil
    Apr 3 '17 at 8:28











  • Getting this error when trying to execute journalctl -xb Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions.

    – Umar saifi
    Apr 3 '17 at 8:33
















0












0








0








I am using windows 10 and configured Ubuntu on virtual machine using Hyper-V for making a shared file server within our small office. I have assigned 2048Mb RAM to Ubuntu file server. I am facing a problem, whenever the physical computer shuts down accidentally (Due to electricity issue) and restarts, the file server is not accessible. When I open the Hyper-V, Ubuntu gives the message in last line



Welcome to emergency mode! After logging in, type "journalct1 -xb" to view
Press enter for maintenance (or press Control-D to continue"




The only problem is that I have to manually RDP the server and click manually the CtrlD to continue otherwise it keeps there and server files are not accessible.



I am not very good in Linux and just first time I am using it with the help of video tutorials.
Kindly help me out to get rid of this situation so in any case when the physical computer restarts, the VM starts completely itself.
Thanks.










share|improve this question
















I am using windows 10 and configured Ubuntu on virtual machine using Hyper-V for making a shared file server within our small office. I have assigned 2048Mb RAM to Ubuntu file server. I am facing a problem, whenever the physical computer shuts down accidentally (Due to electricity issue) and restarts, the file server is not accessible. When I open the Hyper-V, Ubuntu gives the message in last line



Welcome to emergency mode! After logging in, type "journalct1 -xb" to view
Press enter for maintenance (or press Control-D to continue"




The only problem is that I have to manually RDP the server and click manually the CtrlD to continue otherwise it keeps there and server files are not accessible.



I am not very good in Linux and just first time I am using it with the help of video tutorials.
Kindly help me out to get rid of this situation so in any case when the physical computer restarts, the VM starts completely itself.
Thanks.







server






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 3 '17 at 9:12









muru

1




1










asked Apr 3 '17 at 7:02









Umar saifiUmar saifi

111




111








  • 2





    Maybe you should actually run journalctl -xb for once and see what is failing.

    – muru
    Apr 3 '17 at 7:10






  • 2





    Maybe you should put this ubuntu server on dedicated machine or cloud VPS.

    – Kamil
    Apr 3 '17 at 8:28











  • Getting this error when trying to execute journalctl -xb Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions.

    – Umar saifi
    Apr 3 '17 at 8:33
















  • 2





    Maybe you should actually run journalctl -xb for once and see what is failing.

    – muru
    Apr 3 '17 at 7:10






  • 2





    Maybe you should put this ubuntu server on dedicated machine or cloud VPS.

    – Kamil
    Apr 3 '17 at 8:28











  • Getting this error when trying to execute journalctl -xb Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions.

    – Umar saifi
    Apr 3 '17 at 8:33










2




2





Maybe you should actually run journalctl -xb for once and see what is failing.

– muru
Apr 3 '17 at 7:10





Maybe you should actually run journalctl -xb for once and see what is failing.

– muru
Apr 3 '17 at 7:10




2




2





Maybe you should put this ubuntu server on dedicated machine or cloud VPS.

– Kamil
Apr 3 '17 at 8:28





Maybe you should put this ubuntu server on dedicated machine or cloud VPS.

– Kamil
Apr 3 '17 at 8:28













Getting this error when trying to execute journalctl -xb Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions.

– Umar saifi
Apr 3 '17 at 8:33







Getting this error when trying to execute journalctl -xb Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions.

– Umar saifi
Apr 3 '17 at 8:33












2 Answers
2






active

oldest

votes


















0














You need to combat the sickness, not the symptoms!



If your server shuts down because of electricity failures, buy an Uninterruptible Power Supply (UPS)! If you don't, not only is your file system going to go haywire after enough interruptions, but your hardware as well...



That's why we have data centers where we normally store our servers, and if you can't afford a UPS: UPSes are much cheaper to buy then new computers... (Which makes this answer and your question totally off-topic here)



We could make the pesky error message go away but that would be like giving you an aspirin instead of giving you antibiotics to cure your disease.






share|improve this answer
























  • Thanks for your response. i am looking for APC UPS in parallel. Meanwhile i want to overcome this issue as well,that was the purpose of posting question.

    – Umar saifi
    Apr 3 '17 at 11:22











  • You can't overcome hardware issues by a software solution while the reverse is sometimes true...

    – Fabby
    Apr 4 '17 at 11:58



















0














Probably your file-system is corrupted. Try this:



First identify your partition.



Run the command:




umount -t /dev/your-partition




Then:




fsck -y /dev/your-partition




For example, my Linux / directory is at sda3, but my /home directory is at sda5, so when something like this happens to me, I do the following:




  • Press enter for command line;


  • Type:




umount -t /dev/sda3





  • Hit enter;



umount -t /dev/sda5




*****DO NOT USE: umount -a*****




  • Hit enter;


  • Then:




fsck -y /dev/sda3





  • Hit enter;



fsck -y /dev/sda5





  • Hit enter;


If you don't know which partition to choose, type umount -t /dev/sd and hit tab twice for you to see its available partitions.






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%2f899634%2fpress-enter-for-maintenance-or-type-control-d-to-continue%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    You need to combat the sickness, not the symptoms!



    If your server shuts down because of electricity failures, buy an Uninterruptible Power Supply (UPS)! If you don't, not only is your file system going to go haywire after enough interruptions, but your hardware as well...



    That's why we have data centers where we normally store our servers, and if you can't afford a UPS: UPSes are much cheaper to buy then new computers... (Which makes this answer and your question totally off-topic here)



    We could make the pesky error message go away but that would be like giving you an aspirin instead of giving you antibiotics to cure your disease.






    share|improve this answer
























    • Thanks for your response. i am looking for APC UPS in parallel. Meanwhile i want to overcome this issue as well,that was the purpose of posting question.

      – Umar saifi
      Apr 3 '17 at 11:22











    • You can't overcome hardware issues by a software solution while the reverse is sometimes true...

      – Fabby
      Apr 4 '17 at 11:58
















    0














    You need to combat the sickness, not the symptoms!



    If your server shuts down because of electricity failures, buy an Uninterruptible Power Supply (UPS)! If you don't, not only is your file system going to go haywire after enough interruptions, but your hardware as well...



    That's why we have data centers where we normally store our servers, and if you can't afford a UPS: UPSes are much cheaper to buy then new computers... (Which makes this answer and your question totally off-topic here)



    We could make the pesky error message go away but that would be like giving you an aspirin instead of giving you antibiotics to cure your disease.






    share|improve this answer
























    • Thanks for your response. i am looking for APC UPS in parallel. Meanwhile i want to overcome this issue as well,that was the purpose of posting question.

      – Umar saifi
      Apr 3 '17 at 11:22











    • You can't overcome hardware issues by a software solution while the reverse is sometimes true...

      – Fabby
      Apr 4 '17 at 11:58














    0












    0








    0







    You need to combat the sickness, not the symptoms!



    If your server shuts down because of electricity failures, buy an Uninterruptible Power Supply (UPS)! If you don't, not only is your file system going to go haywire after enough interruptions, but your hardware as well...



    That's why we have data centers where we normally store our servers, and if you can't afford a UPS: UPSes are much cheaper to buy then new computers... (Which makes this answer and your question totally off-topic here)



    We could make the pesky error message go away but that would be like giving you an aspirin instead of giving you antibiotics to cure your disease.






    share|improve this answer













    You need to combat the sickness, not the symptoms!



    If your server shuts down because of electricity failures, buy an Uninterruptible Power Supply (UPS)! If you don't, not only is your file system going to go haywire after enough interruptions, but your hardware as well...



    That's why we have data centers where we normally store our servers, and if you can't afford a UPS: UPSes are much cheaper to buy then new computers... (Which makes this answer and your question totally off-topic here)



    We could make the pesky error message go away but that would be like giving you an aspirin instead of giving you antibiotics to cure your disease.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Apr 3 '17 at 8:58









    FabbyFabby

    26.6k1360159




    26.6k1360159













    • Thanks for your response. i am looking for APC UPS in parallel. Meanwhile i want to overcome this issue as well,that was the purpose of posting question.

      – Umar saifi
      Apr 3 '17 at 11:22











    • You can't overcome hardware issues by a software solution while the reverse is sometimes true...

      – Fabby
      Apr 4 '17 at 11:58



















    • Thanks for your response. i am looking for APC UPS in parallel. Meanwhile i want to overcome this issue as well,that was the purpose of posting question.

      – Umar saifi
      Apr 3 '17 at 11:22











    • You can't overcome hardware issues by a software solution while the reverse is sometimes true...

      – Fabby
      Apr 4 '17 at 11:58

















    Thanks for your response. i am looking for APC UPS in parallel. Meanwhile i want to overcome this issue as well,that was the purpose of posting question.

    – Umar saifi
    Apr 3 '17 at 11:22





    Thanks for your response. i am looking for APC UPS in parallel. Meanwhile i want to overcome this issue as well,that was the purpose of posting question.

    – Umar saifi
    Apr 3 '17 at 11:22













    You can't overcome hardware issues by a software solution while the reverse is sometimes true...

    – Fabby
    Apr 4 '17 at 11:58





    You can't overcome hardware issues by a software solution while the reverse is sometimes true...

    – Fabby
    Apr 4 '17 at 11:58













    0














    Probably your file-system is corrupted. Try this:



    First identify your partition.



    Run the command:




    umount -t /dev/your-partition




    Then:




    fsck -y /dev/your-partition




    For example, my Linux / directory is at sda3, but my /home directory is at sda5, so when something like this happens to me, I do the following:




    • Press enter for command line;


    • Type:




    umount -t /dev/sda3





    • Hit enter;



    umount -t /dev/sda5




    *****DO NOT USE: umount -a*****




    • Hit enter;


    • Then:




    fsck -y /dev/sda3





    • Hit enter;



    fsck -y /dev/sda5





    • Hit enter;


    If you don't know which partition to choose, type umount -t /dev/sd and hit tab twice for you to see its available partitions.






    share|improve this answer






























      0














      Probably your file-system is corrupted. Try this:



      First identify your partition.



      Run the command:




      umount -t /dev/your-partition




      Then:




      fsck -y /dev/your-partition




      For example, my Linux / directory is at sda3, but my /home directory is at sda5, so when something like this happens to me, I do the following:




      • Press enter for command line;


      • Type:




      umount -t /dev/sda3





      • Hit enter;



      umount -t /dev/sda5




      *****DO NOT USE: umount -a*****




      • Hit enter;


      • Then:




      fsck -y /dev/sda3





      • Hit enter;



      fsck -y /dev/sda5





      • Hit enter;


      If you don't know which partition to choose, type umount -t /dev/sd and hit tab twice for you to see its available partitions.






      share|improve this answer




























        0












        0








        0







        Probably your file-system is corrupted. Try this:



        First identify your partition.



        Run the command:




        umount -t /dev/your-partition




        Then:




        fsck -y /dev/your-partition




        For example, my Linux / directory is at sda3, but my /home directory is at sda5, so when something like this happens to me, I do the following:




        • Press enter for command line;


        • Type:




        umount -t /dev/sda3





        • Hit enter;



        umount -t /dev/sda5




        *****DO NOT USE: umount -a*****




        • Hit enter;


        • Then:




        fsck -y /dev/sda3





        • Hit enter;



        fsck -y /dev/sda5





        • Hit enter;


        If you don't know which partition to choose, type umount -t /dev/sd and hit tab twice for you to see its available partitions.






        share|improve this answer















        Probably your file-system is corrupted. Try this:



        First identify your partition.



        Run the command:




        umount -t /dev/your-partition




        Then:




        fsck -y /dev/your-partition




        For example, my Linux / directory is at sda3, but my /home directory is at sda5, so when something like this happens to me, I do the following:




        • Press enter for command line;


        • Type:




        umount -t /dev/sda3





        • Hit enter;



        umount -t /dev/sda5




        *****DO NOT USE: umount -a*****




        • Hit enter;


        • Then:




        fsck -y /dev/sda3





        • Hit enter;



        fsck -y /dev/sda5





        • Hit enter;


        If you don't know which partition to choose, type umount -t /dev/sd and hit tab twice for you to see its available partitions.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Oct 28 '17 at 19:01

























        answered Aug 31 '17 at 18:46









        Eduardo HenriqueEduardo Henrique

        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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f899634%2fpress-enter-for-maintenance-or-type-control-d-to-continue%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

            Human spaceflight

            Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

            張江高科駅