Warning with grub2-mkconfig?

[Ahmad Samir]

On 29/06/14 17:58, Michael D. Setzer II wrote:
> I have 20 identical machines in my classroom lab, and have options that require
> me to update the grub.cfg file on all machines via a script. That process works
> fine, but just know 1 of the 20 machines is showing a warning in the process,
> while the other 19 run with no warning. The grub2 report the same version, and
> all machine are fully updated??
>
> grub2-mkconfig -o /boot/grub2/grub.cfg
> Generating grub.cfg ...
> Found background: /boot/verne.png
> Found linux image: /boot/vmlinuz-3.14.8-200.fc20.x86_64
> Found initrd image: /boot/initramfs-3.14.8-200.fc20.x86_64.img
> Warning: Please don't use old title ‘Fedora, with Linux 3.14.8-200.fc20.x86_64’
> for GRUB_DEFAULT, use ‘Advanced options for Fedora>Fedora, with Linux
> 3.14.8-200.fc20.x86_64’ (for versions before 2.00) or
> ‘gnulinux-advanced-da77086f-03af-4125-9acd-f8a4215b5dd6>gnulinux-3.14.8-200.fc20.x86_64-advanced-da77086f-03af-4125-9acd-f8a4215b5dd6’
> (for 2.00 or later)
> Found linux image: /boot/vmlinuz-3.14.7-200.fc20.x86_64
> Found initrd image: /boot/initramfs-3.14.7-200.fc20.x86_64.img
> Found linux image: /boot/vmlinuz-3.14.5-200.fc20.x86_64
> Found initrd image: /boot/initramfs-3.14.5-200.fc20.x86_64.img
> Found linux image: /boot/vmlinuz-0-rescue-c55c7a49359e497fadc04cf0a1871063
> Found initrd image: /boot/initramfs-0-rescue-c55c7a49359e497fadc04cf0a1871063.img
> Found memtest image: /boot/elf-memtest86+-5.01
> Found Windows 7 (loader) on /dev/sda2
> done
>
> So, don't know why 19 machines would work correctly, but one gives the above
> warning?
>
> Even ran yum reinstall grub2*, but results are the same afterwards as well.
>
> Thanks.

I'd compare /etc/default/grub in the affected machine with the one from 
a machine that doesn't exhibit that warning.

[Michael D. Setzer II]

On 30 Jun 2014 at 11:21, Ahmad Samir wrote:

Date sent:      	Mon, 30 Jun 2014 11:21:27 +0200
From:           	Ahmad Samir 
To:             	Community support for Fedora users 

Subject:        	Re: Warning with grub2-mkconfig?
Send reply to:  	Community support for Fedora users 

    

    
> On 29/06/14 17:58, Michael D. Setzer II wrote:
> > I have 20 identical machines in my classroom lab, and have options
> > that require me to update the grub.cfg file on all machines via a
> > script. That process works fine, but just know 1 of the 20 machines
> > is showing a warning in the process, while the other 19 run with no
> > warning. The grub2 report the same version, and all machine are
> > fully updated??
> >
> > grub2-mkconfig -o /boot/grub2/grub.cfg
> > Generating grub.cfg ...
> > Found background: /boot/verne.png
> > Found linux image: /boot/vmlinuz-3.14.8-200.fc20.x86_64
> > Found initrd image: /boot/initramfs-3.14.8-200.fc20.x86_64.img
> > Warning: Please don't use old title ‘Fedora, with Linux
> > 3.14.8-200.fc20.x86_64’ for GRUB_DEFAULT, use ‘Advanced options
> > for Fedora>Fedora, with Linux 3.14.8-200.fc20.x86_64’ (for
> > versions before 2.00) or
> > ‘gnulinux-advanced-da77086f-03af-4125-9acd-f8a4215b5dd6>gnulinux-3
> > .14.8-200.fc20.x86_64-advanced-da77086f-03af-4125-9acd-f8a4215b5dd6
> >  (for 2.00 or later) Found linux image:
> > /boot/vmlinuz-3.14.7-200.fc20.x86_64 Found initrd image:
> > /boot/initramfs-3.14.7-200.fc20.x86_64.img Found linux image:
> > /boot/vmlinuz-3.14.5-200.fc20.x86_64 Found initrd image:
> > /boot/initramfs-3.14.5-200.fc20.x86_64.img Found linux image:
> > /boot/vmlinuz-0-rescue-c55c7a49359e497fadc04cf0a1871063 Found initrd
> > image: /boot/initramfs-0-rescue-c55c7a49359e497fadc04cf0a1871063.img
> > Found memtest image: /boot/elf-memtest86+-5.01 Found Windows 7
> > (loader) on /dev/sda2 done
> >
> > So, don't know why 19 machines would work correctly, but one gives
> > the above warning?
> >
> > Even ran yum reinstall grub2*, but results are the same afterwards
> > as well.
> >
> > Thanks.
>
> I'd compare /etc/default/grub in the affected machine with the one
> from a machine that doesn't exhibit that warning.

