I rebuilt the initrd with the mentioned directive. The modified config file is as follows: BOOTDEV=/dev/hdc BOOTTYPE=iso9660 CRYPTROOT=/dev/hda ROOTTYPE=reiserfs CIPHERTYPE=AES256 DESTINATIONPREFIX=/boot INITRDGZNAME=initrd.gz LOADNATIONALKEYB=0 USEMODULE=0 USEGPGKEY=1 GPGKEYFILE=rootkey.gpg I rebuild initrd.gz as follows: cd loop-aes ./build-initrd.sh build-initrd.conf I then copied the initrd into the cdrom source tree, rebuilt the ISO, and tried to boot. Same problem -- same error. Thanks for your help, Mike On Mon, Jun 9, 2008 at 12:15 AM, Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx> wrote: > Mike Mohr wrote: >> I'm having trouble getting loop-aes to boot an encrypted hard disk. I >> do my testing using qemu, because I don't have to burn CDs over and >> over if things go wrong. At boot time I get about 6-8 pf these errors >> repeated on the system console: >> >> Command "/lib/losetup -e AES256 -I 0 -K /lib/rootkey.gpg -G /lib >> /dev/loop5 /dev/hda" returned error. > > Your build-initrd.sh config says (USEMODULE=1 default) to load a loop.ko > module to kernel. But there is no module to load, and no error message > saying "/lib/insmod /lib/modules-...." returned error. > > That means your build-initrd.sh config "build_in.con" is not the one you > used. Please provide the correct one. It is difficult to see what goes wrong > if I can't see the real config source. > > -- > Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD > - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
