今天我公司做的虛擬化服務器出現故障意外重啟了，主系統啟動之后，在啟動VMware虛擬機的時候出現了Cannot open the disk '*.vmdk' or one of the snapshot disks it depends on.Reason: Failed to lock the file.的錯誤，一個虛擬機無法啟動將影響到很多用戶的使用，所以我馬上開始尋找解決Reason: Failed to lock the file的辦法！于是我到百度搜索了一下這個錯誤的具體原因，搜索結果中給出了兩種解決辦法！
解決辦法一：
1、在VMware該虛擬機路徑下的所有.lck文件和文件夾下刪除或遷移至其它目錄，一般就可以解決了。
2、如果再次啟動VMware的Windows Vista系統失敗，嘗試右鍵虛擬機出錯的系統->Settings->Hardware->Hard Disk->Utilities->Map->映射虛擬硬盤到Z:/
3、斷開虛擬硬盤，重新加載，啟動。系統就可以正常啟動了
經實驗此辦法以失敗結 束。如果有遇到Cannot open the disk '*.vmdk' or one of the snapshot disks it depends on.Reason: Failed to lock the file錯誤的朋友不妨也試一下。如果您實驗成功了，請給我們留言，以便我們進行更好的技術交流
解決辦法二：
使用記事本打開*.VMX文件上加上一行代碼disk.locking = "FALSE"，重新啟動該虛擬機。
使用方法二，問題得到 解決，重新啟動VMware正常啟動，不會再出現Cannot open the disk '*.vmdk' or one of the snapshot disks it depends on.Reason: Failed to lock the file.錯誤。
希望各位從事虛擬化的朋友能有所幫助，也歡迎各位來我站踴躍投稿！
感謝作者的分享，偶使用方法1第1步就解決了
問題出現的原因：
虛擬磁盤(.vmdk)本身有一個磁盤保護機制，為 了防止多臺虛擬機同時訪問同一個虛擬磁盤(.vmdk)帶來的數據丟失和性能削減方面的隱患，每次啟動虛擬機的時候虛擬機會使用擴展名為.lck（磁盤 鎖）文件對虛擬磁盤(.vmdk)進行鎖定保護。當虛擬機關閉時.lck（磁盤鎖）文件自動刪除。但是可能由于您非正常關閉虛擬機，這時虛擬機還沒來得及 刪除您系統上的.lck（磁盤鎖）文件，所以當下次您啟動虛擬機的時候出現了上述錯誤。
VMware “Cannot open the disk ‘XXXXXX.vmdk’ or one of the snapshot disks it depends on.”
From time to time, I want to copy just the minimum files for a VMware virtual machine: the two .vmdk files and the .vmx file. After moving those files to a new location or deleting a snapshot file, attempting to boot the virtual machine returns the following error message:
Cannot open the disk ‘XXXXXX.vmdk’ or one of the snapshot disks it depends on.
Reason: The system cannot find the file specified.
I’ve found that following the steps below fixes the problem and allows me to boot the virtual machine as it existed at the time of creation. DO NOT USE these steps if you need to retain any changes to the machine:
Open the *.vmx file in a text editor and find the line that refers to the old snapshot file, which will look something like:
scsi0:0.fileName = “XXXXXX-000002.vmdk”
or
ide0:0.fileName = “XXXXXX-000002.vmdk”
Change the value to the filename of the ~1kb .vmdk file (which happens to be the same as the name of the VM). For example, if your virtual machine was named “Windows XP Professional”, the line would read:
scsi0:0.fileName = “Windows XP Professional.vmdk”
Power on the VM. It should boot normally, but because the snapshot file is missing, the machine will boot to an earlier state.