superm1
commented
2 years ago Is your ESP full?
Open rogueai opened 2 years ago
superm1
commented
2 years ago Is your ESP full?
rogueai
commented
2 years ago There is plenty of space as far as I can tell:
/dev/nvme0n1p1 1.1G 275M 782M 26% /efiI'm not sure if it's relevant, but there are actually a few files in the efi partition that look related to fwupd:
├── EFI
│ ├── arch
│ │ ├── fw
│ │ │ ├── fwupd-533b2fa2-90be-4e2b-942f-f9b6950e310f.cap
│ │ │ └── fwupd-9d97f767-ea06-474f-9141-7e2430d97fc1.cap
│ │ └── fwupdx64.efiYeah fwupd stages the capsules there, which is why I was suggesting if it's full that could be the problem. Maybe this is a problem with the NVRAM being full then.
We don't have that error string in the fwupd codebase, so it must be coming from the firmware.
I think there isn't much more we can do from fwupd side, let's see if Lenovo has any thoughts on it.
olegk25
commented
2 years ago I have the same issue while trying to apply official Lenovo upgrade (4.8 MB size) and my /efi is only 19% full. ThinkPad T560, ArchLinux 5.19.1-arch2-1 x64
/dev/sda1 256M 49M 208M 19% /efi
hughsie
commented
2 years ago @mrhpearson any ideas?
mrhpearson
commented
2 years ago No idea I'm afraid - I've flagged this to the FW team (ticket # LO-1964)
ChiWei-Chen
commented
2 years ago @rogueai , I'm working with @mrhpearson and got these questions from FW team, could you help t comment them? Thanks!
Could you help confirm where is this message show (OS,post..or..)? Please provide the detail information. BTW, could you let user try use “fwupdmgr update [BIOS Device ID]” to check if can update successfully? I want to confirm if can duplicate or not. Device ID can get from System Firmware by type “fwupdmgr get-devices” .
Ex:
ghost
commented
2 years ago This also happens on my system—ThinkPad T14 Gen 2 (AMD) running Fedora 36.
Kernel: Linux 5.18.17-200.fc36.x86_64
Output of df -h /dev/nvme0n1p1:
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p1 96M 72M 25M 75% /boot/efiThe error message occurs after the machine reboots and says fwupd-efi’s version, which is 1.3 I believe.
Trying to update by targeting specifically the System Firmware has the same issue.
ChiWei-Chen
commented
2 years ago Hello @Jaeson813 ,
Have you tried resizing the EFI partition?
asegarra
commented
2 years ago Fedora 36 on X1 Carbon Gen 9
I have the same issue, tried “fwupdmgr update [BIOS Device ID]” and got the same error. My efi partition is 629MB of which 603 are free. Resizing in not an option for me at the moment, what is the recommended size for fwupd?
ghost
commented
2 years ago @ChiWei-Chen, I’m unable to resize the partition currently. I booted into Windows, and one of the optional BIOS updates actually did successfully update it to 1.19.
olegk25
commented
2 years ago Hi, it's obviously a logical glitch in fwupdmgr while trying to assess available space. I used bootable image from the vendor and upgrade was successful.
ChiWei-Chen
commented
2 years ago @hughsie is there any idea or anything we can do for fwupdmgr?
@Jaeson813 , @olegk25 , thanks for the comment.
hughsie
commented
2 years ago @ChiWei-Chen I don't think it's fwupd at fault here, the userspace bit has already written the capsule to the ESP at the point the Could not apply capsules: volume full appears. The volume full is coming either from the UEFI runtime service, either RT->QueryCapsuleCapabilities or RT->UpdateCapsule -- perhaps it's telling us that NVRAM is full, rather than the ESP is full?
ChiWei-Chen
commented
2 years ago Richard, Thanks, I'll give you back once I heard any clues from FW experts.
rogueai
commented
2 years ago I've retested this with v1.8.5 and it seems to be working now. Unfortunately, in the meanwhile I've setup secure boot + custom signing keys so my environment is not as it was when I first tested it with v1.8.3
jwflory
commented
2 years ago This issue captures my problem, except with a few differences:
I experienced this on the first day of using the laptop, so I am hesitant to blame storage as an issue. This happened after I applied the first round of updates in GNOME Software, after I completed initial user setup.
susman
commented
2 years ago same issue here:
~ # fwupdmgr --version
runtime org.freedesktop.fwupd 1.8.7
runtime org.freedesktop.fwupd-efi 1.3
compile org.freedesktop.gusb 0.4.2
compile com.hughsie.libjcat 0.1.12
runtime org.kernel 5.15.75-gentoo
runtime com.hughsie.libjcat 0.1.12
compile org.freedesktop.fwupd 1.8.7
runtime org.freedesktop.gusb 0.4.2 ~ # dmidecode -s system-version
ThinkPad X1 Carbon Gen 9
~ # dmidecode -s system-product-name
20XWCTO1WWfwupd-efi 1.5 from latest main on https://github.com/fwupd/fwupd-efi doesn't solve it either. The result is the same:
Could not apply capsules: volume fullCan we please re-open this?
mrhpearson
commented
1 year ago Looks like we didn't leave a comment...but this has been reported to the FW team (a couple of weeks back) and we're discussing with them
alexted
commented
1 year ago Is there any news on this problem?
mrhpearson
commented
1 year ago Sorry - no, we've been nagging the FW team for some insight into what would cause that message. Just for my reference as it took me a while to find the notes - tracked by internal ticket LO-1964
autumn-traveller
commented
1 year ago Hi everyone- I am also having this exact problem. I have a lenovo thinkpad T490 with Fedora 36. My fwupd-efi version is also 1.3 , fwupd is 1.8.6
gstephan76
commented
1 year ago Hi Everyone. Lenovo ThinkPad P1 Gen 3, running Fedora 37, with the same issue. fwupdmgr --version: compile org.freedesktop.fwupd 1.8.8 compile com.hughsie.libjcat 0.1.12 runtime org.freedesktop.fwupd-efi 1.3 compile org.freedesktop.gusb 0.4.2 runtime com.hughsie.libjcat 0.1.12 runtime com.dell.libsmbios 2.4 runtime org.freedesktop.gusb 0.4.3 runtime org.freedesktop.fwupd 1.8.8 runtime org.kernel 6.0.16-300.fc37.x86_64
ChiWei-Chen
commented
1 year ago Hi @alexted , @noobsauce101 , @gstephan76 , our FW team wasn't able to reproduce this issue yet, but they suspect this is EFI space related, could you provide output of df -h for our investigation? Thank you.
alexted
commented
1 year ago Right now it looks like this (I've reinstalled the OS a couple of times since then):
Filesystem Size Used Avail Use% Mounted on
dev 7,7G 0 7,7G 0% /dev
run 7,7G 2,1M 7,7G 1% /run
/dev/nvme0n1p2 452G 39G 390G 10% /
tmpfs 7,7G 56M 7,6G 1% /dev/shm
tmpfs 7,7G 28K 7,7G 1% /tmp
/dev/nvme0n1p1 300M 312K 300M 1% /boot/efi
tmpfs 1,6G 64K 1,6G 1% /run/user/1000
@alexted , thanks for the feedback.
Could you also provide the output of fwupdmgr --version and fwupdmgr get-devices, we need to know the machine and current FW version.
Thanks!
alexted
commented
1 year ago compile org.freedesktop.fwupd 1.8.10
compile com.hughsie.libjcat 0.1.12
runtime org.freedesktop.fwupd-efi 1.4
compile org.freedesktop.gusb 0.4.3
runtime com.hughsie.libjcat 0.1.12
runtime com.dell.libsmbios 2.4
runtime org.freedesktop.gusb 0.4.5
runtime org.freedesktop.fwupd 1.8.10
runtime org.kernel 6.1.11-1-MANJAROand
LENOVO 20X300GACY
│
├─USB3.1 Hub:
│ │ Device ID: 7c5b6dadf8126e3820c86cb56d9e1777084a98a8
│ │ Summary: USB 3.x hub
│ │ Current version: 13.24
│ │ Vendor: VIA Labs, Inc. (USB:0x17EF)
│ │ Install Duration: 15 seconds
│ │ GUIDs: 227d0f95-a764-598e-85de-3d2bd0a7372f
│ │ c6381f16-fe6d-5c45-a4ad-b619af4f0f0e ← USB\VID_17EF&PID_A391
│ │ e0c50668-5c2e-54df-8e17-c7c2472f3eaa ← USB\VID_17EF&PID_A391&REV_0D24
│ │ fc6cfb35-d4e9-5467-a014-8863de104969 ← USB\VID_17EF&PID_A391&HUB_000A
│ │ ef65710a-3fa0-5330-9a61-5ced5e976be1 ← USB\VID_17EF&PID_A391&SPI_C220
│ │ 7ae3100f-9b01-571c-9fc2-20cd4544123a ← USB\VID_17EF&PID_A391&SPI_C220&REV_0D24
│ │ Device Flags: • Updatable
│ │ • Cryptographic hash verification is available
│ │ • Device stages updates
│ │ • Device can recover flash failures
│ │ • Unsigned Payload
│ │
│ ├─USB2.0 Hub:
│ │ │ Device ID: 65a54fb6ce182f0e75edf0e43047d547a0d61f0e
│ │ │ Summary: USB 3.x hub
│ │ │ Current version: 13.24
│ │ │ Vendor: VIA Labs, Inc. (USB:0x17EF)
│ │ │ Install Duration: 15 seconds
│ │ │ GUIDs: 227d0f95-a764-598e-85de-3d2bd0a7372f ← USB\VID_17EF&PID_A392
│ │ │ 010262bc-c6fa-5843-bffd-42be9aa16e6a ← USB\VID_17EF&PID_A392&REV_0D24
│ │ │ 4ec36768-1858-5e9b-9d35-40e6143c3cd4 ← USB\VID_17EF&PID_A392&HUB_0A
│ │ │ 181168b9-f5c8-51c4-a8f2-958daab8af2d ← USB\VID_17EF&PID_A392&SPI_C220
│ │ │ b8ce86b1-5d74-5876-8d02-a9fd61b0a9ee ← USB\VID_17EF&PID_A392&SPI_C220&REV_0D24
│ │ │ Device Flags: • Updatable
│ │ │ • Cryptographic hash verification is available
│ │ │ • Device stages updates
│ │ │ • Device can recover flash failures
│ │ │ • Unsigned Payload
│ │ │
│ │ └─USB2.0 Hub:
│ │ │ Device ID: 7a2034b0a5bfbc758ec5bfdce77b0484bdc0b46f
│ │ │ Summary: USB 3.x hub
│ │ │ Current version:13.23
│ │ │ Vendor: VIA Labs, Inc. (USB:0x17EF)
│ │ │ Install Duration:15 seconds
│ │ │ GUIDs: 7a216856-8a97-550c-882e-8233751c7cf2 ← USB\VID_17EF&PID_A394
│ │ │ 5a743458-4929-5738-a812-84cad6574a37 ← USB\VID_17EF&PID_A394&REV_0D23
│ │ │ 36a4a5cc-b78b-5419-a2ba-3a692148e9f5 ← USB\VID_17EF&PID_A394&HUB_08
│ │ │ 9495f83b-bee0-5484-beeb-374325c67cb6 ← USB\VID_17EF&PID_A394&SPI_C840
│ │ │ 575dc5a0-ff9d-5df7-8777-aa9531061b0c ← USB\VID_17EF&PID_A394&SPI_C840&REV_0D23
│ │ │ Device Flags: • Updatable
│ │ │ • Cryptographic hash verification is available
│ │ │ • Device stages updates
│ │ │ • Device can recover flash failures
│ │ │ • Unsigned Payload
│ │ │
│ │ ├─ThinkPad USB-C Dock Gen2 PD Controller:
│ │ │ Device ID: 91ae0d1fd49196e537a79c5e744e9c341c446801
│ │ │ Summary: CCGx Power Delivery Device
│ │ │ Current version:0.0.37
│ │ │ Vendor: Cypress Semiconductor (USB:0x04B4)
│ │ │ Install Duration:2 minutes
│ │ │ GUIDs: f6b5141d-eeb0-5ff1-b8de-ee4f02b222b7
│ │ │ ebd96940-fa49-5cb1-b1a1-aa2d4dea1416 ← USB\VID_04B4&PID_521A
│ │ │ 2c4d586a-a2a6-5957-9427-768add598121 ← USB\VID_04B4&PID_521A&REV_0000
│ │ │ 5108e726-44a6-5eca-bd1a-fbbdabbe7bc1 ← USB\VID_04B4&PID_521A&SID_1F00&APP_6D64
│ │ │ 31d41b9b-361a-50ad-8bea-8dad3339fa04 ← USB\VID_04B4&PID_521A&SID_1F00&APP_6D64&MODE_FW2
│ │ │ Device Flags: • Updatable
│ │ │ • System requires external power source
│ │ │ • Device stages updates
│ │ │ • Device can recover flash failures
│ │ │ • Unsigned Payload
│ │ │
│ │ └─ThinkPad USB-C Dock Gen2 USB Audio:
│ │ Device ID: 04fce9ab8ccd35c21c7c97b3cca8ca6778af17ce
│ │ Summary: CX21985 USB audio device
│ │ Current version:49-0E-14
│ │ Bootloader Version:03.01.00.00
│ │ Vendor: Lenovo (USB:0x17EF)
│ │ Install Duration:3 seconds
│ │ Serial Number:0
│ │ GUIDs: bc09c857-37b9-59ce-abed-62d8e371bca0 ← SYNAPTICS_CXAUDIO\ID_CX2198X
│ │ dbb8d54c-42e6-5215-b7ac-1df16872bb06 ← USB\VID_17EF&PID_A396
│ │ a46dd995-530f-50ea-949e-81ef05951964 ← USB\VID_17EF&PID_A396&REV_0014
│ │ Device Flags: • Updatable
│ │ • Unsigned Payload
│ │
│ └─USB3.1 Hub:
│ Device ID: bfcbc0ddc39dc66e25c82e261ac819888069e447
│ Summary: USB 3.x hub
│ Current version: 13.23
│ Vendor: VIA Labs, Inc. (USB:0x17EF)
│ Install Duration: 15 seconds
│ GUIDs: 7a216856-8a97-550c-882e-8233751c7cf2
│ 8b2439a7-f319-5583-950a-236eeecfe918 ← USB\VID_17EF&PID_A393
│ c6881bd6-7fc5-59f9-a21c-a1d525f817f4 ← USB\VID_17EF&PID_A393&REV_0D23
│ 41802a3a-da33-52c9-92d0-b3e4c8fc45d8 ← USB\VID_17EF&PID_A393&HUB_0008
│ bf4a4117-5351-5633-9dcf-83d67aee418e ← USB\VID_17EF&PID_A393&SPI_C840
│ 1dff17fd-59c2-57b0-8500-690d4ed4ca8e ← USB\VID_17EF&PID_A393&SPI_C840&REV_0D23
│ Device Flags: • Updatable
│ • Cryptographic hash verification is available
│ • Device stages updates
│ • Device can recover flash failures
│ • Unsigned Payload
│
├─0000:00:1f.5:
│ Device ID: b04e387fb80d2b91f37a4d0c7b21461c451775e1
│ Summary: Memory Technology Device
│ Vendor: DMI:LENOVO
│ GUIDs: 5f93d7e7-e282-59b9-b663-0146e382f8f6 ← MTD\NAME_0000:00:1f.5
│ 1d5d8ab8-c56e-59b0-9567-d4d306907af8 ← MTD\VENDOR_LENOVO&NAME_0000:00:1f.5
│ 7e343446-5890-55a0-8b9f-b4a68b7458b1 ← MTD\VENDOR_LENOVO&PRODUCT_20X300GACY&NAME_0000:00:1f.5
│ Device Flags: • Internal device
│ • Updatable
│ • Needs a reboot after installation
│ • Cryptographic hash verification is available
│
├─11th Gen Intel Core™ i7-1165G7 @ 2.80GHz:
│ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ Current version: 0x000000a6
│ Vendor: Intel
│ GUIDs: b9a2dd81-159e-5537-a7db-e7101d164d3f ← cpu
│ 30249f37-d140-5d3e-9319-186b1bd5cac3 ← CPUID\PRO_0&FAM_06
│ 2347ad97-b545-5bae-b6b3-b70a9553cbba ← CPUID\PRO_0&FAM_06&MOD_8C
│ 1df99df5-22f4-5505-98cc-22dcc53b132a ← CPUID\PRO_0&FAM_06&MOD_8C&STP_1
│ Device Flags: • Internal device
│
├─Integrated Camera:
│ Device ID: aa4b7bf130da693bbf1a8a785ad830190788233b
│ Current version: 60.1
│ Vendor: Azurewave (USB:0x13D3)
│ Serial Number: 0000
│ GUIDs: e43e8c39-23e2-55bd-83fb-ccb0264df2d8 ← USB\VID_13D3&PID_56FB
│ 939cfa2d-00c6-5498-b580-752505bacdf5 ← USB\VID_13D3&PID_56FB&REV_6001
│ Device Flags: • Updatable
│
├─Prometheus:
│ │ Device ID: 3fa281ddf80d8a06b8ee5d8beb48d38ee95a9627
│ │ Summary: Fingerprint reader
│ │ Current version: 10.01.3478575
│ │ Vendor: Synaptics (USB:0x06CB)
│ │ Install Duration: 2 seconds
│ │ Serial Number: 159625829836716
│ │ GUIDs: 8088f861-6318-5b1e-9ce4-fbddbedb09ac ← USB\VID_06CB&PID_00BD
│ │ 09e8bf16-3e69-50f5-bb66-c7a040248352 ← USB\VID_06CB&PID_00BD&REV_0000
│ │ Device Flags: • Updatable
│ │ • Cryptographic hash verification is available
│ │ • Signed Payload
│ │
│ └─Prometheus IOTA Config:
│ Device ID: 3401add23ddf0bf6d35b739d67083c343e4f6e35
│ Summary: Fingerprint reader config
│ Current version: 0029
│ Minimum Version: 0029
│ Vendor: Synaptics (USB:0x06CB)
│ GUIDs: 7c5a1e62-38fa-5859-9337-09dbac6377e4 ← USB\VID_06CB&PID_00BD-cfg
│ 8a12a1dd-5e54-5cb8-9607-c3a4e3e9a7e4 ← USB\VID_06CB&PID_00BD&CFG1_3462&CFG2_500
│ Device Flags: • Updatable
│ • Only version upgrades are allowed
│ • Signed Payload
│
├─System Firmware:
│ │ Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f
│ │ Summary: UEFI ESRT device
│ │ Current version: 65596
│ │ Vendor: LENOVO (DMI:LENOVO)
│ │ Update State: Success
│ │ Problems: • Device cannot be used while the lid is closed
│ │ GUIDs: 2efb2b3c-2363-4c0c-8d47-9b6427b449b3
│ │ 230c8b18-8d9b-53ec-838b-6cfc0383493a ← main-system-firmware
│ │ Device Flags: • Internal device
│ │ • System requires external power source
│ │ • Needs a reboot after installation
│ │ • Cryptographic hash verification is available
│ │ • Device is usable for the duration of the update
│ │ • Updatable
│ │
│ ├─BootGuard Configuration:
│ │ Device ID: b0d4430dfa6bde9f0c22680df36dbc8c15c80753
│ │ Current version: 20
│ │ Vendor: Intel Corporation (MEI:0x8086)
│ │ GUIDs: dd17041c-09ea-4b17-a271-5b989867ec65
│ │ f18c7464-aa01-5b3d-bd4f-6623597d0f70 ← MEI\VEN_8086&DEV_A0E0
│ │ 395a4458-f3a4-54b5-9947-e8b069f33c31 ← MEI\VEN_8086&DEV_A0E0&REV_20
│ │ bbcd2c79-2acd-5bd9-a608-57d4857a9ac1 ← MEI\VEN_8086&DEV_A0E0&SUBSYS_17AA508F
│ │ 1a88c6dd-21e6-56b2-b0ef-0b9584454943 ← MEI\VEN_8086&DEV_A0E0&SUBSYS_17AA508F&REV_20
│ │ Device Flags: • Internal device
│ │
│ └─UEFI dbx:
│ Device ID: 362301da643102b9f38477387e2193e57abaa590
│ Summary: UEFI revocation database
│ Current version: 217
│ Minimum Version: 217
│ Vendor: UEFI:Linux Foundation
│ Install Duration: 1 second
│ GUIDs: 1e9c3d61-4bd9-514e-ad87-0a9b61b9e77d ← UEFI\CRT_156645FC005F8617669DF76E1DE6FAE02B3856D24B624E47D97BD2B8ADFFB6E0
│ 304a9ede-aff2-58f6-b5e5-0e651b065f1a ← UEFI\CRT_156645FC005F8617669DF76E1DE6FAE02B3856D24B624E47D97BD2B8ADFFB6E0&ARCH_X64
│ c6682ade-b5ec-57c4-b687-676351208742 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503
│ f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64
│ Device Flags: • Internal device
│ • Updatable
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Only version upgrades are allowed
│ • Signed Payload
│
├─TPM:
│ Device ID: c6a80ac3a22083423992a3cb15018989f37834d6
│ Current version: 7.2.2.0
│ Vendor: Nuvoton Technology (TPM:NTC)
│ GUIDs: ff71992e-52f7-5eea-94ef-883e56e034c6 ← system-tpm
│ fac1c8f3-73c8-5cd6-8330-07a3690b5140 ← TPM\VEN_NTC&DEV_0000
│ e4a6bfd6-81ba-5d6a-bb28-84be07ee7a29 ← TPM\VEN_NTC&MOD_NPCT75x"!!4rls
│ e9ccc1dc-960a-5e09-afe9-e59a904b776d ← TPM\VEN_NTC&DEV_0000&VER_2.0
│ 5a6b5ab6-c483-5eec-8a34-23a6d6d120bd ← TPM\VEN_NTC&MOD_NPCT75x"!!4rls&VER_2.0
│ Device Flags: • Internal device
│
├─TigerLake-LP GT2 [Iris Xe Graphics]:
│ Device ID: 5792b48846ce271fab11c4a545f7a3df0d36e00a
│ Current version: 01
│ Vendor: Intel Corporation (PCI:0x8086)
│ GUIDs: 54ff3ed7-1ea3-5279-975f-93c13bf2aa53 ← PCI\VEN_8086&DEV_9A49
│ 3c11d563-4f83-5bd1-8369-75359ea6b6f6 ← PCI\VEN_8086&DEV_9A49&REV_01
│ 2ea0a4b6-128a-5194-a192-2c7d78808d81 ← PCI\VEN_8086&DEV_9A49&SUBSYS_17AA508F
│ cc508046-109f-5bf7-999e-6418a1085cf7 ← PCI\VEN_8086&DEV_9A49&SUBSYS_17AA508F&REV_01
│ 06f2a40f-75b6-5238-9fac-71ea35045c1c ← PCI\VEN_8086&DEV_9A49&REV_00
│ 52d42c65-309d-5b7c-8260-a1dbacfab91a ← PCI\VEN_8086&DEV_9A49&SUBSYS_17AA508F&REV_00
│ Device Flags: • Internal device
│ • Cryptographic hash verification is available
│
├─UEFI Device Firmware:
│ Device ID: 349bb341230b1a86e5effe7dfe4337e1590227bd
│ Summary: UEFI ESRT device
│ Current version: 4029220958
│ Minimum Version: 1
│ Vendor: DMI:LENOVO
│ Update State: Success
│ Problems: • Device cannot be used while the lid is closed
│ GUID: 51b57353-6b9f-4305-8ed2-12f66755104f
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Updatable
│
├─UEFI Device Firmware:
│ Device ID: 2292ae5236790b47884e37cf162dcf23bfcd1c60
│ Summary: UEFI ESRT device
│ Current version: 65584
│ Minimum Version: 65584
│ Vendor: DMI:LENOVO
│ Update State: Success
│ Problems: • Device cannot be used while the lid is closed
│ GUID: bd289402-2842-4455-8eaf-30b681d29967
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Updatable
│
├─UEFI Device Firmware:
│ Device ID: f95c9218acd12697af946874bfe4239587209232
│ Summary: UEFI ESRT device
│ Current version: 16973831
│ Minimum Version: 1
│ Vendor: DMI:LENOVO
│ Update State: Success
│ Problems: • Device cannot be used while the lid is closed
│ GUID: c494a23b-30a4-4308-a406-615aa4ea7201
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Updatable
│
├─UEFI Device Firmware:
│ Device ID: d96de5c124b60ed6241ebcb6bb2c839cb5580786
│ Summary: UEFI ESRT device
│ Current version: 0
│ Minimum Version: 1
│ Vendor: DMI:LENOVO
│ Update State: Success
│ Problems: • Device cannot be used while the lid is closed
│ GUID: 96fc1fc3-3013-43bd-bc97-5011b6dd7856
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Updatable
│
├─UEFI Device Firmware:
│ Device ID: f37fb01122dd62c773f4e84ec89737e059712d59
│ Summary: UEFI ESRT device
│ Current version: 1
│ Minimum Version: 1
│ Vendor: DMI:LENOVO
│ Update State: Success
│ Problems: • Device cannot be used while the lid is closed
│ GUID: bc9222ea-413e-4e89-aafd-c3857bafb242
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Updatable
│
├─UEFI Device Firmware:
│ Device ID: 36efb79c255f402f619fa9eb53cd659db51f2a04
│ Summary: UEFI ESRT device
│ Current version: 117572096
│ Minimum Version: 117572096
│ Vendor: DMI:LENOVO
│ Update State: Success
│ Problems: • Device cannot be used while the lid is closed
│ GUID: 25ca0f93-f2f0-49da-8f78-b6c4e6b4b520
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Updatable
│
├─UEFI Device Firmware:
│ Device ID: 11a7fbdd09ce583e58b899660fe10f147fd155a2
│ Summary: UEFI ESRT device
│ Current version: 2689118
│ Vendor: DMI:LENOVO
│ Update State: Success
│ Problems: • Device cannot be used while the lid is closed
│ GUID: bb2acbf1-4063-4816-9041-88bad259367a
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Updatable
│
├─UEFI Device Firmware:
│ Device ID: a083ebc5138e5e071ef7270cc9a8280722cc7adf
│ Summary: UEFI ESRT device
│ Current version: 24577
│ Minimum Version: 1
│ Vendor: DMI:LENOVO
│ Update State: Success
│ Problems: • Device cannot be used while the lid is closed
│ GUID: a9e9b56a-8e14-4c28-bb5f-d53d5817f0f7
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Updatable
│
└─WDC PC SN730 SDBQNTY-512G-1001:
Device ID: 04e17fcf7d3de91da49a163ffe4907855c3648be
Summary: NVM Express solid state drive
Current version: 11170101
Vendor: Sandisk Corp (NVME:0x15B7)
Serial Number: 213828802001
GUIDs: fccbb6ea-e20e-58ad-bf8a-7fb7d43ff4c2 ← NVME\VEN_15B7&DEV_5006
a39943dd-3afb-54f8-b110-c5a21f071200 ← NVME\VEN_15B7&DEV_5006&REV_00
12c86995-0b90-5ec5-98f3-7a6ed4ca50e0 ← NVME\VEN_15B7&DEV_5006&SUBSYS_15B75006
7b974856-317d-5538-a915-de0a6353750f ← NVME\VEN_15B7&DEV_5006&SUBSYS_15B75006&REV_00
06b4e2aa-91af-508b-b06e-65e3b3189e97 ← WDC PC SN730 SDBQNTY-512G-1001
Device Flags: • Internal device
• Updatable
• System requires external power source
• Needs a reboot after installation
• Device is usable for the duration of the updateHi, this is my output. As you can see I have nvme and my EFI is relatively full. I have removed one or two snap entries and an nfs entry for privacy reasons but they are almost definitely not relevant.
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 7.7G 15M 7.7G 1% /dev/shm
tmpfs 3.1G 2.2M 3.1G 1% /run
/dev/dm-0 327G 204G 122G 63% /
tmpfs 7.7G 3.1M 7.7G 1% /tmp
/dev/dm-0 327G 204G 122G 63% /home
/dev/loop10 50M 50M 0 100% /var/lib/snapd/snap/snapd/17883
/dev/loop11 348M 348M 0 100% /var/lib/snapd/snap/wine-platform-runtime/333
/dev/nvme0n1p5 974M 258M 649M 29% /boot
/dev/nvme0n1p2 95M 79M 17M 83% /boot/efi
tmpfs 1.6G 280K 1.6G 1% /run/user/1000/dev/nvme0n1p2 95M 79M 17M 83% /boot/efi
@ChiWei-Chen is that too little? If you give me the "it must have xxxM free on the ESP" then I can add that as a check on fwupd.
ChiWei-Chen
commented
1 year ago @hughsie , it looks a bit little, I'll need to get FW team to comment on this. Thanks!
superm1
commented
1 year ago /dev/nvme0n1p2 95M 79M 17M 83% /boot/efi
That's a really small ESP in general. What distro offered it? Probably should get their installer to offer bigger ones too.
ChiWei-Chen
commented
1 year ago Hi everyone- I am also having this exact problem. I have a lenovo thinkpad T490 with Fedora 36. My fwupd-efi version is also 1.3 , fwupd is 1.8.6
It looks Fedora 36.
@hughsie , here is the FW team's feedback, hope this helps:
It is small. I am not sure what product is used. But basically recent BIOS capsule image size is appropriate 30 MB. I recommend to prepare double size of BIOS capsule file at least. And the space should be sequential. Roughly 80 MB available space is needed.
BTW, the issue of the following system needs to investigate separately.
/dev/nvme0n1p1 300M 312K 300M 1% /boot/efi
superm1
commented
1 year ago Roughly 80 MB available space is needed.
I don't recall if we are already, but we should make sure we're clearing space after updates finish the next boot too by the daemon.
autumn-traveller
commented
1 year ago Sorry I completely forgot to mention this but I have a dual-boot system, Windows 10 + Fedora 36. I briefly looked through the /boot/efi/EFI directory and found the following:
du -hsx /boot/efi/EFI/fedora/fw*
37M fedora/fw
61K fedora/fwupdx64.efidu -hsx /boot/efi/EFI/fedora/fw/*
12M fedora/fw/fwupd-2c0665e2-fdbd-495e-b8e4-69d92b9c119a.cap
754K fedora/fw/fwupd-38ea6335-29ca-417b-8cd4-6b4e5e866f92.cap
24M fedora/fw/fwupd-603baf73-b997-45b5-86b4-2f981a008e18.capdu -hsx /boot/efi/EFI/fedora/fw/*
We should be deleting old capsule files before scheduling the new ones, as long as BootNext isn't set. What's the creation time on those files please?
autumn-traveller
commented
1 year ago Feb 10 13:57 on all 3
autumn-traveller
commented
1 year ago Since the entire size of my EFI partition is just 95MB, will your latest commit mean that I am unable to use fwupd at all?
hughsie
commented
1 year ago @noobsauce101 a 95MB partition is quite unsuitable for a dual boot system. For comparison, mine is 600MB. The commit message is slightly misleading, we now require 2*capsule size, plus 20MB.
autumn-traveller
commented
1 year ago Yeah I am looking into resizing it now. Thank you guys for all your help!
mrhpearson
commented
1 year ago Are we OK to close this issue now?
hughsie
commented
1 year ago Yup, 1.8.11 has the checks for double the capsule size.
VannTen
commented
1 year ago Hi.
I'm getting the same problem (or maybe it's related to the new check introduced in fwupd ?)
# dmidecode -s system-version
ThinkPad X1 Carbon Gen 9
# fwupdmgr --version
compile org.freedesktop.fwupd 1.8.12
compile com.hughsie.libxmlb 0.3.11
compile com.hughsie.libjcat 0.1.12
runtime org.freedesktop.fwupd-efi 1.4
compile org.freedesktop.gusb 0.4.5
runtime com.hughsie.libjcat 0.1.13
runtime com.dell.libsmbios 2.4
runtime org.freedesktop.gusb 0.4.5
runtime org.kernel 6.2.6-arch1-1
runtime org.freedesktop.fwupd 1.8.12
# Free space on ESP
df -h /efi
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p1 200M 73M 128M 37% /efiMessage happening when running fwupdmgr upgrade (when rebooting):
fwupd-efi version1.4
WARNING: Could not apply capsule update: Volume Full
WARNING: Could not apply capsules: Volume Full
Reset SystemFrom the previous comment, my EFI partition seems to have enough space, So I think that's not the issue ? Also, I'm using a Unified Kernel Image to boot, if that's relevant.
Any ideas ?
gstephan76
commented
1 year ago Hi,
The issue that I had went away inexplicably. I thought it was due to some new version in the software stack. Regardless, it follows the data that you have requested.
BTW, in my case lack of space as pointed out by "df" has never been an issue.
Thanks for your help,
root > df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 16G 114M 16G 1% /dev/shm tmpfs 6.3G 25M 6.2G 1% /run /dev/dm-0 473G 197G 273G 42% / tmpfs 16G 9.3M 16G 1% /tmp /dev/dm-0 473G 197G 273G 42% /home /dev/nvme0n1p3 974M 435M 472M 48% /boot /dev/nvme0n1p1 200M 57M 144M 29% /boot/efi tmpfs 3.2G 7.1M 3.2G 1% /run/user/1000
root > fwupdmgr --version compile org.freedesktop.fwupd 1.8.12 compile com.hughsie.libxmlb 0.3.10 compile com.hughsie.libjcat 0.1.12 runtime org.freedesktop.fwupd-efi 1.4 compile org.freedesktop.gusb 0.4.5 runtime com.hughsie.libjcat 0.1.13 runtime com.dell.libsmbios 2.4 runtime org.freedesktop.gusb 0.4.5 runtime org.freedesktop.fwupd 1.8.12 runtime org.kernel 6.2.2-300.fc37.x86_64
root > fwupdmgr get-devices LENOVO 20TJS2F42V │ ├─CometLake-H GT2 [UHD Graphics]: │ Device ID: 5792b48846ce271fab11c4a545f7a3df0d36e00a │ Current version: 05 │ Vendor: Intel Corporation (PCI:0x8086) │ GUIDs: 3777783a-3f83-56a5-95f4-533eb6a2bd19 ← PCI\VEN_8086&DEV_9BC4 │ 6c3dbf6c-4e6f-5309-9954-c5ab7aca617e ← PCI\VEN_8086&DEV_9BC4&REV_05 │ 5fde5d20-db24-5f21-afdd-247c1bf1efa1 ← PCI\VEN_8086&DEV_9BC4&SUBSYS_17AA22C2 │ 07168636-0f3b-565c-8fe1-0f0a77d82cd8 ← PCI\VEN_8086&DEV_9BC4&SUBSYS_17AA22C2&REV_05 │ 7ffe1cb7-395a-52a9-a172-70ec6caaf310 ← PCI\VEN_8086&DEV_9BC4&REV_00 │ b813dc18-ddf2-508d-a7eb-0e2fc8752b03 ← PCI\VEN_8086&DEV_9BC4&SUBSYS_17AA22C2&REV_00 │ Device Flags: • Internal device │ • Cryptographic hash verification is available │ ├─Core™ i7-10850H CPU @ 2.70GHz: │ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027 │ Current version: 0x000000f0 │ Vendor: Intel │ GUIDs: b9a2dd81-159e-5537-a7db-e7101d164d3f ← cpu │ 30249f37-d140-5d3e-9319-186b1bd5cac3 ← CPUID\PRO_0&FAM_06 │ a45b0522-5722-54bd-b802-86cd044262df ← CPUID\PRO_0&FAM_06&MOD_A5 │ 7b9b6e8c-226c-5db6-86cb-ea3187578013 ← CPUID\PRO_0&FAM_06&MOD_A5&STP_2 │ Device Flags: • Internal device │ ├─Embedded Controller: │ Device ID: 2292ae5236790b47884e37cf162dcf23bfcd1c60 │ Summary: UEFI ESRT device │ Current version: 0.1.11 │ Minimum Version: 0.1.11 │ Vendor: Lenovo (DMI:LENOVO) │ Update State: Success │ GUID: b616d3d6-cca9-40bd-964e-b86ffb62744d │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─Generic Billboard Device: │ Device ID: d1c0f19d1c857ac319c2d8f29e35ef0056a47b15 │ Current version: 7.99.32.0 │ Vendor: Fresco Logic, Inc (USB:0x1D5C) │ Install Duration: 15 seconds │ GUIDs: 4b8e93aa-7207-5706-9e90-b55306343c84 ← USB\VID_1D5C&PID_7102 │ 5564faf2-5478-5d9c-9e11-29039b6ae7e0 ← USB\VID_1D5C&PID_7102&REV_0100 │ 790a1b00-9cf9-5220-af78-ef690d303fa8 ← USB\VID_1D5C&PID_7102&CID_63 │ Device Flags: • Updatable │ ├─Integrated Camera: │ Device ID: 4745cb127beea10281899d84cd01952ed74156a6 │ Current version: 60.1 │ Vendor: Azurewave (USB:0x13D3) │ Serial Number: 0000 │ GUIDs: 9284c551-0b4c-51ee-905a-168b8787290c ← USB\VID_13D3&PID_5405 │ 4dc71255-84a9-5adc-8eab-c5982db48621 ← USB\VID_13D3&PID_5405&REV_6001 │ Device Flags: • Updatable │ ├─Intel Management Engine: │ Device ID: 349bb341230b1a86e5effe7dfe4337e1590227bd │ Summary: UEFI ESRT device │ Current version: 225.67.2046 │ Minimum Version: 0.0.1 │ Vendor: Lenovo (DMI:LENOVO) │ Update State: Success │ GUID: 5695cc48-4f4f-4677-8ffb-9f496d3ad9d3 │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─KXG6AZNV512G TOSHIBA: │ Device ID: 08e1798bf5d9cb56a0290b552cab6c1a371b5089 │ Summary: NVM Express solid state drive │ Current version: 5108AGLA │ Vendor: Toshiba Corporation (NVME:0x1179) │ Serial Number: 215F73G9FDP3 │ GUIDs: 94eae9cd-5ee6-5b80-9a3e-ffa2db88cd87 ← NVME\VEN_1179&DEV_011A │ de51500a-8b48-5f13-b0c1-0bbded7c54c1 ← NVME\VEN_1179&DEV_011A&REV_00 │ 141102bc-3608-5bc8-a700-983f47d476f4 ← NVME\VEN_1179&DEV_011A&SUBSYS_11790001 │ 9da14130-275e-52fc-8119-63be32bd58dd ← NVME\VEN_1179&DEV_011A&SUBSYS_11790001&REV_00 │ 7907bb58-84c2-5473-bcca-255d8f33a347 ← KXG6AZNV512G TOSHIBA │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Signed Payload │ ├─Prometheus: │ │ Device ID: 9adad7ff10200dcc06aac2d6d70dc2c5cc65f703 │ │ Summary: Fingerprint reader │ │ Current version: 10.01.3478575 │ │ Vendor: Synaptics (USB:0x06CB) │ │ Install Duration: 2 seconds │ │ Serial Number: 131952886400976 │ │ GUIDs: 8088f861-6318-5b1e-9ce4-fbddbedb09ac ← USB\VID_06CB&PID_00BD │ │ 09e8bf16-3e69-50f5-bb66-c7a040248352 ← USB\VID_06CB&PID_00BD&REV_0000 │ │ Device Flags: • Updatable │ │ • Supported on remote server │ │ • Cryptographic hash verification is available │ │ • Signed Payload │ │ │ └─Prometheus IOTA Config: │ Device ID: 292df36495e4c4177c60602877f7a003587799d1 │ Summary: Fingerprint reader config │ Current version: 0030 │ Minimum Version: 0030 │ Vendor: Synaptics (USB:0x06CB) │ GUIDs: 7c5a1e62-38fa-5859-9337-09dbac6377e4 ← USB\VID_06CB&PID_00BD-cfg │ 8177bb07-fa98-5bdb-a55d-bdc0fa95535b ← USB\VID_06CB&PID_00BD&CFG1_3462&CFG2_800 │ Device Flags: • Updatable │ • Supported on remote server │ • Only version upgrades are allowed │ • Signed Payload │ ├─System Firmware: │ │ Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f │ │ Summary: UEFI ESRT device │ │ Current version: 0.1.27 │ │ Minimum Version: 0.1.11 │ │ Vendor: Lenovo (DMI:LENOVO) │ │ Update State: Success │ │ GUIDs: 6e58e73d-8061-44e4-8949-33b7f0d5c726 │ │ 230c8b18-8d9b-53ec-838b-6cfc0383493a ← main-system-firmware │ │ Device Flags: • Internal device │ │ • Updatable │ │ • System requires external power source │ │ • Supported on remote server │ │ • Needs a reboot after installation │ │ • Cryptographic hash verification is available │ │ • Device is usable for the duration of the update │ │ │ ├─AMT [unprovisioned]: │ │ Device ID: 8d5470e73fd9a31eaa460b2b6aea95483fe3f14c │ │ Summary: Hardware and firmware technology for remote out-of-band management │ │ Current version: 14.1.67.2046 │ │ Bootloader Version:14.1.67.2046 │ │ Vendor: Intel Corporation (MEI:0x8086) │ │ GUIDs: 12f80028-b4b7-4b2d-aca8-46e0ff65814c │ │ 15c7ef4d-12fc-5e25-aba6-49b30f5ab130 ← MEI\VEN_8086&DEV_06E0 │ │ a65d125e-0c76-5876-bad3-6956a2f25e5e ← MEI\VEN_8086&DEV_06E0&REV_00 │ │ a8f5ca2d-e46c-5c9b-819b-d64c73c9e48d ← MEI\VEN_8086&DEV_06E0&SUBSYS_17AA22C2 │ │ 45bcbef5-0630-5121-a4d9-881054b2916f ← MEI\VEN_8086&DEV_06E0&SUBSYS_17AA22C2&REV_00 │ │ Device Flags: • Internal device │ │ │ └─UEFI dbx: │ Device ID: 362301da643102b9f38477387e2193e57abaa590 │ Summary: UEFI revocation database │ Current version: 217 │ Minimum Version: 217 │ Vendor: UEFI:Linux Foundation │ Install Duration: 1 second │ GUIDs: 14503b3d-73ce-5d06-8137-77c68972a341 ← UEFI\CRT_A9087D1044AD18F7A94916D284CBC01827CF23CD8F60B79072C9CAA1FEF4D649 │ 5971a208-da00-5fce-b5f5-1234342f9cf7 ← UEFI\CRT_A9087D1044AD18F7A94916D284CBC01827CF23CD8F60B79072C9CAA1FEF4D649&ARCH_X64 │ c6682ade-b5ec-57c4-b687-676351208742 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503 │ f8ba2887-9411-5c36-9cee-88995bb39731 ← UEFI\CRT_A1117F516A32CEFCBA3F2D1ACE10A87972FD6BBE8FE0D0B996E09E65D802A503&ARCH_X64 │ Device Flags: • Internal device │ • Updatable │ • Supported on remote server │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ • Only version upgrades are allowed │ • Signed Payload │ ├─TPM: │ Device ID: c6a80ac3a22083423992a3cb15018989f37834d6 │ Current version: 1.258.0.0 │ Vendor: ST Microelectronics (TPM:STM) │ GUIDs: ff71992e-52f7-5eea-94ef-883e56e034c6 ← system-tpm │ 84df3581-f896-54d2-bd1a-372602f04c32 ← TPM\VEN_STM&DEV_0001 │ bfaed10a-bbc1-525b-a329-35da2f63e918 ← TPM\VENSTM&MOD │ 70b7b833-7e1a-550a-a291-b94a12d0f319 ← TPM\VEN_STM&DEV_0001&VER_2.0 │ 06f005e9-cb62-5d1a-82d9-13c534c53c48 ← TPM\VENSTM&MOD&VER_2.0 │ Device Flags: • Internal device │ ├─UEFI Device Firmware: │ Device ID: f95c9218acd12697af946874bfe4239587209232 │ Summary: UEFI ESRT device │ Current version: 16777222 │ Minimum Version: 1 │ Vendor: DMI:LENOVO │ Update State: Success │ GUID: 439d54f4-5548-4698-a8b0-46a047c0e66e │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ ├─UEFI Device Firmware: │ Device ID: d96de5c124b60ed6241ebcb6bb2c839cb5580786 │ Summary: UEFI ESRT device │ Current version: 65794 │ Minimum Version: 65794 │ Vendor: DMI:LENOVO │ Update State: Success │ GUID: 3fb9a55d-d7f1-4d1b-b216-74e328e28f51 │ Device Flags: • Internal device │ • Updatable │ • System requires external power source │ • Needs a reboot after installation │ • Device is usable for the duration of the update │ └─UEFI Device Firmware: Device ID: f37fb01122dd62c773f4e84ec89737e059712d59 Summary: UEFI ESRT device Current version: 24577 Minimum Version: 1 Vendor: DMI:LENOVO Update State: Success GUID: 33967546-da89-4c51-9c95-5242bcb854e8 Device Flags: • Internal device • Updatable • System requires external power source • Needs a reboot after installation • Device is usable for the duration of the update
Em qua., 15 de fev. de 2023 às 01:50, ChiWei-Chen @.***> escreveu:
Hi @alexted https://github.com/alexted , @noobsauce101 https://github.com/noobsauce101 , @gstephan76 https://github.com/gstephan76 , our FW team wasn't able to reproduce this issue yet, but they suspect this is EFI space related, could you provide output of df -h for our investigation.
— Reply to this email directly, view it on GitHub https://github.com/fwupd/firmware-lenovo/issues/257#issuecomment-1430751528, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIWR3VGJEMNKYDBMLIDJEJLWXROBDANCNFSM56SQRDDQ . You are receiving this because you were mentioned.Message ID: @.***>
capybara-overdose
commented
1 year ago Yeah this needs to be reopened, its still doing it.
x390 applying System firmware update from 0.1.93 to 0.1.95 - over 700MB spare on the EFI partition.
leleogere
commented
1 year ago Maybe it can help someone, or maybe I had some luck, but here is what happed to me. I had the "Volume full" error as others, but I noticed that I had a bootable USB stick plugged. Without much hope, I unplugged it to see if it would have an impact, and after another reboot if worked.
I have no idea if unplugging this USB stick was the solution, but I don't think that I did anything else apart from that. Maybe something else happened at the sale time?
hughsie
commented
1 year ago @leleogere it's certainly plausible; we added https://github.com/fwupd/fwupd/pull/5900 recently to use a better algorithm for choosing an ESP.
soig
commented
1 year ago Maybe it can help someone, or maybe I had some luck, but here is what happed to me. I had the "Volume full" error as others, but I noticed that I had a bootable USB stick plugged. Without much hope, I unplugged it to see if it would have an impact, and after another reboot if worked.
I have no idea if unplugging this USB stick was the solution, but I don't think that I did anything else apart from that. Maybe something else happened at the sale time?
Indeed that fixed the issue for me. I'd still the install USB key plugged in the laptop dock. Removing it made that error message to disapear. Looks like a big issue with Lenovo firwmare. Someone ought to report to Lenovo that their BIOS/UEFI has this issue
susman
commented
9 months ago FYI I ended up resizing EFI partition from ~200M to ~300M and the issue went away. I think the main problem for me was the "Volume full" message. It's a little cryptic: not clear which "volume" that is and "full" is something that really thrown me off the investigation path, I could clearly see that my ESP is not full. A message like "Not enough free space on ESP" would be much more informative.
mrhpearson
commented
8 months ago Just a note as I hit this issue myself, and Google pointed at this bug. I scratched my head, and figured it out. I had a bootable USB in my system (just did a fresh install of Fedora) and that was the problem. As soon as I unplugged the USB the update worked smoothly.
Not sure exactly why - will need to ask the FW team - but I assume that it tries to unpack to the USB and runs out of space?
hughsie
commented
8 months ago As soon as I unplugged the USB the update worked smoothly.
Older versions of fwupd didn't have a great default for choosing which ESP should be used by default. If you can reproduce this with 1.9.14 or newer please let us know!
Describe the bug I'm running
fwmgr updateon my ThinkPad P53 from Arch Linux, dual booting, when rebooting the update process starts correctly, but I'm getting:Steps to Reproduce
fwupdmgr updateExpected behavior Firmware updates correctly.
fwupd version information
Please note how you installed it (
apt,dnf,pacman, source, etc): Installed throughpacman -S fwupdfwupd device information
System UEFI configuration Please provide the output of the following commands:
Note: I'm using rEFInd as a boot loader, booting into a UEFI image created from the above kernel + initrd + ucode + kernel parameters, if that's relevant info.
Additional questions
Linux arch-linux 5.18.16-arch1-1 fwupd/fwupd#1 SMP PREEMPT_DYNAMIC Wed, 03 Aug 2022 11:25:04 +0000 x86_64 GNU/Linux