hank-test/quick-docs
1
0
Fork 0
mirror of https://pagure.io/fedora-docs/quick-docs.git synced 2024-10-18 09:21:50 +00:00
Code Issues 1 Projects Releases Packages Wiki Activity Actions

chore(dracut): update internal links

Browse source 
Ref: https://pagure.io/fedora-docs/quick-docs/issue/641
This commit is contained in:
Ankur Sinha (Ankur Sinha Gmail) 2023-11-21 06:35:56 +00:00
parent f9bb9c04c9
commit dfb5b00d63
No known key found for this signature in database
GPG key ID: F8D8C0BEBAC898BD
1 changed files with 15 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
modules/ROOT/pages/debug-dracut-problems.adoc
View file

@ -1,7 +1,7 @@
= How to debug Dracut problems
Caleb McKee; Héctor Louzao; Frank Sträter
:revnumber: all
:revdate: 2021-02-02
:revdate: 2022-11-21
:category: Bugs
:tags: How-to, Bug-Report, kernel, dracut
//:imagesdir: ./images
@ -11,7 +11,7 @@ Caleb McKee; Héctor Louzao; Frank Sträter
*Foreword*
If you are experiencing a problem with system initialization due to
Dracut, please see the link:Bugs/Common[common bugs] document before
Dracut, please see the link:https://discussion.fedoraproject.org/c/ask/common-issues/82/none[common bugs] document before
filing a bug. Some easy configuration tweaks that fix a wide range of
issues may be listed there. If the problem you are seeing is not listed
there or none of the workarounds seem to help, please consider filing a
@ -53,7 +53,7 @@ report:
the command `dmsetup ls -- tree`
* A list of block device attributes including vol_id compatible mode.
This can be obtained by running the commands `blkid` and `blkid -o udev`
* Turn on dracut debugging (see link:How_to_debug_Dracut_problems#Debugging[the 'debugging dracut'
* Turn on dracut debugging (see link:#debugging-dracut[the 'debugging dracut'
section]), and attach all relevant information from the boot log. This
can be obtained by running the command `dmesg|grep dracut`
* If you use a dracut configuration file, please include `/etc/dracut.conf`
@ -62,7 +62,7 @@ report:
=== Logical Volume Management related problems
As well as the information from
link:How_to_debug_Dracut_problems#AllInfo[the 'all bug reports'
link:#all-bug-reports[the 'all bug reports'
section], include the following information:
* Include physical volume information by running the command: `lvm pvdisplay`
@ -73,7 +73,7 @@ section], include the following information:
=== Software RAID related problems
As well as the information from
link:How_to_debug_Dracut_problems#AllInfo[the 'all bug reports'
link:#all-bug-reports[the 'all bug reports'
section], include the following information:
* If using software RAID disk partitions, please include the output of `/proc/mdstat`
@ -85,7 +85,7 @@ Network root device related problems
This section details information to include when experiencing problems
on a system whose root device is located on a network attached volume
(e.g. iSCSI, NFS or NBD). As well as the information from
link:How_to_debug_Dracut_problems#AllInfo[the 'all bug reports'
link:#all-bug-reports[the 'all bug reports'
section], include the following information:
* Please include the output of
@ -167,7 +167,7 @@ sh: can't access tty; job control turned off
....
Use this shell prompt to gather the information requested above (see
link:How_to_debug_Dracut_problems#AllInfo[the 'all bug reports'
link:#all-bug-reports[the 'all bug reports'
section]).
[[accessing-the-root-volume-from-the-dracut-shell]]
@ -220,8 +220,11 @@ Number Start End Size Type File system Flags
/dev/mapper/linux-swap: UUID="47b4d329-975c-4c08-b218-f9c9bf3635f1" TYPE="swap"
....
// TODO: this link needs to be replaced to point to new documentation
. From the output above, you recall that your root volume exists on an
encrypted block device. Following the guidance disk encryption guidance
encrypted block device. Following the disk encryption guidance
from the
http://docs.fedoraproject.org/install-guide/f%7B%7BFedoraVersion%7D%7D/en-US/html/apcs04s04.html[
Installation Guide], you unlock your encrypted root volume.
@ -251,18 +254,18 @@ exit
A selection of the most common debugging related dracut options:
==== `*rd.shell*`
==== `*rd.shell*`
Drop to a shell, if the initramfs fails.
==== `*rd.debug*`
==== `*rd.debug*`
Set -x for the dracut shell.
==== `*rd.break=[cmdline|pre-udev|pre-trigger|initqueue|pre-mount|mount|pre-pivot|cleanup]*`
==== `*rd.break=[cmdline|pre-udev|pre-trigger|initqueue|pre-mount|mount|pre-pivot|cleanup]*`
Drop the shell on defined breakpoint (use
`egrep 'rd.?break' /usr/lib/dracut/modules.d/99base/init.sh` to find the
breakpoints supported by your dracut version)
==== `*rd.udev.info*`
==== `*rd.udev.info*`
Set udev to loglevel info
==== `*rd.udev.debug*`
@ -271,9 +274,3 @@ Set udev to loglevel debug
See the `dracut.cmdline(7)`
https://man7.org/linux/man-pages/man7/dracut.cmdline.7.html[man page] for
the complete reference.
Category:Debugging[D] Category:How_to[Category:How to]
'''
See a typo, something missing or out of date, or anything else which can be
improved? Edit this document at https://pagure.io/fedora-docs/quick-docs.