Symptoms

VxRM boots into emergency mode with error: "[FAILED] Failed to start Security Auditing Service" If we check the partitions with df -h command, you will not find the partition /dev/mapper/storage2-volume1 If we verify the journalctl -xb command, you find that /dev/mapper/storage2-volume1 failed to start the file system check. Some of the other /dev/mapper/storageX-volume1 partitions depend on /dev/mapper/storage2-volume1 and since the Security Auditing Service requires to have access to /var/log/audit, and this path is not available, the service cannot start. Filesystem Mounted on /dev/mapper/storage1-volume1 /home /dev/mapper/storage2-volume1 /var /dev/mapper/storage3-volume1 /var/log/audit /dev/mapper/storage4-volume1 /var/lib /dev/mapper/storage5-volume1 /data/store2 /dev/mapper/storage6-volume1 /var/lib/pgsql

Cause

File system issues in /dev/mapper/storage2-volume1 partition mounted on /var caused that the Security Auditing Service cannot start.

Resolution

In order to fix this problem, you must follow these steps: Run the e2fsck -y command to the /dev/mapper/storage2-volume1 partition. vxrm:~ # e2fsck -y /dev/mapper/storage2-volume1 You should see that the partition was fixed. Reboot the VxRail Manager virtual machine vxrm:~ # reboot VxRail Manager should boot correctly after the reboot.If after reboot the VxRM fails again with another partition, please check the journalctl -xb command again in order to confirm which partition is still affected (usually one of the partitions that depend on /var) Filesystem Mounted on /dev/mapper/storage2-volume1 /var /dev/mapper/storage3-volume1 /var/log/audit /dev/mapper/storage4-volume1 /var/lib /dev/mapper/storage6-volume1 /var/lib/pgsql Run the e2fsck -y in the new affected partition vxrm:~ # e2fsck -y /dev/mapper/storage4-volume1

Support Cases