Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Mail Systems
Eclipse Documentation

How To Guides
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Problem Solutions
Privacy Policy




Red Hat Enterprise Linux 9 Essentials Book now available.

Purchase a copy of Red Hat Enterprise Linux 9 (RHEL 9) Essentials

Red Hat Enterprise Linux 9 Essentials Print and eBook (PDF) editions contain 34 chapters and 298 pages

Preview Book

23.5. Verifying the Initial RAM Disk Image

The job of the initial RAM disk image is to preload the block device modules, such as for IDE, SCSI or RAID, so that the root file system, on which those modules normally reside, can then be accessed and mounted. On Red Hat Enterprise Linux 6 systems, whenever a new kernel is installed using either the Yum, PackageKit, or RPM package manager, the Dracut utility is always called by the installation scripts to create an initramfs (initial RAM disk image).
On all architectures other than IBM® eServer™ System i™ (see Section 23.5, “Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i”), you can create an initramfs by running the dracut command. However, you usually don't need to create an initramfs manually: this step is automatically performed if the kernel and its associated packages are installed or upgraded from RPM packages distributed by Red Hat.
You can verify that an initramfs corresponding to your current kernel version exists and is specified correctly in the grub.conf configuration file by following this procedure:
Procedure 23.1. Verifying the Initial RAM Disk Image
  1. As root, list the contents in the /boot/ directory and find the kernel (vmlinuz-<kernel_version> ) and initramfs-<kernel_version> with the latest (most recent) version number:
    Example 23.1. Ensuring that the kernel and initramfs versions match
    ~]# ls /boot/
    config-2.6.32-17.el6.x86_64           lost+found
    config-2.6.32-19.el6.x86_64           symvers-2.6.32-17.el6.x86_64.gz
    config-2.6.32-22.el6.x86_64           symvers-2.6.32-19.el6.x86_64.gz
    efi                                   symvers-2.6.32-22.el6.x86_64.gz
    initramfs-2.6.32-22.el6.x86_64.img    vmlinuz-2.6.32-17.el6.x86_64
    initrd-2.6.32-17.el6.x86_64kdump.img  vmlinuz-2.6.32-19.el6.x86_64
    initrd-2.6.32-19.el6.x86_64kdump.img  vmlinuz-2.6.32-22.el6.x86_64

    • we have three kernels installed (or, more correctly, three kernel files are present in /boot/),
    • the latest kernel is vmlinuz-2.6.32-22.el6.x86_64, and
    • an initramfs file matching our kernel version, initramfs-2.6.32-22.el6.x86_64kdump.img, also exists.

    initrd files in the /boot directory are not the same as initramfs files

    In the /boot/ directory you may find several initrd-<version>kdump.img files. These are special files created by the Kdump mechanism for kernel debugging purposes, are not used to boot the system, and can safely be ignored.
  2. (Optional) If your initramfs-<kernel_version> file does not match the version of the latest kernel in /boot/, or, in certain other situations, you may need to generate an initramfs file with the Dracut utility. Simply invoking dracut as root without options causes it to generate an initramfs file in the /boot/ directory for the latest kernel present in that directory:
    ~]# dracut
    You must use the --force option if you want dracut to overwrite an existing initramfs (for example, if your initramfs has become corrupt). Otherwise dracut will refuse to overwrite the existing initramfs file:
    ~]# dracut
    Will not override existing initramfs (/boot/initramfs-2.6.32-22.el6.x86_64.img) without --force
    You can create an initramfs in the current directory by calling dracut <initramfs_name> <kernel_version>:
    ~]# dracut "initramfs-$(uname -r).img" $(uname -r)
    If you need to specify specific kernel modules to be preloaded, add the names of those modules (minus any file name suffixes such as .ko) inside the parentheses of the add_dracutmodules="<module> [<more_modules>]" directive of the /etc/dracut.conf configuration file. You can list the file contents of an initramfs image file created by dracut by using the lsinitrd <initramfs_file> command:
    ~]# lsinitrd initramfs-2.6.32-22.el6.x86_64.img
    drwxr-xr-x  23 root     root            0 May  3 22:34 .
    drwxr-xr-x   2 root     root            0 May  3 22:33 proc
    -rwxr-xr-x   1 root     root         7575 Mar 25 19:53 init
    drwxr-xr-x   7 root     root            0 May  3 22:34 etc
    drwxr-xr-x   2 root     root            0 May  3 22:34 etc/modprobe.d
    [output truncated]
    Refer to man dracut and man dracut.conf for more information on options and usage.
  3. Examine the grub.conf configuration file in the /boot/grub/ directory to ensure that an initrd initramfs-<kernel_version>.img exists for the kernel version you are booting. Refer to Section 23.6, “Verifying the Boot Loader” for more information.

Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i

On IBM eSeries System i machines, the initial RAM disk and kernel files are combined into a single file, which is created with the addRamDisk command. This step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by Red Hat; thus, it does not need to be executed manually. To verify that it was created, use the command ls -l /boot/ to make sure the /boot/vmlinitrd-<kernel_version> file already exists (the <kernel_version> should match the version of the kernel just installed).

  Published under the terms of the Creative Commons License Design by Interspire