Recent content by pablot

Try rebooting to see if it fixes the problem, as my problem was almost the same but with the FSTYPE that appeared to be empty but it wasn't. From your command output you have a similar problem but with the PARTTYPE. Try rebooting and let us know, my guess is that "some info" is not updated as...

ok, I'll reply to myself, just rebooting and reexecuting "pve-efiboot-tool init /dev/sda2" solved my problem as it executed properly without complaining about the wrong filesystem.

I've tried the above but I still get the same error message: # pve-efiboot-tool format /dev/sda2 --force UUID="" SIZE="536870912" FSTYPE=""...

Can you update to the latest packages and reboot to see what happens?

But with that, in my case, the VM starts, but it gets stucked at boot!!!

Can you test what Alwin suggested? (update to the lastest packages and reboot to activate the new kernel)

It's updated to the lastes packages: root@deathstar2:~# apt update Hit:1 http://download.proxmox.com/debian/pve stretch InRelease Ign:2 http://ftp.debian.org/debian stretch InRelease Hit:3 http://ftp.debian.org/debian stretch-updates InRelease Hit:4 http://ftp.debian.org/debian stretch Release...

root@deathstar2:~# qm config 101 boot: cdn bootdisk: virtio0 cores: 1 ide2: none,media=cdrom memory: 2048 name: hassio net0: virtio=6A:84:CE:EA:2E:5E,bridge=vmbr0 numa: 0 ostype: l26 scsihw: virtio-scsi-pci smbios1: uuid=e4851651-6cd8-4667-913e-8f679a10a10c sockets: 1 virtio0...

root@deathstar2:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID...

Same problem here, cannot start VMs. (tried with Alwin suggestion, but it gets stucked at booting from hard disk...) The Proxmox server is an AMD-FX8350 with 24GB RAM. root@deathstar2:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little...