[SOLVED] restoring grub for dual boot with windows

Brains · 02-28-2019, 08:12 PM

It's been seven hours since colorpurple21859 asked for the output of a simple command.
As far as I'm concerned, Ai_Programmer is employing a massive amount of left tactic to achieve an alterior motive.
I base that comment on the quote below.

Quote:

post #25 --->While I do have years of experience with linux

The title of this thread is designed to attract as much attention as possible.
Boot files were deliberately removed before the bootinfo script was run.
I highly doubt the Linux installers would include EFI boot files in the EFI partiton and neglect grub.cfg files
Commands suggested to run according to screenshots provided by Ai_Programmer were never correct
This could have been dealt with within a half hour two days ago
But there is absolutely no evidence of Ai_Programmer attempting to do what was suggested 2 days ago

Quote:

2 days ago --->A fresh installation can be done within a half hour, The computer's boot menu needs to be enabled in order to boot Linux

Failure to respond to colorpurple21859's request in the post above suggest this is not in the direction Ai_Programmer want's things to go.
Ai_Programmer's alterior motive?
To get this community to invest time to help Ai_Programmer enable booting Linux from Windows boot menu

Quote:

Post #14 2 days ago --->I already found the parameters for bcdedit so if someone could tell me how to get the uuid for sdb1 I could at least setup the windows bootloader

Quote:

post #25 --->I tried following the instructions in the following youtube video to use setup linux on the widows bootloader

Quote:

Should I type the above command from a live Ubuntu/debian or from bcdedit?

Brains · 02-28-2019, 08:58 PM

This is how to configure the default boot entry in Windows 10
From an elevated command prompt in Windows, type command: bcdedit /enum all /v
You will get an output similar to the one below, in the example below I highlighted the UUID of the Debian boot entry in red.

Code:

C:\WINDOWS\system32>bcdedit /enum all /v

Firmware Boot Manager
---------------------
identifier              {a5a30fa2-3d06-4e9f-b5f4-a01df9d1fcba}
displayorder            {9dea862c-5cdd-4e70-acc1-f32b344d4795}
                        {a6facddc-03ed-11e9-9cb4-806e6f6e6963}
timeout                 1

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {e0b5f812-f2f9-11e8-9f83-d48768a57186}
resumeobject            {e0b5f811-f2f9-11e8-9f83-d48768a57186}
displayorder            {e0b5f812-f2f9-11e8-9f83-d48768a57186}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {a6facddc-03ed-11e9-9cb4-806e6f6e6963}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\DEBIAN\GRUBX64.EFI
description             debian

Windows Boot Loader
-------------------
identifier              {0363ee6f-1f8a-11e9-9da7-9cb6d0086032}
device                  ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{0363ee70-1f8a-11e9-9da7-9cb6d0086032}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
displaymessage          Recovery
osdevice                ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{0363ee70-1f8a-11e9-9da7-9cb6d0086032}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes
custom:46000010         Yes

Windows Boot Loader
-------------------
identifier              {4f511f6e-c815-48ec-81de-b5ec44f4c136}
device                  ramdisk=[C:]\boot\4F511F6F-C815-48ec-81DE-B5EC44F4C136.WIM,{4f511f6d-c815-48ec-81de-b5ec44f4c136}
path                    \Windows\system32\winload.efi
description             Windows PE (WinToUSB)
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                ramdisk=[C:]\boot\4F511F6F-C815-48ec-81DE-B5EC44F4C136.WIM,{4f511f6d-c815-48ec-81de-b5ec44f4c136}
systemroot              \windows
nx                      OptIn
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {50e655a5-f227-11e6-9e6d-fb267a7ea764}
device                  unknown
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence        {50e655a6-f227-11e6-9e6d-fb267a7ea764}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                unknown
systemroot              \Windows
resumeobject            {50e655a4-f227-11e6-9e6d-fb267a7ea764}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {50e655a6-f227-11e6-9e6d-fb267a7ea764}
device                  ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{50e655a7-f227-11e6-9e6d-fb267a7ea764}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-us
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
displaymessage          Recovery
osdevice                ramdisk=[unknown]\Recovery\WindowsRE\Winre.wim,{50e655a7-f227-11e6-9e6d-fb267a7ea764}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes
custom:46000010         Yes

Windows Boot Loader
-------------------
identifier              {e0b5f812-f2f9-11e8-9f83-d48768a57186}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  en-US
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence        {0363ee6f-1f8a-11e9-9da7-9cb6d0086032}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {e0b5f811-f2f9-11e8-9f83-d48768a57186}
nx                      OptIn
bootmenupolicy          Standard

Resume from Hibernate
---------------------
identifier              {50e655a4-f227-11e6-9e6d-fb267a7ea764}
device                  unknown
path                    \Windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {1afa9c49-16ab-4a5c-901b-212802da9460}
recoverysequence        {50e655a6-f227-11e6-9e6d-fb267a7ea764}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              unknown
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Resume from Hibernate
---------------------
identifier              {e0b5f811-f2f9-11e8-9f83-d48768a57186}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {1afa9c49-16ab-4a5c-901b-212802da9460}
recoverysequence        {0363ee6f-1f8a-11e9-9da7-9cb6d0086032}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {b2721d73-1db4-4c62-bf78-c548a880142d}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
bootems                 No

Debugger Settings
-----------------
identifier              {4636856e-540f-4170-a130-a84776f4c654}
debugtype               Serial
debugport               1
baudrate                115200

RAM Defects
-----------
identifier              {5189b25c-5558-4bf2-bca4-289b11bd29e2}

