Bug#456154: debian-installer: amd64 re-boot fails due to missing /etc/crypttab

2007-12-14 Thread Max Vozeler
On Thu, Dec 13, 2007 at 10:54:44AM +0100, Torsten Neumann wrote:
> The setup I tried is a md setup with everything crypted except /boot
..
> Examining the install I found out that there was only an empty
> /etc/crypttab, adding the entry for /dev/md1 manually I could mount
> all the devices and then the system boots normally.

This sounds a lot like the crypto-raid interop 
problem documented here: 

 http://wiki.debian.org/DebianInstaller/RAIDvsCrypto

The wiki page lists some known workarounds.

Max



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#456154: debian-installer: amd64 re-boot fails due to missing /etc/crypttab

2007-12-13 Thread Frans Pop
reassign 456154 partman-crypto
thanks

On Thursday 13 December 2007, Torsten Neumann wrote:
> while trying to install debian I encountered the problem that the
> installed system was unbootable.

I've reassigned the report to the relevant package so that its authors can 
have a look at it.

Cheers,
FJP



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#456154: debian-installer: amd64 re-boot fails due to missing /etc/crypttab

2007-12-13 Thread Torsten Neumann
Package: debian-installer
Severity: important

Hi there,

while trying to install debian I encountered the problem that the
installed system was unbootable. 

The setup I tried is a md setup with everything crypted except /boot

This was reproducible with debian-40r1-amd64-CD-1.iso and unofficial
netinst cd from kmuto (because of ICH9 chipset and e1000 support, my
disks/cdrom are detected properly with the official cd's)

Here is the way I tried to install

1) Partition the disks
/dev/sda1   =>  256MB
/dev/sda2   =>  rest of disk
/dev/sdb1   =>  256MB
/dev/sdb2   =>  rest of disk
2) Set partition type to raid autodetect for all of the above
3) Setup raids
/dev/md0=>  [ sda1, sdb1 ]
/dev/md1=>  [ sda2, sdb2 ]
4) Choose /dev/md0 as ext3 which should be mounted on /boot
5) Choose /dev/md1 as target for a crypted disk (refered as
/dev/mapper/crypt for the rest of this text)
6) Setup LVM with /dev/mapper/crypt as physical disk
vg00 => /dev/mapper/crypt
lvol-root   2GB /
lvol-swap   8GB swap
lvol-usr8GB /usr
lvol-var8G  /var
lvol-home   16GB/home
7) Happily install debian on it. Works all fine until I try to boot
into the just installed system. There it hangs with (something
similiar to)
vg00-lvol-root not found
vg00-lvol-root not found
Waiting for root filesystem
until it drops into a busybox shell. Disks are detected before, since
I got the message from md that md1 is not synchronized.

Doing the same like above just change / to be on md0 instead of the
crypted volume the system boots at least into single user mode.
Examining the install I found out that there was only an empty
/etc/crypttab, adding the entry for /dev/md1 manually I could mount
all the devices and then the system boots normally.

>From above I conjecture that also the failed try with / on the crypted
device was due to a missing crypttab.

Regards
  Torsten
 
Sitz der Gesellschaft / Corporate Headquarters:
Deutsche Lufthansa Aktiengesellschaft, Koeln
Registereintragung / Registration:
Amtsgericht Koeln HR B 2168


Vorsitzender des Aufsichtsrats /
Chairman of the Supervisory Board:
Dipl.-Ing. Dr.-Ing. E.h. Juergen Weber


Vorstand / Executive Board:
Wolfgang Mayrhuber (Vorsitzender / Chairman)
Stephan Gemkow
Stefan Lauer



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]