Boot method: CD
Image version: debian-testing-i386-netinst.iso
(daily build: Thu Oct 14 15:15:49 UTC 2010)
Date: 2010-10-14

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [x]
Detect network card:    [x]
Configure network:      [x]
Detect CD:              [x]
Load installer modules: [x]
Detect hard drives:     [x]
Partition hard drives:  [E]
Install base system:    [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]

Comments/Problems:

Hi!

I got a test enviroment with 2 harddisk drives. I want install Debian
with RAID, dm-crypt and LVM. I used for the test a virtual machine
(VirtualBox).


HDD /dev/sda
/dev/sda1 - physical volume for RAID
/dev/sda2 - physical volume for RAID

HDD /dev/sdb
/dev/sdb1 - physical volume for RAID
/dev/sdb2 - physical volume for RAID



Here are my steps:

Configure software RAID

Create MD device: RAID1
- /dev/sda1
- /dev/sdb1

Create MD device: RAID1
- /dev/sda2
- /dev/sdb2

RAID1 device #0 (md0)
- Use as: Ext3
- Mount point: /boot

RAID1 device #1 (md1)
- Use as: physical volume for encryption

Configure encrypted volumes


After this step, the "RAID1 device #0" (md0) is no longer the /boot
partition. This means the installation will fail.

reassign 600235 partman-crypto
retitle 600235 previously defined mount points are discarded after encrypted volumes configuration
tags 600235 d-i
thanks

I can confirm this (at least from a KVM installation). However, I would
not say that the installation will necessarily fail as you still have
the opportunity to (re)define the mount point of md0 after encrypted
volumes have been configured.
Also, the correct procedure might be to configure all devices (raid,
crypto, etc.) *before* defining mount points. Yet, previously defined
mount points should probably not be discarded by partman.

Thanks for your report.