failed to lock the file vmware что делать
Failed to lock the file vmware что делать
We are having an isue with a windows guest VM.
Just restarted from the guest OS cleanly.
When I checked on vpshere client (we are not managing through VCenter), I saw errors like file locks.
When I consulted the vmware.log of the file I saw errors like below:
k’ : Failed to lock the file (40003) (0x2013).
2015-09-08T19:46:25.003Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ locked (try 0)
2015-09-08T19:46:25.029Z| Worker#0| I120: DISKLIB-CBT : Initializing ESX kernel change tracking for fid 185988.
2015-09-08T19:46:25.029Z| Worker#0| I120: DISKLIB-CBT : Successfuly created cbt node 2d684-cbt.
2015-09-08T19:46:25.029Z| Worker#0| I120: DISKLIB-CBT : Opening cbt node /vmfs/devices/cbt/2d684-cbt
2015-09-08T19:46:25.029Z| Worker#0| I120: DISKLIB-LIB : Opened «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk» (flags 0xa, type vmfs).
2015-09-08T19:46:25.029Z| Worker#0| I120: DISK: Disk ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk’ has UUID ’60 00 c2 9e 3d 4b a7 bf-5d 5b 83 21 cf 6a 3a 0f’
2015-09-08T19:46:25.029Z| Worker#0| I120: DISK: OPEN ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk’ Geo (4568/255/63) BIOS Geo (0/0/0)
2015-09-08T19:46:25.060Z| Worker#1| I120: DISKLIB-VMFS : «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002-delta.vmdk» : open successful (10) size = 30987591680, hd = 284293. Type 8
2015-09-08T19:46:25.060Z| Worker#1| I120: DISKLIB-DSCPTR: Opened [0]: «New Virtual Machine-000002-delta.vmdk» (0xa)
2015-09-08T19:46:25.060Z| Worker#1| I120: DISKLIB-LINK : Opened ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002.vmdk’ (0xa): vmfsSparse, 73400320 sectors / 35 GB.
2015-09-08T19:46:25.082Z| Worker#1| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ : Failed to lock the file (40003) (0x2011).
2015-09-08T19:46:25.082Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ locked (try 0)
2015-09-08T19:46:25.339Z| vmx| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ : Failed to lock the file (40003) (0x2013).
2015-09-08T19:46:25.339Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ locked (try 1)
2015-09-08T19:46:25.384Z| Worker#1| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ : Failed to lock the file (40003) (0x2011).
2015-09-08T19:46:25.384Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ locked (try 1)
2015-09-08T19:46:25.642Z| vmx| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ : Failed to lock the file (40003) (0x2013).
2015-09-08T19:46:25.642Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ locked (try 2)
2015-09-08T19:46:25.686Z| Worker#1| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ : Failed to lock the file (40003) (0x2011).
2015-09-08T19:46:25.686Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ locked (try 2)
2015-09-08T19:46:25.944Z| vmx| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ : Failed to lock the file (40003) (0x2013).
2015-09-08T19:46:25.944Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ locked (try 3)
2015-09-08T19:46:25.989Z| Worker#1| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ : Failed to lock the file (40003) (0x2011).
2015-09-08T19:46:25.989Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ locked (try 3)
2015-09-08T19:46:26.246Z| vmx| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ : Failed to lock the file (40003) (0x2013).
2015-09-08T19:46:26.246Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ locked (try 4)
2015-09-08T19:46:26.291Z| Worker#1| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ : Failed to lock the file (40003) (0x2011).
2015-09-08T19:46:26.291Z| Worker#1| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ locked (try 4)
2015-09-08T19:46:26.549Z| vmx| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ : Failed to lock the file (40003) (0x2013).
2015-09-08T19:46:26.549Z| vmx| I120: OBJLIB-FILEBE : FileBEOpen: can’t open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk’ : Failed to lock the file (262146).
2015-09-08T19:46:26.549Z| vmx| I120: DISKLIB-VMFS : «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004-delta.vmdk» : failed to open (Failed to lock the file): ObjLib_Open failed. Type 8
2015-09-08T19:46:26.549Z| vmx| I120: DISKLIB-LINK : «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004.vmdk» : failed to open (Failed to lock the file).
2015-09-08T19:46:26.549Z| vmx| I120: DISKLIB-CHAIN : «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004.vmdk» : failed to open (Failed to lock the file).
2015-09-08T19:46:26.549Z| vmx| I120: DISKLIB-LIB : Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004.vmdk’ with flags 0xa Failed to lock the file (16392).
2015-09-08T19:46:26.549Z| vmx| I120: DISK: Cannot open disk «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004.vmdk»: Failed to lock the file (16392).
2015-09-08T19:46:26.549Z| vmx| I120: Msg_Post: Error
2015-09-08T19:46:26.549Z| vmx| I120: [msg.fileio.lock] Failed to lock the file
2015-09-08T19:46:26.549Z| vmx| I120: [msg.disk.noBackEnd] Cannot open the disk ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000004.vmdk’ or one of the snapshot disks it depends on.
2015-09-08T19:46:26.593Z| Worker#1| I120: AIOGNRC: Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ : Failed to lock the file (40003) (0x2011).
2015-09-08T19:46:26.593Z| Worker#1| I120: OBJLIB-FILEBE : FileBEOpen: can’t open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk’ : Failed to lock the file (262146).
2015-09-08T19:46:26.593Z| Worker#1| I120: DISKLIB-VMFS : «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001-flat.vmdk» : failed to open (Failed to lock the file): ObjLib_Open failed. Type 3
2015-09-08T19:46:26.593Z| Worker#1| I120: DISKLIB-LINK : «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk» : failed to open (Failed to lock the file).
2015-09-08T19:46:26.593Z| Worker#1| I120: DISKLIB-CHAIN :»/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002.vmdk»: Failed to open parent «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk»: Failed to lock the file.
2015-09-08T19:46:26.593Z| Worker#1| I120: DISKLIB-CHAIN : «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000001.vmdk» : failed to open (The parent of this virtual disk could not be opened).
2015-09-08T19:46:26.596Z| Worker#1| I120: DISKLIB-VMFS : «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002-delta.vmdk» : closed.
2015-09-08T19:46:26.596Z| Worker#1| I120: DISKLIB-LIB : Failed to open ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002.vmdk’ with flags 0xa The parent of this virtual disk could not be opened (23).
2015-09-08T19:46:26.638Z| Worker#1| I120: DISKLIB-VMFS : «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002-delta.vmdk» : open successful (8) size = 30987591680, hd = 317061. Type 8
2015-09-08T19:46:26.638Z| Worker#1| I120: DISKLIB-DSCPTR: Opened [0]: «New Virtual Machine-000002-delta.vmdk» (0x8)
2015-09-08T19:46:26.638Z| Worker#1| I120: DISKLIB-LINK : Opened ‘/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002.vmdk’ (0x8): vmfsSparse, 73400320 sectors / 35 GB.
2015-09-08T19:46:26.638Z| Worker#1| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 1, numSubChains = 1
2015-09-08T19:46:26.638Z| Worker#1| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 317061, extentType = 0
2015-09-08T19:46:26.639Z| Worker#1| I120: DISKLIB-LIB : Resuming change tracking.
2015-09-08T19:46:26.672Z| Worker#1| I120: DISKLIB-CBT : Initializing ESX kernel change tracking for fid 317061.
2015-09-08T19:46:26.672Z| Worker#1| I120: DISKLIB-CBT : Successfuly created cbt node 8d688-cbt.
2015-09-08T19:46:26.672Z| Worker#1| I120: DISKLIB-CBT : Opening cbt node /vmfs/devices/cbt/8d688-cbt
2015-09-08T19:46:26.672Z| Worker#1| I120: DISKLIB-LIB : Opened «/vmfs/volumes/51841f27-2b034b60-4bcb-0006f62bb2d8/New Virtual Machine/New Virtual Machine-000002.vmdk» (flags 0x8, type vmfsSparse).
Tech Kiranangal
Technical Blogs Created For Server/Desktop/Network Virtualization
Thursday, October 8, 2020
Power On virtual machine: Failed to lock the file. Cannot open the disk. one of the snapshot disks it depends on
Unable to Power on Virtual Machine
Unable to Consolidate Virtual Machine Snapshot disks.
Unable to Clone VM.
It gives below Symptoms.
1. While attempting to power on giving below error.
«Power On virtual machine:Failed to lock the file
See the error stack for details on the cause of this problem.
Time: 10/9/2020 6:37:25 AM
vCenter Server: MYVCENTER.MYDOMAIN.COM
An error was received from the ESX host while powering on VM MYVM001.
Failed to start the virtual machine.
Cannot open the disk ‘/vmfs/volumes/594d0000-d290000-500-00000000002/MYVM001/MYVM001-000002.vmdk’ or one of the snapshot disks it depends on.
Failed to lock the file»
Failed to open file ‘MYVM001-delta.vmdk’; Requested flags 0x4008, world: 1197120 [vmx-vthread-8], (Existing flags 0x4008, world: 43796 [unknown]): Busy
Failed to open disk link /vmfs/volumes/5b4d1233-3e1234-1f5b-0123211000/VM001-000001.vmdk :Failed to lock the file (16392)Disk chain is not consistent : Failed to lock the file (16392)
5. virtual machine disk descriptor file shows normal and CID chain is not broken.
The VMDK or Delta VMDK is locked by one of the esxi in the cluster. Even if we move the VM in the particular Host, VM will fail to power on or consolidate disk.
To identify which disk is locked, refer the /var/log/vmkernal.log
Identify the ESXI host which is currently have lock on the Delta vmdk or VMDK with below command.
vmfsfilelockinfo Version 1.0
Looking for lock owners on «MYVM001-000001-delta.vmdk»
«MYVM001-000001-delta.vmdk» is locked in Exclusive mode by host having mac address [’00:20:b2:01:10:01′]
Found 2 ESX hosts from Virtual Center Server.
Searching on Host MY-ESXI-01.MYCOM.MYDOMAIN.COM
Searching on Host MY-ESXI-02.MYCOM.MYDOMAIN.COM
MAC Address : 00:20:b2:01:10:01
Host owning the lock on the vmdk is MY-ESXI-02.MYCOM.MYDOMAIN.COM, lockMode : Exclusive
Total time taken : 0.38 seconds.
Above output saying, disk is locked by MY-ESXI-02.MYCOM.MYDOMAIN.COM with MAC Address 00:20:b2:01:10:01.
Steps to Clear ESXi Lock:
1. Put the host in maintenance.
Lock will be cleared during ESXi reboot and we will be able to power on or consolidate snapshot of VM.
ИТ База знаний
Полезно
— Онлайн генератор устойчивых паролей
— Онлайн калькулятор подсетей
— Руководство администратора FreePBX на русском языке
— Руководство администратора Cisco UCM/CME на русском языке
— Руководство администратора по Linux/Unix
Навигация
Серверные решения
Телефония
FreePBX и Asterisk
Настройка программных телефонов
Корпоративные сети
Протоколы и стандарты
Блокировка файлов виртуальной машины на ESXi
В этой статье мы расскажем как решить проблему с блокировкой файлов в ESXi.
Интенсив по Виртуализации VMware vSphere 7
Самое важное про виртуализацию и VMware vSphere 7 в 2-х часовом онлайн-интесиве от тренера с 30 летним стажем. Для тех, кто начинает знакомство с виртуализацией и хочет быстро погрузиться в предметную область и решения на базе VMware
Проблема
Решение
Цель блокировки файлов
Для предотвращения непредвиденных изменений в ценные системные файлы и файлы виртуальной машины, их необходимо заблокировать. В определенных обстоятельствах блокировка сохраняется, даже с выключенной виртуальной машиной. Таким образом, другие ESXi хосты не смогут получить доступ к заблокированным файлам, даже если виртуальная машина не запускается.
Файлы виртуальной машины, заблокированные во время выполнения, включают в себя:
Быстрый первичный тест
Действия по устранению неполадок: поиск хоста заблокированного файла
Чтобы определить заблокированный файл, попробуйте включить виртуальную машину. Во время включения питания ошибка может отображаться или записываться в журналы виртуальной машины. Ошибка и запись в журнале идентифицируют виртуальную машину и файлы:
Например:
Снятие блокировки
Внимание: для безопасного извлечения файлов машина должна быть выключена.
Примечание: Тома VMFS не имеют .lck файлов. Механизм блокировки для томов VMFS расположен в метаданных тома VMFS.
Проверка целостности файла конфигурации виртуальной машины (.vmx)
Интенсив по Виртуализации VMware vSphere 7
Самое важное про виртуализацию и VMware vSphere 7 в 2-х часовом онлайн-интесиве от тренера с 30 летним стажем. Для тех, кто начинает знакомство с виртуализацией и хочет быстро погрузиться в предметную область и решения на базе VMware
ERROR Failed to get exclusive lock on the configuration file. Another VMware process might be running using the configuration file
I have been using a virtual machine for a long time and have never had problems starting but now I have a problem:
Whenever I try to start it shows this error:
If I click OK, the next message is:
I tried to remove the vmx.lck folders, but that did not help.
I use windows operating system on local computer.
5 Answers 5
The above comment from azbarcea is what worked for me. If you can’t delete the files because it says they’re in use, restart the machine, then delete the files. Also remember to delete the any folders with lck files
These are the consequences of Windows updating. I rolled back to the previous version and it worked for me.
Try restarting your system..I have faced the same issue solved by just restarting the system.
This problem was solved by Repair VMWare Installation as doing it, all running files in background are closed here is a link to help you out in this situation https://www.majorgeeks.com/content/page/vmware_failed_to_get_exclusive_lock_on_the_configuration_file_error.html
If so ended all of them and tried to open the VM again.
Not the answer you’re looking for? Browse other questions tagged vmware vmware-player or ask your own question.
Related
Hot Network Questions
Subscribe to RSS
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.12.6.40898
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
Failed to start the virtual machine. Failed to lock the file.
I just took on a new position and new to VMWare. One of my VSpheres has this error streaming:
I know failing to lock a file means its in use. How do I find out what’s using it?
I’m a little fuzzy (OK, a lot fuzzy) on the terms and their relation to each other. ESXi is the bit that makes the VMs on the physical box, and vCenter is the part that manages all the ESXi boxes? And then the vSphere Client connects to vCenter to let you administer all of it?? I have an app called VMWare Horizon Client. it seems to be something like Remote Desktop Manager?
vSphere Web Client: Version 6.0.0 Build 3617395
vSphere Client: Version 6.0.0 Build 14472085
VMWare vCenter Server: Version 6.0.0 Build Build 3634793
VMWare ESXi: Version 6.0.0 Build 4510822
VMWare Horizon Client: 4.5.0 build-5650915
16 Replies
The storage is a Nimble-HF20 AF-209660 (S/W Version:5.0.7.200), something else I am not very familiar with. I know it takes an hourly and a daily recovery point and replicates them to our other location. The circuit between the two locations is a super crappy 10mbps pipe, so the hourly snapshots never transfer. Their retention policy is only 24 hours. The daily ones queue up as well because it takes days to transfer one snapshot. If I’m looking at this correctly, our last valid backup is from 5-18. This is better than when I started 2 weeks ago; replication had stopped because only 1 of the 2 smaller Nimbles at the remote site was being used to store the two volumes from the main Nimble, and that machine was full.
Anyone else smell broken snapshot chain?
Your assumptions about ESXi, vCenter and vSphere client are right on. I’m wondering if those nimbles are using the built in vmware snapshotting to somehow replicate the VMs to the off-site Nimble? I bet you got snapshots, from within vSphere, can you check to see if this VM has any snapshots or needs consolidation?
The Needs Consolidation is a column that can be added to the view.
Looks like there is an active snapshot somewhere that needs to be consolidated. By the way, vSphere 6.0 is EOL and you need to migrate asap since there is no support (as long as your servers are on the VMware HCL for the current versions). Does the organisation you work for have an active support contract with VMware? It entitles you to upgrades of any paid VMware products you have.
The circuit between the two locations is a super crappy 10mbps pipe, so the hourly snapshots never transfer. Their retention policy is only 24 hours. The daily ones queue up as well because it takes days to transfer one snapshot. If I’m looking at this correctly, our last valid backup is from 5-18.
If I correctly understand what you are saying, your current situation is pretty dangerous in terms of possible data loss. Your ongoing replication isn’t working due to limited bandwidth between the sites, plus you should take care when using snapshots since they do not replace backups in any way http://www.vmwareblog.org/snapshots-checkpoints-alone-arent-backups/. Try to rethink your backup strategy first to mitigate data loss risks. After that, proceed to the DR/replication strategy to minimize downtime.
I looked at that VMWare article and tried running the commands they mention to find out what has the file locked. I see nothing
There are no lock files in the directory, so I proceeded to the article referenced in the one CrankyAvenger recommended to verify the integrity of the vm files. After following those steps and reregiistering the VM, I still have the same issue. 🙁
Looks like there is an active snapshot somewhere that needs to be consolidated. By the way, vSphere 6.0 is EOL and you need to migrate asap since there is no support (as long as your servers are on the VMware HCL for the current versions). Does the organisation you work for have an active support contract with VMware? It entitles you to upgrades of any paid VMware products you have.
The 3 servers are all Lenovo System X 3650’s, and they appear on the HCL, so *phew*!
No virtual machines need consolidation according to the Needs Consolidation column.
Fuu! Good catch! I should have copied and pasted.
Here’s the results of the correct command:
So the files aren’t locked by another process. but the VM won’t boot because it can’t lock the file. I unregistered and reregistered the VM, and that didn’t correct the issue, so the file itself must be hosed. This is one machine in a pool of machines. I don’t think there’s much about it that is unique from the other 9. If I can verify that is true, I’ll just dump this one entirely and clone one of the other 9 VMs as a new DSM_Basic10.
Edited Jun 24, 2020 at 20:56 UTC
Here’s what a section of VMX file from one of my test VM’s looks like with an active snapshot:
sata0:0.present = «TRUE»
scsi0:0.deviceType = «scsi-hardDisk»
scsi0:0.fileName = «xxxx-xxxx-000001.vmdk»
the ‘xxxx-xxxx’ is the actual VM name.
Here is the same section of the VMX file after removing the snapshot:
sata0:0.present = «TRUE»
scsi0:0.deviceType = «scsi-hardDisk»
scsi0:0.fileName = «xxxx-xxxx.vmdk»
If you are feeling gutsy, download the VMX file, edit the fileName entry appropriately, and upload it back to the datastore. See if there’s any change in power-on behavior.
«then you should take a look at the VMX file to see if there’s an entry in it for a snapshot delta file.» What you say makes sense. WinSCP and edittingb text files is something I think I can handle. 😉
Sadly, no dice. The vmx file makes no mention of an file with 000001 in the filename (or anything remotely close to that).
However, I also looked at the log file and saw that DSM_Basic10-flat.vmdk was having issues, so I ran VMFSfilelockinfo on it and found that it was locked. Now I just need to find the machine with that MAC address.
I’ve also learned that there is an ongoing issue with client getting a black screen on login. My googling suggests this is an issue with differing versions of VMView Horizon client. I think my bigger issue right now is upgrading all the components from version 6 to 6.7, then making sure all the Horizon clients are installed correctly.
I’ll circle back to this once that’s handled, until then thanks for all the help gents. It is greatly appreciated!
I’m a little fuzzy (OK, a lot fuzzy) on the terms and their relation to each other. ESXi is the bit that makes the VMs on the physical box, and vCenter is the part that manages all the ESXi boxes? And then the vSphere Client connects to vCenter to let you administer all of it??
Yes, all of this is correct, except vSphere = management of multiple vCenters (and yes, vCenter = mgmt of multiple ESXi hosts). I would personally use the term ESXi «host» and/or ESXi server instead of «box,» but yes, you have the concept of vSphere.
I have an app called VMWare Horizon Client. it seems to be something like Remote Desktop Manager?
Not exactly. The Horizon Client connects you to a VDI desktop, which is hosted on a Horizon View Connection Server (in conjunction with a VM in vSphere). Conceptually yes, it’s similar to Remote Desktop, but it’s very different from technical perspective in how it works. You could just google «VDI vs RDS» to get the overview.