1MKDUMRD(8) System Manager's Manual MKDUMRD(8)
2
6 mkdumprd - creates initial ramdisk images for kdump crash recovery
7
9 mkdumprd [--version] [-v] [-f]
10 [--preload=module] [--omit-scsi-modules]
11 [--omit-raid-modules] [--omit-lvm-modules]
12 [--with=module] [--image-version]
13 [--fstab=fstab] [--nocompress]
14 [--builtin=module] [--nopivot]
15 image kernel-version
16
19 mkdumprd creates an initial ram file system for use in conjunction with
20 the booting of a kernel within the kdump framework for crash recovery.
21 mkdumprds purpose is to create an initial ram filesystem capable of
22 copying the crashed systems vmcore image to a location specified in
23 /etc/kdump.conf
24 Any module options specified in /etc/modprobe.conf are passed to the
26 modules as they are loaded by the initial ramdisk.
27 mkdumprd interrogates the running system to understand what modules
29 need to be loaded in the initramfs (based on configuration retrieved
30 from /etc/kdump.conf)
31 mkdumprd was origionally derived from the mkinitrd utility (hence the
33 simmilarity in option sets), however mkdumprds purpose and mission is
34 significantly different than that of mkinitrd. As such, while most of
35 the options still exist, and may work, they are largely vestigual at
36 this point. mkdumprd was not intended for casual use outside of the
37 service initialization script for the kdump utility, and should not be
38 run manually. If you require a custom kdump initramfs image, it is
39 suggested that you use the kdump service infrastrucutre to create one,
40 and then manually unpack, modify and repack the image.
41
45 --builtin=module
46 Act as if module is built into the kernel being used. mkdumprd
47 will not look for this module, and will not emit an error if it
48 does not exist. This option may be used multiple times.
49 -f Allows mkdumprd to overwrite an existing image file.
52 --fstab=fstab
55 Use fstab to automatically determine what type of filesystem the
56 root device is on. Normally, /etc/fstab is used.
57 --image-version
60 The kernel version number is appended to the initrd image path
61 before the image is created.
62 --nocompress
65 Normally the created initrd image is compressed with gzip. If
66 this option is specified, the compression is skipped.
67 --nopivot
70 Do not use the pivot_root system call as part of the initrd.
71 This lets mkdumprd build proper images for Linux 2.2 kernels at
72 the expense of some features. In particular, some filesystems
73 (such as ext3) will not work properly and filesystem options
74 will not be used to mount root. This option is not recommended,
75 and will be removed in future versions.
76 --omit-lvm-modules
79 Do not load any lvm modules, even if /etc/fstab expects them.
80 --omit-raid-modules
83 Do not load any raid modules, even if /etc/fstab and
84 /etc/raidtab expect them.
85 --omit-scsi-modules
88 Do not load any scsi modules, including 'scsi_mod' and 'sd_mod'
89 modules, even if they are present.
90 --preload=module
93 Load the module module in the initial ramdisk image. The module
94 gets loaded before any SCSI modules which are specified in
95 /etc/modprobe.conf. This option may be used as many times as
96 necessary.
97 -v Prints out verbose information while creating the image (nor‐
100 mally the mkdumprd runs silently).
101 --version
104 Prints the version of mkdumprd that's being used and then exits.
105 --with=module
108 Load the modules module in the initial ramdisk image. The module
109 gets loaded after any SCSI modules which are specified in
110 /etc/modprobe.conf. This option may be used as many times as
111 necessary.
112
115 /etc/modprobe.conf Specifies modules to be loaded and module options
116 to be used.
117
120 fstab(5), insmod(1) mkinitrd(8)
121 Fri Feb 9 2007 MKDUMRD(8)