Cannot get past Emergency Mode Ubuntu 17.10

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








up vote
0
down vote

favorite
1












I'm working on both Ubuntu 17.10 and Windows 10 as a dual boot system. Suddenly today I restarted PC from Windows and tried to logged into Ubuntu and then I got stuck at emergency mode. Now I can't get pass the emergency mode.
This is what I get and I'm stuck in this screen



[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errdata; please update
[ 1.982327] ACPI_Error: [_SB_.PCIO.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[ 1.982338] ACPI_Error: Method parse/execution failed _SB.PCI0.RP05.PEGP.DD02._BCL, AE_NOT_FOUND (20170531/psparse-550)
[ 3.199674] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun o
[ 3.199760] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe a FIFO underrun
[ 3.455294] sd 4:0:0:0: [sdb] No Caching mode page found
[ 3.455351] sd 4:0:0:0: [sdb] Assuming drive cache: write through
/dev/sda10: clean, 473657/2869776 files, 5567557/1147616 blocks
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or D to boot into default mode.
Press Enter for maintenance


When I try to exit by pressing ctrl+D I it loads until 4.9% and redirected to this same screen. So I can't get pass trying to boot into default mode.



I checked and followed this askubuntu question by unmounting and running fsck -y for root directory with Ubuntu live cd. I don't think this is windows stutdown issue as I have been using the dual boot system for quite some time.



So, how can I get pass this and work on Ubuntu ? Any help would be appreciated.










share|improve this question





















  • Is there anything interesting in journalctl -xb?
    – Jos
    Feb 27 at 12:11














up vote
0
down vote

favorite
1












I'm working on both Ubuntu 17.10 and Windows 10 as a dual boot system. Suddenly today I restarted PC from Windows and tried to logged into Ubuntu and then I got stuck at emergency mode. Now I can't get pass the emergency mode.
This is what I get and I'm stuck in this screen



[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errdata; please update
[ 1.982327] ACPI_Error: [_SB_.PCIO.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[ 1.982338] ACPI_Error: Method parse/execution failed _SB.PCI0.RP05.PEGP.DD02._BCL, AE_NOT_FOUND (20170531/psparse-550)
[ 3.199674] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun o
[ 3.199760] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe a FIFO underrun
[ 3.455294] sd 4:0:0:0: [sdb] No Caching mode page found
[ 3.455351] sd 4:0:0:0: [sdb] Assuming drive cache: write through
/dev/sda10: clean, 473657/2869776 files, 5567557/1147616 blocks
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or D to boot into default mode.
Press Enter for maintenance


When I try to exit by pressing ctrl+D I it loads until 4.9% and redirected to this same screen. So I can't get pass trying to boot into default mode.



I checked and followed this askubuntu question by unmounting and running fsck -y for root directory with Ubuntu live cd. I don't think this is windows stutdown issue as I have been using the dual boot system for quite some time.



So, how can I get pass this and work on Ubuntu ? Any help would be appreciated.










share|improve this question





















  • Is there anything interesting in journalctl -xb?
    – Jos
    Feb 27 at 12:11












up vote
0
down vote

favorite
1









up vote
0
down vote

favorite
1






1





I'm working on both Ubuntu 17.10 and Windows 10 as a dual boot system. Suddenly today I restarted PC from Windows and tried to logged into Ubuntu and then I got stuck at emergency mode. Now I can't get pass the emergency mode.
This is what I get and I'm stuck in this screen



[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errdata; please update
[ 1.982327] ACPI_Error: [_SB_.PCIO.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[ 1.982338] ACPI_Error: Method parse/execution failed _SB.PCI0.RP05.PEGP.DD02._BCL, AE_NOT_FOUND (20170531/psparse-550)
[ 3.199674] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun o
[ 3.199760] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe a FIFO underrun
[ 3.455294] sd 4:0:0:0: [sdb] No Caching mode page found
[ 3.455351] sd 4:0:0:0: [sdb] Assuming drive cache: write through
/dev/sda10: clean, 473657/2869776 files, 5567557/1147616 blocks
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or D to boot into default mode.
Press Enter for maintenance


When I try to exit by pressing ctrl+D I it loads until 4.9% and redirected to this same screen. So I can't get pass trying to boot into default mode.



I checked and followed this askubuntu question by unmounting and running fsck -y for root directory with Ubuntu live cd. I don't think this is windows stutdown issue as I have been using the dual boot system for quite some time.



So, how can I get pass this and work on Ubuntu ? Any help would be appreciated.










share|improve this question













I'm working on both Ubuntu 17.10 and Windows 10 as a dual boot system. Suddenly today I restarted PC from Windows and tried to logged into Ubuntu and then I got stuck at emergency mode. Now I can't get pass the emergency mode.
This is what I get and I'm stuck in this screen



[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errdata; please update
[ 1.982327] ACPI_Error: [_SB_.PCIO.GFX0.DD02._BCL] Namespace lookup failure, AE_NOT_FOUND (20170531/psargs-364)
[ 1.982338] ACPI_Error: Method parse/execution failed _SB.PCI0.RP05.PEGP.DD02._BCL, AE_NOT_FOUND (20170531/psparse-550)
[ 3.199674] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun o
[ 3.199760] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe a FIFO underrun
[ 3.455294] sd 4:0:0:0: [sdb] No Caching mode page found
[ 3.455351] sd 4:0:0:0: [sdb] Assuming drive cache: write through
/dev/sda10: clean, 473657/2869776 files, 5567557/1147616 blocks
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or D to boot into default mode.
Press Enter for maintenance


When I try to exit by pressing ctrl+D I it loads until 4.9% and redirected to this same screen. So I can't get pass trying to boot into default mode.



I checked and followed this askubuntu question by unmounting and running fsck -y for root directory with Ubuntu live cd. I don't think this is windows stutdown issue as I have been using the dual boot system for quite some time.



So, how can I get pass this and work on Ubuntu ? Any help would be appreciated.







boot dual-boot 17.10






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 27 at 11:16









Pankaja Paranavitharana

1351517




1351517











  • Is there anything interesting in journalctl -xb?
    – Jos
    Feb 27 at 12:11
















  • Is there anything interesting in journalctl -xb?
    – Jos
    Feb 27 at 12:11















Is there anything interesting in journalctl -xb?
– Jos
Feb 27 at 12:11




Is there anything interesting in journalctl -xb?
– Jos
Feb 27 at 12:11










1 Answer
1






active

oldest

votes

















up vote
0
down vote













Usually one of your file systems is faulty and needs check,
a good practice before anything is to check all your file systems:



sudo fsck -y /dev/sda2



sudo fsck -y /dev/sda3



...



and so on.






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: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2faskubuntu.com%2fquestions%2f1010249%2fcannot-get-past-emergency-mode-ubuntu-17-10%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













    Usually one of your file systems is faulty and needs check,
    a good practice before anything is to check all your file systems:



    sudo fsck -y /dev/sda2



    sudo fsck -y /dev/sda3



    ...



    and so on.






    share|improve this answer
























      up vote
      0
      down vote













      Usually one of your file systems is faulty and needs check,
      a good practice before anything is to check all your file systems:



      sudo fsck -y /dev/sda2



      sudo fsck -y /dev/sda3



      ...



      and so on.






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        Usually one of your file systems is faulty and needs check,
        a good practice before anything is to check all your file systems:



        sudo fsck -y /dev/sda2



        sudo fsck -y /dev/sda3



        ...



        and so on.






        share|improve this answer












        Usually one of your file systems is faulty and needs check,
        a good practice before anything is to check all your file systems:



        sudo fsck -y /dev/sda2



        sudo fsck -y /dev/sda3



        ...



        and so on.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Sep 8 at 6:04









        Mohammad Kanan

        1418




        1418



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1010249%2fcannot-get-past-emergency-mode-ubuntu-17-10%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            Which professions warranted travel in Medieval times?

            How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

            Trouble downloading packages list due to a “Hash sum mismatch” error