Grub doesn't recognize Win10 anymore [Solved]

[smilliken]

I seem to have the same prolbem, but with a Windows 10 install. I have 4 different kernels installed on the MX system and have tried to also delete the older ones, but this is still causing problems with Grub updating.

Code: Select all

(Reading database ... 375319 files and directories currently installed.)
Removing linux-image-6.1.0-12-amd64 (6.1.52-1) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-12-amd64
/etc/kernel/postrm.d/zz-update-grub:
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-6.1.0-17-amd64
Found initrd image: /boot/initrd.img-6.1.0-17-amd64
Found linux image: /boot/vmlinuz-6.1.0-14-amd64
Found initrd image: /boot/initrd.img-6.1.0-14-amd64
Found linux image: /boot/vmlinuz-6.1.0-13-amd64
Found initrd image: /boot/initrd.img-6.1.0-13-amd64
Found memtest86+x64 image: /boot/memtest86+x64.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
error: out of memory.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 294
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1
dpkg: error processing package linux-image-6.1.0-12-amd64 (--remove):
 installed linux-image-6.1.0-12-amd64 package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
 linux-image-6.1.0-12-amd64
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:

This is the ouput from Synaptic while trying to remove the older kernels. 6.1.0-17-amd64 is the kernel that has booted.

I've tried all of hte suggestion in the thread and still can't seem to get the grub updater to accept the Windows 10 drive. It recognizes that it is there, but I think there is a problem with the EFI. Don't think the BIOS is new enough to work with it.

Code: Select all

