Recover deleted qcow disk
- Thread starter pluteus
- Start date
Hi, yes would have been nice if one had made one just after creating this new vm.
No VM Backup done so far. Next time it's the first thing we do....
Suffered the same disaster today...I originally wanted to delete the second hard disk of 105, but accidentally deleted the second of 106, which is still running...
I dont' know why Proxmox allow to delete hard disk while OS is still running, not the same behavior like in physical machine.
I found the Protection defaults to No in Options. Shouldn't it be Yes by default?
And I suggest to add an extra confirmation step like deleting vm, which need to input the vm id.
I dont' know why Proxmox allow to delete hard disk while OS is still running, not the same behavior like in physical machine.
I found the Protection defaults to No in Options. Shouldn't it be Yes by default?
And I suggest to add an extra confirmation step like deleting vm, which need to input the vm id.
What ancient version are you running?
I cannot delete a running machine and I have to put in the ID after the remove dialog (obviously after stopping the VM).
I was deleting a hard drive of a running machine.
For example, win7 on scsi0(as C: drive), D drive on scsi1, D drive can be detached and removed while win7 is still running if the Protection option is "No", which is set default by PVE.
KEEP THE VM RUNNING AND search the forum, I remember that as long as the VM is still running, the OS does not *really* (yet) delete the file qcow2! Keep the VM alive and find the post about it, there is some sort of trick AFAIR to "resurrect" it.
FOUND the thread: https://forum.proxmox.com/threads/deleted-image-of-running-vm.9258/
Last edited:
Actually, it is deleted. That's what delete means: removing the file entry in your filessystem. If you have the file open (in a process), you can access the file as the file entry on the filesystem is stored in a symbolic link and copy your data unless it is overwritten in the meantime.
As already stated: You cannot remove a disk from a running VM, not via the GUI.
Well, you can. I have just checked that using one of my CentOS guests. You can detach a device from a running guest, even while the volume is mounted. Its probably the equivalent of pulling a drive from it's drivebay on a hotpluggable system… I haven't checked, if any running traffic to that device would circumvent this, but even if that'd be the case, you should always keep in mind, that you can detach/remove a disk device from a running guest.
Yes, I've used to test ZFS with "hot unplug" event. In "Options" there is a HotPlug setting, maybe disk hotplug should be set to FALSE by default instead of true! If someone is willing to file a feature request... is welcomed
Well, that's the nature of defaults, isn't it - they never suit everyone. Actually, I am pretty content with the current set. To me, it's basically the same as walking up to my servers in the rack and checking twice, before pulling a drive from any server. The same applies to the "virtual" rack, I suppose.
Be honest... how often plugging a hard disk from your VM is a good idea against a bad nightmare? Default behavior (and so related default option) is that no one removes disks on running PC/Servers/VM, doing so should be just a nice feature that you can enable if really needed.
Okay, I tried with the boot device and that is not possible. My fault. Another disk can be hot unplugged.