Fail to reboot into Ubuntu after successful update #86

merlijn-sebrechts · 2017-10-22T13:34:31Z

I triggered the update with Gnome Software on Ubuntu 17.10. Gnome Software asked me to restart, I click restart. During boot, the update starts correctly, and succeeds. After it succeeds, the laptop boots back into fwupd, which fails with the following error:

found update fwupdate-49w03513-7afe-49a-9d03-89e5ba1da865-0
fwupdate: No updates to process. Called in error?
start_image() returned Invalid Parameter

After a few seconds, it shows another screen:

No bootable devices found.
Press F1 key to retry boot.
Press F2 key to reboot into setup.
Press F5 key to run onboard diagnostics.

Help, I've got this issue too and I can't boot!

I was able to workaround the issue by going into setup, general > Boot Sequence, and adding grub64.efi back as primary boot option.

Picture walkthrough:

When you see this message, press F2 to enter the UEFI/BIOS setup.

Once in the setup, go to general > Boot Sequence.

Click Add boot option.

Call the boot option "Ubuntu" and click the three dots behind "filename".

Choose the "grubx64.efi" file, click OK and add the boot option.

Now use the arrows to put the "Ubuntu" boot option to the top.

Save and exit, reboot and Ubuntu boots as normal!

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

superm1 · 2017-10-22T14:59:37Z

Can you please share more details about your machine? What model number? BIOS version you were at and version you were trying to upgrade to?

merlijn-sebrechts · 2017-10-22T16:13:13Z

Dell Latitude 5580, I was at 1.4.3 and upgraded to 1.6.4.

I've been trying to replicate this by downgrading and upgrading a few times, but I'm not able to replicate it anymore.

superm1 · 2017-10-23T13:47:10Z

Hmm interesting. to your first comment, a little more clarification:
When you say it starts successfully and succeeds, do you mean it flashed up to 1.6.4 and then didn't want to boot again? or do you mean that fwupdate opened and that error came up?

merlijn-sebrechts · 2017-10-23T13:56:33Z

It flashed to 1.6.4 and it didn't boot again. (well it booted into those two error messages)

superm1 · 2017-10-23T14:02:21Z

It sounds to me like you were missing a boot entry initially. Were you booting using the removable media path \efi\boot\bootx64.efi?

merlijn-sebrechts · 2017-10-23T16:02:10Z

I don't know. It was a standard Ubuntu 17.10 installation.

Note that this was not the first upgrade I performed. The first one succeeded without issues, so I don't think it's an installation issue.

I downgraded the firmware manually using a USB stick and Dell's builtin firmware update utility, in order to reproduce some issues with the fwupdate integration in the software center. It was the first upgrade after this downgrade that failed.

superm1 · 2017-10-23T17:20:59Z

Since this was with ubuntu 17.10, there's actually evidence logged into the journal log for fwupd. can you look through journalctl to see if you have the efibootmgr output from before the update was performed? It's been in fwupd 0.9.6 and later (17.10 has 0.9.7).

(Came from this commit: ) https://github.com/hughsie/fwupd/commit/f043f1f94b7f671e7e8d4fa3963a47e045d94f59

merlijn-sebrechts · 2017-10-24T07:27:55Z

No such luck, apparently Ubuntu 17.10 still doesn't enable persistent logs. Only the logs since last boot are visible. I configured persistent logs now, but that won't help much for this bug..

sudo journalctl --list-boots
 0 7318355f8d464ff7ae7d8f967466edd0 Tue 2017-10-24 09:11:37 CEST—Tue 2017-10-24 09:26:31 CEST

superm1 · 2017-10-24T17:22:53Z

Ah well darn.

gerobum · 2017-11-06T08:12:19Z

Is this topic closes ? Because I have the same issue. Yesterday, I answered "yes" to the "update manager" which ask to me if I would like to change my firmware. And this morning, unable to boot on my ubuntu
found update fwupdate-49w03513-7afe-49a-9d03-89e5ba1da865-0
fwupdate: No updates to process. Called in error?
start_image() returned Invalid Parameter

merlijn-sebrechts · 2017-11-06T09:53:09Z

@gerobum Do you have persistent logs on?

For reference,

The fwupd bug in the Ubuntu launchpad: https://bugs.launchpad.net/fwupd/+bug/1730343
The bug that persistent logs are disabled by default: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188

gerobum · 2017-11-06T14:02:31Z

@galgalesh I don't what do you by "persistent logs on". But I don't know what to do because I am unable to boot.

