If you updated or upgraded your system and didn’t even know anything went wrong until you failed to log in again, there are still ways to get around this.
You’ll find a few different approaches to various error messages, so hopefully something here will be of use to you.
There are three modes of operation create, update or delete. All finding of the root device happens in this early userspace.
update-initramfs: deferring update (trigger activated) Setting up linux-image-4.13.0-31-generic (4.13.0-31.34~16.04.1) ... update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.13.0-31-generic ) points to /boot/initrd.img-4.13.0-31-generic (/boot/initrd.img-4.13.0-31-generic) -- doing nothing at /var/lib /dpkg/info/linux-image-4.13.0-31-generic.postinst line 491.
There are already a bunch of themes available in the repositories, and finding and installing them is as easy as entering “ bar in Synaptic.
But if you install one, it won’t automatically switch to it, and there is no ready way to change between those you’ve added.
The Kernel mounts it as root file system and starts the init process from it.
The Initrd image may be broken or corrupt if the kernel you installed was corrupted or due to some modifications made on the system's kernel or the boot process which in results the system crash :( As we know, "When there is will there is way". In my case I will be showing you with my Ubuntu 13.10 Operating System.