[SOLVED] Recover Dual boot Windows - Kubuntu

[slamelov]

Hi

I have installed Kubuntu over another distro in a system with dual boot Windows / Kubuntu , and now, Kubuntu starts directly, with no grub for dual boot. I used Boot Repair and here is the Pastebin:

http://paste.ubuntu.com/p/9S82qs2fd3/

I don't know how to solve this , any help?

Thanks

Edited: Boot Repair says this:

"GPT detected. Please create a BIOS-Boot partition (>1MB, unformatted filesystem, bios_grub flag). This can be performed via tools such as Gparted. Then try again. Alternatively, you can retry after activating the [Separate /boot/efi partition:] option."

[slamelov]

Also, I've tried this:

lubuntu@lubuntu:~$ sudo os-prober
/dev/sda1:Windows 10:Windows:chain
/dev/sdd3:Ubuntu 18.10 (18.10):Ubuntu:linux
/dev/sde1:Windows 10:Windows1:chain
lubuntu@lubuntu:~$ sudo su
root@lubuntu:/home/lubuntu# fdisk -l
Disk /dev/loop0: 629,3 MiB, 659873792 bytes, 1288816 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme0n1: 27,3 GiB, 29260513280 bytes, 57149440 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 26FD7655-33A0-4773-9D19-242AF4EBE172

Device         Start      End  Sectors  Size Type
/dev/nvme0n1p1  2048 57141247 57139200 27,3G Microsoft basic data

Disk /dev/sda: 223,6 GiB, 240065183744 bytes, 468877312 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1be3a1a4

Device     Boot   Start       End   Sectors  Size Id Type
/dev/sda1  *       2048   1126399   1124352  549M  7 HPFS/NTFS/exFAT
/dev/sda2       1126400 468875263 467748864  223G  7 HPFS/NTFS/exFAT

Disk /dev/sdb: 223,6 GiB, 240057409536 bytes, 468862128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x4335100b

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdb1        2048 468858879 468856832 223,6G  7 HPFS/NTFS/exFAT

Disk /dev/sdc: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000d0c38

Device     Boot Start        End    Sectors  Size Id Type
/dev/sdc1        2048 3907026943 3907024896  1,8T  7 HPFS/NTFS/exFAT

Disk /dev/sdd: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: FA030497-F219-4155-B24F-357E04E072A5

Device          Start        End    Sectors   Size Type
/dev/sdd1          34     262177     262144   128M Microsoft reserved
/dev/sdd2      264192 1859028991 1858764800 886,3G Microsoft basic data
/dev/sdd3  1859028992 3867967487 2008938496   958G Linux filesystem
/dev/sdd4  3867967488 3869138943    1171456   572M EFI System
/dev/sdd5  3869138944 3907026943   37888000  18,1G Linux swap

Partition 1 does not start on physical sector boundary.

Disk /dev/sde: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc1e5efca

Device     Boot Start        End    Sectors   Size Id Type
/dev/sde1  *     2048 1953521663 1953519616 931,5G  7 HPFS/NTFS/exFAT

Disk /dev/sdf: 15 GiB, 16047407104 bytes, 31342592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6b8b4567

Device     Boot Start     End Sectors  Size Id Type
/dev/sdf1  *        0 1449983 1449984  708M 17 Hidden HPFS/NTFS

Disk /dev/zram0: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram1: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram2: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram3: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram4: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram5: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram6: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram7: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram8: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram9: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram10: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram11: 664,7 MiB, 696999936 bytes, 170166 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
root@lubuntu:/home/lubuntu# mount /dev/sdd3 /mnt/
root@lubuntu:/home/lubuntu# mount --bind /dev /mnt/dev/
root@lubuntu:/home/lubuntu# mount --bind /proc /mnt/proc/
root@lubuntu:/home/lubuntu# chroot /mnt
root@lubuntu:/# grub-install --recheck /dev/sdd
Instalando para plataforma i386-pc.
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
device node not found
grub-install: aviso: esta etiqueta de partición GPT no contiene ninguna Partición de Arranque BIOS; el embebido no será posible.
grub-install: aviso: El embebido no es posible. GRUB podrá ser instalado con esta configuración únicamente usando listas de bloques. No obstante, las listas de bloques son INSEGURAS y su uso está desaconsejado..
grub-install: error: no se procederá con las listas de bloques.
root@lubuntu:/#

