Description

This article explains the meaning of the "Minor VMHost RE x Disk y Missing" alarm that may be seen on devices and indicates if any actions need to be taken.

Symptoms

The following alarm may be seen on the device:

xx@xxxx> show chassis alarms no-forwarding
1 alarm currently active
Alarm time               Class  Description
2020-05-21 17:16:01 BST  Minor  VMHost RE 0 Disk 1 Missing
The following logs may be seen: 
May 21 17:16:01.532 2020  R01-XXX alarmd[86387]: Alarm set: RE color=YELLOW, class=CHASSIS, reason=VMHost RE 0 Disk 1 Missing
May 21 17:16:01.543 2020  R01-XXX craftd[6257]:  Minor alarm set, VMHost RE 0 Disk 1 Missing

Solution

The minor alarm "VMHost RE 0 Disk 1 Missing" appears when disk 1 in the Routing Engine 0 is missing. This alarm is caused when the disk is actually missing in the Routing Engine or the disk has turned defective.

Reseat the Routing Engine and check if the missing disk gets detected. The following CLI command can be used to confirm disk is missing for the affected Routing Engine:
show vmhost hardware re<RE slot number>

Manually checking the missing disk is NOT possible and even inserting the disk is also NOT possible. The only way to recover the faulty disk is by running:
request vmhost snapshot
 
 The "request vmhost snapshot" command will fail for the Routing Engine when the disk is missing. Run the following commands to try and clear the disk issue for the Routing Engine:
 request vmhost snapshot recovery re<RE slot number>
request vmhost snapshot partition re<RE slot number>
request vmhost snapshot recovery partition re<RE slot number>
 
Power cycle the affected Routing Engine from the other Routing Engine:
request vmhost power-off other-routing-engine
request vmhost power-on other-routing-engine
 
If the above steps fail well in clearing the alarm, perform a physical reseat for the affected RE and check. If the alarm persists, replace the affected RE.

If this doesn't solve the issue, please open a JTAC case.

Take a snapshot and recover the disk by using the below command:

> request vmhost snapshot

 

Additionally, customer reports after reseating the routing engine the issue is solve. 

To understand installing, upgrading, backing up, and recovering a VM host, see Installing, Upgrading, Backing Up, and Recovery of VM Host .

If the issue persists after performing the above steps, contact Juniper Support  for further investigation.

Modification History

2023-12-13 Updated solution as per feedback
2022-12-16: Updated solution.
2022-11-14: Updated solution.
2020-08-14: Updated cause section.

2024-5-16: Updated solution.

Related Information