grub rescue> after VM reboot

[vikozo]

Hello
my Proxmox VM has done a reboot and stop in there

grub rescue>


why this happen - what should i do?

have a nice day
vinc
===========================

proxmox-ve: 6.0-2 (running kernel: 5.0.21-5-pve)
pve-manager: 6.0-12 (running version: 6.0-12/0a603350)
pve-kernel-helper: 6.0-12
pve-kernel-5.0: 6.0-11
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.21-4-pve: 5.0.21-9
pve-kernel-4.4.98-5-pve: 4.4.98-105
ceph-fuse: 12.2.12-pve1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-3
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-7
libpve-guest-common-perl: 3.0-2
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.0-9
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
openvswitch-switch: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12+deb10u1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-8
pve-cluster: 6.0-7
pve-container: 3.0-10
pve-docs: 6.0-8
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-4
pve-ha-manager: 3.0-3
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.1-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-13
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1

 

[vikozo]

grub rescue> set
cmdpath=(hd0)
prefix=(hd0,msdos1)/boot/grub
root=hd0,msdos1
grub rescue>

 

[vikozo]

may i provide some information for help and a solution?

 

[t.lamprecht]

Does Proxmox VE itself has any boot issues or the VM?

As with the VM you'd need to ask in the Distirubtions support channels, at the first look this does not seems to be related to Proxmox VE directly..

your grub rescue command seem to not be finished..

set prefix=(hd0,msdos1)/boot/grub
set root=(hd0,msdos)

# then:
insmod linux
insmod normal
normal

Else you could use a live CD of a Distro, or GParted, mount the root partition and bindmount proc, sys, .. chroot in there and run update-grub

 

[vikozo]

@t.lamprecht thanks for your feedback,
did not work - and i did restore a backup.
what are the reason for a high Disk latency? the VM is local and the Disk are local too