Host does not reboot anymore after upgrade to proxmox v6

Nov 16, 2018
30
4
13
46
Belgium
Hello!

I followed the following procedure to upgrade my proxmox v5 to v6 : https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0#Update_the_configured_APT_repositories

Everything went well and at the end of the
apt dist-upgrade command, it requests to reboot the server, what I did. But the server does not boot anymore :(

Proxmox is running on a OVH dedicated server. I started the IPMI interface and can see that the boot is blocking at "Booting on local disk", nothing else.

if it can help:

Code:
root@rescue:/var/log# pveversion -v
proxmox-ve: 6.0-2 (running kernel: 4.19.53-mod-std-ipv6-64-rescue)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)
pve-kernel-5.0: 6.0-5
pve-kernel-helper: 6.0-5
pve-kernel-4.15: 5.4-6
pve-kernel-5.0.15-1-pve: 5.0.15-1
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-17-pve: 4.15.18-43
pve-kernel-4.15.18-7-pve: 4.15.18-27
ceph-fuse: 12.2.11+dfsg1-2.1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.10-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-2
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-5
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-61
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-5
pve-cluster: 6.0-4
pve-container: 3.0-4
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-5
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-3
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-5
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve1

looking in log files in rescue mode, I can't find anything helping to understand what's happening. Any help /suggestion would be more than welcome.

Thx!
 
Probably the bootloader is damaged? You could try rewriting the bootloader from within the rescue system. Also you might boot from internal disk if you are able to specify kernel and initrd locations in bootloader of rescue system.
 
Hello!

I tried the following:

Code:
# Mount the filesystem under rescue
zpool import -R /mnt rpool
mount -t proc /proc /mnt/proc
mount --rbind /dev /mnt/dev
mount --rbind /sys /mnt/sys

# Enter chroot
chroot /mnt /bin/bash
source /etc/profile

# Reinstall package
dpkg --configure -a
apt-get update && apt-get dist-upgrade -y
apt-get install --reinstall grub-pc
apt-get install --reinstall zfs-initramfs
apt-get install --reinstall pve-kernel-5.0.15-1-pve linux-image-amd64

# Reinstall grub
grub-install /dev/sda
grub-install /dev/sdb
update-grub
update-initramfs -u -k all

# Exit chroot
exit

reboot

without success. Still blocked at "Booting from local disk" :(

Lydie
 
are you using grub or systemd-boot?

if you set up your system to use ZFS with our installer, then the default bootloader is systemd-boot (using EFI)

there's a tool pve-efiboot-tool. you can try running pve-efiboot-tool refresh to reconfigure the kernels and the boot entries. (pve-efiboot-tool kernel list to see a list of installed kernels)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!