Have you fixed your problem ?

merlijn-sebrechts · 2017-11-06T14:22:48Z

@gerobum Oh, why didn't you say that earlier! I added a picture guide to my original message on the top of this thread.

After fixing your installation, can you show the output of

 sudo journalctl --list-boots

to figure out if you have persistent logs enabled?

gerobum · 2017-11-06T14:42:44Z

@galgalesh Ok thanks. But I tried to do the same. Unfortunatly I have now directly this
No bootable devices found.
Press F1 key to retry boot.
Press F2 key to run onboard diagnostics.
Press F5 key to run onboard diagnostics.

merlijn-sebrechts · 2017-11-06T14:46:27Z

@gerobum can you show a picture of the "boot sequence screen"? (the last picture in my tutorial)

gerobum · 2017-11-06T15:06:01Z

Thanks a lot. It works now.
When I type sudo journalctl --list-boots, I have something like that
0 f4998...ae3b2f6 Mon 2017-11-06 14:57:59 CET—Mon 2017-11-06 1
But I didn't know what doest it mean.

Anyway. Thanks.

merlijn-sebrechts · 2017-11-06T15:09:14Z

That means the systemd journal (the log collector) only contains logs since the last boot (which happened on Mon 2017-11-06 14:57:59).

Thus, we cannot look at the logs from when fwupd failed, because those logs were not saved.

gerobum · 2017-11-06T15:11:42Z

I see.

seb128 · 2017-11-06T21:38:03Z

the journal isn't persistant but the logs are stored in /var/log/syslog as well no? that should have records from previous boot (it's being rotated so could be .1)

jeremybmerrill · 2017-11-17T15:33:59Z

Chiming in to say that I had this same bug occur on my Dell XPS 13 (2016), but didn't have persistent logs on. However @galgalesh, your guide at the top of the thread worked perfectly to fix my issue, so thank you!

superm1 · 2017-11-17T15:37:52Z

@jeremybmerrill were you on Ubuntu as well? We need someone to help to verify the SRU that has been filed.

jeremybmerrill · 2017-11-17T16:01:58Z

@superm1 Yes, Ubuntu 17.10. Happy to do what I can to help, just tell me what to do.

merlijn-sebrechts · 2017-11-17T16:05:33Z

@superm1 I think something went wrong, the patch is still not in proposed..

sudo apt-get install fwupdate-signed/artful-proposed
[sudo] password for merlijn: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Release ‘artful-proposed’ for ‘fwupdate-signed’ was not found

superm1 · 2017-11-17T16:08:15Z

@jeremybmerrill Yes so this is the public bug: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1730343
Can you follow the directions on installing the fwupdate-signed and fwupdate packages from proposed?

@galgalesh
Hmm, I see them in proposed according to: https://launchpad.net/ubuntu/+source/fwupdate and https://launchpad.net/ubuntu/+source/fwupdate-signed

Presumably you've already apt updated and have proposed activated?

jeremybmerrill · 2017-11-18T23:28:25Z

@superm1 Do you know if the bug is such that my system did update the firmware properly, but just didn't boot up correctly afterwards? Or did the system not update the firmware?

I enabled proposed, ran sudo apt-get install fwupdate/artful-proposed (and tried to run sudo apt-get install fwupdate-signed/artful-proposed, but it said E: Release 'artful-proposed' for 'fwupdate-signed' was not found -- same as @galgalesh ).

How do I run the update again, now that I have a new fwupdate?

superm1 · 2017-11-19T01:50:46Z

@jeremybmerrill yes that's the bug, it didn't boot up afterwards properly.

To confirm you have the latest package can you please run:
apt-cache policy fwupdate-signed

IIRC artful-proposed isn't enabled by default, you have to modify /etc/apt/sources.list to do it.

After you confirm you have the new package, you can manually download the CAB file from LVFS for your system.

then run:

fwupdmgr install --allow-reinstall blah.cab

merlijn-sebrechts · 2017-11-19T19:48:30Z

@superm1

$ apt-cache policy fwupdate-signed
fwupdate-signed:
  Installed: (none)
  Candidate: 1.14+9-2
  Version table:
     1.14+9-2 500
        500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
        100 /var/lib/dpkg/status
$ apt-cache policy fwupdate
fwupdate:
  Installed: 9-2ubuntu0.17.10.1
  Candidate: 9-2ubuntu0.17.10.1
  Version table:
 *** 9-2ubuntu0.17.10.1 400
        400 http://us.archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     9-2 500
        500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

