[SOLVED] VM says disk is missing after Hard Shutdown

[joeycarmello]

hey all,
Recently had my first kernel issue and had to update my proxmox box. Upon starting it back up, I noticed a few VM's having issues with startup. Any help would be greatly appreciated.

Output from Console:

Running as unit 110.scope.
kvm: -drive file=/dev/zvol/tank/vm-110-disk-1,if=none,id=drive-ide0,cache=writeback,format=raw,aio=threads,detect-zeroes=on: Could not open '/dev/zvol/tank/vm-110-disk-1': No such file or directory
TASK ERROR: start failed: command '/usr/bin/systemd-run --scope --slice qemu --unit 110 -p 'KillMode=none' -p 'CPUShares=1000' /usr/bin/kvm -id 110 -chardev 'socket,id=qmp,path=/var/run/qemu-server/110.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -vnc unix:/var/run/qemu-server/110.vnc,x509,password -pidfile /var/run/qemu-server/110.pid -daemonize -smbios 'type=1,uuid=98c5f7f0-e45d-46f7-a1aa-04441f9bbbbf' -name dhcp01 -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga cirrus -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 2048 -k en-us -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:4c76e43cf7' -drive 'file=/dev/zvol/tank/vm-110-disk-1,if=none,id=drive-ide0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100' -drive 'file=/var/lib/vz/template/iso/CentOS-6.7-x86_64-minimal.iso,if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -netdev 'type=tap,id=net0,ifname=tap110i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=66:36:65:36:36:30,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'' failed: exit code 1

When i go to my ZVOL I see.

vm-110-disk-1-part1
&
vm-110-disk-1-part2

Any remedy to this situation or an explanation of whats going on?

Cheers,
Joey

 

[joeycarmello]

SOLVED: For some reason there was a missing symlink!

 

[Roberto Schmidt]

Hi Joey

How you fixed this problem? I'm have the same problem with my Proxmox.

Regards,

 

[iJoo]

how to fix it? i found same problem.. disk-1 not found,, but in folder have disk-1-part1 and part2

 

[nixell]

i have same problem, how to fix it?

 

[arebokert]

For anyone coming across this thread in the future,

Look in the end of the error message and find the location it is looking at. Create a symlink between the drive file and the drive label it needs to use.

For example, I have a disk called 101. I found it by searching for it with:

find / -name vm-101-disk

Replace 101 with whatever ID you have for the vm.

In my case it was in /dev/pve/vm-101-disk

Then symlink it to wherever your error message says, in my case /dev/sdf1

ln -s /dev/pve/vm-101-disk-1 /dev/sdf1

 

[Virtualizer]

It will been better, to check this resolution, before you patch manually!

Can been, that the host need much performance to check the filesystem after a hard-reboot and get possible timeout errors, as I see in log-file!
About this the links will not been set!

So wait, that the host with all virtual machines is stable and then you make a restart direct via the GUI! About this, the host shutdown all virtual machines again and close the filesystems correct and then the host is comming up with less work. Then in most time, the filesystems they had before timeout errors, comes up correct and set the links equal correct!

I hope thats helps better!