Dual booting problems

Why don't you search the forum and/or the wiki pages? There are complete manuals on how to do that? But no, just installing the way you think it has to be and then when you are in trouble you come asking here.



Im looking at the forums, ive read the arch and manjaro wikis but cant find a solution. Neither Grub or refind shoes the entry. Can you help me out?


Why do you think your situation is different from all others? You want to use Windows 10 beside Manjaro. A standard configuration. Do it as is told and it will work. It's as simple as that.

Well, following the entry "[wiki] Windows 10 - Manjaro - Dual-boot - Step by Step]([HowTo] Dual-boot Manjaro - Windows 10 - Step by Step)" which i didnt read until i faced the problem, Ive selected Automatic in the installation method, it was installed in the disk where arch was. The article have a section titled "Oh No - It boots directly to Windows - What do I do?" but in my case its manjaro that boots directly.

cat /etc/fstab
sudo blkid
inxi -Fxzc0

Post please

Important knowledge

Please select the text in the terminal
Paste the text into the post
Select the newly pasted text in the post
Click the </> icon in the post toolbar

This creates nicely formatted text which is readable for other users after you.

( Text was copied from @linux-aarhus)

cat /etc/fstab:

# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=98e2fe61-4893-4bf2-8d54-54744608e882 swap           swap    defaults,noatime 0 2
UUID=7440-FF65                            /boot/efi      vfat    defaults,noatime 0 2
UUID=5fb34669-191f-4d27-b5cc-5bfddd913e02 /              ext4    defaults,noatime,discard 0 1
UUID=44df76b2-cd1f-4a3a-928d-d8d6a92bc578 swap           swap    defaults,noatime,discard 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

sudo blkid:

/dev/sda1: UUID="562fdb8c-d96b-4b70-9ae4-1ce8b03bd7ab" TYPE="ext4" PARTUUID="960515ef-008e-402d-9c55-3df1c32b37f3"
/dev/sda2: UUID="98e2fe61-4893-4bf2-8d54-54744608e882" TYPE="swap" PARTUUID="99686546-d4f8-4637-9965-c840de012210"
/dev/sda3: UUID="febec48c-37bc-40ac-abaa-871dae57ab1d" TYPE="ext4" PARTUUID="3193bf39-0a43-48e7-9bbd-ace55c8b0283"
/dev/sdb1: UUID="70A6D6D0A6D695C6" TYPE="ntfs" PARTUUID="3cdaad39-55f8-48c3-b1a4-4ff9e7d79174"
/dev/sdb2: UUID="9442798F42797738" TYPE="ntfs" PARTUUID="d63ee8a9-b479-4d49-8524-70ab1d7c8dc4"
/dev/sdb3: UUID="B632F3AB32F36EAD" TYPE="ntfs" PARTUUID="cf7537fd-3ace-4dc5-a432-07105cd516dd"
/dev/sdc1: UUID="7440-FF65" TYPE="vfat" PARTUUID="e0b690d5-254c-4d92-bbcd-3f1efd25bbee"
/dev/sdc2: UUID="5fb34669-191f-4d27-b5cc-5bfddd913e02" TYPE="ext4" PARTUUID="4adc389e-c50e-4b75-8668-f68037df4db7"
/dev/sdc3: UUID="44df76b2-cd1f-4a3a-928d-d8d6a92bc578" TYPE="swap" PARTUUID="d490720b-4ff0-42e2-b8ff-7b151c5f110c"

