{ 165 Intelligent Comments }

Initramfs Prompt When Ubuntu Boots

Ubuntu Linux LogoInitramfs Prompt Boot Problems

Ubuntu boots to a black screen with a (initramfs) prompt.


  • After selecting to boot into Ubuntu from your boot menu, the boot process halts at a black screen.
  • You are presented with only a prompt (initramfs)
  • You are presented with the BusyBox message
  • You have installed Ubuntu on an NTFS partition dual booting with Microsoft Windows


This can occur when you have installed Ubuntu on an NTFS Windows partition and Windows was incorrectly shutdown.


Step 1 – Run CHKDSK and Gracefully Shutdown Windows

  1. Restart your computer into Windows
  2. Open a CMD prompt and type:

    chkdsk c: /f

    Note: You may get a message that windows needs to schedule the chkdsk the next time the computer starts. Accept this frustrating reality and reboot.

  3. After the chkdsk has successfully completed, shutdown windows gracefully using the Start > Shutdown method
  4. When rebooting choose to go into Ubuntu from your startup menu. If you still land a the balck screen then co to Step 2 below.

Step 2 – Forcibly Mount The Ubuntu Volume

  1. If you are only booting to a prompt and can’t get any further and following Solution 1 above did not resolve the issue then you will need to forcibly mount the NTFS volume. This can be dangerous but is the only other way out of this problem as far as I know. Feel free to comment below if you know otherwise.
  2. At the (initranfs) prompt issue the following command:

    mount -t ntfs-3g /dev/sda1 /root -o force


The mount command may be different for you.

To find out your exact command reboot, select Ubuntu and press Esc when you see the countdown.

Choose to enter in recovery mode.

You will be presented with the same prompt but there will be a whole lot of other lines of text.

You should be able to spot your mount command in there.


