How do to get Windows back in the grub menu?
I have a Dell laptop with Windows 10 and I installed Tumbleweed next to it and got a grub menu in which I could select which one to start. After installation of Leap 15.4 beta, next to Tumbleweed and Windows 10 I only got Leap 15.4 and Tumbleweed in the grub menu. I tried in both openSUSE systems to run "yast bootloader", but no Windows. I found a recipe to get other bootable systems in grub by running the command os-prober and update-grub, however os-prober does not show any sign of windows. So update-grub will not add Windows in the menu. How do I get Windows 10 back in grub? Also the Bios does not show an entry to boot Windows. -- fr.gr. member openSUSE Freek de Kruijf
On 2022-03-16 14:42, Freek de Kruijf wrote:
Also the Bios does not show an entry to boot Windows.
Can you show us? efibootmgr -v lsblk or rather lsblk -oNAME,MAJ:MIN,RM,SIZE,RO,TYPE,PARTTYPENAME or go the whole hog lsblk -O | less -S scroll to the right with your arrow keys -- /bengan
Op woensdag 16 maart 2022 15:36:46 CET schreef Bengt Gördén:
On 2022-03-16 14:42, Freek de Kruijf wrote:
Also the Bios does not show an entry to boot Windows.
Can you show us?
efibootmgr -v
EFI variables are not supported on this system.
lsblk
or rather lsblk -oNAME,MAJ:MIN,RM,SIZE,RO,TYPE,PARTTYPENAME
NAME MAJ:MIN PARTTYPENAME PARTLABEL RO RM SIZE TYPE nvme0n1 259:0 0 0 476.9G disk ├─nvme0n1p1 259:1 EFI System EFI system partition 0 0 100M part ├─nvme0n1p2 259:2 Microsoft reserved Microsoft reserved partition 0 0 16M part ├─nvme0n1p3 259:3 Microsoft basic data Basic data partition 0 0 92.8G part ├─nvme0n1p4 259:4 Windows recovery environment 0 0 500M part ├─nvme0n1p5 259:5 Linux filesystem 0 0 20G part ├─nvme0n1p6 259:6 Linux filesystem 0 0 20G part ├─nvme0n1p7 259:7 Linux filesystem 0 0 20G part ├─nvme0n1p8 259:8 Linux filesystem 0 0 20G part ├─nvme0n1p9 259:9 0 0 20G part ├─nvme0n1p10 259:10 Linux filesystem 0 0 20G part ├─nvme0n1p11 259:11 Linux swap 0 0 8G part └─nvme0n1p12 259:12 Linux filesystem 0 0 255.6G part
or go the whole hog lsblk -O | less -S
scroll to the right with your arrow keys
NAME KNAME PATH MAJ:MIN FSAVAIL FSSIZE FSTYPE FSUSED FSUSE% FSROOTS FSVER MOUNTPOINT MOUNTPOINTS LABEL UUID PTUUID PTTYPE PARTTYPE PARTTYPENAME PARTLABEL PARTUUID PARTFLAGS RA RO RM HOTPLUG MODEL SERIAL SIZE STATE OWNER GROUP MODE ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE TYPE DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO WSAME WWN RAND PKNAME HCTL TRAN SUBSYSTEMS REV VENDOR ZONED DAX nvme0n1 nvme0n1 /dev/nvme0n1 259:0 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt 512 0 0 0 SAMSUNG MZVLB512HAJQ -000H1 S3WTNF0K410831 476.9G live root disk brw-rw---- 0 512 0 512 512 0 none 1023 disk 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme block:nvme:pci none 0 ├─nvme0n1p1 nvme0n1p1 /dev/nvme0n1p1 259:1 46.2M 96M vfat 49.8M 52% / FAT32 /boot/efi /boot/efi EFIL 0CB8-7F04 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt c12a7328-f81f-11d2-ba4b-00a0c93ec93b EFI System EFI system partition e36ffedb-db8e-41ae- ad18-243582e4c473 512 0 0 0 100M root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p2 nvme0n1p2 /dev/nvme0n1p2 259:2 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt e3c9e316-0b5c-4db8-817d-f92df00215ae Microsoft re served Microsoft reserved partition d85f8ea2- dcd7-479d-8e4e-0fec2181c9ab 512 0 0 0 16M root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p3 nvme0n1p3 /dev/nvme0n1p3 259:3 59.4G 92.8G ntfs 33.3G 36% / /windows /windows WINDOWS 4060B91060B90E22 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 Microsoft ba sic data Basic data partition 2a8b3c6d- dbd6-4cea-8fd7-0730faf8f8b8 512 0 0 0 92.8G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p4 nvme0n1p4 /dev/nvme0n1p4 259:4 ntfs 48B65C00B65BECC6 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt de94bba4-06d1-4d40-a16a-bfd50179d6ac Windows reco very environment d17013e2-01f5-4836-be32- b02904832340 0x1 512 0 0 0 500M root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p5 nvme0n1p5 /dev/nvme0n1p5 259:5 ext4 1.0 SUSETUML 016c1efa-9298-4865-bee8-ae6401099f30 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 Linux filesy stem 4c0646b4-72ba-4cb0-8f1d-617bb7d0af0d 512 0 0 0 20G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p6 nvme0n1p6 /dev/nvme0n1p6 259:6 xfs HOMETUML a162a8f8-aeca-44fe-8f84-f79119b97d56 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 Linux filesy stem e07266b7-bedb-4710-aad3- d70144f659e9 512 0 0 0 20G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ─nvme0n1p5 nvme0n1p5 /dev/nvme0n1p5 259:5 ext4 1.0 SUSETUML 016c1efa-9298-4865-bee8-ae6401099f30 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 Linux filesy stem 4c0646b4-72ba-4cb0-8f1d-617bb7d0af0d 512 0 0 0 20G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p6 nvme0n1p6 /dev/nvme0n1p6 259:6 xfs HOMETUML a162a8f8-aeca-44fe-8f84-f79119b97d56 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 Linux filesy stem e07266b7-bedb-4710-aad3- d70144f659e9 512 0 0 0 20G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p7 nvme0n1p7 /dev/nvme0n1p7 259:7 ext4 1.0 SUSE153L f1f7b43e-dcb8-4ee6-ad0c-ab5915f90d42 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 Linux filesy stem 1556e130-f782-4565- ba26-713db3bd37f1 512 0 0 0 20G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p8 nvme0n1p8 /dev/nvme0n1p8 259:8 xfs HOME153L 4de6301d-38b0-4ba3-890f-144b7c612987 b5f64701-b80a-4fd9-a574-4a83835b28bc gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 Linux filesy stem c6dc2501- ae82-4cd6-86bf-304bf6d91d91 512 0 0 0 20G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p9 nvme0n1p9 /dev/nvme0n1p9 259:9 12.7G 19.5G ext4 5.8G 29% / 1.0 / / SUSE154L 99472ecf-aa87-4999-b733-7e44b515cf57 b5f64701-b80a-4fd9-a574-4a83835b28bc dos 0fc63daf-8483-4772-8e79-3d69d8477de4 ab52d30b-5e23-45de-8d06-37eadce14b3d 0x4 512 0 0 0 20G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p10 nvme0n1p10 /dev/nvme0n1p10 259:10 19.9G 20G xfs 85.7M 0% / /home /home HOME154L e969eddb-7c48-47ed-b3cb-e4771ac77b5b b5f64701-b80a-4fd9-a574-4a83835b28bc gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 Linux filesy stem 4ce1c5a8- a010-4ccb-9846-3edf651ccd78 512 0 0 0 20G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 ├─nvme0n1p11 nvme0n1p11 /dev/nvme0n1p11 259:11 swap 1 [SWAP] [SWAP] SWAPL 96feb309-1d68-4c30-9d36-14dc641e28be b5f64701-b80a-4fd9-a574-4a83835b28bc gpt 0657fd6d-a4ab-43c4-84e5-0933c84b4f4f Linux swap e0146299-aaf1-4d03-a979- cad709b15819 512 0 0 0 8G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 0 └─nvme0n1p12 nvme0n1p12 /dev/nvme0n1p12 259:12 170.4G 255.4G xfs 85.1G 33% / /hbasis /hbasis HOMEBASISL bbfa77d5-e084-47dc-b0ec-ac4552171a6b b5f64701-b80a-4fd9-a574-4a83835b28bc gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 Linux filesy stem fe195024-6369-4780-860b-8989bc98d75e 512 0 0 0 255.6G root disk brw-rw---- 0 512 0 512 512 0 none 1023 part 0 512B 2T 0 0B eui.0025388481b4cd7f 0 nvme0n1 nvme block:nvme:pci none 01G -- fr.gr. member openSUSE Freek de Kruijf
On 17.03.2022 02:42, Freek de Kruijf wrote:
Op woensdag 16 maart 2022 15:36:46 CET schreef Bengt Gördén:
On 2022-03-16 14:42, Freek de Kruijf wrote:
Also the Bios does not show an entry to boot Windows.
Can you show us?
efibootmgr -v
EFI variables are not supported on this system.
lsblk
or rather lsblk -oNAME,MAJ:MIN,RM,SIZE,RO,TYPE,PARTTYPENAME
NAME MAJ:MIN PARTTYPENAME PARTLABEL RO RM SIZE TYPE nvme0n1 259:0 0 0 476.9G disk ├─nvme0n1p1 259:1 EFI System EFI system partition
You installed openSUSE in legacy mode while your Windows is most likely installed in EFI mode. You need to install openSUSE and Windows in the same mode for dual-boot support.
Op donderdag 17 maart 2022 05:19:16 CET schreef Andrei Borzenkov:
You installed openSUSE in legacy mode while your Windows is most likely installed in EFI mode. You need to install openSUSE and Windows in the same mode for dual-boot support.
It went wrong at the moment I needed to fiddle in the BIOS to boot the iso image on the USB stick. I did not have enough knowledge about what these different options in the BIOS are. Unfortunately I made it worse. Now I have the BIOS configured on UEFI and Secure Boot: OFF However when I look at the boot options I only can boot from USB and the NIC using IPv4 or IPv6. Apparently I removed the entry to boot from the SSD disk, so the question now is how and where do I find the parameters to enter a boot option for the disk. Looking at one of the existing Boot options, I see three fields: Boot Option Name: File System Name: and File Name: When I press the button "Add Boot Option" I get the message: File System Not Found! I tried copying the FAT partition on the disk to a USB and when this USB is inserted and I press the above button I get can add a Boot Option. However the File System Name points to this USB and I can not change it to the disk device. I don't understand why this disk/FAT partition is not detected when I press this button. I also tried efibootmgr while upgrading/running the openSUSE 15.4 system from the USB. I could display the entries in the Boot Options with "efibootmgr -v" and added the boot entry for openSUSE in the boot order using "efibootmgr -o". Any suggestions? -- fr.gr. member openSUSE Freek de Kruijf
Freek de Kruijf composed on 2022-03-17 16:01 (UTC+0100):
Any suggestions?
Just a hunch, something I would try myself: If the ESP is formatted FAT16, reformat it FAT32. Another: resize it smaller than 5xxGB. All mine are 320MiB: |ID |ux|Dr|Type, description|Begin Sect|End sector| Cylinder range | Sectors | Size MiB | +--[/dev/nvme0n1 GPT disk 1]----------+----------+-------------------[<DISK LABEL> ]-+ |01 | | |Fsp + GPT hdr/pta| 22| 7ff| 0 - 0| 7de| 1.0| |01 | 1| |EFI System (ESP)| 800| a07ff| 1 - 320| a0000| 320.0| -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2022-03-17 16:01, Freek de Kruijf wrote:
Op donderdag 17 maart 2022 05:19:16 CET schreef Andrei Borzenkov:
You installed openSUSE in legacy mode while your Windows is most likely installed in EFI mode. You need to install openSUSE and Windows in the same mode for dual-boot support.
It went wrong at the moment I needed to fiddle in the BIOS to boot the iso image on the USB stick. I did not have enough knowledge about what these different options in the BIOS are.
Unfortunately I made it worse.
Now I have the BIOS configured on UEFI and Secure Boot: OFF
If they are off, and Windows was installed when they were ON, you will not be able to boot Windows again. You must put them back to ON, and then reinstall Linux from scratch, or adapt them, but not trivial. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Op donderdag 17 maart 2022 18:54:06 CET schreef Carlos E. R.:
On 2022-03-17 16:01, Freek de Kruijf wrote:
Op donderdag 17 maart 2022 05:19:16 CET schreef Andrei Borzenkov:
You installed openSUSE in legacy mode while your Windows is most likely installed in EFI mode. You need to install openSUSE and Windows in the same mode for dual-boot support.
It went wrong at the moment I needed to fiddle in the BIOS to boot the iso image on the USB stick. I did not have enough knowledge about what these different options in the BIOS are.
Unfortunately I made it worse.
Now I have the BIOS configured on UEFI and Secure Boot: OFF
If they are off, and Windows was installed when they were ON, you will not be able to boot Windows again. You must put them back to ON, and then reinstall Linux from scratch, or adapt them, but not trivial.
The situation is such that I can not boot any of the systems on the storage device. I can only boot from the USB device and I have access to that device, but I need an entry in the BIOS to boot from that device. The only option I see and will try, if there is no other way, is to (re)install Windows. Hopefully I can use a recover option of the Windows installation iso to get that entry in the BIOS. First thing tomorrow. -- fr.gr. member openSUSE Freek de Kruijf
participants (5)
-
Andrei Borzenkov -
Bengt Gördén -
Carlos E. R. -
Felix Miata -
Freek de Kruijf