Skip to main content

 A Photon OS based virtual appliance fails to start

https://knowledge.broadcom.com/external/article?articleNumber=326323

Products

VMware Cloud FoundationVMware vCenter ServerVMware SDDC ManagerVMware Aria SuiteVMware Site Recovery Manager 8.xVMware Live Recover

Issue/Introduction

  • After rebooting, power outage, datastore issue Photon OS appliance the system enters emergency mode
  • The appliance fails to start and there is an error similar to:

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on the environment.


Environment

  • VMware vCenter Server 6.x
  • VMware vCenter Server 7.x
  • VMware vCenter Server 8.x
  • VMware SDDC Manager 4.x
  • VMware SDDC Manager 5.x 
  • VMware Aria Suite Lifecycle 8.x
  • VMware Aria Automation 8.x
  • VMware Aria Automation Orchestrator 8.x
  • VMware Identity Manager 3.3.7
  • VMware Live Site Recovery 9.x
  • VMware Site Recovery 8.8
  • VMware vSphere Replication 8.x
  • VMware vSphere Replication 9.x

Cause

This issue occurs when the virtual appliances experience file inconsistencies after being forcefully halted as the result of a storage failure, power failure, or software crash.

Resolution

To resolve this issue, scan and correct the filesystem by running the fsck command automatically (preferred) or manually.
 
Note: Before proceeding, take a snapshot of the affected virtual appliance.
  1. Reboot the virtual appliance, and immediately after the OS starts, press 'e' to open the GNU GRUB Edit Menu.
  2. Locate the line that begins with the word linux.

Option 1
At the end of the line, add fsck.repair=yes then press F10 to continue booting the appliance. This will force the default filesystem check to auto-resolve any issues. The appliance may silently reboot several times to fix needed issues.

Option 2
At the end of the line, add systemd.unit=emergency.target then press F10 to continue booting the appliance.

1. Find the filesystems by running the following commands:

  • $ /bin/sh
  • $ /bin/mount
  • $ blkid

2. Run this command against the mount point that has issue:

$ e2fsck -y /dev/<mount>

The -y switch will fix the nodes automatically. Replace <mount> with the mount point experiencing the issue. Ex: $ e2fsck -y /dev/sda3

3. Power OFF the virtual appliance.

4. Power ON the virtual appliance.

Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
Post a Comment
Read more

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
Post a Comment
Read more