on my laptop 1=ASUS vivobook pro N552VW-FY204T (2016) with freshly installed leap 16.0 with KDE
in the installation via agama I leaved untouched my windows partitions with windows11
how can I do so that grub recognise the installed windows11 partition so I can find the windows boot option in grub?
@pier_andreit what does cat /etc/default/grub | grep GRUB_DISABLE_OS_PROBER show, what does the output from os-prober show?
here is
eros@localhost:~> cat /etc/default/grub | grep GRUB_DISABLE_OS_PROBER
GRUB_DISABLE_OS_PROBER="false"
eros@localhost:~> and
eros@localhost:~> os-prober
unshare failed: Operation not permitted
/usr/bin/os-prober: line 105: blkid: command not found
/usr/bin/os-prober: line 192: blkid: command not found
/usr/bin/os-prober: line 192: blkid: command not found
/usr/bin/os-prober: line 192: blkid: command not found
/usr/bin/os-prober: line 192: blkid: command not found
/usr/bin/os-prober: line 192: blkid: command not found
/usr/bin/os-prober: line 192: blkid: command not found
/usr/bin/os-prober: line 192: blkid: command not found
/usr/bin/os-prober: line 192: blkid: command not found
eros@localhost:~> The os-prober command needs to be done as root user…
here is
eros@localhost:~> su -
Password:
localhost:~ # os-prober
5733.281253 | DM multipath kernel driver not loaded
localhost:~ # @pier_andreit seems you have hit this issue before?
https://forums.opensuse.org/t/windows-os-not-present-in-grub-menu/176217
If you press the BIOS boot menu key, does it see “Windows Boot Manager”?
I see (on Tumbleweed with grub-bls);
os-prober
36.006393 | DM multipath kernel driver not loaded
/dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
uh, it was in 2024 and din’t remembered, if it isn’t changed anything in leap 16.0 can I try to do the same things?
no I don’t see windows boot manager, only [opensuse secureboot…] and [opensuse PO: HFS51…]
@pier_andreit then you likely formatted the EFI partition like last time, same step should work from that other thread, but you never updated that one with success or not…
maybe yes, I should have made a bit of mess with agama options, it needs very much attention and has many bugs that lead to fail, I don’t remember what I did in 2024 other thread but as I have all the laptops with windows I suppose I did with success
So have you checked the outputs requested in the other thread?
lsblk
efibootmgr -v
ls -la /boot/efi/EFI
fdisk -l /dev/sda
just now
eros@localhost:~> su -
Password:
localhost:~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 476.9G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
├─sda3 8:3 0 16M 0 part
├─sda4 8:4 0 57.7G 0 part
├─sda5 8:5 0 761M 0 part
├─sda6 8:6 0 58.6G 0 part /
├─sda7 8:7 0 29.3G 0 part /home
├─sda8 8:8 0 31.3G 0 part [SWAP]
└─sda9 8:9 0 298.7G 0 part /dati
sdb 8:16 0 465.8G 0 disk
└─sdb1 8:17 0 465.8G 0 part /run/media/eros/backup5
sr0 11:0 1 1024M 0 rom
localhost:~ # localhost:~ # efibootmgr -v
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0000* opensuse-secureboot HD(1,GPT,679a78ab-37da-4945-b2a8-29b9f3ac4e5d,0x800,0x100000)/File(\EFI\OPENSUSE\SHIM.EFI)
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 ab 78 9a 67 da 37 45 49 b2 a8 29 b9 f3 ac 4e 5d 02 02 / 04 04 32 00 5c 00 45 00 46 00 49 00 5c 00 4f 00 50 00 45 00 4e 00 53 00 55 00 53 00 45 00 5c 00 53 00 48 00 49 00 4d 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
Boot0001* opensuse HD(1,GPT,679a78ab-37da-4945-b2a8-29b9f3ac4e5d,0x800,0x100000)/File(\EFI\OPENSUSE\GRUBX64.EFI)0000424f
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 ab 78 9a 67 da 37 45 49 b2 a8 29 b9 f3 ac 4e 5d 02 02 / 04 04 38 00 5c 00 45 00 46 00 49 00 5c 00 4f 00 50 00 45 00 4e 00 53 00 55 00 53 00 45 00 5c 00 47 00 52 00 55 00 42 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
data: 00 00 42 4f
localhost:~ # localhost:~ # ls -la /boot/efi/EFI
total 16
drwxr-xr-x 4 root root 4096 Feb 4 18:03 .
drwxr-xr-x 3 root root 4096 Jan 1 1970 ..
drwxr-xr-x 2 root root 4096 Feb 4 18:03 boot
drwxr-xr-x 2 root root 4096 Feb 4 18:03 opensuse
localhost:~ # localhost:~ # fdisk -l /dev/sda
Disk /dev/sda: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: HFS512G39MND-351
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: B7450440-725E-44B6-BA4B-C1E7E4B61E11
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda3 1230848 1263615 32768 16M Microsoft reserved
/dev/sda4 1263616 122345471 121081856 57.7G Microsoft basic data
/dev/sda5 122345472 123903999 1558528 761M Windows recovery environment
/dev/sda6 123906048 246786047 122880000 58.6G Linux filesystem
/dev/sda7 246786048 308226047 61440000 29.3G Linux filesystem
/dev/sda8 308226048 373762047 65536000 31.3G Linux swap
/dev/sda9 373762048 1000214527 626452480 298.7G Microsoft basic data
localhost:~ # and this was the fdisk -lx before to install 16.0 where I note /dev/sda2 that now there isn’t, could it be the windows boot partition and I wander that I car recovery it in spite of the different end of /dev/sda2 1050623 now and 1026047 before
Device Start End Sectors Type-UUID UUID Name Attrs
/dev/sda1 2048 1026047 1024000 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 AEE9C626-69B9-433E-B849-994A886011BB nEFI
/dev/sda2 1026048 1230847 204800 C12A7328-F81F-11D2-BA4B-00A0C93EC93B 214D1A7A-AB7B-4C0F-801E-5D8935C9AB46 EFI system partition
/dev/sda3 1230848 1263615 32768 E3C9E316-0B5C-4DB8-817D-F92DF00215AE 69210CD3-6B32-458A-845C-065969CDD4E5 Microsoft reserved partition
/dev/sda4 1263616 122345471 121081856 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 28904F0D-9574-40A6-8DEB-03A9E0692ECD Basic data partition
/dev/sda5 122345472 123903999 1558528 DE94BBA4-06D1-4D40-A16A-BFD50179D6AC EC5D5565-75C0-4149-B77C-0CB1841F5451 RequiredPartition
/dev/sda6 123906048 246786047 122880000 0FC63DAF-8483-4772-8E79-3D69D8477DE4 715E40B1-4154-4C49-9593-CD05149CBFA2 nSUSE1
/dev/sda7 246786048 308226047 61440000 0FC63DAF-8483-4772-8E79-3D69D8477DE4 57B9B075-B304-4206-87D4-39C054BD0789 nHOME1
/dev/sda8 308226048 373762047 65536000 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F C06A39E6-1587-40B7-9FC7-28BEBA0BFFD2 nSWAP
/dev/sda9 373762048 1000214527 626452480 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 0A8C3B0D-BEA0-4427-8659-728D8428AF57 nDATI @pier_andreit So you wiped the Windows Boot partition, so just follow those instructions in the other thread to re-create? Windows and Linux are happy to share the same efi partition, so I would not worry about sda2…
2 Likes
Hi, I tried this:
booted with windows11 usb stick
selected to use prompt
diskpart
from diskpart
list volume
identify the disk (for me was easy by size)
it is hidden so I assign a letter
identify the volume number, mine was volume 3
select volume 3
assign letter Z
exit
bcdboot C:\Windows /s Z: /f UEFI
now pressing the BIOS boot menu key I can see “Windows Boot Manager”
but I cannot see in the grub menu
selecting in the bios windows boot manager windows try to boot but didn’t works, I suppose this is a windows related problem that I’ll try to solve o to reinstall windows
here something you asked me before:
eros@localhost:~> su -
Password:
localhost:~ # os-prober
271.426444 | DM multipath kernel driver not loaded
/dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
localhost:~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 476.9G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
├─sda3 8:3 0 16M 0 part
├─sda4 8:4 0 57.7G 0 part
├─sda5 8:5 0 761M 0 part
├─sda6 8:6 0 58.6G 0 part /
├─sda7 8:7 0 29.3G 0 part /home
├─sda8 8:8 0 31.3G 0 part [SWAP]
└─sda9 8:9 0 298.7G 0 part /dati
sdb 8:16 0 465.8G 0 disk
└─sdb1 8:17 0 465.8G 0 part
sr0 11:0 1 1024M 0 rom
localhost:~ # cat /etc/default/grub | grep GRUB_DISABLE_OS_PROBER
GRUB_DISABLE_OS_PROBER="false"
localhost:~ #
how can I see windows boot manager in my grub menu??
@pier_andreit If you run the command os-prober does it see windows? (I see you did…)
If you run update-bootloader --config does it now appear in the Grub menu?
But if Windows is not booting, then could be the root cause…
manythanks, it works after update-bootloader --config windows appear in the grub menu
probably the not booting of windows is in the root windows, may be I’ll reinstall windows, if I remember well it will brake the grub, so with 15.6 I did boot the 15.6 by systemrescue and reinstall bootloader by yast, now what I have to do?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.