Hi,
> and thanks for the trace, the problem is indeed here:
> >ioctl(3, DM_TABLE_LOAD, 0x80a2040) = -1 EINVAL (Invalid argument)
>
> that means that "crypt" is not a valid device-mapper target.
>
> That in turn means that dm-crypt was not loaded and could not be
> dynamically loaded by the kernel.
As you should be able to observe from my sent kernel config i have built
dm_crypt into the kernel, therefore it cannot (and has not to) be loaded
as a module.
regards,
Johannes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
