I have been using Manjaro KDE version for about half year, yesterday I needed to boot windows10 to use certain tool but failed.
Here's my laptop configuration: LG gram + 2 SSD (one is nvme 512GB installed with win10 and the other is sata 256GB installed with Manjaro).
Some disk info below:
~ >>> sudo fdisk -l
Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 970 EVO 500GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 27B953FC-31EB-11E9-8552-F4DD9CE442AB
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 34815 32768 16M Microsoft reserved
/dev/nvme0n1p2 34816 976773119 976738304 465.7G Microsoft basic data
Disk /dev/sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: HFS256G39TND-N21
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: A541C300-BAF2-5947-BDAB-9C1E62A9E90B
Device Start End Sectors Size Type
/dev/sda1 4096 618495 614400 300M EFI System
/dev/sda2 618496 500103449 499484954 238.2G Linux filesystem
Disk /dev/sdb: 28.64 GiB, 30752000000 bytes, 60062500 sectors
Disk model: Ultra USB 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 6093039 6092976 2.9G 0 Empty
/dev/sdb2 6093040 6101231 8192 4M ef EFI (FAT-12/16/32)
~ >>> sudo lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1 vfat FAT32 CB3A-0C04 299.1M 0% /boot/efi
└─sda2 ext4 1.0 742143b0-ffb4-41b5-9932-27381dbf1df5 123.5G 42% /
sdb iso9660 Joliet Extension MANJARO_KDE_2003 2020-06-06-08-14-33-00
├─sdb1 iso9660 Joliet Extension MANJARO_KDE_2003 2020-06-06-08-14-33-00 0 100% /run/media/gavin/MANJARO_KDE_2003
└─sdb2 vfat FAT12 MISO_EFI F327-8F27
nvme0n1
├─nvme0n1p1
└─nvme0n1p2 ntfs DCD48F0BD48EE6DC 85.4G 82% /run/media/gavin/DCD48F0BD48EE6DC
How can I fix the Windows10 boot entry in grub? I have tried os-prober and adding win10 entry in /etc/grub.d/40_custom but both failed. Below are the entries I tried but failed:
menuentry "Windows 10 -1" --class windows --class os {
insmod ntfs
search --no-floppy --set=root --fs-uuid DCD48F0BD48EE6DC
ntldr /bootmgr
}
menuentry "Windows 10 -2" {
insmod ntfs
set root='(hd0,1)'
search --no-floppy --fs-uuid --set CB3A-0C04
chainloader +1
}
menuentry "Windows 10 -3" {
insmod ntfs
set root='(hd0,1)'
search --no-floppy --fs-uuid --set DCD48F0BD48EE6DC
chainloader +1
}
menuentry "Windows 10 -4" {
insmod ntfs
set root='(hd1,1)'
search --no-floppy --fs-uuid --set CB3A-0C04
chainloader +1
}
menuentry "Windows 10 -5" {
insmod ntfs
set root='(hd1,1)'
search --no-floppy --fs-uuid --set DCD48F0BD48EE6DC
chainloader +1
}
menuentry "Windows 10 -6" {
insmod ntfs
set root='(nvme0,1)'
search --no-floppy --fs-uuid --set CB3A-0C04
chainloader +1
}
menuentry "Windows 10 -7" {
insmod ntfs
set root='(nvme0,1)'
search --no-floppy --fs-uuid --set DCD48F0BD48EE6DC
chainloader +1
}
I really enjoy Linux and have solved several problems with help of Google/Reddit/StackExchange, but this one I really don't know how to solve.
I would appreciate it a lot if you can help because though I use Manjaro mainly I still need some win10 tools occasionally.
User contributions licensed under CC BY-SA 3.0