fwupdmgr: "WARNING: UEFI ESP partition may not be set up correctly" for no apparent reason #6035
Comments
vmatare
changed the title
|
Hmm, that page sure used to exist. Perhaps someone deleted it? |
|
I've added a link to https://github.com/fwupd/fwupd/wiki/LVFS-Triaged-Issue:-Invalid-ESP-Partition as that's the one I think should be used to describe this. fwupdtool esp-list --verbose will work fine -- but the firmware might not. Newer machines are much more strict about partitions being tagged with the correct GUID. |
|
@vmatare did you create the ESP partition, or did Anaconda do it for you? |
I'm pretty sure Anaconda did it. After I got this message from fwupd, I noticed that it had a weird type flag (I think it was So apparently it's not even a GPT partitioning scheme. Anaconda might have just left it the way it was before. But normally GPT shouldn't be strictly necessary, right? |
|
The firmware used to not care, but it seems more and more firmware does nowadays. It's probably more because it's not being tested on MBR partitions anymore. If firmware updates do work for you it's safe to ignore. |
|
I'm having the same problem. Describe the bug Steps to Reproduce Expected behavior fwupd version information $ fwupdmgr --version
compile org.freedesktop.fwupd 1.9.5
compile com.hughsie.libxmlb 0.3.12
compile com.hughsie.libjcat 0.1.13
runtime org.freedesktop.fwupd-efi 1.4
compile org.freedesktop.gusb 0.4.5
runtime com.hughsie.libjcat 0.1.13
runtime org.freedesktop.gusb 0.4.5
runtime org.freedesktop.fwupd 1.9.5
runtime org.kernel 6.5.5-200.fc38.x86_64Please note how you installed it ( fwupd device information$ fwupdmgr get-devices --show-all-devices
WARNING: UEFI ESP partition may not be set up correctly
See https://github.com/fwupd/fwupd/wiki/PluginFlag:esp-not-valid for more information.
Dell Inc. XPS 15 9560
│
├─Core™ i7-7700HQ CPU @ 2.80GHz:
│ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ Current version: 0x000000f4
│ Vendor: Intel
│ GUIDs: b9a2dd81-159e-5537-a7db-e7101d164d3f ← cpu
│ 30249f37-d140-5d3e-9319-186b1bd5cac3 ← CPUID\PRO_0&FAM_06
│ 809a0b93-8a12-5338-a571-ad5583acf896 ← CPUID\PRO_0&FAM_06&MOD_9E
│ d0f754d5-1395-5573-bc83-85ba955da70a ← CPUID\PRO_0&FAM_06&MOD_9E&STP_9
│ Device Flags: • Internal device
│
├─GP107M [GeForce GTX 1050 Mobile]:
│ Device ID: ce4c74a5188d5b9cdb1e72ed32dad2d313c1c999
│ Current version: a1
│ Vendor: NVIDIA Corporation (PCI:0x10DE, PCI:0x8086)
│ GUIDs: ef41e989-4e6e-560d-a860-ea71aa8c21a3 ← PCI\VEN_10DE&DEV_1C8D
│ 5fdc8f12-8985-5dcb-95ea-5761f769cb4d ← PCI\VEN_10DE&DEV_1C8D&SUBSYS_102807BE
│ d29269b6-e458-5f45-975c-9d52bb38e35f ← PCI\VEN_8086&DEV_1901
│ 6949aa50-f4e1-578b-81c8-d8c61915cfe2 ← PCI\VEN_8086&DEV_1901&SUBSYS_102807BE
│ Device Flags: • Internal device
│ • Cryptographic hash verification is available
│
├─HD Graphics 630:
│ Device ID: 5792b48846ce271fab11c4a545f7a3df0d36e00a
│ Current version: 04
│ Vendor: Intel Corporation (PCI:0x8086)
│ GUIDs: f744dc01-a247-5543-b9db-2adba3091233 ← PCI\VEN_8086&DEV_591B
│ 089d6890-1705-50c9-92bd-55a1bd648ed9 ← PCI\VEN_8086&DEV_591B&SUBSYS_102807BE
│ Device Flags: • Internal device
│ • Cryptographic hash verification is available
│
├─SHGP31-1000GM:
│ Device ID: 04e17fcf7d3de91da49a163ffe4907855c3648be
│ Summary: NVM Express solid state drive
│ Current version: 41062C20
│ Vendor: SK hynix (NVME:0x1C5C)
│ Serial Number: ASACN55231020CE1M
│ GUIDs: 0ee57466-ca9d-5f10-a005-ec6bacf6fb82 ← NVME\VEN_1C5C&DEV_174A
│ 34e06406-f620-5b9d-a9cd-7f3a4e648633 ← NVME\VEN_1C5C&DEV_174A&SUBSYS_1C5C174A
│ c555ec26-0c1b-5724-97ac-01bf179af935 ← SHGP31-1000GM
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Signed Payload
│
└─System Firmware:
│ Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f
│ Summary: UEFI ESRT device
│ Current version: 1.31.0
│ Minimum Version: 1.31.0
│ Vendor: Dell (DMI:Dell Inc.)
│ Update State: Success
│ GUIDs: 34578c72-11dc-4378-bc7f-b643866f598c
│ 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
│ • 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: 11.8.93.4323
│ Bootloader Version:11.8.93.4323
│ Vendor: Intel Corporation (MEI:0x8086)
│ GUIDs: 12f80028-b4b7-4b2d-aca8-46e0ff65814c
│ d39310dc-e5d7-5eb2-945d-22011cbd3157 ← MEI\VEN_8086&DEV_A13A
│ fdb39475-3243-525a-915e-26ebf8a413bb ← MEI\VEN_8086&DEV_A13A&SUBSYS_102807BE
│ Device Flags: • Internal device
│
├─UEFI Platform Key:
│ Device ID: 6924110cde4fa051bfdc600a60620dc7aa9d3c6a
│ Summary: Dell Inc. Platform Key
│ Vendor: Dell Inc.
│ GUID: 5f7cc4ea-9f7a-5c5f-b535-dfbcc73f5ba6 ← UEFI\CRT_2493B118EABD632FD3BA49C333A8329B1982E872
│
└─UEFI dbx:
Device ID: 362301da643102b9f38477387e2193e57abaa590
Summary: UEFI revocation database
Current version: 220
Minimum Version: 220
Vendor: UEFI:Linux Foundation
Install Duration: 1 second
GUIDs: 00fe3755-a4d8-5ef7-ba5f-47979fbb3423 ← UEFI\CRT_E28D59CA489BD2AD580F2EA5D62D6A29BB9C02AE5A818434A37DA7FC11DFF9E9
4a6cd2cb-8741-5257-9d1f-89a275dacca7 ← UEFI\CRT_E28D59CA489BD2AD580F2EA5D62D6A29BB9C02AE5A818434A37DA7FC11DFF9E9&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
Additional questions
Interestingly, my FAT32 Basic Data partition (7) is listed alongside my actual ESP (1) when listing
|
|
I have the same problem. I believe that fwupd thinks that a partition with the msftdata flag set is an EFI partition. I do not run windows only linux on my laptop but have a recovery partition with the msftdata flag set. fwupdtool esp-list --verbose also lists my recovery partition along with my 2 EFI partitions. This only happens with fedora. I have debian running on another partition and do not get any error when running debian. It also does not happen with ubuntu. I can do firmware updates from ubuntu or debian but the only one I attempted from fedora 38 hung my system. |
|
[ EDIT : SOLVED TO ME ] Hi, I have exactly the same issue, even a bit worse.
|
|
Also broken for me, and I do have the |
hughsie
added a commit
that referenced
this issue
Dec 7, 2023
4 tasks
So we're showing that as we've chosen the msftdata partition (presumably because it's bigger - and also has linux-related files on it) which doesn't have the ESP flag set. Could you try with #6507 and then get me the output of |
hughsie
added a commit
that referenced
this issue
Dec 7, 2023
hughsie
added a commit
that referenced
this issue
Dec 7, 2023
|
Yes that patch fixes it - this is the output: |
Is that a recovery partition? |
|
I believe so yes - it's a Dell XPS 13 developer edition so it came with Ubuntu and I reinstalled with Fedora but I probably just left the recovery partition alone. |
|
Can you get us the partition "Name" please? We're already ignoring |
|
The first partition (the real ESP ) seems to be called "EFI System Partition" and the second partition (the msftdata one) is called "Basic data partition". |
Bleh, that's the fallback IIRC for when the name isn't set. Maybe the UUID is something we could key-from? i.e. if you google your |
|
The UUID is |
So random -- which is probably good I suppose. Okay, no further action required, thanks! |
|
IIRC Dell recovery partition labels are "OS". |
|
Hi, same situation, Dell XPS 13 9370 preloaded with Ubuntu reinstalled with Fedora. Regards |
|
@diegorondini is the |
|
I could do one better. Here's a relatively complete ignore list: |
|
I almost wonder if |
|
|
|
e.g. like #6512 perhaps. |
hughsie
added a commit
that referenced
this issue
Dec 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Whenever I execute
fwupdmgr, I get:The link however is dead (leads to "create new page").
Steps to Reproduce
Don't know what's causing it. That is precisely the problem.
fwupdtool esp-list --verboseseems to be working just fine:Expected behavior
I expect some info on why
fwupdmgrthinks something is wrong with my ESP.fwupd version information
Please note how you installed it (
apt,dnf,pacman, source, etc):dnf**fwupd device information**
Please provide the output of the fwupd devices recognized in your system.
Additional questions
The text was updated successfully, but these errors were encountered: