Adding an existing hard drive in VMWare vSphere 5 fails to add disk scsi0:1

Hello EE
When I go into Edit Settings and add a Hard Drive choosing existing hard drive I get the following error:
Failed to add disk scsi0:1
Failed to power on scsi0:1
Reason: Failed to lock the file
Cannot open the disk '/vmfs/volumes....vmdk' or one of the snapshot disks it depends on

Some VMs I can.  Until I get these others working I can't get my backup software working.
Why can't I add these?
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
that is correct, when taking a snapshot it takes the lock off the parent disk, as it writes to a new delta file.

so technically the parent should be lock free.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It seems you are adding a virtual disk, that has an existing snapshot?

you need to remove (merge) the snapshot first possibly.

A snapshot is NOT a backup of a VM; that is a gross misconception.

A snap shot is a way to preserve a point in time when the VM was running OK before making changes. A snapshot is NOT a way to get a static copy of a VM before making changes.  When you take a snapshot of a VM what happens is that a delta file gets created and the original VMDK file gets converted to a Read-Only file.  There is an active link between the original VMDK file and the new delta file.  Anything that gets written to the VM actually gets written to the delta file.   The correct way to use a snapshot is when you want to make some change to a VM like adding a new app or a patch; something that might damage the guest OS. After you apply the patch or make the change and it’s stable, you should really go into snapshot manager and delete the snapshot which will commit the changes to the original VM, delete the snap, and make the VMDK file RW. The official stance is that you really shouldn’t have more than one snap at a time and that you should not leave them out there for long periods of time. Adding more snaps and leaving them there a long time degrades the performance of the VM.  If the patch or whatever goes badly or for some reason you need to get back to the original unmodified VM, that’s possible as well.  

I highly recommend reading these 2 articles on VMware Virtual Machine Snapshots:

Understanding Snapshots -
Snaphot Best Practices -

Also check out the following Snapshot Articles by Eric Siebert

bergquistcompanyAuthor Commented:
No I am trying to mount an existing disk from VM1 to VM2 and getting this error.  I do not have any shapshots on either VM.
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
make sure vmdk is not in use.

other VM is not in use?

check using lsof at the console to check if file is in use.

also see here
bergquistcompanyAuthor Commented:
As soon as you said that about snap shots I started reading and thinking I can't mount it if it's added to VM1 and that machine is on, but I am having an issue with Veeam and they told me that until I can mount the disk from VM1 to VM2 (Veeam server) or any other for that matter I won't be able to use Veeam hot swap and get a successful backup.

Right now none of my Windows VMs backup as they all error about hot add and I was told that through the manual add it fails so it's VMWare not Veeam.  I think they were mistaken.
I wanted to confirm as I thought it was in use, but they are more familiar with their software so wanted to make sure my virtual environment wasn't misconfigured first.  

To clarify if VM1 is on with HD added and I try to add the .vmdk from VM1 to VM2 as an existing disk it will not work unless it is powered down?  I think I may need to revisit Veeam.  Thank you!
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
you cannot add another disk to a VM if is on.

Veeam Hot Add uses the Storage API, to Hot Add a powered on VM disk to itself by leveraging vmware snapshots
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
So you did not Solve your Previous Question with Hot Add?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Just to clarify my last statement, you can only add virtual machine disks to a powered ON VM, if the virtual machine disk you are adding from another VM is powered OFF.

So you are still having issues with Hot Add and Veeam?
bergquistcompanyAuthor Commented:
They took a snapshot of VM1 then tried adding the existing disk to the Veeam server and after the higher tier came on and said yes after you take the snapshot you should be able to mount the disk to another VM, I was premature after asking them how it was possible with VM1 powered on to believe them that it was a VM issue since our infrastructure is new.

Thank you for the clarification as it appears I prematurely closed my other question after going through the last experts link and got a couple VMs to work figured I'd better reach out to Veeam to finish with the ones that were giving problems and they successed in getting rid of me for at least the day.  Now back to Veeam.  I appreciate the clarification.  Being new to VM they had me questioning myself
bergquistcompanyAuthor Commented:
With this I was able to go back to Veeam and get escalated up and it was mounting fine after the snapshot.  Thank you for the specifics so I had leverage to go back on.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.