diff options
author | jakobrs <jakobrs100@gmail.com> | 2020-06-17 13:36:06 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-06-17 15:36:06 +0200 |
commit | 2ee84ca8e2adb0ef5b5ea52ad38fe0e107893d3e (patch) | |
tree | de2732e69a59633acf8469bed466f15a0bfc5240 /nixos/doc/manual | |
parent | dda2dd12835a7866c79254d9b9d14dbc57d1e475 (diff) |
nixos/manual: Document `boot.debug1mounts` and clarify what `exit` does with `shell_on_fail` (#89365)
* nixos/manual: document boot.debug1mounts * nixos/manual: clarify what `exit` does with shell_on_fail
Diffstat (limited to 'nixos/doc/manual')
-rw-r--r-- | nixos/doc/manual/administration/boot-problems.xml | 31 |
1 files changed, 28 insertions, 3 deletions
diff --git a/nixos/doc/manual/administration/boot-problems.xml b/nixos/doc/manual/administration/boot-problems.xml index 5fa0b29e6d624..badc374ebcfd9 100644 --- a/nixos/doc/manual/administration/boot-problems.xml +++ b/nixos/doc/manual/administration/boot-problems.xml @@ -19,9 +19,9 @@ </term> <listitem> <para> - Start a root shell if something goes wrong in stage 1 of the boot process - (the initial ramdisk). This is disabled by default because there is no - authentication for the root shell. + Allows the user to start a root shell if something goes wrong in stage 1 + of the boot process (the initial ramdisk). This is disabled by default + because there is no authentication for the root shell. </para> </listitem> </varlistentry> @@ -51,6 +51,22 @@ </varlistentry> <varlistentry> <term> + <literal>boot.debug1mounts</literal> + </term> + <listitem> + <para> + Like <literal>boot.debug1</literal> or + <literal>boot.debug1devices</literal>, but runs stage1 until all + filesystems that are mounted during initrd are mounted (see + <option><link linkend="opt-fileSystems._name__.neededForBoot">neededForBoot</link></option> + ). As a motivating example, this could be useful if you've forgotten to set + <option><link linkend="opt-fileSystems._name__.neededForBoot">neededForBoot</link></option> + on a file system. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> <literal>boot.trace</literal> </term> <listitem> @@ -91,6 +107,15 @@ </para> <para> + Notice that for <literal>boot.shell_on_fail</literal>, + <literal>boot.debug1</literal>, <literal>boot.debug1devices</literal>, and + <literal>boot.debug1mounts</literal>, if you did <emphasis>not</emphasis> + select "start the new shell as pid 1", and you <literal>exit</literal> from + the new shell, boot will proceed normally from the point where it failed, as + if you'd chosen "ignore the error and continue". + </para> + + <para> If no login prompts or X11 login screens appear (e.g. due to hanging dependencies), you can press Alt+ArrowUp. If you’re lucky, this will start rescue mode (described above). (Also note that since most units have a |