Can't boot to Arch Linux

[GoGRaDaN]

I have installed Arch Linux in a sperate partition. I want to use mainly Manjaro, thats why i go with the GRUB from Manjaro. Using os-prober, dedected Arch Linux and added it to the Boot Menu in Grub after using sudo update-grub. However, when i try to boot Arch Linux, i get the message: error: invalid magic number. What ever this means.

When i try to go in to edit mode of the Boot Entry for Arch, i see, that Arch was added on a device /dev/nvme0n1p3. I fear this is wrong. Why does os-prober add the dev name here, instead of a UUID or PART-UUID? And how can i fix that Boot entry permanent?

[Nachlese]

@GoGRaDaN

when i try to boot Arch Linux, i get the message: error: invalid magic number. What ever this means.

That was probably an incomplete reproduction of the message
the next part likely was:
you need to load the kernel first

@GoGRaDaN

that Arch was added on a device /dev/nvme0n1p3. I fear this is wrong.

To say anything about that (from here) we would need to know where Arch is installed.
Disk and partition layout:

lsblk -f

and the contents of /boot/grub/grub.cfg

as well as the good old general system information:

inxi -zv8

Where both systems installed in the same mode?
(both UEFI or both MBR)

[linux-aarhus]

@GoGRaDaN

error: invalid magic number

The error means that the magic of dual-booting is not valid - or something like that -

@GoGRaDaN

Arch was added on a device /dev/nvme0n1p3. I fear this is wrong.

Why would you think that? Unless of course you know you installed it on nvme0n1p4.

Short of joking about the fact that you ask Manjaro Forum about your failing Arch Linux which implies you know way more than you let on.

I am thinking more like a mix of bios and efi - which you also know doesn’t mix - I mean you installed Arch Linux - right?

Did you install Arch Linux without boot-loader ?

When os-prober point to /dev/nvme0n1p3 this must be where you installed Arch Linux - right?

And when there is no boot loader you should point to the correct init and kernel in the boot entry.

To fix it permanently, add a custom entry in /etc/grub.d/40-custom defining your Arch Linux boot.

[GoGRaDaN]

Oh the Arch install is fine. However Grub from Manjaro doesnt integrate it into the bootmenu correctly.

I have now disabled os-prober and added the entry via /etc/grub.d/40-custom. This works fine so far. Im using the UUID, which is more reliable as /dev/nvme0n1p3. However i wonder, why os-prober don’t use a UUID and uses /dev/nvme0n1p3 instead. And yes Arch has its own Bootloader and ESP partition (just to separate the kernel files and not to run in a full disk issue).

[linux-aarhus]

@GoGRaDaN

I have now disabled os-prober and added the entry via /etc/grub.d/40-custom.

And this will be permanent - what you asked for - right, of course the term permanent is only for as long as you let it exist

@GoGRaDaN

Im using the UUID, which is more reliable as /dev/nvme0n1p3

Absolutely

[GaVenga]

Your solution is correct.
German instructions (translate with any app like TWP):
https://groups.google.com/g/de.comp.os.unix.linux.misc/c/KWnyJjMUJAg
OR:
https://www.reddit.com/r/archlinux/comments/1k3nkao/tips_for_installing_arch_linux_on_a_dual_boot/

[soundofthunder]

@GoGRaDaN

Im using the UUID, which is more reliable as /dev/nvme0n1p3. However i wonder, why os-prober don’t use a UUID and uses /dev/nvme0n1p3 instead.

Providing the previously requested information;

@Nachlese

To say anything about that (from here) we would need to know where Arch is installed.
Disk and partition layout: lsblk -f

and the contents of /boot/grub/grub.cfg

as well as the good old general system information: inxi -zv8

might allow someone to answer that.

Regards.