Fedora 40 fwupdmgr: partition kind required #7298

smooge · 2024-05-29T19:32:46Z

Describe the bug
I have a Dell Precision 3630 with an outstanding firmware update. When running the commands, I get a small error but no idea on how to fix it:

# fwupdmgr upgrade
Devices with no available firmware updates: 
 • SSD 850 EVO 500GB
 • SSD 870 EVO 2TB
 • SSD 870 EVO 2TB
 • TPM
 • WDC WD40NDZW-11BCSS0
Devices with the latest available firmware version:
 • PC SN730 NVMe WDC 256GB
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade System Firmware from 2.25.0 to 2.28.0?                               ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ Improved the stability of the system during system boot.                     ║
║                                                                              ║
║ Precision 3630 Tower must remain plugged into a power source for the         ║
║ duration of the update to avoid damage.                                      ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: y
Decompressing…           [                                       ] Less than one minute remaining…
partition kind required

# fwupdtool get-devices --plugins uefi_capsule
Loading…                 [********                               ]19:17:21.826 FuUsbDevice          failed to parse platform BOS descriptor: failed to parse: no supported platform version: did not find magic
Loading…                 [************************************** ]
Dell Inc. Precision 3630 Tower
│
└─System Firmware:
      Device ID:          ffcb7fc2e5d13bb0d48b3d616881c5ba76604ea2
      Summary:            UEFI System Resource Table device (updated via NVRAM)
      Current version:    2.25.0
      Minimum Version:    2.25.0
      Vendor:             Dell (DMI:Dell Inc.)
      Update State:       Success
      GUID:               c0745fac-f5a5-46c9-b716-3cc5781e876e
      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
      Device Requests:    • Message

I added more -v to the call and got

19:25:27.521 FuStruct             Ds20:
  guid: d8dd60df-4589-4cc7-9cd2-659d9e648a9f
  platform_ver: 0xa000000
  total_length: 0x2c4
  vendor_code: 0x5f
  alt_code: 0x0
19:25:27.521 FuUsbDeviceDs20      PlatformVersion=0x0a000000, TotalLength=0x02c4, VendorCode=0x5f, AltCode=0x00
19:25:27.521 FuUsbDevice          failed to parse platform BOS descriptor: failed to parse: no supported platform version: did not find magic
19:25:27.521 FuEngine             usb:01:00:08:03:03 added FuUsbDevice:
  Guid:                 a02c13a4-83fc-50e2-8627-d349a7982b6d <- USB\VID_0BDA&PID_58FC ?
  Flags:                none
  VendorId:             USB:0x0BDA
  Version:              77.18
  VersionFormat:        bcd
  VersionRaw:           0x00007718
  Guid[quirk]:          fb69fd72-4832-567d-9337-790ed4f68416 <- USB\VID_0BDA
  Guid[quirk]:          07e0a3c7-78c7-5bc4-a427-64b6cb854ec7 <- USB\CLASS_0E
  Guid[quirk]:          a0e4d690-5116-54c6-a775-fbe41e15c61c <- USB\CLASS_0E&SUBCLASS_01
  Guid[quirk]:          edb49b58-92cb-5ffd-8c4e-67b6cab9f7cc <- USB\CLASS_0E&SUBCLASS_01&PROT_00
  Guid[quirk]:          f7e73420-87ab-5248-a34e-a48967c622ba <- USB\CLASS_0E&SUBCLASS_02
  Guid[quirk]:          07e4a5c1-04f3-5a47-aa65-07fcac15033e <- USB\CLASS_0E&SUBCLASS_02&PROT_00
  PhysicalId:           usb:01:00:08:03:03
  AcquiesceDelay:       2500
  ParentPhysicalIds:    usb:01:00:08:03,usb:01:00:08
  UsbDeviceClass:       miscellaneous

but I don't know if that helps. I did look to see if the /boot/efi was seen as an EFI partition

[root@xenadu ~]# df -h /boot/efi/
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p1  500M   31M  470M   7% /boot/efi
[root@xenadu ~]# fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: PC SN730 NVMe WDC 256GB                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C873B616-9B19-44BC-8010-8CE59A822373

