Garuda Talon doesn't see useless Windows Partition

I am now using Garuda Talon. But when executing the following:

  sudo grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-lts-fallback.img
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.
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2022-05-09 13:51:55 | @/.snapshots/50/snapshot | post | os-prober-btrfs                                                          |
Found snapshot: 2022-05-09 13:51:53 | @/.snapshots/49/snapshot | pre  | pacman -S --config /etc/pacman.conf -- os-prober-btrfs                   |
Found snapshot: 2022-05-09 13:28:23 | @/.snapshots/48/snapshot | post | oh-my-zsh-git                                                            |
Found snapshot: 2022-05-09 13:28:21 | @/.snapshots/47/snapshot | pre  | pacman -S --config /etc/pacman.conf -- oh-my-zsh-git                     |
Found snapshot: 2022-05-09 13:25:27 | @/.snapshots/46/snapshot | post | zsh-autosuggestions zsh-syntax-highlighting                              |
Found snapshot: 2022-05-09 13:25:25 | @/.snapshots/45/snapshot | pre  | pacman -S --config /etc/pacman.conf -- zsh-syntax-highlighting zsh-autos |
Found snapshot: 2022-05-09 13:24:46 | @/.snapshots/44/snapshot | post | autojump                                                                 |
Found snapshot: 2022-05-09 13:24:44 | @/.snapshots/43/snapshot | pre  | pacman -U --noconfirm --config /etc/pacman.conf -- /home/sevenday4/.cach |
Found snapshot: 2022-05-09 13:19:21 | @/.snapshots/42/snapshot | post | nerd-fonts-complete ttf-iosevka-nerd                                     |
Found snapshot: 2022-05-09 13:19:04 | @/.snapshots/41/snapshot | pre  | pacman -U --config /etc/pacman.conf -- /home/sevenday4/.cache/yay/nerd-f |
Found snapshot: 2022-05-09 12:59:30 | @/.snapshots/40/snapshot | post | xorg-bdftopcf xorg-font-util xorg-mkfontscale                            |
Found snapshot: 2022-05-09 12:59:26 | @/.snapshots/39/snapshot | pre  | pacman -S --config /etc/pacman.conf -- extra/xorg-mkfontscale extra/xorg |
Found 12 snapshot(s)
Unmount /tmp/grub-btrfs.xVtKijksWi .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

Apparently, os-prober-btrfs isn't seeing the windows partion.

here's my garuda inxi:

    ~/Desktop  sudo garuda-inxi             ✔  took 8s   at 14:14:05  
System:
  Kernel: 5.17.5-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=f3130409-2b37-4397-83ca-c685530f7ac0 rw [email protected]
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3
  Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.29 info: xfce4-panel wm: xfwm
    v: 4.16.1 dm: LightDM v: 1.30.0 Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Laptop System: HP product: HP Laptop 15-bs0xx v: Type1ProductConfigId
    serial: <filter> Chassis: type: 10 serial: <filter>
  Mobo: HP model: 832A v: 23.70 serial: <filter> UEFI: Insyde v: F.52
    date: 03/04/2019
Battery:
  ID-1: BAT1 charge: 39.7 Wh (100.0%) condition: 39.7/41.6 Wh (95.3%)
    volts: 16.7 min: 14.6 model: Hewlett-Packard PABAS0241231 type: Li-ion
    serial: <filter> status: full
