Hi!
I’m trying to setup dualboot on my new PC with win10 that already installed on my first m2 SSD and I’m trying to install Manjaro on my second m2 SSD without touching windows EFI partition - is it possible? Since I don’t want to restore grub every time after I update BIOS\reinstall win10 (as it was earlier on my old pc setup with only 1 m2 SSD).
Can someone give me a proper guide how to do it? If it’s possible.
Just install Manjaro on its own drive in the installer select erase the whole disk with auto partition it should work.
1 Like
Yes, it’s better than the old days - the worst issue is needing to go to BIOS and reset default boot options.
Grub is good - up/down arrows scroll to select.
rEFInd is simpler - brings up 2 icons, press left or right arrow to select… down arrow to go to ‘settings’ which reboots to BIOS.
If you want to preserve the windows bootloader, when installing to the second drive make sure to also install grub to that drive. You should be able to go into the bios and then select that second drive to normally dual boot. If you ever want to remove Manjaro you can and then change back to the windows drive as the one to boot first.
The grub selection is in the manual partitioning screen. You may have to manually partition the new drive.
Can you please tell me how to do it properly? Because I’ve tried to manually partitioning my second SSD - making 200mb partition with fat32 and selected /boot with boot flag and also created a root partition with ext4 selected / and root flag. Installation was successful but I was only able to boot into windows - no Manjaro loading option in boot option in bios. I’ve also tried to mount new partitions on my second SSD to chroot and made an update-grub option but there was an error “grub-probe: warning: unknown device type nvme0n1” and I still can’t make my PC to boot into grub.
Did you go into the bios and change the boot drive option to the drive you installed grub to?
Yes, but Manjaro didn’t appear in my bios after installation.
Properly = boot from USB, and install - allow the OS to simply wipe and use the entire SSD without doing any manual paritioning. Only ask questions if the OS asks you to choose something which you don’t understand.
Manjaro installer knows what it’s doing, unless you know better.
You will end up with an installation taking full advantage of the SSD.
Grub will just work… and if you interrupt your BIOS, you will see separate entries under the boot menu - it’s ok to set Manjaro as the default.
Thank you for advice, but it didn’t help.
I’ve made an “erase disk and install Manjaro” - installation process ended with success, but I wasn’t able to load to Manjaro with grub and there is no Manjaro boot entry.
Since Manjaro supports only grub - maybe I should enable legacy-boot option on m2 SSD where Manjaro is installed?
Can you post fdisk -l on console ?
I apologize for the long absence - I need to do this when I am in bootable USB?
Yes, you can do that with the Manjaro USB.
My windows is installed on /dev/nvme1n1.
And I want to install Manjaro on /dev/nvme0n1 without touching windows boot sector.
But, I’ve already tried to install Mnajaro on /dev/nvme0n1 and it doesn’t appear in boot menu.
Disk /dev/nvme1n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDS500G3X0C-00SJG0
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: 7DAD5842-53EE-4E50-A37B-B0899BE32A88
Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 206847 204800 100M EFI System
/dev/nvme1n1p2 206848 239615 32768 16M Microsoft reserved
/dev/nvme1n1p3 239616 975704033 975464418 465.1G Microsoft basic data
/dev/nvme1n1p4 975704064 976771071 1067008 521M Windows recovery environment
Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: m.2 Smartbuy PS5013-2280T 128GB
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: 0x4a25ad57
Device Boot Start End Sectors Size Id Type
/dev/nvme0n1p1 * 2048 250067789 250065742 119.2G 83 Linux
Disk /dev/sda: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: HS-SSD-E100 1024
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: 36D2236B-555C-45C6-A87B-BCFE8083445C
Device Start End Sectors Size Type
/dev/sda1 2048 2000408575 2000406528 953.9G Microsoft basic data
Disk /dev/sdb: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: HS-SSD-E100 1024
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: 13E7D772-A31B-6B49-BB6F-D339EB861303
Device Start End Sectors Size Type
/dev/sdb1 34 2000409230 2000409197 953.9G Linux filesystem
Disk /dev/loop0: 18.9 MiB, 19816448 bytes, 38704 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: 692.71 MiB, 726360064 bytes, 1418672 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.93 GiB, 2068860928 bytes, 4040744 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: 643.7 MiB, 674971648 bytes, 1318304 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/sdc: 117.88 GiB, 126567317504 bytes, 247201792 sectors
Disk model: Extreme
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: 0x76655a28
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 2048 247136255 247134208 117.8G 7 HPFS/NTFS/exFAT
/dev/sdc2 247136256 247201791 65536 32M ef EFI (FAT-12/16/32)
Disk /dev/mapper/ventoy: 3.32 GiB, 3569057792 bytes, 6970816 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
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/mapper/ventoy-part1 * 64 6962623 6962560 3.3G 0 Empty
/dev/mapper/ventoy-part2 6962624 6970815 8192 4M ef EFI (FAT-12/16/32)
You need an EFI partition on the drive, where you want to install Manjaro.
1 Like
Well, I don’t know what happend but, after I downloaded latest ISO of Manjaro and tried to install it again - everything worked! Now I have both windows and linux boot entries in my bios and everything loads and works just fine.
I think there were issue with grub2.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.