• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

The Geek Diary

CONCEPTS | BASICS | HOWTO

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • Linux Services
    • VCS
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
    • Data Guard
  • DevOps
    • Docker
    • Shell Scripting
  • Interview Questions
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

Repairing filesystem issues at Boot in CentOS/RHEL 7 and 8

By admin

This post focuses on manually repairing the file-system configuration or corruption issues that stop the boot process.

Diagnosing and fixing file system issues

Errors in /etc/fstab and corrupt file systems can stop a system from booting. In most cases, systemd drops to an emergency repair shell that requires the root password. The following table lists some common errors and their results.

Common File System Issues

PROBLEM RESULT
Corrupt file system systemd attempts to repair the file system. If the problem is too severe for an automatic fix, the system drops the user to an emergency shell.
Nonexistent device or UUID referenced in /etc/fstab systemd waits for a set amount of time, waiting for the device to become available. If the device does not become available, the system drops the user to an emergency shell after the timeout.
Nonexistent mount point in /etc/fstab The system drops the user to an emergency shell.
Incorrect mount option specified in /etc/fstab The system drops the user to an emergency shell.

In all cases, administrators can also use the emergency target to diagnose and fix the issue, because no file systems are mounted before the emergency shell is displayed.

How to Boot into Rescue Mode or Emergency Mode Through Systemd in CentOS/RHEL 7 and 8
CentOS / RHEL 7 : How to boot into emergency or multi-user mode from GRUB2
CentOS / RHEL 7 : How to boot into Rescue Mode or Emergency Mode
Note: When using the emergency shell to address file-system issues, do not forget to run systemctl daemon-reload after editing /etc/fstab. Without this reload, systemd may continue using the old version.

The nofail option in an entry in the /etc/fstab file permits the system to boot even if the mount of that file system is not successful. Do not use this option under normal circumstances. With nofail, an application can start with its storage missing, with possibly severe consequences.

Filed Under: CentOS/RHEL, CentOS/RHEL 7, CentOS/RHEL 8, Linux

Some more articles you might also be interested in …

  1. How to use the “screen” command in Linux
  2. How to connect to an Active Directory Domain using Realmd (Configure CentOS/RHEL 7 as active directory client)
  3. How to allow or deny telnet login to specific users only in CentOS/RHEL
  4. A File Is Claimed to Be Disappearing – How to monitor a file for deletion in Linux
  5. How to Enable IPv6 In CentOS / RHEL 5
  6. How to Use the ssh-keygen Command to configure passwordless ssh
  7. How to Configure a Fiber-Channel Over Ethernet (FCoE) Interface in CentOS/RHEL
  8. How to rename a KVM VM with virsh
  9. CentOS / RHEL 7 : How to extract initramfs image and edit/view it
  10. How to Check the Size og yum Channels in CentOS/RHEL

You May Also Like

Primary Sidebar

Recent Posts

  • How to Disable IPv6 on Ubuntu 18.04 Bionic Beaver Linux
  • How to Capture More Logs in /var/log/dmesg for CentOS/RHEL
  • Unable to Start RDMA Services on CentOS/RHEL 7
  • How to rename a KVM VM with virsh
  • Archives
  • Contact Us
  • Copyright

© 2021 · The Geek Diary