How to Inspect and Rebuild the Initial RAM Filesystem in Ubuntu Using update-initramfs and lsinitramfs

During the Linux boot sequence, the kernel requires essential storage controller drivers, filesystem modules (such as ext4, Btrfs, or ZFS), and cryptographic engines before the true root filesystem (/) can be mounted. Because these drivers cannot be loaded from an unmounted disk, the system boots using an initial RAM filesystem\u2014an in-memory archive known as the initramfs. In Ubuntu, the creation, inspection, and regeneration of this critical boot archive is orchestrated by initramfs-tools, primarily through the update-initramfs and lsinitramfs command-line utilities.

Understanding the Role of the initramfs in Ubuntu

When the GRUB bootloader loads the Ubuntu Linux kernel (vmlinuz), it simultaneously loads the corresponding initrd.img file into physical RAM. The kernel unpacks this archive into a temporary root filesystem (ramfs), launches an early userspace initialization script (/init), loads required kernel modules (such as NVMe, AHCI, RAID, or LUKS decryption drivers), resolves device UUIDs, and mounts the real physical disk partition. Once mounted, pivot_root or switch_root transfers execution to systemd on the permanent disk.

If the initramfs is corrupted, out of synchronisation with newly installed hardware drivers, or missing required storage modules, the system halts during boot with a kernel panic or drops into an emergency (initramfs) BusyBox shell.

Inspecting Existing initramfs Contents with lsinitramfs

Before making changes or following kernel updates, inspect what files, binaries, and kernel modules (.ko files) are packaged inside your current boot archive. The lsinitramfs tool decompresses and lists contents without altering disk state:

lsinitramfs /boot/initrd.img-$(uname -r) | head -n 30

To verify whether a specific kernel driver\u2014such as an NVMe storage driver, network driver, or graphics module\u2014is bundled inside your active boot image, filter the output with grep:

lsinitramfs /boot/initrd.img-$(uname -r) | grep -E "nvme|ext4|btrfs"

You can also inspect early configuration scripts bundled inside the archive:

lsinitramfs /boot/initrd.img-$(uname -r) | grep "scripts/"

Configuring initramfs-tools Modules and Hooks

The configuration governing which modules are packaged during archive creation resides in /etc/initramfs-tools/:

• /etc/initramfs-tools/initramfs.conf: Core configuration controlling RAM compression algorithm (zstd, gzip, lz4), boot modes, and module inclusion policy (MODULES=most vs MODULES=dep).
• /etc/initramfs-tools/modules: A plain text list of explicit kernel module names that must be forcefully included into the boot archive.
• /etc/initramfs-tools/conf.d/: Modular configuration overrides (e.g., resume swap partition configuration).

For example, if you need to ensure that a hardware driver (such as r8169 or a RAID controller driver) is forcefully included in early boot:

echo "r8169" | sudo tee -a /etc/initramfs-tools/modules

Updating the initramfs for the Running Kernel

To rebuild the boot archive for your currently active Linux kernel after modifying driver settings, blacklists, or filesystem configuration:

sudo update-initramfs -u -v

The parameters operate as follows:

• -u: Specifies update mode, modifying the existing image rather than generating an entirely new kernel version pair.
• -v: Enables verbose output, displaying each script, binary, and kernel module as it is collected and compressed into the archive.

During execution, update-initramfs validates available storage in /boot, executes hooks from /etc/initramfs-tools/hooks/, and creates a backup of the previous image before atomically replacing /boot/initrd.img-<kernel-version>.

Regenerating initramfs for All Installed Kernels

When performing large-scale driver maintenance or recovering from kernel update inconsistencies, you can regenerate initramfs images across every kernel installed on your Ubuntu machine simultaneously:

sudo update-initramfs -u -k all

The -k all switch instructs the utility to iterate through all kernel versions found in /lib/modules/ and recompile corresponding images under /boot.

Creating a New initramfs for a Specific Kernel Version

If you compiled a custom kernel or need to manually create an initial ramdisk for a specific kernel version that lacks an image:

sudo update-initramfs -c -k 6.8.0-48-generic

Here, the -c switch creates a new file, and -k explicitly defines the target kernel version string.

Tuning Compression for Faster Boot Times

By default, modern Ubuntu versions use zstd compression for the initramfs to strike a balance between file size and decompression speed. To check or customize the compression algorithm, inspect /etc/initramfs-tools/initramfs.conf:

grep "COMPRESS=" /etc/initramfs-tools/initramfs.conf

Available algorithms include zstd, lz4, gzip, and xz. For embedded systems or ultra-fast boot requirements where storage footprint is less critical than CPU decompression latency, changing to lz4 decreases boot time by several hundred milliseconds:

sudo sed -i 's/COMPRESS=zstd/COMPRESS=lz4/' /etc/initramfs-tools/initramfs.conf
sudo update-initramfs -u

After rebuilding, verify that the newly generated image resides in /boot with proper permissions:

ls -lh /boot/initrd.img-$(uname -r)