Fwupdmgr - failed to run update on reboot

Could someone kindly help me resolve an issue where fwupdmgr is failing to run update on reboot.

I think it might be something to do with the way my EFI system partition is set up.
The machine used to be dual boot Windows/Manjaro and at some point I removed the Windows OS and I fear I may not have cleaned up properly.

What I believe is the EFI system partition is showing as type “Microsoft basic data”

$ sudo fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: Sabrent
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: 2D75EAFC-0484-5F47-B235-C4D0C28B6C5E

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048    1050623    1048576   512M Microsoft basic data
/dev/nvme0n1p2    1050624   42993663   41943040    20G Linux filesystem
/dev/nvme0n1p3   42993664   74450943   31457280    15G Linux filesystem
/dev/nvme0n1p4 1968314368 2000408575   32094208  15.3G Linux swap
/dev/nvme0n1p5   74450944 1968314367 1893863424 903.1G Linux filesystem

Why not using GParted to change the flags for /dev/nvme0n1p1 to only

esp, boot

then?

Thank you.
I’m waaaay out of my depth here. I have no idea how to achieve what you have suggested or what the implications are.

If you don’t intend to use the GUI program GParted you can also do it via command line:

sudo parted /dev/nvme0n1 set 1 esp on

Excellent! All sorted now and all firmware updated.
Thank you so very much for your help.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.