Everytime I tried to compile grub inside the chroot this error comes out. Reproducible: Always Steps to Reproduce: 1.mount /boot 2.emerge -v grub 3. Actual Results: >>> Merging sys-boot/grub-0.94-r1 to / cat: /proc/mounts: No such file or directory cat: /proc/mounts: No such file or directory * * Cannot automatically mount your /boot partition. * Your boot partition has to be mounted rw before the installation * can continue. grub needs to install important files there. * !!! ERROR: sys-boot/grub-0.94-r1 failed. !!! Function mount-boot_mount_boot_partition, Line 53, Exitcode 0 !!! Please mount your /boot partition manually! /boot was mounted livecd root # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/ROOT 7815376 901668 6913708 12% / /dev/hda1 93307 6994 81496 8% /boot Expected Results: Installed grub into the /boot partition I unmounted /boot from within chroot and ran emerge -v grub again and it compiled fine and mounted boot and copied necessary files.
This appears to be a problem with the grub ebuild, not with the CD, nor the kernel. I'm reassigning to the proper group.
I've had this issue before, it was caused by a lack of mounting a proc filesystem at the proper point before chrooting. Ex: mount /dev/hda1 /mnt/gentoo mount /dev/hda2 /mnt/gentoo/boot chroot /mnt/gentoo /bin/bash Will most likely cause this bug. You need to issue the mount -t proc none /mnt/gentoo/proc command before you chroot. As such, it doesn't appear to be bug. Unless proc was mounted at the time and this wasn't mentioned.
Please close as RESOLVED NEEDINFO, unless the reporter can tell us whether or not he remembered to mount /proc. If /proc is not mounted, no boot partition will show up in /proc/mounts, leading to this bug.
Jake, please reopen this bug when you have the info that robert requested
Ok, I must have forgotten to mount /proc. Sorry about that :-). thanks for the info tho...