You are not logged in.
Today I tried to run fwupdmgr and got the error:
Unable to determine EFI system partition location, See https://github.com/hughsie/fwupd/wiki/Determining-EFI-system-partition-locationWhich was baffeling, because, the EFI partition was mounted unter /boot, formatted as FAT32 (vfat) marked as ef00 and was not corrupt according to fsck.
After half an hour of try-and-error I found out, that fwupdmgr does not recognize the partition when mounted at /boot.
I could. however run it by unmounting it, creating /boot/efi and mounting it there.
In case you wonder, here's the journal:
-- Logs begin at Tue 2019-04-02 00:06:31 CEST, end at Tue 2019-09-03 08:38:10 CEST. --
Sep 03 08:12:17 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:12:17 envy fwupd[14558]: 06:12:17:0906 FuPluginUefi Unable to determine EFI system partition location, See https://github.com/hughsie/fwupd/wiki/Determining-EFI-system-partition-location
Sep 03 08:12:17 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:14:28 envy systemd[1]: Stopping Firmware update daemon...
Sep 03 08:14:28 envy fwupd[14558]: 06:14:28:0569 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:14:28 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:14:28 envy systemd[1]: Stopped Firmware update daemon.
Sep 03 08:14:28 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:14:28 envy fwupd[26106]: 06:14:28:0675 FuPluginUefi Unable to determine EFI system partition location, See https://github.com/hughsie/fwupd/wiki/Determining-EFI-system-partition-location
Sep 03 08:14:28 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:17:55 envy systemd[1]: Stopping Firmware update daemon...
Sep 03 08:17:55 envy fwupd[26106]: 06:17:55:0886 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:17:55 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:17:55 envy systemd[1]: Stopped Firmware update daemon.
Sep 03 08:17:55 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:17:55 envy fwupd[19292]: 06:17:55:0975 FuPluginUefi Unable to determine EFI system partition location, See https://github.com/hughsie/fwupd/wiki/Determining-EFI-system-partition-location
Sep 03 08:17:56 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:18:51 envy systemd[1]: Stopping Firmware update daemon...
Sep 03 08:18:51 envy fwupd[19292]: 06:18:51:0515 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:18:51 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:18:51 envy systemd[1]: Stopped Firmware update daemon.
Sep 03 08:18:51 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:18:51 envy fwupd[19413]: 06:18:51:0595 FuPluginUefi Unable to determine EFI system partition location, See https://github.com/hughsie/fwupd/wiki/Determining-EFI-system-partition-location
Sep 03 08:18:51 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:22:11 envy systemd[1]: Stopping Firmware update daemon...
Sep 03 08:22:11 envy fwupd[19413]: 06:22:11:0294 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:22:11 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:22:11 envy systemd[1]: Stopped Firmware update daemon.
Sep 03 08:22:11 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:22:11 envy fwupd[21672]: 06:22:11:0385 FuPluginUefi Unable to determine EFI system partition location, See https://github.com/hughsie/fwupd/wiki/Determining-EFI-system-partition-location
Sep 03 08:22:11 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:23:37 envy systemd[1]: Stopping Firmware update daemon...
Sep 03 08:23:37 envy fwupd[21672]: 06:23:37:0934 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:23:37 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:23:37 envy systemd[1]: Stopped Firmware update daemon.
Sep 03 08:23:37 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:23:38 envy fwupd[21822]: 06:23:38:0028 FuPluginUefi Unable to determine EFI system partition location, See https://github.com/hughsie/fwupd/wiki/Determining-EFI-system-partition-location
Sep 03 08:23:38 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:28:47 envy fwupd[21822]: 06:28:47:0732 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:28:47 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:30:26 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:30:26 envy fwupd[22484]: 06:30:26:0451 FuPluginUefi Unable to determine EFI system partition location, See https://github.com/hughsie/fwupd/wiki/Determining-EFI-system-partition-location
Sep 03 08:30:26 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:33:01 envy systemd[1]: Stopping Firmware update daemon...
Sep 03 08:33:01 envy fwupd[22484]: 06:33:01:0866 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:33:01 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:33:01 envy systemd[1]: Stopped Firmware update daemon.
Sep 03 08:33:01 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:33:01 envy fwupd[22758]: 06:33:01:0953 FuPluginUefi Unable to determine EFI system partition location, See https://github.com/hughsie/fwupd/wiki/Determining-EFI-system-partition-location
Sep 03 08:33:01 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:34:38 envy systemd[1]: Stopping Firmware update daemon...
Sep 03 08:34:38 envy fwupd[22758]: 06:34:38:0059 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:34:38 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:34:38 envy systemd[1]: Stopped Firmware update daemon.
Sep 03 08:34:38 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:34:38 envy fwupd[22882]: 06:34:38:0147 FuPluginUefi Unable to determine EFI system partition location, See https://github.com/hughsie/fwupd/wiki/Determining-EFI-system-partition-location
Sep 03 08:34:38 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:35:29 envy systemd[1]: Stopping Firmware update daemon...
Sep 03 08:35:29 envy fwupd[22882]: 06:35:29:0223 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:35:29 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:35:29 envy systemd[1]: Stopped Firmware update daemon.
Sep 03 08:35:29 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:35:29 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:37:07 envy systemd[1]: Stopping Firmware update daemon...
Sep 03 08:37:07 envy fwupd[22929]: 06:37:07:0300 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:37:07 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:37:07 envy systemd[1]: Stopped Firmware update daemon.
Sep 03 08:37:07 envy systemd[1]: Starting Firmware update daemon...
Sep 03 08:37:07 envy systemd[1]: Started Firmware update daemon.
Sep 03 08:37:17 envy systemd[1]: Stopping Firmware update daemon...
Sep 03 08:37:17 envy fwupd[23113]: 06:37:17:0592 GLib g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Sep 03 08:37:17 envy systemd[1]: fwupd.service: Succeeded.
Sep 03 08:37:17 envy systemd[1]: Stopped Firmware update daemon.This, however is a bad solution for me, since I use EFISTUB to boot the kernel via EFI directly.
Thus, I need the kernel and initramfs on the EFI partition (and not much else), so mounting the EFI partition to /boot/efi will require me to manually copy the kernel image, initramfs and microcode image to /boot/efi after each upgrade.
While this is certainly possible via pacman hooks, it seems like an unnecessary hassle to me.
Is there a way to tell fwupdmgr to look for the EFI partition under /boot?
Last edited by schard (2019-09-03 20:06:36)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
fwupdmgr does not recognize the partition when mounted at /boot.
I could. however run it by unmounting it, creating /boot/efi and mounting it there.
Does directory /EFI exist on the EFI partition? https://github.com/fwupd/fwupd/blob/c73 … #L313-L314
/* /boot is a special case because systemd sandboxing marks
* it read-only, but we need to write to /boot/EFI--
saint_abroad
Offline
No. It did not. After creating the directory and restarting fwupd.service the error message is gone.
Unfortunately I cannot test, whether it works as there are currently no updates available.
Inofficial first vice president of the Rust Evangelism Strike Force
Offline