[SOLVED] GRUB2 - Menu Entry for Windows 10

inukaze · 03-05-2024, 08:15 AM

Quote:

Originally Posted by yancek

Having an entry for a windows partition in the /etc/fstab file for a "DATA" partition makes sense but for the windows system partition, no. Bad idea to be modifying any files on the system partition. I never have an entry in fstab for windows and have no problem with with Grub creating a boot entry for any windows installed.

The quote above is from your earlier post and causes me to wonder if you have left the default hibernation on in windows?? A Linux system won't try to access a hibernated partition of windows. It may be the reason for the problem but it doesn't seem likely. Quite simple to test though.

If you are interested in finding why the grub-mkconfig on Slackware doesn't seem to find the windows partition when another Linux does, you may try removing Grub completely and reinstalling it. If this is a computer you use daily, I don't know that I would do that without some backup means to boot.

No i don't use any type of Hibernation, i disable because is useless for me
i had use Win10 Setup with "fixboot" and "fixboot" after i use my pendrive with multiples distros, and start porteus and reinstall grub, but the result its the same

From porteus the entry for win10 is autogenerated, Porteus mount all partitions found during boot but i think just with "defaults" option. But when i am inside Slackware i am using fstab to mount win10 partition with the options "fmask=111,dmask=000". but when that options are active the mounted win10 partitions does not autogenerate the entry for win10

i use that options, becuase the slackware setup installation, show me that are the options for write/read all inside the ntfs partitions.

But i want know if someone can replicate that on their distro to know if a problem just for me, or its a general thing caused by options.

breaker · 03-05-2024, 09:30 AM

Quote:

Originally Posted by inukaze

No i don't use any type of Hibernation, i disable because is useless for me
i had use Win10 Setup with "fixboot" and "fixboot" after i use my pendrive with multiples distros, and start porteus and reinstall grub, but the result its the same

From porteus the entry for win10 is autogenerated, Porteus mount all partitions found during boot but i think just with "defaults" option. But when i am inside Slackware i am using fstab to mount win10 partition with the options "fmask=111,dmask=000". but when that options are active the mounted win10 partitions does not autogenerate the entry for win10

i use that options, becuase the slackware setup installation, show me that are the options for write/read all inside the ntfs partitions.

But i want know if someone can replicate that on their distro to know if a problem just for me, or its a general thing caused by options.

You can't run os-prober with Windows system partition mounted. /dev/sda1

os-prober calls grub-mount

Do not have it mounted when you use it.

grub-mkconfig MUST be run as root.

This file calls the scripts in order including /etc/default/grub then each script in /etc/grub.d in order.

If the option is true for os-prober, grub-mkconfig calls 30_os-prober which calls the binary os-prober which uses grub-mount.

You can manually just run the binary os-prober to check if it finds things.

Again, if you have os-prober enabled, DO NOT have Windows mounted and run grub-mkconfig as root, always.

GRUB is the same on all the distros.

breaker · 03-05-2024, 09:31 AM

Quote:

Originally Posted by mw.decavia

On my dual-boot pc, I just skip the entire problem of linux bootloaders vs windows, re: mbr and partitions etc.

When near the end of the slackware install, it asked if I wanted to create an emergency boot thumb drive, I did. And I use that to boot slackware all the time. By hitting f12 at the bios boot screen, I select the thumb drive instead of the hard drive. The thumb drive boots it from /dev/sda7.

If I let my pc boot from the hard drive, windows boots normally from /dev/sda1

Would that work if I were using grub?

Please post your own thread and do not hijack this one.

inukaze · 03-05-2024, 12:10 PM

Quote:

Originally Posted by breaker

You can't run os-prober with Windows system partition mounted. /dev/sda1

os-prober calls grub-mount

Do not have it mounted when you use it.

grub-mkconfig MUST be run as root.

This file calls the scripts in order including /etc/default/grub then each script in /etc/grub.d in order.