CPU:
  Info: model: Intel Core i3-7100U socket: BGA1356 (U3E1) note: check
    bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check family: 6
    model-id: 0x8E (142) stepping: 9 microcode: 0xEC
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
    L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 1080 high: 1922 min/max: 400/2400 base/boost: 2300/8300
    scaling: driver: intel_pstate governor: powersave volts: 0.8 V
    ext-clock: 100 MHz cores: 1: 1922 2: 800 3: 800 4: 800 bogomips: 19200
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915
    v: kernel ports: active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:5916 class-ID: 0300
  Device-2: Realtek HP Webcam type: USB driver: uvcvideo bus-ID: 1-5:4
    chip-ID: 0bda:58ed class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.3 compositor: xfwm v: 4.16.1 driver:
    X: loaded: modesetting alternate: fbdev,intel,vesa gpu: i915
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
    s-diag: 414mm (16.31")
  Monitor-1: eDP-1 model: BOE Display 0x06a4 built: 2015 res: 1366x768
    hz: 60 dpi: 101 gamma: 1.2 size: 344x194mm (13.54x7.64")
    diag: 395mm (15.5") ratio: 16:9 modes: 1366x768
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3
    chip-ID: 8086:9d71 class-ID: 0403
  Sound Server-1: ALSA v: k5.17.5-zen1-1-zen running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak]
    driver: iwlwifi v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 8086:24fb class-ID: 0280
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-4:3 chip-ID: 8087:0aa7 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
Drives:
  Local Storage: total: 1.82 TiB used: 19.32 GiB (1.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WDS200T2B0A-00SM50 size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 20WD
    scheme: GPT
Partition:
  ID-1: / raw-size: 912.04 GiB size: 912.04 GiB (100.00%)
    used: 19.29 GiB (2.1%) fs: btrfs block-size: 4096 B dev: /dev/sda6
    maj-min: 8:6
  ID-2: /boot/efi raw-size: 250 MiB size: 246.1 MiB (98.46%)
    used: 25.6 MiB (10.4%) fs: vfat block-size: 512 B dev: /dev/sda1
    maj-min: 8:1
  ID-3: /home raw-size: 912.04 GiB size: 912.04 GiB (100.00%)
    used: 19.29 GiB (2.1%) fs: btrfs block-size: 4096 B dev: /dev/sda6
    maj-min: 8:6
  ID-4: /var/log raw-size: 912.04 GiB size: 912.04 GiB (100.00%)
    used: 19.29 GiB (2.1%) fs: btrfs block-size: 4096 B dev: /dev/sda6
    maj-min: 8:6
  ID-5: /var/tmp raw-size: 912.04 GiB size: 912.04 GiB (100.00%)
    used: 19.29 GiB (2.1%) fs: btrfs block-size: 4096 B dev: /dev/sda6
    maj-min: 8:6
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda5 maj-min: 8:5
  ID-2: swap-2 type: zram size: 15.54 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 29.8 C pch: 33.5 C mobo: 27.8 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 233 Uptime: 7m wakeups: 1 Memory: 15.54 GiB
  used: 2.47 GiB (15.9%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.2.0 clang: 13.0.1 Packages: 1527 apt: 3 pacman: 1524 lib: 379
  Shell: garuda-inxi (sudo) default: Bash v: 5.1.16
  running-in: xfce4-terminal inxi: 3.3.15
Garuda (2.6.2-1):
  System install date:     2022-05-05
  Last full system update: 2022-05-09
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Snapper
  Failed units:       

Now, the strange thing is, is that I am dual booting with Windows 10. I installed a higher compacity SSD drive to my laptop. I could not copy my old Garuda install to where I could extend the BTRFS partition and had to reinstall Garuda using the Talon version. Any ideas guys?

Please format your post.

sudo update-grub

Post in and output from

lsblk
sudo blkid -o list

in correct text format :slight_smile:

I'm not sure what you meant in correct format, but here goes:

device     fs_type label    mount point    UUID
-------------------------------------------------------------------------------
/dev/sda6  btrfs   Garuda   (in use)       f3130409-2b37-4397-83ca-c685530f7ac0
/dev/sdb1  vfat    NEW VOLUME /run/media/sevenday4/NEW VOLUME 7E1A-4827
/dev/sda4  ntfs             (not mounted)  1E88A3D888A3ACA9
/dev/sda5  swap    Swap     [SWAP]         ee93921d-f04c-4657-8c1c-257700fbe2c2
/dev/sda1  vfat             /boot/efi      BF86-799B
/dev/zram0 swap    zram0    [SWAP]         2488d3bf-a1ec-40c2-8c54-434574d2bd46
/dev/sda2                   (not mounted)  
/dev/sda3                   (not mounted)

If M$ is not on the unmounted drives, then there is no M$ on the machine.

Missing

lsblk

Mount the volumes first.

1 Like

Also missing:

To add code formatting to your post, add three tildes before and after

~~~
like this.
~~~

1 Like
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0   1.8T  0 disk 
├─sda1   8:1    0   250M  0 part /boot/efi
├─sda2   8:2    0   500M  0 part 
├─sda3   8:3    0    16M  0 part 
├─sda4   8:4    0 918.2G  0 part 
├─sda5   8:5    0    32G  0 part [SWAP]
└─sda6   8:6    0   912G  0 part /var/tmp
                                 /var/cache
                                 /var/log
                                 /root
                                 /srv
                                 /home
                                 /
sdb      8:16   1 114.6G  0 disk 
└─sdb1   8:17   1 114.6G  0 part 
zram0  254:0    0  15.5G  0 disk [SWAP]

When all drives are mounted, again

2 Likes

You can either make mount points and mount the drives manually, or another option is to boot into the live environment on your USB you just installed from and pick the chroot tool from the menu. Select sda, it should mount all the drives for you and you can run

sudo update-grub

:point_up_2: Don't forget the hyphen. Afterward,

exit
reboot
3 Likes

Boot to Windows, disable hibernation and fast boot, then reboot (don't shutdown, reboot instead) and try again.

here's what I have:

sevenday4-hplaptop15bs0xx% sudo efibootmgr -v
[sudo] password for sevenday4:                
BootCurrent: 0005
Timeout: 5 seconds
BootOrder: 0005,3005,2001,0004,0003,0001,0002,2002,2004
Boot0001* Network Adapter (IPv4 UEFI)	PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(9c7bef0f186c,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0002* Network Adapter (IPv6 UEFI)	PciRoot(0x0)/Pci(0x1c,0x0)/Pci(0x0,0x0)/MAC(9c7bef0f186c,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0003* Windows Boot Manager on Disk 1	HD(1,GPT,601ead22-b4a9-4a2d-5122-7944c71cb7f0,0x800,0x7d000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.5.6.f.b.2.9.8.f.-.c.a.7.2.-.1.1.e.c.-.8.b.2.2.-.a.4.c.3.f.0.6.6.c.6.5.b.}..._................
Boot0004* Windows Boot Manager	HD(1,GPT,601ead22-b4a9-4a2d-5122-7944c71cb7f0,0x800,0x7d000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0005* Garuda	HD(1,GPT,601ead22-b4a9-4a2d-5122-7944c71cb7f0,0x800,0x7d000)/File(\EFI\Garuda\grubx64.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot3005* Internal Hard Disk or Solid State Disk	RC
sevenday4-hplaptop15bs0xx% 

If you want to restore your Windows installation to the grub menu, efibootmgr will not help you--you are going to have to mount the drives and sudo update-grub.

2 Likes

Try

sudo efibootmgr -n 0003

this will hopefully boot to Windows, for once.
Replace 0003 with 0004 if it doesn't work. Once you are in Windows

Sorry, that doesn't work. I have tried sudo update-grub several times. The previous versions Garuda had no issue in seeing my windows partition.

it's a no go. I did mount the partition But:

[[email protected] Desktop]$ sudo mkdir /mnt/ntfs
[sudo] password for sevenday4:                
[[email protected] Desktop]$ sudo su
[[email protected] Desktop]# mount -t ntfs /dev/sda4 /mnt/ntfs
[[email protected] Desktop]# df -h
Filesystem      Size  Used Avail Use% Mounted on
dev             7.8G     0  7.8G   0% /dev
run             7.8G  1.8M  7.8G   1% /run
/dev/sda6       913G   12G  900G   2% /
tmpfs           7.8G     0  7.8G   0% /dev/shm
/dev/sda6       913G   12G  900G   2% /home
/dev/sda6       913G   12G  900G   2% /srv
/dev/sda6       913G   12G  900G   2% /var/tmp
/dev/sda6       913G   12G  900G   2% /root
/dev/sda6       913G   12G  900G   2% /var/cache
/dev/sda6       913G   12G  900G   2% /var/log
/dev/sda1       247M   26M  221M  11% /boot/efi
tmpfs           7.8G  456K  7.8G   1% /home/guest
tmpfs           7.8G   15M  7.8G   1% /tmp
tmpfs           1.6G  104K  1.6G   1% /run/user/1000
/dev/sda4       919G  425G  495G  47% /mnt/ntfs
[[email protected] Desktop]# update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/garuda/theme.txt
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot:  intel-ucode.img initramfs-linux-lts-fallback.img
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.
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...

Can you actually boot into this Windows installation, from BIOS or the boot menu?

3 Likes

Did you try this or what @BluishHumility suggested?
I started suspecting if Windows bootloader is healthy. If you have an older ISO, can you try booting it and running os-prober from there?

Yes, I did. and no, unfortunately I do not have an older ISO and wish I did because they saw my Windows partition without me doing anything. I don't know what was done, but this is one of those don't fix what isn't broken situation. I like what the Garuda team has done with this distro. But, this is a issue with me because I have to have windows for the work I do. I could switch between the two, but only through BIOS or involking 'sudo efibootmgr -n 0004" which isn't conducive. I wish I had an older version and then upgrade through it.

Yes, I can through BIOS or with 'sudo efibootmgr -n 0004' but I don't want to have to take extra steps if I don't need to. it's bad enough going from Windows to Garuda. I really like this distro, but something was changed that makes this difficult when in the past, Garuda had no issues in finding other partitions.

You did not mount all the partitions, you only mounted sda4 which isn't the Windows boot partition. You need to mount all the partitions, and then run sudo update-grub.

As I mentioned, an easy way to do this is the chroot tool from the live environment. Otherwise make a couple more mount points and mount the other two partitions, then try again.

2 Likes

Actually, sda4 is my windows partition. All the partitions were already mounted. and yes, I used chroot from my USB environment. The reason I know that sda4 is my windows partition is because I can input sudo efimgr -n 0004 and get into windows. The sda4 is designated as '0004.'