Giorgos D. Pallas wrote:
> Emanoil Kotsev wrote:
>> I'm pretty sure that the crypt thing is not compatible with lvm. may be
>> this is the problem. I'm not 100% sure though. The problem could be
>> related to previous formatting and using lvm, or some cached information
>> somewhere.
>>
>> what do
Emanoil Kotsev wrote:
> I'm pretty sure that the crypt thing is not compatible with lvm. may be this
> is the problem. I'm not 100% sure though. The problem could be related to
> previous formatting and using lvm, or some cached information somewhere.
>
> what does sudo fdisk -l /dev/hda looks like
On Mon, Nov 03, 2008 at 02:50:32AM -0600, Manoj Srivastava wrote:
> On Sun, Nov 02 2008, Emanoil Kotsev wrote:
>
>
> > I'm pretty sure that the crypt thing is not compatible with lvm. may
> > be this is the problem. I'm not 100% sure though. The problem could be
> > related to previous formatting
On Sun, Nov 02 2008, Emanoil Kotsev wrote:
> I'm pretty sure that the crypt thing is not compatible with lvm. may
> be this is the problem. I'm not 100% sure though. The problem could be
> related to previous formatting and using lvm, or some cached
> information somewhere.
Umm, no. I am
Michael Wagner wrote:
> * Emanoil Kotsev <[EMAIL PROTECTED]> 02.11.2008
>
>> > So my question is, why aren't those volumes correctly deactivated on
>> > shutdown? How does /dev/dm-0
>> > figure into this when I'm mounting /dev/mapper/debian-root as /? Can I
>> > safely ignore this message, or
* Emanoil Kotsev <[EMAIL PROTECTED]> 02.11.2008
> > So my question is, why aren't those volumes correctly deactivated on
> > shutdown? How does /dev/dm-0
> > figure into this when I'm mounting /dev/mapper/debian-root as /? Can I
> > safely ignore this message, or
> > is closing these devices im
Hatta wrote:
> I appreciate all the pointers I've been given. I've looked pretty
> carefully
> at my initramfs, and I've mostly been able to fix it. I still have a few
> questions though.
>
> I did have to create an /etc/crypttab before updating the initramfs. I'm
> not quite sure how to recre
I appreciate all the pointers I've been given. I've looked pretty carefully
at my initramfs, and I've mostly been able to fix it. I still have a few
questions though.
I did have to create an /etc/crypttab before updating the initramfs. I'm
not quite sure how to recreate the configuration the d
Andrew Reid wrote:
> On Monday 20 October 2008 19:13, Hatta wrote:
>> Yes, I have run 'update-initramfs -v -u -k 2.6.24-1-686'
>>
>> This had no effect.
Did you do it after you have booted from the encrypted system or not. I
suppose you did not get the dm_crypto module into the image. This is
bec
On Monday 20 October 2008 19:13, Hatta wrote:
> Yes, I have run 'update-initramfs -v -u -k 2.6.24-1-686'
>
> This had no effect.
>
> I cannot find any documentation as to how the system is supposed to find
> and
> unencrypt encrypted drives. When in the boot process is the system
> supposed to loa
Yes, I have run 'update-initramfs -v -u -k 2.6.24-1-686'
This had no effect.
I cannot find any documentation as to how the system is supposed to find
and
unencrypt encrypted drives. When in the boot process is the system supposed
to load these drives? What commands does it use? In what file
Hatta wrote:
> A short while ago I set up a system with whole disk encryption. I used
> the guided LUKS
> partitioning sytem to make 3 encrypted lvm volumes, root, home, and
> swap_1.
>
> Anyway, I broke that installation, so I needed to reinstall. I used a
> netboot image in expert
> mode, man
A short while ago I set up a system with whole disk encryption. I used
the guided LUKS
partitioning sytem to make 3 encrypted lvm volumes, root, home, and swap_1.
Anyway, I broke that installation, so I needed to reinstall. I used a
netboot image in expert
mode, manually opened the encrypted
13 matches
Mail list logo
