HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - VMware
- >
- VMWARE crash on
Operating System - VMware
1836438
Members
2600
Online
110100
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2019 08:38 AM
08-16-2019 08:38 AM
VMWARE crash on
HP Proliant DL380 Gen 9
ESXi VMWARE 6.0
Hello, I can't attach an image on the forums here but perhaps someone will understand what I am talking about. With our VMWARE setup, you'll notice I have opened up DATASTORE1. Inside the SQL VM you will see the following files.
SQL_1.vmdk is 500GB. This is where our SQLVM DB is located. The missing file is SQL_0.vmdk which was about 3.48 GB and that contains our Boot disk. Without the boot disk we cannot boot into the VM and extract anything from SQL_1.vmdk.
So the question is whether we can actually access that SQL_1.vmdk file by creating a new VM and moving it over? ( Thus we need the new SSD in there ). OR, we are out of luck.
Thank you!
Jim
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2019 08:40 AM
08-16-2019 08:40 AM
Re: VMWARE crash on HP ESxi
Actually these are the specs of our software.
Client version: 1.23.0
Client build number: 6506686
ESXi version: 6.5.0
ESXi build number: 7388607
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP