Operations for Logs appliance does not start after a reboot.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• .On booting the Operations for Logs appliance, the appliance hangs and the following message is present

  • root (hd0,0)
    Filesystem type is ext2fs, partition type 0x83
    kernel /vmlinuz-5.10.230-1.ph4 root=UUID=########-####-####-####-############
    net.ifnames=0 init=/lib/systemd/systemd ro loglevel=3 quiet plymouth.enable=0
    coredump_filter=0x37 audit=1 rw init=/bin/bash
    net.ifnames=0 init=/lidx=0 in4 init=/lID=########-####-####-####-############
    coredump_filte=0t=/lib/systemd/systemd ro loglevel=3 quiet plymouth.enable=0
    coredump_filter=0x37 audit=1 rw init=/bin/bash
        [Linux-bzImage, setup=0x3000, size=0xa45d70]
    initrd /initrd.img-5.10.230-1.ph4
        [Linux-initrd @ 0x3624c000, 0x1da3174 bytes]

• Shell access is unavailable due to boot hang.

Environment

VMware Aria Operations for Logs 8.18.x

Resolution

Follow the steps outlined in the KB below to run a filesystem check on the 'root', 'data-var' and 'data-core' partitions.

• Manual filesystem check for Aria Operations for Logs