> 5). I was never able to boot my crypted system without manually adding > the cryptopts=source=/dev/md1,target=md1_crypt,lvm=vg0-root > parameters to the grub menu.lst file. I just ran an installation on a 3 disk 386 system with: * 1 512 MB RAID 1 taken from each of the 3 drives (md0) * The remaining portions of each drive are a RAID 5 array (md1) * md1 is an encrypted device * The encrypted version of md1 (md1_crypt) is a physical device for lvm I was similarly unable to boot the system, receiving the error that the system was waiting on the root filesystem (after mdadm assembled the raid). I got it to work by adding: cryptopts=target=md1_crypt,source=/dev/md1,lvm=vg_angela0-dom0 as a kernel option. Jamie -- Jamie McClelland 718-303-3204 ext. 101 May First/People Link Growing networks to build a just world http://www.mayfirst.org https://support.mayfirst.org Members Local 1180, Communications Workers of America, AFL-CIO PGP Key: http://current.workingdirectory.net/pages/identity/
Attachment:
signature.asc
Description: Digital signature