Manual Repair needed! VM wont start.

[phl3geton]

Hey Folks,

I got some serious problem after configurating my Proxmox Server. After several reboots i got following error message (broken down to the important stuff):

root@alec:/dev/pve# qm start 100
kvm: -drive file=/dev/pve/vm-100-disk-1,if=none,id=drive-sata0,format=raw,cache=none,aio=native,detect-zeroes=on: Could not open '/dev/pve/vm-100-disk-1': No such file or directory

After that message I searched the forum and Google. I did find stuff so i tried to fix things myself but even then I did not accomplish anything but frustration.

So what i did tried was repairing the pve/data, pve/vm-100... and those others.
But everytime I try to --repair anything I'm getting Manual repair required ! Well I would like to repair manualy but I dont know how! Im thankful for any help I can get.



Here's some of the output i collected for you, maybe you guy's got an idea:

root@alec:/dev/pve# lvscan
ACTIVE '/dev/pve/swap' [8.00 GiB] inherit
ACTIVE '/dev/pve/root' [96.00 GiB] inherit
inactive '/dev/pve/data' [794.52 GiB] inherit
inactive '/dev/pve/vm-101-disk-1' [32.00 GiB] inherit
inactive '/dev/pve/vm-100-state-Alec' [32.49 GiB] inherit
inactive '/dev/pve/snap_vm-100-disk-1_Alec' [400.00 GiB] inherit



root@alec:/dev/pve# lvchange -ay pve/data
Check of pool pve/data failed (status:1). Manual repair required!


root@alec:/dev/pve# lvs -a
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve twi---tz-- 794.52g
[data_tdata] pve Twi------- 794.52g
[data_tmeta] pve ewi------- 8.11g
[lvol0_pmspare] pve ewi------- 8.11g
root pve -wi-ao---- 96.00g
snap_vm-100-disk-1_Alec pve Vri---tz-k 400.00g data
swap pve -wi-ao---- 8.00g
vm-100-state-Alec pve Vwi---tz-- 32.49g data
vm-101-disk-1 pve Vwi---tz-- 32.00g data

root@alec:/dev/pve#: lvconvert --repair pve/data
Using default stripszie 64.00 KiB..
bad checksum in metadata index block
Repair of thin metadata volume of thin pool pve/data failed (status:1) Manual repair required!

Could there be a corrupted file system on one of my harddrives because of the bad checksum ? I guess im running a e2fsck.

 

[phl3geton]

Case can be closed. Got serious issues with corrupt filesystem and it couldn't be repaired. I started from scratch. Now it works. Remember to first configure all of your proxmox and go then to the VM's ffs.

/close