Red Hat ENTREPRISE LINUX 5 Installation Manual

Table of Contents

Quick Links

Download this manual

Red Hat Enterprise Linux 5

Installation Guide

Installing Red Hat Enterprise Linux 5 for all architectures

Table of Contents

Troubleshooting

Need help?

Do you have a question about the ENTREPRISE LINUX 5 and is the answer not in the manual?

Questions and answers

Summary of Contents for Red Hat ENTREPRISE LINUX 5

Page 1 Red Hat Enterprise Linux 5 Installation Guide Installing Red Hat Enterprise Linux 5 for all architectures...
Page 2 Installation Guide Red Hat Enterprise Linux 5 Installation Guide Installing Red Hat Enterprise Linux 5 for all architectures Edition 3.1 Copyright © 2010 Red Hat, Inc.. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA").
Page 3: Table Of Contents
Preface xiii 1. Document Conventions ....................xiii 1.1. Typographic Conventions ..................xiii 1.2. Pull-quote Conventions ..................xiv 1.3. Notes and Warnings ................... xv 2. Do you need help? ......................xv 3. Getting Help and Giving Feedback ................xvi 3.1. Do You Need Help? ................... xvi 3.2.
Page 4 Installation Guide 4.10. Installing via FTP ....................27 4.11. Installing via HTTP ................... 28 4.12. Welcome to Red Hat Enterprise Linux ............... 29 4.13. Language Selection ..................30 4.14. Keyboard Configuration ..................31 4.15. Enter the Installation Number ................32 4.16.
Page 5 6.4.1. Trouble With the Graphical GRUB Screen on an x86-based System? ..71 6.4.2. Booting into a Graphical Environment ............71 6.4.3. Problems with the X Window System (GUI) ..........72 6.4.4. Problems with the X Server Crashing and Non-Root Users ......72 6.4.5.
Page 6 Installation Guide 11.1. Upgrade or Install? ..................109 11.2. Preparation for IBM eServer System p and System i ......... 109 11.3. Do You Have Enough Disk Space? ..............109 11.4. Can You Install Using the CD-ROM or DVD? ............ 110 11.5.
Page 7 13.3. Performing a driver update during installation ........... 158 13.3.1. Let the installer automatically find a driver update disk ......159 13.3.2. Let the installer prompt you for a driver update ........159 13.3.3. Use a boot option to specify a driver update disk ........159 13.3.4.
Page 8 Installation Guide 17.3.1. Installation using X11 Forwarding ............192 17.3.2. Installation using VNC ................192 17.4. Installing from a Hard Drive (DASD) ..............193 17.5. Installing via NFS ................... 193 17.6. Installing via FTP .................... 194 17.7. Installing via HTTP ..................195 17.8.
Page 9 22.3.2. Creating a Multipath Device With mdadm ..........236 22.4. Configuring IPL from a SCSI Device ..............237 22.4.1. IPL the SCSI Disk ................238 22.5. Adding DASD ....................238 22.6. Adding a Network Device ................242 22.6.1. Adding a qeth Device ................. 243 22.6.2.
Page 10 Installation Guide 29.2. Encrypting block devices using dm-crypt/LUKS ..........287 29.2.1. Overview of LUKS ................287 29.2.2. How will I access the encrypted devices after installation? (System Startup) ......................288 29.2.3. Choosing a Good Passphrase ............. 288 29.3. Creating Encrypted Block Devices in Anaconda ..........288 29.3.1.
Page 11 32.3. Boot Loader Options ..................334 32.4. Partition Information ..................335 32.4.1. Creating Partitions ................335 32.5. Network Configuration ..................340 32.6. Authentication ....................341 32.7. Firewall Configuration ..................341 32.7.1. SELinux Configuration ................342 32.8. Display Configuration ..................342 32.8.1.
Page 13: Preface
Preface 1. Document Conventions This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information. Liberation Fonts In PDF and paper editions, this manual uses typefaces drawn from the set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed.
Page 14: Pull-Quote Conventions
Preface Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand). To insert a special character into a gedit file, choose Applications Accessories Character Map from the main menu bar. Next, choose Search Find…...
Page 15: Notes And Warnings
Red Hat Global Support Services Your Red Hat subscription entitles you to support from Red Hat Global Support Services (GSS). https://www.redhat.com/apps/support/ Visit for more information about obtaining help from GSS. Other Red Hat documentation Access other Red Hat documentation at http://www.redhat.com/docs/.
Page 16: Getting Help And Giving Feedback
Red Hat hosts a large number of electronic mailing lists for discussion about Red Hat software and technology. You can find a list of publicly available lists at https://www.redhat.com/mailman/listinfo. Click on the name of the list for more details of subscribing to the list or to access the list archives.
Page 17: Introduction
Introduction Welcome to the Red Hat Enterprise Linux Installation Guide . HTML and PDF versions of the guides are available online at http://www.redhat.com/docs/. Note Although this manual reflects the most current information possible, read the Red Hat Enterprise Linux Release Notes for information that may not have been available prior to the documentation being finalized.
Page 18: More To Come
In addition to this manual, which covers installation, the Red Hat Enterprise Linux Deployment Guide contains further information on system administration and security. HTML and PDF versions of the guides are available online at http://www.redhat.com/docs/. Note Although this manual reflects the most current information possible, read the Red Hat Enterprise Linux Release Notes for information that may not have been available prior to the documentation being finalized.
Page 19: X86, Amd64, Intel® 64 And Itanium- Installation And Booting
Part I. x86, AMD64, Intel® 64 and Itanium- Installation and Booting The Red Hat Enterprise Linux Installation Guide for Intel and AMD 32-bit and 64-bit systems discusses the installation of Red Hat Enterprise Linux and some basic post-installation troubleshooting. Advanced installation options are covered in the second part of this manual.
Page 21: Itanium System Specific Information
Chapter 1. Itanium System Specific Information 1.1. Itanium System Installation Overview Installing Red Hat Enterprise Linux on an Itanium system is different from installing Red Hat Enterprise Linux on an x86-based system. In general, the sequence of steps to a successful installation are the following: 1.
Page 22: Itanium Systems - Efi System Partition
Chapter 1. Itanium System Specific Information The output is listed in the order the system was probed. So, all FAT16 file systems are listed first, then IDE hard drives, then SCSI hard drives, then IDE CD-ROM drives, and finally SCSI CD-ROM drives. For example, output of the map command might look like the following: Device mapping table : VenHw(Unknown Device:00)/HD(Part1,Sig00000000)
Page 23: Steps To Get You Started
100% compatible. The most recent list of supported hardware can be found at: http://hardware.redhat.com/hcl/ 2.3. Do You Have Enough Disk Space? Nearly every modern-day operating system (OS) uses disk partitions, and Red Hat Enterprise Linux is no exception.
Page 24 If you do not already have a Red Hat Enterprise Linux 5.5 CD set or DVD, you can download one as an ISO image file from the Red Hat Network. Visit https://rhn.redhat.com and enter your Login and Password. Click on the Download Software link to obtain a list of all currently supported Red Hat Enterprise Linux products.
Page 25: Alternative Boot Methods
Alternative Boot Methods Your BIOS may need to be changed to allow booting from your DVD/CD-ROM drive. For more Section 4.4.1, “Booting the Installation Program on information about changing your BIOS, refer to x86, AMD64, and Intel® 64 Systems”. 2.4.1. Alternative Boot Methods Boot DVD/CD-ROM If you can boot using the DVD/CD-ROM drive, you can create your own CD-ROM to boot the installation program.
Page 26: Preparing For A Network Installation
Chapter 2. Steps to Get You Started Note The above command was split into two lines for printing purposes only. When you execute this command, be sure to type it as a single command, all on the same line. Burn the resulting ISO image (named file.iso and located in <path-to-workspace>) to a CD- ROM as you normally would.
Page 27: Preparing For Ftp And Http Installation
Preparing for FTP and HTTP installation To copy the files from the installation DVD or CD-ROMs to a Linux machine which acts as an installation staging server, perform the following steps: • Create an iso image from the installation disk(s) using the following command (for DVDs): dd if=/dev/dvd of=/location/of/disk/space/RHEL5.iso where dvd refers to your DVD drive device.
Page 28: Preparing For A Hard Drive Installation
Chapter 2. Steps to Get You Started Ensure that the /publicly/available/directory directory is exported via NFS via an entry in / etc/exports. To export to a specific system: /publicly/available/directory client.ip.address To export to all systems use an entry such as: /publicly/available/directory * Start the NFS daemon (on a Red Hat Enterprise Linux system, use /sbin/service nfs start).
Page 29 Preparing for a Hard Drive Installation Note The Red Hat Enterprise Linux installation program has the ability to test the integrity of the installation media. It works with the CD / DVD, hard drive ISO, and NFS ISO installation methods. Red Hat recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned CDs).
Page 31: System Specifications List
Chapter 3. System Specifications List The most recent list of supported hardware can be found at http://hardware.redhat.com/hcl/. This system specifications list will help you keep a record of your current system settings and requirements. Enter the corresponding information about your system in the list provided below as a handy reference to help make your Red Hat Enterprise Linux installation goes smoothly.
Page 33: Installing On Intel® And Amd Systems
Chapter 4. Installing on Intel® and AMD Systems This chapter explains how to perform a Red Hat Enterprise Linux installation from the DVD/CD-ROM, using the graphical, mouse-based installation program. The following topics are discussed: • Becoming familiar with the installation program's user interface •...
Page 34: A Note About Virtual Consoles
Chapter 4. Installing on Intel® and AMD Systems elilo linux text 4.1.1. A Note about Virtual Consoles The Red Hat Enterprise Linux installation program offers more than the dialog boxes of the installation process. Several kinds of diagnostic messages are available to you, as well as a way to enter commands from a shell prompt.
Page 35 The Text Mode Installation Program User Interface Note While text mode installations are not explicitly documented, those using the text mode installation program can easily follow the GUI installation instructions. One thing to note is that manipulation of LVM (Logical Volume Management) disk volumes is only possible in graphical mode.
Page 36: Using The Keyboard To Navigate
Chapter 4. Installing on Intel® and AMD Systems Figure 4.1, “Installation Program Widgets as seen Here is a list of the most important widgets shown in in Boot Loader Configuration” Figure 4.2, “Installation Program Widgets as seen in Disk Druid”: •...
Page 37: Starting The Installation Program
Starting the Installation Program Warning Unless a dialog box is waiting for your input, do not press any keys during the installation process (doing so may result in unpredictable behavior). 4.4. Starting the Installation Program To start, first make sure that you have all necessary resources for the installation. If you have already Chapter 2, Steps to Get You Started, and followed the instructions, you should be read through...
Page 38: Booting The Installation Program On Itanium Systems
Chapter 4. Installing on Intel® and AMD Systems Once you have entered your BIOS setup program, find the section where you can alter your boot sequence. The default is often C, A or A, C (depending on whether you boot from your hard drive [C] or a diskette drive [A]).
Page 39: Additional Boot Options
Additional Boot Options 4.4.2.2. Booting the Installation Program from an LS-120 Diskette If your Itanium cannot boot from Red Hat Enterprise Linux CD #1, you must boot from an LS-120 diskette. If you want to perform a hard drive, NFS, FTP, or HTTP installation, you must boot from a boot LS-120 diskette.
Page 40 Chapter 4. Installing on Intel® and AMD Systems Note Chapter 8, Additional Boot Options for Intel® and AMD Systems Refer to for additional boot options not covered in this section. • To perform a text mode installation, at the installation boot prompt, type: linux text •...
Page 41: Selecting An Installation Method
Selecting an Installation Method 4.4.3.1. Kernel Options Options can also be passed to the kernel. For example, to apply updates for the anaconda installation program from a floppy disk enter: linux updates For text mode installations, use: linux text updates This command will prompt you to insert a floppy diskette containing updates for anaconda.
Page 42: Installing From Dvd/Cd-Rom
Chapter 4. Installing on Intel® and AMD Systems HTTP If you are installing directly from an HTTP (Web) server, use this method. You need a boot CD- Section 4.11, “Installing via HTTP”, for ROM (use the linux askmethod boot option). Refer to HTTP installation instructions.
Page 43: Performing A Network Installation
Performing a Network Installation Figure 4.3. Selecting Partition Dialog for Hard Drive Installation Enter the device name of the partition containing the Red Hat Enterprise Linux ISO images. This partition must be formatted with a ext2 or vfat filesystem, and cannot be a logical volume. There is also a field labeled Directory holding images.
Page 44: Installing Via Nfs
Chapter 4. Installing on Intel® and AMD Systems Figure 4.4. TCP/IP Configuration 4.9. Installing via NFS The NFS dialog applies only if you are installing from an NFS server (if you selected NFS Image in the Installation Method dialog). Enter the domain name or IP address of your NFS server. For example, if you are installing from a host named eastcoast in the domain example.com, enter eastcoast.example.com in the NFS Server field.
Page 45: Installing Via Ftp
Installing via FTP Figure 4.5. NFS Setup Dialog If the NFS server is exporting the ISO images of the Red Hat Enterprise Linux CD-ROMs, enter the directory which contains the ISO images. Next, the Welcome dialog appears. 4.10. Installing via FTP The FTP dialog applies only if you are installing from an FTP server (that is, if you used the askmethod boot options and selected FTP in the Installation Method dialog).
Page 46: Installing Via Http
For example, if the FTP site contains the directory /mirrors/redhat/arch/variant;/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.).
Page 47: Welcome To Red Hat Enterprise Linux
Welcome to Red Hat Enterprise Linux directory /mirrors/redhat/arch/variant/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
Page 48: Language Selection
Chapter 4. Installing on Intel® and AMD Systems Click on the Next button to continue. 4.13. Language Selection Figure 4.8, “Language Using your mouse, select a language to use for the installation (refer to Selection”). The language you select here will become the default language for the operating system once it is installed.
Page 49: Keyboard Configuration
Keyboard Configuration Figure 4.8. Language Selection Once you select the appropriate language, click Next to continue. 4.14. Keyboard Configuration Using your mouse, select the correct layout type (for example, U.S. English) for the keyboard you would prefer to use for the installation and as the system default (refer to the figure below). Once you have made your selection, click Next to continue.
Page 50: Enter The Installation Number
Chapter 4. Installing on Intel® and AMD Systems Figure 4.9. Keyboard Configuration Note To change your keyboard layout type after you have completed the installation, use the Keyboard Configuration Tool. Type the system-config-keyboard command in a shell prompt to launch the Keyboard Configuration Tool.
Page 51: Disk Partitioning Setup
Disk Partitioning Setup Figure 4.10. Installation Number 4.16. Disk Partitioning Setup Partitioning allows you to divide your hard drive into isolated sections, where each section behaves as its own hard drive. Partitioning is particularly useful if you run multiple operating systems. If you are not Chapter 26, An Introduction to Disk Partitions sure how you want your system to be partitioned, read for more information.
Page 52 Chapter 4. Installing on Intel® and AMD Systems Figure 4.11. Disk Partitioning Setup If you choose to create a custom layout using Disk Druid, refer to Section 4.19, “Partitioning Your System”. Warning If you receive an error after the Disk Partitioning Setup phase of the installation saying something similar to: "The partition table on device hda was unreadable.
Page 53: Advanced Storage Options
Advanced Storage Options Important — multipath devices To install Red Hat Enterprise Linux on a network device accessible through multiple paths, deselect all local storage in the Select the drive(s) to use for this installation window, and select a device labeled mapper/mpath instead. 4.17.
Page 54 Chapter 4. Installing on Intel® and AMD Systems Figure 4.13. Enable network Interface Fill in the details for the iSCSI target IP and provide a unique iSCSI initiator name to identify this system. If the iSCSI target uses Challenge Handshake Authentication Protocol (CHAP) for authentication, enter the CHAP username and password.
Page 55: Create Default Layout
Create Default Layout Please note that you will be able to reattempt with a different ISCSI target IP should you enter it incorrectly, but in order to change the ISCSI initiator name you will need to restart the installation. 4.18. Create Default Layout Create default layout allows you to have some control concerning what data is removed (if any) from your system.
Page 56 Chapter 4. Installing on Intel® and AMD Systems Figure 4.15. Create Default Layout Using your mouse, choose the storage drive(s) on which you want Red Hat Enterprise Linux to be installed. If you have two or more drives, you can choose which drive(s) should contain this installation.
Page 57: Partitioning Your System
Partitioning Your System To review and make any necessary changes to the partitions created by automatic partitioning, select the Review option. After selecting Review and clicking Next to move forward, the partitions created for you in Disk Druid appear. You can make modifications to these partitions if they do not meet your needs.
Page 58: Graphical Display Of Hard Drive(S)
Chapter 4. Installing on Intel® and AMD Systems Figure 4.16. Partitioning with Disk Druid on x86, AMD64, and Intel® 64 Systems The partitioning tool used by the installation program is Disk Druid. With the exception of certain esoteric situations, Disk Druid can handle the partitioning requirements for a typical installation. 4.19.1.
Page 59: Partition Fields
Partition Fields • Edit: Used to modify attributes of the partition currently selected in the Partitions section. Selecting Edit opens a dialog box. Some or all of the fields can be edited, depending on whether the partition information has already been written to disk. You can also edit free space as represented in the graphical display to create a new partition within that space.
Page 60: Recommended Partitioning Scheme
Chapter 4. Installing on Intel® and AMD Systems • Start: This field shows the cylinder on your hard drive where the partition begins. • End: This field shows the cylinder on your hard drive where the partition ends. Hide RAID device/LVM Volume Group members: Select this option if you do not want to view any RAID device or LVM Volume Group members that have been created.
Page 61 Recommended Partitioning Scheme 4.19.4.2. x86, AMD64, and Intel® 64 systems Unless you have a reason for doing otherwise, we recommend that you create the following partitions for x86, AMD64, and Intel® 64 systems: • A swap partition (at least 256 MB) — swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing.
Page 62: Adding Partitions
Chapter 4. Installing on Intel® and AMD Systems Warning — do not place /var on network storage Red Hat Enterprise Linux 5.5 does not support having a separate /var on a network filesystem (for example, NFS, iSCSI, or NBD) The /var directory contains critical data that must be read from or written to during the boot process before establishing network services.
Page 63 Adding Partitions Figure 4.17. Creating a New Partition • Mount Point: Enter the partition's mount point. For example, if this partition should be the root partition, enter /; enter /boot for the /boot partition, and so on. You can also use the pull-down menu to choose the correct mount point for your partition.
Page 64: Editing Partitions
Chapter 4. Installing on Intel® and AMD Systems If you choose Fill all space up to (MB), you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use. •...
Page 65: Deleting A Partition
Deleting a Partition Note If the partition already exists on your disk, you can only change the partition's mount point. To make any other changes, you must delete the partition and recreate it. 4.19.7. Deleting a Partition To delete a partition, highlight it in the Partitions section and click the Delete button. Confirm the deletion when prompted.
Page 66 Chapter 4. Installing on Intel® and AMD Systems Figure 4.18. Boot Loader Configuration If you do not want to install GRUB as your boot loader, click Change boot loader, where you can choose not to install a boot loader at all. If you already have a boot loader that can boot Red Hat Enterprise Linux and do not want to overwrite your current boot loader, choose Do not install a boot loader by clicking on the Change boot loader button.
Page 67: Advanced Boot Loader Configuration
Advanced Boot Loader Configuration Note The Label column lists what you must enter at the boot prompt, in non-graphical boot loaders, in order to boot the desired operating system. Once you have loaded the GRUB boot screen, use the arrow keys to choose a boot label or type e for edit.
Page 68 Chapter 4. Installing on Intel® and AMD Systems the MBR, when your machine boots, GRUB presents a boot prompt. You can then boot Red Hat Enterprise Linux or any other operating system that you have configured the boot loader to boot. •...
Page 69: Rescue Mode
Rescue Mode Note While partitioning your hard drive, keep in mind that the BIOS in some older systems cannot access more than the first 1024 cylinders on a hard drive. If this is the case, leave enough room for the /boot Linux partition on the first 1024 cylinders of your hard drive to boot Linux.
Page 70: Smp Motherboards And Grub
Chapter 4. Installing on Intel® and AMD Systems ftp://metalab.unc.edu/pub/Linux/system/boot/loaders/ and associated mirror sites. Commercial boot loaders You can load Linux using commercial boot loaders. For example, System Commander and Partition Magic are able to boot Linux (but still require GRUB to be installed in your Linux root partition).
Page 71 Network Configuration Figure 4.20. Network Configuration The installation program automatically detects any network devices you have and displays them in the Network Devices list. When you have selected a network device, click Edit. From the Edit Interface dialog, you can choose to configure the IP address and Netmask (for IPv4 - Prefix for IPv6) of the device to use DHCP or to use static settings.
Page 72 Chapter 4. Installing on Intel® and AMD Systems Figure 4.21. Editing a Network Device Note Do not use the numbers as seen in this sample configuration. These values will not work for your own network configuration. If you are not sure what values to enter, contact your network administrator for assistance.
Page 73: Time Zone Configuration
Time Zone Configuration Note To change your network configuration after you have completed the installation, use the Network Administration Tool. Type the system-config-network command in a shell prompt to launch the Network Administration Tool. If you are not root, it prompts you for the root password to continue. 4.22.
Page 74: Set Root Password
Chapter 4. Installing on Intel® and AMD Systems Note To change your time zone configuration after you have completed the installation, use the Time and Date Properties Tool. Type the system-config-date command in a shell prompt to launch the Time and Date Properties Tool.
Page 75 Set Root Password Figure 4.23. Root Password Use the root account only for system administration. Create a non-root account for your general use and su - to root when you need to fix something quickly. These basic rules minimize the chances of a typo or an incorrect command doing damage to your system.
Page 76: Package Group Selection
Chapter 4. Installing on Intel® and AMD Systems that the password is case-sensitive. If you write down your password, keep it in a secure place. However, it is recommended that you do not write down this or any password you create. Note Do not use one of the example passwords offered in this manual.
Page 77 Package Group Selection Figure 4.24. Package Group Selection Select each component you wish to install. Once a package group has been selected, if optional components are available you can click on Optional packages to view which packages are installed by default, and to add or remove optional packages from that group.
Page 78: Preparing To Install
Chapter 4. Installing on Intel® and AMD Systems Figure 4.25. Package Group Details 4.25. Preparing to Install 4.25.1. Prepare to Install A screen preparing you for the installation of Red Hat Enterprise Linux now appears. For your reference, a complete log of your installation can be found in /root/install.log once you reboot your system.
Page 79: Installing Packages
Installing Packages 4.26. Installing Packages At this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed. 4.27.
Page 80: Post-Installation Boot Loader Options
Chapter 4. Installing on Intel® and AMD Systems elilo linux If you do not know the names of the installed kernels, you can view the /boot/efi/elilo.conf file in EFI with the following instructions: 1. At the Shell> prompt, change devices to the system partition (mounted as /boot/efi in Linux). For example, if fs0 is the system boot partition, type fs0: at the EFI Shell prompt.
Page 81 Booting Red Hat Enterprise Linux Automatically want to pass options to the boot loader, you can configure it in the /boot/efi/elilo.conf configuration file instead. 7. Answer Yes to the Save changes to NVRAM prompt. This returns you to the EFI Boot Maintenance Manager menu.
Page 83: Removing Red Hat Enterprise Linux
Chapter 5. Removing Red Hat Enterprise Linux To uninstall Red Hat Enterprise Linux from your x86-based system, you must remove the Red Hat Enterprise Linux boot loader information from your master boot record (MBR). Note It is always a good idea to backup any data that you have on your system(s). Mistakes do happen and can result in the loss all of your data.
Page 84 Chapter 5. Removing Red Hat Enterprise Linux The print command also displays the partition's type (such as linux-swap, ext2, ext3, and so on). Knowing the type of the partition helps you in determining whether to remove the partition. Remove the partition with the command rm. For example, to remove the partition with minor number 3: rm 3 Important The changes start taking place as soon as you press [Enter], so review the command...
Page 85: Troubleshooting Installation On An Intel® Or Amd System
Chapter 6. Troubleshooting Installation on an Intel® or AMD System This appendix discusses some common installation problems and their solutions. 6.1. You are Unable to Boot Red Hat Enterprise Linux 6.1.1. Are You Unable to Boot With Your RAID Card? If you have performed an installation and cannot boot your system properly, you may need to reinstall and create your partitions differently.
Page 86: Trouble Beginning The Installation
You can also refer to the Red Hat Hardware Compatibility List, available online at: http://hardware.redhat.com/hcl/ 6.3.2. Saving Traceback Messages Without a Diskette Drive If you receive a traceback error message during installation, you can usually save it to a diskette.
Page 87: Trouble With Partition Tables
Trouble with Partition Tables When the traceback dialog appears, the traceback error message is automatically written to a file named /tmp/anacdump.txt. Once the dialog appears, switch over to a new tty (virtual console) by pressing the keys Ctrl+Alt+F2 and scp the message written to /tmp/anacdump.txt to a known working remote system.
Page 88: Are You Seeing Python Errors
If you experience such an error, first try to download any available errata for anaconda. Errata can be found at: http://www.redhat.com/support/errata/ The anaconda website may also be a useful reference and can be found online at: http://fedoraproject.org/wiki/Anaconda You can also search for bug reports related to this problem.
Page 89: Problems After Installation
Finally, if you are still facing problems related to this error, register your product and contact our support team. To register your product, go to: http://www.redhat.com/apps/activate/ 6.4. Problems After Installation 6.4.1. Trouble With the Graphical GRUB Screen on an x86-based System? If you are experiencing problems with GRUB, you may need to disable the graphical boot screen.
Page 90: Problems With The X Window System (Gui)
Chapter 6. Troubleshooting Installation on an Intel® or AMD System id:3:initdefault: To change from a console to a graphical login, you should change the number in the line id:3:initdefault: from a 3 to a 5. Warning Change only the number of the default runlevel from 3 to 5. Your changed line should look like the following: id:5:initdefault: When you are satisfied with your change, save and exit the file using the Ctrl+Q keys.
Page 91: Is Your Ram Not Being Recognized
If the graphical login screen does not appear, check your hardware for compatibility issues. The Hardware Compatibility List can be found at: http://hardware.redhat.com/hcl/ 6.4.6. Is Your RAM Not Being Recognized? Sometimes, the kernel does not recognize all of your memory (RAM). You can check this with the cat /proc/meminfo command.
Page 92: Your Printer Does Not Work
Chapter 6. Troubleshooting Installation on an Intel® or AMD System root (hd0,0) kernel /vmlinuz2.6.95.EL ro root=/dev/hda3 mem=128M Once you reboot, the changes made to grub.conf are reflected on your system. Once you have loaded the GRUB boot screen, type e for edit. You are presented with a list of items in the configuration file for the boot label you have selected.
Page 93: Updating Drivers During Installation On Intel And Amd Systems
Chapter 7. Updating drivers during installation on Intel and AMD systems In most cases, Red Hat Enterprise Linux already includes drivers for the devices that make up your system. However, if your system contains hardware that has been released very recently, drivers for this hardware might not yet be included.
Page 94: Preparing For A Driver Update During Installation
Chapter 7. Updating drivers during installation on Intel and AMD systems Devices already in use You cannot use a driver update to replace drivers that the installation program has already loaded. Instead, you must complete the installation with the drivers that the installation program loaded and update to the new drivers after installation, or, if you need the new drivers for the installation Section 7.2.3, “Preparing process, consider performing an initial RAM disk driver update —...
Page 95: Preparing To Use A Driver Update Image File
Preparing to use a driver update image file 7.2.1. Preparing to use a driver update image file 7.2.1.1. Preparing to use an image file on local storage To make the ISO image file available on local storage, such as a USB flash drive, USB hard drive, or local IDE hard drive, simply copy the file onto the storage device.
Page 96: Preparing A Driver Update Disk
Chapter 7. Updating drivers during installation on Intel and AMD systems Section 7.3.2, “Let the installer prompt you for a driver update” Section 7.3.4, “Use a boot Refer to option to specify a driver update image file on a network” to learn how to specify this network location during installation.
Page 97 Preparing a driver update disk Right-click on this file and choose Write to disc. You will see a window similar to the following: Figure 7.3. CD/DVD Creator's Write to Disc dialog Click the Write button. If a blank disc is not already in the drive, CD/DVD Creator will prompt you to insert one.
Page 98 Chapter 7. Updating drivers during installation on Intel and AMD systems Figure 7.4. Contents of a typical driver update disc on CD or DVD If you see only a single file ending in .iso, then you have not created the disk correctly and should try again.
Page 99: Preparing An Initial Ram Disk Update
Preparing an initial RAM disk update Insert a blank, formatted floppy disk into an available drive, or connect an empty USB storage device (such as a USB flash drive) to your computer. Note the device name allocated to this disk, for example, /dev/fd0 for a floppy disk in the first floppy drive on your system.
Page 100: Performing A Driver Update During Installation
Chapter 7. Updating drivers during installation on Intel and AMD systems Rename the driver update image file to dd.img. At the command line, change into the /tmp/initrd_update directory, type the following command, and press Enter: find . | cpio quiet c o | gzip 9 >/tmp/initrd_update.img Copy the file /tmp/initrd_update.img into the directory the holds the target that you want to use for installation.
Page 101: Let The Installer Automatically Find A Driver Update Disk
Let the installer automatically find a driver update disk • select a PXE target that includes a driver update. 7.3.1. Let the installer automatically find a driver update disk Attach a block device with the filesystem label OEMDRV before starting the installation process. The installer will automatically examine the device and load any driver updates that it detects and will Section 7.2.1.1, “Preparing to use an image file on local not prompt you during the process.
Page 102: Use A Boot Option To Specify A Driver Update Image File On A Network
Chapter 7. Updating drivers during installation on Intel and AMD systems Type linux dd at the boot prompt at the start of the installation process and press Enter. The installer prompts you to confirm that you have a driver disk: Figure 7.6.
Page 103: Specifying The Location Of A Driver Update Image File Or Driver Update Disk
Specifying the location of a driver update image file or driver update disk pxelinux/pxelinux.cfg/default file on your PXE server, type r5su3-dd at the prompt and press Enter. Section 7.2.3, “Preparing an initial RAM disk update” Chapter 34, PXE Network Refer to Installations for instructions on using PXE to perform an update during installation.
Page 104 Chapter 7. Updating drivers during installation on Intel and AMD systems Figure 7.8. Selecting a driver disk partition The installer prompts you to specify which file contains the driver update: Figure 7.9. Selecting an ISO image...
Page 105 Specifying the location of a driver update image file or driver update disk Expect to see these screens if you stored the driver update on an internal hard drive or on a USB storage device. You should not see them if the driver update is on a floppy disk, CD, or DVD. Regardless of whether you are providing a driver update in the form of an image file or with a driver update disk, the installer now copies the appropriate update files into a temporary storage area (located in system RAM and not on disk).
Page 107: Additional Boot Options For Intel® And Amd Systems
Red Hat Enterprise Linux. linux upgradeany this command relaxes some of the checks on your /etc/redhat-release file. If your / etc/redhat-release file has been changed from the default, your Red Hat Enterprise Linux installation may not be found when attempting an upgrade to Red Hat Enterprise Linux 5. Use this option only if your existing Red Hat Enterprise Linux installation was not detected.
Page 108 Chapter 8. Additional Boot Options for Intel® and AMD Systems mem=xxxm this command allows you to override the amount of memory the kernel detects for the machine. This may be needed for some older systems where only 16 mb is detected and for some new machines where the video card shares the video memory with the main memory.
Page 109 nousb this command disables the loading of USB support during the installation. If the installation program tends to hang early in the process, this command may be helpful. nousbstorage this command disables the loading of the usbstorage module in the installation program's loader. It may help with device ordering on SCSI systems.
Page 110 Chapter 8. Additional Boot Options for Intel® and AMD Systems Important Other kernel boot options have no particular meaning for anaconda and do not affect the installation process. However, if you use these options to boot the installation system, anaconda will preserve them in the bootloader configuration.
Page 111: The Grub Boot Loader
Chapter 9. The GRUB Boot Loader When a computer with Red Hat Enterprise Linux is turned on, the operating system is loaded into memory by a special program called a boot loader. A boot loader usually exists on the system's primary hard drive (or other media device) and has the sole responsibility of loading the Linux kernel with its required files or (in some cases) other operating systems into memory.
Page 112: Features Of Grub
Chapter 9. The GRUB Boot Loader 3. The Stage 2 or secondary boot loader is read into memory. The secondary boot loader displays the GRUB menu and command environment. This interface allows the user to select which kernel or operating system to boot, pass arguments to the kernel, or look at system parameters. 4.
Page 113: Installing Grub
This is true even if the disk is mirrored in a level 1 RAID. The following Red Hat Knowledgebase article describes how to make the system bootable from another disk in http://kbase.redhat.com/faq/docs/DOC-7095 the mirrored set: Note that these issues apply only to RAID that is implemented in software, where the individual disks that make up the array are still visible as individual disks on the system.
Page 114: File Names And Blocklists
Chapter 9. The GRUB Boot Loader available called nd for a network disk. Instructions on configuring GRUB to boot over the network are available online at http://www.gnu.org/software/grub/manual/. The <bios-device-number> is the BIOS device number. The primary IDE hard drive is numbered 0 and a secondary IDE hard drive is numbered 1.
Page 115: The Root File System And Grub
The Root File System and GRUB specified by an offset number of blocks, followed by the number of blocks from that offset point. Block offsets are listed sequentially in a comma-delimited list. The following is a sample blocklist: 0+50,100+25,200+1 This sample blocklist specifies a file that starts at the first block on the partition and uses blocks 0 through 49, 100 through 124, and 200.
Page 116: Interfaces Load Order
Chapter 9. The GRUB Boot Loader Menu Interface This is the default interface shown when GRUB is configured by the installation program. A menu of operating systems or preconfigured kernels are displayed as a list, ordered by name. Use the arrow keys to select an operating system or kernel version and press the Enter key to boot it.
Page 117: Grub Commands
GRUB Commands 9.6. GRUB Commands GRUB allows a number of useful commands in its command line interface. Some of the commands accept options after their name; these options should be separated from the command and other options on that line by space characters. The following is a list of useful commands: •...
Page 118: Grub Menu Configuration File
Chapter 9. The GRUB Boot Loader partition specified by the root command. Replace <option-1> with options for the Linux kernel, such as root=/dev/VolGroup00/LogVol00 to specify the device on which the root partition for the system is located. Multiple options can be passed to the kernel in a space separated list. The following is an example kernel command: kernel -/vmlinuz-2.6.8-1.523 ro root=/dev/VolGroup00/LogVol00 The option in the previous example specifies that the root file system for Linux is located on the...
Page 119: Configuration File Directives
Configuration File Directives chainloader +1 This file configures GRUB to build a menu with Red Hat Enterprise Linux as the default operating system and sets it to autoboot after 10 seconds. Two sections are given, one for each operating system entry, with commands specific to the system disk partition table. Note Note that the default is specified as an integer.
Page 120: Changing Runlevels At Boot Time
Chapter 9. The GRUB Boot Loader uses the specified alternate configuration file to build the menu. If an alternate menu configuration file is left out of the command, a user who knows the password is allowed to edit the current configuration file.
Page 121: Useful Websites
FAQ document about GRUB and its usage. 9.9.2. Useful Websites http://www.gnu.org/software/grub/ • — The home page of the GNU GRUB project. This site contains information concerning the state of GRUB development and an FAQ. http://kbase.redhat.com/faq/FAQ_43_4053.shtm • — Details booting operating systems other than Linux. http://www.linuxgazette.com/issue64/kohli.html •...
Page 123: Additional Resources About Itanium And Linux
Chapter 10. Additional Resources about Itanium and Linux Other reference materials, related to running Red Hat Enterprise Linux on an Itanium system, are available on the Web. A few of the available resources are as follows: • — The Intel website on the Itanium Processor http://developer.intel.com/technology/efi/index.htm?iid=sr+efi •...
Page 125: Ii. Ibm Power Architecture - Installation And Booting
Part II. IBM POWER Architecture - Installation and Booting The Red Hat Enterprise Linux Installation Guide for IBM POWER systems discusses the installation of Red Hat Enterprise Linux and some basic post-installation troubleshooting. Advanced installation options are covered in the second part of this manual.
Page 127: Upgrade Or Install
Chapter 11. Steps to Get You Started 11.1. Upgrade or Install? For information to help you determine whether to perform an upgrade or an installation refer to Chapter 24, Upgrading Your Current System. 11.2. Preparation for IBM eServer System p and System i The IBM eServer System p and IBM eServer System i systems introduce many options for partitioning, virtual or native devices, and consoles.
Page 128: Can You Install Using The Cd-Rom Or Dvd
Chapter 11. Steps to Get You Started • have enough unpartitioned disk space for the installation of Red Hat Enterprise Linux, or • have one or more partitions that may be deleted, thereby freeing up enough disk space to install Red Hat Enterprise Linux.
Page 129: Preparing For Ftp And Http Installation
Preparing for FTP and HTTP installation will be made publicly available via FTP, NFS, or HTTP will be specified as /publicly/ available/directory. For example, /location/of/disk/space may be a directory you create called /var/isos. /publicly/available/directory might be /var/www/html/rhel5, for an HTTP install. To copy the files from the installation DVD or CD-ROMs to a Linux machine which acts as an installation staging server, perform the following steps: •...
Page 130: Preparing For A Hard Drive Installation
Chapter 11. Steps to Get You Started • For CDROMs: mv /location/of/disk/space/disk*.iso /publicly/available/directory/ Ensure that the /publicly/available/directory directory is exported via NFS via an entry in / etc/exports. To export to a specific system: /publicly/available/directory client.ip.address To export to all systems use an entry such as: /publicly/available/directory * Start the NFS daemon (on a Red Hat Enterprise Linux system, use /sbin/service nfs start).
Page 131 Preparing for a Hard Drive Installation md5sum programs are available for various operating systems). An md5sum program should be available on the same Linux machine as the ISO images. Additionally, if a file called updates.img exists in the location from which you install, it is used for updates to anaconda, the installation program.
Page 133: Installing On Ibm System I And Ibm System P Systems
Chapter 12. Installing on IBM System i and IBM System p systems This chapter explains how to perform a Red Hat Enterprise Linux installation from the DVD/CD-ROM, using the graphical, mouse-based installation program. The following topics are discussed: • Becoming familiar with the installation program's user interface •...
Page 134: Booting The Ibm System I Or Ibm System P Installation Program
Chapter 12. Installing on IBM System i and IBM System p systems Users who must use the text mode installation program can follow the GUI installation instructions and obtain all needed information. 12.2. Booting the IBM System i or IBM System p Installation Program To boot an IBM System i or IBM System p system from a CD-ROM, you must specify the install boot device in the System Management Services (SMS) menu.
Page 135: A Note About Linux Virtual Consoles
A Note about Linux Virtual Consoles 12.3. A Note about Linux Virtual Consoles This information only applies to users of non-partitioned System p systems using a video card as their Section 12.4, “Using the console. Users of partitioned System i and System p systems should skip to vterm”.
Page 136 Chapter 12. Installing on IBM System i and IBM System p systems Note While text mode installations are not explicitly documented, those using the text mode installation program can easily follow the GUI installation instructions. One thing to note is that manipulation of LVM (Logical Volume Management) disk volumes is only possible in graphical mode.
Page 137: Using The Keyboard To Navigate
Using the Keyboard to Navigate Figure 12.2, “Installation Program Widgets as Here is a list of the most important widgets shown in seen in Boot Loader Configuration” Figure 12.3, “Installation Program Widgets as seen in Disk Druid”: • Window — Windows (usually referred to as dialogs in this manual) appear on your screen throughout the installation process.
Page 138: Beginning Installation
Chapter 12. Installing on IBM System i and IBM System p systems Warning Unless a dialog box is waiting for your input, do not press any keys during the installation process (doing so may result in unpredictable behavior). 12.6. Beginning Installation 12.6.1.
Page 139: Performing A Network Installation
Performing a Network Installation Figure 12.4. Selecting Partition Dialog for Hard Drive Installation Enter the device name of the partition containing the Red Hat Enterprise Linux ISO images. This partition must be formatted with a ext2 or vfat filesystem, and cannot be a logical volume. There is also a field labeled Directory holding images.
Page 140: Installing Via Nfs
Chapter 12. Installing on IBM System i and IBM System p systems Figure 12.5. TCP/IP Configuration 12.9. Installing via NFS The NFS dialog applies only if you are installing from an NFS server (if you selected NFS Image in the Installation Method dialog).
Page 141: Installing Via Ftp
Installing via FTP Figure 12.6. NFS Setup Dialog If the NFS server is exporting the ISO images of the Red Hat Enterprise Linux CD-ROMs, enter the directory which contains the ISO images. Next, the Welcome dialog appears. 12.10. Installing via FTP The FTP dialog applies only if you are installing from an FTP server (that is, if you used the askmethod boot options and selected FTP in the Installation Method dialog).
Page 142: Installing Via Http
For example, if the FTP site contains the directory /mirrors/redhat/arch/variant;/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.).
Page 143: Welcome To Red Hat Enterprise Linux
Welcome to Red Hat Enterprise Linux directory /mirrors/redhat/arch/variant/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
Page 144: Language Selection
Chapter 12. Installing on IBM System i and IBM System p systems Click on the Next button to continue. 12.13. Language Selection Figure 12.9, “Language Using your mouse, select a language to use for the installation (refer to Selection”). The language you select here will become the default language for the operating system once it is installed.
Page 145: Keyboard Configuration
Keyboard Configuration Figure 12.9. Language Selection Once you select the appropriate language, click Next to continue. 12.14. Keyboard Configuration Using your mouse, select the correct layout type (for example, U.S. English) for the keyboard you Figure 12.10, “Keyboard would prefer to use for the installation and as the system default (refer to Configuration”).
Page 146: Enter The Installation Number
Chapter 12. Installing on IBM System i and IBM System p systems Figure 12.10. Keyboard Configuration Note To change your keyboard layout type after you have completed the installation, use the Keyboard Configuration Tool. Type the system-config-keyboard command in a shell prompt to launch the Keyboard Configuration Tool.
Page 147: Disk Partitioning Setup
Disk Partitioning Setup Figure 12.11. Installation Number 12.16. Disk Partitioning Setup Partitioning allows you to divide your hard drive into isolated sections, where each section behaves as its own hard drive. Partitioning is particularly useful if you run multiple operating systems. If you are not Chapter 26, An Introduction to Disk Partitions sure how you want your system to be partitioned, read for more information.
Page 148 Chapter 12. Installing on IBM System i and IBM System p systems Figure 12.12. Disk Partitioning Setup If you choose to create a custom layout using Disk Druid, refer to Section 12.19, “Partitioning Your System”. Warning If you receive an error after the Disk Partitioning Setup phase of the installation saying something similar to: "The partition table on device hda was unreadable.
Page 149: Advanced Storage Options
Advanced Storage Options 12.17. Advanced Storage Options Figure 12.13. Advanced Storage Options From this screen you can choose to disable a dmraid device, in which case the individual elements of the dmraid device will appear as separate hard drives. You can also choose to configure an iSCSI (SCSI over TCP/IP) target.
Page 150 Chapter 12. Installing on IBM System i and IBM System p systems Figure 12.14. Enable network Interface Fill in the details for the iSCSI target IP and provide a unique iSCSI initiator name to identify this system. If the iSCSI target uses Challenge Handshake Authentication Protocol (CHAP) for authentication, enter the CHAP username and password.
Page 151: Create Default Layout
Create Default Layout Please note that you will be able to reattempt with a different ISCSI target IP should you enter it incorrectly, but in order to change the ISCSI initiator name you will need to restart the installation. 12.18. Create Default Layout Create default layout allows you to have some control concerning what data is removed (if any) from your system.
Page 152 Chapter 12. Installing on IBM System i and IBM System p systems Figure 12.16. Create Default Layout Using your mouse, choose the storage drive(s) on which you want Red Hat Enterprise Linux to be installed. If you have two or more drives, you can choose which drive(s) should contain this installation.
Page 153: Partitioning Your System
Partitioning Your System If you have chosen to automatically partition your system, you should select Review and manually edit your /boot/ partition. To review and make any necessary changes to the partitions created by automatic partitioning, select the Review option. After selecting Review and clicking Next to move forward, the partitions created for you in Disk Druid appear.
Page 154: Graphical Display Of Hard Drive(S)
Chapter 12. Installing on IBM System i and IBM System p systems Figure 12.17. Partitioning with Disk Druid on IBM System p and System i systems The partitioning tool used by the installation program is Disk Druid. With the exception of certain esoteric situations, Disk Druid can handle the partitioning requirements for a typical installation.
Page 155: Partition Fields
Partition Fields You can also edit free space as represented in the graphical display to create a new partition within that space. Either highlight the free space and then select the Edit button, or double-click on the free space to edit it. •...
Page 156: Recommended Partitioning Scheme
Chapter 12. Installing on IBM System i and IBM System p systems Hide RAID device/LVM Volume Group members: Select this option if you do not want to view any RAID device or LVM Volume Group members that have been created. 12.19.4.
Page 157: Adding Partitions
Adding Partitions • A root partition (3.0 GB - 5.0 GB) — this is where "/" (the root directory) is located. In this setup, all files (except those stored in /boot) are on the root partition. A 3.0 GB partition allows you to install a minimal installation, while a 5.0 GB root partition lets you perform a full installation, choosing all package groups.
Page 158 Chapter 12. Installing on IBM System i and IBM System p systems Figure 12.18. Creating a New Partition • Mount Point: Enter the partition's mount point. For example, if this partition should be the root partition, enter /; enter /boot for the /boot partition, and so on. You can also use the pull-down menu to choose the correct mount point for your partition.
Page 159: Editing Partitions
Editing Partitions If you choose Fill all space up to (MB), you must give size constraints in the field to the right of this option. This allows you to keep a certain amount of space free on your hard drive for future use. •...
Page 160: Network Configuration
Chapter 12. Installing on IBM System i and IBM System p systems 12.20. Network Configuration If you do not have a network device, physical LAN, or virtual LAN, this screen does not appear during Section 12.21, “Time Zone Configuration”. your installation and you should advance to Figure 12.19.
Page 161 Network Configuration Figure 12.20. Editing a Network Device Note Do not use the numbers as seen in this sample configuration. These values will not work for your own network configuration. If you are not sure what values to enter, contact your network administrator for assistance.
Page 162: Time Zone Configuration
Chapter 12. Installing on IBM System i and IBM System p systems 12.21. Time Zone Configuration Set your time zone by selecting the city closest to your computer's physical location. Click on the map to zoom in to a particular geographical region of the world. From here there are two ways for you to select your time zone: •...
Page 163: Set Root Password
Set Root Password To run the Time and Date Properties Tool as a text-based application, use the command timeconfig. 12.22. Set Root Password Setting up a root account and password is one of the most important steps during your installation. Your root account is similar to the administrator account used on Windows NT machines.
Page 164: Package Group Selection
Chapter 12. Installing on IBM System i and IBM System p systems Note To become root, type su - at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter. for your system. You cannot proceed to The installation program prompts you to set a root password the next stage of the installation process without entering a root password.
Page 165 Package Group Selection Note Users who want support for developing or running 64-bit applications are encouraged to select the Compatibility Arch Support and Compatibility Arch Development Support packages to install architecure specific support for their systems. Figure 12.23, “Package Group To select a component, click on the checkbox beside it (refer to Selection”).
Page 166: Preparing To Install
Chapter 12. Installing on IBM System i and IBM System p systems Figure 12.24. Package Group Details 12.24. Preparing to Install 12.24.1. Prepare to Install A screen preparing you for the installation of Red Hat Enterprise Linux now appears. For your reference, a complete log of your installation can be found in /root/install.log once you reboot your system.
Page 167: Installing Packages
Installing Packages 12.25. Installing Packages At this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed. 12.26.
Page 169: Updating Drivers During Installation On Ibm Power Systems
Chapter 13. Updating drivers during installation on IBM POWER systems In most cases, Red Hat Enterprise Linux already includes drivers for the devices that make up your system. However, if your system contains hardware that has been released very recently, drivers for this hardware might not yet be included.
Page 170: Preparing For A Driver Update During Installation
Chapter 13. Updating drivers during installation on IBM POWER systems Devices already in use You cannot use a driver update to replace drivers that the installation program has already loaded. Instead, you must complete the installation with the drivers that the installation program loaded and update to the new drivers after installation, or, if you need the new drivers for the installation Section 13.2.3, process, consider performing an initial RAM disk driver update —...
Page 171: Preparing To Use A Driver Update Image File
Preparing to use a driver update image file 13.2.1. Preparing to use a driver update image file 13.2.1.1. Preparing to use an image file on local storage To make the ISO image file available on local storage, such as a USB flash drive, USB hard drive, or local IDE hard drive, simply copy the file onto the storage device.
Page 172: Preparing A Driver Update Disk
Chapter 13. Updating drivers during installation on IBM POWER systems Section 13.3.2, “Let the installer prompt you for a driver update” Section 13.3.4, “Use Refer to a boot option to specify a driver update image file on a network” to learn how to specify this network location during installation.
Page 173 Preparing a driver update disk Right-click on this file and choose Write to disc. You will see a window similar to the following: Figure 13.3. CD/DVD Creator's Write to Disc dialog Click the Write button. If a blank disc is not already in the drive, CD/DVD Creator will prompt you to insert one.
Page 174 Chapter 13. Updating drivers during installation on IBM POWER systems Figure 13.4. Contents of a typical driver update disc on CD or DVD If you see only a single file ending in .iso, then you have not created the disk correctly and should try again.
Page 175: Preparing An Initial Ram Disk Update
Preparing an initial RAM disk update Insert a blank, formatted floppy disk into an available drive, or connect an empty USB storage device (such as a USB flash drive) to your computer. Note the device name allocated to this disk, for example, /dev/fd0 for a floppy disk in the first floppy drive on your system.
Page 176: Performing A Driver Update During Installation
Chapter 13. Updating drivers during installation on IBM POWER systems Rename the driver update image file to dd.img. At the command line, change into the /tmp/initrd_update directory, type the following command, and press Enter: find . | cpio quiet c o | gzip 9 >/tmp/initrd_update.img Copy the file /tmp/initrd_update.img into the directory the holds the target that you want to use for installation.
Page 177: Let The Installer Automatically Find A Driver Update Disk
Let the installer automatically find a driver update disk • select a PXE target that includes a driver update. 13.3.1. Let the installer automatically find a driver update disk Attach a block device with the filesystem label OEMDRV before starting the installation process. The installer will automatically examine the device and load any driver updates that it detects and will not Section 13.2.1.1, “Preparing to use an image file on local prompt you during the process.
Page 178: Use A Boot Option To Specify A Driver Update Image File On A Network
Chapter 13. Updating drivers during installation on IBM POWER systems Type linux dd at the boot prompt at the start of the installation process and press Enter. The installer prompts you to confirm that you have a driver disk: Figure 13.6. The driver disk prompt Insert the driver update disk that you created on CD, DVD, floppy disk, or USB storage device and select Yes.
Page 179: Specifying The Location Of A Driver Update Image File Or Driver Update Disk
Specifying the location of a driver update image file or driver update disk pxelinux/pxelinux.cfg/default file on your PXE server, type r5su3-dd at the prompt and press Enter. Section 13.2.3, “Preparing an initial RAM disk update” Chapter 34, PXE Network Refer to Installations for instructions on using PXE to perform an update during installation.
Page 180 Chapter 13. Updating drivers during installation on IBM POWER systems Figure 13.8. Selecting a driver disk partition The installer prompts you to specify which file contains the driver update: Figure 13.9. Selecting an ISO image...
Page 181 Specifying the location of a driver update image file or driver update disk Expect to see these screens if you stored the driver update on an internal hard drive or on a USB storage device. You should not see them if the driver update is on a floppy disk, CD, or DVD. Regardless of whether you are providing a driver update in the form of an image file or with a driver update disk, the installer now copies the appropriate update files into a temporary storage area (located in system RAM and not on disk).
Page 183: Troubleshooting Installation On An Ibm Power System
Chapter 14. Troubleshooting Installation on an IBM POWER System This appendix discusses some common installation problems and their solutions. You may also find the IBM Online Alert Section for System p and System i useful. It is located at: http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/info/LinuxAlerts.html Please note that the url above has been split across two lines for readability.
Page 184: Trouble Beginning The Installation
You can also refer to the Red Hat Hardware Compatibility List, available online at: http://hardware.redhat.com/hcl/ 14.3.2. Saving Traceback Messages Without a Diskette Drive If you receive a traceback error message during installation, you can usually save it to a diskette.
Page 185: Other Partitioning Problems For Ibm™ Power System Users
Other Partitioning Problems for IBM™ POWER System Users The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive. you may not have a partition table on that drive or the partition table on the drive may not be recognizable by the partitioning software used in the installation program.
Page 186: Problems After Installation
Chapter 14. Troubleshooting Installation on an IBM POWER System If you experience such an error, first try to download any available errata for anaconda. Errata can be found at: http://www.redhat.com/support/errata/ The anaconda website may also be a useful reference and can be found online at: http://fedoraproject.org/wiki/Anaconda You can also search for bug reports related to this problem.
Page 187: Problems With The X Window System (Gui)
Problems with the X Window System (GUI) 2 Multiuser, without NFS (The same as 3, if you do not have networking) 3 Full multiuser mode 4 unused 5 X11 6 reboot (Do NOT set initdefault to this) id:3:initdefault: To change from a console to a graphical login, you should change the number in the line id:3:initdefault: from a 3 to a 5.
Page 188: Problems When You Try To Log In
If the graphical login screen does not appear, check your hardware for compatibility issues. The Hardware Compatibility List can be found at: http://hardware.redhat.com/hcl/ 14.4.6. Your Printer Does Not Work If you are not sure how to set up your printer or are having trouble getting it to work properly, try using the Printer Configuration Tool.
Page 189: Additional Boot Options For Ibm Power Systems
Chapter 15. Additional Boot Options for IBM Power Systems This section discusses additional boot and kernel boot options available for the Red Hat Enterprise Linux installation program. To use any of the boot options presented here, type the command you wish to invoke at the installation boot: prompt.
Page 190 Chapter 15. Additional Boot Options for IBM Power Systems mpath enables multipath support. Important — mandatory for installation on multipath devices If you install Red Hat Enterprise Linux 5.5 on a network storage device accessible through multiple paths, you must boot the installation process with this option. If you do not specify this option at boot time, installation will fail, or the system will fail to boot after installation completes.
Page 191 updates this command prompts you to insert a floppy diskette containing updates (bug fixes) for the anaconda installation program. It is not needed if you are performing a network installation and have already placed the updates image contents in rhupdates/ on the server. this command allows you to install from a VNC server.
Page 193: Ibm System Z Architecture - Installation And Booting
Part III. IBM System z Architecture - Installation and Booting The Red Hat Enterprise Linux Installation Guide for IBM System z Architecture systems discusses the installation of Red Hat Enterprise Linux and some basic post-installation troubleshooting. Advanced installation options are covered in the second part of this manual.
Page 195: Steps To Get You Started
Chapter 16. Steps to Get You Started 16.1. Pre-Installation The installation process assumes a basic familiarity with the IBM eServer System z platforms. For additional information on these platforms, refer to the IBM Redbooks available online at: http://www.redbooks.ibm.com/ This manual assumes you are familiar with the related Redbooks and can set up logical partitions (LPARs) and virtual machines (VMs) on an IBM eServer System z system.
Page 196: Basic Overview Of The Boot Method
Sample parameter and CMS configuration files are provided (redhat.parm and redhat.conf). You should edit the CMS configuration file and add information about your DASD. You may also want to add some information about your network configuration. Once this is started on the IBM System z, the networking is configured.
Page 197: Preparing For Ftp And Http Installation
Preparing for FTP and HTTP installation For instructions on how to prepare a network installation using CD-ROMs, refer to the instructions on the README-en file in disk1. 16.4.1. Preparing for FTP and HTTP installation For FTP and HTTP installation, the iso image or images should be mounted via loopback in the publicly available directory, in the following manner: •...
Page 198: Preparing For A Hard Drive Installation
Chapter 16. Steps to Get You Started /publicly/available/directory * Start the NFS daemon (on a Red Hat Enterprise Linux system, use /sbin/service nfs start). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux system use / sbin/service nfs reload).
Page 199: Installing Under Z/Vm
• get generic.prm redhat.parm (repl • quit Chapter 19, Sample You may now create the parameter file (for example, redhat.parm). Refer to Parameter Files for sample parm files. Below is an explanation of the parm file contents. There is a limit of 32 total parameters in the parameter file. In order to accommodate limitations with parameter files, a new configuration file on a CMS DASD should be used to configure the initial network setup and the DASD specification.
Page 200 Example redhat.exec file: /* */ 'cl rdr' 'purge rdr all' 'spool punch * rdr' 'PUNCH KERNEL IMG A (NOH' 'PUNCH REDHAT PARM A (NOH' 'PUNCH INITRD IMG A (NOH' 'ch rdr all keep nohold' 'i 00c' Example redhat.conf file: HOSTNAME="foobar.systemz.example.com"...
Page 201 Installing under z/VM • root=file-system where file-system represents the device on which the root file system can be found. For installation purposes, it should be set to /dev/ram0, which is the ramdisk containing the Red Hat Enterprise Linux installation program. The following parameters are required to set up networking: •...
Page 202 Chapter 16. Steps to Get You Started • NETMASK=netmask Where netmask is the netmask. • BROADCAST=broadcast Where broadcast is the broadcast address. • GATEWAY=gw Where gw is the gateway-IP for your eth device. • MTU=mtu Where mtu is the Maximum Transmission Unit (MTU) for this connection. •...
Page 203 Installing under z/VM • WWPN is the world wide port name used for routing (often in conjunction with multipathing) and is as a 16-digit hex value (e.g. 0x5105074308c212e9). • SCSI_LUN refers to the local SCSI logical unit value and is specified as a hex-value, typically sequential values (e.g.
Page 204: Installing In An Lpar Using The Red Hat Enterprise Linux Lpar Cd
'CL RDR' 'PURGE RDR ALL' 'SPOOL PUNCH * RDR' 'PUNCH KERNEL IMG A (NOH' 'PUNCH REDHAT PARM A (NOH' 'PUNCH INITRD IMG A (NOH' 'CH RDR ALL KEEP NOHOLD' 'IPL 00C CLEAR' The initial installation start-up script prompts you for information about your networking and DASDs unless you have specified all necessary information in the parm file.
Page 205: Installing In An Lpar Without The Red Hat Enterprise Linux For System Z Cd-Roms
Directory on the FTP server holding Red Hat Enterprise Linux for System z (for example, /pub/ redhat/linux/rawhide/s390x) • Click Continue. • In the dialog that follows, keep the default selection of redhat.ins and click Continue. Section 16.9, “Installing in an LPAR (Common Steps)” • Refer to to continue.
Page 206: Do You Have Enough Disk Space
Chapter 16. Steps to Get You Started Note If you install over a network with a Hard Drive Installation source you must perform a text mode installation. 16.10. Do You Have Enough Disk Space? Nearly every modern-day operating system (OS) uses disk partitions, and Red Hat Enterprise Linux is no exception.
Page 207: Installing On Ibm System Z Systems
Chapter 17. Installing on IBM System z Systems This chapter explains how to perform a Red Hat Enterprise Linux installation using the graphical, mouse-based installation program. The following topics are discussed: • Becoming familiar with the installation program's user interface •...
Page 208 Chapter 17. Installing on IBM System z Systems Figure 17.1. Installation Program Widgets as seen in Boot Loader Configuration Figure 17.2. Installation Program Widgets as seen in Disk Druid Figure 17.1, “Installation Program Widgets as Here is a list of the most important widgets shown in seen in Boot Loader Configuration”...
Page 209: Using The Keyboard To Navigate
Using the Keyboard to Navigate you can only interact with the window on top. When you are finished in that window, it disappears, allowing you to continue working in the window underneath. • Checkbox — Checkboxes allow you to select or deselect a feature. The box displays either an asterisk (selected) or a space (unselected).
Page 210: Running The Installation Program
Chapter 17. Installing on IBM System z Systems 17.3. Running the Installation Program Chapter 16, Steps to Get You Started After following the steps outlined in for booting an LPAR or VM system, ssh to the configured Linux install system on the IBM System z. Although the text mode installation program is run by default for most installations, you can optionally run the graphical installation program available for both VM and LPAR installations via the NFS installation method.
Page 211: Installing From A Hard Drive (Dasd)
Installing from a Hard Drive (DASD) Once you have logged into the Linux image the loader will start the installation program. When the loader starts, several screens appear for selecting the installation method. 17.4. Installing from a Hard Drive (DASD) The Select Partition screen applies only if you are installing from a disk partition (that is, if you used the askmethod boot options and selected Hard Drive in the Installation Method dialog).
Page 212: Installing Via Ftp
Chapter 17. Installing on IBM System z Systems Figure 17.3. NFS Setup Dialog If the NFS server is exporting the ISO images of the Red Hat Enterprise Linux CD-ROMs, enter the directory which contains the ISO images. Next, the Welcome dialog appears. 17.6.
Page 213: Installing Via Http
For example, if the FTP site contains the directory /mirrors/redhat/arch/variant;/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.).
Page 214: Welcome To Red Hat Enterprise Linux
Chapter 17. Installing on IBM System z Systems directory /mirrors/redhat/arch/variant/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390x, and variant is the variant that you are installing, such as Client, Server, Workstation, etc.). If everything was specified properly, a message box appears indicating that files are being retrieved from the server.
Page 215: Language Selection
Language Selection Click on the Next button to continue. 17.9. Language Selection Figure 17.6, “Language Using your mouse, select a language to use for the installation (refer to Selection”). The language you select here will become the default language for the operating system once it is installed.
Page 216: Enter The Installation Number
Chapter 17. Installing on IBM System z Systems Figure 17.6. Language Selection Once you select the appropriate language, click Next to continue. 17.10. Enter the Installation Number Figure 17.7, “Installation Number”). This number will determine Enter your Installation Number (refer to the package selection set that is available to the installer.
Page 217: Disk Partitioning Setup
Disk Partitioning Setup Figure 17.7. Installation Number 17.11. Disk Partitioning Setup Partitioning allows you to divide your storage drive(s) into isolated sections, where each section behaves as its own drive. Partitioning is particularly useful if you run multiple operating systems, or wish to enforce a logical or functional distinction between your storage partitions (such as a /home partition that persistently contains user information).
Page 218 Chapter 17. Installing on IBM System z Systems Figure 17.8. Disk Partitioning Setup If you choose to create a custom layout using Disk Druid, refer to Section 17.14, “Partitioning Your System”. Warning If you receive an error after the Disk Partitioning Setup phase of the installation saying something similar to: "The partition table on device dasda was unreadable.
Page 219: Advanced Storage Options
Advanced Storage Options 17.12. Advanced Storage Options 17.12.1. FCP Devices FCP (Fibre Channel protocol) devices enable IBM System z to use SCSI devices rather than DASD devices. FCP (Fibre Channel protocol) devices provide a switched fabric topology that enables zSeries systems to use SCSI LUNs as disk devices in addition to traditional DASD devices.
Page 220 Chapter 17. Installing on IBM System z Systems Figure 17.9. Advanced Storage Options To configure a Fiber Channel Protocol SCSI device invoke the 'Add FCP device' dialog by selecting 'Add ZFCP LUN' and clicking on the 'Add Drive' button. Fill in the details for the 16 bit device number, 64 bit World Wide Port Number (WWPN) and 64 bit FCP LUN.
Page 221 FCP Devices Figure 17.10. Configure FCP Device The newly added device should then be present and usable during the Disk Druid portion of the installation.
Page 222: Create Default Layout
Chapter 17. Installing on IBM System z Systems Figure 17.11. Configure FCP Device Note The installer requires that at least one ECKD DASD be defined. In the situation where a SCSI-only installation is desired a DASD= parameter should be entered into the CMS conf file with a non-existent device number.
Page 223 Create Default Layout • Remove Linux partitions on selected drives and create default layout — select this option to remove only Linux partitions (partitions created from a previous Linux installation). This does not remove other partitions you may have on your storage drive(s) (such as z/VM or z/OS partitions). •...
Page 224: Partitioning Your System
Chapter 17. Installing on IBM System z Systems Click Next once you have made your selections to proceed. 17.14. Partitioning Your System If you chose to create a custom layout, you must tell the installation program where to install Red Hat Enterprise Linux.
Page 225: Disk Druid's Buttons
Disk Druid's Buttons for some unusual cases, this may not be the case. The device number will be used when re-ipling the post-installed system. 17.14.2. Disk Druid's Buttons These buttons control Disk Druid's actions. They are used to change the attributes of a partition (for example the file system type and mount point) and also to create RAID devices.
Page 226: Editing Partitions
Chapter 17. Installing on IBM System z Systems • 'Chapter 7. Linux Swapping' in the IBM Redbook Linux on IBM System z: Performance Measurement and Tuning [IBM Form Number SG24-6926-01], [ISBN 0738485586], available from http://www.redbooks.ibm.com/abstracts/sg246926.html • Linux on System z performance in the IBM Systems Information Center at http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/liaag/ lcon_Linux_on_System_z_performance.htm •...
Page 227 Network Configuration Figure 17.14. Network Configuration The installation program automatically detects any network devices you have and displays them in the Network Devices list. When you have selected a network device, click Edit. From the Edit Interface dialog, you can choose to configure the IP address and Netmask (for IPv4 - Prefix for IPv6) of the device to use DHCP or to use static settings.
Page 228: Time Zone Configuration
Chapter 17. Installing on IBM System z Systems Figure 17.15. Editing a Network Device Note Do not use the numbers as seen in this sample configuration. These values will not work for your own network configuration. If you are not sure what values to enter, contact your network administrator for assistance.
Page 229: Set Root Password
Set Root Password • You can also scroll through the list at the bottom of the screen to select your time zone. Using your mouse, click on a location to highlight your selection. Figure 17.16. Configuring the Time Zone Select System Clock uses UTC if you know that your system is set to UTC. Note To change your time zone configuration after you have completed the installation, use the Time and Date Properties Tool.
Page 230 Chapter 17. Installing on IBM System z Systems Note The root user (also known as the superuser) has complete access to the entire system; for this reason, logging in as the root user is best done only to perform system maintenance or administration.
Page 231: Package Group Selection
Package Group Selection The root password must be at least six characters long; the password you type is not echoed to the screen. You must enter the password twice; if the two passwords do not match, the installation program asks you to enter them again. You should make the root password something you can remember, but not something that is easy for someone else to guess.
Page 232 Chapter 17. Installing on IBM System z Systems Figure 17.18. Package Group Selection Select each component you wish to install. Once a package group has been selected, if optional components are available you can click on Optional packages to view which packages are installed by default, and to add or remove optional packages from that group.
Page 233: Preparing To Install
Preparing to Install Figure 17.19. Package Group Details 17.19. Preparing to Install 17.19.1. Preparing to Install A screen preparing you for the installation of Red Hat Enterprise Linux now appears. For your reference, a complete log of your installation can be found in /root/install.log once you reboot your system.
Page 234: Installing Packages
Chapter 17. Installing on IBM System z Systems 17.20. Installing Packages At this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed. 17.21.
Page 235 Installation Complete Chapter 25, For information on registering your Red Hat Enterprise Linux subscription, refer to Activate Your Subscription.
Page 237: Removing Red Hat Enterprise Linux
Chapter 18. Removing Red Hat Enterprise Linux To remove from the S/390 you can either remove the DASD allocation from the VM or you can start the installation program and re-format all of the DASD partitions. Instead of selecting OK you will select Cancel to exit the installation program.
Page 239: Sample Parameter Files
Where configuration_file represents the name of the configuration file. This value must be specified in lower case. It is specified in a Linux style file name format. The CMS file REDHAT CONF is specified as redhat.conf. This option is applicable only for users who have a CMS formatted disk (z/VM) available.
Page 240 Chapter 19. Sample Parameter Files For example (a sample qeth SUBCHANNEL statement): SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 The following parameters are optional: HOSTNAME=string Where string is the hostname of the newly-installed Linux guest. NETTYPE=type Where type must be one of the following: qeth or lcs. IPADDR=IP Where IP is the IP address of the new Linux guest.
Page 241 The installation program prompts the user for any required parameters not specified in the parameter file. Sample file configuring a QETH networking device: Example of redhat.parm file: root=/dev/ram0 ro ip=off ramdisk_size=40000 CMSDASD=191 CMSCONFFILE=redhat.conf Example of redhat.conf file (pointed to by CMSCONFFILE in redhat.parm) DASD=200 HOSTNAME="foobar.systemz.example.com" DASD="200203" NETTYPE="qeth" IPADDR="192.168.17.115"...
Page 242 Chapter 19. Sample Parameter Files PORTNAME="FOOBAR" NETWORK="192.168.17.0" NETMASK="255.255.255.0" BROADCAST="192.168.17.255" SEARCHDNS="example.com:systemz.example.com" GATEWAY="192.168.17.254" DNS="192.168.17.1" MTU="4096"...
Page 243: Additional Boot Options
Chapter 20. Additional Boot Options This section discusses additional boot and kernel boot options available for the Red Hat Enterprise Linux installation program. To use any of the boot options presented here, type the command you wish to invoke at the installation boot: prompt.
Page 244 Chapter 20. Additional Boot Options do not specify this option at boot time, installation will fail, or the system will fail to boot after installation completes. noprobe this command disables hardware detection and instead prompts the user for hardware information. rescue Chapter 27, Basic System Recovery this command runs rescue mode.
Page 245: Troubleshooting Installation On An Ibm System Z System
Chapter 21. Troubleshooting Installation on an IBM System z System This appendix discusses some common installation problems and their solutions. 21.1. You are Unable to Boot Red Hat Enterprise Linux 21.1.1. Is Your System Displaying Signal 11 Errors? A signal 11 error, commonly know as a segmentation fault, means that the program accessed a memory location that was not assigned to it.
Page 246: Are You Seeing Python Errors
If you experience such an error, first try to download any available errata for anaconda. Errata can be found at: http://www.redhat.com/support/errata/ The anaconda website may also be a useful reference and can be found online at: http://fedoraproject.org/wiki/Anaconda You can also search for bug reports related to this problem.
Page 247: Problems After Installation
Problems After Installation Finally, if you are still facing problems related to this error, register your product and contact our support team. To register your product, go to: http://www.redhat.com/apps/activate/ 21.3. Problems After Installation 21.3.1. Remote Graphical Desktops and XDMCP If you have installed the X Window System and would like to log in to your Red Hat Enterprise Linux system using a graphical login manager, enable the X Display Manager Control Protocol (XDMCP).
Page 248: Your Printer Does Not Work
If the graphical login screen does not appear, check your hardware for compatibility issues. The Hardware Compatibility List can be found at: http://hardware.redhat.com/hcl/ 21.3.3. Your Printer Does Not Work If you are not sure how to set up your printer or are having trouble getting it to work properly, try using the Printer Configuration Tool.
Page 249: Additional Information For Ibm System Z Users
Chapter 22. Additional Information for IBM System z Users 22.1. The sysfs File System The Linux 2.6 kernel introduced the sysfs file system. The sysfs file system is described as a union of the proc, devfs, and devpty file systems. The sysfs file system enumerates the devices and busses attached to the system into a file system hierarchy that can be accessed from user space.
Page 250: Using The Zfcp Driver
Chapter 22. Additional Information for IBM System z Users to devices by their sysfs name. On a 2.4 kernel image, the zFCP driver was passed as its device addresses. On the 2.6 Kernel image system the driver is passed as 0.0.1600. 22.2.
Page 251 Using the zFCP Driver # cd /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154 # echo 0x5719000000000000 > unit_add # ls 0x5719000000000000 d_id in_recovery status unit_remove detach_state failed scsi_id unit_add wwnn # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/scsi_host_no # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/scsi_id # cat \ /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/0x5719000000000000/scsi_lun # cat /sys/bus/scsi/devices/0\:0\:1\:0/hba_id 0.0.010a # cat /sys/bus/scsi/devices/0\:0\:1\:0/wwpn 0x5005076300c18154 # cat /sys/bus/scsi/devices/0\:0\:1\:0/fcp_lun 0x5719000000000000...
Page 252 Chapter 22. Additional Information for IBM System z Users ./kernel/drivers/s390/block/dasd_eckd_mod.ko ./kernel/drivers/s390/block/dasd_fba_mod.ko ./kernel/fs/jbd/jbd.ko ./kernel/fs/ext3/ext3.ko ./kernel/drivers/scsi/scsi_mod.ko ./kernel/drivers/s390/cio/qdio.ko ./kernel/drivers/s390/scsi/zfcp.ko ./kernel/drivers/scsi/sd_mod.ko Using loopback device /dev/loop0 /sbin/nash > /tmp/initrd.cT1534/bin/nash /sbin/insmod.static > /tmp/initrd.cT1534/bin/insmod `/lib/modules/2.6.71.451.2.3/./kernel/drivers/s390/block/dasd_mod.ko'> `/tmp/initrd.cT1534/lib/dasd_mod.ko' `/lib/modules/2.6.71.451.2.3/./kernel/drivers/s390/block/dasd_eckd_mod.ko' > `/tmp/initrd.cT1534/lib/dasd_eckd_mod.ko' `/lib/modules/2.6.71.451.2.3/./kernel/drivers/s390/block/dasd_fba_mod.ko' > `/tmp/initrd.cT1534/lib/dasd_fba_mod.ko' `/lib/modules/2.6.71.451.2.3/./kernel/fs/jbd/jbd.ko' > `/tmp/initrd.cT1534/lib/jbd.ko' `/lib/modules/2.6.71.451.2.3/./kernel/fs/ext3/ext3.ko' > `/tmp/initrd.cT1534/lib/ext3.ko' `/lib/modules/2.6.71.451.2.3/./kernel/drivers/scsi/scsi_mod.ko' >...
Page 253: Using Mdadm To Configure Raid-Based And Multipath Storage
Using mdadm to Configure RAID-Based and Multipath Storage Syncing disks... Done. 22.3. Using mdadm to Configure RAID-Based and Multipath Storage Similar to other tools comprising the raidtools package set, the mdadm command can be used to perform all the necessary functions related to administering multiple-device sets. This section explains how mdadm can be used to: •...
Page 254: Creating A Multipath Device With Mdadm
Chapter 22. Additional Information for IBM System z Users Version : 00.90.00 Creation Time : Mon Mar 1 13:49:10 2004 Raid Level : raid0 Array Size : 15621632 (14.90 GiB 15.100 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Mon Mar...
Page 255: Configuring Ipl From A Scsi Device
Configuring IPL from a SCSI Device mdadm: array /dev/md0 started. Due to the length of the mdadm command line, it has been broken into two lines. In this example, the hardware consists of one SCSI LUN presented as four separate SCSI devices, each accessing the same storage by a different pathway.
Page 256: Ipl The Scsi Disk
00: MLOEVL012I: Machine loader up and running (version 0.13). 00: MLOPDM003I: Machine loader finished, moving data to final storage location. Linux version 2.6.71.451.2.3 (bhcompile@example.z900.redhat.com) (gcc version 3.4 .1 20040702 (Red Hat Linux 3.4.12)) #1 SMP Wed Jul 14 17:52:22 EDT 2004...
Page 257 Adding DASD Procedure 22.1. Bringing a disk online Use the cd command to change to the /sys/ directory that represents that volume: # cd /sys/bus/ccw/drivers/dasdeckd/0.0.4b2e/ # ls l total 0 rrr 1 root root 4096 Aug 25 17:04 availability rwrr 1 root root 4096 Aug 25 17:04 cmb_enable rrr...
Page 258 Chapter 22. Additional Information for IBM System z Users When the progress bar reaches the end and the format is complete, use fdasd to partition the device: # fdasd a /dev/dasdb autocreating one partition for the whole disk... writing volume label... writing VTOC...
Page 259 Adding DASD Add the device to the option line for the dasd_mod in /etc/modprobe.conf Make sure to add the new device at the end of the list, otherwise it changes the device number : devnode mapping and file systems are not on the devices they used to be on. # vi /etc/modprobe.conf # cat /etc/modprobe.conf alias eth0 qeth...
Page 260: Adding A Network Device
Chapter 22. Additional Information for IBM System z Users Loading module ext3 Run zipl to save the changes to initrd for the next IPL: # zipl V Using config file '/etc/zipl.conf' Target device information Device......: 5e:00 Partition.......: 5e:01 Device name.....: dasda DASD device number....: 0201 Type......: disk partition Disk layout.....: ECKD/compatible disk layout...
Page 261: Adding A Qeth Device
Adding a qeth Device 22.6.1. Adding a qeth Device First, determine whether the qeth device driver modules are loaded. # lsmod | grep qeth qeth 135240 qdio 45360 2 qeth ipv6 303984 13 qeth ccwgroup 15104 1 qeth If the output of the lsmod command shows that the modules are not loaded, you must run the modprobe command to load them: # modprobe qeth Next, create a qeth group device.
Page 262 Chapter 22. Additional Information for IBM System z Users # cat /sys/bus/ccwgroup/drivers/qeth/0.0.0600/online A return value of "1" indicates that the device is online, while a return value '0' indicates that the device is offline. Check to see what interface name was assigned to the device: # cat /sys/bus/ccwgroup/drivers/qeth/0.0.0600/if_name eth1 You may optionally set additional parameters and features, depending on the way you are setting up...
Page 263 Adding a qeth Device If there is an existing configuration file for another device of the same type already defined, the simplest solution is to copy it to the new name. # cd /etc/sysconfig/networkscripts # cp ifcfgeth0 ifcfgeth1 If you do not have a similar device defined you must create one. Use this example of ifcfg-eth0 as a template.
Page 264: Quick Reference For Adding Network Devices
Chapter 22. Additional Information for IBM System z Users # ifconfig eth1 eth1 Link encap:Ethernet HWaddr 02:00:00:00:00:01 inet addr:192.168.70.87 Bcast:192.168.70.255 Mask:255.255.255.0 inet6 addr: fe80::ff:fe00:1/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:23 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:644 (644.0 b) TX bytes:264 (264.0 b)
Page 265 Quick Reference for Adding Network Devices • Define the alias (if needed). • Create a configuration script. • Activate the device. The following sections provide basic information for each task of each IBM System z network device driver. 22.6.2.1. Working With the LCS Device Driver The LAN channel station (LCS) device driver supports OSA-2 Ethernet/Token Ring, OSA-Express Fast Ethernet in non-QDIO mode, and OSA-Express High Speed Token Ring in non-QDIO mode.
Page 266 Chapter 22. Additional Information for IBM System z Users • Create a configuration script. Create a file in /etc/sysconfig/network-scripts/ with a name like one of the following: ifcfgethn ifcfgtrn The file should look similar to the following: /etc/sysconfig/network-scripts/ifcfg-eth0 # IBM LCS DEVICE=eth0 BOOTPROTO=static HWADDR=00:06:29:FB:5F:F1...
Page 267 Quick Reference for Adding Network Devices • Create the group device: # echo read_device_bus_id,write_device_bus_id,data_device_bus_id > /sys/bus/ccwgroup/drivers/qeth/group Due to the length of this command, it has been broken into two lines. • Configure the device. For more information about configuration of the QETH driver, refer to the following: http://oss.software.ibm.com/developerworks/opensource/linux390/docu/lx26apr04dd01.pdf (Linux for IBM System z and S/390 Device Drivers, Features, and Commands)
Page 268: Kernel-Related Information
If you notice a malfunction related to system accounting, verify that the malfunction http:// disappears if periodic timer interrupts are enabled, then submit a bug at bugzilla.redhat.com/bugzilla/ (for malfunctioning bundled tools), or inform the tool vendor (for malfunctioning third-party tools).
Page 269: Common Tasks
Part IV. Common Tasks Information that is common to all architectures related to registering your system with Red Hat Network, choosing whether to install or upgrade, and information on disk partitioning is contained in this section.
Page 271: Updating Your System
Chapter 23. Updating Your System 23.1. Driver update rpm packages Occasionally, when a new piece of hardware is not yet supported in the kernel that you have installed, Red Hat or a hardware vendor might make a driver update available. Although you can install driver Chapter 7, Updating drivers during installation on Intel updates during the installation process (refer to and AMD systems...
Page 272 Red Hat GPG package signing key that is already installed on any Red Hat Enterprise Linux 5.5 system. If you need this key for verification purposes on another system, https://www.redhat.com/security/team/key/ you can can obtain it from: Locate and double-click the file that you downloaded.
Page 273 Driver update rpm packages $ rpm ivh kmodipw39451.2.04.17.el5.i686 Whether you used a graphical install, or a command line install, reboot your system to ensure your system is using the new driver. If Red Hat ships a kernel errata update before the next release of Red Hat Enterprise Linux, your system will continue to use the driver updates that you have installed.
Page 275: Upgrading Your Current System
This recommended reinstallation method helps to ensure the best system stability possible. For more information about re-installing your Red Hat Enterprise Linux system, refer to the Whitepapers available online at http://www.redhat.com/rhel/resource_center/. If you currently use Red Hat Enterprise Linux 4 Update 4, you can perform a traditional, installation program-based upgrade.
Page 276: Upgrading Your System
The Upgrade Examine screen appears if you have instructed the installation program to perform an upgrade. Note If the contents of your /etc/redhat-release file have been changed from the default, your Red Hat Enterprise Linux installation may not be found when attempting an upgrade to Red Hat Enterprise Linux 5.5.
Page 277 Upgrading Your System To perform a new installation of Red Hat Enterprise Linux on your system, select Perform a new Red Hat Enterprise Linux installation and refer to Chapter 4, Installing on Intel® and AMD Systems, Chapter 12, Installing on IBM System i and IBM System p systems, or Chapter 17, Installing on IBM System z Systems...
Page 279: Activate Your Subscription
If you can not complete registration during the Setup Agent (which requires network access), you can alternatively complete the Red Hat registration process online at http://www.redhat.com/register/. 25.1.1. Provide a Red Hat Login If you do not have an existing Red Hat login, you can create one when prompted during the Setup Agent or online at: https://www.redhat.com/apps/activate/newlogin.html...
Page 280 Chapter 25. Activate Your Subscription 1. During the Setup Agent — Check the Send hardware information and Send system package list options when prompted. 2. After the Setup Agent has been completed — From Applications (the main menu on the panel), go to System Tools, then select Software Updater.
Page 281: An Introduction To Disk Partitions
Chapter 26. An Introduction to Disk Partitions Note This appendix is not necessarily applicable to non-x86-based architectures. However, the general concepts mentioned here may apply. This appendix is not necessarily applicable to non-x86-based architectures. However, the general concepts mentioned here may apply. Section 26.1.4, “Making If you are reasonably comfortable with disk partitions, you could skip ahead to Room For Red Hat Enterprise...
Page 282 Chapter 26. An Introduction to Disk Partitions Figure 26.2, “Disk Drive with a File System”, implies, the order imposed by a file system involves some trade-offs: • A small percentage of the drive's available space is used to store file system-related data and can be considered as overhead.
Page 283: Partitions: Turning One Drive Into Many
Partitions: Turning One Drive Into Many 26.1.2. Partitions: Turning One Drive Into Many As disk drive capacities soared, some people began to wonder if having all of that formatted space in one big chunk was such a great idea. This line of thinking was driven by several issues, some philosophical, some technical.
Page 284 Chapter 26. An Introduction to Disk Partitions Figure 26.6. Disk Drive With Single Partition In many cases, there is only a single partition spanning the entire disk, essentially duplicating the method used before partitions. The partition table has only one entry used, and it points to the start of the partition.
Page 285: Partitions Within Partitions - An Overview Of Extended Partitions
Partitions within Partitions — An Overview of Extended Partitions 26.1.3. Partitions within Partitions — An Overview of Extended Partitions Of course, over time it became obvious that four partitions would not be enough. As disk drives continued to grow, it became more and more likely that a person could configure four reasonably-sized partitions and still have disk space left over.
Page 286 Chapter 26. An Introduction to Disk Partitions 26.1.4.1. Using Unpartitioned Free Space In this situation, the partitions already defined do not span the entire hard disk, leaving unallocated Figure 26.8, “Disk Drive with Unpartitioned Free Space”, space that is not part of any defined partition. shows what this might look like.
Page 287 Making Room For Red Hat Enterprise Linux If you purchased a computer with pre-installed software, the hard disk most likely has one massive partition holding the operating system and data. Aside from adding a new hard drive to your system, you have two choices: Destructive Repartitioning Basically, you delete the single large partition and create several smaller ones.
Page 288 Chapter 26. An Introduction to Disk Partitions • Resize the existing partition • Create new partition(s) Next we will look at each step in a bit more detail. 26.1.4.3.1. Compress existing data Figure 26.11, “Disk Drive Being Compressed”, shows, the first step is to compress the data in your existing partition.
Page 289: Partition Naming Scheme
Partition Naming Scheme Figure 26.13, “Disk Drive with Final Partition Configuration”, created during the resizing process. shows this being done. Figure 26.13. Disk Drive with Final Partition Configuration Figure 26.13, “Disk Drive with Final Partition Configuration”, 1 represents before and 2 represents after.
Page 290: Disk Partitions And Other Operating Systems
Chapter 26. An Introduction to Disk Partitions /dev/ This is the name of the directory in which all device files reside. Since partitions reside on hard disks, and hard disks are devices, the files representing all possible partitions reside in /dev/. The first two letters of the partition name indicate the type of device on which the partition resides, usually either hd (for IDE disks) or sd (for SCSI disks).
Page 291: How Many Partitions
How Many Partitions? Continuing our example, it is also possible that one or more directories below /usr/ would be mount points for other partitions. For instance, a partition (say, /dev/hda7) could be mounted on /usr/ local/, meaning that /usr/local/man/whatis would then reside on /dev/hda7 rather than / dev/hda5.
Page 293: Basic System Recovery
Part V. Basic System Recovery When things go wrong, there are ways to fix problems. However, these methods require that you understand the system well. This section describes how to boot into rescue mode, single-user mode, and emergency mode, where you can use your own knowledge to repair the system..
Page 295: Basic System Recovery
Chapter 27. Basic System Recovery When things go wrong, there are ways to fix problems. However, these methods require that you understand the system well. This chapter describes how to boot into rescue mode, single-user mode, and emergency mode, where you can use your own knowledge to repair the system. 27.1.
Page 296 Chapter 27. Basic System Recovery As the name implies, rescue mode is provided to rescue you from something. During normal operation, your Red Hat Enterprise Linux system uses files located on your system's hard drive to do everything — run programs, store your files, and more. However, there may be times when you are unable to get Red Hat Enterprise Linux running completely enough to access files on your system's hard drive.
Page 297 Booting into Rescue Mode sh3.00b# If you selected Continue to mount your partitions automatically and they were mounted successfully, you are in single-user mode. Even if your file system is mounted, the default root partition while in rescue mode is a temporary root partition, not the root partition of the file system used during normal user mode (runlevel 3 or 5).
Page 298: Reinstalling The Boot Loader
Chapter 27. Basic System Recovery • rpm for installing or upgrading software • joe for editing configuration files Note If you try to start other popular editors such as emacs, pico, or vi, the joe editor is started. 27.2.1. Reinstalling the Boot Loader In many cases, the GRUB boot loader can mistakenly be deleted, corrupted, or replaced by other operating systems.
Page 299: Booting Into Emergency Mode
Booting into Emergency Mode 27.4. Booting into Emergency Mode In emergency mode, you are booted into the most minimal environment possible. The root file system is mounted read-only and almost nothing is set up. The main advantage of emergency mode over single-user mode is that the init files are not loaded.
Page 301: Rescue Mode On Power Systems
Chapter 28. Rescue Mode on POWER Systems You can use the installation disks in rescue mode, in case your system does not boot. Rescue mode gives you access to the disk partitions on your system so you can make any changes necessary to rescue your installation.
Page 302 Chapter 28. Rescue Mode on POWER Systems 8. When the Linux system has booted into rescue mode, the CD-ROM drive is available for use and you can mount the driver media to access the SCSI utilities.
Page 303: Advanced Installation And Deployment
Part VI. Advanced Installation and Deployment The Red Hat Enterprise Linux Installation Guide discusses the installation of Red Hat Enterprise Linux and some basic post-installation troubleshooting. However, advanced installation options are also covered in this manual. This part provides instructions for kickstart (an automated installation technique)and all related tools.
Page 305: Disk Encryption Guide
Chapter 29. Disk Encryption Guide Note Red Hat Enterprise Linux 5.3 now contains support during installation for file system encryption. This is not supported for earlier versions of Red Hat Enterprise Linux. 29.1. What is block device encryption? Block device encryption protects the data on a block device by encrypting it. To access the device's decrypted contents, a user must provide a passphrase or key as authentication.
Page 306: How Will I Access The Encrypted Devices After Installation? (System Startup)
Chapter 29. Disk Encryption Guide • LUKS is not well-suited for applications requiring many (more than eight) users to have distinct access keys to the same device. • LUKS is not well-suited for applications requiring file-level encryption. http://code.google.com/p/cryptsetup/ For more information on LUKS, refer to 29.2.2.
Page 307: What Kinds Of Block Devices Can Be Encrypted
What Kinds of Block Devices Can Be Encrypted? Therefore, even if you set a global passphrase during installation, you must still supply individual passphrases for each encrypted block device every time that the system boots. Checking the "Encrypt System" checkbox on the "Automatic Partitioning" screen and then choosing "Create custom layout"...
Page 308: Format The Device As A Dm-Crypt/Luks Encrypted Device
Chapter 29. Disk Encryption Guide 29.4.3. Format the device as a dm-crypt/LUKS encrypted device Warning The command below will destroy any existing data on the device. cryptsetup luksFormat <device> For more information, read the cryptsetup(8) man page. After supplying the passphrase twice the device will be formatted for use. To verify, use the following command: cryptsetup isLuks <device>...
Page 309: Create Filesystems On The Mapped Device, Or Continue To Build Complex Storage Structures Using The Mapped Device
Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device For more information, read the dmsetup(8) man page. 29.4.5. Create filesystems on the mapped device, or continue to build complex storage structures using the mapped device Use the mapped device node (/dev/mapper/<name>) as any other block device.
Page 310: Common Post-Installation Tasks
Chapter 29. Disk Encryption Guide only on the device's LUKS UUID, and are therefore guaranteed to remain constant. This fact makes them suitable for use in /etc/fstab. Title For details on the format of the /etc/fstab file, read the fstab(5) man page. 29.5.
Page 311: Installing Through Vnc
Chapter 30. Installing Through VNC Many enterprise customers perform interactive installations on systems in datacenters. These systems are often, but not always, installed in a rack environment and do not have a display, keyboard, or mouse. Additionally, a lot of these systems even lack the ability to connect a graphical display. Given that enterprise hardware rarely needs that ability at the physical system, this hardware configuration is acceptable.
Page 312: Vnc Modes In Anaconda
Chapter 30. Installing Through VNC Once you have verified you have a VNC viewer available, it's time to start the installation. 30.2. VNC Modes in Anaconda Anaconda offers two modes for VNC installation. The mode you select will depend on the network configuration in your environment.
Page 313: Installation Using Vnc
Installation Using VNC Replace HOST with your VNC viewer's IP address or DNS host name. Before starting the installation process on the target system, start up your VNC viewer and have it wait for an incoming connection. Start the installation and when your VNC viewer displays the graphical installer, you are ready to go. 30.3.
Page 314: Kickstart Considerations
Chapter 30. Installing Through VNC Note This IP address is only used during installation. You will have an opportunity to configure the final network settings, if any, later in the installer. 5. Once the installer indicates it is starting anaconda, you will be instructed to connect to the system using the VNC viewer.
Page 315 References http://www.tightvnc.com/ • TightVNC: http://www.ietf.org/rfc/rfc1918.txt • RFC 1918 - Address Allocation for Private Networks: http://fedoraproject.org/wiki/Anaconda/Options • Anaconda boot options: http://fedoraproject.org/wiki/Anaconda/Kickstart • Kickstart documentation:...
Page 317: Kickstart Installations
Chapter 31. Kickstart Installations 31.1. What are Kickstart Installations? Many system administrators would prefer to use an automated installation method to install Red Hat Enterprise Linux on their machines. To answer this need, Red Hat created the kickstart installation method. Using kickstart, a system administrator can create a single file containing the answers to all the questions that would normally be asked during a typical installation.
Page 318: Kickstart Options
Chapter 31. Kickstart Installations • Items that are not required can be omitted. • Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation continues unattended (unless it finds another missing item).
Page 319 Kickstart Options The syntax is: ignoredisk drives=drive1,drive2,... where driveN is one of sda, sdb,..., hda,... etc. autostep (optional) Similar to interactive except it goes to the next screen for you. It is used mostly for debugging. • --autoscreenshot — Take a screenshot at every step during installation and copy the images over to /root/anaconda-screenshots after installation is complete.
Page 320 Chapter 31. Kickstart Installations known to this workstation by enabling LDAP, NIS, or Hesiod or by using the /usr/sbin/ useradd command. If you use this option, you must have the pam_krb5 package installed. • --krb5realm= — The Kerberos 5 realm to which your workstation belongs. •...
Page 321 Kickstart Options • --enablecache — Enables the nscd service. The nscd service caches information about users, groups, and various other types of information. Caching is especially helpful if you choose to distribute information about users and groups over your network using NIS, LDAP, or hesiod.
Page 322 Chapter 31. Kickstart Installations • --drives= — Specifies which drives to clear partitions from. For example, the following clears all the partitions on the first two drives on the primary IDE controller: clearpart drives=hda,hdb all • --initlabel — Initializes the disk label to the default for your architecture (for example msdos for x86 and gpt for Itanium).
Page 323 Kickstart Options firewall enabled|disabled [trust=] <device> [port=] • --enabled or --enable — Reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is needed, you can choose to allow specific services through the firewall. •...
Page 324 Chapter 31. Kickstart Installations install (optional) Tells the system to install a fresh system rather than upgrade an existing system. This is the default mode. For installation, you must specify the type of installation from cdrom, harddrive, nfs, or url (for FTP or HTTP installations). The install command and the installation method command must be on separate lines.
Page 325 Kickstart Options interactive (optional) Uses the information provided in the kickstart file during the installation, but allow for inspection and modification of the values given. You are presented with each screen of the installation program with the values from the kickstart file. Either accept the values by clicking Next or change the values and click Next to continue.
Page 326 Chapter 31. Kickstart Installations islatin1, it, itibm, it2, jp106, lalatin1, mkutf, no, nolatin1, pl, ptlatin1, ro_win, ru, rucp1251, rums, ru1, ru2, ru_win, selatin1, sg, sglatin1, skqwerty, slovene, speakup, speakuplt, svlatin1, sg, sglatin1, skquerty, slovene, trq, ua, uk, us, usacentos The file /usr/lib/python2.2/site-packages/rhpl/keyboard_models.py also contains this list and is part of the rhpl package.
Page 327 Kickstart Options • --bytes-per-inode= — Specifies the size of inodes on the filesystem to be made on the logical volume. Not all filesystems support this option, so it is silently ignored for those cases. • --grow= — Tells the logical volume to grow to fill available space (if any), or up to the maximum size setting.
Page 328 Chapter 31. Kickstart Installations • --noprobe= — Do not try to probe the monitor. • --vsync= — Specifies the vertical sync frequency of the monitor. mouse (deprecated) The mouse keyword is deprecated. network (optional) Configures network information for the system. If the kickstart installation does not require networking (in other words, it is not installed over NFS, HTTP, or FTP), networking is not configured for the system.
Page 329 Kickstart Options Note that although the presentation of this example on this page has broken the line, in a real kickstart file, you must include all this information on a single line with no break. network bootproto=static ip=10.0.2.15 netmask=255.255.255.0 gateway=10.0.2.254 nameserver 192.168.2.1,192.168.3.1 •...
Page 330 Chapter 31. Kickstart Installations Warning All partitions created are formatted as part of the installation process unless -- noformat and --onpart are used. Section 31.4.1, “Advanced Partitioning For a detailed example of part in action, refer to Example”. • <mntpoint> — The <mntpoint> is where the partition is mounted and must be of one of the following forms: •...
Page 331 Kickstart Options • --noformat — Tells the installation program not to format the partition, for use with the -- onpart command. • --onpart= or --usepart= — Put the partition on the already existing device. For example: partition /home onpart=hda1 puts /home on /dev/hda1, which must already exist. •...
Page 332 Chapter 31. Kickstart Installations Note The poweroff option is highly dependent on the system hardware in use. Specifically, certain hardware components such as the BIOS, APM (advanced power management), and ACPI (advanced configuration and power interface) must be able to interact with the system kernel. Contact your manufacturer for more information on you system's APM/ACPI abilities.
Page 333 Kickstart Options part raid.01 size=60 ondisk=sda part raid.02 size=60 ondisk=sdb part raid.03 size=60 ondisk=sdc part swap size=128 ondisk=sda part swap size=128 ondisk=sdb part swap size=128 ondisk=sdc part raid.11 size=1 grow ondisk=sda part raid.12 size=1 grow ondisk=sdb part raid.13 size=1 grow ondisk=sdc raid / level=1 device=md0 raid.01 raid.02 raid.03 raid /usr level=5 device=md1 raid.11 raid.12 raid.13 Section 31.4.1, “Advanced Partitioning...
Page 334 Chapter 31. Kickstart Installations rootpw [iscrypted] <password> • --iscrypted — If this is present, the password argument is assumed to already be encrypted. selinux (optional) Sets the state of SELinux on the installed system. SELinux defaults to enforcing in anaconda. selinux [disabled|enforcing|permissive] •...
Page 335 Kickstart Options text (optional) Perform the kickstart installation in text mode. Kickstart installations are performed in graphical mode by default. timezone (required) Sets the system time zone to <timezone> which may be any of the time zones listed by timeconfig. timezone [utc] <timezone>...
Page 336 Chapter 31. Kickstart Installations • --password= — Set a password which must be provided to connect to the VNC session. This is optional, but recommended. volgroup (optional) Use to create a Logical Volume Management (LVM) group with the syntax: volgroup <name> <partition> <options> The options are as follows: •...
Page 337: Advanced Partitioning Example
Advanced Partitioning Example zfcp (optional) Define a Fiber channel device (IBM System z). zfcp [--devnum=<devnum>] [--fcplun=<fcplun>] [--scsiid=<scsiid>] [-- scsilun=<scsilun>] [--wwpn=<wwpn>] %include (optional) Use the %include /path/to/file command to include the contents of another file in the kickstart file as though the contents were at the location of the %include command in the kickstart file.
Page 338 Chapter 31. Kickstart Installations @Everything @Conflicts Note that Red Hat does not support the use of @Everything in a kickstart file, even if you exclude @Conflicts. Use the %packages command to begin a kickstart file section that lists the packages you would like to install (this is for installations only, as package selection during upgrades is not supported).
Page 339: Pre-Installation Script
Pre-installation Script --ignoremissing Ignore the missing packages and groups instead of halting the installation to ask if the installation should be aborted or continued. For example: %packages ignoremissing 31.6. Pre-installation Script You can add commands to run on the system immediately after the ks.cfg has been parsed. This section must be at the end of the kickstart file (after the commands) and must start with the %pre command.
Page 340: Post-Installation Script
Chapter 31. Kickstart Installations echo "part /home fstype ext3 size 2048 grow" >> /tmp/partinclude This script determines the number of hard drives in the system and writes a text file with a different partitioning scheme depending on whether it has one or two drives. Instead of having a set of partitioning commands in the kickstart file, include the line: %include /tmp/partinclude The partitioning commands selected in the script are used.
Page 341: Examples
Examples 31.7.1. Examples Register the system to a Red Hat Network Satellite: %post ( # Note that in this example we run the entire %post section as a subshell for logging. wget O http://proxyorsat.example.com/pub/bootstrap_script | /bin/bash /usr/sbin/rhnreg_ks activationkey=<activationkey> # End the subshell and capture any output to a postinstall log file. ) 1>/root/post_install.log 2>&1 Run a script named runme from an NFS share: mkdir /mnt/temp...
Page 342: Making The Kickstart File Available On The Network
BOOTP/DHCP server you use. Here is an example of a line from the dhcpd.conf file for the DHCP server: filename "/usr/new-machine/kickstart/"; nextserver blarg.redhat.com; Note that you should replace the value after filename with the name of the kickstart file (or the directory in which the kickstart file resides) and the value after next-server with the NFS server name.
Page 343: Making The Installation Tree Available
Making the Installation Tree Available 31.9. Making the Installation Tree Available The kickstart installation must access an installation tree. An installation tree is a copy of the binary Red Hat Enterprise Linux CD-ROMs with the same directory structure. If you are performing a CD-based installation, insert the Red Hat Enterprise Linux CD-ROM #1 into the computer before starting the kickstart installation.
Page 344 Chapter 31. Kickstart Installations debug Start up pdb immediately. Use a driver disk. dhcpclass=<class> Sends a custom DHCP vendor class identifier. ISC's dhcpcd can inspect this value using "option vendor-class-identifier". dns=<dns> Comma separated list of nameservers to use for a network installation. driverdisk Same as 'dd'.
Page 345 Starting a Kickstart Installation ks=floppy:/<path> The installation program looks for the kickstart file on the diskette in /dev/fd0, as file <path>. ks=hd:<device>:/<file> The installation program mounts the file system on <device> (which must be vfat or ext2), and look for the kickstart configuration file as <file> in that file system (for example, ks=hd:sda3:/ mydir/ks.cfg).
Page 346 Chapter 31. Kickstart Installations mediacheck Activates loader code to give user option of testing integrity of install source (if an ISO-based method). method=cdrom Do a CDROM based installation. method=ftp://<path> Use <path> for an FTP installation. method=hd:<dev>:<path> Use <path> on <dev> for a hard drive installation. method=http://<path>...
Page 347 Image containing updates over FTP. updates=http://<path> Image containing updates over HTTP. upgradeany Don't require an /etc/redhat-release that matches the expected syntax to upgrade. Enable vnc-based installation. You will need to connect to the machine using a vnc client application.
Page 348 Chapter 31. Kickstart Installations vncconnect=<host>[:<port>] Once installation is up and running, connect to the vnc client named <host>, and optionally use port <port>. Requires 'vnc' option to be specified as well. vncpassword=<password> Enable a password for the vnc connection. This will prevent someone from inadvertently connecting to the vnc-based installation.
Page 349: Kickstart Configurator
Chapter 32. Kickstart Configurator Kickstart Configurator allows you to create or modify a kickstart file using a graphical user interface, so that you do not have to remember the correct syntax of the file. To use Kickstart Configurator, you must be running the X Window System and have Kickstart Configurator installed on your system.
Page 350 Chapter 32. Kickstart Configurator Select the system keyboard type from the Keyboard menu. From the Time Zone menu, choose the time zone to use for the system. To configure the system to use UTC, select Use UTC clock. Enter the desired root password for the system in the Root Password text entry box. Type the same password in the Confirm Password text box.
Page 351: Installation Method
NFS server, enter a fully-qualified domain name or IP address. For the NFS directory, enter the name of the NFS directory that contains the variant directory of the installation tree. For example, if the NFS server contains the directory /mirrors/redhat/i386/Server/, enter /mirrors/ redhat/i386/ for the NFS directory.
Page 352: Boot Loader Options
Chapter 32. Kickstart Configurator • Hard Drive — Choose this option to install or upgrade from a hard drive. Hard drive installations require the use of ISO (or CD-ROM) images. Be sure to verify that the ISO images are intact before you start the installation.
Page 353: Partition Information
Partition Information Password text field. To save the password as an encrypted password in the file, select Encrypt GRUB password. If the encryption option is selected, when the file is saved, the plain text password that you typed is encrypted and written to the kickstart file. If the password you typed was already encrypted, unselect the encryption option.
Page 354 Chapter 32. Kickstart Configurator • In the Additional Size Options section, choose to make the partition a fixed size, up to a chosen size, or fill the remaining space on the hard drive. If you selected swap as the file system type, you can select to have the installation program create the swap partition with the recommended size instead of specifying a size.
Page 355 Creating Partitions To edit an existing partition, select the partition from the list and click the Edit button. The same Partition Options window appears as when you chose to add a partition as shown in Figure 32.5, “Creating Partitions”, except it reflects the values for the selected partition. Modify the partition options and click OK.
Page 356 Chapter 32. Kickstart Configurator Figure 32.6. Creating a Software RAID Partition Repeat these steps to create as many partitions as needed for your RAID setup. All of your partitions do not have to be RAID partitions. After creating all the partitions needed to form a RAID device, follow these steps: 1.
Page 357 Creating Partitions Figure 32.7. Creating a Software RAID Device 4. Click OK to add the device to the list.
Page 358: Network Configuration
Chapter 32. Kickstart Configurator 32.5. Network Configuration Figure 32.8. Network Configuration If the system to be installed via kickstart does not have an Ethernet card, do not configure one on the Network Configuration page. Networking is only required if you choose a networking-based installation method (NFS, FTP, or HTTP).
Page 359: Authentication
Authentication 32.6. Authentication Figure 32.9. Authentication In the Authentication section, select whether to use shadow passwords and MD5 encryption for user passwords. These options are highly recommended and chosen by default. The Authentication Configuration options allow you to configure the following methods of authentication: •...
Page 360: Selinux Configuration
Chapter 32. Kickstart Configurator Figure 32.10. Firewall Configuration If Disable firewall is selected, the system allows complete access to any active services and ports. No connections to the system are refused or denied. Selecting Enable firewall configures the system to reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests.
Page 361: General
General Figure 32.11, “X Configuration - General”. If this option is not chosen, the X configuration shown in options are disabled and the skipx option is written to the kickstart file. 32.8.1. General The first step in configuring X is to choose the default color depth and resolution. Select them from their respective pulldown menus.
Page 362: Monitor
Chapter 32. Kickstart Configurator program stops at the video card configuration screen. To continue the installation process, select the driver for your video card from the list and click Next. Alternatively, you can select the video card driver from the list on the Video Card tab as shown in Figure 32.12, “X Configuration - Video Card”.
Page 363 Monitor Figure 32.13. X Configuration - Monitor Probe for monitor is selected by default. Accept this default to have the installation program probe for the monitor during installation. Probing works for most modern monitors. If this option is selected and the installation program cannot successfully probe the monitor, the installation program stops at the monitor configuration screen.
Page 364: Package Selection
Chapter 32. Kickstart Configurator 32.9. Package Selection Figure 32.14. Package Selection The Package Selection window allows you to choose which package groups to install. Package resolution is carried out automatically. Currently, Kickstart Configurator does not allow you to select individual packages. To install individual packages, modify the %packages section of the kickstart file after you save it.
Page 365: Pre-Installation Script
Pre-Installation Script 32.10. Pre-Installation Script Figure 32.15. Pre-Installation Script You can add commands to run on the system immediately after the kickstart file has been parsed and before the installation begins. If you have configured the network in the kickstart file, the network is enabled before this section is processed.
Page 366 Chapter 32. Kickstart Configurator linux64, ln, load_policy, loadfont, loadkmap, login, logname, losetup, ls, lsattr, lsmod, lzmacat, makedevs, md5sum, mdev, mesg, mkdir, mke2fs, mkfifo, mkfs.ext2, mkfs.ext3, mkfs.minix, mknod, mkswap, mktemp, modprobe, more, mount, mountpoint, msh, mt, mv, nameif, nc, netstat, nice, nohup, nslookup, od, openvt, passwd, patch, pidof, ping, ping6, pipe_progress, pivot_root, printenv, printf, ps, pwd, rdate, readlink, readprofile, realpath, renice, reset, rm, rmdir, rmmod, route, rpm, rpm2cpio, run- parts, runlevel, rx, sed, seq, setarch, setconsole, setkeycodes, setlogcons, setsid,...
Page 367: Post-Installation Script
Post-Installation Script 32.11. Post-Installation Script Figure 32.16. Post-Installation Script You can also add commands to execute on the system after the installation is completed. If the network is properly configured in the kickstart file, the network is enabled, and the script can include commands to access resources on the network.
Page 368: Chroot Environment
Chapter 32. Kickstart Configurator 32.11.1. Chroot Environment To run the post-installation script outside of the chroot environment, click the checkbox next to this option on the top of the Post-Installation window. This is equivalent to using the --nochroot option in the %post section. To make changes to the newly installed file system, within the post-installation section, but outside of the chroot environment, you must prepend the directory name with /mnt/sysimage/.
Page 369 Saving the File Figure 32.17. Preview To save the kickstart file, click the Save to File button in the preview window. To save the file without previewing it, select File => Save File or press Ctrl+S . A dialog box appears. Select where to save the file.
Page 371: Boot Process, Init, And Shutdown
Chapter 33. Boot Process, Init, and Shutdown An important and powerful aspect of Red Hat Enterprise Linux is the open, user-configurable method it uses for starting the operating system. Users are free to configure many aspects of the boot process, including specifying the programs launched at boot-time.
Page 372: The Boot Loader
If upgrading the kernel using the Red Hat Update Agent, the boot loader configuration file is updated automatically. More information on Red Hat Network can be found online at the following URL: https://rhn.redhat.com/. Once the second stage boot loader is in memory, it presents the user with a graphical screen showing the different operating systems or kernels it has been configured to boot.
Page 373: The Kernel
The Kernel For instructions on using the boot loader to supply command line arguments to the kernel, refer to Chapter 9, The GRUB Boot Loader. For information on changing the runlevel at the boot loader Section 9.8, “Changing Runlevels at Boot Time”.
Page 374 Chapter 33. Boot Process, Init, and Shutdown The init command then runs the /etc/inittab script, which describes how the system should be set up in each SysV init runlevel. Runlevels are a state, or mode, defined by the services listed in the SysV /etc/rc.d/rc<x>.d/ directory, where <x>...
Page 375 The /sbin/init Program K85mdmpd > ../init.d/mdmpd K89netplugd > ../init.d/netplugd K99microcode_ctl > ../init.d/microcode_ctl S04readahead_early > ../init.d/readahead_early S05kudzu > ../init.d/kudzu S06cpuspeed > ../init.d/cpuspeed S08ip6tables > ../init.d/ip6tables S08iptables > ../init.d/iptables S09isdn > ../init.d/isdn S10network > ../init.d/network S12syslog > ../init.d/syslog S13irqbalance > ../init.d/irqbalance S13portmap > ../init.d/portmap S15mdmonitor >...
Page 376: Running Additional Programs At Boot Time
Chapter 33. Boot Process, Init, and Shutdown Note After the system is finished booting, it is possible to log in as root and execute these same scripts to start and stop services. For instance, the command /etc/rc.d/init.d/ httpd stop stops the Apache HTTP Server. Each of the symbolic links are numbered to dictate start order.
Page 377: Runlevels
Runlevels init.d/ rc0.d/ rc1.d/ rc2.d/ rc3.d/ rc4.d/ rc5.d/ rc6.d/ The init.d/ directory contains the scripts used by the /sbin/init command when controlling services. Each of the numbered directories represent the six runlevels configured by default under Red Hat Enterprise Linux. 33.4.1.
Page 378: Runlevel Utilities
Chapter 33. Boot Process, Init, and Shutdown For more information on single-user and rescue mode, refer to the chapter titled Basic System Recovery in the Red Hat Enterprise Linux Deployment Guide. It is possible to change the default runlevel at boot time by modifying the arguments passed by the Section 9.8, boot loader to the kernel.
Page 379: Pxe Network Installations
Chapter 34. PXE Network Installations Red Hat Enterprise Linux allows for installation over a network using the NFS, FTP, or HTTP protocols. A network installation can be started from a boot CD-ROM, a bootable flash memory drive, or by using the askmethod boot option with the Red Hat Enterprise Linux CD #1.
Page 380: Adding Pxe Hosts
Chapter 34. PXE Network Installations The following list explains the options: • -a — Specifies that an OS instance is being added to the PXE configuration. • -i "<description>" — Replace "<description>" with a description of the OS instance. • -p <NFS|HTTP|FTP> — Specify which of the NFS, FTP, or HTTP protocols to use for installation. Only one may be specified.
Page 381 Adding PXE Hosts Figure 34.1. Add Hosts The next step is to configure which hosts are allowed to connect to the PXE boot server. For the Section 34.3.1, “Command Line Configuration”. command line version of this step, refer to To add hosts, click the New button. Figure 34.2.
Page 382: Command Line Configuration
Chapter 34. PXE Network Installations • Serial Console — This option allows use of a serial console. • Kickstart File — The location of a kickstart file to use, such as http://server.example.com/ kickstart/ks.cfg. This file can be created with the Kickstart Configurator. Refer to Chapter 32, Kickstart Configurator for details.
Page 383: Configuring The Dhcp Server
Configuring the DHCP Server 34.5. Configuring the DHCP Server If a DHCP server does not already exist on the network, configure one. Refer to the Red Hat Enterprise Linux Deployment Guide for details. Make sure the configuration file contains the following so that PXE booting is enabled for systems which support it: allow booting;...
Page 385: Appendix
Part VII. Appendix...
Page 387: Revision History
Note that revision numbers relate to the edition of this manual, not to version numbers of Red Hat Enterprise Linux. Revision 3.1-2 Mon Apr 19 2010 Rüdiger Landmann r.landmann@redhat.com Bump release number to build Revision 3.1-1 Mon Apr 19 2010 Rüdiger Landmann r.landmann@redhat.com...
Page 388 Fri Dec 11 2009 Rüdiger Landmann r.landmann@redhat.com revised Legal Notice, removed restrictions Revision 3.0 Tue Aug 04 2009 Rüdiger Landmann r.landmann@redhat.com, Jon Masters jcm@redhat.com Numerous bug fixes, new chapters on driver updates Revision 2.0 Mon Jan 05 2009 Don Domingo ddomingo@redhat.com...

This manual is also suitable for:

Enterprise linux 5