[Qqmike]

What a mess--so it looks to an outsider. But I respect your choice to run such a system. Mixing HDD with GPT, mixing EFI with MBR-Legacy, an EFI on a 4th partition, etc. Without taking time at the moment to sort out that Boot Repair output (e.g., to WHICH drive did you install the new Kubuntu?), I'll drop a quick, first thing to try: Boot into that new Kubuntu (which I think you say is your only choice anyway), and issue the command at Konsole:
sudo update-grub
to see if that generates a new GRUB boot menu that includes what you want it to include.
It's a wild shot, but easy to try.

[slamelov]

I need to have Windows Installed in this computer, it's not a choice. I don't like Windows.

New Kubuntu is in SDD device.

I have used sudo update-grub:

sudo update-grub2
Generando un fichero de configuración de grub...
Encontrada imagen de linux: /boot/vmlinuz-4.18.0-13-generic
Encontrada imagen de memoria inicial: /boot/initrd.img-4.18.0-13-generic
Encontrada imagen de linux: /boot/vmlinuz-4.18.0-10-generic
Encontrada imagen de memoria inicial: /boot/initrd.img-4.18.0-10-generic
Añadiendo menú de entrada de inicio para la configuración del firmware EFI
hecho

The problem continues.

If I use sudo os-prober into a Boot Repair console, appears:

"/dev/sda1:Windows 10:Windows:chain
/dev/sdd3:Ubuntu 18.10 (18.10):Ubuntu:linux
/dev/sde1:Windows 10:Windows1:chain"

But if I use it booting from my new Kubuntu, there is not output:

slamelov@Kubuntu-Ultra:~$ sudo os-prober
slamelov@Kubuntu-Ultra:~$

[Qqmike]

As I say, your system has evolved little by little to where there's all sorts of issues with it. The Boot Repair output -- the top section, Boot Info Summary, tells how the system is booting as it is seen when you run Boot Repair. Toward the end, you see Suggested Repair. Have you tried that, accepted the "Suggested Repair," to see if it works? There are issues: You have an ESP (for UEFI booting) at sdd4 (a little unusual to have it at the 4th partition, but it's OK to do so), BUT it doesn't look like Windows is configured for UEFI booting ... Thus, your booting is by the older legacy method. Looks like sdd is a GPT, and it's not clear if you have a BIOS Boot Partition. Looks like this is mentioned in the Blockers to the Suggested Repair:

=================== Blockers in case of suggested repair
GPT detectado. Cree una partición BIOS-Boot (>1MB, sistema de archivos sin formato, marca bios_grub). Esto puede hacerse con herramientas como Gparted. Y vuelva a intentarlo.
Alternativamente, podrá reintentar después de activar la opción [Partición /boot/efi separada:].

Again, this may take a closer look. However, you could try the Suggested Repair: it indicates a re-install of GRUB to MBRs using the GRUB in sdd3 (your Kubuntu partition, right?).
And it indicated it would fix the Windows boot loader:

Additional repair would be performed: unhide-bootmenu-10s fix-windows-boot

When it comes to this sort of booting, it is kind of a crap-shoot, short of starting over from scratch and cleaning up those drives.

[oshunluvr]

Not withstanding Qqmike's advice regarding EFI vs. legacy boot - he's the qualified expert in that area - the error message posted in the OP:

"GPT detected. Please create a BIOS-Boot partition (>1MB, unformatted filesystem, bios_grub flag). This can be performed via tools such as Gparted. Then try again. Alternatively, you can retry after activating the [Separate /boot/efi partition:] option."

can be fixed by creating a partition of the type "EF02". This can be done in the normally unused space on your boot drive from sectors 34 to 2047. You didn't say which drive you're booting from (or I missed it), but if it's the NVME drive, you have the room to do this if that's the route you go.

I have a couple dual-boot laptops that are Windows 10 and KDEneon 18.04. I just turned off secure boot and the installer detected the windows EFI partition and used EFI. It works, so I haven't messed with it.

