RHCSA Rapid Track

You had a new admin in your team, but it was decided that it would be in everybody's best interest if that admin pursued a different career.

Now that your staffing issue has been solved, there are a couple of remaining issues. One of them is a machine that had been “fixed” by this admin.

1. Take a good look at the console of your serverX machine. It seems it is stuck early on.

   Take a minute to speculate about a possible cause for this behavior, then reboot the machine and interrupt the boot loader menu countdown. (If you wait long enough, the system will eventually spawn a rescue shell by itself, but that can take a while.)

   1. Usually you would send a Ctrl+Alt+Del to your system to reboot it. This particular boot problem causes that key sequence to retry the boot sequence again without rebooting. In this case, either wait for the task to timeout or use the power switch to force a reboot.

   2. When the boot loader menu appears after the BIOS self-test, press any key to interrupt the countdown.

2. Looking at the error you had during the previous boot, it appears that at least parts of the system are still functioning. Since you know the root password (redhat), attempt an emergency boot.

   1. Use the cursor keys to highlight the default boot loader entry.

   2. Press e to edit the current entry.

   3. Using the cursor keys, navigate to the line that starts with linux16.

   4. Press End to move the cursor to the end of the line.

   5. Append systemd.unit=emergency.target to the end of the line.

   6. Press Ctrl+x to boot using the modified config.

3. Log into the emergency mode. Pay close attention to any errors you might receive.

   1. At the Give root password for maintenance prompt, enter redhat.

4. Inspect what file systems are currently mounted.

   1. [root@localhost ~]# mount
      ...
      /dev/vda1 on / type xfs (ro,relatime,seclabel,attr2,inode64,noquota)

5. It appears that the root file system is mounted read-only; mount it read-write.

   1. [root@localhost ~]# mount -o remount,rw /

6. Attempt to mount all the other file systems:

   1. [root@localhost ~]# mount -a
      mount: mount point /RemoveMe does not exist

7. Open /etc/fstab in an editor and fix the issue.

   1. [root@localhost ~]# vi /etc/fstab

   2. Remove the invalid line (the one with RemoveMe).

   3. Save your changes, then exit your editor.

8. Verify that your /etc/fstab is now correct by attempting to mount all entries.

   1. [root@localhost ~]# mount -a

9. Exit your emergency shell and reboot the system by typing reboot. Your system should now boot normally.