Precision 5510 bios 1.2.19 update on ubuntu fails with no boot drive

Bug #1666056 reported by Dave Cramer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Dell Sputnik
New
Undecided
Unassigned

Bug Description

Ubuntu version 16.04
Just updated the bios using ubuntu software center
After the upgrade the machine is not bootable and the message is no bootable drive

The solution is to go into Setup (F2) on boot

In Boot Sequence, add a boot option which uses the file name \EFI\ubuntu\grubx64.efi.

Move this boot option to the top and reboot

Revision history for this message
Mario Limonciello (superm1) wrote :

@Dave Cramer,

Sorry to hear this experience happened. This can be caused by a variety of factors, but in order to reproduce it can you share:

1) More about how you installed Ubuntu?
1) Did the machine come with Ubuntu?
2) Did you turn on or off secure boot?
3) Did you do anything special manually related to creating boot options or boot files?
4) Did you manually add or remove any boot options when installing?

What does $ sudo efibootmgr -v output look like now?

Revision history for this message
Dave Cramer (davecramer) wrote :

@Mario,

1) Machine came with 14.04 pre-installed, I upgraded to 16.04 using ubuntu dist-upgrade
2) secure boot was off as it came from factory
3) Not that I recall
4) I had to choose a boot option, which of course I can't recall

BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,0000
Boot0000* Linux-Firmware-Updater \fwupx64.efi HD(1,GPT,e91ea938-66cc-4d25-b68e-17e86182f2a0,0x800,0xfa000)/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* Linux-Firmware-Updater \fwupx64.efi HD(1,GPT,e91ea938-66cc-4d25-b68e-17e86182f2a0,0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.x.6.4...e.f.i...
Boot0004* grub PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-08-0D-02-00-12-7F-45)/HD(1,GPT,e91ea938-66cc-4d25-b68e-17e86182f2a0,0x800,0xfa000)/File(\EFI\ubuntu\grubx64.efi)
Boot0008* UEFI: THNSN51T02DUK NVMe TOSHIBA 1024GB, Partition 1 HD(1,GPT,e91ea938-66cc-4d25-b68e-17e86182f2a0,0x800,0xfa000)/File(EFI\boot\bootx64.efi)..BO
Boot0009* M.2 PCIe SSD BBS(HD,THNSN51T02DUK NVMe TOSHIBA 1024,0x0)..BO

Revision history for this message
Mario Limonciello (superm1) wrote :

Thanks. A few things stand out here to me.

1) You're missing an "ubuntu" boot entry. That's the default one Dell populates when the machine is factory installed. It would have been pointed at shimx64.efi to chainload grubx64.efi.

Did you replace your SSD and manually reinstall at some point? Or is that the factory SSD?

2) There is actually a file \efi\boot\bootx64.efi on the ESP. Did you make that yourself?

3) I think if you run sudo update-grub you should get your missing 'ubuntu' boot entry replaced.

But so assuming you didn't replace the disk or tweak anything else a set of reproduce steps sounds like:
1) Start with preinstalled Dell 14.04.
2) Use Update manager to upgrade to 16.04.
3) From 16.04 do all the standard updates.
4) In software center apply BIOS update

That sound right?

Revision history for this message
Dave Cramer (davecramer) wrote : Re: [Bug 1666056] Re: Precision 5510 bios 1.2.19 update on ubuntu fails with no boot drive

On 20 February 2017 at 17:51, Mario Limonciello <email address hidden> wrote:

> Thanks. A few things stand out here to me.
>
> 1) You're missing an "ubuntu" boot entry. That's the default one Dell
> populates when the machine is factory installed. It would have been
> pointed at shimx64.efi to chainload grubx64.efi.
>
> Did you replace your SSD and manually reinstall at some point? Or is
> that the factory SSD?

No, this is the factory SSD

>

> 2) There is actually a file \efi\boot\bootx64.efi on the ESP. Did you
> make that yourself?
>
> No, I'm trying real hard not to do anything myself.. 16.04 was a necessity
as lots of things fail to work with 14.04

> 3) I think if you run sudo update-grub you should get your missing
> 'ubuntu' boot entry replaced.
>
> I'll give that a try

