WARN: no efidisk configured! Using temporary efivars disk.

N

nycrush

New Member
Dec 18, 2022
2
0
1
I switched my NVME drive from one pci slot to another. now my ubuntu VM is giving me an error. WARN: no efidisk configured! Using temporary efivars disk.
please help.
thank you
below is my config file

GNU nano 5.4 /etc/pve/qemu-server/108.conf
balloon: 2016
bios: ovmf
boot: order=scsi0;net0
cores: 5
efidisk0: NVMEstorage:108/vm-108-disk-2.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
machine: q35
memory: 33184
meta: creation-qemu=6.1.0,ctime=1658461400
name: Ubuntu
net0: virtio=AE:1E:A0:3C:BF:6C,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=2808c881-dc12-4486-906b-56fd4071c5f5
sockets: 1
unused0: NVMEstorage:108/vm-108-disk-1.qcow2
vmgenid: b225a536-5846-4ed1-9005-15ad3dd8f0a0
 
Can you please post the output of cat /etc/pve/storage.cfg, cat /etc/fstab and mount?
My guess is that the disk does not get mounted correctly and thus the efidisk image cannot be found.

Are there maybe any other warnings/errors in the journal (journalctl -b -e)?
 
Hi together,
I'm going to roll up this topic once again. However, it is a slightly different case for me.
I have created a VM without EFI DISK. Now, every time I start this VM, I get the error message already mentioned.

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

Is it somehow possible to set the EFI DISK afterwards and what exactly do I have to do so that the VM boots properly again.

I just tried once to add an EFI DISK, however, the VM then no longer boots and I then unfortunately do not know what exactly I have to do.

Can anyone help me?

Thanks in advance.

Greetings

Translated with DeepL
 
Hi,
Nireins said:
Hi together,
I'm going to roll up this topic once again. However, it is a slightly different case for me.
I have created a VM without EFI DISK. Now, every time I start this VM, I get the error message already mentioned.

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

Is it somehow possible to set the EFI DISK afterwards and what exactly do I have to do so that the VM boots properly again.

I just tried once to add an EFI DISK, however, the VM then no longer boots and I then unfortunately do not know what exactly I have to do.

Can anyone help me?

Thanks in advance.

Greetings

Translated with DeepL
Click to expand...
after adding the EFI disk, I guess you need to add the correct boot option(s) to it, see: https://pve.proxmox.com/wiki/OVMF/UEFI_Boot_Entries
 
  • Like
Reactions: leesteken
Nireins said:
Hi together,
I'm going to roll up this topic once again. However, it is a slightly different case for me.
I have created a VM without EFI DISK. Now, every time I start this VM, I get the error message already mentioned.

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

Is it somehow possible to set the EFI DISK afterwards and what exactly do I have to do so that the VM boots properly again.

I just tried once to add an EFI DISK, however, the VM then no longer boots and I then unfortunately do not know what exactly I have to do.

Can anyone help me?

Thanks in advance.

Greetings

Translated with DeepL
Click to expand...
I have the same issue, resolved with adding a EFI disk afterwards and set up the correct boot order in the Options tab.
 
Hi and sorry for pushing up this thread again.
After a restart of my proxmox 7.3-3 due to a power loss, my OMV6 didn't start again.
My 'DATA' storage is not active anymore.
The logs shows one warning which - I guess - is the root cause "WARN: no efidisk configured! Using temporary efivars disk.".
And then an error appears: "zfs error: cannot open 'DATA': no such pool".

/etc/pve/storage.cfg:
dir: local
path /var/lib/vz
content iso,backup,vztmpl

lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

zfspool: DATA
pool DATA
content rootdir,images
mountpoint /DATA
nodes pve

/etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
UUID=3786-F146 /boot/efi vfat defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=3857208k,nr_inodes=964302,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=778180k,mode=755,inode64)
/dev/mapper/pve-root on / type ext4 (rw,relatime,errors=remount-ro)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=18077)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=778176k,nr_inodes=194544,mode=700,inode64)