sudo dpkg-reconfigure grub-pc
[sudo] password for scott:       
grub-pc: Running grub-install ...
Installing for i386-pc platform.
grub-install: warning: File system `ext2' doesn't support embedding.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
Installation finished. No error reported.
  grub-install success for /dev/sda1
Installing for i386-pc platform.
grub-install: warning: Sector 33 is already in use by the program `FlexNet'; avoiding it.  This software may cause boot or other problems in future.  Please ask its authors not to store data in the boot track.
grub-install: warning: Sector 34 is already in use by the program `FlexNet'; avoiding it.  This software may cause boot or other problems in future.  Please ask its authors not to store data in the boot track.
Installation finished. No error reported.
  grub-install success for /dev/sdb
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-6.1.0-17-amd64
Found initrd image: /boot/initrd.img-6.1.0-17-amd64
Found linux image: /boot/vmlinuz-6.1.0-14-amd64
Found initrd image: /boot/initrd.img-6.1.0-14-amd64
Found linux image: /boot/vmlinuz-6.1.0-13-amd64
Found initrd image: /boot/initrd.img-6.1.0-13-amd64
Found memtest86+x64 image: /boot/memtest86+x64.bin
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.
Found Windows 10 on /dev/sdb1
error: out of memory.
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 307
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.

Code: Select all

sudo os-prober
/dev/sdb1:Windows 10:Windows:chain

Code: Select all

sudo blkid
/dev/sdb2: LABEL="Win 10" BLOCK_SIZE="512" UUID="4C746C0B746BF5DC" TYPE="ntfs" PARTUUID="9dc96e9e-02"

Not sure what I've missed here. I've tried the repair with a Live USB and it stated it completed with no errors, yet still doesn't work.

Any help greatly appreciated.

Code: Select all

System:    Kernel: 6.1.0-17-amd64 [6.1.69-1] x86_64 bits: 64 compiler: gcc v: 12.2.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-17-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.36 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-23.1_x64 Libretto January 15  2023 
           base: Debian GNU/Linux 12 (bookworm) 
Machine:   Type: Desktop Mobo: ASUSTeK model: P8Z68-V PRO v: Rev 1.xx serial: <filter> 
           BIOS: American Megatrends v: 3603 date: 11/09/2012 
CPU:       Info: Quad Core model: Intel Core i5-2500 bits: 64 type: MCP arch: Sandy Bridge 
           family: 6 model-id: 2A (42) stepping: 7 microcode: 2F cache: L2: 6 MiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 26485 
           Speed: 1605 MHz min/max: 1600/5900 MHz Core speeds (MHz): 1: 1605 2: 1600 3: 1605 
           4: 1642 
           Vulnerabilities: Type: gather_data_sampling status: Not affected 
           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 status: Unknown: No mitigations 
           Type: retbleed status: Not affected 
           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: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, 
           RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
           vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0102 
           class-ID: 0300 
           Display: x11 server: X.Org 1.21.1.7 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.0x11.2") 
           s-diag: 1055mm (41.5") 
           Monitor-1: HDMI-1 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") 
           diag: 686mm (27") 
           Monitor-2: HDMI-3 res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.5x13.2") 
           diag: 686mm (27") 
           OpenGL: renderer: Mesa Intel HD Graphics 2000 (SNB GT1) v: 3.3 Mesa 23.1.2-1~mx23ahs 
           direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403 
           Sound Server-1: ALSA v: k6.1.0-17-amd64 running: yes 
           Sound Server-2: PulseAudio v: 16.1 running: yes 
Network:   Device-1: Intel 82579V Gigabit Network vendor: ASUSTeK P8P67 Deluxe driver: e1000e 
           v: kernel port: f080 bus-ID: 00:19.0 chip-ID: 8086:1503 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel modules: wl 
           port: f040 bus-ID: 03:00.0 chip-ID: 8086:2725 class-ID: 0280 
           IF: wlan1 state: up mac: <filter> 
           Device-3: Qualcomm Atheros AR2413/AR2414 Wireless Network Adapter [AR5005G 802.11bg] 
           vendor: D-Link System WDA-1320 driver: ath5k v: kernel port: e000 bus-ID: 07:01.0 
           chip-ID: 168c:001a class-ID: 0200 
           IF: wlan0 state: down mac: <filter> 
Bluetooth: Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-1.5:4 
           chip-ID: 8087:0032 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> 
           Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff 
           link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony 
Drives:    Local Storage: total: 1.17 TiB used: 208.18 GiB (17.4%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD6400AAKS-00A7B0 
           size: 596.17 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A 
           serial: <filter> rev: 3B01 scheme: MBR 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD6400AAKS-22A7B0 
           size: 596.17 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A 
           serial: <filter> rev: 3B01 scheme: MBR 
           ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Lexar model: USB Flash Drive 
           size: 7.48 GiB block-size: physical: 512 B logical: 512 B type: SSD serial: <filter> 
           rev: 1100 scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition: ID-1: / raw-size: 50.08 GiB size: 48.99 GiB (97.83%) used: 14.14 GiB (28.9%) fs: ext4 
           dev: /dev/sda1 maj-min: 8:1 
           ID-2: /home raw-size: 543.91 GiB size: 534.3 GiB (98.23%) used: 59.17 GiB (11.1%) 
           fs: ext4 dev: /dev/sda3 maj-min: 8:3 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 2.18 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sda2 maj-min: 8:2 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2197 lib: 1087 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           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/hashicorp.list 
           1: deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com/ bookworm main
           No active apt repos in: /etc/apt/sources.list.d/meganz-deb12.list 
           Active apt repos in: /etc/apt/sources.list.d/megasync.list 
           1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_12/ ./
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bookworm non-free main
           2: deb http://mxrepo.com/mx/repo/ bookworm ahs
           Active apt repos in: /etc/apt/sources.list.d/virtualbox.list 
           1: deb [arch=amd64 signed-by=/usr/share/keyrings/oracle_vbox_2016.gpg] https://download.virtualbox.org/virtualbox/debian/ bookworm contrib
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 271 Uptime: 2m wakeups: 1 Memory: 15.33 GiB used: 2 GiB (13.1%) 
           Init: SysVinit v: 3.06 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 12.2.0 
           alt: 10/12 Client: shell wrapper v: 5.2.15-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

[fehlix]

I seem to have the same prolbem, but with a Windows 10 install.

Nope, looks to me like a different problem.
Please don't hijack other user threads.
Can someone move this into it's own thread please.
Thanks

[Eadwine Rose]

Done!

As fehlix said: don't tack onto other peoples' threads, start your own.

[fehlix]

I seem to have the same prolbem, but with a Windows 10 install. I have 4 different kernels installed on the MX system and have tried to also delete the older ones, but this is still causing problems with Grub updating.

OK, I may see a couple of potential issue.
Maybe you mention how was MX Linux installed and Windows.
I mean is it fresh install or a so called upgrade or migration.
Did it just happen out of the blue. No other substantialy changes from your side. ("Operators error.")
A couple of things can be "detected" from the pieces shown after the accident.
But I prefer to get a better picture of the accident before issuing a sickness certificate and prescribing a prescription.

[smilliken]

I seem to have the same prolbem, but with a Windows 10 install. I have 4 different kernels installed on the MX system and have tried to also delete the older ones, but this is still causing problems with Grub updating.

OK, I may see a couple of potential issue.
Maybe you mention how was MX Linux installed and Windows.
I mean is it fresh install or a so called upgrade or migration.

It was an install from an Live USB saving the home directory. IOnstalled several months ago, now.

Did it just happen out of the blue. No other substantialy changes from your side. ("Operators error.")
A couple of things can be "detected" from the pieces shown after the accident.
But I prefer to get a better picture of the accident before issuing a sickness certificate and prescribing a prescription.

None noted. Don't believe it reconzised the Windows drive after the installation, come to think of it.

[fehlix]

Maybe post these files:
This
/etc/default/grub
and all of those:
/etc/grub.d/*
and this
/boot/grub/grub.cfg.new
preferable as zip- or any other archive file.

[smilliken]

boot-grub-grub-cfg-new.zip

etc-grub-d.zip

etc-default-grub.zip

[fehlix]

OK, something went wrong ...
Main show stopper is within this file /etc/grub.d/40_custom
where a failing attempt is visible to add a Windows boot entry to grub menu,
which finally made postinstall of the kernel fail.

Propose this :

1.) reset /etc/grub.d/40_custom

Code: Select all

sudo cp /usr/local/share/live-files/files/etc/grub.d/40_custom /etc/grub.d/40_custom

and re-run

Code: Select all

sudo dpkg-reconfigure grub-pc

here do click/enable "os prober ..."
and further select only the drive sda where MX Linux is installed on:
/dev/sda
don't select any partitions like sda1 or sdb1 etc.
++EDIT+++
As you already selected also /dev/sdb
do now also select both /dev/sda and /dev/sdb
+++++++

And probably finalize the failing installs:

Code: Select all

sudo apt update

and

Code: Select all

sudo apt install -f

Maybe that's already the fix, please report. Otherwise some more files need to be reset.

[smilliken]

Thanks for the help @fehlix, the GRUB menu is fix and the the computer will boot into Windows, sort of. I'm able to enter the PIN and the desktop shows up, less the icons and there is something happening in the back ground as there is an blue circular icon spinng nonstop.

I'll have to do some diggin on this end, but thanks again for your assistance.

[fehlix]

Thanks for the help @fehlix, the GRUB menu is fix and the the computer will boot into Windows, sort of. I'm able to enter the PIN and the desktop shows up, less the icons and there is something happening in the back ground as there is an blue circular icon spinng nonstop.

I'll have to do some diggin on this end, but thanks again for your assistance.

Good, so the GRUB part of this puzzle is now [SOLVED], right?
The other issue might be Windows after such a long time of absence from the net
might now try to upgrade itself which may take some time, or even revert back the last upgrade attempt, which may takes even longer some time.