Anybody knows? Appreciate.
↧
Re: Why QAVG is so high ?
↧
Problem with recreating a missing descriptor file
Hi,
I trying to recreat vmdk file from flat.vmdk as VMware Knowledge Base , but i can't get into the section of the virtual machine:
/vmfs/volumes/5cb5fcec-19f64160-4478-14dae93d862e] cd ******
-sh: cd: can't cd to *******
Plz help.
↧
↧
Re: Problem with recreating a missing descriptor file
-sh: cd: can't cd to ...
Does the folder name have any special characters, or spaces in its name? Did you try to put the folder name in quotes, e.g. cd "My virtual machine"? Alternatively you may try the TAB extension for the folder name.
André
↧
Re: Problem with recreating a missing descriptor file
Thank you, Andre. Your recommendations helped!
↧
Re: Problem with recreating a missing descriptor file
vmkfstools -e "1C-Server Windows 2012.vmdk"
Failed to open disk link /vmfs/volumes/5cb5fcec-19f64160-4478-14dae93d862e/1C-Server Windows 2012/1C-Server Windows 2012.vmdk :The system cannot find the file specified (25)Disk chain is not consistent : The system cannot find the file specified (25)
Plz, help
↧
↧
Re: Problem with recreating a missing descriptor file
To be able to help I need some information.
As a first step, please run ls -lisa in the VM's folder and provide the command's output.
André
↧
Re: Problem with recreating a missing descriptor file
total 262153240
3844 8 drwxr-xr-x 1 root root 2100 Mar 31 11:14 .
4 1024 drwxr-xr-t 1 root root 1540 Mar 30 20:02 ..
8392452 262144000 -rw------- 1 root root 268435456000 Mar 30 17:31 1C-Server Windows 2012-flat.vmdk
364908292 1024 -rw------- 1 root root 8684 Mar 30 21:09 1C-Server Windows 2012.nvram
478154500 0 -rw------- 1 root root 481 Mar 31 10:22 1C-Server Windows 2012.vmdk
385879812 0 -rw------- 1 root root 0 Mar 30 21:09 1C-Server Windows 2012.vmsd
377491204 8 -rw------- 1 root root 2890 Mar 30 21:09 1C-Server Windows 2012.vmx
356519684 8 -rw------- 1 root root 3236 Mar 30 21:09 1C-Server Windows 2012.vmxf
402657028 1024 -rw------- 1 root root 41876 Mar 30 21:10 vmware-10.log
419434244 1024 -rw------- 1 root root 41793 Mar 30 21:12 vmware-11.log
436211460 1024 -rw------- 1 root root 41795 Mar 30 21:16 vmware-12.log
452988676 1024 -rw------- 1 root root 41793 Mar 30 21:24 vmware-13.log
469765892 1024 -rw------- 1 root root 41722 Mar 30 21:37 vmware-14.log
381685508 1024 -rw------- 1 root root 550106 Mar 30 21:09 vmware-9.log
494931716 1024 -rw------- 1 root root 41807 Mar 31 11:14 vmware.log
↧
Re: Problem with recreating a missing descriptor file
I assume that there's something wrong with the "1C-Server Windows 2012.vmdk" descriptor file. Please attach this file to a reply post, or copy&paste its contents.
André
↧
Re: Problem with recreating a missing descriptor file
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=fffffffe
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfs"
# Extent description
RW 524288000 VMFS "1C-Server Windows-flat.vmdk"
# The Disk Data Base
#DDB
ddb.adapterType = "lsilogic"
ddb.geometry.cylinders = "32635"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.longContentID = "add23fb4abf83a2566fdbd56fffffffe"
ddb.uuid = "60 00 C2 97 49 8d a0 49-da d6 b4 24 e8 82 f8 d6"
ddb.virtualHWVersion = "11"
~
↧
↧
Re: Problem with recreating a missing descriptor file
RW 524288000 VMFS "1C-Server Windows-flat.vmdk"
should be
RW 524288000 VMFS "1C-Server Windows 2012-flat.vmdk"
André
↧
Re: Problem with recreating a missing descriptor file
Thank you very mach, Andre!
↧
When will we get support for 4Kn / 4096 byte sector FC storage targets?
4K device targets have been shipping for years, and it's increasing impact to not have support. There is still only support for locally attached 4Kn SAS/SATA spinning disks. When will we get support for 4K / 4Kn targets over other interfaces? eg FC, iSCSI, NVMeOF, iSER, etc?
ref: vSphere 7.0 Storage Guide still shows the same limitations that we had around ~6.4 IIRC...
When you use 4Kn devices, the following considerations apply:
- ESXi supports only local 4Kn SAS and SATA HDDs
- ESXi does not support 4Kn SSD and NVMe devices, or 4Kn devices as RDMs
...
Thanks
↧
The need to run a chkdsk equivalent on a attached datastore?
My storage admin just told me that they are seeing possible corruption (maybe false positive) on a m disk in a v7000 SAN.
As they cant see inside a LUN they have presented to my hosts the SAN admin is suggesting I should run a chkdsk equivalent on my LUN/Datastore.
I have never come across this before and a bunch of googling didn't make me any smarter in this matter.
Now, I am not seeing any corruption of my VM's running on that datastore and obviously they would not see anything as they are abstracted from the storage.
Would this be a chkdsk from the console of the ESXi host? or perhaps something I can do via powercli. Any kind of service interruptions to expect or perhaps i should vacate the LUN/Datastore.
I spoke with my SAN admin and he mentioned he have seen false positives of corruption before on this array.
↧
↧
Win 2012r2 physical compatibility RDM free space DELL SCv2020
Hi,
We have a Win 2012r2 VM running on 6.0 ESXi. It has attached 4 RDM disks in physical compatibility mode. These LUNs belongs to a DELL SCv2020 compellent.
Each LUN/Volume is configured with ~6TB in the compellent. In the VM the disks are not fully used, there are ~1TB free in each one. However, I don't see that free space in the compellent.
Is this behaviour correct? Do I have to run some command in the VM so storage can reclaim free space?
Thanks.
↧
Re: Win 2012r2 physical compatibility RDM free space DELL SCv2020
Welcome to the Community,
please take a look at Solved: Compellent SC2020 Auto-space reclamation does not work with vmware 6.5 - Dell Community to see whether this describes the reason why unmap is not working for you.
André
↧
Re: Locked files - VMFS 6
Hello,
Have you created a post with the steps to try and fix this?
I've just had this happening in my homelab. After an issue with the storage array, which led to a disk replacement, I now have 5-6 VMs which are inaccesible/orphaned and their vmx is locked by one of the ESXi hosts. Of course I've pretty much tried everything, host reboots, storage array reboot etc. I will not release the lock. Since it's my homelab I'm pretty much open to try anything.
Thank you!
↧
Re: Locked files - VMFS 6
This is what I do nowadays:
plan A - safest option :
extract the VMs with Linux
plan B - smartest option but not for the faint at heart:
patch the .vh.sf file
send from iphone
↧
↧
Unable to create virtual machines in new datastore--frustrated beyond belief! :/
Hey all,
I am about to tear out the rest of my hair. I am hoping someone here has seen this behavior and can point me to a solution. I simply have tried everything I can think of, an nothing is making sense.
Summary: I have a Samsung 840 SSD, good for about 700GB, installed along with other SSDs in a box running ESXi 6.7
When I try to create a new VMFS6 datastore on this SSD, the process goes without issue. I have tried this under regular ESXi 6.7 UI, under ssh using command-line tools, and under vCenter 6.7 -- regardless, creating the datastore works just fine, as expected.
However, creating a new VM using that DS, or migrating an existing VM to that new DS, fails. EVERY TIME. The errors vary, they never seem to be the same, but it is always a combination of:
- Unable to load configuration file '/vmfs/volumes/5ea9ef7c-23eb5578-3738-000af7a1d9e1/VM1/VM1.vmx'
- An error occurred while creating a temporary dictionary file: Error.
- Failed - The file is too large
No matter what though, the VM fails to be created/migrated. Google and other searches have yielded no help for this problem.
Of note: I can browse the new datastore, and upload files. I can create folders. I can ssh to the host and create files. I can create a text file using the text editor vi and read the file using cat. I can delete the files. In other words, the datastore seems to be perfectly happy. It just won't take virtual machines!
When I have tried creating the DS under command line, I have used partedUtil to create the partition (starting at sector 2048 as recommended for VMFS6) and then vmkfstools for creating the VMFS store. Currently, the SSD has a GPT format. I have tried taking the SSD into a Linux machine and clearing out all partitions there, and trying again under ESXi. Same result: the datastore is created but VMs can't be written to it. I have tried leaving a little space at the front of the partition and some space at the end of the partition. I did this because examining the other SSD's partitions, they seemed to have some free space before and after. I figured I would try that. No dice.
I truly am baffled. I don't know what could possibly be wrong with this datastore in terms on creating VMs or VMs being migrated to it, but being totally fine for writing files and directories directly or using the Browsing UI.
Here is a quick movie I made which shows the failed process, and you can also see I am displaying the info for the device in ESXi under ssh.
I am also attaching an image with the same information being shown in the ssh console.
If you would like any more details, I can provide them. If anyone can help, I will be forever grateful.
# polo
↧
How Should VMware do Kubernetes Backup for Project Pacific?
Hello All!
I'm the product manager responsible for the data protection features of vSphere and I'm here to ask a favor. VMware has a robust set of solutions for protecting VMs and we want to have a similar set of offerings for containers and their data. Would you please spend a few minutes to help me understand how you protect containerized workloads today and how you want to do so in the future?
The survey: https://vmwarek8sbackup.surveyanalytics.comhttps://vmwarek8sbackup.surveyanalytics.com/
If you have any questions or would prefer to just set-up a few minutes to help me understand your needs please reach out: rhammond@vmware.com
Stay safe!
↧
Re: Unable to create virtual machines in new datastore--frustrated beyond belief! :/
Do you see anything in the vmkernel.log of the ESXi that rejects loading your Test-VMs ?
↧