Unfortunately, I'm a beginner when it comes to proxmox and linux.
And of course, as always, there is important data on DATA.
I would really appreciate any help...

Best regards
Andreas
 
Hi,
aj68 said:
The logs shows one warning which - I guess - is the root cause "WARN: no efidisk configured! Using temporary efivars disk.".
Click to expand...
that error is not the real issue here, but just means you cannot make changes to your VM's UEFI settings persistent. Adding an EFI disk to the VM will fix that.

aj68 said:
And then an error appears: "zfs error: cannot open 'DATA': no such pool".
Click to expand...
Please check/share your boot log, journalctl -b > /tmp/boot.log. What is the output of the following
Code: 
zpool import
zpool status -v
lsblk -o NAME,MAJ:MIN,SIZE,TYPE,FSTYPE
?
 
Hi Fiona,
thx for your help!

/tmp/boot.log =>


zpool import + zpool status -v =>
no pools available to import

lsblk -o NAME,MAJ:MIN,SIZE,TYPE,FSTYPE

Code: 
NAME                         MAJ:MIN   SIZE TYPE FSTYPE
sda                            8:0   931.5G disk
├─sda1                         8:1    1007K part
├─sda2                         8:2     512M part vfat
└─sda3                         8:3     931G part LVM2_member
  ├─pve-swap                 253:0       7G lvm  swap
  ├─pve-root                 253:1      96G lvm  ext4
  ├─pve-data_tmeta           253:2     8.1G lvm 
  │ └─pve-data-tpool         253:4   795.8G lvm 
  │   ├─pve-data             253:5   795.8G lvm 
  │   ├─pve-vm--100--disk--0 253:6       8G lvm  ext4
  │   ├─pve-vm--102--disk--0 253:7      32G lvm 
  │   └─pve-vm--103--disk--0 253:8      12G lvm 
  └─pve-data_tdata           253:3   795.8G lvm 
    └─pve-data-tpool         253:4   795.8G lvm 
      ├─pve-data             253:5   795.8G lvm 
      ├─pve-vm--100--disk--0 253:6       8G lvm  ext4
      ├─pve-vm--102--disk--0 253:7      32G lvm 
      └─pve-vm--103--disk--0 253:8      12G lvm

Best regards
Andreas
 

Attachments

So there is no disk with ZFS reported by lsblk and your boot log shows a lot of device errors for ata2 and sdb:
Code: 
Dec 14 18:28:22 pve kernel: sd 1:0:0:0: [sdb] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Dec 14 18:28:22 pve kernel: sd 1:0:0:0: [sdb] tag#16 Sense Key : Illegal Request [current]
Dec 14 18:28:22 pve kernel: sd 1:0:0:0: [sdb] tag#16 Add. Sense: Unaligned write command
Dec 14 18:28:22 pve kernel: sd 1:0:0:0: [sdb] tag#16 CDB: Write(16) 8a 00 00 00 00 00 00 00 0a 10 00 00 00 10 00 00
Dec 14 18:28:22 pve kernel: blk_update_request: I/O error, dev sdb, sector 2576 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Dec 14 18:28:22 pve kernel: zio pool=DATA vdev=/dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6BCNJ0R707073Z-part1 error=5 type=2 offset=270336 size=8192 flags=b08c1
Dec 14 18:28:22 pve kernel: ata2: EH complete
Dec 14 18:28:22 pve kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 14 18:28:22 pve kernel: ata2.00: irq_stat 0x40000001
Dec 14 18:28:22 pve kernel: ata2.00: failed command: WRITE DMA EXT
Dec 14 18:28:22 pve kernel: ata2.00: cmd 35/00:10:10:74:c0/00:00:d1:01:00/e0 tag 0 dma 8192 out
                                     res 51/04:10:10:74:c0/00:00:d1:01:00/e0 Emask 0x1 (device error)
