5:35 p.m.
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.
5:55 p.m.
On Tue, Oct 28, 2008 at 3:35 PM, Bruno Wolff III <bruno(a)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
tom
--
Tom London
7:01 p.m.
On Tue, Oct 28, 2008 at 15:55:57 -0700,
Tom London <selinux(a)gmail.com> wrote:
On Tue, Oct 28, 2008 at 3:35 PM, Bruno Wolff III
<bruno(a)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.
7:37 p.m.
On Tue, Oct 28, 2008 at 15:55:57 -0700,
Tom London <selinux(a)gmail.com> wrote:
On Tue, Oct 28, 2008 at 3:35 PM, Bruno Wolff III
<bruno(a)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
After my last try I did notice that it was trying to switch to the new root before asking
for my passphrase so that it is likely that the
problem is the same. I'll look at it again and see about using an older version of
plymouth. Though I may have to change the device names
back if that is something that is only different for rescue mode.
7:40 p.m.
On Tue, Oct 28, 2008 at 5:37 PM, Bruno Wolff III <bruno(a)wolff.to> wrote:
On Tue, Oct 28, 2008 at 15:55:57 -0700,
Tom London <selinux(a)gmail.com> wrote:
> On Tue, Oct 28, 2008 at 3:35 PM, Bruno Wolff III <bruno(a)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
After my last try I did notice that it was trying to switch to the new root before asking
for my passphrase so that it is likely that the
problem is the same. I'll look at it again and see about using an older version of
plymouth. Though I may have to change the device names
back if that is something that is only different for rescue mode.
The problem described in the BZ above is with mkinitrd, not plymouth.
I just reverted mkinitrd (and nash and libbdevid-python), rebuilt the
initrd and all was OK.
tom
--
Tom London
8:26 p.m.
On Tue, Oct 28, 2008 at 17:40:51 -0700,
Tom London <selinux(a)gmail.com> wrote:
I just reverted mkinitrd (and nash and libbdevid-python), rebuilt the
initrd and all was OK.
Yeah, I meant mkinitrd needed to be reverted. I had to access the bugzilla
through lynx and have been bouncing back and forth.
However, there are two separate problems. One is not running crypt setup
another is that plymouth is using a different way to name encrypted raid
devices than udev.
I got my machine booted up into its (mostly) normal state now but there
are a lot of errors I need to skip during the boot.
To fix things I needed to name / and swap with /dev/mapper/luks-*long luks id*
in /etc/fstab and /boot/grub/grub.conf and leave /home and /play as
/dev/mapper/luks-md? . When udev runs it tries to mount the old style names
for / and swap again and things fail. But I can hit return a bunch of times
and eventually the system finishes booting.
This is what my device names look like:
[bruno@cerberus ~]$ ls /dev/mapper
control luks-md3
luks-9979e281-5710-476f-8536-e49846d53398 luks-md4
luks-9cfcdd2a-d2ff-4c30-818c-344764c7cc21
I wouldn't mind seeing a switch over to using the luks ids but that is probably
going to bite people with existing setups and its probably too late to
develop this since we are at the freeze. So I suggest changing plymouth
(or whatever) back to using names like udev currently does and consider
changing later with some way of simply updating for people.
8:33 p.m.
On Tue, Oct 28, 2008 at 20:26:56 -0500,
Bruno Wolff III <bruno(a)wolff.to> wrote:
On Tue, Oct 28, 2008 at 17:40:51 -0700,
However, there are two separate problems. One is not running crypt setup
another is that plymouth is using a different way to name encrypted raid
devices than udev.
Do you want a separate bugzilla for this?
11:41 p.m.
On Tue, Oct 28, 2008 at 20:33:46 -0500,
Bruno Wolff III <bruno(a)wolff.to> wrote:
On Tue, Oct 28, 2008 at 20:26:56 -0500,
Bruno Wolff III <bruno(a)wolff.to> wrote:
> On Tue, Oct 28, 2008 at 17:40:51 -0700,
>
> However, there are two separate problems. One is not running crypt setup
> another is that plymouth is using a different way to name encrypted raid
> devices than udev.
Do you want a separate bugzilla for this?
This is now bug 468955.
5658
days inactive
5659
days old
7 comments
2 participants
participants (2)
-
Bruno Wolff III -
Tom London