docs-commits September 2014

docs-commits@lists.fedoraproject.org

5 participants
89 discussions

[install-guide/F21-rewrite] Some better phrasing in Troubleshooting
by pbokoc 13 Sep '14

13 Sep '14

commit 8ac1b3b2ca51f1104af0640fa9fdb70c9667632d Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Sat Sep 13 21:12:19 2014 +0200 Some better phrasing in Troubleshooting en-US/Troubleshooting.xml | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) --- diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml index 45a01d8..21531c7 100644 --- a/en-US/Troubleshooting.xml +++ b/en-US/Troubleshooting.xml @@ -39,14 +39,14 @@ </itemizedlist> <note> <para> - The above list is by no means complete - you can find help in many other places as well. You can find additional information about available resources such as IRC channels and mailing lists at <ulink url="https://fedoraproject.org/wiki/Communicating_and_getting_help" />. + The above list is by no means complete - you can find help in many other places as well. Additional information about available resources such as IRC channels and mailing lists is available at <ulink url="https://fedoraproject.org/wiki/Communicating_and_getting_help" />. </para> </note> <para> Before you open a new discussion or ask anyone for help on IRC, you should always do some research on your own. If you are encountering an issue, there is usually a good chance that someone else ran into the same problem before you and published a solution somewhere. Opening a discussion about something already explained elsewhere, or asking a common question which has been answered many times before, is not likely to result in a friendly, constructive response. </para> <para> - When troubleshooting issues related to the installation, you might be asked to provide log files. The sections below explains which log files are generated during the installation and how to obtain them. + When you ask for help troubleshooting problems related to the installation, you may be asked to provide log files generated by the installer. The sections below explain which files are generated, what their contents are, and how to transfer them from the installation system. </para> <section id="sect-troubleshooting-log-files">

1 0

[install-guide/F21-rewrite] Moved Kickstart Syntax into an appendix and changed structure
by pbokoc 13 Sep '14

13 Sep '14

commit 42cfe809a4162ba2fecf25a4fec4e79f1134995b Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Sat Sep 13 21:10:01 2014 +0200 Moved Kickstart Syntax into an appendix and changed structure en-US/Installation_Guide.xml | 5 +- en-US/Kickstart_Installations.xml | 52 ----- en-US/Kickstart_Syntax_Reference.xml | 403 ++++++++++++++++++++++++++++++++++ 3 files changed, 406 insertions(+), 54 deletions(-) --- diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml index 3ee0a65..f5e4cdf 100644 --- a/en-US/Installation_Guide.xml +++ b/en-US/Installation_Guide.xml @@ -37,14 +37,15 @@ <xi:include href="Upgrading_Your_Current_System.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </part> - + <xi:include href="Kickstart_Syntax_Reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </part> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <index /> diff --git a/en-US/Kickstart_Installations.xml b/en-US/Kickstart_Installations.xml index da1d348..ece14fe 100644 --- a/en-US/Kickstart_Installations.xml +++ b/en-US/Kickstart_Installations.xml @@ -74,56 +74,4 @@ </section> - <section id="sect-kickstart-syntax"> - <title>Kickstart Syntax Reference</title> - - <section id="sect-kickstart-syntax-changes"> - <title>Changes in Kickstart Syntax</title> - <para> - text - </para> - </section> - - <section id="sect-kickstart-commands"> - <title>Kickstart Commands and Options</title> - <para> - text - </para> - </section> - - <section id="sect-kickstart-packages"> - <title>Package Selection</title> - <para> - text - </para> - </section> - - <section id="sect-kickstart-preinstall"> - <title>Pre-installation Script</title> - <para> - text - </para> - </section> - - <section id="sect-kickstart-postinstall"> - <title>Post-installation Script</title> - <para> - text - </para> - </section> - - </section> - - <section id="sect-kickstart-examples"> - <title>Sample Kickstart Configurations</title> - - <section id="sect-kickstart-partitioning-example"> - <title>Advanced Partitioning Example</title> - <para> - text - </para> - </section> - - </section> - </chapter> diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml new file mode 100644 index 0000000..a690a44 --- /dev/null +++ b/en-US/Kickstart_Syntax_Reference.xml @@ -0,0 +1,403 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> +%BOOK_ENTITIES; +]> +<appendix id="appe-kickstart-syntax-reference"> + <title>Kickstart Syntax Reference</title> + <para> + intro text + </para> + + <section id="sect-kickstart-syntax-changes"> + <title>Changes in Kickstart Syntax</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands"> + <title>Kickstart Commands and Options</title> + <para> + text + </para> + + <section id="sect-kickstart-commands-auth"> + <title>auth - Configure Authentication</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-autopart"> + <title>autopart - Automatic Partitioning</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-autostep"> + <title>autostep - Go Through Every Screen Automatically</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-bootloader"> + <title>bootloader - Configure Boot Loader</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-btrfs"> + <title>btrfs - Create Btrfs Volume or Subvolume</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-clearpart"> + <title>clearpart - Remove All Existing Partitions</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-cmdline"> + <title>cmdline - Perform Installation in Command Line Mode</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-device"> + <title>device - Install Extra Device Drivers</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-driverdisk"> + <title>driverdisk - Use a Driver Disk</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-eula"> + <title>eula - Accept the License Agreement</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-fcoe"> + <title>fcoe - Configure Fibre Channel Over Ethernet Devices</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-firewall"> + <title>firewall - Configure Firewall</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-firstboot"> + <title>firstboot - Enable or Disable Initial Setup</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-group"> + <title>group - Create User Group</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-graphical"> + <title>graphical - Perform Installation in Graphical Mode</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-halt"> + <title>halt - Halt System After Installation</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-ignoredisk"> + <title>ignoredisk - Ignore Specified Disks</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-install"> + <title>install - Configure Installation Method</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-iscsi"> + <title>iscsi - Configure iSCSI Devices</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-iscsiname"> + <title>iscsiname - Assign Name to iSCSI Device</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-keyboard"> + <title>keyboard - Configure Keyboard Layouts</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-lang"> + <title>lang - Configure Language During Installation</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-logging"> + <title>logging - Configure Error Logging During Installation</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-logvol"> + <title>logvol - Create LVM Logical Volume</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-mediacheck"> + <title>mediacheck - Verify Installation Media Integrity</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-network"> + <title>network - Configure Network Interfaces</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-part"> + <title>part - Create Physical Partition</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-poweroff"> + <title>poweroff - Power Off After Installation</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-raid"> + <title>raid - Create Software RAID</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-realm"> + <title>realm - Join AD or IPA Domain</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-reboot"> + <title>reboot - Reboot After Installation</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-repo"> + <title>repo - Configure Instalaltion Source</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-rescue"> + <title>rescue - Rescue Mode</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-rootpw"> + <title>rootpw - Set Root Password</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-selinux"> + <title>selinux - Configure SELinux</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-services"> + <title>services - Configure Services</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-shutdown"> + <title>shutdown - Shut Down After Installation</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-skipx"> + <title>skipx - Do Not Configure X Window System</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-sshpw"> + <title>sshpw - Restrict ssh Access During Installation</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-text"> + <title>text - Perform Installation in Text Mode</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-timezone"> + <title>timezone - Configure Time Zone</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-unsupported_hardware"> + <title>unsupported_hardware - Suppress Unsupported Hardware Alerts</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-user"> + <title>user - Create User Accound</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-vnc"> + <title>vnc - Configure VNC Access</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-volgroup"> + <title>volgroup - Create LVM Volume Group</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-xconfig"> + <title>xconfig - Configure X Window System</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-zerombr"> + <title>zerombr - Reinitialize Partition Tables</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-zfcp"> + <title>zfcp - Configure Fibre Channel Device</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-commands-include"> + <title>%include - Include Contents of Another File</title> + <para> + text + </para> + </section> + + </section> + + <section id="sect-kickstart-packages"> + <title>Package Selection</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-preinstall"> + <title>Pre-installation Script</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-postinstall"> + <title>Post-installation Script</title> + <para> + text + </para> + </section> + + <section id="sect-kickstart-examples"> + <title>Example Kickstart Configurations</title> + + <section id="sect-kickstart-partitioning-example"> + <title>Advanced Partitioning Example</title> + <para> + text + </para> + </section> + + </section> + +</appendix> \ No newline at end of file