Dec 14 18:28:22 pve kernel: ata2.00: status: { DRDY ERR }
Dec 14 18:28:22 pve kernel: ata2.00: error: { ABRT }
Dec 14 18:28:22 pve kernel: ata2.00: supports DRM functions and may not be fully accessible
Dec 14 18:28:22 pve kernel: ata2.00: failed to enable AA (error_mask=0x1)
Dec 14 18:28:22 pve kernel: ata2.00: disabling queued TRIM support
Dec 14 18:28:22 pve kernel: ata2.00: supports DRM functions and may not be fully accessible
Dec 14 18:28:22 pve kernel: ata2.00: failed to enable AA (error_mask=0x1)
Dec 14 18:28:22 pve kernel: ata2.00: disabling queued TRIM support
Dec 14 18:28:23 pve kernel: ata2.00: configured for UDMA/133 (device error ignored)
Dec 14 18:28:23 pve kernel: ata2: EH complete
Dec 14 18:28:23 pve kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Dec 14 18:28:23 pve kernel: ata2.00: irq_stat 0x40000001
Dec 14 18:28:23 pve kernel: ata2.00: failed command: WRITE DMA EXT
Dec 14 18:28:23 pve kernel: ata2.00: cmd 35/00:10:10:76:c0/00:00:d1:01:00/e0 tag 2 dma 8192 out
                                     res 51/04:10:10:76:c0/00:00:d1:01:00/e0 Emask 0x1 (device error)
and
Code: 
Dec 14 18:28:36 pve kernel: sd 1:0:0:0: [sdb] tag#30 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=12s
Dec 14 18:28:36 pve kernel: sd 1:0:0:0: [sdb] tag#30 CDB: Write(16) 8a 00 00 00 00 00 00 00 0a 10 00 00 00 10 00 00
Dec 14 18:28:36 pve kernel: blk_update_request: I/O error, dev sdb, sector 2576 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Dec 14 18:28:36 pve kernel: zio pool=DATA vdev=/dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6BCNJ0R707073Z-part1 error=5 type=2 offset=270336 size=8192 flags=b08c1
Dec 14 18:28:36 pve kernel: sd 1:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=12s
Dec 14 18:28:36 pve kernel: sd 1:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 00 00 00 00 01 d1 c0 74 10 00 00 00 10 00 00
Dec 14 18:28:36 pve kernel: blk_update_request: I/O error, dev sdb, sector 7814018064 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Dec 14 18:28:36 pve kernel: zio pool=DATA vdev=/dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6BCNJ0R707073Z-part1 error=5 type=2 offset=4000776200192 size=8192 flags=b08c1
Dec 14 18:28:36 pve kernel: sd 1:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=12s
Dec 14 18:28:36 pve kernel: sd 1:0:0:0: [sdb] tag#1 CDB: Write(16) 8a 00 00 00 00 01 d1 c0 76 10 00 00 00 10 00 00
Dec 14 18:28:36 pve kernel: blk_update_request: I/O error, dev sdb, sector 7814018576 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Dec 14 18:28:36 pve kernel: zio pool=DATA vdev=/dev/disk/by-id/ata-Samsung_SSD_870_EVO_4TB_S6BCNJ0R707073Z-part1 error=5 type=2 offset=4000776462336 size=8192 flags=b08c1
Dec 14 18:28:36 pve kernel: sdb: detected capacity change from 7814037168 to 0
Dec 14 18:28:36 pve zpool[546]: no pools available to import

I'd check the cable, etc. but it sounds like the power loss left its marks.
 
Hi Fiona,
omg, I just forgot, that the DATA pool resides on a second sdd with 4TB.
Unfortunately I guess I run into the known firmware bug of samsung's 870 evo SSD, which makes sectors unreadable.
I've tried to update the firmware, but failed here on different devices: the ssd is just (half?) dead.
It can still be recognized, but not read or updated. I also tried two tools, which are able to repair zfs drives, but stopped both after 1000nds of read errors... I will open a ticket by samsung, the drive is one year old.
Thx a lot for your help!
Andreas
 
