luks related change is prevented boots of system with encryption over raid

Bruno Wolff III bruno at wolff.to
Wed Oct 29 00:01:01 UTC 2008


On Tue, Oct 28, 2008 at 15:55:57 -0700,
  Tom London <selinux at gmail.com> wrote:
> On Tue, Oct 28, 2008 at 3:35 PM, Bruno Wolff III <bruno at wolff.to> wrote:
> > I rebooted this morning after pulling in some changes from last night (a mix of rawhide and koji updates) and my system was not booting.
> > I so far have noticed that the /dev/mapper/luks-8 naming format has changed and I think that is relating to my problems. I haven't gotten
> > things totally fixed, but i now have my file systems mount under /mnt/sysimage when rebooting. Hopefully now that the /dev directory is
> > there a new mkinitrd will clean things up.
> >
> > I think using the luks ids in the names is a good idea, but it would have been nice to have something automatically handle the transition.
> > I haven't seen a big heads up about this and there probably should have been one. It also was a bad thing to change right before the freeze.
> > So far I have changed /boot/grub/grub.conf and /etc/fstab to use the new names. I'll report back again after hopefully finishing getting
> > things to work again.
> >
> This related?  https://bugzilla.redhat.com/show_bug.cgi?id=468856

It might be related. What I am seeing with the rescue disk was that the files were being opened as dm-? devices were being set up which
I could mount without a problem. What seems to have been the problem in rescue mode is that the names in fstab and grub.conf weren't matching.
For luks devices device names were being used instead of labels.

Now things are working with the rescue boot, but regular boots still aren't working.

I am in the process of updating to current koji and will do a test then in case anything has been fixed. I have the new local repo built
and will be doing the update shortly.




More information about the test mailing list