On Sun, Nov 03, 2013 at 18:55:07 CET, merc1984@xxxxxx wrote: > I can't figure out how to subscribe to the list, so I hope that just > sending is OK. Subscription info is at the bottom of http://code.google.com/p/cryptsetup/ > I've installed SolydX (Debian), but it won't boot. It never asks me for > sda3's password, and after a bit always drops me to (initramfs), saying > that no root disk was found. Indeed there is no /dev/mapper/sda3_crypt. Sounds like SolydX just does not support root-on-LUKS. Or maybe you just did not configure it right. But that the installer does not support encryption is a dead giveaway. Best complain there, not here. Booting to encrypted disk is somethign the distribution has to handle, not cryptsetup. If you plan to fix this yourself, just make sure cryptsetup and all required libraries are on the initrd, the kernel has the required modules in the initrd. Then open the device with cryptsetup and mount it. Next steps are documented here: https://www.kernel.org/doc/Documentation/initrd.txt under "Changing the root device". You can try this manually from the shell you get in the initramfs to figure out what is wrong. Arno > For some reason, on boot it is not setting up the luks disk. My method > below works just fine for a SolydK install (KDE), but not for a SolydX > install (XFCE). > > The installer does not support encryption, so I installed it to > partitions: > /boot /dev/sda1 200MB ext3 > / /dev/sda4 1.8TB jfs > > While still in the SolydX live DVD: > # cryptsetup luksFormat /dev/sda3 > # cryptsetup luksOpen /dev/sda3 sda3_crypt > # mkfs.jfs /dev/mapper/sda3_crypt > # mkdir /media/3 > # mount /dev/mapper/sda3_crypt /media/3 > > Now I copied everything from sda4 (the / install) to sda3 > # rsync --archive --hard-links --numeric-ids --progress > /media/solydxk/???/* 3 > > # cd /media/3/etc > In /etc/crypttab (which doesn't exist in SolydX until I create > it, in contrast with SolydK which has one): > sda3_crypt /dev/sda3 none luks > In fstab: > /dev/mapper/sda3_crypt / jfs > errors=remount-ro,noatime 0 1 > > # mount /dev/sda1 /media/3/boot > # cd /media/3 > # mount -t proc proc proc/ > # mount -t sysfs sys sys/ > # mount -o bind /dev dev/ > # mount -t devpts pts dev/pts/ > # chroot /media/3 /bin/bash > > In /etc/initramfs-tools/modules: > dm_mod > dm_crypt > aes_x86_64 > > Then > # which cryptsetup > /usr/bin/cryptsetup > # update-initramfs -k all -u > # nano /etc/default/grub and add to > GRUB_CMDLINE_LINUX_DEFAULT > ipv6-disable=1 > # update-grub > > > > -- > http://www.fastmail.fm - Same, same, but different... > > _______________________________________________ > dm-crypt mailing list > dm-crypt@xxxxxxxx > http://www.saout.de/mailman/listinfo/dm-crypt -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@xxxxxxxxxxx GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718 ---- There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. --Tony Hoare _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