Hello.

Is it possible to disable that warning?

I've created a VM to emulate ARM64 hardware, which has no EFI disk (I don't require it and don't want it), and the warning gets pretty annoying over time.

I thought, maybe there's a way to get that warning out of the way... after all it's just a warning, not an error.

Regards!
 
Hi,
linkstat said:
Is it possible to disable that warning?
Click to expand...
Not without patching the code.
linkstat said:
I've created a VM to emulate ARM64 hardware, which has no EFI disk (I don't require it and don't want it), and the warning gets pretty annoying over time.
Click to expand...
The VM is using the default read-only EFI disk for ARM64 if you don't create one. It is required to boot for OVMF. But the VM won't be able to persist any EFI-related settings like that. What is the issue with creating one for the VM?
 
Hello Fiona,

I would like to get rid of this warning also.

My storage environment - commercial iSCSI storage connected over multipath and shared LVM
  • works stable and quite fast
  • the big problem is the missing snapshot functionality for VMs
I'm migrating my Linux VMs to root-on-ZFS with ZFS Bootmenu to get back the missing snapshot functionality
But now I've to create an EFI disk to get rid of the warning. As I'm also booting from a mirrored ZFS root - I would have to mirror this EFI disk - which is not possible in my environment.
Booting with root-on-ZFS and ZFS Bootmenu works surprisingly well - but now I get this warning on every VM boot.

Could proxmox please add an option to ignore the missing EFI disk?

Regards,
Gerald
 
Hi,
GeraldH said:
Hello Fiona,

I would like to get rid of this warning also.

My storage environment - commercial iSCSI storage connected over multipath and shared LVM
  • works stable and quite fast
  • the big problem is the missing snapshot functionality for VMs
I'm migrating my Linux VMs to root-on-ZFS with ZFS Bootmenu to get back the missing snapshot functionality
But now I've to create an EFI disk to get rid of the warning. As I'm also booting from a mirrored ZFS root - I would have to mirror this EFI disk - which is not possible in my environment.
Booting with root-on-ZFS and ZFS Bootmenu works surprisingly well - but now I get this warning on every VM boot.
Click to expand...
What exactly is the issue with creating an EFI disk? Why would you need to mirror it?

GeraldH said:
Could proxmox please add an option to ignore the missing EFI disk?
Click to expand...
It's just a warning, so you can ignore it if you know you don't want a disk for persisting the EFI settings.
 
Hello Fiona,

What exactly is the issue with creating an EFI disk? Why would you need to mirror it?
Click to expand...

  • my two VM disks are remote iSCSI disks (over shared LVM) - no local disks are attached
  • to survive a failure/reboot of an iSCSI storage the two VM disks are attached to different iSCSI storages and are mirrored with ZFS inside the VM
  • if I create an EFI disk on one iSCSI storage only - it would not be available (while booting) if this iSCSI storage with the EFI disk is down
  • so this EFI disk would have to be mirrored somehow on both iSCSI storages - way too much effort
It's just a warning, so you can ignore it if you know you don't want a disk for persisting the EFI settings.
Click to expand...
but I've many VMs with mirrored ZFS inside - so I get many warnings :)

Regards,
Gerald
 
GeraldH said:
  • so this EFI disk would have to be mirrored somehow on both iSCSI storages - way too much effort
Click to expand...
Without an EFI disk, the default EFI variables/OVMF configuration will be used. That means you currently don't rely on any modification to the EFI disks, i.e. you could just create an EFI disks on each iSCSI storage and just not mirror it.

Adding an option, just to remove that single warning for your really specialized use case is honestly not worth it. Imagine if we needed to do that for every warning for every special use case out there.
 
You must log in or register to reply here.
Top Bottom