Windows VM no bootable device found

[assey60]

Hello,

the pc name of a windows server 2008 vm just got changed so it ask for a restart and now proxmox keep saying that there is no bootable device, tried repair the installation by using a windows cd iso but the disk doesn't show there either.

pveversion -v

proxmox-ve: 4.4-76 (running kernel: 4.4.10-1-pve)
pve-manager: 4.4-2 (running version: 4.4-2/80259e05)
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.4.35-1-pve: 4.4.35-76
pve-kernel-4.4.8-1-pve: 4.4.8-52
pve-kernel-4.4.13-2-pve: 4.4.13-58
pve-kernel-4.4.21-1-pve: 4.4.21-71
pve-kernel-4.4.15-1-pve: 4.4.15-60
pve-kernel-4.2.8-1-pve: 4.2.8-41
pve-kernel-4.4.16-1-pve: 4.4.16-64
pve-kernel-4.4.24-1-pve: 4.4.24-72
pve-kernel-4.4.19-1-pve: 4.4.19-66
pve-kernel-4.4.10-1-pve: 4.4.10-54
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-102
pve-firmware: 1.1-10
libpve-common-perl: 4.0-84
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-89
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve13~bpo80

I have no idea what to do maybe it's because of an proxmox update? Last time the vm got restarted was the 19th of november.

EDIT: Also it says sometimes in the task viewer: "lvmetad is running but disabled. Restart lvmetad before enabling it!"

 

[LnxBil]

Why should this be problem of Proxmox VE? Windows tends to destroy itself from time-to-time, so I'd suspect the problem is there. If you do not have the problem with other VMs, then it is most probably the VM itself. Try to restore a backup of the said windows in a new VM (with new ID) try to boot it. If it start up fine, your Windows corrupted something.

 

[assey60]

Why should this be problem of Proxmox VE? Windows tends to destroy itself from time-to-time, so I'd suspect the problem is there. If you do not have the problem with other VMs, then it is most probably the VM itself. Try to restore a backup of the said windows in a new VM (with new ID) try to boot it. If it start up fine, your Windows corrupted something.

Well I'm kinda confused because the disk shows up in the webinterface but not in /dev/pve/ but all other vm disks are there

 

[Ashley]

Well I'm kinda confused because the disk shows up in the webinterface but not in /dev/pve/ but all other vm disks are there

Sounds like something may have deleted the disk, however due to the VM running this would place a lock on the file, once the VM is rebooted between the time the lock is removed on the file and the VM trys to restart the rm command would have fully removed the disk file.

 

[LnxBil]

If this is LVM-based, the disk is only shown in the VM is running. All logical volumes are normally not opened. Please check with the output of lvm. There should not be a 'o' flag set

root@proxmox1 ~ > lvs
  LV              VG        Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  data            pve       twi-a-tz--  78.45g             0.00   0.43
  root            pve       -wi-ao----  34.00g
  swap            pve       -wi-ao----   8.00g
 ...
  vm-10000-disk-1 san-dx100 -wi-a-----  50.00g
...

root@proxmox1 ~ > ls -l /dev/pve/san-dx100/vm-10000*
ls: cannot access /dev/pve/san-dx100/vm-10000*: No such file or directory

 

[assey60]

If this is LVM-based, the disk is only shown in the VM is running. All logical volumes are normally not opened. Please check with the output of lvm. There should not be a 'o' flag set

root@proxmox1 ~ > lvs
  LV              VG        Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  data            pve       twi-a-tz--  78.45g             0.00   0.43
  root            pve       -wi-ao----  34.00g
  swap            pve       -wi-ao----   8.00g
...
  vm-10000-disk-1 san-dx100 -wi-a-----  50.00g
...

root@proxmox1 ~ > ls -l /dev/pve/san-dx100/vm-10000*
ls: cannot access /dev/pve/san-dx100/vm-10000*: No such file or directory

I checked lvs before and there are only the other vm disks.
tried to move the disk via the webinterface but the disk was still corrupt and now I completely messed it up I guess.
any log I could check to find out what happen?

 

[LnxBil]

The data lives in your VM, so there is no log in Proxmox VE for a simple block storage for a VM. If it is an underlying problem (e.g. disk error), it will be in the default location

/var/log/syslog(|\.)(|\.gz)