On Mon, Feb 3, 2014 at 5:05 AM, Stephan Wiesand <[log in to unmask]> wrote:
> On 2014-02-01, at 19:57, Patrick J. LoPresti <[log in to unmask]> wrote:
>
> Confirmed. But it only happens when you enable the fastbugs repo when installing. That's where grub-0.97-13.11.el5_10.1.x86_64.rpm is from. The package released with 5.10 is ok.

I thought I had checked that, but obviously I messed up. Thanks.

>> Doing "chroot /mnt/sysimage" and then "/sbin/grub" by hand results in:
>>
>>  bash: /sbin/grub: /usr/lib/libc.so.1: bad ELF interpreter: No such
>> file or directory
>
> It's a bit more complicated. When my ks installation reaches %post, /sbin/grub in the chroot environment works fine. But anaconda still crashes. Seems like it uses the installed grub from outside the chroot.

Well, when I said I did "chroot /mnt/sysimage", I meant I ran "chroot
/mnt/sysimage /bin/bash"; i.e., I started a shell inside the installed
system image. Then I found that /sbin/grub fails to execute. This is
similar to what Anaconda itself does.

> No clue why they don't use the (static) /usr/sbin/grub in the initrd.

Maybe because they want to create and use configuration files under
/boot/grub in the installed image, and "chroot" into that environment
was the easiest way to achieve that. Also this way ensures the result
is identical to what happens when you (e.g.) upgrade your kernel on
the running system. grub is a mandatory package, so there is no risk
of its not being present at this point in the installation.

> Anyway, replacing the fastbugs package should fix this.

Confirmed: Rebuilding from the SRPM and replacing the package by hand
works around the issue.

Thanks again.

 - Pat