reassign 546610 cryptsetup retitle 546610 cryptsetup: initrd boots from root partition when created, ignores root= cmdline option notfound 546610 0.93.4 found 546610 1.0.7-1 thanks
On Tue, Sep 15, 2009 at 04:04:57PM +0200, Agustin Martin wrote: > On Mon, Sep 14, 2009 at 05:00:47PM +0200, Agustin Martin wrote: Package: initramfs-tools > > Version: 0.93.4 > > Severity: normal > > > > Hi, > > > > I noticed that with an initrd image created by means of sid initramfs-tools > > I can no longer select another root filesystem. It always boots with sid > > root, the filesystem that was root when the initrd image was created. While > > I tried to boot a testing box as root the sid box (where the initrd was > > created) results booted as root. /proc/cmdline has the expected value, > > > > root=/dev/mapper/lvm-testing ro > > > > I however can do that from an initrd image created from lenny with lenny > > initrd-tools and kernel 2.6.26. > > > > I am doing this in a box having everything but boot in lvm inside of an > > encrypted volume. > > I have been looking at this a bit more, seems that this problem may not be > related to initramfs-tools itself, but to debian default 2.6.30 kernel > (2.6.30-6). I installed stable initramfs-tools in sid and rebuilt initrd, > and the same problem was present with 2.6.30 kernel, the same way it was > with sid initramfs-tools. > > I also tried with a 2.6.29 kernel whose initrd was built from sid in June, > and worked as expected. Rebuilt 2.6.29 initrd in current sid and problem reappeared. However seems I found the package responsible for the problem, cryptsetup. If I install lenny cryptsetup (1.0.6-7) and rebuild he initrd things work again as expected. However, if I install previous (1.0.7-1) or current (1.0.7-2) cryptsetup problem reappears. Reassigning, -- Agustin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org