Device           Start       End   Sectors   Size Type
/dev/nvme0n1p1    2048   1026047   1024000   500M EFI System
/dev/nvme0n1p2 1026048   8837119   7811072   3.7G Linux filesystem
/dev/nvme0n1p3 8837120 458110975 449273856 214.2G Linux LVM

Steps to Reproduce
On a Dell Precision 3630, run fwupdmgr to get updates

Expected behavior
I expected either the update to go through or a more clear message on what kind of partition was not matching.

fwupd version information
Version of the fwupdmgr package:

[root@xenadu ~]# fwupdmgr --version
compile   org.freedesktop.fwupd         1.9.20
compile   com.hughsie.libxmlb           0.3.19
compile   org.freedesktop.Passim        0.1.7
compile   com.hughsie.libjcat           0.2.1
runtime   org.freedesktop.fwupd-efi     1.6
compile   org.freedesktop.gusb          0.4.9
runtime   com.hughsie.libxmlb           0.3.19
runtime   org.freedesktop.Passim        0.1.7
runtime   org.freedesktop.gusb          0.4.9
runtime   com.hughsie.libjcat           0.2.1
runtime   org.kernel                    6.8.10-300.fc40.x86_64
runtime   org.freedesktop.fwupd         1.9.20

Please note how you installed it (apt, dnf, pacman, source, etc):

This was installed via dnf on Fedora 40

**fwupd device information**

Please provide the output of the fwupd devices recognized in your system.

