1DRACUT.CMDLINE(7) dracut DRACUT.CMDLINE(7)
2
6 dracut.cmdline - dracut kernel command line options
7
9 The root device used by the kernel is specified in the boot
10 configuration file on the kernel command line, as always.
11 The traditional root=/dev/sda1 style device specification is allowed,
13 but not encouraged. The root device should better be identified by
14 LABEL or UUID. If a label is used, as in root=LABEL=<label_of_root> the
15 initramfs will search all available devices for a filesystem with the
16 appropriate label, and mount that device as the root filesystem.
17 root=UUID=<uuidnumber> will mount the partition with that UUID as the
18 root filesystem.
19 In the following all kernel command line parameters, which are
21 processed by dracut, are described.
22 "rd.*" parameters mentioned without "=" are boolean parameters. They
24 can be turned on/off by setting them to {0|1}. If the assignment with
25 "=" is missing "=1" is implied. For example rd.info can be turned off
26 with rd.info=0 or turned on with rd.info=1 or rd.info. The last value
27 in the kernel command line is the value, which is honored.
28 Standard
30 init=<path to real init>
31 specify the path to the init program to be started after the
32 initramfs has finished
33 root=<path to blockdevice>
35 specify the block device to use as the root filesystem.
36 Example.
38 root=/dev/sda1
40 root=/dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:1:0-part1
41 root=/dev/disk/by-label/Root
42 root=LABEL=Root
43 root=/dev/disk/by-uuid/3f5ad593-4546-4a94-a374-bcfb68aa11f7
44 root=UUID=3f5ad593-4546-4a94-a374-bcfb68aa11f7
45 root=PARTUUID=3f5ad593-4546-4a94-a374-bcfb68aa11f7
46 rootfstype=<filesystem type>
49 "auto" if not specified.
50 Example.
52 rootfstype=ext3
54 rootflags=<mount options>
57 specify additional mount options for the root filesystem. If not
58 set, /etc/fstab of the real root will be parsed for special mount
59 options and mounted accordingly.
60 ro
62 force mounting / and /usr (if it is a separate device) read-only.
63 If none of ro and rw is present, both are mounted according to
64 /etc/fstab.
65 rw
67 force mounting / and /usr (if it is a separate device) read-write.
68 See also ro option.
69 rootfallback=<path to blockdevice>
71 specify the block device to use as the root filesystem, if the
72 normal root cannot be found. This can only be a simple block device
73 with a simple file system, for which the filesystem driver is
74 either compiled in, or added manually to the initramfs. This
75 parameter can be specified multiple times.
76 rd.auto rd.auto=1
78 enable autoassembly of special devices like cryptoLUKS, dmraid,
79 mdraid or lvm. Default is off as of dracut version >= 024.
80 rd.hostonly=0
82 removes all compiled in configuration of the host system the
83 initramfs image was built on. This helps booting, if any disk
84 layout changed, especially in combination with rd.auto or other
85 parameters specifying the layout.
86 rd.cmdline=ask
88 prompts the user for additional kernel command line parameters
89 rd.fstab=0
91 do not honor special mount options for the root filesystem found in
92 /etc/fstab of the real root.
93 resume=<path to resume partition>
95 resume from a swap partition
96 Example.
98 resume=/dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:1:0-part1
100 resume=/dev/disk/by-uuid/3f5ad593-4546-4a94-a374-bcfb68aa11f7
101 resume=UUID=3f5ad593-4546-4a94-a374-bcfb68aa11f7
102 rd.skipfsck
105 skip fsck for rootfs and /usr. If you’re mounting /usr read-only
106 and the init system performs fsck before remount, you might want to
107 use this option to avoid duplication.
108 iso-scan/filename
110 Mount all mountable devices and search for ISO pointed by the argument.
111 When the ISO is found set it up as a loop device. Device containing
112 this ISO image will stay mounted at /run/initramfs/isoscandev. Using
113 iso-scan/filename with a Fedora/Red Hat/CentOS Live iso should just
114 work by copying the original kernel cmdline parameters.
115 Example.
117 menuentry 'Live Fedora 20' --class fedora --class gnu-linux --class gnu --class os {
119 set isolabel=Fedora-Live-LXDE-x86_64-20-1
120 set isofile="/boot/iso/Fedora-Live-LXDE-x86_64-20-1.iso"
121 loopback loop $isofile
122 linux (loop)/isolinux/vmlinuz0 boot=isolinux iso-scan/filename=$isofile root=live:LABEL=$isolabel ro rd.live.image quiet rhgb
123 initrd (loop)/isolinux/initrd0.img
124 }
125 Misc
128 rd.emergency=[reboot|poweroff|halt]
129 specify, what action to execute in case of a critical failure.
130 rd.shell=0 must also be specified.
131 rd.driver.blacklist=<drivername>[,<drivername>,...]
133 do not load kernel module <drivername>. This parameter can be
134 specified multiple times.
135 rd.driver.pre=<drivername>[,<drivername>,...]
137 force loading kernel module <drivername>. This parameter can be
138 specified multiple times.
139 rd.driver.post=<drivername>[,<drivername>,...]
141 force loading kernel module <drivername> after all automatic
142 loading modules have been loaded. This parameter can be specified
143 multiple times.
144 rd.retry=<seconds>
146 specify how long dracut should retry the initqueue to configure
147 devices. The default is 180 seconds. After 2/3 of the time,
148 degraded raids are force started. If you have hardware, which takes
149 a very long time to announce its drives, you might want to extend
150 this value.
151 rd.timeout=<seconds>
153 specify how long dracut should wait for devices to appear. The
154 default is 0, which means forever. Note that this timeout should be
155 longer than rd.retry to allow for proper configuration.
156 rd.noverifyssl
158 accept self-signed certificates for ssl downloads.
159 rd.ctty=<terminal device>
161 specify the controlling terminal for the console. This is useful,
162 if you have multiple "console=" arguments.
163 rd.shutdown.timeout.umount=<seconds>
165 specify how long dracut should wait for an individual umount to
166 finish during shutdown. This avoids the system from blocking when
167 unmounting a file system cannot complete and waits indefinitely.
168 Value 0 means to wait forever. The default is 90 seconds.
169 Debug
171 If you are dropped to an emergency shell, the file
172 /run/initramfs/rdsosreport.txt is created, which can be saved to a (to
173 be mounted by hand) partition (usually /boot) or a USB stick.
174 Additional debugging info can be produced by adding rd.debug to the
175 kernel command line. /run/initramfs/rdsosreport.txt contains all logs
176 and the output of some tools. It should be attached to any report about
177 dracut problems.
178 rd.info
180 print informational output though "quiet" is set
181 rd.shell
183 allow dropping to a shell, if root mounting fails
184 rd.debug
186 set -x for the dracut shell. If systemd is active in the initramfs,
187 all output is logged to the systemd journal, which you can inspect
188 with "journalctl -ab". If systemd is not active, the logs are
189 written to dmesg and /run/initramfs/init.log. If "quiet" is set, it
190 also logs to the console.
191 rd.memdebug=[0-5]
193 Print memory usage info at various points, set the verbose level
194 from 0 to 5.
195 Higher level means more debugging output:
197 0 - no output
199 1 - partial /proc/meminfo
200 2 - /proc/meminfo
201 3 - /proc/meminfo + /proc/slabinfo
202 4 - /proc/meminfo + /proc/slabinfo + memstrack summary
203 NOTE: memstrack is a memory tracing tool that tracks the total memory
204 consumption, and peak memory consumption of each kernel modules
205 and userspace progress during the whole initramfs runtime, report
206 is genereted and the end of initramsfs run.
207 5 - /proc/meminfo + /proc/slabinfo + memstrack (with top memory stacktrace)
208 NOTE: memstrack (with top memory stacktrace) will print top memory
209 allocation stack traces during the whole initramfs runtime.
210 rd.break
212 drop to a shell at the end
213 rd.break={cmdline|pre-udev|pre-trigger|initqueue|pre-mount|mount|pre-pivot|cleanup}
215 drop to a shell before the defined breakpoint starts
216 rd.udev.info
218 set udev to loglevel info
219 rd.udev.debug
221 set udev to loglevel debug
222 I18N
224 rd.vconsole.keymap=<keymap base file name>
225 keyboard translation table loaded by loadkeys; taken from keymaps
226 directory; will be written as KEYMAP to /etc/vconsole.conf in the
227 initramfs.
228 Example.
230 rd.vconsole.keymap=de-latin1-nodeadkeys
232 rd.vconsole.keymap.ext=<list of keymap base file names>
235 list of extra keymaps to bo loaded (sep. by space); will be written
236 as EXT_KEYMAP to /etc/vconsole.conf in the initramfs
237 rd.vconsole.unicode
239 boolean, indicating UTF-8 mode; will be written as UNICODE to
240 /etc/vconsole.conf in the initramfs
241 rd.vconsole.font=<font base file name>
243 console font; taken from consolefonts directory; will be written as
244 FONT to /etc/vconsole.conf in the initramfs.
245 Example.
247 rd.vconsole.font=eurlatgr
249 rd.vconsole.font.map=<console map base file name>
252 see description of -m parameter in setfont manual; taken from
253 consoletrans directory; will be written as FONT_MAP to
254 /etc/vconsole.conf in the initramfs
255 rd.vconsole.font.unimap=<unicode table base file name>
257 see description of -u parameter in setfont manual; taken from
258 unimaps directory; will be written as FONT_UNIMAP to
259 /etc/vconsole.conf in the initramfs
260 rd.locale.LANG=<locale>
262 taken from the environment; if no UNICODE is defined we set its
263 value in basis of LANG value (whether it ends with ".utf8" (or
264 similar) or not); will be written as LANG to /etc/locale.conf in
265 the initramfs.
266 Example.
268 rd.locale.LANG=pl_PL.utf8
270 rd.locale.LC_ALL=<locale>
273 taken from the environment; will be written as LC_ALL to
274 /etc/locale.conf in the initramfs
275 LVM
277 rd.lvm=0
278 disable LVM detection
279 rd.lvm.vg=<volume group name>
281 only activate all logical volumes in the the volume groups with the
282 given name. rd.lvm.vg can be specified multiple times on the kernel
283 command line.
284 rd.lvm.lv=<volume group name>/<logical volume name>
286 only activate the logical volumes with the given name. rd.lvm.lv
287 can be specified multiple times on the kernel command line.
288 rd.lvm.conf=0
290 remove any /etc/lvm/lvm.conf, which may exist in the initramfs
291 crypto LUKS
293 rd.luks=0
294 disable crypto LUKS detection
295 rd.luks.uuid=<luks uuid>
297 only activate the LUKS partitions with the given UUID. Any "luks-"
298 of the LUKS UUID is removed before comparing to <luks uuid>. The
299 comparisons also matches, if <luks uuid> is only the beginning of
300 the LUKS UUID, so you don’t have to specify the full UUID. This
301 parameter can be specified multiple times. <luks uuid> may be
302 prefixed by the keyword keysource:, see rd.luks.key below.
303 rd.luks.allow-discards=<luks uuid>
305 Allow using of discards (TRIM) requests for LUKS partitions with
306 the given UUID. Any "luks-" of the LUKS UUID is removed before
307 comparing to <luks uuid>. The comparisons also matches, if <luks
308 uuid> is only the beginning of the LUKS UUID, so you don’t have to
309 specify the full UUID. This parameter can be specified multiple
310 times.
311 rd.luks.allow-discards
313 Allow using of discards (TRIM) requests on all LUKS partitions.
314 rd.luks.crypttab=0
316 do not check, if LUKS partition is in /etc/crypttab
317 rd.luks.timeout=<seconds>
319 specify how long dracut should wait when waiting for the user to
320 enter the password. This avoid blocking the boot if no password is
321 entered. It does not apply to luks key. The default is 0, which
322 means forever.
323 crypto LUKS - key on removable device support
325 NB: If systemd is included in the dracut initrd, dracut’s built in
326 removable device keying support won’t work. systemd will prompt for a
327 password from the console even if you’ve supplied rd.luks.key. You may
328 be able to use standard systemd fstab(5) syntax to get the same effect.
329 If you do need rd.luks.key to work, you will have to exclude the
330 "systemd" dracut module and any modules that depend on it. See
331 dracut.conf(5) and https://bugzilla.redhat.com/show_bug.cgi?id=905683
332 for more information.
333 rd.luks.key=<keypath>[:<keydev>[:<luksdev>]]
335 <keypath> is the pathname of a key file, relative to the root of
336 the filesystem on some device. It’s REQUIRED. When <keypath> ends
337 with .gpg it’s considered to be key encrypted symmetrically with
338 GPG. You will be prompted for the GPG password on boot. GPG support
339 comes with the crypt-gpg module, which needs to be added
340 explicitly.
341 <keydev> identifies the device on which the key file resides. It
343 may be the kernel name of the device (should start with "/dev/"), a
344 UUID (prefixed with "UUID=") or a label (prefix with "LABEL="). You
345 don’t have to specify a full UUID. Just its beginning will suffice,
346 even if its ambiguous. All matching devices will be probed. This
347 parameter is recommended, but not required. If it’s not present,
348 all block devices will be probed, which may significantly increase
349 boot time.
350 If <luksdev> is given, the specified key will only be used for the
352 specified LUKS device. Possible values are the same as for
353 <keydev>. Unless you have several LUKS devices, you don’t have to
354 specify this parameter. The simplest usage is:
355 Example.
357 rd.luks.key=/foo/bar.key
359 As you see, you can skip colons in such a case.
362 Note
364 Your LUKS partition must match your key file.
365 dracut provides keys to cryptsetup with -d (an older alias for
367 --key-file). This uses the entire binary content of the key file as
368 part of the secret. If you pipe a password into cryptsetup without
369 -d or --key-file, it will be treated as text user input, and only
370 characters before the first newline will be used. Therefore, when
371 you’re creating an encrypted partition for dracut to mount, and you
372 pipe a key into cryptsetup luksFormat,you must use -d -.
373 Here is an example for a key encrypted with GPG (warning:
375 --batch-mode will overwrite the device without asking for
376 confirmation):
377 gpg --quiet --decrypt rootkey.gpg | \
379 cryptsetup --batch-mode --key-file - \
380 luksFormat /dev/sda47
381 If you use unencrypted key files, just use the key file pathname
383 instead of the standard input. For a random key with 256 bits of
384 entropy, you might use:
385 head -32c /dev/urandom > rootkey.key
387 cryptsetup --batch-mode --key-file rootkey.key \
388 luksFormat /dev/sda47
389 You can also use regular key files on an encrypted keydev.
391 Compared to using GPG encrypted keyfiles on an unencrypted device
393 this provides the following advantages:
394 • you can unlock your disk(s) using multiple passphrases
396 • better security by not loosing the key stretching mechanism
398 To use an encrypted keydev you must ensure that it becomes
400 available by using the keyword keysource, e.g.
401 rd.luks.uuid=keysource:aaaa aaaa being the uuid of the encrypted
402 keydev.
403 Example:
405 Lets assume you have three disks A, B and C with the uuids aaaa,
407 bbbb and cccc. You want to unlock A and B using keyfile keyfile.
408 The unlocked volumes be A', B' and C' with the uuids AAAA, BBBB and
409 CCCC. keyfile is saved on C' as /keyfile.
410 One luks keyslot of each A, B and C is setup with a passphrase.
412 Another luks keyslot of each A and B is setup with keyfile.
413 To boot this configuration you could use:
415 rd.luks.uuid=aaaa
417 rd.luks.uuid=bbbb
418 rd.luks.uuid=keysource:cccc
419 rd.luks.key=/keyfile:UUID=CCCC
420 Dracut asks for the passphrase for C and uses the keyfile to unlock
422 A and B. If getting the passphrase for C fails it falls back to
423 asking for the passphrases for A and B.
424 If you want C' to stay unlocked, specify a luks name for it, e.g.
426 rd.luks.name=cccc=mykeys, otherwise it gets closed when not needed
427 anymore.
428 rd.luks.key.tout=0
430 specify how many times dracut will try to read the keys specified
431 in in rd.luk.key. This gives a chance to the removable device
432 containing the key to initialise.
433 MD RAID
435 rd.md=0
436 disable MD RAID detection
437 rd.md.imsm=0
439 disable MD RAID for imsm/isw raids, use DM RAID instead
440 rd.md.ddf=0
442 disable MD RAID for SNIA ddf raids, use DM RAID instead
443 rd.md.conf=0
445 ignore mdadm.conf included in initramfs
446 rd.md.waitclean=1
448 wait for any resync, recovery, or reshape activity to finish before
449 continuing
450 rd.md.uuid=<md raid uuid>
452 only activate the raid sets with the given UUID. This parameter can
453 be specified multiple times.
454 DM RAID
456 rd.dm=0
457 disable DM RAID detection
458 rd.dm.uuid=<dm raid uuid>
460 only activate the raid sets with the given UUID. This parameter can
461 be specified multiple times.
462 MULTIPATH
464 rd.multipath=0
465 disable multipath detection
466 rd.multipath=default
468 use default multipath settings
469 FIPS
471 rd.fips
472 enable FIPS
473 boot=<boot device>
475 specify the device, where /boot is located.
476 Example.
478 boot=/dev/sda1
480 boot=/dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:1:0-part1
481 boot=UUID=<uuid>
482 boot=LABEL=<label>
483 rd.fips.skipkernel
486 skip checksum check of the kernel image. Useful, if the kernel
487 image is not in a separate boot partition.
488 Network
490 Important
491 It is recommended to either bind an interface to a MAC with the
492 ifname argument, or to use the systemd-udevd predictable network
493 interface names.
494 Predictable network interface device names based on:
496 • firmware/bios-provided index numbers for on-board devices
498 • firmware-provided pci-express hotplug slot index number
500 • physical/geographical location of the hardware
502 • the interface’s MAC address
504 See:
506 http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
507 Two character prefixes based on the type of interface:
509 en
511 ethernet
512 wl
514 wlan
515 ww
517 wwan
518 Type of names:
520 o<index>
522 on-board device index number
523 s<slot>[f<function>][d<dev_id>]
525 hotplug slot index number
526 x<MAC>
528 MAC address
529 [P<domain>]p<bus>s<slot>[f<function>][d<dev_id>]
531 PCI geographical location
532 [P<domain>]p<bus>s<slot>[f<function>][u<port>][..][c<config>][i<interface>]
534 USB port number chain
535 All multi-function PCI devices will carry the [f<function>] number
537 in the device name, including the function 0 device.
538 When using PCI geography, The PCI domain is only prepended when it
540 is not 0.
541 For USB devices the full chain of port numbers of hubs is composed.
543 If the name gets longer than the maximum number of 15 characters,
544 the name is not exported. The usual USB configuration == 1 and
545 interface == 0 values are suppressed.
546 PCI ethernet card with firmware index "1"
548 • eno1
550 PCI ethernet card in hotplug slot with firmware index number
552 • ens1
554 PCI ethernet multi-function card with 2 ports
556 • enp2s0f0
558 • enp2s0f1
560 PCI wlan card
562 • wlp3s0
564 USB built-in 3G modem
566 • wwp0s29u1u4i6
568 USB Android phone
570 • enp0s29u1u2
572 The following options are supported by the network-legacy dracut
574 module. Other network modules might support a slightly different set of
575 options; refer to the documentation of the specific network module in
576 use. For NetworkManager, see nm-initrd-generator(8).
577 ip={dhcp|on|any|dhcp6|auto6|either6|link6|single-dhcp}
579 dhcp|on|any
581 get ip from dhcp server from all interfaces. If netroot=dhcp,
582 loop sequentially through all interfaces (eth0, eth1, ...) and
583 use the first with a valid DHCP root-path.
584 single-dhcp
586 Send DHCP on all available interfaces in parallel, as opposed
587 to one after another. After the first DHCP response is
588 received, stop DHCP on all other interfaces. This gives the
589 fastest boot time by using the IP on interface for which DHCP
590 succeeded first during early boot. Caveat: Does not apply to
591 Network Manager and to SUSE using wicked.
592 auto6
594 IPv6 autoconfiguration
595 dhcp6
597 IPv6 DHCP
598 either6
600 if auto6 fails, then dhcp6
601 link6
603 bring up interface for IPv6 link-local addressing
604 ip=<interface>:{dhcp|on|any|dhcp6|auto6|link6}[:[<mtu>][:<macaddr>]]
606 This parameter can be specified multiple times.
607 dhcp|on|any|dhcp6
609 get ip from dhcp server on a specific interface
610 auto6
612 do IPv6 autoconfiguration
613 link6
615 bring up interface for IPv6 link local address
616 <macaddr>
618 optionally set <macaddr> on the <interface>. This cannot be
619 used in conjunction with the ifname argument for the same
620 <interface>.
621 ip=<client-IP>:[<peer>]:<gateway-IP>:<netmask>:<client_hostname>:<interface>:{none|off|dhcp|on|any|dhcp6|auto6|ibft}[:[<mtu>][:<macaddr>]]
623 explicit network configuration. If you want do define a IPv6
624 address, put it in brackets (e.g. [2001:DB8::1]). This parameter
625 can be specified multiple times. <peer> is optional and is the
626 address of the remote endpoint for pointopoint interfaces and it
627 may be followed by a slash and a decimal number, encoding the
628 network prefix length.
629 <macaddr>
631 optionally set <macaddr> on the <interface>. This cannot be
632 used in conjunction with the ifname argument for the same
633 <interface>.
634 ip=<client-IP>:[<peer>]:<gateway-IP>:<netmask>:<client_hostname>:<interface>:{none|off|dhcp|on|any|dhcp6|auto6|ibft}[:[<dns1>][:<dns2>]]
636 explicit network configuration. If you want do define a IPv6
637 address, put it in brackets (e.g. [2001:DB8::1]). This parameter
638 can be specified multiple times. <peer> is optional and is the
639 address of the remote endpoint for pointopoint interfaces and it
640 may be followed by a slash and a decimal number, encoding the
641 network prefix length.
642 ifname=<interface>:<MAC>
644 Assign network device name <interface> (i.e. "bootnet") to the NIC
645 with MAC <MAC>.
646 Warning
648 Do not use the default kernel naming scheme for the interface
649 name, as it can conflict with the kernel names. So, don’t use
650 "eth[0-9]+" for the interface name. Better name it "bootnet" or
651 "bluesocket".
652 rd.route=<net>/<netmask>:<gateway>[:<interface>]
654 Add a static route with route options, which are separated by a
655 colon. IPv6 addresses have to be put in brackets.
656 Example.
658 rd.route=192.168.200.0/24:192.168.100.222:ens10
660 rd.route=192.168.200.0/24:192.168.100.222
661 rd.route=192.168.200.0/24::ens10
662 rd.route=[2001:DB8:3::/8]:[2001:DB8:2::1]:ens10
663 bootdev=<interface>
666 specify network interface to use routing and netroot information
667 from. Required if multiple ip= lines are used.
668 BOOTIF=<MAC>
670 specify network interface to use routing and netroot information
671 from.
672 rd.bootif=0
674 Disable BOOTIF parsing, which is provided by PXE
675 nameserver=<IP> [nameserver=<IP> ...]
677 specify nameserver(s) to use
678 rd.peerdns=0
680 Disable DNS setting of DHCP parameters.
681 biosdevname=0
683 boolean, turn off biosdevname network interface renaming
684 rd.neednet=1
686 boolean, bring up network even without netroot set
687 vlan=<vlanname>:<phydevice>
689 Setup vlan device named <vlanname> on <phydevice>. We support the
690 four styles of vlan names: VLAN_PLUS_VID (vlan0005),
691 VLAN_PLUS_VID_NO_PAD (vlan5), DEV_PLUS_VID (eth0.0005),
692 DEV_PLUS_VID_NO_PAD (eth0.5)
693 bond=<bondname>[:<bondslaves>:[:<options>[:<mtu>]]]
695 Setup bonding device <bondname> on top of <bondslaves>.
696 <bondslaves> is a comma-separated list of physical (ethernet)
697 interfaces. <options> is a comma-separated list on bonding options
698 (modinfo bonding for details) in format compatible with
699 initscripts. If <options> includes multi-valued arp_ip_target
700 option, then its values should be separated by semicolon. if the
701 mtu is specified, it will be set on the bond master. Bond without
702 parameters assumes bond=bond0:eth0,eth1:mode=balance-rr
703 team=<teammaster>:<teamslaves>[:<teamrunner>]
705 Setup team device <teammaster> on top of <teamslaves>. <teamslaves>
706 is a comma-separated list of physical (ethernet) interfaces.
707 <teamrunner> is the runner type to be used (see teamd.conf(5));
708 defaults to activebackup. Team without parameters assumes
709 team=team0:eth0,eth1:activebackup
710 bridge=<bridgename>:<ethnames>
712 Setup bridge <bridgename> with <ethnames>. <ethnames> is a
713 comma-separated list of physical (ethernet) interfaces. Bridge
714 without parameters assumes bridge=br0:eth0
715 NFS
717 root=[<server-ip>:]<root-dir>[:<nfs-options>]
718 mount nfs share from <server-ip>:/<root-dir>, if no server-ip is
719 given, use dhcp next_server. If server-ip is an IPv6 address it has
720 to be put in brackets, e.g. [2001:DB8::1]. NFS options can be
721 appended with the prefix ":" or "," and are separated by ",".
722 root=nfs:[<server-ip>:]<root-dir>[:<nfs-options>],
724 root=nfs4:[<server-ip>:]<root-dir>[:<nfs-options>], root={dhcp|dhcp6}
725 netroot=dhcp alone directs initrd to look at the DHCP root-path
726 where NFS options can be specified.
727 Example.
729 root-path=<server-ip>:<root-dir>[,<nfs-options>]
731 root-path=nfs:<server-ip>:<root-dir>[,<nfs-options>]
732 root-path=nfs4:<server-ip>:<root-dir>[,<nfs-options>]
733 root=/dev/nfs nfsroot=[<server-ip>:]<root-dir>[:<nfs-options>]
736 Deprecated! kernel Documentation_/filesystems/nfsroot.txt_ defines
737 this method. This is supported by dracut, but not recommended.
738 rd.nfs.domain=<NFSv4 domain name>
740 Set the NFSv4 domain name. Will override the settings in
741 /etc/idmap.conf.
742 rd.net.dhcp.retry=<cnt>
744 If this option is set, dracut will try to connect via dhcp <cnt>
745 times before failing. Default is 1.
746 rd.net.timeout.dhcp=<arg>
748 If this option is set, dhclient is called with "--timeout <arg>".
749 rd.net.timeout.iflink=<seconds>
751 Wait <seconds> until link shows up. Default is 60 seconds.
752 rd.net.timeout.ifup=<seconds>
754 Wait <seconds> until link has state "UP". Default is 20 seconds.
755 rd.net.timeout.route=<seconds>
757 Wait <seconds> until route shows up. Default is 20 seconds.
758 rd.net.timeout.ipv6dad=<seconds>
760 Wait <seconds> until IPv6 DAD is finished. Default is 50 seconds.
761 rd.net.timeout.ipv6auto=<seconds>
763 Wait <seconds> until IPv6 automatic addresses are assigned. Default
764 is 40 seconds.
765 rd.net.timeout.carrier=<seconds>
767 Wait <seconds> until carrier is recognized. Default is 10 seconds.
768 CIFS
770 root=cifs://[<username>[:<password>]@]<server-ip>:<root-dir>
771 mount cifs share from <server-ip>:/<root-dir>, if no server-ip is
772 given, use dhcp next_server. if server-ip is an IPv6 address it has
773 to be put in brackets, e.g. [2001:DB8::1]. If a username or
774 password are not specified as part of the root, then they must be
775 passed on the command line through cifsuser/cifspass.
776 Warning
778 Passwords specified on the kernel command line are visible for
779 all users via the file /proc/cmdline and via dmesg or can be
780 sniffed on the network, when using DHCP with DHCP root-path.
781 cifsuser=<username>
783 Set the cifs username, if not specified as part of the root.
784 cifspass=<password>
786 Set the cifs password, if not specified as part of the root.
787 Warning
789 Passwords specified on the kernel command line are visible for
790 all users via the file /proc/cmdline and via dmesg or can be
791 sniffed on the network, when using DHCP with DHCP root-path.
792 iSCSI
794 root=iscsi:[<username>:<password>[:<reverse>:<password>]@][<servername>]:[<protocol>]:[<port>][:[<iscsi_iface_name>]:[<netdev_name>]]:[<LUN>]:<targetname>
795 protocol defaults to "6", LUN defaults to "0". If the "servername"
796 field is provided by BOOTP or DHCP, then that field is used in
797 conjunction with other associated fields to contact the boot server
798 in the Boot stage. However, if the "servername" field is not
799 provided, then the "targetname" field is then used in the Discovery
800 Service stage in conjunction with other associated fields. See
801 rfc4173[1].
802 Warning
804 Passwords specified on the kernel command line are visible for
805 all users via the file /proc/cmdline and via dmesg or can be
806 sniffed on the network, when using DHCP with DHCP root-path.
807 Example.
809 root=iscsi:192.168.50.1::::iqn.2009-06.dracut:target0
811 If servername is an IPv6 address, it has to be put in brackets:
814 Example.
816 root=iscsi:[2001:DB8::1]::::iqn.2009-06.dracut:target0
818 root=???
821 netroot=iscsi:[<username>:<password>[:<reverse>:<password>]@][<servername>]:[<protocol>]:[<port>][:[<iscsi_iface_name>]:[<netdev_name>]]:[<LUN>]:<targetname>
822 ...
823 multiple netroot options allow setting up multiple iscsi disks:
824 Example.
826 root=UUID=12424547
828 netroot=iscsi:192.168.50.1::::iqn.2009-06.dracut:target0
829 netroot=iscsi:192.168.50.1::::iqn.2009-06.dracut:target1
830 If servername is an IPv6 address, it has to be put in brackets:
833 Example.
835 netroot=iscsi:[2001:DB8::1]::::iqn.2009-06.dracut:target0
837 Warning
840 Passwords specified on the kernel command line are visible for
841 all users via the file /proc/cmdline and via dmesg or can be
842 sniffed on the network, when using DHCP with DHCP root-path.
843 You may want to use rd.iscsi.firmware.
844 root=??? rd.iscsi.initiator=<initiator> rd.iscsi.target.name=<target
846 name> rd.iscsi.target.ip=<target ip> rd.iscsi.target.port=<target port>
847 rd.iscsi.target.group=<target group> rd.iscsi.username=<username>
848 rd.iscsi.password=<password> rd.iscsi.in.username=<in username>
849 rd.iscsi.in.password=<in password>
850 manually specify all iscsistart parameter (see iscsistart --help)
851 Warning
853 Passwords specified on the kernel command line are visible for
854 all users via the file /proc/cmdline and via dmesg or can be
855 sniffed on the network, when using DHCP with DHCP root-path.
856 You may want to use rd.iscsi.firmware.
857 root=??? netroot=iscsi rd.iscsi.firmware=1
859 will read the iscsi parameter from the BIOS firmware
860 rd.iscsi.login_retry_max=<num>
862 maximum number of login retries
863 rd.iscsi.param=<param>
865 <param> will be passed as "--param <param>" to iscsistart. This
866 parameter can be specified multiple times.
867 Example.
869 "netroot=iscsi rd.iscsi.firmware=1 rd.iscsi.param=node.session.timeo.replacement_timeout=30"
871 will result in
874 iscsistart -b --param node.session.timeo.replacement_timeout=30
876 rd.iscsi.ibft rd.iscsi.ibft=1: Turn on iBFT autoconfiguration for the
878 interfaces
879 rd.iscsi.mp rd.iscsi.mp=1: Configure all iBFT interfaces, not only used
881 for booting (multipath)
882 rd.iscsi.waitnet=0: Turn off waiting for all interfaces to be up before
884 trying to login to the iSCSI targets.
885 rd.iscsi.testroute=0: Turn off checking, if the route to the iSCSI
887 target IP is possible before trying to login.
888 FCoE
890 rd.fcoe=0
891 disable FCoE and lldpad
892 fcoe=<edd|interface|MAC>:{dcb|nodcb}:{fabric|vn2vn}
894 Try to connect to a FCoE SAN through the NIC specified by
895 <interface> or <MAC> or EDD settings. The second argument specifies
896 if DCB should be used. The optional third argument specifies
897 whether fabric or VN2VN mode should be used. This parameter can be
898 specified multiple times.
899 Note
901 letters in the MAC-address must be lowercase!
902 NVMf
904 rd.nonvmf
905 Disable NVMf
906 rd.nvmf.hostnqn=<hostNQN>
908 NVMe host NQN to use
909 rd.nvmf.hostid=<hostID>
911 NVMe host id to use
912 rd.nvmf.discover={rdma|fc|tcp},<traddr>,[<host_traddr>],[<trsvcid>]
914 Discover and connect to a NVMe-over-Fabric controller specified by
915 <traddr> and the optionally <host_traddr> or <trsvcid>. The first
916 argument specifies the transport to use; currently only rdma, fc,
917 or tcp are supported. This parameter can be specified multiple
918 times.
919 Examples.
921 rd.nvmf.discover=tcp,192.168.10.10,,4420
923 rd.nvmf.discover=fc,nn-0x201700a05634f5bf:pn-0x201900a05634f5bf,nn-0x200000109b579ef3:pn-0x100000109b579ef3
924 rd.nvmf.discover=fc,auto
927 This special syntax determines that Fibre Channel autodiscovery is
928 to be used rather than regular NVMe discovery. It takes precedence
929 over all other rd.nvmf.discover= arguments.
930 NBD
932 root=???
933 netroot=nbd:<server>:<port/exportname>[:<fstype>[:<mountopts>[:<nbdopts>]]]
934 mount nbd share from <server>.
935 NOTE: If "exportname" instead of "port" is given the standard port
937 is used. Newer versions of nbd are only supported with
938 "exportname".
939 root=/dev/root netroot=dhcp with dhcp
941 root-path=nbd:<server>:<port/exportname>[:<fstype>[:<mountopts>[:<nbdopts>]]]
942 netroot=dhcp alone directs initrd to look at the DHCP root-path
943 where NBD options can be specified. This syntax is only usable in
944 cases where you are directly mounting the volume as the rootfs.
945 NOTE: If "exportname" instead of "port" is given the standard port
947 is used. Newer versions of nbd are only supported with
948 "exportname".
949 VIRTIOFS
951 root=virtiofs:<mount-tag>
952 mount virtiofs share using the tag <mount-tag>. The tag name is
953 arbitrary and must match the tag given in the qemu -device command.
954 rootfstype=virtiofs root=<mount-tag>
956 mount virtiofs share using the tag <mount-tag>. The tag name is
957 arbitrary and must match the tag given in the qemu -device command.
958 Both formats are supported by the virtiofs dracut module. See
960 https://gitlab.com/virtio-fs/virtiofsd for more information.
961 Example.
963 root=virtiofs:host rw
965 DASD
968 rd.dasd=....
969 same syntax as the kernel module parameter (s390 only)
970 ZFCP
972 rd.zfcp=<zfcp adaptor device bus ID>,<WWPN>,<FCPLUN>
973 rd.zfcp can be specified multiple times on the kernel command line.
974 rd.zfcp=<zfcp adaptor device bus ID>
976 If NPIV is enabled and the allow_lun_scan parameter to the zfcp
977 module is set to Y then the zfcp adaptor will be initiating a scan
978 internally and the <WWPN> and <FCPLUN> parameters can be omitted.
979 Example.
981 rd.zfcp=0.0.4000,0x5005076300C213e9,0x5022000000000000
983 rd.zfcp=0.0.4000
984 rd.zfcp.conf=0
987 ignore zfcp.conf included in the initramfs
988 ZNET
990 rd.znet=<nettype>,<subchannels>,<options>
991 The whole parameter is appended to /etc/ccw.conf, which is used on
992 RHEL/Fedora with ccw_init, which is called from udev for certain
993 devices on z-series. rd.znet can be specified multiple times on the
994 kernel command line.
995 rd.znet_ifname=<ifname>:<subchannels>
997 Assign network device name <interface> (i.e. "bootnet") to the NIC
998 corresponds to the subchannels. This is useful when dracut’s
999 default "ifname=" doesn’t work due to device having a changing MAC
1000 address.
1001 Example.
1003 rd.znet=qeth,0.0.0600,0.0.0601,0.0.0602,layer2=1,portname=foo
1005 rd.znet=ctc,0.0.0600,0.0.0601,protocol=bar
1006 Booting live images
1009 Dracut offers multiple options for live booted images:
1010 SquashFS with read-only filesystem image
1012 The system will boot with a read-only filesystem from the SquashFS
1013 and apply a writable Device-mapper snapshot or an OverlayFS overlay
1014 mount for the read-only base filesystem. This method ensures a
1015 relatively fast boot and lower RAM usage. Users must be careful to
1016 avoid writing too many blocks to a snapshot volume. Once the blocks
1017 of the snapshot overlay are exhausted, the root filesystem becomes
1018 read-only and may cause application failures. The snapshot overlay
1019 file is marked Overflow, and a difficult recovery is required to
1020 repair and enlarge the overlay offline. Non-persistent overlays are
1021 sparse files in RAM that only consume content space as required
1022 blocks are allocated. They default to an apparent size of 32 GiB in
1023 RAM. The size can be adjusted with the rd.live.overlay.size= kernel
1024 command line option.
1025 The filesystem structure is traditionally expected to be:
1027 squashfs.img | SquashFS from LiveCD .iso
1029 !(mount)
1030 /LiveOS
1031 |- rootfs.img | Filesystem image to mount read-only
1032 !(mount)
1033 /bin | Live filesystem
1034 /boot |
1035 /dev |
1036 ... |
1037 For OverlayFS mount overlays, the filesystem structure may also be
1039 a direct compression of the root filesystem:
1040 squashfs.img | SquashFS from LiveCD .iso
1042 !(mount)
1043 /bin | Live filesystem
1044 /boot |
1045 /dev |
1046 ... |
1047 Dracut uses one of the overlay methods of live booting by default.
1049 No additional command line options are required other than
1050 root=live:<URL> to specify the location of your squashed
1051 filesystem.
1052 • The compressed SquashFS image can be copied during boot to RAM
1054 at /run/initramfs/squashed.img by using the rd.live.ram=1
1055 option.
1056 • A device with a persistent overlay can be booted read-only by
1058 using the rd.live.overlay.readonly option on the kernel command
1059 line. This will either cause a temporary, writable overlay to
1060 be stacked over a read-only snapshot of the root filesystem or
1061 the OverlayFS mount will use an additional lower layer with the
1062 root filesystem.
1063 Uncompressed live filesystem image
1065 When the live system was installed with the --skipcompress option
1066 of the livecd-iso-to-disk installation script for Live USB devices,
1067 the root filesystem image, rootfs.img, is expanded on installation
1068 and no SquashFS is involved during boot.
1069 • If rd.live.ram=1 is used in this situation, the full,
1071 uncompressed root filesystem is copied during boot to
1072 /run/initramfs/rootfs.img in the /run tmpfs.
1073 • If rd.live.overlay=none is provided as a kernel command line
1075 option, a writable, linear Device-mapper target is created on
1076 boot with no overlay.
1077 Writable filesystem image
1079 The system will retrieve a compressed filesystem image, extract it
1080 to /run/initramfs/fsimg/rootfs.img, connect it to a loop device,
1081 create a writable, linear Device-mapper target at
1082 /dev/mapper/live-rw, and mount that as a writable volume at /. More
1083 RAM is required during boot but the live filesystem is easier to
1084 manage if it becomes full. Users can make a filesystem image of any
1085 size and that size will be maintained when the system boots. There
1086 is no persistence of root filesystem changes between boots with
1087 this option.
1088 The filesystem structure is expected to be:
1090 rootfs.tgz | Compressed tarball containing filesystem image
1092 !(unpack)
1093 /rootfs.img | Filesystem image at /run/initramfs/fsimg/
1094 !(mount)
1095 /bin | Live filesystem
1096 /boot |
1097 /dev |
1098 ... |
1099 To use this boot option, ensure that rd.writable.fsimg=1 is in your
1101 kernel command line and add the root=live:<URL> to specify the
1102 location of your compressed filesystem image tarball or SquashFS
1103 image.
1104 rd.writable.fsimg=1
1106 Enables writable filesystem support. The system will boot with a
1107 fully writable (but non-persistent) filesystem without snapshots
1108 (see notes above about available live boot options). You can use
1109 the rootflags option to set mount options for the live filesystem
1110 as well (see documentation about rootflags in the Standard section
1111 above). This implies that the whole image is copied to RAM before
1112 the boot continues.
1113 Note
1115 There must be enough free RAM available to hold the complete
1116 image.
1117 This method is very suitable for diskless boots.
1118 root=live:<url>
1120 Boots a live image retrieved from <url>. Requires the dracut
1121 livenet module. Valid handlers: http, https, ftp, torrent, tftp.
1122 Examples.
1124 root=live:http://example.com/liveboot.img
1126 root=live:ftp://ftp.example.com/liveboot.img
1127 root=live:torrent://example.com/liveboot.img.torrent
1128 rd.live.debug=1
1131 Enables debug output from the live boot process.
1132 rd.live.dir=<path>
1134 Specifies the directory within the boot device where the
1135 squashfs.img or rootfs.img can be found. By default, this is
1136 /LiveOS.
1137 rd.live.squashimg=<filename of SquashFS image>
1139 Specifies the filename for a SquashFS image of the root filesystem.
1140 By default, this is squashfs.img.
1141 rd.live.ram=1
1143 Copy the complete image to RAM and use this for booting. This is
1144 useful when the image resides on, e.g., a DVD which needs to be
1145 ejected later on.
1146 rd.live.overlay={<devspec>[:{<pathspec>|auto}]|none}
1148 Manage the usage of a permanent overlay.
1149 • <devspec> specifies the path to a device with a mountable
1151 filesystem.
1152 • <pathspec> is the path to a file within that filesystem, which
1154 shall be used to persist the changes made to the device
1155 specified by the root=live:<url> option.
1156 The default pathspec, when auto or no :<pathspec> is given, is
1158 /<rd.live.dir>/overlay-<label>-<uuid>, where <label> is the
1159 device LABEL, and <uuid> is the device UUID. * none (the word
1160 itself) specifies that no overlay will be used, such as when an
1161 uncompressed, writable live root filesystem is available.
1162 If a persistent overlay is detected at the standard LiveOS
1164 path, the overlay & overlay type detected, whether
1165 Device-mapper or OverlayFS, will be used.
1166 Examples.
1168 rd.live.overlay=/dev/sdb1:persistent-overlay.img
1170 rd.live.overlay=UUID=99440c1f-8daa-41bf-b965-b7240a8996f4
1171 rd.live.overlay.cowfs=[btrfs|ext4|xfs]
1174 Specifies the filesystem to use when formatting the overlay
1175 partition. The default is ext4.
1176 rd.live.overlay.size=<size_MiB>
1178 Specifies a non-persistent Device-mapper overlay size in MiB. The
1179 default is 32768.
1180 rd.live.overlay.readonly=1
1182 This is used to boot with a normally read-write persistent overlay
1183 in a read-only mode. With this option, either an additional,
1184 non-persistent, writable snapshot overlay will be stacked over a
1185 read-only snapshot, /dev/mapper/live-ro, of the base filesystem
1186 with the persistent overlay, or a read-only loop device, in the
1187 case of a writable rootfs.img, or an OverlayFS mount will use the
1188 persistent overlay directory linked at /run/overlayfs-r as an
1189 additional lower layer along with the base root filesystem and
1190 apply a transient, writable upper directory overlay, in order to
1191 complete the booted root filesystem.
1192 rd.live.overlay.reset=1
1194 Specifies that a persistent overlay should be reset on boot. All
1195 previous root filesystem changes are vacated by this action.
1196 rd.live.overlay.thin=1
1198 Enables the usage of thin snapshots instead of classic dm
1199 snapshots. The advantage of thin snapshots is that they support
1200 discards, and will free blocks that are not claimed by the
1201 filesystem. In this use case, this means that memory is given back
1202 to the kernel when the filesystem does not claim it anymore.
1203 rd.live.overlay.overlayfs=1
1205 Enables the use of the OverlayFS kernel module, if available, to
1206 provide a copy-on-write union directory for the root filesystem.
1207 OverlayFS overlays are directories of the files that have changed
1208 on the read-only base (lower) filesystem. The root filesystem is
1209 provided through a special overlay type mount that merges the lower
1210 and upper directories. If an OverlayFS upper directory is not
1211 present on the boot device, a tmpfs directory will be created at
1212 /run/overlayfs to provide temporary storage. Persistent storage can
1213 be provided on vfat or msdos formatted devices by supplying the
1214 OverlayFS upper directory within an embedded filesystem that
1215 supports the creation of trusted.* extended attributes and provides
1216 a valid d_type in readdir responses, such as with ext4 and xfs. On
1217 non-vfat-formatted devices, a persistent OverlayFS overlay can
1218 extend the available root filesystem storage up to the capacity of
1219 the LiveOS disk device.
1220 If a persistent overlay is detected at the standard LiveOS path,
1222 the overlay & overlay type detected, whether OverlayFS or
1223 Device-mapper, will be used.
1224 The rd.live.overlay.readonly option, which allows a persistent
1226 overlayfs to be mounted read-only through a higher level transient
1227 overlay directory, has been implemented through the multiple lower
1228 layers feature of OverlayFS.
1229 ZIPL
1231 rd.zipl=<path to blockdevice>
1232 Update the dracut commandline with the values found in the
1233 dracut-cmdline.conf file on the given device. The values are merged
1234 into the existing commandline values and the udev events are
1235 regenerated.
1236 Example.
1238 rd.zipl=UUID=0fb28157-99e3-4395-adef-da3f7d44835a
1240 CIO_IGNORE
1243 rd.cio_accept=<device-ids>
1244 Remove the devices listed in <device-ids> from the default
1245 cio_ignore kernel command-line settings. <device-ids> is a list of
1246 comma-separated CCW device ids. The default for this value is taken
1247 from the /boot/zipl/active_devices.txt file.
1248 Example.
1250 rd.cio_accept=0.0.0180,0.0.0800,0.0.0801,0.0.0802
1252 Plymouth Boot Splash
1255 plymouth.enable=0
1256 disable the plymouth bootsplash completely.
1257 rd.plymouth=0
1259 disable the plymouth bootsplash only for the initramfs.
1260 Kernel keys
1262 masterkey=<kernel master key path name>
1263 Set the path name of the kernel master key.
1264 Example.
1266 masterkey=/etc/keys/kmk-trusted.blob
1268 masterkeytype=<kernel master key type>
1271 Set the type of the kernel master key.
1272 Example.
1274 masterkeytype=trusted
1276 evmkey=<EVM HMAC key path name>
1279 Set the path name of the EVM HMAC key.
1280 Example.
1282 evmkey=/etc/keys/evm-trusted.blob
1284 evmx509=<EVM X.509 cert path name>
1287 Set the path name of the EVM X.509 certificate.
1288 Example.
1290 evmx509=/etc/keys/x509_evm.der
1292 ecryptfskey=<eCryptfs key path name>
1295 Set the path name of the eCryptfs key.
1296 Example.
1298 ecryptfskey=/etc/keys/ecryptfs-trusted.blob
1300 Deprecated, renamed Options
1303 Here is a list of options, which were used in dracut prior to version
1304 008, and their new replacement.
1305 rdbreak
1307 rd.break
1308 rd.ccw
1310 rd.znet
1311 rd_CCW
1313 rd.znet
1314 rd_DASD_MOD
1316 rd.dasd
1317 rd_DASD
1319 rd.dasd
1320 rdinitdebug rdnetdebug
1322 rd.debug
1323 rd_NO_DM
1325 rd.dm=0
1326 rd_DM_UUID
1328 rd.dm.uuid
1329 rdblacklist
1331 rd.driver.blacklist
1332 rdinsmodpost
1334 rd.driver.post
1335 rdloaddriver
1337 rd.driver.pre
1338 rd_NO_FSTAB
1340 rd.fstab=0
1341 rdinfo
1343 rd.info
1344 check
1346 rd.live.check
1347 rdlivedebug
1349 rd.live.debug
1350 live_dir
1352 rd.live.dir
1353 liveimg
1355 rd.live.image
1356 overlay
1358 rd.live.overlay
1359 readonly_overlay
1361 rd.live.overlay.readonly
1362 reset_overlay
1364 rd.live.overlay.reset
1365 live_ram
1367 rd.live.ram
1368 rd_NO_CRYPTTAB
1370 rd.luks.crypttab=0
1371 rd_LUKS_KEYDEV_UUID
1373 rd.luks.keydev.uuid
1374 rd_LUKS_KEYPATH
1376 rd.luks.keypath
1377 rd_NO_LUKS
1379 rd.luks=0
1380 rd_LUKS_UUID
1382 rd.luks.uuid
1383 rd_NO_LVMCONF
1385 rd.lvm.conf
1386 rd_LVM_LV
1388 rd.lvm.lv
1389 rd_NO_LVM
1391 rd.lvm=0
1392 rd_LVM_SNAPSHOT
1394 rd.lvm.snapshot
1395 rd_LVM_SNAPSIZE
1397 rd.lvm.snapsize
1398 rd_LVM_VG
1400 rd.lvm.vg
1401 rd_NO_MDADMCONF
1403 rd.md.conf=0
1404 rd_NO_MDIMSM
1406 rd.md.imsm=0
1407 rd_NO_MD
1409 rd.md=0
1410 rd_MD_UUID
1412 rd.md.uuid
1413 rd_NO_MULTIPATH: rd.multipath=0
1415 rd_NFS_DOMAIN
1417 rd.nfs.domain
1418 iscsi_initiator
1420 rd.iscsi.initiator
1421 iscsi_target_name
1423 rd.iscsi.target.name
1424 iscsi_target_ip
1426 rd.iscsi.target.ip
1427 iscsi_target_port
1429 rd.iscsi.target.port
1430 iscsi_target_group
1432 rd.iscsi.target.group
1433 iscsi_username
1435 rd.iscsi.username
1436 iscsi_password
1438 rd.iscsi.password
1439 iscsi_in_username
1441 rd.iscsi.in.username
1442 iscsi_in_password
1444 rd.iscsi.in.password
1445 iscsi_firmware
1447 rd.iscsi.firmware=0
1448 rd_NO_PLYMOUTH
1450 rd.plymouth=0
1451 rd_retry
1453 rd.retry
1454 rdshell
1456 rd.shell
1457 rd_NO_SPLASH
1459 rd.splash
1460 rdudevdebug
1462 rd.udev.debug
1463 rdudevinfo
1465 rd.udev.info
1466 rd_NO_ZFCPCONF
1468 rd.zfcp.conf=0
1469 rd_ZFCP
1471 rd.zfcp
1472 rd_ZNET
1474 rd.znet
1475 KEYMAP
1477 vconsole.keymap
1478 KEYTABLE
1480 vconsole.keymap
1481 SYSFONT
1483 vconsole.font
1484 CONTRANS
1486 vconsole.font.map
1487 UNIMAP
1489 vconsole.font.unimap
1490 UNICODE
1492 vconsole.unicode
1493 EXT_KEYMAP
1495 vconsole.keymap.ext
1496 Configuration in the Initramfs
1498 /etc/conf.d/
1499 Any files found in /etc/conf.d/ will be sourced in the initramfs to
1500 set initial values. Command line options will override these values
1501 set in the configuration files.
1502 /etc/cmdline
1504 Can contain additional command line options. Deprecated, better use
1505 /etc/cmdline.d/*.conf.
1506 /etc/cmdline.d/*.conf
1508 Can contain additional command line options.
1509
1511 Harald Hoyer
1512
1514 dracut(8) dracut.conf(5)
1515
1517 1. rfc4173
1518 http://tools.ietf.org/html/rfc4173#section-5
1519dracut b15d29d 11/16/2023 DRACUT.CMDLINE(7)