1 0

[install-guide/F21-rewrite] Changed a few links in Troubleshooting - Getting Help
by pbokoc 13 Sep '14

13 Sep '14

commit 893e617601b965df904688ece6f9a4490c4642f1 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Sat Sep 13 21:09:26 2014 +0200 Changed a few links in Troubleshooting - Getting Help en-US/Troubleshooting.xml | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) --- diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml index 060adab..45a01d8 100644 --- a/en-US/Troubleshooting.xml +++ b/en-US/Troubleshooting.xml @@ -28,18 +28,18 @@ </listitem> <listitem> <para> - <ulink url="http://unix.stackexchange.com/">Stack Exchange</ulink> - an English language Q&A board, not specific to Fedora + <ulink url="https://fedoraproject.org/wiki/">Fedora Project Wiki</ulink> - the official wiki for Fedora Project </para> </listitem> <listitem> <para> - <ulink url="http://www.phoronix.com/forums/">Phoronix Forums</ulink> - an English language forum, not specific to Fedora + <ulink url="http://unix.stackexchange.com/">Stack Exchange</ulink> - an English language Q&A board, not specific to Fedora </para> </listitem> </itemizedlist> <note> <para> - The above list is by no means complete - you can find help in many other places as well. + The above list is by no means complete - you can find help in many other places as well. You can find additional information about available resources such as IRC channels and mailing lists at <ulink url="https://fedoraproject.org/wiki/Communicating_and_getting_help" />. </para> </note> <para>

1 0

[install-guide/F21-rewrite] Added intro to troubleshooting
by pbokoc 13 Sep '14

13 Sep '14

commit 8b7c66b17d7084c47ac48c5b2e9acb4474f6cad6 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Sat Sep 13 19:34:42 2014 +0200 Added intro to troubleshooting en-US/Troubleshooting.xml | 35 ++++++++++++++++++++++++++++++++++- 1 files changed, 34 insertions(+), 1 deletions(-) --- diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml index 0bdc31f..060adab 100644 --- a/en-US/Troubleshooting.xml +++ b/en-US/Troubleshooting.xml @@ -13,7 +13,40 @@ <section id="sect-troubleshooting-getting-help"> <title>Getting Help</title> <para> - text about ask.fedora.com, stackexchange, phoronix etc. + There are many places on the internet which can help you when you encounter a problem not described in this chapter: discussion boards, blogs, IRC, and more. Some of the more popular places where you can find help include: + </para> + <itemizedlist> + <listitem> + <para> + <ulink url="https://ask.fedoraproject.org/en/questions/">Ask Fedora</ulink> - Fedora's knowledge base, available in multiple languages + </para> + </listitem> + <listitem> + <para> + The #fedora IRC channel on <ulink url="http://freenode.net/">FreeNode</ulink> - one of the main IRC channels used by Fedora users, English only + </para> + </listitem> + <listitem> + <para> + <ulink url="http://unix.stackexchange.com/">Stack Exchange</ulink> - an English language Q&A board, not specific to Fedora + </para> + </listitem> + <listitem> + <para> + <ulink url="http://www.phoronix.com/forums/">Phoronix Forums</ulink> - an English language forum, not specific to Fedora + </para> + </listitem> + </itemizedlist> + <note> + <para> + The above list is by no means complete - you can find help in many other places as well. + </para> + </note> + <para> + Before you open a new discussion or ask anyone for help on IRC, you should always do some research on your own. If you are encountering an issue, there is usually a good chance that someone else ran into the same problem before you and published a solution somewhere. Opening a discussion about something already explained elsewhere, or asking a common question which has been answered many times before, is not likely to result in a friendly, constructive response. + </para> + <para> + When troubleshooting issues related to the installation, you might be asked to provide log files. The sections below explains which log files are generated during the installation and how to obtain them. </para> <section id="sect-troubleshooting-log-files">

1 0

[install-guide/F21-rewrite] Missing word in troubleshooting
by pbokoc 07 Sep '14

07 Sep '14

commit 1f4926b6642a732191b24e6d875b6347ef22a77c Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Sun Sep 7 21:24:50 2014 +0200 Missing word in troubleshooting en-US/Troubleshooting.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml index 555a28e..0bdc31f 100644 --- a/en-US/Troubleshooting.xml +++ b/en-US/Troubleshooting.xml @@ -638,7 +638,7 @@ tmpfs 1.8G 2.6M 1.8G 1% /tmp </para> <note> <para> - If you have 4GB or more memory installed, but &PRODUCT; only shows around 3.5GB or 3.7GB, you have probably installed a 32-bit version of &PRODUCT; on a 64bit kernel. For modern systems, the 64-bit (x86_64) version. + If you have 4GB or more memory installed, but &PRODUCT; only shows around 3.5GB or 3.7GB, you have probably installed a 32-bit version of &PRODUCT; on a 64bit kernel. For modern systems, use the 64-bit (x86_64) version. </para> <para> Some hardware configurations have a part of the system's RAM reserved and unavailable to the main system. Notably, laptop computers with integrated graphics cards will reserve some memory for the GPU. For example, a laptop with 4 GB of RAM and an integrated Intel graphics card will show only roughly 3.7 GB of available memory, even with a 64-bit system.

1 0

[install-guide/F21-rewrite] Better structure in Troubleshooting
by pbokoc 07 Sep '14

07 Sep '14

