On 2010-09-24 11:50, Alexander Kurtz wrote:
So after all this was just mdadm bug #583917 combined with the fact that
you used to wrong name (compared to /etc/cryptsetup) when unlocking the
crypto device manually. This of course caused the cryptsetup initramfs
hook to break when recreating the initramfs. As a consequence, your
cryptroot didn't get unlocked during early boot stage. Correct?
Correct.
PS: You should revert /etc/cryptab to the state it had before all the
debugging (i.e. with "UUID="). You should also revert the change you
made to the cryptsetup initramfs hook, for example like this:
apt-get --reinstall install cryptsetup
Thank you, --reinstall is perhaps a safer solution than rolling back the
manual changes I made.
Now I am only left wondering: Was it just the coincidence of mdadm bug
#583917 being new and my installing a new system that prevented GRUB to
be installed properly in said new system, or was I simultaneously hit by
a GRUB bug that's been resolved as well in the meantime? I recall that
installing GRUB had to be done manually, and that this had been awkward.
Best regards,
A.v. Heydwolff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