fwupdmgr get-devices --show-all-devices
Idle…: 0%
Dell Inc. Precision 3630 Tower
│
├─Unknown Device:
│     Device ID:          4a4907dbb1b96c6a1177dfd1b95eb41c781d1265
│     GUID:               1199a818-4c52-5137-b536-d59e2e2cada9 ← GPIO\ID_INT3450:00
│   
├─Core™ i7-9700 CPU @ 3.00GHz:
│     Device ID:          4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│     Current version:    0x000000fa
│     Vendor:             Intel
│     GUIDs:              809a0b93-8a12-5338-a571-ad5583acf896 ← CPUID\PRO_0&FAM_06&MOD_9E
│                         50a811ae-a8fd-5cd0-90f4-33583974b789 ← CPUID\PRO_0&FAM_06&MOD_9E&STP_D
│     Device Flags:       • Internal device
│   
├─Lexa XT [Radeon PRO WX 2100]:
│     Device ID:          ce4c74a5188d5b9cdb1e72ed32dad2d313c1c999
│     Summary:            D0910802 Lexa GLPRO A0 GDDR5 64bit 2GB 214e/300m
│     Current version:    015.050.002.001.010908
│     Vendor:             Advanced Micro Devices, Inc. [AMD/ATI] (PCI:0x1002, PCI:0x8086)
│     GUID:               493a106e-fd51-5c26-a920-7f08131885ac ← AMD\113-D0910802-101
│     Device Flags:       • Cryptographic hash verification is available
│   
├─PC SN730 NVMe WDC 256GB:
│     Device ID:          03281da317dccd2b18de2bd1cc70a782df40ed7e
│     Summary:            NVM Express solid state drive
│     Current version:    11170012
│     Vendor:             Sandisk Corp (NVME:0x15B7)
│     Serial Number:      20216F805556
│     GUIDs:              10215a6e-5eb4-5fe4-a3d0-1ff4b3295840 ← STORAGE-DELL-108613
│                         e3a1928f-2cb0-4b92-8526-9368d8c0c2d1
│     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
│   
├─SSD 850 EVO 500GB:
│     Device ID:          5dbeb140337f610d54913c0f43d15fdaa0eafb51
│     Summary:            ATA drive
│     Current version:    EMT02B6Q
│     Vendor:             Samsung (ATA:0x144D, OUI:002538)
│     Serial Number:      S2RANXAH147105D
│     GUIDs:              4f91c57f-0080-5f61-95b8-c54899cc39cb ← IDE\Samsung_SSD_850_EVO_500GB_______________EMT02B6Q
│                         086811eb-c412-5a0b-a319-7c37d3dd3e46 ← IDE\0Samsung_SSD_850_EVO_500GB_______________
│                         967c50bf-25a0-5394-b21d-5939967dade6 ← Samsung SSD 850 EVO 500GB
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│   
├─SSD 870 EVO 2TB:
│     Device ID:          e421b2fc248391f6fe3e55ddbb3c9043be068bd0
│     Summary:            ATA drive
│     Current version:    SVT01B6Q
│     Vendor:             Samsung (ATA:0x144D, OUI:002538)
│     Serial Number:      S6PNNJ0RB00580H
│     GUIDs:              8b62ca61-8b96-58f6-b1e9-281087a83995 ← IDE\Samsung_SSD_870_EVO_2TB_________________SVT01B6Q
│                         ea4b26cf-ffd9-5fb0-a207-c230a5d621e9 ← IDE\0Samsung_SSD_870_EVO_2TB_________________
│                         e0518d76-10bc-5c2d-9693-ee18a7e91881 ← Samsung SSD 870 EVO 2TB
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│   
├─SSD 870 EVO 2TB:
│     Device ID:          64ec4cd1e1c9565e79b00f4e7221b1c689b33e96
│     Summary:            ATA drive
│     Current version:    SVT01B6Q
│     Vendor:             Samsung (ATA:0x144D, OUI:002538)
│     Serial Number:      S6PNNJ0RB00555T
│     GUIDs:              8b62ca61-8b96-58f6-b1e9-281087a83995 ← IDE\Samsung_SSD_870_EVO_2TB_________________SVT01B6Q
│                         ea4b26cf-ffd9-5fb0-a207-c230a5d621e9 ← IDE\0Samsung_SSD_870_EVO_2TB_________________
│                         e0518d76-10bc-5c2d-9693-ee18a7e91881 ← Samsung SSD 870 EVO 2TB
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device is usable for the duration of the update
│   
├─System Firmware:
│ │   Device ID:          ffcb7fc2e5d13bb0d48b3d616881c5ba76604ea2
│ │   Summary:            UEFI System Resource Table device (updated via NVRAM)
│ │   Current version:    2.25.0
│ │   Minimum Version:    2.25.0
│ │   Vendor:             Dell (DMI:Dell Inc.)
│ │   Update State:       Success
│ │   GUID:               c0745fac-f5a5-46c9-b716-3cc5781e876e
│ │   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
│ │   Device Requests:    • Message
│ │ 
│ ├─AMT [unprovisioned]:
│ │     Device ID:        8d5470e73fd9a31eaa460b2b6aea95483fe3f14c
│ │     Summary:          Hardware and firmware technology for remote out-of-band management
│ │     Current version:  12.0.93.2331
│ │     Bootloader Version:12.0.93.2331
│ │     Vendor:           Intel Corporation (MEI:0x8086)
│ │     GUIDs:            12f80028-b4b7-4b2d-aca8-46e0ff65814c
│ │                       fa9a959e-9b8d-521e-9353-1c475d09e2de ← MEI\VEN_8086&DEV_A360
│ │                       960f4eed-bccb-5729-b2b2-8fc6ad83d4e8 ← MEI\VEN_8086&DEV_A360&SUBSYS_10280871
│ │     Device Flags:     • Internal device
│ │   
│ └─UEFI dbx:
│       Device ID:        362301da643102b9f38477387e2193e57abaa590
│       Summary:          UEFI revocation database
│       Current version:  371
│       Minimum Version:  371
│       Vendor:           UEFI:Linux Foundation
│       Install Duration: 1 second
│       GUIDs:            4a6cd2cb-8741-5257-9d1f-89a275dacca7 ← UEFI\CRT_E28D59CA489BD2AD580F2EA5D62D6A29BB9C02AE5A818434A37DA7FC11DFF9E9&ARCH_X64
│                         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:    7.2.0.2
│     Vendor:             Nuvoton Technology (TPM:NTC)
│     GUIDs:              fac1c8f3-73c8-5cd6-8330-07a3690b5140 ← TPM\VEN_NTC&DEV_0000
│                         bdb182b9-7533-5c43-b775-0c8327246042 ← TPM\VEN_NTC&MOD_NPCT75x;rls
│                         e9ccc1dc-960a-5e09-afe9-e59a904b776d ← TPM\VEN_NTC&DEV_0000&VER_2.0
│                         31c399b3-9c72-58ce-8fc3-489e76ab1e35 ← TPM\VEN_NTC&MOD_NPCT75x;rls&VER_2.0
│                         6ed025d4-7c75-59de-ab55-53191b2657e0 ← 0871-2.0
│     Device Flags:       • Internal device
│                         • Updatable
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device can recover flash failures
│                         • Full disk encryption secrets may be invalidated when updating
│                         • Signed Payload
│   
├─UEFI Platform Key:
│     Device ID:          6924110cde4fa051bfdc600a60620dc7aa9d3c6a
│     Summary:            Dell Inc. Platform Key
│     Vendor:             Dell Inc.
│     GUID:               5f7cc4ea-9f7a-5c5f-b535-dfbcc73f5ba6 ← UEFI\CRT_2493B118EABD632FD3BA49C333A8329B1982E872
│   
└─Unifying Receiver:
      Device ID:          fb1a5fd6e7d8cbf5d5a2ba7df68aee106ce41027
      Summary:            Miniaturised USB wireless receiver
      Current version:    RQR12.11_B0032
      Bootloader Version: BOT01.04_B0016
      Vendor:             Logitech, Inc. (HIDRAW:0x046D, USB:0x046D)
      Install Duration:   30 seconds
      GUIDs:              9d131a0c-a606-580f-8eda-80587250b8d6
                          279ed287-3607-549e-bacc-f873bb9838c4 ← HIDRAW\VEN_046D&DEV_C52B
      Device Flags:       • Updatable
                          • Supported on remote server
                          • Signed Payload

