Error 16392 Opening Disk
Contents |
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vSphere™ > VMware ESXi 5 > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 5 Replies Latest reply: May 18, 2016 2:57 AM by systemww vmkfstools failed to lock the file 16392 RDM creating problem: Failed to reopen virtual disk: Failed to lock the
Vmware Cannot Open The Disk .vmdk Or One Of The Snapshot Disks It Depends On
file (16392). zelda110 Mar 22, 2013 12:45 PM When I tried this command I got this error, but the cannot open the disk or one of the snapshot disks it depends on. failed to lock the file VMDK file has been created./vmfs/volumes # vmkfstools -z /vmfs/devices/disks/naa.600605b00560fa6001f4b57b11ae893c "/vmfs/volumes/datastore2/10TB.VMDK"Failed to reopen virtual disk: Failed to lock the file (16392). I tried to add it to the VMit got this errorCannot
Cannot Open The Disk '/vmfs/volumes Failed To Lock The File
open the disk '/vmfs/volumes/514caade-11d8c0f6-7501-002590702bbc/10TB.VMDK' or one of the snapshot disks it depends on. Failed to lock the file
10740Views Tags: none (add) This content has been marked as final. Show 5 replies 1. Re: RDM creating problem: Failed to reopen virtual disk: Failed to lock the file (16392). Zifik Jun 24, 2013 5:53 AM (in response to zelda110) I just encountered the failed to open virtual disk failed to lock the file 16392 16392 error myself and it really had me frustrated for a while. Turns out that the solution was to create the VMDK file in a datastore folder that was NOT the large 2TB+ location. Here's more details of my setup for clarification and in case anyone else is looking for help. I'm still at the novice-intermediate skill level, so I apologize for anything that may be considered "poor practice".Mounting a 2TB+ RAID drive or virtual disk as a raw device mapping (RDM) using ESXi 5:Eight 3TB disks in a RAID 5 configuration using a LSI Logic controller. From within the RAID Controller 2 virtual disks were created. The first was about 1.5 TB and was for the purpose of storing all of the VMs. The remaining space, approx 17TB, was to be used for as file server storage.From within vSphere, mounted the 17TB disk. (Select server -> Configuration -> Storage -> Devices)Opened up SSH and logged in using PuTTY as root.Did the following as root:Used a combination of the next two commands to ensure I had the proper vm1.REALLY_LONG_HEX_OF_DISK value. Not sure if these stethis post when searching for help with a VM that will not power on. This post was written for a specific scenario related to missing snapshot files, but if you are merely trying to power on a VM that was working recently,
Module Diskearly Power On Failed.
you may be able to resolve the problem by simply delete any folders containing .LCK in
Vmware Failed To Lock The File Module Disk Power On Failed
the name from your virtual machine's folder, which would preserve any snapshot data. From time to time, I want to copy just the failed to lock the file vmware shared disk 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: https://communities.vmware.com/thread/440213?start=0&tstart=0 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 made to the virtual machine since the last snapshot: Open the *.vmx file in a text editor https://ardamis.com/2009/11/20/vmware-cannot-open-the-disk-xxxxxx-vmdk-or-one-of-the-snapshot-disks-it-depends-on/ 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. This entry was posted in Nonsense, Tutorials and tagged Microsoft, troubleshooting on 20 November 2009 by Oliver Baty. Post navigation ← A PHP function to sum values in associative arrays Circumventing Cisco Security Agent → 52 thoughts on “VMware "Cannot open the disk ‘XXXXXX.vmdk' or one of the snapshot disks it depends on."” colorzone 12 January 2010 at 1:22 am WinMount provides an easiest way to mount VMDK as a virtual disk. You can read or write to the vmdk file without loading the virtual system. Here shows you how to do: http://www.winmount.com/mount_vmdk.html nick 21 July 2010 at 9:42 am Thanks so much for posting this! You saved me a ton of time! KenPem 8 November 2010 at 4:45 am If this happens as the result of a crash, rather than intentionally as a "boot-clean" restart, and you're trying to recover, th
OS Discussion Free VMware Backup solution for ESXi OS © VMWare ESXi free compatible, hot & differential backup, mail report Brought to you by: danjgf Summary Files Reviews Support Wiki Discussion *** Please Donate *** Create Topic Stats Graph Forums General Discussion 184 Help Formatting Help Failed to https://sourceforge.net/p/xsibackup/discussion/general/thread/76a3c845/ lock the file (16392) Forum: General Discussion Creator: Tom Created: 2016-01-18 Updated: 2016-01-18 Tom - 2016-01-18 Hi, I am using XSIBACKUP 4.6.4 and ESXI 5.5 with 6 VMs. When I run xsibackup, two of the VMs are not hot-backing up with this error message: ERRORS FOUND: Failed to open '/vmfs/volumes/53c7da76-77199518-3ac0-d050991b6417/---/---.vmdk': Failed to lock the file (16392). [I have obviously replaced the VM's name with ---, but it's the identical error-message for the two VMs] I have the tried the "-D" option failed to for vmkfstools to find out more about the lock: Lock [type 10c00001 offset 74799104 v 470, hb offset 4087808 gen 411, mode 0, owner 00000000-00000000-0000-000000000000 mtime 100335 num 0 gblnum 0 gblgen 0 gblbrk 0] Addr <4, 164, 11>, gen 24, links 1, type reg, flags 0, uid 0, gid 0, mode 600 len 492, nb 0 tbz 0, cow 0, newSinceEpoch 0, zla 4305, bs 8192 As far as I can see, 'mode 0' would indicate, that the vmdk-file is failed to lock un-locked. This is as well the case for the other VM. I don't know how to proceed from here. Any clues how to find the root cause for this? Thanks, Tom If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Daniel J. García Fidalgo - 2016-01-18 If XSIBackup fails to lock the file it is becouse it is locked by something else, no doubt about it. So, run this command to find out which process is hooking it. root# lsof | grep .vmdk The upper command will show what vmdk files are locked. If the vmdk file you want to backup is locked by some process it can only be its own VM. So, find the process ID and run: ps | grep [process ID] You say "are not hot-backing up", what do you mean by that?, are you using the --backup-how=cold flag?, please give more details: command, program output, etc... If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Tom - 2016-01-18 This is the command, which I run as [root]: "/vmfs/volumes/datastore1/xsibackup" --backup-point=/vmfs/volumes/Backup/vmware --backup-type=custom --backup-vms="SBS 2011" XSIBackup PID: 1609803 Mon, 18 Jan 2016 12:33:36 +0000 Found --backup-point at /vmfs/volumes/Backup/vmware The e-mail report will not be sent becouse of the followig reasons: The --mail-from string has not been set. The --mail-to string has not been set. The --smtp-srv string