Page 1 of 1
Grub doesn't recognize Win11 anymore
Posted: Sat Dec 30, 2023 6:28 pm
by pete67
Hi,
I installed MX-23.1 over MX 21.3 and everything went good so far.
But one issue appears which is very annoying.
Grub doesn't recognize Win11 anymore and I need it in the Dualboot with MX-Linux as I'm learning right now the programing language Python and I have to program in a Linux environment as well as in a Windows environment.
I searched the forum but I didn't find a thread for this serious issue.
Does anybody know, how to solve this annoying problem and what to do that grub recognizes Win11 as a Dualboot system again.
Greetings Peter
Re: Grub doesn't recognize Win11 anymore
Posted: Sat Dec 30, 2023 6:35 pm
by j2mcgreg
We are going to need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules
Re: Grub doesn't recognize Win11 anymore
Posted: Sat Dec 30, 2023 6:39 pm
by pete67
Ah ok, I forgot about that.
Code: Select all
[CODE]System:
Kernel: 6.6.7-1-liquorix-amd64 [6.6-8~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.6.7-1-liquorix-amd64
root=UUID=<filter> ro resume=UUID=<filter> resume_offset=854016
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
dm: LightDM v: 1.26.0 Distro: MX-23.1_ahs_x64 Libretto October 15 2023 base: Debian GNU/Linux
12 (bookworm)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME Z370-P v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 3004 date: 07/12/2021
CPU:
Info: model: Intel Core i5-8600K bits: 64 type: MCP arch: Coffee Lake gen: core 8 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xA (10)
microcode: 0xF4
Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB
L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB desc: 1x9 MiB
Speed (MHz): avg: 803 high: 819 min/max: 800/3601 boost: enabled scaling: driver: acpi-cpufreq
governor: ondemand cores: 1: 800 2: 800 3: 800 4: 800 5: 819 6: 800 bogomips: 43200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: disabled, RSB filling,
PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: Micro-Star MSI driver: nvidia
v: 525.147.05 non-free: 530.xx+ status: current (as of 2023-03) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s bus-ID: 01:00.0 chip-ID: 10de:2504 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
Monitor-1: DP-2 res: 2560x1440 hz: 60 dpi: 93 size: 700x390mm (27.56x15.35")
diag: 801mm (31.55") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.147.05 renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
Device-2: NVIDIA GA106 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.1
chip-ID: 10de:228e class-ID: 0403
API: ALSA v: k6.6.7-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 04:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-9:6 chip-ID: 0bda:8771
class-ID: e001 serial: <filter>
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
sub-v: d922 hci-v: 5.1 rev: dfc6
Info: acl-mtu: 1021:6 sco-mtu: 255:12 link-policy: rswitch hold sniff park
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
RAID:
Hardware-1: Silicon Image SiI 3132 Serial ATA Raid II Controller driver: sata_sil24 v: kernel
port: c000 bus-ID: 06:00.0 chip-ID: 1095:3132 rev: N/A class-ID: 0104
Drives:
Local Storage: total: 10.01 TiB used: 1.72 TiB (17.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 3B4QFXO7 temp: 27.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 3B4QFXO7 temp: 29.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: HD103UJ size: 931.51 GiB block-size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1118 scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: HD103UJ size: 931.51 GiB block-size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1118 scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 QVO 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
scheme: GPT
ID-6: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD serial: <filter> rev: 4B6Q
scheme: GPT
ID-7: /dev/sde maj-min: 8:64 type: USB vendor: Western Digital model: WD50NDZW-11BCSS1
size: 4.55 TiB block-size: physical: 4096 B logical: 512 B type: HDD rpm: 4800 serial: <filter>
rev: 4010 scheme: GPT
Partition:
ID-1: / raw-size: 931.26 GiB size: 915.57 GiB (98.31%) used: 52.17 GiB (5.7%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 411 KiB (0.2%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 37.28 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 32.0 C mobo: N/A gpu: nvidia temp: 40 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos:
Packages: pm: dpkg pkgs: 2850 libs: 1538 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm ahs
Info:
Processes: 352 Uptime: 51m wakeups: 1 Memory: 31.3 GiB used: 3.18 GiB (10.2%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
[/code]
Re: Grub doesn't recognize Win11 anymore
Posted: Sat Dec 30, 2023 8:22 pm
by fehlix
pete67 wrote: Sat Dec 30, 2023 6:28 pm
I installed MX-23.1 over MX 21.3 and everything went good so far.
What is "installed ... over " ? Was it a fresh and clean install, or something else?
Re: Grub doesn't recognize Win11 anymore
Posted: Sun Dec 31, 2023 5:07 am
by pete67
@fehlix ,instead of upgrading from 21.3, I ran the MX-Tool User Installed Packages before the fresh installation and copied the result to my "Austausch"-drive as a precaution to make sure that I can find this list later in case something goes wrong.
Then I downloaded MX-23.1_ahs_x64.iso and created it on a USB stick with MX-Live-USB as a live system.
Then I ran the installation from the USB stick as a boot medium as normal and entered my previous user when prompted for the user.
The installation went through with the standard Debian kernel and after I had started the system now running on 23.1, I installed the current liquorix kernel 6.6-8~mx23ahs, as I had installed before.
Then I called up the MX boot options and switched off the splash and set the notifications to "very detailed".
To be on the safe side, I called up the MX Boot Repair and ran it with the option "Reinstall the GRUB boot program in ESP, MBR or PBR (root)" and then selected "ESP" under "install on:" and selected the correct EFI partition as the location, as I always did when I installed a Linux system next to Win11 to have GRUB recognize the Win11 UEFI installation.
Unfortunately, this did not work and the Win11 installation is not recognized by GRUB as usual and is therefore no longer bootable.
Win11 is on ID-2: /dev/nvme1n1 but is no longer recognized.
Re: Grub doesn't recognize Win11 anymore
Posted: Sun Dec 31, 2023 7:44 am
by fehlix
pete67 wrote: Sun Dec 31, 2023 5:07 am
@fehlix ,instead of upgrading from 21.3, I ran the MX-Tool User Installed Packages before the fresh installation and copied the result to my "Austausch"-drive as a precaution to make sure that I can find this list later in case something goes wrong.
Then I downloaded MX-23.1_ahs_x64.iso and created it on a USB stick with MX-Live-USB as a live system.
Then I ran the installation from the USB stick as a boot medium as normal and entered my previous user when prompted for the user.
The installation went through with the standard Debian kernel and after I had started the system now running on 23.1, I installed the current liquorix kernel 6.6-8~mx23ahs, as I had installed before.
Then I called up the MX boot options and switched off the splash and set the notifications to "very detailed".
To be on the safe side, I called up the MX Boot Repair and ran it with the option "Reinstall the GRUB boot program in ESP, MBR or PBR (root)" and then selected "ESP" under "install on:" and selected the correct EFI partition as the location, as I always did when I installed a Linux system next to Win11 to have GRUB recognize the Win11 UEFI installation.
Unfortunately, this did not work and the Win11 installation is not recognized by GRUB as usual and is therefore no longer bootable.
Win11 is on ID-2: /dev/nvme1n1 but is no longer recognized.
Preliminary remark:
The issue is reported appears to me posted within the wrong forum section,
b/c it looks more like Help-Request rather then a Bug Report.
UEFI systems do have their own way to boot into other OS
by means of UEFI Boot Options list.
Booting into other OS is an option provided by GRUB,
which was in Debian-12 now set as an optional feature and no longer
enabled as default.
OK, Please try in this order:
* Reboot and select from UEFI Boot Options list the WIndows UEFI entry.
You normally get this UEFI boot options list after pressing/tapping an Fn-key (F12? or similar)
during early boot (aka POST)
After booted into Win11, hold the Shift key and select Power off,
This should make win11 power off properly in case the hybrid-sleep poweroff mode was not disabled.
They call it something like FastStartup or similar.
* Next boot into MX Linux
Open command line as normal user and run:
Make sure you select the option to run "Run os-prober automatically to detect and boot other OS".
Select the shown text in the terminal and post here.
HTH
Re: Grub doesn't recognize Win11 anymore
Posted: Sun Dec 31, 2023 10:14 am
by pete67
@fehlix ,
I've done as you told me but in the boot-order in my UEFI-Bios I couldn't find the Win11-NVMe anymore to boot from. It seams that the UEFI-Bios doesn't recognize the bootmgfw.efi which I see in thunar in the mounted Win11-NVMe under Windows/Boot/EFI/bootmgfw.efi
and under Program Files (x86)/AOMEI/bootmgfw.efi --> this is the version of the file which is the target as AOMEI is the recovery stage before booting Win11 in case that Win11 would not boot anymore so that I could restore a saved version out of AOMEI Backupper which is the Backup-Software I use in Win11 and where I have saved security images on a external USB-Drive.
So
shows me that
Code: Select all
$ sudo dpkg-reconfigure grub-pc
[sudo] Passwort für tuxpete:
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-6.6.7-1-liquorix-amd64
Found initrd image: /boot/initrd.img-6.6.7-1-liquorix-amd64
Found linux image: /boot/vmlinuz-6.5.0-1mx-ahs-amd64
Found initrd image: /boot/initrd.img-6.5.0-1mx-ahs-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Adding boot menu entry for EFI firmware configuration
done
although I chose "Run os-prober automatically to detect and boot other OS"
So I goggled a bit and found another possible solution.
In case that os-prober is not working as it hasn't found the win11-bootmgfw.efi Files whether under Windows/boot/EFI nor under Program Files (x86)/AOMEI/ there is another possibility:
To edit
/etc/grub.d/40_custom
and insert under the
exec tail -n +3 $0
the following:
Code: Select all
menuentry 'Windows 11 Pro' {
search --fs-uuid --set=root $uuid
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
Additionally I've looked up the UUIDs on my system with "blkid"
Code: Select all
$ blkid
/dev/nvme0n1p2: LABEL="NVMe-SSD_980_Games" BLOCK_SIZE="512" UUID="3860FBFB60FBBE26" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="94094084-1aa0-47a4-a911-a3b485a99a5f"
/dev/sdd1: LABEL="Samsung_860_EVO_SATA-SSD" BLOCK_SIZE="512" UUID="7C50627A50623B52" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="17c6efda-f458-4a4b-8aaf-bd5159d5dbbe"
/dev/sdb1: LABEL_FATBOOT="Austausch" LABEL="Austausch" UUID="CB1B-933E" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="da5b4055-78d9-11ed-91fc-1831bf25e70a"
/dev/sdc2: LABEL="Samsung_870_QVO_SATA-SSD" BLOCK_SIZE="512" UUID="1C4C54294C53FFC6" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="e0c1e71a-bc60-4e17-874b-41e3820eb3e6"
/dev/nvme1n1p2: LABEL="NVMe_SSD_Windows" BLOCK_SIZE="512" UUID="068CFCA08CFC8C05" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="33ac05b4-5a9a-4029-9dd4-f5446e42fea5"
/dev/nvme1n1p3: BLOCK_SIZE="512" UUID="CC08738808736FF6" TYPE="ntfs" PARTUUID="1f5388da-d72d-427c-91b1-25bc86c114be"
/dev/sda2: LABEL="rootMX23" UUID="4e77752f-8b89-414c-be14-fa342c0915bf" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="ef2f731e-22d6-49d8-a106-ff24d2947a3e"
/dev/sda1: LABEL_FATBOOT="EFI-SYSTEM" LABEL="EFI-SYSTEM" UUID="32DC-956D" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="c5071425-43ab-48c7-bc57-4b64f5ce1320"
So I assume I could try it with the UUID "068CFCA08CFC8C05" but I'm unsure how to name the chainloader command due to the target "under Program Files (x86)/AOMEI/bootmgfw.efi"
But if that is not possible to take for the chainloader command I assume to take the standard under
Code: Select all
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
What do you think about that as
doesn't find the Win11-OS?
Re: Grub doesn't recognize Win11 anymore
Posted: Sun Dec 31, 2023 10:36 am
by kris777
Re: Grub doesn't recognize Win11 anymore
Posted: Sun Dec 31, 2023 12:30 pm
by fehlix
UEFI would normally not boot from ntfs but rather boots from vfat/fat23 ESP.
A grub menu entry could be injected with a custom.cfg file like this one
Code: Select all
# name: custom.cfg
# file: /boot/grub/custom.cfg
menuentry 'Windows' {
insmod fat
insmod chain
insmod part_gpt
search --no-floppy --set=root --fs-uuid 32DC-956D
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
The uuid shown is the one from the ESP within your example above.
In case it's still not working, do try/check whether
on the MX LiveUSB Boot Menu ->Boot Rescue Menu -> Windows boot loader
would find the window efi-loader or not. You need to use a MX Live USB as ISO-dump,
or with MX Live USB Maker made. Rufus made USB's might work , Ventoy probaly would not work
with the "Boot Rescue Menu".
In case LiveUSB->Boot Rescue would still not find Window boot loader,
I guess something is wrong with you windows.
Some hints was given already like disable faststart.
And also regenerating WIndows boot loder with help of WIndows own tools was suggested.
Re: Grub doesn't recognize Win11 anymore
Posted: Sun Dec 31, 2023 4:02 pm
by jbernardo
Stupid question - you have checked /etc/default/grub, and set "GRUB_DISABLE_OS_PROBER=false"? On my upgrade from 21.3 that was set to TRUE, and of course it would not find the windows install...
Re: Grub doesn't recognize Win11 anymore
Posted: Sun Dec 31, 2023 4:12 pm
by Charlie Brown
Maybe for sata mode is set to Raid ...
(However if you turn it to Ahci, this time it won't be able to boot Windows even if it detects it. Therefore you need to first boot into Windows indirectly (this or that way) then do the
change in Regedit)
Re: Grub doesn't recognize Win11 anymore
Posted: Mon Jan 01, 2024 10:01 am
by pete67
@jbernardo OS_PROBER is set to false in
Code: Select all
#run dpkg-reconfigure grub-pc to allow toggle of os-prober
GRUB_DISABLE_OS_PROBER=false
if [ -e /etc/default/grub.mx-defaults ]; then
. /etc/default/grub.mx-defaults
fi
GRUB_THEME="/boot/grub/themes/mx_linux/theme.txt"
GRUB_SAVEDEFAULT=true
GRUB_DISABLE_OS_PROBER=false
Re: Grub doesn't recognize Win11 anymore
Posted: Mon Jan 01, 2024 10:03 am
by pete67
@Charlie Brown no the sata mode is definitely set to AHCI. I don't use Raid and will never do.
Re: Grub doesn't recognize Win11 anymore
Posted: Mon Jan 01, 2024 10:42 am
by Charlie Brown
Ok, just.. the qsi shows it like that:
Code: Select all
...
RAID:
Hardware-1: Silicon Image SiI 3132 Serial ATA Raid II Controller ... bus-ID: 06:00.0 chip-ID: 1095:3132 ...
Drives:...
Re: Grub doesn't recognize Win11 anymore
Posted: Mon Jan 01, 2024 10:55 am
by kris777
Re: Grub doesn't recognize Win11 anymore
Posted: Mon Jan 01, 2024 10:59 am
by Charlie Brown
Yes, that's telling the custom entry we mentioned above. In case nothing works (it doesn't detect it by itself) that's doable. In case you follow those instructions you can skip the chmod ...custom.cfg steps as they're already present and executable ...
Re: Grub doesn't recognize Win11 anymore
Posted: Mon Jan 01, 2024 1:04 pm
by fehlix
OK, first check whether it is an RAID issue or not:
Please run this command from terminal as normal user:
Will it recognize WIndows installation or not?
If not, suggest to disbale RAID and change to SATA/AHCI with in the UEFI System Setup.
If yes:
Do run again:
and tick "Enable othe OS ...
Will it recognize WIndows installation now with the 2nd run?
Next:
Within the last section of /etc/default/grub:
Code: Select all
#run dpkg-reconfigure grub-pc to allow toggle of os-prober
GRUB_DISABLE_OS_PROBER=false
if [ -e /etc/default/grub.mx-defaults ]; then
. /etc/default/grub.mx-defaults
fi
GRUB_THEME="/boot/grub/themes/mx_linux/theme.txt"
GRUB_SAVEDEFAULT=true
GRUB_DISABLE_OS_PROBER=false
do remove the 2nd entry the - last line with GRUB_DISABLE_OS_PROBER=false,
otherwise a next GRUB upgrade won't detect any other OS,
due to Debian's special handling to disable os-prober
during upgrade, regardless of the setting found in /etc/default/grub.
Please report back.
Thanks
Re: Grub doesn't recognize Win11 anymore
Posted: Tue Jan 02, 2024 5:47 am
by pete67
First of all a happy new year and thank's for all the help and tips you all are giving me to solve the mystery of the disappeared Win11-Boot-Grub-Listing.
I have analyzed my system with an supergrub-USB-Stick and this is what it has shown me and what for a Sata-Setting I have in my UEFI-Bios and whats making me wonder why linux sees in as a raid.
https://imgur.com/a/R5Ll8jv
The supergrub analyze shows clearly that the two NVMe-Drives are bond to a raid although I never had set such a setting and even don't know where I could set it in my UEFI-Bios as the only option to set a raid is to set SATA-Drives as a Raid and as one can see it isn't set to raid but to AHCI!
I really don't understand what's going on there and how can this happen.
I have two separate NVMe's both 1 GB and from Samsung "Samsung SSD 980" and it seems that the UEFI-Bios set then as a Raid.
I can set a SSD 980 as first boot medium but it doesn't find the boot manager and yesterday evening I tried to boot from a AOMEI-Recovery-Stick and after it shows it is loading drivers nothing happened and the screen stays black. This is a additional sign, that at the moment even the UEFI-Bios doesn't recognize two SSDs but both as one.
Re: Grub doesn't recognize Win11 anymore
Posted: Tue Jan 02, 2024 8:22 am
by pete67
I will now try to set the whole UEFI-Bios back by hardware-setback and will remove the battery for about 20 Sec. and shorten the 2-pol CLRTC Header.
Afterwards I will load the optimized settings in the uefi-bios and will see if this time the bios is recognizing the TWO SSDs and not only one and that in the overview where you see the most common data in the field M2.1 there will appear the window-ssd separately. I assume as long as the bios isn't correctly detecting TWO separately SSD's one with windows 11 and the second with my game-Files everything else will not help solving this problem.
Re: Grub doesn't recognize Win11 anymore
Posted: Mon Jan 15, 2024 10:03 am
by pete67
Hi, During the Christmas holidays I reinstalled Win11 using a Win10 installation stick by simply restoring the last Aomei backup of the Win11 installation after installing Win10.
During the installation of Win10, the two NVMe drives were recognized correctly again, since I had previously reset the UEFI bios via battery removal and jumper shorting.
I am now so far advanced in my Python course that I will soon be programming under Linux.
However, before I reactivate MX 23.1 with Grub, I want to make sure that this time the Win1 boot manager is recognized correctly under Debian Bookworm and integrated into Grub.
As far as I have understood the procedure described by you in the thread, the 40_Custom file must be populated with the Win11 boot entry due to the deactivation of the OS prober function under Debian Bookworm in Grub 2.
To do this, I have to boot with an MX live stick and switch to the MX 23.1 installation in the live system and populate the 40 custom file with the search parameters for the Win11 boot manager. Then rebuild Grub. Display the Grub content so that the Win11 boot manager really appears and then reboot MX 23.1 and see if Grub now also displays Win11 and you can boot it.
Is that correct?
Re: Grub doesn't recognize Win11 anymore
Posted: Mon Jan 15, 2024 12:18 pm
by fehlix
pete67 wrote: Mon Jan 15, 2024 10:03 am
As far as I have understood the procedure described by you in the thread, the 40_Custom file must be populated with the Win11 boot entry due to the deactivation of the OS prober function under Debian Bookworm in Grub 2.
...
Is that correct?
Probably not, b/c in MX Linux OS prober was activated again.
So after installing the GRUB menu should already have an entry for Windows.
In case it could not detect windows during installation,
and windows was properly shutdown (with no windows fast-boot)
Rerunning update grub either this way:
sudo update-grub
or with
sudo dpkg-reconfigure grub-pc
is supposed to add the missing entry.
Re: Grub doesn't recognize Win11 anymore
Posted: Sun Jan 28, 2024 9:32 am
by pete67
Hi @fehlix ,
so at the moment, Win11 starts automatically, as this was the only OS entered in the EFI partition during the restore.
So I boot with my MX-Live stick and then have to rebuild Grub 2 in MX-Linux on the existing partition of MX 23.1.
If I understood your post correctly, in the latest version of MX Linux 23.1 I had updated my "old" 21.3 despite the Debian Bookworm based on the 23.1 OS prober is still active, although Debian no longer supports it.
I'm so suspicious because the thread said several times that OS-Prober doesn't work anymore because Debian Bookworm has disabled it and I don't want to fall into the trap again that the bootloader of Win11 is not recognized again, no matter what I do.
Re: Grub doesn't recognize Win11 anymore
Posted: Sun Jan 28, 2024 9:43 am
by fehlix
Maybe a misunderstanding: Debian had disabled os-prober on automatic re-genration of the grub menu,
e.g during/after kernel upgrade/install. But user can re-enable always using the dppk-reconfigure command shown above. The MX adjustment made would probably also have the regenerate working during kernel upgrade.
Of course, all depends whether some manually changes with the grub-setup have been made by the user and disturbed the finetuned changes made, or potentially even worse, in case grub-customizer would be in use.
Re: Grub doesn't recognize Win11 anymore [Solved]
Posted: Sat Jul 06, 2024 5:11 pm
by pete67
Meanwhile Wingarbage 11 has decided to crash totally and to kill it EFI-Partition or write such a xxxxxxx in it, that even my Supergrub-Stick doesn't find it anymore. So let this xxxxxxx be dead and gone. As MS decided to give us all Co-Pilos and Recall they can kiss me where no sun shines. So I close this thread as obsolete.