[Qqmike]

Yeah, I saw that and mentioned it:

Looks like sdd is a GPT, and it's not clear if you have a BIOS Boot Partition. Looks like this is mentioned in the Blockers to the Suggested Repair: ... [etc.]

I'm only hesitating because I'm not clear on how this whole picture fits together! But, that may not matter, as long as it boots THIS TIME (but the future maintenance ... ? ). To re-install GRUB to that sdd (GPT), gonna need a place to put it ...

[slamelov]

I only need to boot Kubuntu (SDD3) and Windows (SDA1). So, I think that repairing Grub in some way could solve the problem.

I tried the boot-repair suggestion, but not sure about the GPT issue.

[Qqmike]

I only need to boot Kubuntu (SDD3) and Windows (SDA1). So, I think that repairing Grub in some way could solve the problem.

I'm pretty sure you can get GRUB fixed.

Question: Is the sdd drive the "new" drive that you put Kubuntu on?

I tried the boot-repair suggestion, but not sure about the GPT issue.

What happened whe you tried the Boot-Repair suggestion? Did it kick back any result or message or issue?

The GPT issue we are concerned about is this: You are using a GPT, but you are NOT using UEFI booting, and that is OK, except with a GPT drive (and No UEFI booting), you need a place for GRUB to reside.

Oshuluvr has this How-to which explains it and a solution (a BIOS Boot Partition, type ef02):

GRUB and GPT partitioned disks

https://www.kubuntuforums.net/showth...l=1#post403281

This how-to, by oshunluvr, shows you how to do this:

On a system that is not UEFI,
use the GPT partition table,
and install GRUB (using a BIOS Boot Partition) to your GPT.

[Qqmike]

It may be the case that if you fix that GPT drive (as per Oshuluvr's how-to with a BIOS Boot Partition), that the solution suggested in Boot-Repair may work. I.e., you run Boot Repair again and click to tell it to run its suggested fix.

[slamelov]

I'm a bit lost.

Before installing Kubuntu, I had a dual boot Windows 10 / Solus. Grub was at SSD3. So, installed Kubuntu in SDD3 removing Solus partition. Kubuntu installation said I should install using EFI.

So, I think I have to recover Grum in some way, but I can't do it. I have followed these steps:

First, I select uefi In bios for USB Boot:



Then, I boot from a Boot Repair USB



Boot Repair starts without problem, so, I select recomended repair. But GPT error appears:



So, I go to advanced and Try...



But...



I don't understand, I have selected EFI in the Bios for USB. What I'm doing wrong?

Also, I can enter at Grub rescue choosing another device for booting, but not sure what can I do in the command line.

[Qqmike]

What I'm doing wrong?

Good question.

So, it is a Gigabyte PC that uses UEFI as its "BIOS firmware", right?

Wondering ...
(1)
If you boot into Kubuntu, open Konsole and run the command:
sudo efibootmgr -v
what does the output look like?

(2)
When you made the Boot-Repair USB, did you choose to download the file:
boot-repair-disk-64.iso
?

(3)
As you showed us, you entered BIOS and selected UEFI as the booting mechanism (i.e., not legacy, not CSM). OK, so after doing that, suppose you re-boot the PC, enter BIOS again, and select a menu called Boot or Boot Menu, and see if your USB is listed--AND is listed saying something about UEFI (along with Kingston). I notice your Kingston USB is the "..DT MicroDuo PMAP", but no mention is made of UEFI ... MAYBE that is how Gigabyte works, but I am used to seeing some reference to the USB being a UEFI device.
Like here:

Install the Kubuntu OS in UEFI mode
--> Must be 64-bit Kubuntu OS for UEFI. I am using Kubuntu 14.04, 64-bit.

Important: You must make certain you are installing Kubuntu in UEFI mode.

I used a Live DVD Kubuntu installer.
Install the DVD in the optical drive, reboot the PC, enter UEFI(-BIOS) by pressing F2.
Under Advanced, find the ASUS boot menu, and the "boot override" menu under that.
The bootable devices will be listed.
Choose the one that corresponds to the Kubuntu UEFI choice.
Look for UEFI / FAT) or some reference to UEFI.
My Live Kubuntu DVD installer showed up twice in UEFI BIOS (under Boot Override) as a "normal" DVD writer, and also as:
UEFI (FAT) TSSTcorp CDDVDW SH-224DB (1028 MB) (= my Samsung DVD player).
Found out you may have to re-boot a time or two for this to appear correctly, so I think.
Select that option from the boot override menu.
The PC will re-boot, and you will see a text mode screen with a grub-like menu. Select install O/S. If, instead, you see the full graphical setup menu, the installer is probably in legacy BIOS mode so reboot, enter the UEFI setup, navigate to boot override and try again.

