32.2. Anaconda Rescue Mode

Procedure 32.2. Using sosreport in Anaconda Rescue Mode

1. Follow steps in Procedure 32.1, “Booting into Anaconda Rescue Mode” to boot into Anaconda rescue mode. Ensure that you mount the installed system / (root) partition in read-write mode.
2. Change the root directory to the /mnt/sysimage/ directory:

   sh-4.2# chroot /mnt/sysimage/

3. Execute sosreport to generate an archive with system configuration and diagnostic information:

   sh-4.2# sosreport

   Important

   When running, sosreport will prompt you to enter your name and case number that you get when you contact Red Hat Support service and open a new support case. Use only letters and numbers because adding any of the following characters or spaces could render the report unusable:

   # % & { } \ < > > * ? / $ ~ ' " : @ + ` | =

4. Optional. If you want to transfer the generated archive to a new location using the network, it is necessary to have a network interface configured. In case you use the dynamic IP addressing, there are no other steps required. However, when using the static addressing, enter the following command to assign an IP address (for example 10.13.153.64/23) to a network interface (for example dev eth0):

   bash-4.2# ip addr add 10.13.153.64/23 dev eth0

   See the Red Hat Enterprise Linux 7 Networking Guide for additional information about static addressing.
5. Exit the chroot environment:

   sh-4.2# exit

6. Store the generated archive in a new location, from where it can be easily accessible:

   sh-4.2# cp /mnt/sysimage/var/tmp/sosreport new_location

   For transferring the archive through the network, use the scp utility:

   sh-4.2# scp /mnt/sysimage/var/tmp/sosreport username@hostname:sosreport

Procedure 32.3. Reinstalling the GRUB2 Boot Loader

1. Follow instructions in Procedure 32.1, “Booting into Anaconda Rescue Mode” to boot into Anaconda rescue mode. Ensure that you mount the installed system's / (root) partition in read-write mode.
2. Change the root partition:

   sh-4.2# chroot /mnt/sysimage/

3. Use the following command to reinstall the GRUB2 boot loader, where install_device is the boot device (typically, /dev/sda):

   sh-4.2# /sbin/grub2-install install_device

4. Reboot the system.

Procedure 32.4. Using RPM to Remove a Driver

1. Boot the system into Anaconda rescue mode. Follow the instructions in Procedure 32.1, “Booting into Anaconda Rescue Mode”. Ensure that you mount the installed system in read-write mode.
2. Change the root directory to /mnt/sysimage/:

   sh-4.2# chroot /mnt/sysimage/

3. Use the rpm -e command to remove the driver package. For example, to remove the xorg-x11-drv-wacom driver package, run:

   sh-4.2# rpm -e xorg-x11-drv-wacom

4. Exit the chroot environment:

   sh-4.2# exit

Procedure 32.5. Installing a Driver from an RPM package

1. Boot the system into Anaconda rescue mode. Follow the instructions in Procedure 32.1, “Booting into Anaconda Rescue Mode”. Do not choose to mount the installed system as read only.
2. Make the RPM package that contains the driver available. For example, mount a CD or USB flash drive and copy the RPM package to a location of your choice under /mnt/sysimage/, for example: /mnt/sysimage/root/drivers/
3. Change the root directory to /mnt/sysimage/:

   sh-4.2# chroot /mnt/sysimage/

4. Use the rpm -ivh command to install the driver package. For example, to install the xorg-x11-drv-wacom driver package from /root/drivers/, run:

   sh-4.2# rpm -­ivh /root/drivers/xorg-x11-drv-wacom-0.23.0-6.el7.x86_64.rpm

   Note

   The /root/drivers/ directory in this chroot environment is the /mnt/sysimage/root/drivers/ directory in the original rescue environment.
5. Exit the chroot environment:

   sh-4.2# exit