Dual Booting with Windows 10 - fails to find partition

Hello Manjaros(? Manjaro-ers?)!

I have been researching distros far too long instead of toying with Linux in multiple environments and testing them out on bootable drives, and finally took the plunge last night with Manjaro-Gnome. I went through the process a couple times of burning the iso to a bootable usb, because my first couple attempts were clearly a little off, small things like applications closing, images not appearing etc. I realized I had not done checksum checks and when a download finally matched, I was up and running!

A bit of background on my setup. I have three drives on my computer:
2tb SSD (Windows)
1tb HDD (old windows, completely wiped, now formatted for Linux)
128gb (old boot drive) since used for storage and planning to use as shared storage between the two OS.

I moved onto attempting to install manjaro using the provided installer. I was stuck with an issue where it was saying 1 module loading. So I finally found that you could close it and try running the installer from the command line, which I did, and lead me to look into a partitioning problem, which I seemed to have some remnants of trying to partition the particular drive in windows, so I used gparted to correct the issue. I then found some other guides and things to disable/enable in the bios in order to be successful. At some point, the installer did not hang on the "1 module" issue.. but the installer actually found my windows OS and its partitions (2tb SSD) and asked me if I wanted to install there, no other drives were listed, neither of my other two, the one formatted recently by gpart, and the other 128gb either.

At another point... I was able to try and install the system straight through the CLI and was able to select configuring my partitions in which I was able to create the boot partition needed for gnome. When it came time to mount the partitions and "root" was up, I selected my larger of the two (one was 512mb, and the other was still the remaining drive). It then failed with some sort of permissions error that I don't have on hand right now.

After looking at some more threads I found this one:


Which has now made me wonder if I have an issue because my windows installation is "legacy" and therefore not uefi? I'm assuming it is legacy, as when I turned on UEFI only in the bios, windows was no longer a boot option and only my usb was available. And the author seems to indicate that just means I can't install Manjaro side by side? Is that just if I'm attempting to do them on the same drive, or on the same system?

I have spent about 24hours at this point, 8 yesterday and 16 today to no avail. I really don't want to give up, but was talking with a friend today who told me he ran into issues as well and just gave up during the install process after about 14 hours of tinkering.

TL;DR:

  • Attempting to run Manjaro on separate hard drive from Windows
  • Partitioning has been the failure point for all of my attempts so far
  • Can you install Manjaro in the same system as a "legacy" Windows 10 install?

This is a bit small ... :wink:

Make clear to decide if you want to have a dual boot with all systems in legacy/msdos parted disk with MBR or all systems with UEFI/gpt parted disk. Mixing these will cause that you won't be able to boot Windoze via grub, later-on.

The guide from @linux-aarhus is given for UEFI/gpt, for legacy systems it's a bit different as you don't need a /boot/efi partition in that case as boot.img goes to the MBR in this case. If your Windoze is installed in legacy mode with an msdos parted disk and your BIOS does not support UEFI and you accept to be limited to max. 2 TB drive size you can certainly install everything in legacy/msdos parted mode which works fine as well. Just make sure to boot your install media (disk or USB stick) in the same mode as you want to install Manjaro. In that case if asked by the installer select MBR for the bootloader (grub) location.

Personally, I would do the whole partitioning upfront with Gparted and not with Calamares.

Edited my post with that! Thanks for pointing that out.

As to your point about MBR vs GPT, I think that was my issue, I think most of my testing after fixing the corrupted USB was done in the UEFI and that could be why it wasn't brining up the right drive, in the installer, I don't know.

As an update, I did finally go through the install process through Manjaro Architect, when it came to root, it mounted successfully, but I wasn't sure if I did indeed need to do anything for boot, the instructions above seemed to indicate there was no need... but I'm not sure how to get my BIOS to see that drive as bootable. I just went into bios to try and boot with my "successful install" but I'm wondering if I did need to do something with the boot part of the mounting...

The grub stuff is new to me (again total novice here with this stuff). So perhaps there is just something I need to do around that... googles what grub is and opens many links

If properly installed you only need to select the drive in your firmware (to boot from it), no special boot flag or something like that needed in legacy/msdos installs.

When you want to learn more about grub, start here:

Hmmmm, something must be wrong then, after selecting the drive in the BIOS boot menu, I just saw a black screen with a cursor for about 10 minutes before giving up.

EDIT: Yep, I just realized I was following another page for part of it I had tabbed to, and thought it was the explanation of dual booting, going to retry.

However, I'm still confused why I could run through an install using the CLI architect, but cannot do it through the included Clamares Installer. It just refuses to not crash with the same partition issue after 9 seconds of trying to load "1 module".

