Linux VM entering in emergency mode.
search cancel

Linux VM entering in emergency mode.

book

Article ID: 402404

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • RHEL guest OS is unable to boot
  • On web console, we can see Warning: Unnaintained hardware is detected
  • Warning: Unnaintained driver is detected
  • Entering emergency mode. Exit the shell to continuc.
    Type "journalctl" to view system logs.
    You might want to save "/run/initramfs/rdsosreport. txt" to a USB stick or /boot
    after mounting them and attach it to a bug report.
  • Journalctl logs may report below errors:
    MMM DD HH:MM:SS localhost systemd[1]: Starting File Systenm Check on /dcu/mapper/rhel_localhost-root>
    MMM DD HH:MM:SS localhost systemd-fsck[918]: /dev/mapper/rhel_localhost-root contains a file system>
    MMM DD HH:MM:SS localhost systemd-fsck[918]: /dev/mapper/rhel_localhost-root: Inodes that were part>
    MMM DD HH:MM:SS localhost systemd-fsck[918]: /dev/mapper/rhel_localhost-root: UNEXPECTED INCONSISTENCY>
    MMM DD HH:MM:SS localhost systemd-fsck[918]:
    MMM DD HH:MM:SS localhost systemd-fsck[916]: fsck failed with exit status 4.
    MMM DD HH:MM:SS localhost systemd-fsck[916]: Runing request emergency.target/start/replace
    MMM DD HH:MM:SS localhost systemd[1]: systemd-fsck-root.service: Main process exited, code=exited, >
    MMM DD HH:MM:SS localhost systemd[1]: systemd-fsck-root.service: Failed with result 'exit-code'.
    MMM DD HH:MM:SS localhost systemd[1]: Failed to start File Systen Check on /deu/mapper/rhel_loca lho>

Environment

Virtual machine with Linux guest os above 8.6

Cause

This unexpected inconsistency reported beucase guest os has detected a filesystem inconsistency on the root logical volume (/dev/mapper/rhel_localhost-root) during boot, and entered into emergency mode to prevent further damage.

 

Resolution

Please connect with OS vendor to fix the file system inconsistency.

Regarding Unnaintained hardware, These hardware categories are classified by the guest os vendor.

Please refer below document from RedHat:

Disclaimer: Broadcom is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that Broadcom endorses, recommends, or accepts any responsibility for the content of such sites.

What does it mean when hardware is classified as "unmaintained" in Red Hat Enterprise Linux 8.6+, 9.0 and newer?