Bug#411284: [Pkg-cryptsetup-devel] Processed: Re: Bug#411284: initramfs-tools: Created initramfs fails to evms_activate

[David Härdeman]

reassign 411284 evms
thanks

On Mon, Feb 19, 2007 at 11:15:20PM +0200, Sami Liedes wrote:
>On Mon, Feb 19, 2007 at 09:38:58PM +0100, David Härdeman wrote:
>> First of all, the 'Volume group "root" not found' warning is harmless. 
>> The reason that you see it is that your luks volume is called 
>> "root-crypted", which corresponds to /dev/mapper/root-crypted which 
>> is the same device name that a lvm LV named "crypted", in VG "root", 
>> would get. 
>
>Ok. Then there's left the error produced by evms_activate after doing
>what it needed to do ("libgcc_s.so.1 must be installed for
>pthread_cancel to work\nAborted") which I mentioned in my original
>report, perhaps that's something that needs to be added to initramfs?

How did you get evms_activate into the initramfs image? The hook scripts 
usually call a shell function which automagically adds all necessary 
libraries as well...which it seems that it hasn't done.

>> Second, cryptsetup already contains code to call evms_activate if the 
>> underlying device is a evms device. The real problem here is that no 
>> crypto-device configuration has been written to /conf/conf.d/cryptroot. 
>> This means that the cryptsetup hook script did not believe that your 
>> root device involved crypto for some reason.
>> 
>> Could you please provide me with the contents of your /etc/crypttab and 
>> /etc/fstab?
>
>Ah, ok, now I think I know what the reason is. I have nothing in my
>crypttab, in fact I had forgotten that such a file exists :) My bad.
>(I did a manual conversion to crypted so it's not a debian-installer
>fault either.)
>
>Now I note that there's a README.initramfs, I think I only read
>README.Debian. I see that crypttab is mentioned there.
>
>Sorry, it was an RTFM bug :)

No problem...I'll reassign this bug report to evms for further investigation 
as to the libgcc_s library...(or perhaps maks knows?)

-- 
David Härdeman