sudo parted -l output:

Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  106MB   105MB   primary  ntfs         boot
 2      106MB   2000GB  2000GB  primary  ntfs
 3      2000GB  2000GB  564MB   primary  ntfs


Model: ATA KINGSTON SV300S3 (scsi)
Disk /dev/sdb: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

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


Model: ATA WDC WD1003FZEX-0 (scsi)
Disk /dev/sdc: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  1000GB  1000GB  primary  ext4


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

Number  Start   End     Size    Type     File system  Flags
 2      2773MB  2777MB  4194kB  primary               esp

sudo fdisk -l output:

Disk /dev/sda: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 860 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1172ffd5

Device     Boot      Start        End    Sectors  Size Id Type
/dev/sda1  *          2048     206847     204800  100M  7 HPFS/NTFS/exFAT
/dev/sda2           206848 3905927280 3905720433  1.8T  7 HPFS/NTFS/exFAT
/dev/sda3       3905927344 3907029167    1101824  538M  7 HPFS/NTFS/exFAT


Disk /dev/sdb: 111.81 GiB, 120034123776 bytes, 234441648 sectors
Disk model: KINGSTON SV300S3
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 82ED7C9E-B3EB-48F8-99E6-91CA8FDDB55C

Device     Start       End   Sectors   Size Type
/dev/sdb1     34     32767     32734    16M Microsoft reserved
/dev/sdb2  32768 234438655 234405888 111.8G Microsoft basic data


Disk /dev/sdc: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD1003FZEX-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x346435d3

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdc1        2048 1953523711 1953521664 931.5G 83 Linux


Disk /dev/loop0: 64.78 MiB, 67903488 bytes, 132624 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 602.98 MiB, 632250368 bytes, 1234864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1.29 GiB, 1380737024 bytes, 2696752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 596.6 MiB, 625012736 bytes, 1220728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdd: 28.92 GiB, 31029460992 bytes, 60604416 sectors
Disk model: USB DISK 3.0    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdd1  *         64 5415071 5415008  2.6G  0 Empty
/dev/sdd2       5415072 5423263    8192    4M ef EFI (FAT-12/16/32)

I'm giving up for now, as I have work in 2 hours and should probably get some sleep. If anyone has any ideas I'll likely give this another spin tomorrow or the day following. I simply cannot get the installer to work on its own. Will probably start next with another architect install and try something different when I get to the bootloader stuff.

If the installation went fine but failed at installing the bootloader, you might be able to do it manually. Please refer to the guide at:
https://wiki.manjaro.org/index.php?title=Restore_the_GRUB_Bootloader

If you disable UEFI in the firmware - and you Windows go missing - then your Windows is probably EFI based.

You cannot - and should attempt to - install both a Legacy and UEFI system on the same hardware - as this will only lead to confusion.

Disable Legacy in your systems firmware - if Windows boot - fine - install Manjaro as EFI system.

Always use the same type of installation when using dual-boot.

With a live Manjaro ISO - open a terminal - and check the content of this folder

ls /sys/firmware/efi/efivars

If the folder exist if will produce a file listing and your system is booted using EFI - just follow the guide - especially with relation to the preparations.

Though this looks like a legacy Windows:

Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  106MB   105MB   primary  ntfs         boot
 2      106MB   2000GB  2000GB  primary  ntfs
 3      2000GB  2000GB  564MB   primary  ntfs

:thinking:

Indeed it does - :thinking: - why would OP write

There is a certain amount of contradicting information - no wonder it has become a problem.

  • sda is bios parttion schema but partitions look intended for efi.
  • sdb is gpt with a vfat partition
  • sdc is easy - this is just one big ext4 partition
  • sdd is usb

Despite the misleading info in OP it seems to be a BIOS/MBR installation.

I would

  • Disconnect every disk you don't need for your Manjaro install.
  • Disable EFI - enable CSM - activate Legacy boot - a loved one has many names.
  • Boot Manjaro ISO - install to the - only device available.
  • Shutdown - reconnect the remaining disks
  • In system firmware set boot priority to the device you installed Manjaro to.
  • Boot the system to Manjaro
  • Open a terminal and use os-proper to locate your Windows
  • Update your grub to reflect it
1 Like

To address your latest reply. I used the incorrect negative there for sure. I should probably reread it today as I was 6 hours past my normal bedtime lol.

You are correct, it should have said when I turned it to ONLY UEFI it would not show windows to boot from.

Well, I just finished up the install I ran overnight! Apparently it was just my bootloader options in the install that messed me up!

The only question that remains would appear to be why the Calamares installer would not recognize any partitions. But using the CLI architect certainly works!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by