Additional questions

Operating system and version: Fedora Linux 39 and Fedora Linux 40
Have you tried rebooting? Yes
Is this a regression? Yes. The system has done multiple updates for 2 years and started reporting this recently

The text was updated successfully, but these errors were encountered:

hughsie · 2024-05-29T20:04:03Z

I'm wondering if it's this perhaps? b42ad1d -- would a COPR build be okay for testing?

hughsie · 2024-05-29T20:14:27Z

If so, there's a new build in https://copr.fedorainfracloud.org/coprs/rhughes/fwupd/ available in a few minutes.

smooge · 2024-05-29T20:37:54Z

Doesn't seem to fix it.. what can I do to give you more info?

Decompressing…           [                                       ] Less than one minute remaining…
partition kind required
[root@xenadu ~]# rpm -q fwupd
fwupd-1.9.21-0.1129.20240529git.fc40.x86_64

superm1 · 2024-05-29T20:40:23Z

sudo fwupdtool esp-list -v

And

udisksctl dump

smooge · 2024-05-29T20:49:56Z

The fwupdtool output (I chose to look at /boot/efi partition at the choice)
fwupd-20240529.txt
The udisk info
udisk-20240529.txt

superm1 · 2024-05-29T20:55:01Z

Looks like md127 is xfs. Same kind of problem we saw with btrfs. I guess time for us to switch to an allow list.

A user has reported an md array that is an xfs kind that with the wrong partition table flags. Explicitly only allow vfat and ntfs for ESPs. Fixes: b42ad1d ("trivial: catch miscategorized ESP partitions") Fixes #7298

smooge · 2024-05-29T21:09:11Z

yeah. I went with / as xfs because it was installed from Fedora Server. The EFI partition is not on a raid partition because I only had 1 nvme in the system at the time. I can run an updated rpm when ready

A user has reported an md array that is an xfs kind that with the wrong partition table flags. Explicitly only allow vfat and ntfs for ESPs. Fixes: b42ad1d ("trivial: catch miscategorized ESP partitions") Fixes #7298

superm1 · 2024-05-29T21:12:11Z

IMO - Something is totally wrong with the Fedora installer that it's making partitions of kind c12a7328-f81f-11d2-ba4b-00a0c93ec93b. Please also raise a bug against the installer and link back here.