Wow, 165 Comments! We've got a conversation going now. Join the discussion below!

  1. Linnie says:

    Thanks!!! That really helped 🙂

    1. Googly Googly says:

      Try this. It works every time for me on Ubuntu 16.04


      You may get something like this —

      /dev/sda1: Unexpected …
      fsck exited ….
      The root filesystem on /dev/sda1 requires manual fsck

      BusyBox v1.22 ……


      … means etc etc.

      Now use the following command

      (initramfs)fsck /dev/sda1

      (pl note that /dev/ is constant. sda1 is to be known from the line above — The root filesystem on /dev/sda1 requires manual fsck)

      If it works for any one don’t forget to tell that it works

      1. Helal says:

        fsck /dev/sda1 worked for me , thanks

      2. Anonymous says:

        it worked for me

      3. Mary says:

        It worked for me, thanks 🙂 I’m a novel in linux os

      4. A says:

        fsck /dev/sda1 works for me. Thank you!

      5. Mgu says:

        Thank you bro, worked for Ubuntu 16.10

      6. rahul yadav says:

        It’s really works 4r my ellimentry os


      7. shajan says:

        Thanks very much !
        fsck /dev/sda2 worked for me.

      8. PrinceB says:

        it worked for me… thanks for the help

      9. Pradeep says:

        Yeah man….. It worked for me luv u……

      10. mint 18 user says:

        It worked for me to fix it with fsck /dev/sda1

      11. Manoj Kumar Singh says:

        fsck dev/sda5 Worked in my case

      12. thanks says:

        worked for me!!! so simple

      13. Amir Pacolli says:

        worked for me

      14. raj says:

        fsck /dev/sda2 worked for me..thnx

        1. Anonymous says:

          It worked thanks.

      15. Bhaskaran says:

        Thanks I got back which I lost, I like to add to people here that after fsck you need to leave a space and type /dev for example

        fsck/dev is wrong fsck /dev is correct.

      16. espoir says:

        Works 🙂 thx

      17. Anonymous says:

        Thanks so much! I was confused, kept getting internal errors and froze so I rebooted into that! Thanks!

      18. Melissa says:

        Thank you so much! Worked for Linux Mint Cinammon 18.1

        Running it from recovery I noticed the sda8 file in question had errors so from there I just gave the same commands as you and manually fixed (yes prompt) to each error until it was done. Shut if off after and then restarted from there. Properly booted up with not having to reset everything.

        But I also did the first part of the article for the windows cmd prompt fix as I suspect the error came from improperly shutting off the computer.

      19. Jonathan says:

        The command worked for my Xubuntu computer. Thank you very much, Googly Googly!

        1. Reva says:

          Hlo..i want help

      20. Anonymous says:

        Worked. Thanks!

      21. PLogic says:

        Simple, elegant and successful, but warn folks about all the “Yes” answers they may encounter and then instruct them to reboot.

        Many thanks.

      22. linuxnewfag says:

        This worked for me. It’s an error I’ve come across lately. I know I seen the command before but it had an extra command to answer all the questions that came after it as yes automatically. I’d like to say that command is (after you exit) fsck /dev/sda1 -y . I would’ve tested it, but I fixed it and have to wait to test out this theory. Could anyone shed light on this? I got a feeling this is one of those go to commands one should know when working with linux as I’ve gotten this error 3 times so far on same computer. Thanks anyways! (Linux mInt)

      23. Akash says:

        Thanks I got. It’s working fine

      24. Manan says:

        This worked thanks

      25. Thanks a lot!
        fcsk /dev/sda4 worked for me.
        I’m using dual boot with Windows 7 and Linux Mint.

      26. Akash says:

        It worked thanks:D:D

      27. Anonymous says:

        it worked.

      28. Hellow says:

        Awesome !

        It works perfectly.

      29. Anonymous says:

        It goes in a infinite loop…., !

      30. selvam says:

        Due to power shutdown this happened for me and the above fsck worked for me perfectly.Thanks

      31. Chuckufarley says:

        This worked for me. Thanks a million.

      32. fsck /dev/sda2 worked for me. Thank you very much!

      33. Sheldon says:

        Worked for me too

      34. Sheldon says:

        fsck /dev/sda1 Worked for me too

      35. RASH says:

        Thanks dude that really helped!!! <3

      36. ashu says:

        thnxxx…. it worked

      37. Sheldon says:

        Fsck/dev/sda1 worked for me too..
        Thanks much

      38. Anonymous says:

        Thank you!!

      39. sam says:

        Thank you for good job. fsck /dev/sda5 worked for me. But there is space between fsck and /dev

      40. Ben X says:

        The dev/sda1 option worked for me as well, thank you

      41. Jag says:

        Oh my God! It worked! Thanks a lot! Instead of sda1 my computer suggested partition sda10. I have multiple partitions as I am running 3 different variants of GNU/Linux, namely Linux Mint, Linux lite and Elementary OS. Thanks a lot!

      42. Alana says:

        Thanks so much! After I typed that, I said y and y and y. Then I exited, and it worked just fine. My computer went dead as I was booting Mint on my VM. Then that screen wouldn’t go away. Easy fix. You are awesome!

      43. Sou.ya says:

        Not working please try another command

      44. Nakul Mathur says:

        Is it work for Ubuntu 17.04 too?

      45. Raja says:

        I am getting fsck not found

      46. Raja says:

        I am getting fsck not found. Pls help me

      47. Varun says:

        Worked for me. Prompted me to fix filesytem error and I selected “y” for all. Finally did exit again and it worked.

      48. Anonymous says:

        It is work for me

      49. DKAM says:

        Than you very much. it works for me too.

      50. Haris says:

        It has worked for me.
        I am able to login back to Ubuntu.

      51. COAHTR says:

        Totally worked! Thx SO MUCH. Had to do it twice in a row for mine. First time had to answer yes a couple of times then powered-off (forcing shut down). Second time had to answer yes innumerable times then simply typed in command “reboot” right after, restarted naturally, and it worked just fine!

        Back like new. (:

      52. himanshu says:

        yes it works for me.

      53. Anonymous says:

        Wow, thanks so much, Googly Googly!!! This worked like a charm! Much appreciated!!! Happy New Year to you!!!

      54. Anonymous says:

        worked for me thanks

      55. DKAM says:

        Thanks a lot. It works! 😀

      56. William West says:

        I’m a beginner and it worked beautifully! Thanks for saving me from a wipe and reinstall!

      57. rho says:

        thanks ♥

      58. Pash says:


        Oddly enough i tried it so many times from others advice it didnt work, after trying
        your advise i’m astounded it WORKS


      59. Anonymous says:

        sda2 worked for me. Dude thank you very much!

    2. Thanks. it worked says:

      Thanks. it worked

      1. Googly Googly says:

        Wow! I am not computer literate. But, somehow got the solution and posted here. Am so happy to know that it works for many. In fact, I did not open this page for so many months. I encountered the problem again and was searching for solution and came to this page and found that my solution is useful to others. Feeling very happy!

        1. SanD says:

          Today, your solution helped me immensely. I screwed up my system by pressing CTRL-C while “sudo badblocks ” was taking too long. Thanks for posting your solution.

    3. mian waseeq says:

      Thank you bro, it relay works for Ubuntu 16.10

      first just type fsck press enter will show you sda 1/2/3/4/5
      then type shown sda in my case 5
      then reboot

    4. Anonymous says:

      it really worked thanks a lot

    5. Kasj says:

      Thank you ?

    6. PRADEEP B NAIK says:

      IT WORKS FOR ME THANKS.Iused (initramfs)fsck/dev/sda8

    7. jhs1 says:

      worked for me also. don;t know why this keeps happening

  2. Anonymous says:

    Thanks that helped my disk is toast but I was still able to log on and clean up a bit before getting a new one.

  3. Anonymous says:

    wat is supposed to happen after mounting?? I got the (initramfs) prompt again…i rebooted but again got stuck at (initramfs)_

    1. Allan says:

      Yeah what happens after?

  4. Ruksana says:

    This works. Being a newbie to Ubuntu and Windows partitioning, this really helps.


  5. Adnan says:

    ThaNks man this helped me getting in the system, i need to fix it again.

  6. Epsi says:

    Hi there. I have the same issue after having passed DBAN to wipe hardrive. So I don’t have the alternative of going to Windows. There seems to be no partitions either. Any idea on what to do?

    Many thanks

  7. Epsi says:

    Ah, sorry, forgot to mention I am runnimg Ubuntu from CD and as I choose to install it the black screen comes in with the initramfs Prompt Boot issue featured above.

    Not much knowledge of Linux or computers either…

    1. Rosco says:

      Hi there Epsi…I haven’t heard of this happening during the install process…have you completely wiped the drive clean and started fresh?

      Here’s a link to Ubuntu Forums where they were having the same or similar issues. Give it a try.

      Hope this helps


      1. Epsi says:

        Hi there, thanks a lot for that. I read somewhere else that my iso copy of Ubuntu could be corrupted so I made a new copy downloaded from another computer and run it again on the problematic one from the cd unit. It worked!

  8. Swapnil says:

    Hey buddy. I tried the above repair but it was unsuccessful on my Laptop. It shows some commands over there and write at last that there are EVEN MORE commands… and finally, the problem did not got solved. 🙁 is there any other method? I need it back badly!

  9. Anonymous says:

    I have Ubuntu 8.4 work fine but when i tried to install 10.4 or 11.4 it dosn’t work i have this problem (Initramfs) why

  10. toyin says:

    i tried to forcibly mount the NTFS volume this is the message it displayed “mounting /dev/sda1 on /root failed:success
    (initramfs) what do i do next?

  11. mete says:

    ubuntuyu winsowsun içine kurmayın bir başka partitiona kurun

  12. Al W says:

    Im unable to get beyondinitramfs.
    Conical, Ubuntu … Can someone please help. I presume this all happened after an upgrade to Ubuntu

    Please help. I’ve been down for quite some time- only have iPhone to check things out and even to write this plea.

    1. Santanu says:

      I get this frequently and I just press Crtl-Alt-Del to reboot. It runs fine second time. I am booting from a pen-drive.

  13. Angel Genchev says:

    This solution is not complete.
    When You fix problems, assemble raid arrays, etc and mount the /root, the boot process must be resumed. BUT nobody said how ?
    I tried to re-run it by typing “/init 3”, but this fails since the init in ubuntu requires /com/ubuntu/upstart socket.
    Another script has to be run.

  14. Angel Genchev says:

    1. At GRUB Menu Choose to enter in recovery mode.
    2. At iniramfs mount the root filesystem in /root
    3. type “exit”
    4. At the prompt resume booting (or so) choose to resume. The system will come up. Mine initialized at a strange graphics mode.

  15. Alan Peart says:

    I just wanted to add my non-expert voice here. I tried most of the solutions people had offered in this thread, without success. What finally worked for me was pressing ESC in the 5 seconds for the extra boot options, then choosing “ACPI Workarounds”. The installation proceeded without any further problems. Don’t ask me why.

    1. dent says:

      That worked for me. From one non-expert to another, I thank you.

    2. Sexybomber says:

      i was trying to dual boot ylfm os 3.0, frist i tried using the usb,, after going through the installationn procedures,, it says ” no root defined” i tried and read everything online for 3 days without sleeping trying to find solution to the rooting issue,, all failed,i read the jargons but where to type those commands i dont even know,,i used wubi to install to c driver NTFS format,, everything was installed .,,, time to boot,, only initramfs,, i press escape and tried all other options all initramfs,, what a hell on earth is this so called initramfs and no one can solve it? it’s time to quit obuntu and linx and conerntrate on windows,, all these shits are never found with windows,, meaning MSI is the chief divinity in IT,,all others are nothing but shit

  16. Sexybomber says:

    In fact, about 98% of all i have been reading in forums are senseless and so selfish,, why? 99.9% of contributors are weired,,why? someone is new to obuntu or linux or windows: meaning the person is technically naive,, he lacks the knowledge of every technical terms etc such kernel, bash,, mount etc,,, how can people just come in and say.. mount/………. where do we mount those things or characters? in word doc or pdf or txt files? please be a bit educational and start your explanaition very carefully and seriously,, do not bamboozle people with all the aristocratic jargons,, no one understands.. initrafms,, what is it? set command and mount/… at where? use pen and paper to mount or where? ohh shit

  17. Priya says:

    I had the same problem and I tries step2 after which I get

    Mount is denied because the NTFS volume is already exclusively opened.The volume may be already mounted, or another software may use it which could be identified for example by the help of the ‘fuser’ command.
    mount: mounting /dev/sda1 on /root failed:No such device

    How do I solve this?

  18. Priya says:

    I had the same problem and I tried step2 after which I get

    Mount is denied because the NTFS volume is already exclusively opened.The volume may be already mounted, or another software may use it which could be identified for example by the help of the ‘fuser’ command.
    mount: mounting /dev/sda1 on /root failed:No such device

    How do I solve this?

  19. Kat says:

    Almost same issu occured me, when I wanted to try Ubuntu LiveUSB.
    Some people in forums say, that make sudo that and this, but the sudo command isnt working in intframs.

    please help

  20. haynal says:

    I just want to say thank you, in my case with Initramfs Prompt your first step has already helped. I let run the windows tool chkdsk over the ubuntu partition and after a new start ubuntu was there! I am very happy. Bevor that I was reading in a forum 42 pages with the most complicated “solutions”, but they could not help, as I am a newbee in linux. (My English is also not the best 🙂 Many-many thanks! It is really great!

  21. Angela says:

    Thanks for posting, step 1 worked for me. Appreciated. Cheers.

  22. Angela says:

    I’d just like to mention too, that if users are removing the dvd when the drawer opens, after installing, you’ll return to black screen every time. Rather than follow the urge to remove the dvd (thinking ubuntu will install/run without it after it spits out) just push the drawer back in, THEN do the step 1. I still have a little confusion; I thought I’d be installing everything onto hard disk and only using dvd very rarely to repair. Maybe I downloaded the wrong version? (Dear Kat, I think ‘sudo’ work in ‘terminal’, not (initramfs).

  23. Asger says:

    The chkdsk solution worked like a charm for me, thank you so very much!

  24. Abhishek says:

    This happened to me too, but I am on chrome OS. Any help?

  25. Abhishek says:

    when I say chrome OS, I mean a chrome book with both chrome OS and linux 14.04

  26. Anonymous says:

    Didn’t work, after completing step 1 Ubuntu boots to gnu grub… O.o wat?

    1. Abhishek says:

      I actually found something else that works. I booted into GRUB by holding down shift while booting. Then I booted into an older kernel that worked just fine. I opened terminal and ran the command “sudo apt-get dist-update” (it might have been dist-upgrade). After re-booting the newer kernel worked just fine. dist update aparently corrects any inconsistencies with the UUID’s.

  27. Lazaros says:

    Ubuntu is the only OS in my old Acer, stuck at initramfs, won’t boot from a live CD nor live alternate CD and cannot afford a new laptop. I need help or a brave donation 🙂

  28. Ruben says:

    Excellent. It worked exactly as told.

  29. Ruben says:

    Well, it worked once. This morning I booted and again the same issue.
    After listing Boot args show Missing modules and right after and ALERT! /dev/disk/by-uuid/96a7daf9-a19d-475e-a441-14dec558428b does not exist. Dropping to a shell!
    BusyBox v1.21.1 (Ubuntu 1;1.21.0-1ubuntu1) built-in shell (ash)
    How do I solve it before making it worst.
    I tried Abhishek option and I got just the logo and went back to what I wrote above.

  30. Thomas Naser says:

    The only real solution is rm -rf / and install Windows.
    To developers: quit scratching your own itch, buy some benedryl and just fix whats already there. wirelss is a pain in the ass for newbies to set up and bluetooth forget it. I tried a number of different Distros, both Debian and Redhat based and none of them let me out of the box, get bluetooth to work, in some cases, but not all, wireless wasnt such a problem.. In this day and age Broadcom chips are the standard in 95% of the commonly available laptops. And no I can’t afford the Linux tax on the “Open Source” systems, $500 US for a system with Windows for <$300 no way – Mama didn't raise no idiot.

    Return to Windows, at least there it works.

  31. Anonymous says:

    It really helped after the 1st solution

  32. Oo says:

    Yup, reading this thread leaves no doubt in my mind that 2016 is definitely going to be the year of the Linux desktop.

  33. SuXiaoheng says:

    Thanks very much. Your solution helps a lot. Appreciate sincerely.

  34. SuXiaoheng says:

    Thanks very much. Your solution solve my problem perfectly.

  35. Sreeraj says:

    Thanks first step itself allowed to get me out from the problem

  36. ITwurx says:

    I struggled for most of the morning with this. The thing that worked for me was to run the chkdsk in Windows, close, reboot to Ubuntu and reinsert the disk. I took it out when Windows ejected it during the initial install. I wish I would have run the chkdsk earlier – I think that was the problem. I performed unhealthy shutdowns multiple times out of frustration. Thank you to everyone that left feedback. Together, we are strong!

  37. […] tried the method described here, and after the final command mount -t ntfs-3g /dev/sda1 /root -o force it does nothing and gives me […]

  38. lankesh says:

    thank u so much dude

  39. Zoyrah says:

    What if it says “Permission denied” after entering the “/dev/sda1 /root -o force”? Thank you!

  40. fighcell says:

    This helped me a lot. The step 2 worked for me. I am running Ubuntu 16.04 on an ESXi Machine and got the initramfs prompt. Thanks a lot.

  41. Pawan Sasane says:

    Thanks buddy, it works for me. I am working in software company, when I was working on some really important stuff today, suddenly this issue was faced. But as per ur guidelines to enter ‘fsck /dev/sda1’ ..it works…. thank you so much… keep smiling 😉

  42. if you are getting initramfs error, use this command to resolve the issue.

    mount /dev/sda*
    fsck /dev/sda1 -f and it will ask for fix the error type y evry time…
    after that it will be come back initramfs> reboot
    (type reboot) system will reboot and work fine.

    1. mrray says:

      Hello everybody,
      GReetings !
      Mr Raj Singh, Very thank you for posting the solution.actually what you have suggested has worked for me.

  43. Ambi says:

    (initramfs)fsck /dev/sda1

    works for me thanks…..

  44. sunita says:

    in case of usb boot just remove/insert pendrive while loading.
    crazy but this works for me.

  45. Ubuntu003 says:

    Hey please someone can help me ? They ask at the end ” permission denied ” what i supposed to write ?

  46. dell says:

    I have no idea how this initramfs thing happened to my laptop, but your solution was the cure. Very grateful and much obliged. 🙂

  47. mementomori says:

    yes it worked for me on mint 18..tnx!! i had a very different line fsck/dev/mapper/mint

  48. marcel says:

    juste vous dire un grand Merci,grâce a vous j’ai pu redémarrer mon PC, car sa fessai 24h que je cherché une solution son pour autant trouvé, jusqu’à ou je tombe sur votre réponse aussi simple que de dire bonjour,mes fallait trouvé, Merci,encore, cordialement.

  49. Tony T says:

    None of these fixes worked for me.

    I found something online. If you hit esc during the boot cycle, then F6 and delete the quiet splash boot option, and add break debug, then continue with the install, once it freezes, you can pull the USB and put it back in, and BOOM, the GUI installer starts back up. Odd, but it fixes it

    (I was doing full install via USB when I encountered this issue)

  50. Darius says:

    Hi there. I have the same problem (initramfs boot) but the command fsck is not found when i type (fsck /dev/sda1). Please help me

  51. Anonymous says:

    Thank you man it worked ! You daved the day

  52. Prax Brax says:

    I’m using Linux Mint 17.3 and the fsck /dev/sda2 … worked like a charm. So grateful guys and happy Easter holidays.

  53. Casper says:

    The last step worked perfectly for me with the:

    fsck /dev/sdb1

    I’m booting up from a usb thumdrive with mint 18.1 and I think that the bios settings on the work laptop is killing the startsequence in Mint, even though it is on its own separate disk.

  54. Dick says:

    Hell yeah dude !!!!

  55. Jugal Dumka says:

    Thanks it works for me

  56. Vince says:

    awesome bro…you’re my hero

  57. guest says:

    thank you, it worked for me!

  58. numbheart says:

    Thanks a lot. It helps!


    1. Jonathan B says:

      If Anyone has Ubuntu and you are getting
      BusyBox v1.22.1
      Do the following.
      1. Type exit —> (Initramfs) exit
      2. wait until finished
      3. After it is finished at the very top Look for something that says


      This part is tricky. Depending on what you’re specific terminal says, copy the whole thing for example mine had


      4. Before you copy. What I had to type for my specific problem was write onto the (initramfs)
      “fsck /dev/mapper/ubuntu–v6/”
      DO NOT COPY mine because it will not work.
      5. reboot

  59. Anonymous says:

    it didn’t work for me. it says mount a filesystem

  60. Ubuntu user says:

    Thanks fcsk /dev/sda5 worked for me.

  61. Sow says:

    Haha thanks ! fsck /dev/sda5 work for me ! Googly !!!

  62. Anonymous says:

    Man you are awesome, it’s work with me but instead with 6

  63. Valdo says:

    It works for me in ubuntu 16.04. Thank.

  64. lflem001 says:

    Works for mint 18.2 mate. Saved me a full system rebuild.

  65. Kellu says:

    It works (fsck /dev/sda1)! Thank you so much.

  66. Walter says:

    I’ve used the basic fix many times, and it does work. But the Initramfs error has been happening for a long time and seems to get worse (takes longer) each time. I just went through numerous read errors, rewrites, wrong counts, etc. If this is a systemic error, why has it been so long in correction? is it being worked on for future releases? Should version 16.04 be dumped?

    If this is not an Ubuntu system error, is it indicative of a dying hard drive and is its replacement advised?

  67. Vaisakh G says:

    fsck /dev/sda1 will work fine to clean the disk errors.

  68. Rajesh Pal says:

    yeah , great command, solved ….thanks

  69. Anonymous says:

    fsck /dev/sda5 worked for me. Thank you

  70. Anonymous says:

    fsck /dev/sda1 worked for me , thank you só much

  71. PLogic says:

    As many others have found. The error recurs regularly and seems to take longer to fix each time. I suspect it is indicative of a dying hard drive. I’ve been waiting for a new stable version of Ubuntu before replacing the drive and OS with a fresh instal. Others have cited Ubuntu 17.10 as problematic and suggested waiting for 18.04. But I may be resigned to doing it twice.

  72. PLogic says:

    BTW this is happening on a hitherto bulletproof Ubuntu 16.04 PC with no Windows OS onboard. Though, I have other dual-boot machines, this is not one, so I’m not sure that the NTFS comment applies.

  73. manu says:

    fsck /dev/sda1 worked for me too.thank you very much. Adipoli.

  74. mihretu says:

    fsck /dev/sda1
    after the process completed I make force restart ..
    thanks it worked for me

  75. Trilok says:

    It worked for me. Thanks a lot

  76. Marcel Cools says:

    fsk /dev/sdax (multiboot) worked fine!

  77. alindi says:

    fsck /dev/sda6 worked for me after a couple of y/n queries then i rebooted and it was okay.

    1. djoko chris says:

      me too

  78. Viktor says:

    I am trying to get Elementary OS running on my HP Elite X2 1012. The system start ends with BusyBox initramfs prompt. Unfortunately, the solutions described here don’t work for me because I don’t see any /dev/sda* neither /dev/mapper/* items. Before installing Elementary OS I was using Ubuntu 17.04 on the same PC without any issues. Does anybody have any idea what else could resolve the issue?

  79. Ranga says:

    fsck /dev/sdb6

    worked for me nicely

  80. fsck /dev/sda6 worked for me. Thanks! Very helpful.

  81. Jean says:

    Thanks very much!! it works for me too.

  82. Anonymous says:

    Thanks it works for me

Leave a Reply