Many issues with adding windows to grub

I was following the official Cachyos guide to adding windows to its grub (How To Install CachyOS & Partition Guide | CachyOS) and when executing ❯ sudo mount /dev/nvme0n1p1 /mnt/WinBoot it says

mount: /mnt/WinBoot: der Einhängepunkt ist nicht vorhanden.
       dmesg(1) könnte nach einem fehlgeschlagenen mount-Systemaufruf
       weitere Informationen liefern.
# It's in german btw

I tried switching /dev/nvme01n1p1 to *p2 and still the same thing, and when I replaced it with /dev/nvme0n1 it said

mount: /mnt/WinBoot: Falscher Dateisystemtyp, ungültige Optionen, der Superblock von /dev/nvme0n1 ist beschädigt, fehlende Kodierungsseite oder ein anderer Fehler.
       dmesg(1) könnte nach einem fehlgeschlagenen mount-Systemaufruf
       weitere Informationen liefern.
# German too

Also here’s the ❯ sudo lsbk output:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 931,5G  0 disk 
└─sda1        8:1    0 931,5G  0 part /home
                                      /var/log
                                      /var/cache
                                      /var/tmp
                                      /srv
                                      /root
                                      /
sr0          11:0    1  1024M  0 rom  
zram0       253:0    0   7,7G  0 disk [SWAP]
nvme0n1     259:0    0 931,5G  0 disk 
├─nvme0n1p1 259:1    0    50M  0 part 
├─nvme0n1p2 259:2    0   930G  0 part 
├─nvme0n1p3 259:3    0   863M  0 part 
├─nvme0n1p4 259:4    0   100M  0 part 
└─nvme0n1p5 259:5    0   518M  0 part 

#btw on Dolphin windows appears as nvme0n1p2

Have you created the directory /mnt/WinBoot? He tells you it is not available…

Wait do you really have to? Let me do it brb

Now I got another issue. The files it contians are:

❯ ls
drwxr-xr-x     - root 10 dic  2023  $RECYCLE.BIN
drwxr-xr-x     - root 20 oct  2024  Recovery
drwxr-xr-x     - root 26 dic  2023  'System Volume Information'
.r-xr-xr-x  416k root  9 dic  2023 󰡯 bootmgr
.rwxr-xr-x@    1 root  7 dic  2019 󰡯 BOOTNXT
.r-xr-xr-x  8,2k root  9 dic  2023  BOOTSECT.BAK

The file EFI does not exist here so when executing ❯ sudo cp -r /mnt/WinBoot/EFI/* /boot/EFI there is no EFI nor anything inside so fish says

fish: No matches for wildcard '/mnt/WinBoot/EFI/*'. See `help wildcards-globbing`.
sudo cp -r /mnt/WinBoot/EFI/* /boot/EFI
           ^~~~~~~~~~~~~~~~~^

Well, that’s an other story, mounting works.

What do you want to achieve? Might be we could better help, if we understand what you are trying to do. Might be better in a new thread with appropriate title, so people who know of the issue can find it.

I’m following the How To Install CachyOS & Partition Guide | CachyOS tutorial but I find many road blocks

So you have a running CachyOS installation with grub, that reboots just fine into cachy, and you want to add you previously installed Windows as bootoption to grub?
Cachy ist installed on sda and windows on nvme0n1 ?

The Windows-installation was not automatically added to Grub?

One hint: You can normally select the boot-media while booting (e.g. by pressing F10 or so), this is the easiest way, as your Windows seems to have its own bootmanager…

But could you show us your Grub-configuration?

Where can I find my grub config?

cat /etc/default/grub

(Little hint: If you are doing a fresh installation and don’t have a reason for grub: I’ve installed cachy with limine as bootloader and it automatically added Windows to the Menu).

# GRUB boot loader configuration

GRUB_DEFAULT='saved'
GRUB_TIMEOUT='5'
GRUB_DISTRIBUTOR='CachyOS'
GRUB_CMDLINE_LINUX_DEFAULT='nowatchdog nvme_load=YES zswap.enabled=0 splash loglevel=3'
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'hidden' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=menu

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY='true'

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
GRUB_THEME='/usr/share/grub/themes/cachyos/theme.txt'

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
#GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
GRUB_DISABLE_SUBMENU='false'

# Probing for other operating systems is disabled for security reasons. Read
# documentation on GRUB_DISABLE_OS_PROBER, if still want to enable this
# functionality install os-prober and uncomment to detect and include other
# operating systems.
#GRUB_DISABLE_OS_PROBER=false
GRUB_EARLY_INITRD_LINUX_STOCK=''

You have installed os-prober as said in the wiki? And afterwards run sudo os-prober?

Then you have to remove the “#” in front of the line #GRUB_DISABLE_OS_PROBER=false, so that the line now looks like GRUB_DISABLE_OS_PROBER=false and save the file.

After having done this just run sudo grub-mkconfig -o /boot/grub/grub.cfg and reboot your machine.

That’s what said in the wiki. If you have trouble, tell us on which exact point you have which exact problem.

Ninja-ed by @Kalliseppl :slight_smile:
Is os-prober installed? If yes comment this line “#GRUB_DISABLE_OS_PROBER=false”
To:

GRUB_DISABLE_OS_PROBER=false

Now update grub:

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

Thank you both. removed the # and then ran grub-mkconfig -o /boot/grub/grub.cfg. Do I follow the tutorial or do I first have to reboot

There is nothing else in the Wiki:

Not sure of your meaning here, you can do that now, and after a reboot you should see Windows now

Ok

I meant the CachyOS Installation Desktop/Laptop | CachyOS tutorial not the Prober one.

I’ll try brb

Hello, I had a similar issue with GRUB. This is how I solved it.

Step 1: Install the os-prober package:
sudo apt update
sudo apt install os-prober

Step 2: Then remove the # from this line in etc/default/grub configuration file that has a probe for another OS

Step 3: Open file for editing:
sudo nano /etc/default/grub

line should look like this:
GRUB_DISABLE_OS_PROBER=false

Step 4: Update Grub:
sudo update-grub

Step 5: Reboot

you should now see Windows in the GRUB menu.

Hope this helps you.

FTR This is an Arch forum, not debian…:wink:

There is a script in AUR for update-grub if that’s easier for you.

paru update-grub
1 aur/update-grub 0.0.1-8 [+132 ~2.13]
    Simple wrapper around grub-mkconfig

While Arch Linux does not use the APT package manager by default and instead relies on its native Pacman package manager , it is technically possible to install APT on Arch Linux. This can be achieved by installing the APT package manager from the Arch User Repository (AUR) using an AUR helper like yay.

However, doing so is strongly discouraged by the Arch Linux community because it can lead to significant system instability and dependency conflicts.

The APT and Pacman package managers have different methods for tracking installed packages and managing dependencies, and using both simultaneously can result in “dependency hell,” where conflicting package versions or duplicate installations cause system-wide issues.

Some users have reported that installing APT on Arch triggers warnings about the potential for irreparable harm to the system.

For these reasons, the recommended approach is to learn and use the native Pacman package manager, which is well-documented and designed specifically for Arch Linux.

Nothing, Windows is still ghosting me