Climbs initramfs when booting Ubuntu

the initramfs file system of memory that is used for the initial launch of operating systems based on Linux kernel. When installing the OS, all libraries, utilities, and configuration files are compressed into an archive before being transmitted to the specified file system in the boot, where, and continues the system startup. Sometimes users of Ubuntu face the fact that when you turn on the computer they go into the management console of this FS without the possibility of further boot the system. This is due to damage to the flow of the run and recovered fairly simple method.

Fixed error with loading in initramfs when run Ubuntu

In most cases the problem is associated with a failure in one of the superblocks, and when you try to exit the initramfs using the command exit you receive the following message:

exit /dev/mapper/ubuntu--vg-root contains a file system with errors, check forced. Inodes that were part of a corrupted orphan linked list found. /dev/mapper/ubuntu-vg-root: UNEXPECTED INCONSISTENCY; Run fsck MANUALLY. (ie without-a or -p options) fsck exited with status code 4. The root file system on /dev/mapper/ubuntu--vg-root requires manual fsck.

In the event of such a situation, the best method of correcting the problem is the restoration of the superblock, and it can be done in the following way:

  • Download the ISO image with the same Ubuntu version as installed on your computer, from official website and create a bootable USB flash drive. For more information about this procedure you can read in our other article on the following link.
  • Read more: how to create a bootable USB drive with Ubuntu

  • At boot time, select boot from the stick, and when window appears, the installation will enter the live “Try Ubuntu”.
  • Here will display a standard graphical interface. Open the menu and double-click LMB on this icon to launch the app “Terminal”. This is done also by holding the key combination Ctrl + Alt + T.
  • Find out the number of the system partition of the hard disk with system installed by typing the command sudo fdisk-l|grep Linux|grep -Ev 'swap'.
  • In the new row, you will see the designation, e.g. /dev/sda1. Remember it, because in the future it will be required to correct the error.
  • Start enumerating all available superblocks, putting sudo dumpe2fs /dev/sda1 | grep superblock. Each superblock is stored a certain amount of metadata the file system, so failures in their work and provoke the failure of loading the operating system.
  • In the new rows after the activation of the command displays a list of all those present in the section superblocks.
  • Take for example any block, for example, the first. With it will be restored FS. Start this activity after entering sudo fsck-b 32768 /dev/sda1 -y, where 32768 is the number of the superblock, but /dev/sda1 — the partition of hard drive.

    Thanks to the option -y , all changes will be automatically accepted, and upon successful completion of the process the screen will display the following notice:

    fsck 1.40.2 (12-Jul-2007) e2fsck 1.40.2 (12-Jul-2007) /dev/sda1 was not cleanly unmounted, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong for group #241 (32254, counted=32253). Fix? yes Free blocks count wrong for group #362 (32254, counted=32248). Fix? yes Free blocks count wrong for group #368 (32254, counted=27774). Fix? yes .......... /dev/sda1: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda1: 59586/30539776 files (0.6% non-contiguous), 3604682/61059048 blocks

  • It remains to mount the system partition sudo mount /dev/sda1 /mnt.
  • Then navigate to it using cd /mntso all the commands were run directly from the directory itself.
  • View the contents of the filesystem using sudo mkdir test ls-l. Successful execution of this operation, says that the restore was successful and to restart the OS.
  • Sometimes even after successful remediation are considered problem users encounter errors when you start the operating system. Most often they are associated with the breakdown of the standard GRUB boot loader. So have to recover and this standard component. A detailed guide on how to perform the task using Boot-Repair, check for a material on.

    Upon completion of all procedures the flash drive with the Ubuntu LiveCD, you no longer need. If you have any desire to format it and use for their own purposes, take a look at our separate article on the execution of the operation.

    Today we tell about the most popular solution to the problem, booting into initramfs, but that does not mean that the method is universal. In the event of an error, another character describe it in the comments and we will try to provide the correct solution to this situation.

    Source: lumpics.ru

    (Visited 6 times, 1 visits today)