[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#492790: marked as done (debian-installer: lvm+raid+cryptfs blues)

Your message dated Tue, 11 Jan 2011 23:35:11 +0000
with message-id <1294788911.3497.89.camel@eeepc.Belkin>
and subject line 
has caused the Debian Bug report #492790,
regarding debian-installer: lvm+raid+cryptfs blues
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

492790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492790
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: lenny beta 2
Severity: normal

I have used lenny beta 2 d-i several times (not particularly with the system from
which I am sending this report, so please ignore sys info below). 

All systems were x86 - in all cases I was looking to get two physical disks
mdadm mirrored, with a /boot primary partition, and one or more partitions
(sometimes logical, sometimes primary) running lvm on top of crypt. 

The process was not straightforward, and I made the following notes:

1). If d-i finds a nic, it attempts to DHCP even when I do not wish to use the 
    network. Even when I do not have the cable plugged in, in fact.

2). If raid is already set up on the devices from a previous attempt, the 
    assemblable devices are not shown until raid is configured, even though there
    is nothing presented to configure, as all the partitions are already part of
    a logical disk.

3). I was never able to get swap onto encrypted to work, either as an lvm or a
    dedicated partition. 

4). I also could not see anyway to use /dev/random as the
    key-file for swap, rather than hard-wiring a key-phrase.

5). I was never able to boot my crypted system without manually adding the
    parameters to the grub menu.lst file.

6). I was not able to set /boot up prior to the lvm crypt part. (Obviously 
    all the config for /boot can be done long before the lvm and crypt partitions are
    configured). Any attempt to set /boot up and then continue to do config lvm
    and crypt for the root partition causes the partitioner to forget that
    the boot partition is allocated to /boot. (If I set up configure
    the boot partition at the same time as all the other partitions that have
    required lvm and crypt, then it will work: only swap will fail).

I don't have access to the dilab to demo the above using small partitions, but
I have been through the process on enough of my own boxes to believe it is 
easily replicable. I have used both GUI and text versions of the installer. 


-- System Information:
Debian Release: lenny/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.26-M51-D370
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15)

--- End Message ---
--- Begin Message ---

Thanks for your report.
Closing as it's an installation report from Etch which isn't supported
Feel free to test and report any issues against the current debian
installer release (Squeeze RC1) which supports more hardware and also
it's improved.


Melhores cumprimentos/Best regards,

Miguel Figueiredo

--- End Message ---

Reply to: