Boot failed: not a bootable disk after reboot

[spoonman]

Hello, I've migrate to 3.1 version, after rebooting the server (using the web interface) there is a virtual machine that is not starting anymore.

The error is:
boot failed: not a bootable disk
I tried to analyze the disk with the testdisk utility this is the partition table found:

Disk 109/vm-109-disk-1.raw - 31 GB / 29 GiB - CHS 3849 255 63

Partition Start End Size in sectors

1 * Linux 63 0 1 3811 254 63 60227685

If I take a backup (that is ok) I have this situation:

Disk 107/vm-107-disk-1.raw - 32 GB / 30 GiB - CHS 3917 255 63
Current partition structure:
Partition Start End Size in sectors

1 * Linux 0 1 1 3748 254 63 60227622
2 E extended 3749 0 1 3915 254 63 2682855
5 L Linux Swap 3749 1 1 3915 254 63 2682792

I can't see any file from the wrong raw file (vm-109-disk-1.raw).

How could be happened ? Any ideas ?
There is any tool for analyze the raw file and search some files ?

Can I copy the mbr structure from the backup raw file to the corrupted one ?

Best regards

 

[spoonman]

I've installed proxmox 2.3 version in another machine, and i moved the raw file (vm-109-disk-1.raw).
With the old Proxmox version the VM start regulary.
If I try to see the partition with testdisk I also can't see any partition inside the raw file, but the vm start regolary... now i'm going to copy the files