inxi -Fxzc0:

  Host: Desktop Kernel: 4.19.0-3-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 8.2.1 Desktop: Gnome 3.30.1 Distro: Manjaro Linux 
  Type: Desktop Mobo: ASUSTeK model: M5A99X EVO v: Rev 1.xx serial: <filter> 
  UEFI: American Megatrends v: 1708 date: 04/10/2013 
  Topology: 8-Core model: AMD FX-8320 bits: 64 type: MCP arch: Bulldozer 
  L2 cache: 2048 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 56215 
  Speed: 1402 MHz min/max: 1400/3500 MHz Core speeds (MHz): 1: 1402 2: 1398 
  3: 1407 4: 1447 5: 1407 6: 1688 7: 1400 8: 1405 
  Device-1: NVIDIA GK104 [GeForce GTX 660 Ti] vendor: Micro-Star MSI 
  driver: nvidia v: 410.73 bus ID: 01:00.0 
  Display: x11 server: X.org 1.20.3 driver: nvidia 
  resolution: <xdpyinfo missing> 
  OpenGL: renderer: GeForce GTX 660 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 410.73 
  direct render: Yes 
  Device-1: AMD SBx00 Azalia vendor: ASUSTeK M4A89GTD PRO/USB3 
  driver: snd_hda_intel v: kernel bus ID: 00:14.2 
  Device-2: NVIDIA GK104 HDMI Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 
  Device-3: Corsair type: USB driver: hid-generic,snd-usb-audio,usbhid 
  bus ID: 8-1:2 
  Sound Server: ALSA v: k4.19.0-3-MANJARO 
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK P8P67 and other motherboards driver: r8168 
  v: 8.045.08-NAPI port: d000 bus ID: 02:00.0 
  IF: enp2s0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc 
  bus ID: 4-2:2 
  IF: wlp0s19f2u2 state: up mac: <filter> 
  Local Storage: total: 2.05 TiB used: 137.95 GiB (6.6%) 
  ID-1: /dev/sda vendor: Seagate model: ST1500DL003-9VT16L size: 1.36 TiB 
  ID-2: /dev/sdb vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB 
  ID-3: /dev/sdc vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB 
  ID-1: / size: 219.28 GiB used: 6.23 GiB (2.8%) fs: ext4 dev: /dev/sdc2 
  ID-2: swap-1 size: 8.80 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdc3 
  ID-3: swap-2 size: 12.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
  System Temperatures: cpu: 16.4 C mobo: N/A gpu: nvidia temp: 34 C 
  Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 31% 
  Processes: 255 Uptime: 13m Memory: 7.74 GiB used: 1.54 GiB (19.9%) 
  Init: systemd Compilers: gcc: N/A Shell: bash v: 4.4.23 inxi: 3.0.27 
sudo grub-install /dev/sda
sudo update-grub

or /sdc

Ive installed grub already but dont even show up at the startup, manjaro just start straight up.

Win on /sdb
Manjaro on?

Grub on /sdc?

To many/much swap :wink:

Yeah lol, the other swap partition stayed since arch where installed. So, Windows its on sdb, Manjaro on sdc with grub, sda its used as storage.

Install grub on sdc, in bios start hdd set to sdc.

sudo update-grub found Win10???

 Found memtest86+ image: /boot/memtest86+/memtest.bin
Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
 initrd-Abbild gefunden: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-4.14-x86_64.img
 Linux-Abbild gefunden: /boot/vmlinuz-4.14-x86_64
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
 initrd-Abbild gefunden: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
Linux-Abbild gefunden: /boot/vmlinuz-4.19-x86_64

Yes, now Windows 10 is showing up at Grub, but when i select it a error message come up saying "cant find the command ntldr press any key to continue... "

You can see I do not use win.

1 Like

I had dual-boot problems in the past with GRUB and Windows MBR getting messed up, so now I avoid dual-boot 100% by installing Linux on a completely separate, dedicated drive, and F8 into BIOS boot manager whenever I have to boot into Windows.

Dual-booting might be convenient, but pretty hellish when things get corrupted.


@klipo, if you want to start all over again, I'll try to make some sense of what has happened and we'll try to fix it; if you are willing.
Before you proceed, if you want to, please let us know...

  1. Have you added new disk(s) and you change the cabling to your original windows disk (sdb)?
    Or is your windows disk (sdb) from another system that you added to the computer?
    Is it an external drive now?
  2. If 1. above is not true (not from another system, no new disk added), is your windows bootable at all before the point of installing Manjaro? It is important, to be able to fix it.
  3. What is windows partition sdb1, sdb2 and sdb3?
  4. Is your windows in uefi or bios-legacy? If don't know, it is okay to say 'don't know'.
  5. You said error message was "cant find the command ntldr press any key to continue… "
    ntldr command or file? If command, from where? grub does not issue ntldr command.

