I have the latest Manjaro Distro installed and really like it. I do have multiple distros and whenever I update Grub Manjaro always gives me a kernel panic.
I usually have to copy the entry from the grub.cfg in Manjaro to my grub.cfg in Zorin which is my preferred boot loader and that always works. There is a difference between the entries and I'm puzzled why Zorin's Grub2 does not handle Manjaro's entry the same way it looks in Manjaro's own Grub.cfg.
I wonder if it's because of Arch.
Grub2 responds the same way in other distros such as Fedora and Open Suse. It's no big deal because I expect and am ready for it. But it's a minor puzzle. Seems like Manjaro is the only one that does this.

I used to have the same problem with Slackware and Voyager (Xubuntu 16.04).

What fixes it for me when the Dev's upgrade the kernel I boot into Voyager and run:
You wondered if it has something to do with Arch?
Does Arch Linux use Grub 2?

https://www.gnu.org/software/grub/manual/grub.html

we will need more information about it.
probably the actual /boot/grub/grub.cfg and /etc/default/grub from both distros.
please use code tags for code (it's going to be a lot).

I do think it has something to do with Arch. I just installed another Arch derivative Blue Star Linux and I had to follow the same procedure. There's a difference between Zorin's grub.cfg and Blue Stars grub.cfg.
menuentry 'Bluestar Linux' --class bluestar --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-ec0ff592-bc17-4943-9775-a2d0fa05e92b' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd3,msdos9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos9 --hint-efi=hd3,msdos9 --hint-baremetal=ahci3,msdos9 ec0ff592-bc17-4943-9775-a2d0fa05e92b
else
search --no-floppy --fs-uuid --set=root ec0ff592-bc17-4943-9775-a2d0fa05e92b
fi
echo 'Loading Linux linux ...'
linux /boot/vmlinuz-linux root=UUID=ec0ff592-bc17-4943-9775-a2d0fa05e92b rw quiet ipv6.disable=1 loglevel=3 logo.nologo console=tty1 splash=silent,fadein,fadeout,theme:bslx-splash resume=UUID=9b6d8104-acb2-41a1-89c6-a487f987ddd0
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img

This is Zorins Blue Star entry
menuentry "BlueStar Arch (on /dev/sdd9)" --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-ec0ff592-bc17-4943-9775-a2d0fa05e92b' {
insmod part_msdos
insmod ext2
set root='hd3,msdos9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos9 --hint-efi=hd3,msdos9 --hint-baremetal=ahci3,msdos9 ec0ff592-bc17-4943-9775-a2d0fa05e92b
else
search --no-floppy --fs-uuid --set=root ec0ff592-bc17-4943-9775-a2d0fa05e92b
fi
linux /boot/vmlinuz-linux root=UUID=ec0ff592-bc17-4943-9775-a2d0fa05e92b rw quiet ipv6.disable=1 loglevel=3 logo.nologo console=tty1 splash=silent,fadein,fadeout,theme:bslx-splash resume=UUID=9b6d8104-acb2-41a1-89c6-a487f987ddd0
initrd /boot/initramfs-linux.img

The echo entries seem to make the difference. Like I said it's easy to cut and paste and fix it but it's puzzling.

Manjaro is almost identical to the Blue Star with the echo entries.

i don't think it's the echos. there are other differences, but the main bit (linux and initrd) seems identical.
are you sure you are seeing an actual kernel panic?

you can try reinstalling grub from within manjaro (grub-install /dev/sda), maybe it works better the other way around.

you can also try to add a custom entry to zorin's grub configuration. read grub documentation.

and try a little harder with the code tags next time you post code.

I've tried using #grub-install /dev/sda and then update-grub for a number of different distro's. With all producing the same results. Kernel Panic. So, fixing it was always copy and paste from the Manjaro grub.cfg to whichever Distro I was using grub.cfg. Basically it's no problem since I know how to fix it. Just found the value of e2fsck. Had a number of distros that were not booting with the same errors showing up and after using a LiveCD and e2fsck it fixed all of them ( about five )
I'm retired and 77 years old so I have a lot of time on my hands. Have over 50 distros and 7 Windows 10 OS installed over four drives. I just got them all working but I had to go back in forth with Easus Partition Manager. I belong to the Windows Insider Program and get fast track Windows 10 builds.
I still find that for web surfing and most other tasks Linux is hard to beat.

Learning form our Guru, yancek; it might be a good idea to run boot information script to see what's going on.

https://sourceforge.net/projects/bootinfoscript/

When you install Manjaro did you install it to the MBR? <just making sure>

Re-installing Grub as ondoho is certainly worth a try.

http://my-linux-installation-files.b...2-manjaro.html

http://www.dedoimedo.com/computers/grub-2.html
http://ubuntuguide.net/manually-addi...to-grub-2-menu

that's a file system check utility.
if that fixes "it", then "it" has nothing to do with grub.

Are you still getting kernel panic?

The problems I was having that e2fsck fixed were unrelated to the grub.cfg problem. No Kernel panic. Manjaro is working fine since I copied and pasted the entry from Manjaro's
grub.cfg to Zorin's grub cfg. No problem when Manjaro is intalled to the mbr. Only when I grub-install to one of the other distros. Then I have to copy and paste.

1 members found this post helpful.

maybe?

Glad to hear Manjaro is working correctly.

You shouldn't have to keep copying the grub configuration file from Manjaro to Zorin.

-::-I'm thinking the reason why this keeps happening is possibly related to a kernel upgrade.-::-

IF you continue to have this issue you may want to post the output of boot information script so someone can take a look at it.

If you get the time you may want to read through the grub documentation and or the grub manual.

https://www.gnu.org/software/grub/gr...mentation.html

https://www.gnu.org/software/grub/manual/grub.html

Have a look at the Arch Linux Grub Documentation. Maybe Arch configures Grub differently than your other os's?
https://wiki.archlinux.org/index.php/GRUB

HTH