Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[Junos] Minor alarm: VMHost RE x Disk y Label Missing

0

0

Article ID: KB36005 KB Last Updated: 29 Jun 2020Version: 1.0
Summary:

This article explains the meaning of the following alarms seen on the device and indicates if any actions need to be taken:

XX@XXXX> show chassis alarms
4 alarms currently active
Alarm time               Class  Description
2019-09-04 03:22:54 UTC  Minor  VMHost RE 1 Disk 2 Label Missing
Cause:

The above minor alarms are seen on the device when the labels on the disk in the Routing Engine is missing. Sometimes the above alarms might be transient in nature.

Solution:

In alarm 'VMHost RE x Disk y Label Missing' - x–0 for RE0 and 1 for RE1 and y–1 for disk 1 and 2 for disk 2

Labels in the Routing Engine mean from which set the VM booted up.
labroot@lab> show vmhost version
Current root details, Device sda, Label: jrootp_P,
Partition: sda3
Current boot disk: Primary
Current root set: p
UEFI Version: NGRE_v00.53.00.0

The above VM host was booted from Set P from the Primary disk.

Due to the disk corruption/missing, the label may be missed and can be verified by the command below:
labroot@lab> show vmhost version | no-more
Current root details, Device sda, Label: jrootb_S, Partition: sda4
Current boot disk: Secondary
Current root set: b
Version get failed.
Warning: Unable to open /dev read-write (Is a directory). /dev has been opened read-only. 
Warning: Unable to open /dev read-write (Is a directory). /dev has been opened read-only. 
Error: /dev: unrecognised disk label /sbin/unified-disk-functions.sh: line 163: 0.02: 
syntax error: invalid arithmetic operator (error token is ".02").

In the above command, Label from Set P of the disk is missing due to which alarm is seen.

To clear the alarm, follow the steps below:
  1. Reboot the Routing-Engine from the healthy disk and check if the alarm is cleared.

    To boot from the desired disk, you execute the command: 

    request vmhost reboot { disk1, disk2} 
  2. Recover the impacted disk using the command below:

    > request vmhost snapshot.

Note: If the state of the primary disk (disk1) is good and the backup disk (disk2) has to be recovered then use the 'request vmhost snapshot' command to recover the backup disk assuming the Routing Engine is booted from the primary disk. If the state of the secondary disk is not known or the file systems in the disk are not in a consistent state, then include partition option in the command i.e. 'request vmhost snapshot partition'.

If the state of the backup disk (disk2) is good and the primary disk (disk1) has to be recovered then use the 'request vmhost snapshot' recovery command to recover the primary disk assuming the Routing Engine is booted from the backup disk. If the state of the primary disk is not known or the partition tables are in bad condition, then include partition option in the command i.e. 'request vmhost snapshot recovery partition'.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search