Installation of manjaro deepin on a second hdd: error at bootup

Error at bootup: installation of manjaro deepin on a second hdd.

On the first hdd there is windows 7 only.
On sdb5 there is xubuntu. Xubuntu was able to install itself and grub2. The installation was sucessfull and operational.
Recently, I decided to add manjaro on sdb3 with the text installer provided by manjaro deepin 16.06 usb install.
. I installed everything for manjaro except the bootloader, as xubuntu had a functional one.

  • reboot and update-grub in xubuntu

Error at bootup for manjaro deepin.

Here is the grub.cfg entry of xubuntu for manjaro:

menuentry 'Manjaro Linux (16.06) (on /dev/sdb3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-f30736fd-3489-48ac-8396-cece826cdcdc' { insmod part_msdos insmod ext2 set root='hd1,msdos3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos3 --hint-efi=hd1,msdos3 --hint-baremetal=ahci1,msdos3 f30736fd-3489-48ac-8396-cece826cdcdc else search --no-floppy --fs-uuid --set=root f30736fd-3489-48ac-8396-cece826cdcdc fi linux /boot/vmlinuz-4.4-x86_64 root=/dev/sdb3 initrd /boot/initramfs-4.4-x86_64.img } submenu 'Advanced options for Manjaro Linux (16.06) (on /dev/sdb3)' $menuentry_id_option 'osprober-gnulinux-advanced-f30736fd-3489-48ac-8396-cece826cdcdc' { menuentry 'Manjaro Linux (16.06) (on /dev/sdb3)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.4-x86_64--f30736fd-3489-48ac-8396-cece826cdcdc' { insmod part_msdos insmod ext2 set root='hd1,msdos3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos3 --hint-efi=hd1,msdos3 --hint-baremetal=ahci1,msdos3 f30736fd-3489-48ac-8396-cece826cdcdc else search --no-floppy --fs-uuid --set=root f30736fd-3489-48ac-8396-cece826cdcdc fi linux /boot/vmlinuz-4.4-x86_64 root=/dev/sdb3 initrd /boot/initramfs-4.4-x86_64.img }

Any suggestion appreciated.

Would you please change forum section to “Support for community editions” as Manjaro Deepin is not an oficial release. Also please add tags “deepin” and “boot” to your post. Can you also write what is error message during boot.

The entry for intel-ucode is missing in Xubuntu’s grub, it should look like this

menuentry 'Manjaro Linux' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-a6f95914-9f63-4e46-b2b0-9fef42b3d963' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos2'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  a6f95914-9f63-4e46-b2b0-9fef42b3d963
    else
      search --no-floppy --fs-uuid --set=root a6f95914-9f63-4e46-b2b0-9fef42b3d963
    fi
    linux    /boot/vmlinuz-netbook-manjaro-i686 root=UUID=a6f95914-9f63-4e46-b2b0-9fef42b3d963 rw   resume=UUID=a6f95914-9f63-4e46-b2b0-9fef42b3d963 resume_offset=634880
    initrd    /boot/intel-ucode.img /boot/initramfs-netbook-manjaro-i686.img
}

Easiest solution would be to add the entry pressing “e” at startup and editing the menu entry for Manjaro, then in Manjaro do grub-install and update-grub.

3 Likes

@eugen-b:
Thanks a lot for the solution.

@kainonergon:
Sorry for being in the wrong section. You can move me to the appropriate one if you desire.

1 Like

Is there a way to change the manjaro entry from kubuntu?

For one reason or another, as both kubuntu and manjaro are installed on a second hdd. Installing manjaro with its own grub2 will not boot.

There is a windows 7 installation on the first hdd.

Thanks.

In xubuntu (or kubuntu?) create file /etc/grub.d/40_custom and paste there menu entry for Manjaro from /boot/grub/grub.cfg. Add /boot/intel-ucode.img to initrd line. Run sudo update-grub. Use this entry to boot Manjaro. Don’t forget to change this entry when change Manjaro kernel.

1 Like

As @kainonergon proposes, but better place in the pasted code a better recognizable name than ‘Manjaro Linux’ so you can better recognize it in your Grub menu.

2 Likes

There is a message at bootup, I will not get in X:
End kernel panic …
… unable to mount root fs on unknown block (0,0)

Here is an excerpt of my modified grub.cfg:

BEGIN /etc/grub.d/30_uefi-firmware

END /etc/grub.d/30_uefi-firmware

BEGIN /etc/grub.d/40_custom

This file provides an easy way to add custom menu entries. Simply type the

menu entries you want to add after this comment. Be careful not to change

the ‘exec tail’ line above.

path to the partition holding ISO images (using UUID)

probe -u $root --set=rootuuid
set imgdevpath="/dev/disk/by-uuid/$rootuuid"

menuentry ‘MANJARO EUGEN (16.06) (on /dev/sdb3)’ --class gnu-linux --class gnu --class os $menuentry_id_option ‘osprober-gnulinux-simple-f30736fd-3489-48ac-8396-cece826cdcdc’ {
insmod part_msdos
insmod ext2
set root='hd1,msdos3’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos3 --hint-efi=hd1,msdos3 --hint-baremetal=ahci1,msdos3 f30736fd-3489-48ac-8396-cece826cdcdc
else
search --no-floppy --fs-uuid --set=root f30736fd-3489-48ac-8396-cece826cdcdc
fi
linux /boot/vmlinuz-4.4-x86_64 root=/dev/sdb3
initrd /boot/intel-ucode.img /boot/initramfs-4.4-x86_64.img
}
menuentry “porteus on sdb6 64bit porteus 3.2 NEMESIS” {
set root=(hd1,2)
linux /64bit_nemesis/boot/syslinux/vmlinuz from=/dev/sdb2/64bit_nemesis changes=EXIT:/64bit_nemesis login=root
initrd /64bit_nemesis/boot/syslinux/initrd.xz
}
menuentry “porteus on sdb6 64bit porteus 3.1 XFCE” {
set root=(hd1,2)
linux /64bit_v31/boot/syslinux/vmlinuz from=/dev/sdb2/64bit_v31 extramod=/64bit_v31/xfce changes=EXIT:/64bit_v31/xfce login=root
initrd /64bit_v31/boot/syslinux/initrd.xz
}
etc.

Any suggestion?

Thanks.

I think you should use root=UUID=VERY-LONG-NUMBER instead of /dev/sdb3. I guess f30736fd-3489-48ac-8396-cece826cdcdc. Use blkid to be sure about that number.
Also, you need rw in this line.

1 Like

Sorry for taking so much time to reply, your input is appreciated. Your proposition was not enough.

Is there a way for me to get the output of the booting process so I could post it? Unless you think of something else.

Try this.

If works, then put it in Manjaro boot.
Use uuid for that partition not “search -f” though it will work.

Thanks gohlip. Very useful document.

I finally reintalled completely manjaro and now evething works fine.

Thanks all.

Forum kindly sponsored by Bytemark