[pkg-cryptsetup-devel] Bug#535801: Bug#535801: cryptsetup: root-device is changed wrongly

Jonas Meurer jonas at freesources.org
Sun Jul 12 22:48:14 UTC 2009


Hey,

On 05/07/2009 johfel at gmx.de wrote:
> sda1Crypt is root filesystem, sda2Crypt is my swap partition.
> 
> In the new version 2:1.0.7~rc1-1 the root device is changed to
> /dev/mapper/sda2Crypt, so the system can't mount its root partition and
> fails to boot.
> 
> I think the recent fix for lilo (I use grub):
>   echo "ROOT=$NEWROOT" >> /conf/param.conf
> in scripts/local-top/cryptroot is responsible for this behavior.

you're correct, "ROOT=$NEWROOT" is added to /conf/param.conf for every
device from /conf/conf.d/cryptroot. that means that it even happens for
resume devices.

i prepared a package which hopefully fixes this issue. it adds a flag
'rootdev' to /conf/conf.d/cryptroot for the real root device at
initramfs creation time. in the initramfs, cryptroot script checks for
that 'rootdev' flag before adding "ROOT=$NEWROOT" to /conf/param.conf.

that way the new introduced bug should be fixed while the lilo bug
remains fixed as well.

could you give the new package a try before I actually upload it to
debian/unstable? (everyone who commented on the bugreport is Cc'ed)

you can find the package (i386 and amd64) at:
http://people.debian.org/~mejo/cryptsetup/

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20090713/73f110a2/attachment.pgp>


More information about the pkg-cryptsetup-devel mailing list