You are not logged in.
I have Windows 7 and Arch installed on UEFI-CSM, Arch after Windows. After Arch install, Windows Bootloader would not show in boot option.
$ ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 10 Feb 15 20:27 Media -> ../../sda5
lrwxrwxrwx 1 root root 15 Feb 15 20:27 Program -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 Feb 15 20:27 'System\x20Reserved' -> ../../nvme0n1p1
$ sudo mount -t ntfs3 /dev/nvme0n1p1 /mnt
$ ls /mnt
Boot bootmgr BOOTSECT.BAK 'System Volume Information'
$ sudo os-prober
$ sudo grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
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
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-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.
Detecting snapshots ...
Found snapshot: 2022-02-15 21:00:31 | @.snapshots/6/snapshot | single | timeline |
Found snapshot: 2022-02-15 20:00:16 | @.snapshots/5/snapshot | single | timeline |
Found snapshot: 2022-02-15 19:00:16 | @.snapshots/4/snapshot | single | timeline |
Found snapshot: 2022-02-15 18:00:16 | @.snapshots/3/snapshot | single | timeline |
Found snapshot: 2022-02-15 17:00:16 | @.snapshots/2/snapshot | single | timeline |
Found snapshot: 2022-02-15 16:00:16 | @.snapshots/1/snapshot | single | timeline |
Found 6 snapshot(s)
Unmount /tmp/grub-btrfs.K8VvDjBbUi .. Success
doneLast edited by ochinko (2022-02-15 17:40:38)
Offline
Are you sure your Windows is installed in CSM-BIOS mode on a NVME drive? Vice-versa are you sure your a booted in BIOS mode? Post
lsblk -fFWIW the warning regarding explicitly using ntfs-3g rather than ntfs3 for os-prober to probe might indeed hold: https://github.com/campadrenalin/os-pro … rosoft#L17
Last edited by V1del (2022-02-15 13:24:47)
Offline
Yes they should be, made sure they were while installing. And thank you, ntfs-3g solved the problem. You're the best V1del !
$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
zram0 [SWAP]
nvme0n1
├─nvme0n1p1 ntfs System Reserved A6EADA08EAD9D521
├─nvme0n1p2 ntfs 786EEDEC6EEDA35C
├─nvme0n1p3 ntfs CE8AD1BC8AD1A16F
├─nvme0n1p4
├─nvme0n1p5 ntfs Program E624102A240FFBED
├─nvme0n1p6 ntfs F8C0665DC06621DC
├─nvme0n1p7 ntfs F4D6AD0FD6ACD2E2
└─nvme0n1p8 btrfs f9df1b06-24cf-495b-9ef7-e37dd0aeff7a 374.3G 9% /var
/tmp
/opt
/home
/.snapshots
/From grub-config -o
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.
Found Windows 7 on /dev/nvme0n1p1Last edited by ochinko (2022-02-15 13:49:14)
Offline
you can technically remove ntfs3-g again now. Somewhat of an unfortunate situation, might be worth doing a small patch for/report a bug if there's some upstream bugtracker to report this to.
In any case if you consider this [SOLVED] please mark as such by editing the title in your first post.
Offline