[bug #59803] grub-mkconfig omits insmod chain in Windows 10 menu entry

[Reed Lawson]

URL:
  <https://savannah.gnu.org/bugs/?59803>

                 Summary: grub-mkconfig omits insmod chain in Windows 10 menu
entry
                 Project: GNU GRUB
            Submitted by: yoreed
            Submitted on: Sat 02 Jan 2021 05:09:09 PM UTC
                Category: Configuration
                Severity: Major
                Priority: 5 - Normal
              Item Group: Software Error
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Reed Lawson
        Originator Email: yoreed@gmail.com
             Open/Closed: Open
                 Release: 
                 Release: 2.02
         Discussion Lock: Any
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

using grub-mkconfig (GRUB) 2.02-2ubuntu8.20 generates the following menuentry
for the dos Windows 10 partition on my SSD located at /dev/sdd1

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 10 (on /dev/sdd1)' --class windows --class os
$menuentry_id_option 'osprober-chain-3676E6BD76E67CCD' {
        insmod part_msdos
        insmod ntfs
        set root='hd3,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1
--hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1  3676E6BD76E67CCD
        else
          search --no-floppy --fs-uuid --set=root 3676E6BD76E67CCD
        fi
        parttool ${root} hidden-
        drivemap -s (hd0) ${root}
        chainloader +1
}
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
  set timeout=10
fi
### END /etc/grub.d/30_os-prober ###

When used, the message: 

A disk read error occured
Press Ctrl-Alt-Del to restart

is shown on the display.

I noticed that in the manual here: 
https://www.gnu.org/software/grub/manual/grub/html_node/Chain_002dloading.html#Chain_002dloading

The line "insmod chain" appears. 
Adding "insmod chain" to the menuentry above right after "insmod part_msdos"
results in a good boot up of Windows 10 when used.

So it would appear that grub-mkconfig omits the "insmod chain" line for some
reason. 

fdisk -l
Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
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: 3036FC6B-AA82-624E-9F61-20FC65AF51A8

Device        Start        End    Sectors  Size Type
/dev/sdb1      2040       2055         16    8K Linux swap
/dev/sdb2  31250432 5860532223 5829281792  2.7T Microsoft basic data


Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
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: 0x4e1210f4

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1  *     2048 500117503 500115456 238.5G 83 Linux


Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
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: 5FC5A0D0-AD43-9F48-B14E-46B14BE93AF4

Device        Start        End    Sectors  Size Type
/dev/sdc1      2040       2055         16    8K Linux swap
/dev/sdc2  31250432 5860532223 5829281792  2.7T Microsoft basic data


Disk /dev/sdd: 223.6 GiB, 240057409536 bytes, 468862128 sectors
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: dos
Disk identifier: 0x6ad0aa4d

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdd1  *     2048 468858879 468856832 223.6G  7 HPFS/NTFS/exFAT

uname -a
Linux miranda 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

Hope this helps!
- Reed





    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59803>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/