Thanks for the reply, but looked at the files, and they are identical?
The machine is a classroom system, and the one was configured, and then 
cloned to all the other machines, so not sure why the one would act 
differently.
> -- 
> Ahmad Samir
> -- 
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have
> a question? Ask away: http://ask.fedoraproject.org

+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
  Guam Community College  Computer Center                  
  mailto:[e-mail]                            
  mailto:[e-mail]
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins                        
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+----------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS
ROSETTA     16911939.323994   |   SETI        28066819.801758
ABC         16613838.513356   |   EINSTEIN    26934147.994939

[Chris Murphy]

I'm totally guessing, but since /etc/default/grub is the same on working and not working systems, this implicates grubenv. What I'm not sure of is the proper way to obliterate it and make sure it gets recreated correctly. I think you could just delete it, and then:
grub2-install /dev/sda
grub2-mkconfig -o /boot/grub2/grub.cfg

However, before you do that it might be useful to capture some debug output from grub.cfg creation with this:
bash -x grub2-mkconfig

Post the output. This intentionally leaves out the -o. I'm not sure this will tell us why the warning is produced. Also it's just a warning, it's not an actual problem or error.

Chris Murphy

[Tom H]

On Mon, Jun 30, 2014 at 12:51 PM, Chris Murphy  wrote:
> I'm totally guessing, but since /etc/default/grub is the same on working and not working systems, this implicates grubenv. What I'm not sure of is the proper way to obliterate it and make sure it gets recreated correctly. I think you could just delete it, and then:

You can delete it or you can use grub2-editenv to list or unset variables.

[Michael D. Setzer II]

On 30 Jun 2014 at 14:28, Tom H wrote:

Date sent:      	Mon, 30 Jun 2014 14:28:37 -0400
Subject:        	Re: Warning with grub2-mkconfig?
From:           	Tom H 
To:             	Fedora Users 
Send reply to:  	Community support for Fedora users 
> On Mon, Jun 30, 2014 at 12:51 PM, Chris Murphy
>  wrote: > > I'm totally guessing, but since
> /etc/default/grub is the same on working and not working systems, this
> implicates grubenv. What I'm not sure of is the proper way to
> obliterate it and make sure it gets recreated correctly. I think you
> could just delete it, and then:

Ran the yum update again, and it installed 3.14.9 kernel, and then reran the 
grub2-mkconfig on all machine, and now none show the warning? Nothing 
else was done? Accessing the machines from 7 timezones away, so don't 
have direct access to systems till August. But thought it strange that one got 
the warning will 19 didn't?

Thanks again, for the suggestion. Wish I knew what fixed it, but it seemed to 
be something that I didn't do?
> You can delete it or you can use grub2-editenv to list or unset
> variables. -- users mailing list [e-mail] To
> unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of
> Conduct: http://fedoraproject.org/code-of-conduct Guidelines:
> http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question?
> Ask away: http://ask.fedoraproject.org

+----------------------------------------------------------+
  Michael D. Setzer II -  Computer Science Instructor      
  Guam Community College  Computer Center                  
  mailto:[e-mail]                            
  mailto:[e-mail]
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins                        
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+----------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS
ROSETTA     16959984.509916   |   SETI        28132633.578134
ABC         16613838.513356   |   EINSTEIN    27019412.734938