On Tue, 22 Mar 2016 11:46:24 +0100, Dennis Tants wrote: Please don't top-post
> So I thought it would be a GRUB problem, because if I use the grub
> shell with following commands, I can actually boot into the new kernel:
> set prefix=(hd0,msdos1)/grub/
> set root=(hd0,msdos3)
> insmod linux
> insmod normal
> normal
> And then choose to boot the newly created entry.
Ah, you didn't tell us that!
> /etc/fstab:
> /dev/sda1 /boot ext4 defaults 0 2 --->
> UUID = 0aabf45f-9868-471f-bda2-8d7501983048
> /dev/sda3 / ext4 defaults 0 1 --->
> UUID = 42eea483-72a2-4bf6-8491-8bfd63e8fc87
> /dev/sda2 none swap sw 0 0
> /dev/sda4 /home ext4 defaults 0 0
>
> And my /boot/grub/grub.cfg (main part I guess):
> menuentry 'Gentoo GNU/Linux' --class gentoo --class gnu-linux --class
> gnu --class os $menuentry_id_option
> 'gnulinux-simple-42eea483-72a2-4bf6-8491-8bfd63e8fc87' {
> load_video
> if [ "x$grub_platform" = xefi ]; then
> set gfxpayload=keep
> fi
> insmod gzio
> insmod part_msdos
> insmod ext2
> set root='hd0,msdos1'
Which is different to what you used on a manual boot. It appears you can
boot when using /boot on the root filesystem, but not when booting from
the separate boot partition.
Did you have sda1 mounted at /boot when you installed the kernel and ran
grub2-mkconfig?
--
Neil Bothwick
Did you hear about the blind prostitute? You have to hand it to her.
pgpvq_gNFSSoM.pgp
Description: OpenPGP digital signature
