hey, On 05/03/2010 Selim Levy wrote: > On 22 February 2010 18:12, Jonas Meurer <jonas@xxxxxxxxxxxxxxx> wrote: > > you're right. if you're not even asked for a dm-crypt password, then the > > initramfs doesn't even know about the propper root device to unlock. > > what exactly is the output you see at the boot process? does the > > initramfs output any warnings or errors? > > > > > There is no relevant output at the boot process. If I wait long enough for > busybox to appear, then all its info appears... > > The only initramfs errors are the ones I mentioned before: > cryptsetup: WARNING: invalid line in /etc/crypttab - > > Just on a random whim, and despite my better judgement, I decided to modify > my crypttab again. I removed the (original) 'sdb3_crypt' target (which was > a name given automatically by Debian upon installation) and renamed it to > something that makes more sense to me: 'rescue'. Lo and behold, I now no > longer have an error upon updating initramfs. Why or how should simply the > target (name) change anything? > > Well, at least now I get somewhere. Upon booting, I get the typical: > > cryptsetup: source device <device> not found > message. this message does not exist. please paste the _exact_ error message. > I changed my <device> (which was originally /dev/sdb3 and later modified by > me to be given by UUID) in crypttab a few times, but nothing seems to help. > I'm now more and more convinced that when cryptsetup gets called, my /dev/* > have not yet been populated. I wanted to add debugging info, say a simple > echo `ls /dev/sd*` > just before the error I quoted above, but can't seem to find a relevant file > and cryptsetup is a binary. How could I add debugging info (upon boot) just > before that cryptsetup error? In particular, I will want to add debugging > info about the devices and about which modules are loaded. simply modify the initramfs cryptroot script at /usr/share/initramfs-tools/scripts/local-top/cryptroot. the code which invokes cryptsetup begins at line 280. after modifying the script, don't forget to update the initramfs with 'update-initramfs -u'. > I should mention that if I wait about 5 minutes for the busybox prompt, I > can manually luksOpen the drive in question. Could this be some sort of a > race condition that gets resolved with enough patience? it could be possible, but the cryptroot script already contains loops in order to wait for the source device to become available. see the beginning of setup_mapping() in the script. greetings, jonas
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
