Machine inaccessible after proxmox version upgrade

[davidoeol0]

Hello everyone,

After migrating a node from version 7.4-3 to version 8-2.4, one of the machines I had in Ceph has become inoperative because I am unable to access the hard drive. I would like to inform you that this is a machine that had been migrated from VMware ESXi 8.0 to my previous version of Proxmox.

This is the error I get when I turn on the machine currently:

WARN: no efidisk configured! Using temporary efivars disk.
TASK WARNINGS: 1

This was the configuration I had in my previous version of Proxmox, with which the machine was working.





I tested importing it again in my new version of Proxmox with the following configuration, and I can get the machine to start.





Here is the output of the pveversion -v command to shed more light on this issue.

root@proxmox01:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-1-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
pve-kernel-5.15: 7.4-15
proxmox-kernel-6.8: 6.8.12-1
proxmox-kernel-6.8.12-1-pve-signed: 6.8.12-1
pve-kernel-5.15.158-2-pve: 5.15.158-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph: 17.2.7-pve3
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.2
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.2-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1

Thank you all in advance

 

[sw-omit]

In the hardware tab, click add, click EFI, change the data-store location if neceserry, save, then try to start.

Since you're using UEFI, it needs an EFI-disk to save some boot-configuration on.

If it doesn't work like that right away, try booting from a Windows-iso and then repairing the installation.

(Still strange that disk is suddenly gone though after an upgrade)

 

[davidoeol0]

Hello,

Thank you very much for the help sw-omit, I'll try the steps you told me and I'll let you know.

 

[davidoeol0]

Hello,

I tried both options you indicated, but neither of them worked for me, I attach a screenshot so you can have a look at it.

 

[sw-omit]

Could you try detaching the main harddisk (so leave the EFI-disk as-is) and then re-attaching it as a sata-drive instead of a scsi drive?
See if it then boots normally, if not, try the repair again (the repair might not be able to see the drive on scsi by default, and we can get it converted back to scsi again later)

You also seem to have a disk on CEPH, was that the 100GB data-disk or perhaps a "left over" 1MB efi-disk? (Look in the storage tab and find the disk by that name to easily see the size of it.)