commit 88d9ad2166256c7a8ef59bbd98b494888ac941d8 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Sun Sep 7 21:20:45 2014 +0200 Better structure in Troubleshooting en-US/Troubleshooting.xml | 340 ++++++++++++++++++++++++--------------------- 1 files changed, 180 insertions(+), 160 deletions(-) --- diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml index 98e4417..555a28e 100644 --- a/en-US/Troubleshooting.xml +++ b/en-US/Troubleshooting.xml @@ -7,189 +7,209 @@ <chapter id="chap-troubleshooting"> <title>Troubleshooting</title> <para> - This chapter discusses some common installation problems and their solutions. + This chapter offers some pointers on how to get help when something goes wrong. It also discusses some common installation problems and their solutions. </para> - <section id="chap-troubleshooting-log-files"> - <title>Log Files Generated During the Installation</title> + <section id="sect-troubleshooting-getting-help"> + <title>Getting Help</title> <para> - For debugging purposes, <application>Anaconda</application> logs installation actions into files in the <filename>/tmp</filename> directory. These files are listed in the following table. + text about ask.fedora.com, stackexchange, phoronix etc. </para> - <table id="tabl-installation-log-files"> - <title>Log Files and Their Contents</title> - <tgroup cols="2"> - <colspec colname="c1" colwidth="1*" /> - <colspec colname="c2" colwidth="2*" /> - <thead> - <row> - <entry> - Log file - </entry> - <entry> - Contents - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <filename>/tmp/anaconda.log</filename> - </entry> - <entry> - general <application>Anaconda</application> messages - </entry> - </row> - <row> - <entry> - <filename>/tmp/program.log</filename> - </entry> - <entry> - all external programs run during the installation - </entry> - </row> - <row> - <entry> - <filename>/tmp/storage.log</filename> - </entry> - <entry> - extensive storage module information - </entry> - </row> - <row> - <entry> - <filename>/tmp/packaging.log</filename> - </entry> - <entry> - <application>yum</application> and <application>rpm</application> package installation messages - </entry> - </row> - <row> - <entry> - <filename>/tmp/syslog</filename> - </entry> - <entry> - hardware-related system messages - </entry> - </row> - </tbody> - </tgroup> - </table> - <para> - If the installation fails, the messages from these files are consolidated into <filename>/tmp/anaconda-tb-<replaceable>identifier</replaceable></filename>, where <replaceable>identifier</replaceable> is a random string. - </para> - <para> - All of the files listed above reside in the installation program's RAM disk, which means they are not saved permamently and will be lost once the system is powered down. To store them permanently, copy those files to another system on the network using <command>scp</command> on the system running the installation program, or copy them to a mounted storage device (such as an USB flash drive). Details on how to transfer the log files are below. Note that if you use an USB flash drive or other removable media, you should make sure to back up any data on it before starting the procedure. - </para> - <procedure> - <title>Transferring Log Files Onto a USB Drive</title> - <step> - <para> - On the system you are installing, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap></keycombo> to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system. - </para> - </step> - <step> - <para> - Connect a USB flash drive to the system and execute the <command>dmesg</command> command. A log detailing all recent events will be displayed. At the bottom of this log, you will see a set of messages caused by the USB flash drive you just connected. It will look like a set of lines similar to the following: - </para> - <screen> + + <section id="sect-troubleshooting-log-files"> + <title>Log Files Generated During the Installation</title> + <para> + For debugging purposes, <application>Anaconda</application> logs installation actions into files in the <filename>/tmp</filename> directory. These files are listed in the following table. + </para> + <table id="tabl-installation-log-files"> + <title>Log Files and Their Contents</title> + <tgroup cols="2"> + <colspec colname="c1" colwidth="1*" /> + <colspec colname="c2" colwidth="2*" /> + <thead> + <row> + <entry> + Log file + </entry> + <entry> + Contents + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <filename>/tmp/anaconda.log</filename> + </entry> + <entry> + general <application>Anaconda</application> messages + </entry> + </row> + <row> + <entry> + <filename>/tmp/program.log</filename> + </entry> + <entry> + all external programs run during the installation + </entry> + </row> + <row> + <entry> + <filename>/tmp/storage.log</filename> + </entry> + <entry> + extensive storage module information + </entry> + </row> + <row> + <entry> + <filename>/tmp/packaging.log</filename> + </entry> + <entry> + <application>yum</application> and <application>rpm</application> package installation messages + </entry> + </row> + <row> + <entry> + <filename>/tmp/syslog</filename> + </entry> + <entry> + hardware-related system messages + </entry> + </row> + </tbody> + </tgroup> + </table> + <para> + If the installation fails, the messages from these files are consolidated into <filename>/tmp/anaconda-tb-<replaceable>identifier</replaceable></filename>, where <replaceable>identifier</replaceable> is a random string. + </para> + </section> + + <section id="sect-troubleshooting-transferring-logs"> + <title>Transferring Log Files from the Installation System</title> + <para> + All of the files described in <xref linkend="sect-troubleshooting-log-files" /> reside in the installation program's RAM disk, which means they are not saved permamently and will be lost once the system is powered down. To store them permanently, copy those files to another system on the network using <command>scp</command> on the system running the installation program, or copy them to a mounted storage device (such as an USB flash drive). Details on how to transfer the log files are below. Note that if you use an USB flash drive or other removable media, you should make sure to back up any data on it before starting the procedure. + </para> + + <section id="sect-troubleshooting-transferring-logs-usb"> + <title>Transferring Log Files Onto a USB Drive</title> + <procedure> + <step> + <para> + On the system you are installing, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap></keycombo> to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system. + </para> + </step> + <step> + <para> + Connect a USB flash drive to the system and execute the <command>dmesg</command> command. A log detailing all recent events will be displayed. At the bottom of this log, you will see a set of messages caused by the USB flash drive you just connected. It will look like a set of lines similar to the following: + </para> + <screen> <computeroutput>[ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk</computeroutput> - </screen> - <para> - Note the name of the connected device - in the above example, it is <literal>sdb</literal>. - </para> - </step> - <step> - <para> - Go to the <filename>/mnt</filename> directory and once there, create new directory which will serve as the mount target for the USB drive. The name of the directory does not matter; this example uses the name <literal>usb</literal>. - </para> - <screen> + </screen> + <para> + Note the name of the connected device - in the above example, it is <literal>sdb</literal>. + </para> + </step> + <step> + <para> + Go to the <filename>/mnt</filename> directory and once there, create new directory which will serve as the mount target for the USB drive. The name of the directory does not matter; this example uses the name <literal>usb</literal>. + </para> + <screen> <prompt>#</prompt> <command>mkdir usb</command> - </screen> - </step> - <step> - <para> - Mount the USB flash drive onto the newly created directory. Note that in most cases, you do not want to mount the whole drive, but a partition on it. Therefore, do not use the name <literal>sdb</literal> - use the name of the partition you want to write the log files to. In this example, the name <literal>sdb1</literal> is used. - </para> - <screen> + </screen> + </step> + <step> + <para> + Mount the USB flash drive onto the newly created directory. Note that in most cases, you do not want to mount the whole drive, but a partition on it. Therefore, do not use the name <literal>sdb</literal> - use the name of the partition you want to write the log files to. In this example, the name <literal>sdb1</literal> is used. + </para> + <screen> <prompt>#</prompt> <command>mount /dev/sdb1 /mnt/usb</command> - </screen> - <para> - You can now verify that you mounted the correct device and partition by accessing it and listing its contents - the list should match what you expect to be on the drive. - </para> - <screen> + </screen> + <para> + You can now verify that you mounted the correct device and partition by accessing it and listing its contents - the list should match what you expect to be on the drive. + </para> + <screen> <prompt>#</prompt> <command>cd /mnt/usb</command> - </screen> - <screen> + </screen> + <screen> <prompt>#</prompt> <command>ls</command> - </screen> - </step> - <step> - <para> - Copy the log files to the mounted device. - </para> - <screen> + </screen> + </step> + <step> + <para> + Copy the log files to the mounted device. + </para> + <screen> <prompt>#</prompt> <command>cp /tmp/*log /mnt/usb</command> - </screen> - </step> - <step> - <para> - Unmount the USB flash drive. If you get an error message saying that the target is busy, change your working directory to outside the mount (for example, <filename>/</filename>). - </para> - <screen> + </screen> + </step> + <step> + <para> + Unmount the USB flash drive. If you get an error message saying that the target is busy, change your working directory to outside the mount (for example, <filename>/</filename>). + </para> + <screen> <prompt>#</prompt> <command>umount /mnt/usb</command> - </screen> - </step> - </procedure> - <para> - The log files from the installation are now saved on the USB flash drive. - </para> - - <procedure> - <title>Transferring Log Files Over the Network</title> - <step> + </screen> + </step> + </procedure> <para> - On the system you are installing, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap></keycombo> to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system. + The log files from the installation are now saved on the USB flash drive. </para> - </step> - <step> - <para> - Switch to the <filename class="directory">/tmp</filename> directory where the log files are located: - </para> - <screen> + </section> + + <section id="sect-troubleshooting-transferring-logs-network"> + <title>Transferring Log Files Over the Network</title> + <procedure> + <step> + <para> + On the system you are installing, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap></keycombo> to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system. + </para> + </step> + <step> + <para> + Switch to the <filename class="directory">/tmp</filename> directory where the log files are located: + </para> + <screen> <prompt>#</prompt> <command>cd /tmp</command> - </screen> - </step> - <step> - <para> - Copy the log files onto another system on the network using the <command>scp</command> command: - </para> - <screen> + </screen> + </step> + <step> + <para> + Copy the log files onto another system on the network using the <command>scp</command> command: + </para> + <screen> <prompt>#</prompt> <command>scp *log <replaceable>user</replaceable>@<replaceable>address</replaceable>:<replaceable>path</replaceable></command> - </screen> - <para> - Replace <replaceable>user</replaceable> with a valid user name on the target system, <replaceable>address</replaceable> with the target system's address or host name, and <replaceable>path</replaceable> with the path to the directory you wish to save the log files into. For example, if you want to log in as <systemitem class="username">john</systemitem> to a system with an IP address of <systemitem>192.168.0.122</systemitem> and place the log files into the <filename class="directory">/home/john/logs/</filename> directory on that system, the command will have the following form: - </para> - <screen> + </screen> + <para> + Replace <replaceable>user</replaceable> with a valid user name on the target system, <replaceable>address</replaceable> with the target system's address or host name, and <replaceable>path</replaceable> with the path to the directory you wish to save the log files into. For example, if you want to log in as <systemitem class="username">john</systemitem> to a system with an IP address of <systemitem>192.168.0.122</systemitem> and place the log files into the <filename class="directory">/home/john/logs/</filename> directory on that system, the command will have the following form: + </para> + <screen> <prompt>#</prompt> <command>scp *log john@192.168.0.122:/home/john/logs/</command> - </screen> - <para> - When connecting to the target system for the first time, you may encounter a message similar to the following: - </para> - <screen> + </screen> + <para> + When connecting to the target system for the first time, you may encounter a message similar to the following: + </para> + <screen> <computeroutput>The authenticity of host '192.168.0.122 (192.168.0.122)' can't be established.</computeroutput> <computeroutput>ECDSA key fingerprint is a4:60:76:eb:b2:d0:aa:23:af:3d:59:5c:de:bb:c4:42.</computeroutput> <computeroutput>Are you sure you want to continue connecting (yes/no)?</computeroutput> - </screen> + </screen> + <para> + Type <literal>yes</literal> and press <keycap>Enter</keycap> to continue. Then, provide a valid password when prompted. The files will start transferring to the specified directory on the target system. + </para> + </step> + </procedure> <para> - Type <literal>yes</literal> and press <keycap>Enter</keycap> to continue. Then, provide a valid password when prompted. The files will start transferring to the specified directory on the target system. + The log files from the installation are now permanently saved on the target system and available for review. </para> - </step> - </procedure> - <para> - The log files from the installation are now permanently saved on the target system and available for review. - </para> + </section> + + </section> + </section> + + <section id="sect-troubleshooting-problems-beginning-installation"> <title>Trouble Beginning the Installation</title>

1 0

[install-guide/F21-rewrite] Removing a reference to RHEL & adding a note about 32-bit systems to Troubleshooting
by pbokoc 07 Sep '14

07 Sep '14

commit 4fff2c6a6d3c901e5dc7f37aafa9c5d2c51e71d0 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Sun Sep 7 21:11:53 2014 +0200 Removing a reference to RHEL & adding a note about 32-bit systems to Troubleshooting en-US/Troubleshooting.xml | 9 ++++++--- 1 files changed, 6 insertions(+), 3 deletions(-) --- diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml index a2f2a7a..98e4417 100644 --- a/en-US/Troubleshooting.xml +++ b/en-US/Troubleshooting.xml @@ -444,7 +444,7 @@ <section id="sect-troubleshooting-problems-after-installation"> <title>Problems After Installation</title> - <section> + <section id="sect-trouble-after-raid"> <title>Are You Unable to Boot With Your RAID Card?</title> <para> If you have performed an installation and cannot boot your system properly, you may need to reinstall and partition your system's storage differently. @@ -529,7 +529,7 @@ GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([ - </step> </procedure> <para> - After you finish this procedure, you can reboot your computer. Red Hat Enterprise Linux will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the <literal>rhgb</literal> option to the <literal>GRUB_CMDLINE_LINUX</literal> line in the <filename>/etc/default/grub</filename> file and refresh the boot loader configuration again using the <command>grub2-mkconfig</command> command. + After you finish this procedure, you can reboot your computer. &PRODUCT; will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the <literal>rhgb</literal> option to the <literal>GRUB_CMDLINE_LINUX</literal> line in the <filename>/etc/default/grub</filename> file and refresh the boot loader configuration again using the <command>grub2-mkconfig</command> command. </para> <para> See the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org">Fedora Documentation website</ulink>, for more information about working with the <application>GRUB2</application> boot loader. @@ -618,7 +618,10 @@ tmpfs 1.8G 2.6M 1.8G 1% /tmp </para> <note> <para> - Some hardware configurations have a part of the system's RAM reserved and unavailable to the main system. Notably, laptop computers with integrated graphics cards will reserve some memory for the GPU. For example, a laptop with 4 GB of RAM and an integrated Intel graphics card will show only roughly 3.7 GB of available memory. + If you have 4GB or more memory installed, but &PRODUCT; only shows around 3.5GB or 3.7GB, you have probably installed a 32-bit version of &PRODUCT; on a 64bit kernel. For modern systems, the 64-bit (x86_64) version. + </para> + <para> + Some hardware configurations have a part of the system's RAM reserved and unavailable to the main system. Notably, laptop computers with integrated graphics cards will reserve some memory for the GPU. For example, a laptop with 4 GB of RAM and an integrated Intel graphics card will show only roughly 3.7 GB of available memory, even with a 64-bit system. </para> <para> Additionally, the <application>kdump</application> crash kernel dumping mechanism reserves some memory for the secondary kernel used in case of the primary kernel crashing. This reserved memory will also not be displayed as available when using the <command>free</command> command. For details about <application>kdump</application> and its memory requirements, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org">Fedora Documentation website</ulink>.

1 0

[install-guide/F21-rewrite] Putting back Troubleshooting
by pbokoc 07 Sep '14

07 Sep '14

commit 2496c8bfffbba338abaddc5b35c695bcb16a5974 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Sun Sep 7 20:50:00 2014 +0200 Putting back Troubleshooting en-US/Troubleshooting.xml | 714 +++++++++++++++++++++++++++++++++++++++++++-- 1 files changed, 689 insertions(+), 25 deletions(-) --- diff --git a/en-US/Troubleshooting.xml b/en-US/Troubleshooting.xml index 4ff814c..a2f2a7a 100644 --- a/en-US/Troubleshooting.xml +++ b/en-US/Troubleshooting.xml @@ -3,31 +3,695 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent"> %BOOK_ENTITIES; ]> + <chapter id="chap-troubleshooting"> - <title>Troubleshooting</title> - <para> - intro text - </para> - - <section id="sect-troubleshooting-starting-installation"> - <title>Problems Starting the Installation</title> - <para> - text - </para> - </section> - - <section id="sect-troubleshooting-during-installation"> - <title>Problems During the Installation</title> - <para> - text - </para> - </section> - - <section id="sect-troubleshooting-after-installation"> - <title>Problems After the Installation</title> - <para> - text - </para> - </section> + <title>Troubleshooting</title> + <para> + This chapter discusses some common installation problems and their solutions. + </para> + + <section id="chap-troubleshooting-log-files"> + <title>Log Files Generated During the Installation</title> + <para> + For debugging purposes, <application>Anaconda</application> logs installation actions into files in the <filename>/tmp</filename> directory. These files are listed in the following table. + </para> + <table id="tabl-installation-log-files"> + <title>Log Files and Their Contents</title> + <tgroup cols="2"> + <colspec colname="c1" colwidth="1*" /> + <colspec colname="c2" colwidth="2*" /> + <thead> + <row> + <entry> + Log file + </entry> + <entry> + Contents + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <filename>/tmp/anaconda.log</filename> + </entry> + <entry> + general <application>Anaconda</application> messages + </entry> + </row> + <row> + <entry> + <filename>/tmp/program.log</filename> + </entry> + <entry> + all external programs run during the installation + </entry> + </row> + <row> + <entry> + <filename>/tmp/storage.log</filename> + </entry> + <entry> + extensive storage module information + </entry> + </row> + <row> + <entry> + <filename>/tmp/packaging.log</filename> + </entry> + <entry> + <application>yum</application> and <application>rpm</application> package installation messages + </entry> + </row> + <row> + <entry> + <filename>/tmp/syslog</filename> + </entry> + <entry> + hardware-related system messages + </entry> + </row> + </tbody> + </tgroup> + </table> + <para> + If the installation fails, the messages from these files are consolidated into <filename>/tmp/anaconda-tb-<replaceable>identifier</replaceable></filename>, where <replaceable>identifier</replaceable> is a random string. + </para> + <para> + All of the files listed above reside in the installation program's RAM disk, which means they are not saved permamently and will be lost once the system is powered down. To store them permanently, copy those files to another system on the network using <command>scp</command> on the system running the installation program, or copy them to a mounted storage device (such as an USB flash drive). Details on how to transfer the log files are below. Note that if you use an USB flash drive or other removable media, you should make sure to back up any data on it before starting the procedure. + </para> + <procedure> + <title>Transferring Log Files Onto a USB Drive</title> + <step> + <para> + On the system you are installing, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap></keycombo> to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system. + </para> + </step> + <step> + <para> + Connect a USB flash drive to the system and execute the <command>dmesg</command> command. A log detailing all recent events will be displayed. At the bottom of this log, you will see a set of messages caused by the USB flash drive you just connected. It will look like a set of lines similar to the following: + </para> + <screen> +<computeroutput>[ 170.171135] sd 5:0:0:0: [sdb] Attached SCSI removable disk</computeroutput> + </screen> + <para> + Note the name of the connected device - in the above example, it is <literal>sdb</literal>. + </para> + </step> + <step> + <para> + Go to the <filename>/mnt</filename> directory and once there, create new directory which will serve as the mount target for the USB drive. The name of the directory does not matter; this example uses the name <literal>usb</literal>. + </para> + <screen> +<prompt>#</prompt> <command>mkdir usb</command> + </screen> + </step> + <step> + <para> + Mount the USB flash drive onto the newly created directory. Note that in most cases, you do not want to mount the whole drive, but a partition on it. Therefore, do not use the name <literal>sdb</literal> - use the name of the partition you want to write the log files to. In this example, the name <literal>sdb1</literal> is used. + </para> + <screen> +<prompt>#</prompt> <command>mount /dev/sdb1 /mnt/usb</command> + </screen> + <para> + You can now verify that you mounted the correct device and partition by accessing it and listing its contents - the list should match what you expect to be on the drive. + </para> + <screen> +<prompt>#</prompt> <command>cd /mnt/usb</command> + </screen> + <screen> +<prompt>#</prompt> <command>ls</command> + </screen> + </step> + <step> + <para> + Copy the log files to the mounted device. + </para> + <screen> +<prompt>#</prompt> <command>cp /tmp/*log /mnt/usb</command> + </screen> + </step> + <step> + <para> + Unmount the USB flash drive. If you get an error message saying that the target is busy, change your working directory to outside the mount (for example, <filename>/</filename>). + </para> + <screen> +<prompt>#</prompt> <command>umount /mnt/usb</command> + </screen> + </step> + </procedure> + <para> + The log files from the installation are now saved on the USB flash drive. + </para> + + <procedure> + <title>Transferring Log Files Over the Network</title> + <step> + <para> + On the system you are installing, press <keycombo><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>F2</keycap></keycombo> to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system. + </para> + </step> + <step> + <para> + Switch to the <filename class="directory">/tmp</filename> directory where the log files are located: + </para> + <screen> +<prompt>#</prompt> <command>cd /tmp</command> + </screen> + </step> + <step> + <para> + Copy the log files onto another system on the network using the <command>scp</command> command: + </para> + <screen> +<prompt>#</prompt> <command>scp *log <replaceable>user</replaceable>@<replaceable>address</replaceable>:<replaceable>path</replaceable></command> + </screen> + <para> + Replace <replaceable>user</replaceable> with a valid user name on the target system, <replaceable>address</replaceable> with the target system's address or host name, and <replaceable>path</replaceable> with the path to the directory you wish to save the log files into. For example, if you want to log in as <systemitem class="username">john</systemitem> to a system with an IP address of <systemitem>192.168.0.122</systemitem> and place the log files into the <filename class="directory">/home/john/logs/</filename> directory on that system, the command will have the following form: + </para> + <screen> +<prompt>#</prompt> <command>scp *log john@192.168.0.122:/home/john/logs/</command> + </screen> + <para> + When connecting to the target system for the first time, you may encounter a message similar to the following: + </para> + <screen> +<computeroutput>The authenticity of host '192.168.0.122 (192.168.0.122)' can't be established.</computeroutput> +<computeroutput>ECDSA key fingerprint is a4:60:76:eb:b2:d0:aa:23:af:3d:59:5c:de:bb:c4:42.</computeroutput> +<computeroutput>Are you sure you want to continue connecting (yes/no)?</computeroutput> + </screen> + <para> + Type <literal>yes</literal> and press <keycap>Enter</keycap> to continue. Then, provide a valid password when prompted. The files will start transferring to the specified directory on the target system. + </para> + </step> + </procedure> + <para> + The log files from the installation are now permanently saved on the target system and available for review. + </para> + </section> + + <section id="sect-troubleshooting-problems-beginning-installation"> + <title>Trouble Beginning the Installation</title> + + <section> + <title>Problems with Booting into the Graphical Installation</title> + <para> + Systems with some video cards have trouble booting into the graphical installation program. If the installation program does not run using its default settings, it attempts to run in a lower resolution mode. If that still fails, the installation program attempts to run in text mode. + </para> + <para> + There are several possible solutions to display issues, most of which involve specifying custom boot options. For more information, see <xref linkend="sect-boot-options-installer" />. + </para> + <variablelist> + <varlistentry> + <term>Use the basic graphics mode</term> + <listitem> + <para> + You can attempt to perform the installation using the basic graphics driver. To do this, edit the installation program's boot options and append <option>inst.xdriver=vesa</option> at the end of the command line. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Specify the display resolution manually</term> + <listitem> + <para> + If the installation program fails to detect your screen resolution, you can override the automatic detection and specify it manually. To do this, append the <option>inst.resolution=<replaceable>x</replaceable></option> option at the boot menu, where <replaceable>x</replaceable> is your display's resolution (for example, <literal>1024x768</literal>). + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Use an alternate video driver</term> + <listitem> + <para> + You can also attempt to specify a custom video driver, overriding the installation program's automatic detection. To specify a driver, use the <option>inst.xdriver=<replaceable>x</replaceable></option> option, where <replaceable>x</replaceable> is the device driver you want to use (for example, <literal>nouveau</literal>). + </para> + <note> + <para> + If specifying a custom video driver solves your problem, you should report it as a bug at <ulink url="https://bugzilla.redhat.com" /> under the <literal>anaconda</literal> component. <application>Anaconda</application> should be able to detect your hardware automatically and use the appropriate driver without your intervention. + </para> + </note> + </listitem> + </varlistentry> + <varlistentry> + <term>Perform the installation using VNC</term> + <listitem> + <para> + If the above options fail, you can use a separate system to access the graphical installation over the network, using the <firstterm>Virtual Network Computing</firstterm> (VNC) protocol. For details on installing using VNC, see <xref linkend="chap-vnc-installations" />. + </para> + </listitem> + </varlistentry> + </variablelist> + </section> + + <section> + <title>Serial Console Not Detected</title> + <para> + In some cases, attempting to install in text mode using a serial console will result in no output on the console. This happens on systems which have a graphics card, but no monitor connected. If <application>Anaconda</application> detects a graphics card, it will attempt to use it for a display, even if no display is connected. + </para> + <para> + If you want to perform a text-based installation on a serial console, use the <option>inst.text</option> and <option>console=</option> boot options. See <xref linkend="chap-anaconda-boot-options" /> for more details. + </para> + </section> + + </section> + + <section id="sect-troubleshooting-problems-during-installation"> + <title>Trouble During the Installation</title> + + <section id="sect-trouble-during-no-target"> + <title>No Disks Detected</title> + <para> + In the <guilabel>Installation Destination</guilabel> screen, the following error message may appear at the bottom: <guilabel>No disks detected. Please shut down the computer, connect at least one disk, and restart to complete installation</guilabel>. + </para> + <para> + The message indicates that <application>Anaconda</application> did not find any writable storage devices to install to. In that case, first make sure that your system does have at least one storage device attached. + </para> + <para> + If your system uses a hardware RAID controller, verify that the controller is properly configured and working. See your controller's documentation for instructions. + </para> + <para> + If you are installing into one or more iSCSI devices and there is no local storage present on the system, make sure that all required LUNs (<firstterm>Logical Unit Numbers</firstterm>) are being presented to the appropriate HBA (<firstterm>Host Bus Adapter</firstterm>). + </para> + <para> + If you made sure you have a connected and properly configured storage device and the message still appears after you reboot the system and start the installation again, it means that the installation program failed to detect the storage. In most cases this message appears when you attempt to install on an SCSI device which has not been recognized by the installation program. + </para> + </section> + +  + + </section> + + <section id="sect-troubleshooting-problems-after-installation"> + <title>Problems After Installation</title> + + <section> + <title>Are You Unable to Boot With Your RAID Card?</title> + <para> + If you have performed an installation and cannot boot your system properly, you may need to reinstall and partition your system's storage differently. + </para> + <para> + Some BIOS types do not support booting from RAID cards. After you finish the installation and reboot the system for the first time, a text-based screen showing the boot loader prompt (for example, <prompt>grub></prompt>) and a flashing cursor may be all that appears. If this is the case, you must repartition your system and move your <filename>/boot</filename> partition and the boot loader outside the RAID array. The <filename>/boot</filename> partition and the boot loader must be on the same drive. + </para> + <para> + Once these changes have been made, you should be able to finish your installation and boot the system properly. For more information about partitioning, see <xref linkend="sect-installation-gui-storage-partitioning" />. + </para> + </section> + + <section id="sect-trouble-after-graphical-boot"> + <title>Trouble With the Graphical Boot Sequence</title> + <para> + After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently. + </para> + <procedure> + <title>Disabling Graphical Boot Temporarily</title> + <step> + <para> + Start your computer and wait until the boot loader menu appears. If you set your boot loader timeout period to 0, hold down the <keycap>Esc</keycap> key to access it. + </para> + </step> + <step> + <para> + When the boot loader menu appears, use your cursor keys to highlight the entry you want to boot and press the <keycap>e</keycap> key to edit this entry's options. + </para> + </step> + <step> + <para> + In the list of options, find the kernel line - that is, the line beginning with the keyword <literal>linux</literal> (or, in some cases, <literal>linux16</literal> or <literal>linuxefi</literal>). On this line, locate the <literal>rhgb</literal> option and delete it. The option may not be immediately visible; use the cursor keys to scroll up and down. + </para> + </step> + <step> + <para> + Press <keycap>F10</keycap> or <keycombo><keycap>Ctrl</keycap><keycap>X</keycap></keycombo> to boot your system with the edited options. + </para> + </step> + </procedure> + <para> + If the system started successfully, you can log in normally. Then you will need to disable the graphical boot permanently - otherwise you will have to perform the previous procedure every time the system boots. To permanently change boot options, do the following. + </para> + <procedure> + <title>Disabling Graphical Boot Permanently</title> + <step> + <para> + Log in to the <systemitem>root</systemitem> account using the <command>su -</command> command: + </para> + <screen> +<prompt>$</prompt> <command>su -</command> + </screen> + </step> + <step> + <para> + Open the <filename>/etc/default/grub</filename> configuration file using a plain text editor such as <application>vim</application>. + </para> + </step> + <step> + <para> + Within the <filename>grub</filename> file, locate the line beginning with <literal>GRUB_CMDLINE_LINUX</literal>. The line should look similar to the following: + </para> + <programlisting> +GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=vg_rhel/swap rhgb quiet" + </programlisting> + <para> + On this line, delete the <literal>rhgb</literal> option. + </para> + </step> + <step> + <para> + Save the edited configuration file. + </para> + </step> + <step> + <para> + Refresh the boot loader configuration by executing the following command: + </para> + <screen> +<prompt>#</prompt> <command>grub2-mkconfig --output=/boot/grub2/grub.cfg</command> + </screen> + </step> + </procedure> + <para> + After you finish this procedure, you can reboot your computer. Red Hat Enterprise Linux will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the <literal>rhgb</literal> option to the <literal>GRUB_CMDLINE_LINUX</literal> line in the <filename>/etc/default/grub</filename> file and refresh the boot loader configuration again using the <command>grub2-mkconfig</command> command. + </para> + <para> + See the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org">Fedora Documentation website</ulink>, for more information about working with the <application>GRUB2</application> boot loader. + </para> + </section> + + <section id="sect-trouble-after-graphical-login"> + <title>Booting into a Graphical Environment</title> + <para> + If you have installed the <application>X Window System</application> and a desktop environment such as <application>GNOME</application>, but are not seeing a graphical desktop environment once you log into your system, you can start it manually using the <command>startx</command> command. Note, however, that this is just a one-time fix and does not change the log in process for future log ins. + </para> + <para> + To set up your system so that you can log in at a graphical login screen, you must change the default <application>systemd</application> target to <literal>graphical.target</literal>. When you are finished, reboot the computer. You will presented with a graphical login prompt after the system restarts. + </para> + <procedure> + <title>Setting Graphical Login as Default</title> + <step> + <para> + Open a shell prompt. If you are in your user account, become root by typing the <command>su -</command> command. + </para> + </step> + <step> + <para> + Change the default target to <systemitem>graphical.target</systemitem>. To do this, execute the following command: + </para> + <screen> +<prompt>#</prompt> <command>systemctl set-default graphical.target</command> + </screen> + </step> + </procedure> + <para> + Graphical login is now enabled by default - you will be presented with a graphical login prompt after the next reboot. If you want to reverse this change and keep using the text-based login prompt, execute the following command as <systemitem>root</systemitem>: + </para> + <screen> +<prompt>#</prompt> <command>systemctl set-default multi-user.target</command> + </screen> + <para> + For more information about targets in <application>systemd</application>, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org">Fedora Documentation website</ulink>. + </para> + </section> + + <section id="sect-trouble-after-no-gui"> + <title>No Graphical User Interface Present</title> + <para> + If you are having trouble getting <application>X</application> (the <application>X Window System</application>) to start, it is possible that it has not been installed. Some of the pre-set base environments you can select during the installation, such as <guilabel>Minimal install</guilabel> or <guilabel>Web Server</guilabel>, do not include a graphical interface - it has to be installed manually. + </para> + <para> + If you want <application>X</application>, you can install the necessary packages after the installation using the <application>Yum</application> package manager. For example, to install <application>GNOME</application>, use <command>yum install gnome-shell</command> as <systemitem class="username">root</systemitem>. + </para> + </section> + + <section> + <title>X Server Crashing After User Logs In</title> + <para> + If you are having trouble with the <application>X</application> server crashing when a user logs in, one or more of your file systems may be full (or nearly full). To verify that this is the problem you are experiencing, execute the following command: + </para> + <screen> +<prompt>$</prompt> <command>df -h</command> + </screen> + <para> + The output will help you diagnose which partition is full - in most cases, the problem will be on the <filename>/home</filename> partition. A sample output of the <command>df</command> command may look similar to the following: + </para> + <screen> +Filesystem Size Used Avail Use% Mounted on +/dev/mapper/vg_rhel-root 20G 6.0G 13G 32% / +devtmpfs 1.8G 0 1.8G 0% /dev +tmpfs 1.8G 2.7M 1.8G 1% /dev/shm +tmpfs 1.8G 1012K 1.8G 1% /run +tmpfs 1.8G 0 1.8G 0% /sys/fs/cgroup +tmpfs 1.8G 2.6M 1.8G 1% /tmp +/dev/sda1 976M 150M 760M 17% /boot +/dev/dm-4 90G 90G 0 100% /home + </screen> + <para> + In the above example, you can see that the <filename>/home</filename> partition is full, which causes the crash. You can make some room on the partition by removing unneeded files. After you free up some disk space, start <application>X</application> using the <command>startx</command> command. + </para> + <para> + For additional information about <command>df</command> and an explanation of the options available (such as the <option>-h</option> option used in this example), see the <systemitem>df(1)</systemitem> man page. + </para> + </section> + + <section id="sect-trouble-after-missing-ram"> + <title>Is Your RAM Not Being Recognized?</title> + <para> + In some cases the kernel does not recognize all of your memory (RAM), which causes the system to use less memory than is installed. You can find out how much RAM is being utilized using the <command>free -m</command> command. If the displayed total amount of memory does not match your expectations, it is likely that at least one of your memory modules is faulty. On BIOS-based systems, you can use the <application>Memtest86+</application> utility to test your system's memory - see <xref linkend="sect-boot-options-memtest" /> for details. + </para> + <note> + <para> + Some hardware configurations have a part of the system's RAM reserved and unavailable to the main system. Notably, laptop computers with integrated graphics cards will reserve some memory for the GPU. For example, a laptop with 4 GB of RAM and an integrated Intel graphics card will show only roughly 3.7 GB of available memory. + </para> + <para> + Additionally, the <application>kdump</application> crash kernel dumping mechanism reserves some memory for the secondary kernel used in case of the primary kernel crashing. This reserved memory will also not be displayed as available when using the <command>free</command> command. For details about <application>kdump</application> and its memory requirements, see the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org">Fedora Documentation website</ulink>. + </para> + </note> + <para> + If you made sure that your memory does not have any issues, you can try and set the amount of memory manually using the <option>mem=</option> kernel option. + </para> + <procedure> + <title>Configuring the Memory Manually</title> + <step> + <para> + Start your computer and wait until the boot loader menu appears. If you set your boot loader timeout period to 0, hold down the <keycap>Esc</keycap> key to access it. + </para> + </step> + <step> + <para> + When the boot loader menu appears, use your cursor keys to highlight the entry you want to boot and press the <keycap>e</keycap> key to edit this entry's options. + </para> + </step> + <step> + <para> + In the list of options, find the kernel line - that is, the line beginning with the keyword <literal>linux</literal> (or, in some cases, <literal>linux16</literal>). Append the following option to the end of this line: + </para> + <screen> +mem=<replaceable>xx</replaceable>M + </screen> + <para> + Replace <replaceable>xx</replaceable> with the amount of RAM you have in megabytes. + </para> + </step> + <step> + <para> + Press <keycap>F10</keycap> or <keycombo><keycap>Ctrl</keycap><keycap>X</keycap></keycombo> to boot your system with the edited options. + </para> + </step> + <step> + <para> + Wait for the system to boot and log in. Then, open a command line and execute the <command>free -m</command> command again. If total amount of RAM displayed by the command matches your expectations, append the following to the line beginning with <literal>GRUB_CMDLINE_LINUX</literal> in the <filename>/etc/default/grub</filename> file to make the change permanent: + </para> + <screen> +mem=<replaceable>xx</replaceable>M + </screen> + <para> + Replace <replaceable>xx</replaceable> with the amount of RAM you have in megabytes. + </para> + </step> + <step> + <para> + After you updated the file and saved it, refresh the boot loader configuration so that the change will take effect. Run the following command with root privileges: + </para> + <screen> +<prompt>#</prompt> <command>grub2-mkconfig --output=/boot/grub2/grub.cfg</command> + </screen> + </step> + </procedure> + <para> + In <filename>/etc/default/grub</filename>, the above example would look similar to the following: + </para> + <programlisting> +GRUB_TIMEOUT=5 +GRUB_DISTRIBUTOR="$(sed 's, release.*$,,g' /etc/system-release)" +GRUB_DEFAULT=saved +GRUB_DISABLE_SUBMENU=true +GRUB_TERMINAL_OUTPUT="console" +GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root vconsole.font=latarcyrheb-sun16 rd.lvm.lv=rhel/swap $([ -x /usr/sbin/rhcrashkernel.param ] && /usr/sbin/rhcrashkernel-param || :) vconsole.keymap=us rhgb quiet mem=1024M" +GRUB_DISABLE_RECOVERY="true" + </programlisting> + <para> + See the <citetitle>&PRODUCT; System Administrator's Guide</citetitle>, available at the <ulink url="http://docs.fedoraproject.org">Fedora Documentation website</ulink>, for more information about working with the <application>GRUB2</application> boot loader. + </para> + </section> + + </section> </chapter>

1 0

[install-guide/F21-rewrite] removing whitespace before <screen> content
by Pete Travis 07 Sep '14

07 Sep '14

commit 9013188ae7aead20965073e07dcbe5dffbfeb89a Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sun Sep 7 12:44:34 2014 -0600 removing whitespace before <screen> content en-US/Network_based_Installations.xml | 112 ++++++++++++++++----------------- 1 files changed, 54 insertions(+), 58 deletions(-) --- diff --git a/en-US/Network_based_Installations.xml b/en-US/Network_based_Installations.xml index e6a2092..da789f0 100644 --- a/en-US/Network_based_Installations.xml +++ b/en-US/Network_based_Installations.xml @@ -81,16 +81,16 @@ Create a simple configuration for the dhcp server at <filename>/etc/dhcp/dhcpd.conf</filename> </para> <screen> - subnet 192.168.1.0 netmask 255.255.255.0 { - authoritative; - default-lease-time 600; - max-lease-time 7200; - ddns-update-style none; +subnet 192.168.1.0 netmask 255.255.255.0 { + authoritative; + default-lease-time 600; + max-lease-time 7200; + ddns-update-style none; - option domain-name-servers 192.168.1.1; - option routers 192.168.1.1; + option domain-name-servers 192.168.1.1; + option routers 192.168.1.1; - } + } </screen> </step> <step> @@ -98,8 +98,8 @@ Test your configuration and address any problems you discover. </para> <screen> - <command>systemctl start dhcpd</command> - <command>journalctl --unit dhcpd --since -2m --follow</command> +<command>systemctl start dhcpd</command> +<command>journalctl --unit dhcpd --since -2m --follow</command> </screen> </step> <step> @@ -107,16 +107,16 @@ Add entries to point clients to their bootloader and the server that provides it to your subnet configuration in <filename>/etc/dhcp/dhcpd.conf</filename>. Because DHCP clients provide the server with identifying information along with their address request, BIOS clients and UEFI clients can each be directed to the correct bootloader. </para> <screen> - subnet 192.168.1.0 netmask 255.255.255.0 { - if option arch = 00:07 { - filename "uefi/shim.efi"; - } else { - filename "pxelinux/pxelinux.0"; - } +subnet 192.168.1.0 netmask 255.255.255.0 { + if option arch = 00:07 { + filename "uefi/shim.efi"; + } else { + filename "pxelinux/pxelinux.0"; + } - next-server 192.168.1.2; + next-server 192.168.1.2; - ... + ... </screen> </step> <step> @@ -124,8 +124,8 @@ Restart the dhcp service to check the configuration and make changes as needed. </para> <screen> - <command>systemctl restart dhcpd</command> - <command>journalctl --unit dhcpd --since -2m --follow</command> +<command>systemctl restart dhcpd</command> +<command>journalctl --unit dhcpd --since -2m --follow</command> </screen> </step> </procedure> @@ -139,7 +139,7 @@ Install the tftp server package. </para> <screen> - <command>yum install tftp-server</command> +<command>yum install tftp-server</command> </screen> </step> <step> @@ -147,8 +147,8 @@ Start and enable the <systemitem class="resource">tftp socket</systemitem>. <systemitem class="daemon">systemd</systemitem> will automatically start the <systemitem class="daemon">tftpd</systemitem> service when required. </para> <screen> - <command>systemctl start tftp.socket</command> - <command>systemctl enable tftp.socket</command> +<command>systemctl start tftp.socket</command> +<command>systemctl enable tftp.socket</command> </screen> </step> </procedure> @@ -167,7 +167,7 @@ Install the <package>syslinux</package> package. </para> <screen> - <command>yum install syslinux</command> +<command>yum install syslinux</command> </screen> </step> <step> @@ -175,8 +175,8 @@ Create a directory for the bootloader files, and make them available there. </para> <screen> - <command>mkdir -p <filename class="directory">/var/lib/tftpboot/pxelinux</filename></command> - <command>cp <filename>/usr/share/syslinux/{pxelinux.0,vesamenu.c32}</filename> <filename class="directory">/var/lib/tftpboot/pxelinux/</filename></command> +<command>mkdir -p <filename class="directory">/var/lib/tftpboot/pxelinux</filename></command> +<command>cp <filename>/usr/share/syslinux/{pxelinux.0,vesamenu.c32}</filename> <filename class="directory">/var/lib/tftpboot/pxelinux/</filename></command> </screen> </step> </substeps> @@ -189,7 +189,7 @@ Install the <package>shim</package> and <package>grub2-efi</package> packages. If your server is a BIOS system, you <emphasis>must install the packages to a temporary install root</emphasis>. Installing them directly on a BIOS machine will attempt to configure the system for UEFI booting and cause problems. </para> <screen> - <command>yum install shim grub2-efi --installroot=/tmp/fedora --releasever &PRODVER;</command> +<command>yum install shim grub2-efi --installroot=/tmp/fedora --releasever &PRODVER;</command> </screen> </step> <step> @@ -197,8 +197,8 @@ Create a directory for the bootloader files, and make them available there. </para> <screen> - <command>mkdir -p <filename class="directory" >/var/lib/tftpboot/uefi</filename></command> - <command>cp <filename>/tmp/fedora/boot/efi/EFI/fedora/{shim.efi,grubx64.efi}</filename> <filename>/var/lib/tftpboot/uefi/</filename></command> +<command>mkdir -p <filename class="directory" >/var/lib/tftpboot/uefi</filename></command> +<command>cp <filename>/tmp/fedora/boot/efi/EFI/fedora/{shim.efi,grubx64.efi}</filename> <filename>/var/lib/tftpboot/uefi/</filename></command> </screen> </step> </substeps> @@ -243,32 +243,32 @@ label local Create a boot menu for UEFI clients at <filename>/var/lib/tftpboot/pxelinux/uefi</filename>. </para> <programlisting> - function load_video { - insmod efi_gop - insmod efi_uga - insmod video_bochs - insmod video_cirrus - insmod all_video - } +function load_video { + insmod efi_gop + insmod efi_uga + insmod video_bochs + insmod video_cirrus + insmod all_video + } - load_video - set gfxpayload=keep - insmod gzio +load_video +set gfxpayload=keep +insmod gzio - menuentry 'Install &PRODUCT; 64-bit' --class fedora --class gnu-linux --class gnu --class os { - linuxefi f&PRODVER;/vmlinuz ip=dhcp inst.repo=inst.repo=http://download.fedoraproject.org/pub/fedora/linux/rele… - initrdefi f&PRODVER;/initrd.img - } +menuentry 'Install &PRODUCT; 64-bit' --class fedora --class gnu-linux --class gnu --class os { + linuxefi f&PRODVER;/vmlinuz ip=dhcp inst.repo=inst.repo=http://download.fedoraproject.org/pub/fedora/linux/rele… + initrdefi f&PRODVER;/initrd.img + } - menuentry 'Install Fedora &PRODVER; Server' --class fedora --class gnu-linux --class gnu --class os { - kernel f&PRODVER;/vmlinuz - append initrd=f&PRODVER;/initrd.img ip=dhcp ks=https://git.fedorahosted.org/cgit/spin-kickstarts.git/plain/fedora-insta… - } +menuentry 'Install Fedora &PRODVER; Server' --class fedora --class gnu-linux --class gnu --class os { + kernel f&PRODVER;/vmlinuz + append initrd=f&PRODVER;/initrd.img ip=dhcp ks=https://git.fedorahosted.org/cgit/spin-kickstarts.git/plain/fedora-insta… + } - menuentry 'Rescue installed system' --class fedora --class gnu-linux --class gnu --class os { - kernel f&PRODVER;/vmlinuz - append f&PRODVER;/initrd=initrd.img rescue root=live:http://download.fedoraproject.org/pub/fedora/linux/releases/&PROD… rescue - } +menuentry 'Rescue installed system' --class fedora --class gnu-linux --class gnu --class os { + kernel f&PRODVER;/vmlinuz + append f&PRODVER;/initrd=initrd.img rescue root=live:http://download.fedoraproject.org/pub/fedora/linux/releases/&PROD… rescue + } </programlisting> </step> </procedure> @@ -282,23 +282,19 @@ label local Create a directory for the files. </para> <screen> - <command>mkdir -p <filename class="directory" >/var/lib/tftpboot/f&PRODVER;</filename></command> +<command>mkdir -p <filename class="directory" >/var/lib/tftpboot/f&PRODVER;</filename></command> </screen> </step> <step> <para>Download the kernel.</para> <screen> - <command> - wget http://download.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Fedor… -o <filename>/var/lib/tftpboot/f&PRODVER;/vmlinuz</filename> - </command> +<command>wget http://download.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Fedor… -o <filename>/var/lib/tftpboot/f&PRODVER;/vmlinuz</filename></command> </screen> </step> <step> <para>Download the initrd</para> <screen> - <command> - wget http://download.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Fedor… -o <filename>/var/lib/tftpboot/f&PRODVER;/initrd.img</filename> - </command> +<command>wget http://download.fedoraproject.org/pub/fedora/linux/releases/&PRODVER;/Fedor… -o <filename>/var/lib/tftpboot/f&PRODVER;/initrd.img</filename></command> </screen> </step> </procedure>

1 0

[install-guide/F21-rewrite] Look at the mirroring wiki page if you want a local repo.
by Pete Travis 07 Sep '14

07 Sep '14

commit 9e7723ee72536ec19b3b0a2107016fd85afef97a Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Sun Sep 7 12:20:55 2014 -0600 Look at the mirroring wiki page if you want a local repo. Bonus changes include chapter wide markup repair, and minor tab alignment for the cobbler section. en-US/Network_based_Installations.xml | 45 +++++++++++++++++--------------- 1 files changed, 24 insertions(+), 21 deletions(-) --- diff --git a/en-US/Network_based_Installations.xml b/en-US/Network_based_Installations.xml index 21df376..e6a2092 100644 --- a/en-US/Network_based_Installations.xml +++ b/en-US/Network_based_Installations.xml @@ -21,7 +21,8 @@ </para> </warning> --> - <section id="pxe-overview"> + <section id="pxe-overview"> + <title>PXE Installation Overview</title> <para> Pre-Execution Environment, or PXE, is a techonology that allows computers to boot directly from resources provided over the network. Installing Fedora over the network means you don't have to create media, and you can install to multiple computers or virtual machine simultaneously. The process involves a number of components and features working together to provide the resources required. </para> @@ -50,7 +51,7 @@ </para> </formalpara> <formalpara> - <title>Kernel & Initramfs</title> + <title>Kernel and Initramfs</title> <para> The kernel is the core of any Linux operating system, and the initramfs provides the kernel with required tools and resources. These files are also provided by tftp. </para> @@ -60,9 +61,9 @@ <para> A Fedora repository must be available for the installation. The example in this section uses the public Fedora mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP. </para> - <remark>Dump a link in here to the inst.repo option. Update the inst.repo option with examples if needed. --Pete</remark> + </formalpara> + <remark>Dump a link in here to the inst.repo option. Update the inst.repo option with examples if needed. --Pete</remark> <remark>A link to mirrormanager and some instructions to other guides too. All the elaboration on installation methods might be going to far, but we can ref. --Pete</remark> - </formalpara> </section> <section id="pxe-dhcpd"> <title>DHCP Server Configuration</title> @@ -130,6 +131,7 @@ </procedure> </section> <section id="pxe-tftpd"> + <title>Installing the tftp server</title> <procedure> <title>Installing the tftp server</title> <step> @@ -301,22 +303,23 @@ label local </step> </procedure> </section> - <section id="sect-install-server-cobbler"> - <para> - For more complex environments, &PRODUCT; offers the <package>cobbler</package> installation server. Tasks like managing kickstart configurtations, coordinating repositories, maintaining dns records, dhcp servers, and even puppet manifests are effectively automated by <package>cobbler</package>. - </para> - <para> - While levaraging all of the features provided by cobbler can be relatively simple, the full functionality of this powerful tool is too broad to be documented in this guide. The cobbler community provides excellent documentation at <ulink url="http://www.cobblerd.org/manuals/2.6.0/" /> to accompany the packages in the Fedora repository. - </para> - - <section id="sect-booting-pxe-installation"> - <title>Booting the Network Installation</title> - <para> - After the PXE server has been configured and the installation tree or ISO image made available, you are ready to start the network installation. You must make sure that the system you are installing &PRODUCT; on is configured to boot from the network. The exact way to ensure varies depending on the hardware you are using. - </para> - <para> - For more specific instructions about booting your system, see <xref linkend="sect-booting-network" />. - </para> - </section> + <section id="pxe-repositories"> + <title>Providing repositories</title> + <para> + The examples in this section use the public Fedora mirrors as the package source. For faster installations, installing to many systems, or more isolated environments, you may wish to maintain a local repository. + </para> + <para> + Fedora Infrastructure maintains instructions for a configuring a local mirror at <ulink url="https://fedoraproject.org/wiki/Infrastructure/Mirroring" />. The preferred method for providing repositories is via HTTP, and you can refer to the Fedora <citetitle>System Adminsitrators Guide</citetitle> for Fedora &PRODVER; to configure <systemitem class="daemon">httpd</systemitem>. + </para> + </section> + <section id="sect-install-server-cobbler"> + <title>Advanced network installations with Cobbler</title> + <para> + For more complex environments, &PRODUCT; offers the <package>cobbler</package> installation server. Tasks like managing kickstart configurtations, coordinating repositories, maintaining dns records, dhcp servers, and even puppet manifests are effectively automated by <package>cobbler</package>. + </para> + <para> + While levaraging all of the features provided by cobbler can be relatively simple, the full functionality of this powerful tool is too broad to be documented in this guide. The cobbler community provides excellent documentation at <ulink url="http://www.cobblerd.org/manuals/2.6.0/" /> to accompany the packages in the Fedora repository. + </para> + </section> </chapter>

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits September 2014