hey carl, On 20/09/2009 Carl Worth wrote: > > > could you try to reproduce the bug with the cryptsetup from > > > debian/testing[1]? > > > > > > you can do so by installing (downgrading to) the cryptsetup 2:1.0.7-1 > > > package and regenerating the initramfs with > > > # update-initramfs -u -k $(uname -r) > > > > > > you might want to backup the working initramfs before. > > > > > > i guess that the bug is not related to version 2:1.0.7-2 of the > > > cryptsetup package, as nothing regarding device symlinks etc. changed > > > between -1 and -2. > > > > please try the attached (yet untested) patch, and see whether that fixes > > the bug for you. you'll need to update the initramfs after applying the > > patch. > > I really appreciate you following up and suggesting various things to > try. And I'm sorry I didn't get back to you sooner with any feedback. > > Today I'm upgrading my kernel and needing to generate a new initramfs, > so I thought this would be the perfect time to test your proposed fix. > > However, I found that an unmodified initramfs-tools is now generating > a functional initramfs for me. > > Apparently something (certainly the upgrade of some package) changed > my setup so that my root filesystem is no longer a symlink. See the > contents of /etc/fstab and /etc/mtab below and contrast with the > contents I originally reported. > > So things are working for me now, and apparently whatever was buggy > has been fixed. I do wish I could verify the patch you sent, but I > don't know that it would be wise for me to try getting my system into > a state such that I could test it.
the reason for both appearance and disappearance of the bug where last but one and last upload of the lvm2 packages. see the buglog of bug #544773 for more information: http://bugs.debian.org/544773 greetings, jonas
signature.asc
Description: Digital signature

