fsck destroy a VM

[michi616]

Hello,

i have the last beta Proxmox VE 1.5 with Kernel 2.6.32 and only 5 KVM VMs.
I has with that not problems, but at s start the auto fsck checks my disks that all in a LVM and destroy one VM.

Why?
Is this normal with fsck and LVM? or must i disable fsck on startup?

 

[Nemesiz]

You lost kvm disk or config files?

 

[michi616]

no, the Server works fine.
I has in a VM 2 Disks and the VM works fine. But on a start of the Proxmox 1.5 Server (not the VM) the auto fsck has found in the LVM (i have 4 Harddrive in a LVM) (of my Proxmox Server) on the second disk file of the VM a lot of failure and fix this.
But on the boot of the VM the files in the second Disk were lost. I must every run by start of the VM in the VM the fsck and fix the problems to see the files of the seccond disk.