We can add a workaround in fwupd, but who knows what else breaks from this.

smooge · 2024-05-29T21:55:12Z

I wonder if I did something odd when installing the system, but I just checked another Fedora 38 system which I did a straight install on and it is also Type: c12a7328-f81f-11d2-ba4b-00a0c93ec93b

OK searching on that string gave me from 2017 storaged-project/blivet#538 which says that is the expected partition type

smooge · 2024-05-29T21:56:48Z

but I am swimming way outside of my expertise so not sure where this bug would need to be or what type is expected.

A user has reported an md array that is an xfs kind that with the wrong partition table flags. Explicitly only allow vfat for ESPs. Fixes: b42ad1d ("trivial: catch miscategorized ESP partitions") Fixes #7298

superm1 · 2024-05-29T23:09:21Z

Yeah that's the expected partition type for an ESP but if you look at the logs you shared from fwupdtool you can see your MD partition was marked as that. Which isn't expected for fwupd.

smooge · 2024-05-29T23:20:19Z

That is weird. Looking at the udisk.. it isn't labeled at all but looking at the fwupd I see it thinks it is two different partition types:

20:46:30.043 FuVolume             Looking for volumes of type c12a7328-f81f-11d2-ba4b-00a0c93ec93b
20:46:30.046 FuVolume             device /org/freedesktop/UDisks2/block_devices/md127, type: c12a7328-f81f-11d2-ba4b-00a0c93ec93b, internal: 1, fs: xfs
...
20:46:30.065 FuVolume             Looking for volumes of type ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
20:46:30.068 FuVolume             device /org/freedesktop/UDisks2/block_devices/md127, type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7, internal: 1, fs: xfs

Can it be labeled with 2 different types? Or is there something else going on

superm1 · 2024-05-29T23:21:35Z

Oh good point! Let me dig in more.

superm1 · 2024-05-30T00:48:06Z

I think it's a side effect of 7c1df3d.

superm1 · 2024-05-30T01:34:11Z

I added an extra commit to the PR to help clarify that. It looks like it's not an installer bug; it's our own doing in that we tried to help support people who put EFI partition on RAID 1 arrays that caused all of this.

A user has reported an md array that is an xfs kind that with the wrong partition table flags. Explicitly only allow vfat for ESPs. Fixes: b42ad1d ("trivial: catch miscategorized ESP partitions") Fixes #7298

smooge · 2024-05-30T12:53:35Z

thanks.. sometimes our past helpful selves are future selfs worst enemy 😆

A user has reported an md array that is an xfs kind that with the wrong partition table flags. Explicitly only allow vfat for ESPs. Fixes: b42ad1d ("trivial: catch miscategorized ESP partitions") Fixes #7298 (cherry picked from commit f33dd43)

hughsie · 2024-05-30T14:59:06Z

There should be a new build in the COPR now.

smooge · 2024-05-31T13:23:35Z

Sadly.. it doesn't seem to have fixed the issue:

Perform operation? [Y|n]: Y
Decompressing…           [                                       ]
partition kind required
[root@xenadu ~]# fwupdmgr --version
compile   org.freedesktop.fwupd         1.9.21
compile   com.hughsie.libxmlb           0.3.20
compile   org.freedesktop.Passim        0.1.7
compile   com.hughsie.libjcat           0.2.1
runtime   org.freedesktop.fwupd-efi     1.6
compile   org.freedesktop.gusb          0.4.9
runtime   com.hughsie.libxmlb           0.3.20
runtime   org.freedesktop.Passim        0.1.7
runtime   org.freedesktop.gusb          0.4.9
runtime   com.hughsie.libjcat           0.2.1
runtime   org.kernel                    6.8.10-300.fc40.x86_64
runtime   org.freedesktop.fwupd         1.9.21
[root@xenadu ~]# rpm -q fwupd
fwupd-1.9.21-0.1130.20240530git.fc40.x86_64

smooge · 2024-05-31T13:32:40Z

Looking at the output of the newer fwupdtool I get

