help-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Destroyed Entries at /dev/sda - boot not possible anymore


From: Andrei Borzenkov
Subject: Re: Destroyed Entries at /dev/sda - boot not possible anymore
Date: Mon, 30 Mar 2015 15:12:16 +0300

On Mon, Mar 30, 2015 at 3:06 PM, Stefan Lamby <address@hidden> wrote:
>
>> Andrei Borzenkov <address@hidden> hat am 30. März 2015 um 13:52
>> geschrieben:
>>
>>
>> On Mon, Mar 30, 2015 at 2:29 PM, Stefan Lamby <address@hidden>
>> wrote:
>> >
>> ...
>> > There was no error, since grub seems to do everything it was told to. The
>> > error
>> > was that it booted from usb stick instead of my laptops hard disk. My fault
>> > was,
>> > that I didn't expect /dev/sda to be overwritten during the install process
>> > for
>> > the usb disk.
>> >
>> ...
>> >
>> > BIOS is set to UEFI Boot, disabled secure boot.
>> >
>>
>> Please boot to Linux and post output of "efibootmgr -v".
>>
>
> Thank you very much for your time and support.
> Here is the output you wanted.
>
> address@hidden:~# efibootmgr -v
> BootCurrent: 0003
> Timeout: 0 seconds
> BootOrder:
> 001E,001F,0010,0011,0012,0013,0014,0015,0016,0003,0019,001A,001B,0001,0002,0017,0018,0000
> Boot0000* Windows Boot Manager
>  
> HD(1,800,100000,57132a06-a1c8-417f-bb0f-c0957dae67fc)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.}...r................
> Boot0001* arch_grub
>     
> HD(1,800,fa000,e3baa10e-75a1-42c0-816c-9bd86d46ec40)File(\EFI\arch_grub\grubx64.efi)
> Boot0002* grub_uefi
>     
> HD(1,800,fa000,e3baa10e-75a1-42c0-816c-9bd86d46ec40)File(\EFI\grub_uefi\grubx64.efi)
> Boot0003* ubuntu
>        
> HD(1,800,100000,57132a06-a1c8-417f-bb0f-c0957dae67fc)File(\EFI\ubuntu\shimx64.efi)
> Boot0010  Setup
> Boot0011  Boot Menu
> Boot0012* Removable Drive
>       030a2400d23878bc820f604d8316c068ee79d25b20699b27e1a34f488e97534d40523c1d
> Boot0013* Hard Drive
>    030a2400d23878bc820f604d8316c068ee79d25bf5b01cc8ce8e9841b3a8fb94b6dfefee
> Boot0014* USB Storage Device
>    030a2400d23878bc820f604d8316c068ee79d25b6895f49a99882e4bb0da03ec784d2828
> Boot0015* CD/DVD/CD-RW Drive
>    030a2400d23878bc820f604d8316c068ee79d25b3750dce1249e1748876bee5d3f25ebfb
> Boot0016* Network
>       030a2400d23878bc820f604d8316c068ee79d25b6567de8ee595634d842b325e6a43510b
> Boot0017* Onboard NIC
>   030a2400d23878bc820f604d8316c068ee79d25b1b7f7356e3475744a9a6ed8e91832083
> Boot0018* Onboard NIC
>   030a2400d23878bc820f604d8316c068ee79d25bb4a054dda1fa7043abf832c5a88367a6
> Boot0019  Diagnostics
> Boot001A  Peripheral Device setting (OPROM setting)
> Boot001B  Change boot mode setting
> Boot001E* USB
>   ACPI(a0341d0,0)PCI(1d,0)USB(0,0)USB(2,0)HD(1,ea8,fb3d58,c3072e18)File()
> Boot001F* DVD
>   ACPI(a0341d0,0)PCI(1f,2)03120a00010000000000CD-ROM(1,7c8ed,1240)File()
>


Just change bootorder so that Ubuntu is listed first (you likely could
do the same from within your BIOS setup). The following is one line in
case it wraps.

efibootmgr --bootorder
0003,001E,001F,0010,0011,0012,0013,0014,0015,0016,0019,001A,001B,0001,0002,0017,0018,0000

Verify using efibootmgr -v again.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]