If the option is true for os-prober, grub-mkconfig calls 30_os-prober which calls the binary os-prober which uses grub-mount.

You can manually just run the binary os-prober to check if it finds things.

Again, if you have os-prober enabled, DO NOT have Windows mounted and run grub-mkconfig as root, always.

GRUB is the same on all the distros.

Ok you have reason, i umount, i see the output from mount and after i remount using "mount -a" to read all from /etc/fstab

Code:

inukaze@darkstar:~$ sudo su
Contraseña: 
root@darkstar:/home/inukaze# umount /dev/sda1
root@darkstar:/home/inukaze# mount

Quote:

proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=32768k,mode=755,inode64)
devtmpfs on /dev type devtmpfs (rw,relatime,size=8192k,nr_inodes=378926,mode=755,inode64)
/dev/sda6 on / type ext4 (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,inode64)
cgroup_root on /sys/fs/cgroup type tmpfs (rw,relatime,size=8192k,mode=755,inode64)
cpuset on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)
cpu on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)
cpuacct on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)
blkio on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)
memory on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
devices on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
freezer on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
net_cls on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)
perf_event on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)
net_prio on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)
pids on /sys/fs/cgroup/pids type cgroup (rw,relatime,pids)
misc on /sys/fs/cgroup/misc type cgroup (rw,relatime,misc)
/dev/sda3 on /boot type ext2 (rw,relatime,errors=continue,user_xattr,acl)
/dev/sda7 on /media/Slack32 type ext4 (rw,relatime)
/dev/sda2 on /media/Compartido type ntfs3 (rw,relatime,uid=0,gid=0,fmask=37777600177,dmask=37777600077,iocharset=utf8)
cgroup on /sys/fs/cgroup/elogind type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib64/elogind/elogind-cgroups-agent,name=elogind)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=304860k,nr_inodes=76215,mode=700,uid=1000,gid=100,inode64)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sdg1 on /run/media/inukaze/Inukaze-1 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper= udisks2)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)

Here the Windows 10 partitions is not mounted, i will go to use grub-mkconfig

Code:

grub-mkconfig -o /boot/grub/grub.cfg

Quote:

grub-mkconfig -o /boot/grub/grub.cfg
Generando un fichero de configuración de grub...
Encontrada imagen de linux: /boot/vmlinuz-huge-5.15.145
Encontrada imagen de memoria inicial: /boot/initrd.gz
Encontrada imagen de linux: /boot/vmlinuz-huge
Encontrada imagen de memoria inicial: /boot/initrd.gz
Encontrada imagen de linux: /boot/vmlinuz-generic-5.15.145
Encontrada imagen de memoria inicial: /boot/initrd.gz
Encontrada imagen de linux: /boot/vmlinuz-generic
Encontrada imagen de memoria inicial: /boot/initrd.gz
Aviso: 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.
Encontrado Windows 10 en /dev/sda1
Encontrado Slackware 15.0 i586 en /dev/sda7
hecho

Ok then the strange are the follow :

Code:

mount -a ; mount | grep win10

Quote:

/dev/sda1 on /media/win10 type ntfs3 (rw,relatime,uid=0,gid=0,fmask=37777600177,dmask=37777600077,iocharset=utf8)

Code:

grub-mkconfig -o /boot/grub/grub.cfg

Quote:

Generando un fichero de configuración de grub...
Encontrada imagen de linux: /boot/vmlinuz-huge-5.15.145
Encontrada imagen de memoria inicial: /boot/initrd.gz
Encontrada imagen de linux: /boot/vmlinuz-huge
Encontrada imagen de memoria inicial: /boot/initrd.gz
Encontrada imagen de linux: /boot/vmlinuz-generic-5.15.145
Encontrada imagen de memoria inicial: /boot/initrd.gz
Encontrada imagen de linux: /boot/vmlinuz-generic
Encontrada imagen de memoria inicial: /boot/initrd.gz
Aviso: 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.
Encontrado Slackware 15.0 i586 en /dev/sda7
hecho

