No Grub after installing win10 on second drive

I’ve installed windows 10 on sdb, and after that, PC starts immediately into windows.

Then I’ve started Manjaro from live CD, and grub-update, and install it to /dev/sda

Now if I do start the PC, I got (drive not present) in the bootup-dialog, where I can choose the boot device at startup.

If I choose this device anyway, I got “insert bootmedia” request.

Any Idea, what’s wrong here?

If I now boot via liveCD and run this grub commands:

It starts the grub with the needed entries:

I do choose Manjaro, and the boot process stuck on trying to mount the device:

And here is disk -l:

this very bad :
on boot USB then disk , the disk sda is GPT , and is looking for /boot/efi …
that is present in /etc/fstab ( check this on your disk )

installation is Bios on sdb , so you have mixed GPT/MBR format

  1. create a profile for windows and linux in your UEFI motherboard

  2. in your UEFI , recheck

    disable secure boot
    disable fast boot
    disks on AHCI
    no legacy
    no CSM
    UEFI only or others ( not windows )

  3. you should see
    UEFI < USB vendor name > < partition 1 > → boot in EFI
    or < USB vendor name > ( no UEFI: before )
    boot on USB iso ( live )

open a terminal and browser on this topic
and report

inxi  -Fza 
test -d /sys/firmware/efi && echo efi || echo bios
1 Like

Ok, here is my fstab:


Last command returns “bios”

@stephane but I must install EFI at my SDA again, right?
Because /boot/efi is currently empty

point 1 - update your UEFI version

point 2 - if you can create profile for windows & linux in UEFI

point 3 - can you convert your disk sdb to GPT ?

*** be careful , DO NOT FORMAT MBR to GPT or GPT to MBR , you WILL LOOSE ALL DATA ***
==> make a backup of Data always before conversion
==> may be need to deconnect sda for theses actions on sdb

sb1 is wrong on type partition , it should be type vfat ( Fat32 ) , il will be done by windows

for both sda1 & future sdb1 each you have Esp flag & Boot flag

I can’t upgrade firmware, because firmware-bios-tool requires 20% battery charged, and battery is to old /broken

Before I do anything to convert windows, isn’t there a way to only boot Linux??

I ask, because it seems that I, myself have broken the grub with own grub-install commands, because before I upgrade Win7 to win 10, only grub was loaded on startup, and windows wasn’t shown anywhere.

So it would be perfectly fine to me, to only load grub, and need to choose the Windows-Drive by bios-bootup-choose-drive-dialog.

If I try to install the efi-grub, the installer told me, that there is no EFI at all… That’s why I’m confused here

My first big target is to get Linux running again, without windows. That worked before windows 10 installation, and should be possible to get back to work without Firmware-flash or changing windows drive, right?

@stephane it might be, that I’ve accidentally execute the grup-install for sda1 instead of SDA… Might this be the cause?

1 - never do an upgrade on battery , always on AC
2 - if there any data to save from windows ?
3 - you will have to restore change flag then install grub EFI
launch your UEFI , recheck

disable secure boot
disable fast boot
disks on AHCI
no legacy
no CSM
UEFI only or others ( not windows )

you should see
UEFI < USB vendor name > < partition 1 > → boot in EFI

open a terminal and check

inxi  -Fza 
test -d /sys/firmware/efi && echo efi || echo bios

launch Gparted
add flag boot & esp on sda1 ( bios have change by windows )


sudo manjaro-chroot -a
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck --verbose 
mkinitcptio -P
efibootmgr -v
exit ( quit chroot )

you will update your bios later

I don’t have any of this options in my bios: secure boot, fastboot, legacy, and don’t see what csm means (even don’t have it)
AHCI is on.

UEFI only or others ( not windows ) even is no where to see in bios.

I can only launch gparted after live-cd started, but didn’t found an esp-flag there.

BTW: I never would flash only on battery driven laptop. For sure the AC is plugged in. But the firmware upgrader who is build-in in bios told me, he will only start if battery is above 20%, nevertheless if AC is plugged in or not.