This is the specific example I have found: Installation of Gentoo on Compaq DL-580 server requires usage of cciss.o kernel module to permit access to ServerRaid 53xx-controlled logical drives. When modprobing this module at the initial boot environment prompt, new device nodes are created: /dev/cciss/disc0/disc /dev/cciss/disc0/part1 etc. Continuing with setup, everything proceeds normally, until it's time to install the bootloader. From within the chroot environment, /dev/cciss/* are not accessable because they've not been copied from the boot environment to the chrooted environment. I am not sure of a reliable method of resolving this issue. Installing the bootloader from the initial boot environment (ie, outside the chroot environment) does not appear to work properly, either because of the grub version provided or the file paths to the system (/mnt/gentoo/boot/grub/stage2 instead of /boot/...) Will continue to search for a reliable workaround.
do this before you chroot: mount --bind /dev /mnt/gentoo/dev That will fix it. Remember to "umount /mnt/gentoo/dev" before trying to umount /mnt/gentoo.
