Fedora 16 grub2-mkconfig

[Nicolae Ghimbovschi]

Thanks! I have applied the patch and it worked :)
changed the following in the
/etc/grub.d/30_os-proberOSXUUID="`grub-probe --target=fs_uuid --device
${DEVICE} 2> /dev/null`"
to
OSXUUID="`grub2-probe --target=fs_uuid --device ${DEVICE} 2> /dev/null`"

On Thu, Nov 3, 2011 at 13:11, Michael Schwendt <mschwendt at gmail.com> wrote:
> On Thu, 3 Nov 2011 11:52:16 +0100, MS (Michael) wrote:
>
>> On Thu, 3 Nov 2011 11:34:53 +0200, NG (Nicolae) wrote:
>>
>> > After running grub2-mkconfig -o /boot/grub2/grub.cfg, I saw that
>> > /boot/grub2/grub.cfg was not updated.
>> >
>> > grub2-mkconfig -o /boot/grub2/grub.cfg
>> > Generating grub.cfg ...
>> > Found linux image: /boot/vmlinuz-3.1.0-5.fc16.x86_64
>> > Found initrd image: /boot/initramfs-3.1.0-5.fc16.x86_64.img
>> >  No volume groups found
>> > Found Windows 7 (loader) on /dev/sda1
>> > Found Mac OS X on /dev/sda3
>> >
>> > Instead  /boot/grub2/grub.cfg.new was created, and it did not contain
>> > my custom menu entry.
>> >
>> > What am I doing wrong ? Am I missing a step ?
>>
>> /sbin/grub2-mkconfig is just a shell script. grub.cfg.new is the temporary
>> file it uses for creating and verifying the new config file. Based on your
>> output quoted above you could find out where the script stops unexpectedly
>> and without printing an error message. Especially if the problem is
>> reproducible for you, it shouldn't be difficult to debug the script.
>
> And since this thread has been started on several lists, the "Mac OS X"
> entry above means it's this bug:
>
>  https://bugzilla.redhat.com/737203
>
> --
> Fedora release 16 (Verne) - Linux 3.1.0-5.fc16.x86_64
> loadavg: 0.07 0.09 0.08
> --
> test mailing list
> test at lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test