Dual boot issue

I have 2 ssd’s. I have windows on a 1tb nvme, and just installed Manjaro on a sata3 ssd. Now I cannot boot windows. I can go into bios (f12 during boot) and select the windows drive but it will not boot. Windows worked just fine until I installed manjaro, and I have to work tomorrow, so this is a big problem for me. Apparently its a grub issue but i am unable to resolve it. Hope I dont get fired tomorrow.

sudo os-prober && sudo update-grub

Did you installed Manjaro in UEFI or BIOS mode? Do you know how Windows was installed?

Just to check before doing anything not recoverable, boot from the Manjaro installation media in UEFI mode. For reference:

  • BIOS booting: https://paste.pics/e0d6dda01c316f55ab8df81c80ac92f7
  • UEFI booting: https://paste.pics/2c280dbbf637e36f9abf62c10870289e
    (Can’t post links now)

From the installation media open a terminal and run:

sudo efibootmgr -v
sudo parted -l
lsblk -f
inxi  -Fxza

[Edited: Commands corrected for future references]

Post here the output of these commands. Please enclose outputs in ``` marks to correctly format the text. Like this:

More output


More output

ok just finished dinner ill get on this now thanks

oh, to answer your questions i installed windows 10 and manjaro both with usb installation media, default settings. This is on a desktop AMD 3400g box. I am trying now to get the requested output

installation media also wont boot i get this result : (grub rescue) (cant post links here, apparently)
please advise. I am starting to get nervous. (wheres my xanax?)

managed to get installation media working again. will post output results shortly

EFI variables are not supported on this system.

(parted -l resulted in no output)

NAME        FSTYPE      FSVER            LABEL            UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0       squashfs    4.0                                                                          0   100% /run/miso/sfs/livefs
loop1       squashfs    4.0                                                                          0   100% /run/miso/sfs/mhwdfs
loop2       squashfs    4.0                                                                          0   100% /run/miso/sfs/desktopfs
loop3       squashfs    4.0                                                                          0   100% /run/miso/sfs/rootfs
└─sda1      crypto_LUKS 1                                 ad58b2c0-1fe4-47da-ab15-9c30bb4ec978                
sdb         iso9660     Joliet Extension MANJARO_KDE_2003 2020-06-06-08-14-33-00                              
├─sdb1      iso9660     Joliet Extension MANJARO_KDE_2003 2020-06-06-08-14-33-00                     0   100% /run/miso/bootmnt
└─sdb2      vfat        FAT12            MISO_EFI         F327-8F27                                           
└─nvme0n1p2 ntfs                                          AA969BC0969B8B87
ystem:    Host: manjaro Kernel: 5.6.15-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC driver=free nouveau.modeset=1 
           i915.modeset=1 radeon.modeset=1 misobasedir=manjaro misolabel=MANJARO_KDE_2003 quiet systemd.show_status=1 
           apparmor=1 security=apparmor 
           Desktop: KDE Plasma 5.18.5 Distro: Manjaro Linux 
Machine:   Type: Desktop System: Gigabyte product: B450 AORUS M v: N/A serial: <filter> 
           Mobo: Gigabyte model: B450 AORUS M v: x.x serial: <filter> UEFI [Legacy]: American Megatrends v: F50 
           date: 11/27/2019 
Battery:   Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus M705 charge: 55% (should be ignored) 
           status: Discharging 
CPU:       Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen+ 
           family: 17 (23) model-id: 18 (24) stepping: 1 microcode: 8108109 L2 cache: 2048 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 59112 
           Speed: 1259 MHz min/max: 1400/3700 MHz Core speeds (MHz): 1: 1258 2: 1259 3: 1258 4: 1295 5: 1331 6: 1258 7: 1260 
           8: 1395 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: amdgpu v: kernel bus ID: 07:00.0 
           Display: x11 server: X.Org 1.20.8 driver: amdgpu FAILED: ati unloaded: modesetting resolution: 1680x1050~60Hz 
           OpenGL: renderer: AMD RAVEN (DRM 3.36.0 5.6.15-1-MANJARO LLVM 10.0.0) v: 4.6 Mesa 20.0.7 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel v: kernel 
           bus ID: 07:00.1 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel 
           bus ID: 07:00.6 
           Sound Server: ALSA v: k5.6.15-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: kernel 
           port: f000 bus ID: 03:00.0 
           IF: eno1 state: down mac: <filter> 
           Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel port: f000 bus ID: 04:00.0 
           IF: wlp4s0 state: down mac: <filter> 
Drives:    Local Storage: total: 1.43 TiB used: 104.5 MiB (0.0%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB block size: physical: 512 B 
           logical: 512 B 
           ID-2: /dev/sda model: 512GB SATA SSD size: 476.94 GiB block size: physical: 512 B logical: 512 B 
           ID-3: /dev/sdb type: USB model: USB DISK 3.0 size: 57.70 GiB block size: physical: 512 B logical: 512 B 
Partition: ID-1: / raw size: N/A size: 10.26 GiB used: 104.5 MiB (1.0%) fs: overlay source: ERR-102 
Sensors:   System Temperatures: cpu: 43.2 C mobo: N/A gpu: amdgpu temp: 43 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 262 Uptime: 3m Memory: 13.68 GiB used: 832.9 MiB (5.9%) Init: systemd Compilers: gcc: 10.1.0 Shell: bash 
           v: 5.0.17 inxi: 3.0.37 

hope i did this correctly
/me holds breath

forgot to mention manjaro is installwed in BIOS mode
i dont know about the windows installation

is should be

sudo parted -l
Model: ATA 512GB SATA SSD (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      1049kB  512GB  512GB  primary               boot

Model:  USB DISK 3.0 (scsi)
Disk /dev/sdb: 62.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      4194kB  62.0GB  62.0GB  primary  ntfs
 2      62.0GB  62.0GB  524kB   primary               lba

Model: Samsung SSD 970 EVO Plus 1TB (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  17.8MB  16.8MB               Microsoft reserved partition  msftres
 2      17.8MB  1000GB  1000GB  ntfs         Basic data partition          msftdata

Yeah there we have it.

A boot with UEFI and GPT Partition Table need a EFI Partition to boot.
A boot with BIOS (CMS/legacy) and GPT Partition needs a 1MB BIOS-Grub partition to boot
A boot with BIOS and MS-DOS Partition table needs nothing like this.

So to be direct your installation of Linux with luks is a linux only installation. You need to use UEFI without secure boot before installation and install it with an efi partition.

Because Windows is UEFI and GPT, legacy Grub can’t boot into windows.

You have two drives. Your Windows is in nvme0n1 drive and it seems to be in BIOS mode.

I guess that you installed Manjaro in sda in BIOS mode but installed grub in nvme0n1 drive, overwriting Windows MBR. But for the reasons megavolt explained, it won’t boot.

You have two options to recover your Windows:

  1. Boot with a Windows install media and repair the MBR (I think bootrec /fixmbr do that). After that you can also do step 2 to get your Linux.

  2. Install Manjaro in BIOS mode again to the second drive (sda), installing grub also in sda. Then use your BIOS boot menu to boot from that disk. Grub should have detected Windows and you should have an option in grub menu to boot Windows that should work. Sda drive have msdos partition type, so you don’t need an extra partition there.

Hope it works.

Generally, if you have to dual-boot with Windows 10, it is always preferable to install all operating systems (starting with Windows 10) using legacy BIOS mode and MBR partitioning. This method eliminates much of the need for troubleshooting and maintenance later on.

I doubt it as UEFI and gpt parted disk is the standard recommendation by Windoze. If done properly, i.e. Secure boot being switched off, AHCI and not raid mode set in firmware then dual boot can be managed. Ideally, on two disks but if one disk is used and two efi partitions have been created this runs smoothly as well.

  1. Windows recommends UEFI and GPT, but is fully comfortable with MBR+BIOS. You just need to be careful that the USB pen drive you use for W10 installation has been partitioned MBR and booted non-UEFI.

  2. Windows + Linux is still possible in GPT+UEFI mode. Consider what happens when you - like me - need FreeBSD too on your computer. FreeBSD is impossible to dual-boot/multi-boot under GPT+UEFI.

The point is, you said

and this is not true. In some cases legacy BIOS and MBR parted disk are the better solution but not always and not preferable.

You can not obviate the fact that BIOS/MBR is designed for one OS in mind and UEFI has support by design to multiple OS. In BIOS diferent OS are competing for the only MBR. In UEFI every OS has it’s own folder.For that reason only in BIOS it’s guaranteed you are going to have “problems” in dual boot with Windows.

I think much of the bad press for UEFI comes from the first buggy implementations of UEFI from many motherboard producers. But the situation is much better from some years ago.

Wrong | Try setting up dual-boot Windows 10 and FreeBSD - now or 10 years later. Once you have done, give your feedback which is better for dual-booting - GPT+UEFI or MBR+BIOS.

I must admit I don’t know what’s the problem with FreeBSD and UEFI, but I was talking about Linux and Windows. I suppose FreeBSD use here is really small.