Skip to main content

 Mware PSOD (Purple Screen of Death) 

-----------------------------------------------------------------------------------------

Causes

1. Hardware issues: Hardware failures, such as CPU, memory, or disk failures, can cause a PSOD.

2. Software bugs: Software bugs or errors in the ESXi code can cause a PSOD.

3. Configuration issues: Configuration errors, such as incorrect settings or incompatible hardware, can cause a PSOD.

4. Firmware issues: Firmware issues, such as outdated or corrupted firmware, can cause a PSOD.

==========================================================================================

Symptoms 

1. Purple screen: A purple screen with a white font appears, displaying an error message.

2. System crash: The ESXi host crashes, and all VMs running on it are terminated.

3. Error logs: Error logs are generated, providing information about the cause of the PSOD.

------------------------------------------------------------------------------------------

Troubleshooting PSOD:

1. Check error logs: Check the error logs to determine the cause of the PSOD.

2. Verify hardware: Verify that all hardware components are functioning correctly.

3. Update ESXi: Update ESXi to the latest version to ensure that any known bugs are fixed.

4. Check configuration: Check the configuration to ensure that all settings are correct.

Preventing PSOD:

----------------------------------------------------------------------------------------

1. Regularly update ESXi: Regularly update ESXi to the latest version.

2. Monitor hardware: Monitor hardware components for signs of failure.

3. Verify configuration: Verify that all configuration settings are correct.

4. Implement a backup strategy: Implement a backup strategy to ensure that all data is protected in case of a PSOD.

Comments

Post a Comment

Popular posts from this blog

Top 10 high-level EC2 scenario-based questions to challenge your AWS & DevOps skills

 Here are 10 high-level EC2 scenario-based questions to challenge your AWS & DevOps skills 1. Your EC2 instance is running but you can’t connect via SSH. What troubleshooting steps will you take?  Check Security Group inbound rules (port 22 open to your IP).  Verify Network ACLs (NACLs not blocking inbound/outbound).  Confirm instance’s Public IP / Elastic IP.  Validate Key Pair and correct permissions on .pem.  Ensure SSM Agent is installed (Session Manager can help).  Check system logs on the console for OS-level issues. 2. You terminated an EC2 instance by mistake. How can you prevent this in the future? Enable Termination Protection in EC2 settings. Use IAM permissions to restrict TerminateInstances. Tag critical instances and set resource policies. 3. Your EC2 instance needs to access an S3 bucket securely. What’s the best way to configure this? Best practice: Attach an IAM Role with least privilege policy to the EC2 instance. Avoid hardcoding...
Post a Comment
Read more

GitOps-Driven Management of VKS Clusters: Enabling GitOps on VCF 9.0 (Part 03)

  GitOps-Driven Management of VKS Clusters: Enabling GitOps on VCF 9.0 (Part 03) In the Part-02 blog, we walked through the process of deploying an Argo CD instance within a vSphere Namespace on  VMware Cloud Foundation (VCF) 9.0 , enabling a GitOps-based approach to manage Kubernetes workloads in a vSphere environment. With Argo CD successfully installed, we now have a powerful toolset to drive declarative infrastructure and application delivery. In this blog post, we’ll take the next step by demonstrating how to  provision and manage VKS clusters  directly through the Argo CD  UI and CLI . This allows us to fully operationalise GitOps within the private cloud, delivering consistency, scalability, and automation across the Kubernetes lifecycle. Importance of Managing the Kubernetes Cluster with a Gitops Approach Adopting a GitOps-based approach for managing Kubernetes clusters enables declarative, version-controlled, and automated operations by leveraging Git a...
Post a Comment
Read more
 https://knowledge.broadcom.com/external/article?articleNumber=389217 VMware Aria Suite Backup and Restore Documentation Issue/Introduction This article host backup and restore documentation for VMware Aria Suite 2019 product lines. Environment VMware Aria Suite 8.x VMware Aria Automation 8.x VMware Aria Automation Orchestrator 8.x Cause Technical documentation has been migrated from docs dot vmware dot com to  https://techdocs.broadcom.com . During this migration, some content considered End of Life (EOL) or End of General Support (EOGS) was not targeted for migration. Resolution PDF files are provided in this article while these documents are restored to https://techdocs.broadcom.com. Attachments Backup & Restore with EMC Avamar for VMware Aria Suite.pdf get_app Backup & Restore with Netbackup for VMware Aria Suite.pdf get_app VMware Aria Suite Backup and Restore by Using vSphere Data Protection.pdf get_app
Post a Comment
Read more