Hello,
I installed Mint and Windows in different partitions on the same disk about a year ago, I had updated Mint and never had to go back to Windows until now some apps that I need to uwe, and when I tried to boot the Windows OS it doesnt do anything, like the OS isnt there.
The config shows that it the partition is in hd0, gpt2 but when I run a ls on the grub all the gpt’s show on hd1.
Im a little confused about how to fix this.
Thanks
Hi Oscar,
Welcome! Can you post output of command lsblk from Mint. You’re using Grub? EFI?
Edit: I’m not familiar with Windows dual boot but there’s many here who can help you
Hi Oscar,
Grub does not differentiate between HDD and SSD devices, so
everything is labelled hd, beginning eith hd0
Do you perhaps also have an SSD disk?
We need to see the outout of lsblk which @ihasama asked for.
I would suspect that your Mint update has done an update-grub and that it has not found the Windows OS.
What you could check is
cd to /etc/default
and look at the file called grub
does it contain a line
grub_disable_os_prober=FALSE
if not, add that line
then do update-grub
then reboot and see if your grub menu contains windows.
Regards
Neville
Since Mint is a derivative of Ubuntu perhaps this will help:
Here is the result of lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 388.9M 1 loop /snap/anbox/214
loop1 7:1 0 373.8M 1 loop /snap/anbox/186
loop2 7:2 0 4K 1 loop /snap/bare/5
loop3 7:3 0 60.9M 1 loop /snap/bower/7
loop4 7:4 0 105.8M 1 loop /snap/core/16202
loop5 7:5 0 105.4M 1 loop /snap/core/16574
loop6 7:6 0 55.7M 1 loop /snap/core18/2796
loop7 7:7 0 55.7M 1 loop /snap/core18/2812
loop8 7:8 0 63.5M 1 loop /snap/core20/2015
loop9 7:9 0 63.9M 1 loop /snap/core20/2105
loop10 7:10 0 74.1M 1 loop /snap/core22/1033
loop11 7:11 0 262.1M 1 loop /snap/firefox/3728
loop12 7:12 0 262.5M 1 loop /snap/firefox/3779
loop13 7:13 0 497M 1 loop /snap/gnome-42-2204/141
loop14 7:14 0 91.7M 1 loop /snap/gtk-common-themes/1535
loop15 7:15 0 40.9M 1 loop /snap/snapd/20290
loop16 7:16 0 40.4M 1 loop /snap/snapd/20671
loop17 7:17 0 310.8M 1 loop
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 499M 0 part
├─sda2 8:2 0 100M 0 part /boot/efi
├─sda3 8:3 0 16M 0 part
├─sda4 8:4 0 679.8G 0 part
├─sda5 8:5 0 248.5G 0 part /var/snap/firefox/common/host-hunspell
│ /
└─sda6 8:6 0 612M 0 part
sdb 8:16 0 1.8T 0 disk
└─sdb1 8:17 0 1.8T 0 part /data1
sdc 8:32 0 3.6T 0 disk
└─sdc1 8:33 0 3.6T 0 part /data
sdd 8:48 0 931.5G 0 disk
└─sdd1 8:49 0 931.5G 0 part /data2
sde 8:64 0 279.5G 0 disk
└─sde1 8:65 0 279.5G 0 part /data3
sdf 8:80 0 931.5G 0 disk
├─sdf1 8:81 0 39.2M 0 part
├─sdf2 8:82 0 11.7G 0 part
└─sdf3 8:83 0 919.7G 0 part
sr0 11:0 1 1024M 0 rom
I tried adding the os_prober line… but got the same result
How many disks you have? Sda2 has the efi boot. In your original message you said you have one disk with win and mint on different partitions. What are the sdb-sdf?
Can you run sudo os-prober separately. Does it find anything? Or please list what sudo update-grub shows
Did you do update-grub after adding the line?
Where is windows… on which disk?
Something is unusual about your setup… you have Mint, but there are snaps…
I thought Mint decided against snaps.
I have several disks in this pc for storage…
sudo os-prober
/dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
sudo update-grub
Sourcing file /etc/default/grub' Sourcing file /etc/default/grub.d/50_linuxmint.cfg’
Sourcing file `/etc/default/grub.d/init-select.cfg’
Generating grub configuration file …
Found linux image: /boot/vmlinuz-5.15.0-97-generic
Found initrd image: /boot/initrd.img-5.15.0-97-generic
Found linux image: /boot/vmlinuz-5.15.0-94-generic
Found initrd image: /boot/initrd.img-5.15.0-94-generic
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 Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings …
done
The Windows disk is on the SSD disk
sudo parted -l /flags
Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 524MB 523MB ntfs Basic data partition hidden, diag
2 524MB 629MB 105MB fat32 EFI system partition boot, esp
3 629MB 646MB 16.8MB Microsoft reserved partition msftres
4 646MB 731GB 730GB ntfs Basic data partition msftdata
5 731GB 997GB 267GB ext4
6 997GB 998GB 642MB ntfs hidden, diag
Model: ATA WDC WD20EARS-00M (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 32.3kB 2000GB 2000GB primary ntfs
Model: ATA WDC WD40EZRX-00S (scsi)
Disk /dev/sdc: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 4001GB 4001GB ntfs Basic data partition msftdata
Model: ATA WDC WD10EADS-00L (scsi)
Disk /dev/sdd: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 32.3kB 1000GB 1000GB primary ntfs boot
Model: ATA Maxtor 6L300S0 (scsi)
Disk /dev/sde: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 32.3kB 300GB 300GB primary ntfs
So grub(osprober) detects the Windows boot manager
but it is adding it to the UEFI bios, instead of to the grub menu?
I think you need to go to the BIOS and boot the windows
bootloader from there.
I do not understand why it did not make a grub menu entry?
The Windows Boot does makes it to the GRUB Menu, but i you select it it doesn’t work.
Select the Windows Boot, go into edit mode (type e), then you can see the grub.cfg file entry for Windows.
Inspect it and see if you can see what is wrong… I cant even guess, I have no experience with Windows, but if it was Linux I would look at the location of the root filesystem and the kernel boot parameters. If you can see the mistake, you can
edit it, then ‘escape’ ( ie ESC key) and it will boot.
Editing changes are temporary… next time you boot they will be gone. To make a change permanent you have to change the grub configuration in Linux.