I uninstalled fwupdate-signed and installed fwupdate I suspect the "signed" is only relevant for secureboot?
I removed all boot options in my UEFI boot menu.
I rebooted and it boots into Ubuntu
I downloaded the firmware from here: https://fwupd.org/lvfs/devicelist (Are you aware that there are two entries for Latitude 5X80?)
I ran fwupdmgr install --allow-reinstall <filename>.cab and rebooted my machine.
fwupdate starts, updates, and reboots into Ubuntu.

So If your assessment of the cause of the bug is correct, then the bug is fixed.

However there is clearly something wrong with fwupdate-signed since it isn't visible for us in the artful-proposed repos as you can see in the output of the commands up top.

superm1 · 2017-11-19T22:35:27Z

Can you confirm the efibootmgr -v output after that list of steps you followed?

merlijn-sebrechts · 2017-11-20T08:30:36Z

$ efibootmgr -v
BootCurrent: 0002
Timeout: 2 seconds
BootOrder: 0002,0001
Boot0000* Windows Boot Manager	HD(1,GPT,4076bdbf-fe0f-4db3-85f6-2cab5d6263a3,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* UEFI: SanDisk X400 M.2 2280 512GB, Partition 1	HD(1,GPT,50def640-b2e4-47e9-9456-a8755c5b6cd4,0x800,0x100000)/File(EFI\boot\bootx64.efi)..BO
Boot0002* ubuntu	HD(1,GPT,50def640-b2e4-47e9-9456-a8755c5b6cd4,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)

I am surprised that windows boot manager shows up here, I don't run Windows..

4l1fe · 2017-11-20T14:08:07Z

@galgalesh bro, you have saved my life by your guide!

for dell xps on Ubuntu 16.04 there is one more step is to disable secure booting in BIOS because of such problem

superm1 · 2018-01-02T21:08:16Z

@KoenDG thanks for looking. Yes they're two separate packages due to how the signing works in Ubuntu.

You can download the latest CAB file for your system and install with fwupdmgr install <blah.cab> --allow-reinstall
If you can succesfully boot after installing that way then I would deem it a successful test (and please mark it on the Launchpad bug too).

KoenDG · 2018-01-02T21:50:46Z

@superm1 I can't get it to work.

I had to look for the cab file in my download cache, it was still there. The Dell website isn't offering it for download anywhere.

I did the command as instructed, got the output saying an upgrade was scheduled.

I tried both shutdown -r and going to the Ubuntu Software menu and doing the upgrade&restart from there.

I tried it with and without --allow-reinstall. I tried it with the cab file as a normal file and as an executable file.

In all instances, a regular reboot happens and nothing else.

dmidecode still says the BIOS is on version 1.7.5, dating 11/12/2017

Not sure why it's not picking up the upgrade.

superm1 · 2018-01-02T22:01:25Z

The CAB file comes from LVFS not from the Dell site, so that's why you couldn't find it there. It's good you had it in your cache though.

After you have scheduled it but before rebooting, can you please share the output of:

# efibootmgr -v

In dmidecode output the date should stay the same even if you were successful. It's the date the BIOS was built not the date that it was flashed. To query the date of the last flash you would have to look elsewhere.

KoenDG · 2018-01-02T22:08:05Z

@superm1 As requested:

# efibootmgr -v
BootNext: 0008
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0000,0008
Boot0000  Linux-Firmware-Updater \fwupx64.efi	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.x.6.4...e.f.i...
Boot0001* Diskette Drive	BBS(Floppy,Diskette Drive,0x0)..BO
Boot0002* ubuntu	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(\EFI\ubuntu\shimx64.efi)
Boot0003* USB Storage Device	BBS(USB,USB Storage Device,0x0)..BO
Boot0004* CD/DVD/CD-RW Drive	BBS(CDROM,CD/DVD/CD-RW Drive,0x0)..BO
Boot0005* Onboard NIC	BBS(Network,IBA CL Slot 00FE v0109,0x0)..BO
Boot0006* M.2 SATA SSD	BBS(HD,P0: Micron 1100 SATA 256GB,0x0)..BO
Boot0007* UEFI: Micron 1100 SATA 256GB, Partition 1	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(EFI\boot\bootx64.efi)..BO
Boot0008* Linux-Firmware-Updater \fwupx64.efi	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.x.6.4...e.f.i...

superm1 · 2018-01-03T03:17:02Z

Hmm, looks like it did the correct thing to me. And after that you don't see the fwupx64.efi quick between post and GRUB coming up pop up?
Do you have secure boot enabled? Can you confirm the checksums of /boot/efi/efi/ubuntu/fwupx64.efi?

KoenDG · 2018-01-03T09:24:12Z

Nothing comes up. Secure boot is disabled

MD5: 1a68d9b11532c19640b4a2eeeee4fd80 /boot/efi/efi/ubuntu/fwupx64.efi
SHA256: 52d202634650ae9196a9bcf79c6a689f15feb82be4f4cc5462a0dc1aca64456e /boot/efi/efi/ubuntu/fwupx64.efi

Could this be related to the fact that I had to use the fix given in the top post here, when this happened to me? So I selected the ubuntu shimx64.efi and that's still selected?

superm1 · 2018-01-03T16:21:47Z

That is the correct checksum. Something that stick out is that you have two different Linux Firmware Updater entries. I wonder if that's throwing something off.

Can you please try to delete both with efibootmgr and try again?

KoenDG · 2018-01-03T20:37:06Z

@superm1 I executed sudo efibootmgr -D which deletes duplicates.

Attempt the update now gave me a new message: Cannot install update when not on AC power.

So that's progress. I don't have my AC adapter with me so it'll have to wait until tomorrow.

superm1 · 2018-01-03T20:42:47Z

@KoenDG That message came from the Dell flash screen or from fwupd? If it's from the Dell flash screen that's great news and it means that the duplicates were the root cause.

KoenDG · 2018-01-03T20:48:57Z

@superm1 Sorry, it's from fwupdmgr. The flash screen just saying "Bootin in insecure mode".

... .cache/gnome-software/3.20/firmware/4a89bbb6bd769fdfc315c37db55a74b8e7f25768-firmware.Latitude_5x80_Precision_3520_1.8.1H.wu.cab --allow-reinstall
 * Decompressing firmware
Retrying as an offline update...
 * Idle
 * Decompressing firmware
Cannot install update when not on AC power

superm1 · 2018-01-03T20:52:48Z

Ah OK, so then it doesn't tell anything interesting yet. I guess we'll see tomorrow then.

KoenDG · 2018-01-04T16:15:58Z

@superm1 Just tried with the AC plugged in, nothing happens.

Tried it with the 1.7.5 and the 1.8.1, restart from commandline, restart from the "Ubuntu Software" GUI, nothing happens.

It just goes by the DELL logo, I see "Booting in insecure mode" in the top left and then it starts normally.

superm1 · 2018-01-04T20:27:10Z

Ok so that's definitely a failure then. I'll need to get a 16.04 box setup to dig into what's going wrong.

KoenDG · 2018-01-04T21:14:56Z

@superm1 Could this have something to do with having followed the guide at the top of this thread? Do I need to revert that last step?

superm1 · 2018-01-04T21:41:51Z

@KoenDG I don't think it should have, it looked like in your above efibootmgr output that you had not followed the guide (you picked shimx64.efi not grubx64.efi)

Boot0002* ubuntu	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(\EFI\ubuntu\shimx64.efi)

KoenDG · 2018-01-04T21:51:43Z

@superm1 It appears that after I did efibootmgr -D it removed the duplicate but left the BootNext on a non-existing entry.

# efibootmgr -v
BootNext: 0008
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0000
Boot0000  Linux-Firmware-Updater \fwupx64.efi	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.x.6.4...e.f.i...
Boot0001* Diskette Drive	BBS(Floppy,Diskette Drive,0x0)..BO
Boot0002* ubuntu	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(\EFI\ubuntu\shimx64.efi)
Boot0003* USB Storage Device	BBS(USB,USB Storage Device,0x0)..BO
Boot0004* CD/DVD/CD-RW Drive	BBS(CDROM,CD/DVD/CD-RW Drive,0x0)..BO
Boot0005* Onboard NIC	BBS(Network,IBA CL Slot 00FE v0109,0x0)..BO
Boot0006* M.2 SATA SSD	BBS(HD,P0: Micron 1100 SATA 256GB,0x0)..BO
Boot0007* UEFI: Micron 1100 SATA 256GB, Partition 1	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(EFI\boot\bootx64.efi)..BO

superm1 · 2018-01-04T22:23:37Z

@KoenDG
I still see a stray entry there, can you please manually delete the 0000 entry and the BootNext entry then?

When you run the update it will create a new entry for you and set it appropriately.

KoenDG · 2018-01-04T22:33:23Z

Alright, I did the cleanup as follow:

BootNext: 0008
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0000
Boot0000  Linux-Firmware-Updater \fwupx64.efi   HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.x.6.4...e.f.i...
Boot0001* Diskette Drive    BBS(Floppy,Diskette Drive,0x0)..BO
Boot0002* ubuntu    HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(\EFI\ubuntu\shimx64.efi)
Boot0003* USB Storage Device    BBS(USB,USB Storage Device,0x0)..BO
Boot0004* CD/DVD/CD-RW Drive    BBS(CDROM,CD/DVD/CD-RW Drive,0x0)..BO
Boot0005* Onboard NIC   BBS(Network,IBA CL Slot 00FE v0109,0x0)..BO
Boot0006* M.2 SATA SSD  BBS(HD,P0: Micron 1100 SATA 256GB,0x0)..BO
Boot0007* UEFI: Micron 1100 SATA 256GB, Partition 1 HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(EFI\boot\bootx64.efi)..BO

# efibootmgr -b 0 -B
BootNext: 0008
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002
Boot0001* Diskette Drive
Boot0002* ubuntu
Boot0003* USB Storage Device
Boot0004* CD/DVD/CD-RW Drive
Boot0005* Onboard NIC
Boot0006* M.2 SATA SSD
Boot0007* UEFI: Micron 1100 SATA 256GB, Partition 1

# efibootmgr -N
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002
Boot0001* Diskette Drive
Boot0002* ubuntu
Boot0003* USB Storage Device
Boot0004* CD/DVD/CD-RW Drive
Boot0005* Onboard NIC
Boot0006* M.2 SATA SSD
Boot0007* UEFI: Micron 1100 SATA 256GB, Partition 1

After setting the reinstall for 1.7.5, it did indeed create the new option:

BootNext: 0000
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0000
Boot0000* Linux-Firmware-Updater \fwupx64.efi	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.x.6.4...e.f.i...
Boot0001* Diskette Drive	BBS(Floppy,Diskette Drive,0x0)..BO
Boot0002* ubuntu	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(\EFI\ubuntu\shimx64.efi)
Boot0003* USB Storage Device	BBS(USB,USB Storage Device,0x0)..BO
Boot0004* CD/DVD/CD-RW Drive	BBS(CDROM,CD/DVD/CD-RW Drive,0x0)..BO
Boot0005* Onboard NIC	BBS(Network,IBA CL Slot 00FE v0109,0x0)..BO
Boot0006* M.2 SATA SSD	BBS(HD,P0: Micron 1100 SATA 256GB,0x0)..BO
Boot0007* UEFI: Micron 1100 SATA 256GB, Partition 1	HD(1,GPT,9b1d146c-b8a3-45b6-9076-150bb5292428,0x800,0x12c000)/File(EFI\boot\bootx64.efi)..BO

Here goes.

KoenDG · 2018-01-04T22:51:17Z

@superm1 Looks like a failure.

I took a picture with my phone: https://www.dropbox.com/s/6r6zeadqakbtjg5/2018-01-04%2023.35.59-1.jpg?dl=0

Hope it's readable.

After that it just went on with a regular boot.

superm1 · 2018-01-04T23:09:25Z

Ah darn. OK so some other patches really need to come back with it then still, that's unfortunate.
Can you please share that link on Launchpad and mark it verification failed? I'll need to dig into what else needs to come back.

KoenDG · 2018-01-04T23:20:28Z

@superm1 Comment made. Not sure how to mark as failed.

EDIT: Ah hang on I found it. Updated the tags at the top.

superm1 · 2018-01-09T20:30:29Z

So this issue from an upstream fwupdate perspective is fixed, I'm going to close it on Github. From an Ubuntu perspective, the SRU still needs to be done/fixed for xenial/16.04.

Anyone who encounters this outside of Ubuntu with the older fwupdate, please file retry with the latest release (10) and open a new bug referencing this one if you have problems.

superm1 · 2018-01-09T20:32:09Z

@galgalesh Would you be able to bring your content from the first post about how to recover over to a Wiki page? I think it would be good to have it there so it's not lost in Github bug history if someone encounters this in the future.

superm1 · 2018-01-18T22:38:31Z

@galgalesh thanks for making the wiki page.
@KoenDG 16.04 fix has landed now in -proposed. I personally verified it on XPS 9350.

KoenDG · 2018-01-19T13:38:04Z

@superm1 Neat, I'll try it out this weekend.

KoenDG · 2018-01-20T17:28:52Z

@superm1 Update success. Firmware update from 1.7.5 to 1.8.1 was successful.

superm1 · 2018-01-22T15:54:15Z

That's great to hear, thanks. I'm going to lock this issue.

Anyone who encounters this issue in the future:

If you need help recovering, please follow the steps outlined here:
https://github.com/rhboot/fwupdate/wiki/How-to-recover-from-%22no-bootable-devices-found%22-and-%22No-updates-to-process%22
If you are on Ubuntu, please make sure that you are in a version containing the fix
(details in https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1730343)

If you are on Ubuntu and have that version or newer or you encounter it on any other distro, please file a new issue.

superm1 added the bug label Jan 9, 2018

superm1 closed this as completed Jan 9, 2018

rhboot locked as resolved and limited conversation to collaborators Jan 22, 2018

Fail to reboot into Ubuntu after successful update #86

Fail to reboot into Ubuntu after successful update #86

Comments

merlijn-sebrechts commented Oct 22, 2017 • edited Loading

Help, I've got this issue too and I can't boot!

superm1 commented Oct 22, 2017

merlijn-sebrechts commented Oct 22, 2017

superm1 commented Oct 23, 2017

merlijn-sebrechts commented Oct 23, 2017

superm1 commented Oct 23, 2017

merlijn-sebrechts commented Oct 23, 2017 • edited Loading

superm1 commented Oct 23, 2017

merlijn-sebrechts commented Oct 24, 2017

superm1 commented Oct 24, 2017

gerobum commented Nov 6, 2017

merlijn-sebrechts commented Nov 6, 2017

gerobum commented Nov 6, 2017

merlijn-sebrechts commented Nov 6, 2017 • edited Loading

gerobum commented Nov 6, 2017

merlijn-sebrechts commented Nov 6, 2017

gerobum commented Nov 6, 2017

merlijn-sebrechts commented Nov 6, 2017

gerobum commented Nov 6, 2017

seb128 commented Nov 6, 2017

jeremybmerrill commented Nov 17, 2017

superm1 commented Nov 17, 2017

jeremybmerrill commented Nov 17, 2017

merlijn-sebrechts commented Nov 17, 2017

superm1 commented Nov 17, 2017

jeremybmerrill commented Nov 18, 2017

superm1 commented Nov 19, 2017

merlijn-sebrechts commented Nov 19, 2017 • edited Loading

superm1 commented Nov 19, 2017

merlijn-sebrechts commented Nov 20, 2017

4l1fe commented Nov 20, 2017 • edited Loading

superm1 commented Jan 2, 2018

KoenDG commented Jan 2, 2018 • edited Loading

superm1 commented Jan 2, 2018

KoenDG commented Jan 2, 2018

superm1 commented Jan 3, 2018

KoenDG commented Jan 3, 2018

superm1 commented Jan 3, 2018

KoenDG commented Jan 3, 2018

superm1 commented Jan 3, 2018

KoenDG commented Jan 3, 2018

superm1 commented Jan 3, 2018

KoenDG commented Jan 4, 2018

superm1 commented Jan 4, 2018

KoenDG commented Jan 4, 2018 • edited Loading

superm1 commented Jan 4, 2018

KoenDG commented Jan 4, 2018 • edited Loading

superm1 commented Jan 4, 2018

KoenDG commented Jan 4, 2018 • edited Loading

KoenDG commented Jan 4, 2018

superm1 commented Jan 4, 2018

KoenDG commented Jan 4, 2018 • edited Loading

superm1 commented Jan 9, 2018

superm1 commented Jan 9, 2018

superm1 commented Jan 18, 2018

KoenDG commented Jan 19, 2018

KoenDG commented Jan 20, 2018

superm1 commented Jan 22, 2018

merlijn-sebrechts commented Oct 22, 2017 •

edited

Loading

merlijn-sebrechts commented Oct 23, 2017 •

edited

Loading

merlijn-sebrechts commented Nov 6, 2017 •

edited

Loading

merlijn-sebrechts commented Nov 19, 2017 •

edited

Loading

4l1fe commented Nov 20, 2017 •

edited

Loading

KoenDG commented Jan 2, 2018 •

edited

Loading

KoenDG commented Jan 4, 2018 •

edited

Loading

KoenDG commented Jan 4, 2018 •

edited

Loading

KoenDG commented Jan 4, 2018 •

edited

Loading

KoenDG commented Jan 4, 2018 •

edited

Loading