Until there, if mounted, and the options dmask and fmask are enable the entry is not autogenerated
Well but if i umount manually and mount again manually that options are not used and the entry for win10 are autogenerated.

Look this :

Code:

umount /dev/sda1
mount /dev/sda1 /media/win10/
mount | grep win10
/dev/sda1 on /media/win10 type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
grub-mkconfig -o /boot/grub/grub.cfg

Quote:

Generando un fichero de configuración de grub...
Encontrada imagen de linux: /boot/vmlinuz-huge-5.15.145
Encontrada imagen de memoria inicial: /boot/initrd.gz
Encontrada imagen de linux: /boot/vmlinuz-huge
Encontrada imagen de memoria inicial: /boot/initrd.gz
Encontrada imagen de linux: /boot/vmlinuz-generic-5.15.145
Encontrada imagen de memoria inicial: /boot/initrd.gz
Encontrada imagen de linux: /boot/vmlinuz-generic
Encontrada imagen de memoria inicial: /boot/initrd.gz
Aviso: 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.
Encontrado Windows 10 en /dev/sda1
Encontrado Slackware 15.0 i586 en /dev/sda7
hecho

Why when is mounted by fstab the type is ntfs3, but when i do is fuseblk, well i go to try use that parameters like option on fstab

Well i will go try with this /etc/fstab

Code:

UUID=8bfb2d02-7390-42dd-9a72-7d7b750a63f8       swap                    swap    defaults                                0       0
UUID=674d8a56-4cb2-43a0-bdca-6ae5bd01828b       /                       ext4    defaults                                1       2
UUID=7e1ea804-82bd-486a-a01d-6798ab9adf43       /boot                   ext2    defaults                                1       2
UUID=45f7bc61-14c3-4118-81a5-034d35ebc6b9       /media/Slack32          ext4    defaults                                1       2
#WIN10-ORIGINAL#UUID=90D06FC4D06FAEE2                           /media/win10            ntfs3   fmask=0177,dmask=0077                   1  0
UUID=90D06FC4D06FAEE2                           /media/win10            ntfs3   rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096  10
UUID=24045D0035428EFF                           /media/Compartido       ntfs3   fmask=0177,dmask=0077                   1       0
#/dev/cdrom                                     /mnt/cdrom              auto    noauto,owner,ro,comment=x-gvfs-show     0       0
#/dev/fd0                                       /mnt/floppy             auto    noauto,owner                            0       0
devpts                                          /dev/pts                devpts  gid=5,mode=620                          0       0
proc                                            /proc                   proc    defaults                                0       0
tmpfs                                           /dev/shm                tmpfs   nosuid,nodev,noexec                     0       0

fuseblk is valid for fstab ?

i had restart, but the win10 partition not mounted with that options during boot i
see "wrong fs type" line and can't read the rest

Well when i reach desktop i open konsole and use :

Code:

sudo su
export LANGUAGE=en
export LANG=us_US.UTF-8
mount -a

Quote:

mount: /media/win10: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.

Well that options does not work, rolling back XD
well better i modify the os-prober script to detect if windows partition(s) are mounted and if yes, then umount generate the entry's an at end of file remount partitions with "mount -a"

inukaze · 03-05-2024, 12:59 PM

Final dunno someone remember witch tools generate the file /var/log/boot, i do with Slackware(64) 14.2 but i can't remember the name of that tool, and is very useful for me to see and analyze the same text i saw during Slackware boot.

i had check each file and directory inside /var/log, and i don't file that file, the output of another files like dmesg happend before i and looking for.

breaker · 03-05-2024, 02:18 PM

os-prober wants it mounted read-only, I think.

You can also check manually by running grub-mount /dev/sda1 /mnt/win10 and that will show you how it will execute when os-prober calls it or if grub-mount fails.

I assume your fstab entry mounts it wrong. You should remove that entry and not use it ever.