Search results

  1. D

    [Critical] VM Dead after creating snapshot. :'(

    Hi and thank for your reply Udo, Yes I have tried converting it to raw but it didn't helped. Though I haven't tried extracting the lvm out. I'm now gonna give it a try.
  2. D

    [Critical] VM Dead after creating snapshot. :'(

    Trying to re-create the image with qemu-img convert (Original image was 105 but I have made a copy and trying to run the same on a new vm ID108) converted the disk to raw then back to qcow2 root@instant:/var/lib/vz/images/108# qemu-img info vm-108-disk-2.raw image: vm-108-disk-2.raw file...
  3. D

    [Critical] VM Dead after creating snapshot. :'(

    after running qemu-check on the image I found some errors 160 errors were found on the image. Data may be corrupted, or further writes to the image may corrupt it. 409496/1245184 = 32.89% allocated, 0.18% fragmented, 0.00% compressed clusters Image end offset: 66800386048 Tried repairing it...
  4. D

    [Critical] VM Dead after creating snapshot. :'(

    I am not experimenting on the original file. I have made a copy and using the same to fix this issue.
  5. D

    [Critical] VM Dead after creating snapshot. :'(

    Hi toshko4 Thanks for your reply. My issue is a bit different from yours. The main issue I'm facing is that the original disk image I have, is corrupted and not booting up. Whenever I try to boot the VM with the original image, it just shows "Boot Failed, Not a bootable device" .
  6. D

    [Critical] VM Dead after creating snapshot. :'(

    many thanks for replying toshko4 :) [root@static /]# fdisk -l Disk /dev/sda: 107.4 GB, 107374182400 bytes 255 heads, 63 sectors/track, 13054 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes...
  7. D

    [Critical] VM Dead after creating snapshot. :'(

    thanks to testdiks, I have added the partitions back. What I did next is attached this disk image to another vm running on centos and luckily the system is able to find the LVms. But I can't mount them. So can anyone help me with this?
  8. D

    Hi Udo, SOrry for reaching out like this. I need a lil help with a situation I'm stuck. Please...

    Hi Udo, SOrry for reaching out like this. I need a lil help with a situation I'm stuck. Please see if you can help me out with this http://forum.proxmox.com/threads/20955-Critical-VM-Dead-after-creating-snapshot-(
  9. D

    [Critical] VM Dead after creating snapshot. :'(

    Ok I switched the kernel, now I can use qemu-nbd to mount the image. Trying my luck again. Lets see if it works.
  10. D

    [Critical] VM Dead after creating snapshot. :'(

    Hi there everyone, Now here is what happened. This node was running since 2013 perfectly. I have created 8 VMs back then and they were all up, they are still. When I consoled into the VM using VNC, the vm was stuck at boot with error "boot failed, This hard drive is not bootable" here...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!