-
Bug
-
Resolution: Fixed
-
Critical (System)
-
None
-
None
-
None
-
/etc/fstab
/dev/sda1 /boot ext2 noatime 1 2
/dev/sda2 none swap sw 0 0
/dev/sda3 / ext4 noatime 0 1grub.cfg as produced by boot-update
set timeout=3insmod part_msdos
insmod ext2
set root=(hostdisk//dev/sda,msdos1)
search --no-floppy --fs-uuid --set ea1ec171-b9e3-41b9-a361-d0743aa8336a
if loadfont /grub/unifont.pf2; then
set gfxmode=text
insmod all_video
terminal_output gfxterm
fiset menu_color_normal=cyan/blue
set menu_color_highlight=blue/cyanmenuentry "Funtoo Linux - kernel-genkernel-x86-3.19.3-1~exp1"
{ insmod part_msdos insmod ext2 set root=(hostdisk//dev/sda,msdos1) search --no-floppy --fs-uuid --set ea1ec171-b9e3-41b9-a361-d0743aa8336a linux /kernel-genkernel-x86-3.19.3-1~exp1 root=/dev/sda3 rootfstype=ext4 initrd /initramfs-genkernel-x86-3.19.3-1~exp1 set gfxpayload=keep }
set default=0/etc/fstab /dev/sda1 /boot ext2 noatime 1 2 /dev/sda2 none swap sw 0 0 /dev/sda3 / ext4 noatime 0 1 grub.cfg as produced by boot-update set timeout=3 insmod part_msdos insmod ext2 set root=(hostdisk//dev/sda,msdos1) search --no-floppy --fs-uuid --set ea1ec171-b9e3-41b9-a361-d0743aa8336a if loadfont /grub/unifont.pf2; then set gfxmode=text insmod all_video terminal_output gfxterm fi set menu_color_normal=cyan/blue set menu_color_highlight=blue/cyan menuentry "Funtoo Linux - kernel-genkernel-x86-3.19.3-1~exp1" { insmod part_msdos insmod ext2 set root=(hostdisk//dev/sda,msdos1) search --no-floppy --fs-uuid --set ea1ec171-b9e3-41b9-a361-d0743aa8336a linux /kernel-genkernel-x86-3.19.3-1~exp1 root=/dev/sda3 rootfstype=ext4 initrd /initramfs-genkernel-x86-3.19.3-1~exp1 set gfxpayload=keep } set default=0
I'm building funtoo 32-bit using debian-sources. When grub boots, it confuses the root device, /dev/sda3, for /dev/sda1 and mounts it to /boot! It's left as read-only after the filesystem check and the boot process gives up.
Even force-feeding it the devices in /etc/fstab with hardcoded UUIDs, grub insists on mounting the root device to /boot.
The problem is also present when booting the kernel directly (as vmlinuz without an initramfs). That rules out initramfs as the problem.
Grub works fine with a similar kernel under 64-bit.
