In http://www.gentoo.org/doc/en/gentoo-x86-tipsntricks.xml: We should mention that the boot directory must be raid1, or mirrored. The boot directory cannot be raid0, or striped. Under the 2.3 code listing: ... From now onwards, use /dev/md0 for the boot partition, /dev/md1 for the swap partition and /dev/md2 for the root partition. *The following is incorrect procedure* After mounting /dev/md2 on /mnt/gentoo, don't forget to copy over /etc/mdadm.conf to /mnt/gentoo/etc. You should also bind-mount /dev to /mnt/gentoo/dev or create the device nodes in the chrooted environment as well: /*It should read:*/ Continue with the install using /dev/md2 as /mnt/gentoo, /dev/md0 as /mnt/gentoo/boot, and /dev/md1 as swap. After you have unpacked the stage to /mnt/gentoo, don't forget to copy over /etc/mdadm.conf to /mnt/gentoo/etc. You should also bind-mount /dev to /mnt/gentoo/dev or create the device nodes in the chrooted environment as well. With the documented procedure, we are telling the user to create /mnt/gentoo/etc with the contents of /etc/mdadm.conf. We are also telling them to create /dev on the hardrive with the bind-mount. This might cause a few problems = ) Reproducible: Always Steps to Reproduce: 1.Carefully follow the instructions. 2. 3. Actual Results: The contents of /mnt/gentoo/etc were created with /etc/mdadm.conf, and /dev was created with mount -o bind /dev /mnt/gentoo/dev, rather than creating the directories, then placing the desired files inside those directories. Expected Results: Inform the user that the boot directory must be raid1. Instruct the user to return to the main install guide, where s/he would mount the partitions and unpack the stage from cd, then after the directories exist, to go ahead and copy over the files from the liveCD environment to the chroot environment.
you need to mention *why* only raid1 is supported (lilo/grub do not support anything else) i dont see anything wrong with the /etc/mdadm.conf or the bind mount of /dev notes
Most likely because you have not installed recently. If you follow the mdadm.conf and bind mound notes as written, you will simply over-write the files when you unpack the system. The user must unpack the tarball before cping the files. I think this should be made explicit, rather than implied.
(In reply to comment #2) > I think this should be made explicit, rather than implied. That's the only confusing thing actually. After, not right after :) It should simply say 'before chrooting, copy...' Anyway, you don't really need mdadm.conf, it only makes reassembling easier should you need to restart the installation process.
Fixed along with some cleanup. Thanks for reporting.
