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

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • 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. certbot: command not found
  2. How to create LXC container using lxcbr0 and virbr0 in CentOS/RHEL
  3. Upgrading from CentOS/RHEL 7 to CentOS/RHEL 8 using Leapp
  4. Couldn’t find device with uuid [UUID] – LVM Not Active on Reboot
  5. What are Bash Exit Codes in Linux
  6. How to Disable the ‘lvm2-lvmetad.socket/service’ on CentOS/RHEL 7
  7. How to Setup SSH keys for SSH “public/private key” Login On Linux
  8. fuser: command not found
  9. rc-service Command Examples in Linux
  10. Mutt, Mail and Telnet – Send mails from linux command line or terminal

You May Also Like

Primary Sidebar

Recent Posts

  • aws ec2: CLI for AWS EC2 (Command Examples)
  • aws cur – Create, query, and delete AWS usage report definitions (Command Examples)
  • aws configure – Manage configuration for the AWS CLI (Command Examples)
  • aws cognito-idp: Manage Amazon Cognito user pool and its users and groups using the CLI

© 2023 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright