[solved] fwupd failure: what's the best thing to do now?

cfr · 2022-10-16 04:21:52

I just ran

fwupdmgr get-devices
fwupdmgr refresh
fwupdmgr get-updates
fwupdmgr update

Two updates were to be installed when the laptop rebooted. The firmware tried to update but the process ended with an error. This flashed on the screen pretty fast and I'm not sure exactly what it said. It had something to do with a shell, possibly a shell command. Then the laptop rebooted as normal.

On examining the situation with get-history, it seems that the Intel Management Engine firmware was successfully updated, but the System Firmware update failed. This is currently at version 0.1.45 with 0.1.46 the new version. All it says about the error is:

Update Error:       failed to run update on reboot

Here's the full output for this device:

─System Firmware
  │   Device ID:          a45df35ac0e948ee180fe216a5f703f32dda163f
  │   Previous version:   0.1.45
  │   Update State:       Failed
  │   Update Error:       failed to run update on reboot
  │   Last modified:      2022-10-16 03:58
  │   GUID:               14cc970e-c105-4eba-a704-448dde9de64d
  │   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
  │ 
  └─ThinkPad X270:
        New version:      0.1.46
        Remote ID:        lvfs
        Release ID:       14296
        Summary:          Lenovo ThinkPad X270 System Firmware
        Licence:          Proprietary
        Size:             9.4 MB
        Created:          2016-07-08
        Urgency:          Critical
        Vendor:           Lenovo
        Update Message:   Do not turn off your computer or remove the AC adapter while the update is in progress.
        Release Flags:    • Is upgrade
        Description:      
        This stable release fixes the following issues:
        
        • Updated includes a security fix.
        
        Do not turn off your computer or remove the AC adapter while the update is in progress.

I take it the update file is /boot/EFI/arch/fw/fwupd-14cc970e-c105-4eba-a704-448dde9de64d.cap as that matches the GUID in the output, while the other .cap is the one which succeeded.

What is recommended at this point? Should I delete the files from the ESP and rerun the update, hoping that it may succeed if it is applied on its own? Or should I quit while I've still got a laptop and not a brick? Or ...?

Last edited by cfr (2022-10-16 22:37:00)

seth · 2022-10-16 07:18:16

You've seen https://wiki.archlinux.org/title/Fwupd#Troubleshooting ?

The firmware tried to update but the process ended with an error. This flashed on the screen pretty fast and I'm not sure exactly what it said.

If the errors show up on every reboot, record your monitor (phone, cam, (makeshift-)tripod, fastest framerate possible) - knowing the error will help a great deal with solving it

cfr · 2022-10-16 16:13:00

seth wrote:

You've seen https://wiki.archlinux.org/title/Fwupd#Troubleshooting ?

Yes, but I wasn't sure exactly what to do. Do I need to delete the files on the ESP and then rerun the update? I'm assuming I wouldn't need to specify the updates one-by-one as there's only one which didn't work? Or do I delete the one which worked?

seth · 2022-10-16 20:17:23

First ensure it's not

Possible cause: In BIOS settings changing the boot order must be allowed.

notably because of https://github.com/fwupd/fwupd/issues/1929

You can try to re-run the update, but unless the EFI partition is out of space, I don't think that'll do anything (and then you'd still be out of space)
If it's not the boot order lock, try to get the actual error message.

seth wrote:

knowing the error will help a great deal with solving it

cfr · 2022-10-16 20:38:07

It's definitely not the boot order lock because one of the two updates succeeded and the machine rebooted immediately into the fw updater. I didn't have to choose it from refind or anything like that.

I'll try deleting the files from the ESP and rerunning the update to get the error message.

EDIT: While doing the above, I was asked to submit a report, which I did. This yielded a 'known issue' message with a URL. The information there helped not at all, so I ploughed on. This time, the firmware updated successfully. (Maybe it just needed to be run on its own?) It also wiped out my boot menu entries. I know this happens, but I really don't get why it has to. How hard can it be to restore boot menu entries?

Last edited by cfr (2022-10-16 22:42:39)

Arch Linux

#1 2022-10-16 04:21:52

[solved] fwupd failure: what's the best thing to do now?

#2 2022-10-16 07:18:16

Re: [solved] fwupd failure: what's the best thing to do now?

#3 2022-10-16 16:13:00

Re: [solved] fwupd failure: what's the best thing to do now?

#4 2022-10-16 20:17:23

Re: [solved] fwupd failure: what's the best thing to do now?

#5 2022-10-16 20:38:07

Re: [solved] fwupd failure: what's the best thing to do now?

Board footer