Taken from this:
https://www.kubuntuforums.net/showth...l=1#post368216

(4) That raises another question. When you installed Kubuntu, did you do it in Legacy mode or UEFI mode (the iso must be 64-bit for UEFI). Or, maybe that is not what you are sure about.

See, it looks like your PC does boot in UEFI mode if you want it to. How is Windows booting: in Legacy or in UEFI mode? That efibootmgr command should tell us something about this. For UEFI, you do need a special partition called an ESP partition--EFI System Partition, and it looks like you have one set up at sdd4. Very, very strange. If you are booting by UEFI, then you do not need to worry about your GPT not having a BIOS Boot Partition. If you are booting by Legacy mode, then that GPT drive should have a BIOS Boot Partition. This is why I said in my first post(s) that it looks like you have some sort of mixture of booting mode.

----- If anyone else gleans something here, please feel free to jump in -- you won't hurt my feelings at all, and it may help slamelov -----

[jlittle]

I'm not sure this might help, but there's a principle here that maybe should be applied:

If some (if not all) computers are booted in UEFI mode, they cannot do a BIOS boot, or a BIOS install. And vice versa. Except that your motherboard might be able to do a "legacy boot" from its UEFI code, but once you've booted any device you can't go back without a reboot.

Since your Windows 7 install uses a BIOS boot, installing Kubuntu on a new device with a UEFI boot means the grub of that install can't boot windows, which seems to me to be your original problem; because that new UEFI install can only see itself, thus it's the only install, you don't get a menu.

Note that GPT is not the same as UEFI; you can do a BIOS boot from a GPT formatted device, but to install a BIOS boot grub to it you need to create the grub boot partition the messages talk about. GPT has some advantages over the old MBR scheme.

If a reinstall of Kubuntu is contemplated, make sure that the install media is booted in BIOS mode, or it won't do a BIOS mode install.

I suggest that because you want to have a choice of your windows install, you need a BIOS boot, perhaps aka a legacy boot. Once the OS is running it won't care.

I don't know where boot repair fits in all this; last time I looked at it didn't support UEFI very well.

[Qqmike]

jlittle: If a reinstall of Kubuntu is contemplated, make sure that the install media is booted in BIOS mode, or it won't do a BIOS mode install.

I suggest that because you want to have a choice of your windows install, you need a BIOS boot, perhaps aka a legacy boot. Once the OS is running it won't care.

Yes, good. There does seem to be a mixture of UEFI and BIOS going on, and you see it, too. The efibootmgr command might shed light on this, but ...

Now, given the conclusion that he needs to be consistent and do a BIOS installation and boot of BOTH Windows and Kubuntu, then he needs to deal with that GPT issue: your GPT disk needs a BIOS BOOT Partition--as per Oshunluvr's how-to on that (linked above in one of my posts).

What you say, jlittle, makes sense to me. His computer may be able to use UEFI, but his older Windows 7 may not be using it! Somehow, that ESP partition did get created, though, sdd4.

[Qqmike]

Kubuntu installation said I should install using EFI.

Yeah, something here doesn't add up. Kubuntu installer tried to install using EFI because on that GPT it didn't see a BIOS Boot Partition on sdd. (But then, how did Solus boot?) Maybe that ESP got put there at sdd4 because the Kubuntu installer put it there? Windows never booted by UEFI, but by Legacy BIOS. I think this whole thing has to do with the GPT not being properly set up for BIOS boot--with the BIOS Boot Partition on it--as per Oshuluver's how-to.