At manjaro terminal, provide..

sudo parted -l
ls /boot/efi/EFI/

ps: I think your windows is in bios-legacy (in a gpt disk?).
or you had overridden your windows boot files in the $esp if windows is in fact in uefi when you installed manjaro but that would mean your windows $esp is not in windows disk (sdb) which is highly unusual.


No, the disks stay the same, this disk was here and i havent unpluged or changed the cables.

Yes, it was bootable and fully operational.

sdb1 - The Windows filesystem (Program Files, Users, System32, etc)
sdb2 - Windows Recovery (i think)
sdb3 - ? (it have a folder called "Recovery" and inside it has one called "WindowsRE")

I really dont know.

I found that i had a that command on /etc/grub.d/40_custom. I erase what i had there and i think i cant start windows because i dont have this file /EFI/Microsoft/Boot/bootmgfw.efi, so right now im trying to restore it with the Win10 ISO.

parted -l:

Model: ATA ST1500DL003-9VT1 (scsi)
Disk /dev/sda: 1500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  43.0GB  42.9GB  ext4
 2      43.0GB  55.8GB  12.9GB  linux-swap(v1)
 3      55.8GB  1500GB  1444GB  ext4

Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name  Flags
 1      1049kB  499GB  499GB  ntfs               msftdata
 2      499GB   500GB  498MB  ntfs               hidden, diag
 3      500GB   500GB  472MB  ntfs               msftdata

Model: ATA Samsung SSD 840 (scsi)
Disk /dev/sdc: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name  Flags
 1      2097kB  317MB  315MB   fat32                 boot, esp
 2      317MB   241GB  240GB   ext4
 3      241GB   250GB  9449MB  linux-swap(v1)

Error: /dev/sdd: unrecognised disk label
Model: ADATA USB Flash Drive (scsi)                                       
Disk /dev/sdd: 15.5GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 


BootCurrent: 0000
Timeout: 3 seconds
BootOrder: 0000,0001,000D,000A,000B,000C,000E,0009
Boot0000* manjaro
Boot0001* rEFInd Boot Manager
Boot0009* UEFI OS
Boot000A* TSSTcorp CDDVDW SH-222AB
Boot000B* ST1500DL003-9VT16L
Boot000C* Samsung SSD 850 EVO 500GB
Boot000D* Samsung SSD 840 EVO 250GB
Boot000E* ADATA USB Flash Drive

ls /boot/efi/EFI/:

boot  Manjaro  refind  tools

I dont know if i have windows bios-legacy but i checked the partition type and it was gpt in all disks.

Right now, we are still trying to 'make some sense'..of it.
But here's what we know.

  1. Windows, if uefi in gpt, needs an $esp partition, which you do not have (for windows).
    And if it at all it is the same as Manjaro (only $esp in your system), efi file is not there.
    And if there previously (highly unlikely) but accidentally removed (by manjaro installation), it will still be shown in 'efibootmgr' unless manually removed by user (with special 'efibootmgr' command, which you did not do).
  2. Windows, if bios-legacy in gpt disk, needs a special partition (bios_grub) and labelled as such and will be shown in 'parted -l'. You do not have this in your gpt partitioned windows disk.
  3. 40_custom entries has to be manually input by user, not auto-generated by grub.
  4. 'ntldr' command in grub entry is a user-manually created command and not auto-generated by grub.
  5. 'ntldr' command is only for bios-legacy windows and cannot boot a uefi windows.

Okay, that would be the best.
Make sure it is in uefi though.
It may generate its own $esp.
Let us know when you're done with a 'parted -l' and 'efibootmgr' (from manjaro).
When done you may need to boot manjaro with boot-up key (F8~F12) and 'update-grub' and then reset efibootmgr order (efibootmgr -o xxxx,yyyy,zzzz).
Good luck. Cheers.

1 Like

I finally fix it, i needed to recreate that file (/EFI/Microsoft/Boot/bootmgfw.efi) by using the win10 iso. Thanks a lot everyone for helping me out.

Forum kindly sponsored by