Somehow, I managed to install Leap and lose Window 10 in the Grub2 boot menu.
Below is what I get when I do the operations shown:
Top down:
Windows
/home
/boot/efi
/ (root)
I do not know what I did during the install to rid the boot menu of Windows boot manager.
localhost:~ # os-prober
localhost:~ # grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file …
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-5.14.21-150400.24.38-default
Found initrd image: /boot/initrd-5.14.21-150400.24.38-default
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings …
done
localhost:~ # bootctl
Couldn’t find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --esp-path= to specify path to mount point.
System:
Firmware: n/a (n/a)
Secure Boot: enabled
Setup Mode: user
TPM2 Support: no
Boot into FW: supported
Current Boot Loader:
Product: n/a
Features: ✗ Boot counting
✗ Menu timeout control
✗ One-shot menu timeout control
✗ Default entry control
✗ One-shot entry control
✗ Support for XBOOTLDR partition
✗ Support for passing random seed to OS
✗ Boot loader sets ESP information
ESP: n/a
File: └─n/a
Random Seed:
Passed to OS: no
System Token: not set
@Bill_L What does efibootmgr -v show? Since it appears the efi partition is sda7, add the entry for windows manually… or was windows installed as legacy boot? Show ls -la /boot/efi/EFI.
@Bill_L you need to run windows recovery and see if it will add the boot option, you need to check out windows forums on that part…
That’s why for dual boot it always pays to partition the disk first from a linux USB rescue system, then install as required… for windows select custom install and point at the partition you want windows on and it will sort out the rest.
You do not have any Windows EFI bootloader and your partitions look like Windows has been installed in legacy BIOS mode (and you converted from MBR to GPT after that). In which case you need to search Internet for instructions how to convert Windows legacy BIOS installation to EFI.
Once Windows EFI bootloader is present on ESP, it should be detected by os-prober.
The issue is with “Somehow …”. To my experience it almost never works with my installs as well as with other users I am watching. You may improve your strategy by writing up the essentials: Install Leap / Tumbleweed from USB Stick On Internal Disk. When installing always follow the write-up.
I know Win10 was installed in Elfi mode. I know that because I installed it with legacy disabled in the bios.
At one point in the Leap install partitioner, there was a 16MB boot/EFI partition. During that gawd awful Partitioner I was informed after trying to Partien for Leap that the Win10 boot partition was not large enough.
I completed the partitions for Leap, and From there I just absolutely do not know what happened to /boot/efi for windows.
I will do my best to ‘recover’ Win10 boot. If not I will reinstall it, the try to get through the Leap partitioner without screwing up AGAIN.
Same situation here. A friend of mine bought a Samsung 870 EVO 1TB and had me install Windows and Tumbleweed:
6700k:~ # lsblk /dev/sdc
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sdc 8:32 0 931.5G 0 disk
├─sdc1 8:33 0 100M 0 part
├─sdc2 8:34 0 16M 0 part
├─sdc3 8:35 0 833.2G 0 part
├─sdc4 8:36 0 546M 0 part
└─sdc5 8:37 0 97.7G 0 part
6700k:~ #
I first installed Windows 10 and shrank sdc3. Then I booted into Tumbleweed net-install. With expert partitioner I mounted /dev/sdc1 at /boot/efi and created sdc5. That’s all.
Lsblk doesn’t report much useful for troubleshooting without the -f switch. /dev/sda in that image looks like a simple Windows installation and nothing more, no Linux anywhere except the sdb USB stick.
You should learn how to mount a filesystem while in rescue mode, so you can capture logs and command output that you can copy and paste, and we can quote in reply. It looks like that USB has lots of room for another filesystem you could mount for capturing rescues.
