Node is inaccessible after rebooting phase of the upgrade process in vRealize Operations Manager 8.1
search cancel

Node is inaccessible after rebooting phase of the upgrade process in vRealize Operations Manager 8.1

book

Article ID: 340094

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • The upgrade process is stuck on step 4 of 9 on one or more nodes.
  • On one or more nodes in the cluster, searching the output of the journalctl -xb command shows errors similar to:
Failed to start File System Check on /dev/disk/by-label/boot.

Dependency failed for /boot.
  • On one or more nodes in the cluster, the command mount | grep /boot returns no results.


Environment

VMware vRealize Operations 8.1.x

Cause

This issue occurs when the /boot drive fails to mount during the reboot step of an upgrade.

Resolution

To resolve this issue, fix any disk errors using fsck and restart the node.
  1. Log into the affected node as root via Console.
  2. Run the following command to run a disk check on /boot:
fsck /dev/disk/by-label/boot
  1. Follow the prompts to fix any errors that are found.
  2. Run the following command to reboot the node:
reboot
  1. Repeat steps 1-4 on any other affected nodes in the vRealize Operations Manager cluster.
After the affected nodes are rebooted, the upgrade will continue as normal.