FAQ

Red Hat Enterprise Linux (or CentOS) does not boot.

(:Last updated)

Follow the steps below to acquire boot logs to investigate why Red Hat Enterprise Linux (or CentOS) does not boot.

1. Boot Red Hat Enterprise Linux (or CentOS) in rescue mode.

Reference FAQ: What is the procedure for booting in rescue mode on RHEL (or CentOS)?

2. Execute the following command to acquire the boot logs.

# journalctl -xb | less

If the following logs exist in Red Hat Enterprise Linux (or CentOS) boot logs, the description of "/etc/ fstab" is not appropriate.

By commenting out or deleting the line where the description of "/etc / fstab" is not appropriate, you could normally boot Red Hat Enterprise Linux (or CentOS).

(e.g.) The mount option is not specified properly in "/etc/fstab".

Jan 01 00:00:00 localhost systemd[1]: Mounting /mnt...
Jan 01 00:00:00 localhost mount[531]: mount: wrong fs type, bad option, bad superblock on /mnt,
Jan 01 00:00:00 localhost mount[531]: missing codepage or helper program, or other error
Jan 01 00:00:00 localhost mount[531]: In some cases useful info is found in syslog - try
Jan 01 00:00:00 localhost mount[531]: dmesg | tail or so.
Jan 01 00:00:00 localhost kernel: XFS (vdb): unknown mount option [default]. ※ There is a description of non-existent mount option "default" in "/etc/fstab".
Jan 01 00:00:00 localhost systemd[1]: mnt.mount mount process exited, code=exited status=32
Jan 01 00:00:00 localhost systemd[1]: Failed to mount /mnt.

(e.g.) The device is not specified properly in "/etc/fstab".

Jan 01 00:00:00 localhost systemd[1]: Job dev-vdc.device/start timed out. ※ There is a description of non-existent device "/dev/vdc" in "/etc/fstab".

 

Is this page helpful?

Yes No

We appreciate your cooperation in improving the site

Did this FAQ be helpful? If you have any comments, please let us know.

Thank you

Your feedback has been received.