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

[MX/PTX] Minor Alarm: 'VMHost RE x Disk y File System Errors'

0

0

Article ID: KB36007 KB Last Updated: 02 Jul 2020Version: 1.0
Summary:

This article explains the meaning of the following alarm, 'VMHost RE 0 Disk 1 File System Errors' and indicates if any actions need to be taken:

Symptoms:

Alarm seen on the device:

root> show system alarms
7 alarms currently active
Alarm time               Class  Description
2019-08-05 12:41:41 UTC  Minor  VMHost RE 0 Disk 2 File System Errors
2019-08-05 12:41:41 UTC  Minor  VMHost RE 0 Disk 1 File System Errors
This alarm is seen when there is a file system error on the disk of the Routing Engine. 
Solution:

NG-RE has two SSDs: SSD1 and SSD2. The first disk connected with channel 0 is the primary disk. The other disk is considered as a backup. There are two sets of software boot images on the primary disk. We boot with one set, and when an upgrade is needed, it switches to use the other set. Similarly, on the rollback, we switch to the other set.

In the alarm 'VMHost RE x Disk y File System Errors', x–0 for RE0 and 1 for RE1 and y–1 for disk 1 and 2 for disk 2.

To clear the alarm, boot the affected Routing-engine from healthy disk and recover the impacted disk using the below command.

Command:

> request vmhost snapshot.

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.

To boot from the desired disk, execute request vmhost reboot { disk1, disk2} command.

Related Links

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