> But so assuming you didn't replace the disk or tweak anything else a set
> of reproduce steps sounds like:
> 1) Start with preinstalled Dell 14.04.
> 2) Use Update manager to upgrade to 16.04.
> 3) From 16.04 do all the standard updates.
> 4) In software center apply BIOS update
>
> That sound right?
>
> YUP!

Thanks!

Dave Cramer

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1666056
>
> Title:
> Precision 5510 bios 1.2.19 update on ubuntu fails with no boot drive
>
> Status in Dell Sputnik:
> New
>
> Bug description:
> Ubuntu version 16.04
> Just updated the bios using ubuntu software center
> After the upgrade the machine is not bootable and the message is no
> bootable drive
>
> The solution is to go into Setup (F2) on boot
>
> In Boot Sequence, add a boot option which uses the file name
> \EFI\ubuntu\grubx64.efi.
>
> Move this boot option to the top and reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dell-sputnik/+bug/1666056/+subscriptions
>

Revision history for this message
Dave Cramer (davecramer) wrote :

Here's the new output after running sudo update-grub

BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,0000
Boot0000* Linux-Firmware-Updater \fwupx64.efi
HD(1,GPT,e91ea938-66cc-4d25-b68e-17e86182f2a0,0x800,0xfa000)/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* Linux-Firmware-Updater \fwupx64.efi
HD(1,GPT,e91ea938-66cc-4d25-b68e-17e86182f2a0,0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.x.6.4...e.f.i...
Boot0004* grub
PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-08-0D-02-00-12-7F-45)/HD(1,GPT,e91ea938-66cc-4d25-b68e-17e86182f2a0,0x800,0xfa000)/File(\EFI\ubuntu\grubx64.efi)
Boot0008* UEFI: THNSN51T02DUK NVMe TOSHIBA 1024GB, Partition 1
HD(1,GPT,e91ea938-66cc-4d25-b68e-17e86182f2a0,0x800,0xfa000)/File(EFI\boot\bootx64.efi)..BO
Boot0009* M.2 PCIe SSD BBS(HD,THNSN51T02DUK NVMe TOSHIBA 1024,0x0)..BO

Dave Cramer

On 20 February 2017 at 18:05, Dave Cramer <email address hidden> wrote:

>
>
> On 20 February 2017 at 17:51, Mario Limonciello <email address hidden>
> wrote:
>
>> Thanks. A few things stand out here to me.
>>
>> 1) You're missing an "ubuntu" boot entry. That's the default one Dell
>> populates when the machine is factory installed. It would have been
>> pointed at shimx64.efi to chainload grubx64.efi.
>>
>> Did you replace your SSD and manually reinstall at some point? Or is
>> that the factory SSD?
>
>
> No, this is the factory SSD
>
>>
>
>
>> 2) There is actually a file \efi\boot\bootx64.efi on the ESP. Did you
>> make that yourself?
>>
>> No, I'm trying real hard not to do anything myself.. 16.04 was a
> necessity as lots of things fail to work with 14.04
>
>> 3) I think if you run sudo update-grub you should get your missing
>> 'ubuntu' boot entry replaced.
>>
>> I'll give that a try
>
>> But so assuming you didn't replace the disk or tweak anything else a set
>> of reproduce steps sounds like:
>> 1) Start with preinstalled Dell 14.04.
>> 2) Use Update manager to upgrade to 16.04.
>> 3) From 16.04 do all the standard updates.
>> 4) In software center apply BIOS update
>>
>> That sound right?
>>
>> YUP!
>
> Thanks!
>
>
> Dave Cramer
>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1666056
>>
>> Title:
>> Precision 5510 bios 1.2.19 update on ubuntu fails with no boot drive
>>
>> Status in Dell Sputnik:
>> New
>>
>> Bug description:
>> Ubuntu version 16.04
>> Just updated the bios using ubuntu software center
>> After the upgrade the machine is not bootable and the message is no
>> bootable drive
>>
>> The solution is to go into Setup (F2) on boot
>>
>> In Boot Sequence, add a boot option which uses the file name
>> \EFI\ubuntu\grubx64.efi.
>>
>> Move this boot option to the top and reboot
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/dell-sputnik/+bug/1666056/+subscriptions
>>
>
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.