[root@xenadu ~]# fwupdtool --version
Loading…                 [************************************** ]
compile   org.freedesktop.fwupd         1.9.21
compile   com.hughsie.libxmlb           0.3.20
compile   org.freedesktop.Passim        0.1.7
compile   com.hughsie.libjcat           0.2.1
runtime   org.freedesktop.fwupd-efi     1.6
runtime   org.freedesktop.Passim        0.1.7
compile   org.freedesktop.gusb          0.4.9
runtime   com.hughsie.libxmlb           0.3.20
runtime   com.hughsie.libjcat           0.2.1
runtime   org.freedesktop.gusb          0.4.9
runtime   org.kernel                    6.8.10-300.fc40.x86_64
runtime   org.freedesktop.fwupd         1.9.21

[root@xenadu ~]# fwupdtool esp-list -v
...
13:29:24.568 FuVolume             Looking for volumes of type c12a7328-f81f-11d2-ba4b-00a0c93ec93b
13:29:24.570 FuVolume             device /org/freedesktop/UDisks2/block_devices/md127, type: c12a7328-f81f-11d2-ba4b-00a0c93ec93b, internal: 1, fs: xfs
...
13:29:24.590 FuVolume             Looking for volumes of type ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
13:29:24.592 FuVolume             device /org/freedesktop/UDisks2/block_devices/md127, type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7, internal: 1, fs: xfs
13:29:24.594 FuVolume             device /org/freedesktop/UDisks2/block_devices/nvme0n1p2, type: 0fc63daf-8483-4772-8e79-3d69d8477de4, internal: 1, fs: xfs

superm1 · 2024-05-31T13:57:06Z

@hughsie can you please double check the commits you included in that test build?

I notice this:

13:29:24.570 FuVolume device /org/freedesktop/UDisks2/block_devices/md127, type: c12a7328-f81f-11d2-ba4b-00a0c93ec93b, internal: 1, fs: xfs

But with those commits we should have seen the word mdraid. This is from the udisks output:

MDRaid: '/org/freedesktop/UDisks2/mdraid/75a7ac19_ee9aa0ce_2978bd10_6272211d'

smooge added the bug label May 29, 2024

superm1 mentioned this issue May 29, 2024

trivial: switch to allowlist for partition kinds #7299

Merged

4 tasks

superm1 closed this as completed in #7299 May 30, 2024

superm1 closed this as completed in f33dd43 May 30, 2024

superm1 reopened this May 31, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fedora 40 fwupdmgr: partition kind required #7298

Fedora 40 fwupdmgr: partition kind required #7298

smooge commented May 29, 2024

hughsie commented May 29, 2024

hughsie commented May 29, 2024

smooge commented May 29, 2024

superm1 commented May 29, 2024

smooge commented May 29, 2024

superm1 commented May 29, 2024

smooge commented May 29, 2024

superm1 commented May 29, 2024

smooge commented May 29, 2024

smooge commented May 29, 2024

superm1 commented May 29, 2024

smooge commented May 29, 2024

superm1 commented May 29, 2024

superm1 commented May 30, 2024

superm1 commented May 30, 2024

smooge commented May 30, 2024

hughsie commented May 30, 2024

smooge commented May 31, 2024

smooge commented May 31, 2024

superm1 commented May 31, 2024

Fedora 40 fwupdmgr: partition kind required #7298

Fedora 40 fwupdmgr: partition kind required #7298

Comments

smooge commented May 29, 2024

hughsie commented May 29, 2024

hughsie commented May 29, 2024

smooge commented May 29, 2024

superm1 commented May 29, 2024

smooge commented May 29, 2024

superm1 commented May 29, 2024

smooge commented May 29, 2024

superm1 commented May 29, 2024

smooge commented May 29, 2024

smooge commented May 29, 2024

superm1 commented May 29, 2024

smooge commented May 29, 2024

superm1 commented May 29, 2024

superm1 commented May 30, 2024

superm1 commented May 30, 2024

smooge commented May 30, 2024

hughsie commented May 30, 2024

smooge commented May 31, 2024

smooge commented May 31, 2024

superm1 commented May 31, 2024