Fix boot issue on Ubuntu and Linux Mint (Initramfs)

tuxterminal_icon

Hello everyone, this time I want to share how to solve the boot problem called Initramfs, I imagine that some have happened and even this time I got the error.

Searching the web on various pages I was finally able to gather information and after that I tried the simple solution and it was a success.

To start we follow these steps:

We insert our Live CD (Let's not forget to configure the BIOS to boot from the CD.) We open a terminal and write:

sudo fdisk -l

We give Enter and it will give us the name of the device with which your PC starts. example:

Disk / dev / sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors / track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: ********** Device Boot Start End Blocks Id System / dev / sda1 * 1 30238 242886703+ 83 Linux / dev / sda2 30239 30401 1309297+ 5 Extended / dev / sda5 30239 30401 1309266 82 Linux swap / Solaris

We write the following again in our terminal and give Enter:

sudo fsck /dev/sda1

We wait for you to repair the partition. At the end we restart and ready it should start normal.


Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   elav said

    Usually this happens when the partition (some or all of them) have inconsistencies. When you run that command it will constantly ask us if we want to repair. To make it automatic we execute:

    # fsck /dev/sda1 -y

    It would also be highly recommended to use this tool depending on the partition, that is:

    # fsck.ext4 /dev/sda1 -y

    Changing ext4 for the type of partition that we want to repair.

    1.    Pablo said

      That's right ... VERY good contribution

      1.    gecoxx said

        Thanks for the post and the comments.

  2.   solidus said

    elav complemented the news very well, thanks for the information. personally in mint I came out 1 time just at the beginning as described but alone I began to recover and start, why? who knows but it was the same case described. thanks greetings.

  3.   ozkar said

    Speaking of Mint, on Saturday I helped a friend install Mint, and wow, after months of using Fedora it is very refreshing to see such a comfortable and intuitive installer ...

  4.   Francisco Gomez said

    One does not have to be fixing this kind of thing, Ubuntu and mint are supposed to be distros for basic users.

    1.    cuervo291286 said

      That's how Francisco is but it doesn't hurt to learn something new and put it into practice.

      regards

  5.   albert said

    Hi!
    After a recent reinstallation of ubuntu 12.04.2 it gives me problems to boot (when before it was fine). Sometimes after loading the grub it stays on the black screen, or it stays stuck after the login screen and other times it loads me well. When the first thing happens I go into TTY for a sudo reboot but it doesn't respond, and when I come back there are a lot of error messages. When it hangs after the login screen sometimes AltGr + ImpPant + K or a sudo pkill Xorg from TTY works.

    Until reading your article I believed that the culprit was the rc.local file modified by me so that only the integrated card is activated when booting, just as I had it before reinstalling, working without problems. But now I have doubts, is it possible that a partition with errors causes these failures? I remember that at the beginning of the installation in the Ubuntu installer it put a message that it was deleting conflicting files ...

    What a mess…

    Regards!!

  6.   ever said

    Sorry but I am totally against this type of post that is called being the solution of a generic problem, they incite the reader to not learn by not explaining absolutely (what is the initramfs? What is fsck for? What is an inconsistency in the filesystem?) making it just copy and paste without understanding why and making GNU / Linux look just for nerds.

    Sorry, but the users are really helped by teaching them, not putting one command after another without understanding why they put something.

    regards

    1.    cuervo291286 said

      It is assumed that to solve this problem you should already know what it means, you can not get to copy commands to be copied, the fact that it is published like this is just to give an idea to the solution, but you should already know what is talking.
      There is no need to be explaining every word that is written.

      regards

      1.    ever said

        If the user knew what the fsck is and where the initrd is, he would not need to enter a tutorial that tells him how to pass an fsck.

    2.    sieg84 said

      if that person wants to learn, he / she will just look for what each command is for.

    3.    Dryant said

      I totally agree with your comment.
      Without underestimating the work of the author of the post.

  7.   Mauricio said

    In which version is it that gives that error.

    So far, I have been mint 13 for more than 8 months and have many power outages and I have not run into that error.

    Another thing, will it be for the kernel version ???

    1.    cuervo291286 said

      It can be in any version of Mint or Ubuntu and the problem occurs unexpectedly, but here is the solution.

      regards

  8.   I know nothing said

    Dear Raven291286, I am a computer "nosenada" but I know that Linux is the best thing on the market and I have been convinced of it. The problem is that when these things happen and I need someone to help me repair them, because as I explained to you, I am a computer "nosenada", a typical user, I can't find anyone and that's when I find these super "self-help" forums.
    In short, I found someone to explain what the Live CD was, I downloaded it, I have it. now I can't get the computer to boot from the cd. I imagine it will be because I do not have what you call the BIOS configured to boot from the CD.
    Can someone explain to me how to do that for me, the "nosenada" can repair my computer and make linux start?
    thank you!

    1.    cuervo291286 said

      Ok look to start can you tell me what brand is your pc? And so I can tell you how to enter the BIOS, the keys with which you can enter vary depending on the pc such as "F2, F8, F10, F12, F9 etc" try those, you have to restart the pc and before it returns boot press one of these keys repeatedly and this is how you would enter the BIOS menu.

      1.    S Mariola said

        Thanks Raven and Elav
        The solutions you indicate have worked perfectly

  9.   htc said

    Sorry for the inconvenience…. but when executing the command: sudo fsck / dev / sda1
    I think this….

    fsck from util-linux 2.20.1
    fsck: fsck.ntfs: not found
    fsck: error 2 while executing fsck.ntfs for / dev / sda1

    The truth is I do not know what is the reason why it appears to me ...
    then I try with:
    fsck / dev / sda1 -y

    It appears to me:
    fsck from util-linux 2.20.1
    e2fsck 1.42 (Nov 29, 2011)
    fsck.ext2: permission denied while trying open / dev / sda1
    you most have r / w access to the filesystem or be root

    then I start in root with the command: sudo -i
    I run the command again: fsck / dev / sda1 -y
    and it shows me this:

    fsck from util-linux 2.20.1
    fsck: fsck.ntfs: not found
    fsck: error 2 while executing fsck.ntfs for / dev / sda1

    I try with the command: fsck.ext2 / dev / sda1 -y
    showing this:

    e2fsck 1.42 (Nov 29, 2011)
    fsck.ext2: Superblock invalid, trying backup blocks…
    fsck.ext2: Bad magic number in super-block while trying to open / dev / sda1

    The superblock could not be read or does not describe a correct ext2
    filesystem. If the divice go valid and go really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock:
    e2fsk -b 8193

    So what should I do?
    is ubuntu-12.04.4-desktop-i386
    first of all, Thanks!

    1.    Santiago! said

      THE SAME HAPPENS TO ME BUT IN SPANISH !! I would like to know how to fix it ubuntu 12.04 lts

    2.    Richard Warlike said

      Make sure sda1 is not the Windows partition. To do this, the first thing is to restart with a live CD or live USB and only then use the command sudo fdisk -l as it says at the beginning of the post and other steps. Fdisk does not allow you to modify do not repair if it is in use. If I am wrong please correct me.
      regards

  10.   enrique said

    I'm starting to get to know UBUNTU, I'm quite a newbie. But I am quite interested in learning about this operating system. I was about to install it at home, but I got an error in the installation. Could you tell me about a website that explains in more detail about the installation of UBUNTU and what newbies can do when having any type of problems in the attempt. Thanks in advance.

  11.   Aracely said

    Hi. Initramfs tortures me. Is there any possible solution without the bootable CD? Can booting from pendrive be done? If so, how should I prepare it? Thank you

    1.    Anonymous said

      No need to boot from a Live-CD
      Just use the console that appears at startup, it is limited to busybox but it still works only that you do not need sudo permissions

  12.   fabio said

    Hello, your suggestion has helped me, thank you very much. But it fixes itself and does the same again. That is, it does not start. They appear as errors in the blocks when I retrieve it, sometimes I give ignore and sometimes not. But the problem persists. I do not know what to do?

  13.   ectulu said

    Hello the suggestion works. The problem is that over and over you have the same problem. In addition to that now the toolbar and the screen saver disappeared.
    I have put update but nothing, it is not allowed to update and says that it has errors in the packages.
    The operating system you have is linux mint Petra.

  14.   tdjmd said

    Hello, crow ...
    I can't fix my boot problem.

    Please let me know if you can give me a hand with this matter. Better if we use a chat, instant messaging, I say.

    If you can help me, let me know what time is best for you and thus, then I will give you the technical data of the equipment or any other information you require.

    I thank you in advance for the help,

    1.    Christian said

      At the time I also had problems with this screen and it happened to me both in linux mint and elementary, I tried EVERYTHING and nothing worked. In the end I discovered it was my graphics card that was not supported with the drivers that are installed by default. I had to remove it, install a couple of drivers and when I put my graphics back, READY. All good! The strange thing is that this only happened to me with mint and elementary, I have tried ubuntu 14.04 and debian 7 and none of the 2 distro gave me problems other than a small flicker on the screen that disappeared after updating

  15.   WARMIN4TOR said

    It didn't work for me »sudo fdisk -1» I had to write »sudo fdisk -l»

  16.   Suzanne said

    Hello everyone:
    I've tried everything you've told me and it doesn't do anything you say it should do.
    I'm a bit lost.
    In my case I get this message:
    mount: mounting / dev / disk / by-uuid / 709569c0-ffc8-414e-8337-e55dd68665a1 on / root failed: Invalid argument
    mount: mounting / dev on / root / dev failed: no such file or directory
    mount: mounting / sys on / root / sysfailed: no such file or directory
    mount: mounting / proc on / root / proc failed: no such file or directory
    Target file system doesn´t have resquested / sbin / unit.
    No init found. Try passing init = bootarg

    Busybox v1.18.5 (ubuntu 1: 1.18.5-1ubuntu4.1) built-in shell (ash)
    Enter »help» for a list of built-in commands
    (initramfs) -
    I ask you please, if anyone has any idea how to solve it, tell me step by step.
    Thank you

    1.    Manuel Ulloa said

      sorry, I think I reposted a similar problem below,…. I am in the same

  17.   wolfgang rodriguez said

    Good afternoon, when performing these steps, no data is lost about what I have stored there. I am new to debian and have some valuable information on my pc. and I got the initramfs error.

    Waiting for your prompt response.

  18.   DOES said

    I have a desktop computer with Ubuntu 10.04. After power installation error error message shows a box with Details and then OK. The cursor is an X. I accept and the screen is black. What do I have to do to get it started? I have no cd or internet, but it is time to change the machine. How can I retrieve some of the information? Could it be that I would enter a command screen with Ctrl + Alt + F1? Thanks for your help!

  19.   Alfonso Jimenez Mohedano said

    It worked for me by changing the configuration option for the SATA drives in the BIOS.
    I put it from IDE to AHCI and voila !!

    Health @ s

  20.   Ramon said

    Thanks it worked for me only with the first part, thanks for the help. : *

  21.   ature said

    Hello, I would like to know if doing this that indicates the files are deleted ... and if this is how I can recover them before reinstalling the system, thanks in advance

  22.   rimdgard said

    Hello, I have a problem that I do not know if it has to do with the current issue, my netbook, it is ubuntu and everything was fine until it was being updated to version 15 if I remember correctly, the issue is that I stopped updating the system and left home, when the battery arrived it was dead, that is, apparently it did not finish updating and it was left halfway, how can I make it start?

  23.   Luis said

    What happens is that I installed ubuntu and I had windows 8 I deleted windows 8 and ubuntu and I wanted to install windows 8 again but it asked me to have 500 GB of memory so I formatted my hard disk and restarted my pc but when I entered four options appeared 1 ubuntu 2 advanced options for ubuntu 3 memory test (memtest86 +) 4 memory test (memtest86 +, serial console 115200) and when I put it in ubuntu it does not enter and it gets a strange message from imintramf something like that I wanted to know if it can be solved and if not thank you anyway

    1.    compilex said

      For the initframfs you can use this video: https://www.youtube.com/watch?v=91TaW1LCRkM (33 seconds)

      and to install windows 8 again, because the normal procedure is to format the partition where you will install it, or the disk and proceed to install.

      If you want to perform dual-boot, to start windows / ubuntu, there is a problem that now new computers do not allow installing linux distributions, due to the UEFI boot mode, in my case I have to disable that option and use linux, if I want to use windows I activate it again.

      1.    Luis said

        But what happens is that I am not allowed to enter only ubuntu appears and it starts to load but then it starts the initramsf and I cannot enter or anything because when I turned it on it appeared ubuntu and asked me for the password and well now nothing appears to me, only appears charging and does not enter as it could be

  24.   Wrincon said

    Thanks for the help

  25.   leonardo stolen said

    good night my brother's canaima does not start and I am following the steps but when I do the command sudo fsck / dev / sda2 I get

    the superblock could not be read or does not describe a correct ext2
    filesiten. if the device is valid and it really contains an ext2
    filesiste (and not swap or ufs go someting else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblck:
    e2fsck -b 8193

  26.   Simo said

    Hi, I live in Venezuela and this problem occurred in a Canaima device. I don't have a live cd or a usb with the data, will there be a way to fix it

    regards

  27.   Sam said

    Thank you very much, it definitely saved my day, thanks for sharing the information it served me with Kubuntu 15

  28.   Christian said

    Thank you very much crow the first time it occurred to me I have installed ubuntu 15.04 currently and I solve it as you said with the boot disk! - Cheers

  29.   BuB0 said

    In Ubuntu 16.04 I managed to fix it by booting Ubuntu in advanced options choosing the recovery option. When it reaches initramfs, it indicates which partition to fsck, which will be the boot partition, so just run:

    fsck / dev / the name you indicate

    And then mark the option "y" to any fix that you request

  30.   possibly said

    Thank you very much it was perfect!

    Does anyone know why this might happen? I have a new hard drive (just bought) and that this has happened to me leaves me wondering.

  31.   Anonymous said

    Thanks a lot! It works perfectly

  32.   Anonymous said

    hello, my problem is that it happens to me in a live disttro and it only loads me busy-box, so these commands do not work for me. and I don't have any linux system to run them on.

  33.   Anonymous said

    No need to boot from a Live-CD
    Just use the console that appears at startup, it is limited to busybox but it still works only that you do not need sudo permissions

  34.   gecoxx said

    Thank you very much for the post!!!
    I turned off the laptop when I was copying files from my / media / Storage partition to a usb and then I was unable to access the partition again. I thought I had to format and lose some data, but no.
    Again, thank you very much

  35.   Gabriella Vargas A. said

    Excellent worked great for me

  36.   Victor Manuel Lopez Collado placeholder image said

    Dear Sirs:
    I've never used Linux, and yesterday I installed Linux Mint, but where the language goes I put Mexico Latinoamerica dvorak. As is logical, when I want to write ... Well, it gives me a series of characters that are very different from what I want to write. How can I solve that? Will I have to format the Hard Drive and reinstall Linux Mint?

    I appreciate your advice and suggestions in advance.

    Victor

  37.   Raul Agullo said

    Thanks for the Post. He got me out of trouble with a live Knoppix CD.
    Congratulations on the work you do.

  38.   andres said

    Thanks .. it worked. My problem appeared when I ripped the partition where my linux deepin was installed. Regarding the explanation of the command, there is a forum full of that information. I think the objective of this publication is to provide the solution. For example I was just looking for the command. Do not waste time looking for what each thing means

  39.   Anuar said

    I do not understand how I am going to enter through live CD and configure the bios to boot the laptop, if I want to, I can get out of the problem I have

  40.   Jack Jack said

    Hi, thanks for the input. I'm having this error on Debian 9. The commands work perfectly for me. But every time I start Windows 7 it throws me a partition error. Then when I start Debian again I get the same initramfs screen and I have to do the same fsck procedure. And it only happens when I start Windows because the rest works fine. Tried reinstalling grub and it has given me the same result. Any solution?

  41.   Andres Choque Lopez said

    The post has misinformation. "Initramfs" is not a bug name, it is a small system that loads together with the kernel into RAM in the first moments of boot.
    If booting stops in initramfs, it is because you have not yet mounted the root (/) filesystem due to some problem.

    1.    Andres Choque Lopez said

      I add because I submitted the comment by mistake before finishing.
      This solution from the post works in case the partition that is mounted in "/" has errors (such as the UNEXPECTED INCONSISTENCY in such partition). There are other causes that boot hangs in initramfs and is not fixed by the fsck command, examples: partition not found; partition to mount was not specified in "/" in boot options (root option =…); he was manually instructed to stop there. And the post suggests that if initramfs exits, then the "solution" for that (without seeing the details of the cause) is sudo fsck…. Why?
      I got here because the link to this post is still being shared to this day, and it worries me (and angers me) when I see these kinds of solutions.

  42.   Eduardo Andrés said

    Thank you, crow291286! Having in my life a little less than a month of experience with the Linux operating system (mine is Mint 19.3), I was presented with this problem that unfortunately I could not find the solution in the official Linux Mint forum in Spanish: where I titled:
    "Several problems presented at the same time, from an update?"
    https://forums.linuxmint.com/viewtopic.php?f=68&t=328817&p=1874309#p1874309

    But this tutorial helped me since it offered some insight into my specific problem (initramfs), only without using "sudo" and from the same terminal? where the problem appeared. I clarify that a couple of pages that were also very useful were also helpful to be sure of what I was going to do:

    https://www.youtube.com/watch?v=I_Nnq9HDQrA (Error starting Linux (initramfs) fixed!)

    https://slimbook.es/tutoriales/linux/315-error-initramfs-como-arreglarlo

    That they are very well.

  43.   John Araujo said

    It is not necessary from the usb or live cd, it can also be from init, and it is not always / dev / sda1

  44.   ramiro said

    my linux lite does not start, it puts some letters that say loading initial ramdisk, how do I remove that and leave it as it was, please help

  45.   Paweł said

    Pomoglo dzięki

    Odpaliłem Linuxa z pendrive bo mam jeszcze z czasu installation z tego nosnika i mogę odpalać jako live usb.

    Use fsck i reboot

    System wstał

  46.   Katarina Jan said

    Chcel by som poďakovať spoločnosti Lapo Micro Finance za poskytnutie pôžičky. Niekoľkokrát som bol oklamaný, keď som sa snažil získať pôžičku, až som narazil na spoločnosť Lapo Micro Finance, ktorá mi poskytla pôžičku v hodnote 23 000 dolárov na starostlivosť or moje choré dieťa. Ak dnes potrebujete skutočného veriteľa, kontaktujte Lapo a nenechajte sa oklamať. Kontaktný e-mail: lapofunding960@gmail.com