Global Settings
---------------
identifier              {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
inherit                 {4636856e-540f-4170-a130-a84776f4c654}
                        {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
                        {5189b25c-5558-4bf2-bca4-289b11bd29e2}

Boot Loader Settings
--------------------
identifier              {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
                        {7ff607e0-4395-11db-b0de-0800200c9a66}

Hypervisor Settings
-------------------
identifier              {7ff607e0-4395-11db-b0de-0800200c9a66}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {1afa9c49-16ab-4a5c-901b-212802da9460}
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

Device options
--------------
identifier              {0363ee70-1f8a-11e9-9da7-9cb6d0086032}
description             Windows Recovery
ramdisksdidevice        partition=\Device\HarddiskVolume5
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier              {4f511f6d-c815-48ec-81de-b5ec44f4c136}
description             Windows PE (WinToUSB)
ramdisksdidevice        partition=C:
ramdisksdipath          \boot\4F511F6F-C815-48ec-81DE-B5EC44F4C136.SDI

Device options
--------------
identifier              {50e655a7-f227-11e6-9e6d-fb267a7ea764}
description             Windows Recovery
ramdisksdidevice        unknown
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

C:\WINDOWS\system32>

Using the UUID of the Debian boot entry, run the command below:

Code:

bcdedit /default {a6facddc-03ed-11e9-9cb4-806e6f6e6963}

Now reboot, on my laptop, it reboots to Windows

Ai_Programmer · 03-01-2019, 07:36 AM

1)I've disabled secure boot as can be seen from my posted images

2)I've noticed that after a successful install windows tries to "repair" my computer or boot sequence. I just did another fresh install & I don't think it "repaired" the boot sequence but as we speak I'm formatting & installing once more just in case

3)Here's that requested output but I'm not sure if windows had a chance to screw it up and also a pic of my f12 menu

Ai_Programmer · 03-01-2019, 07:46 PM

So today I realized that I missed 2 posts. Sorry about that

After a fresh reinstall I hit f12 right away & got the same boot option: only windows. I then tried to to boot from my live ubuntu & it booted to windows (maybe I should have hit f12 for this time as well anyway in windows I ran the command as requested:

Quote:

C:\WINDOWS\system32>bcdedit /default {a6facddc-03ed-11e9-9cb4-806e6f6e6963}
The operation completed successfully.

I don't care which bootloader that I use whether it's windows or linux as long as I get to run linux. So now i'mm going to try booting linux & if that fails I'll post the output of the command lsblk

Ai_Programmer · 03-01-2019, 08:46 PM

So output from lsblk:

colorpurple21859 · 03-01-2019, 10:03 PM

If efibootmgr -v still shows the same thing, try this

Code:

sudo efibootmgr -a 0003
sudo efibootmgr -o 0003,0002,0001,2001,2002,2003

Ai_Programmer · 03-02-2019, 01:22 AM

Quote:

Originally Posted by colorpurple21859

If efibootmgr -v still shows the same thing, try this

Code:

sudo efibootmgr -a 0003
sudo efibootmgr -o 0003,0002,0001,2001,2002,2003

So I tried this command I'm sorry but if there's something that I'm supposed to add because it's common sense then it's lost on me. WRT the cli I only know basic commands like cp, cd, mv || and &&.

colorpurple21859 · 03-02-2019, 06:26 AM

output of

Code:

sudo efibootmgr -v

Code:

sudo ls /boot/efi/EFI

Code:

sudo ls /boot/efi/EFI/debian

Ai_Programmer · 03-02-2019, 06:48 AM

here you go:

Code:

ubuntu@ubuntu:~$ sudo efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0002,0001,2001,2002,2003
Boot0000* Unknown Device: 	HD(1,GPT,f6b2a8de-c36b-4629-866a-812c324705e4,0x800,0x32000)/File(\EFI\ubuntu\shimx64.efi)RC
Boot0001* Linux	HD(1,MBR,0x6a2a1840,0x800,0x39c9800)/File(\EFI\Boot\grubx64.efi)RC
Boot0002* Windows Boot Manager	HD(1,GPT,f6b2a8de-c36b-4629-866a-812c324705e4,0x800,0x32000)/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.}....................
Boot0003* debian	HD(1,GPT,f6b2a8de-c36b-4629-866a-812c324705e4,0x800,0x32000)/File(\EFI\debian\grubx64.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC
ubuntu@ubuntu:~$ sudo ls /boot/efi/EFI
ls: cannot access '/boot/efi/EFI': No such file or directory

Ai_Programmer · 03-02-2019, 10:54 AM

If I reformat the whole drive & commit to Linux will that solve the problem? I'm feeling hopeless

colorpurple21859 · 03-02-2019, 12:26 PM

Rerun the code in post 36

Ai_Programmer · 03-02-2019, 01:16 PM

Code:

ubuntu@ubuntu:~$ sudo efibootmgr -a 0003
You must specify a entry to activate (see the -b option

AP

colorpurple21859 · 03-02-2019, 03:43 PM

what does this do?

Code:

sudo mkdir /boot/efi
sudo mount /dev/sdb1 /boot/efi
sudo efibootmgr -o 0003,0002,0001,2001,2002,2003

Ai_Programmer · 03-02-2019, 06:57 PM

It crashed have a look

colorpurple21859 · 03-03-2019, 07:12 AM

You must have efi firmware that doesn't play nice
maybe this will work make sure you have a windows cd/iso just in case you need to do a windows boot repair.
https://itsfoss.com/no-grub-windows-linux/
there is some information in here that maybe of some help
https://wiki.archlinux.org/index.php...ware_Interface