Hi,
I updated using yum last night and while the new 3.12.5 kernel was installed, it does not show up on grub. So, I did the following:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.12.5-302.fc20.x86_64 Found initrd image: /boot/initramfs-3.12.5-302.fc20.x86_64.img Found linux image: /boot/vmlinuz-3.11.10-301.fc20.x86_64 Found linux image: /boot/vmlinuz-0-rescue-26b05c2e8b5144b4b396c604c823681b Found initrd image: /boot/initramfs-0-rescue-26b05c2e8b5144b4b396c604c823681b.img done
What is causing this not to happen automatically when yum updates the kernel? What do I fix to get this issue taken care of?
Many thanks and best wishes, Ranjan
On Sun, 22 Dec 2013 08:54:54 -0600, Ranjan Maitra wrote:
Hi,
I updated using yum last night and while the new 3.12.5 kernel was installed, it does not show up on grub. So, I did the following:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.12.5-302.fc20.x86_64 Found initrd image: /boot/initramfs-3.12.5-302.fc20.x86_64.img Found linux image: /boot/vmlinuz-3.11.10-301.fc20.x86_64 Found linux image: /boot/vmlinuz-0-rescue-26b05c2e8b5144b4b396c604c823681b Found initrd image: /boot/initramfs-0-rescue-26b05c2e8b5144b4b396c604c823681b.img done
What is causing this not to happen automatically when yum updates the kernel? What do I fix to get this issue taken care of?
Only somebody who is aware of the problem could answer that. You might want to do some trouble-shooting to figure out what has gone wrong. You may examine the "kernel" package scriptlets: rpm -q --scripts kernel You may run the commands found there in an attempt at reproducing the problem. Some are shell scripts. However, since you've overwritten your grub.cfg file already, it could be that the problem will not be reproducible anymore. ;-)
On Sun, 22 Dec 2013 20:14:27 +0100 Michael Schwendt mschwendt@gmail.com wrote:
On Sun, 22 Dec 2013 08:54:54 -0600, Ranjan Maitra wrote:
Hi,
I updated using yum last night and while the new 3.12.5 kernel was installed, it does not show up on grub. So, I did the following:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub.cfg ... Found linux image: /boot/vmlinuz-3.12.5-302.fc20.x86_64 Found initrd image: /boot/initramfs-3.12.5-302.fc20.x86_64.img Found linux image: /boot/vmlinuz-3.11.10-301.fc20.x86_64 Found linux image: /boot/vmlinuz-0-rescue-26b05c2e8b5144b4b396c604c823681b Found initrd image: /boot/initramfs-0-rescue-26b05c2e8b5144b4b396c604c823681b.img done
What is causing this not to happen automatically when yum updates the kernel? What do I fix to get this issue taken care of?
Only somebody who is aware of the problem could answer that. You might want to do some trouble-shooting to figure out what has gone wrong. You may examine the "kernel" package scriptlets: rpm -q --scripts kernel You may run the commands found there in an attempt at reproducing the problem. Some are shell scripts. However, since you've overwritten your grub.cfg file already, it could be that the problem will not be reproducible anymore. ;-)
OK, I have downdated the kernel, run grub2-mkconfig so we should be back on the same plane as before. So how do I debug this? Thanks!
An important thing to note is that the resume=/dev/sda? parameter that I had installed previously to get my system to come back from hibernation is not updated with grub2-mkconfig. So fixing this feature is also very important.
Many thanks again!
Best wishes, Ranjan
On Sun, 22 Dec 2013 14:03:08 -0600, Ranjan Maitra wrote:
OK, I have downdated the kernel, run grub2-mkconfig so we should be back on the same plane as before.
"Should be"? Do you mean the problem is reproducible after simple downgrade of the kernel package?
An important thing to note is that the resume=/dev/sda? parameter that I had installed previously to get my system to come back from hibernation is not updated with grub2-mkconfig.
Where exactly did you add that parameter?
Thanks!
On Sun, 22 Dec 2013 21:08:05 +0100 Michael Schwendt mschwendt@gmail.com wrote:
On Sun, 22 Dec 2013 14:03:08 -0600, Ranjan Maitra wrote:
OK, I have downdated the kernel, run grub2-mkconfig so we should be back on the same plane as before.
"Should be"? Do you mean the problem is reproducible after simple downgrade of the kernel package?
I removed the new kernel, updated grub2-mkconfig and rebooted into the old kernel. Does this not bring it back to the old setup (before installation of the new kernel). Or if your question was if the problem is reproducible in the sense that grub does not automatically update after a yum update (or downdate) of the kernel, then the answer is yes.
An important thing to note is that the resume=/dev/sda? parameter that I had installed previously to get my system to come back from hibernation is not updated with grub2-mkconfig.
Where exactly did you add that parameter?
In /etc/grub2.cfg as in:
linux /vmlinuz-3.11.10-301.fc20.x86_64 resume=/dev/sda2 root=/dev/sda3 ro vconsole.font=latarcyrheb-sun16 nomodeset rhgb quiet
Is this not the right place to have done it?
Many thanks, Ranjan
-- users mailing list users@lists.fedoraproject.org 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
On Sun, 22 Dec 2013 15:26:32 -0600, Ranjan Maitra wrote:
I removed the new kernel, updated grub2-mkconfig and rebooted into the old kernel. Does this not bring it back to the old setup (before installation of the new kernel). Or if your question was if the problem is reproducible in the sense that grub does not automatically update after a yum update (or downdate) of the kernel, then the answer is yes.
Great! Then you can try running the kernel package's %posttrans scriptlet commands manually and try to determine which part fails. Here it calls the kernel-install shell script:
# rpm -q --scripts kernel|tail -2 posttrans scriptlet (using /bin/sh): /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $?
In /etc/grub2.cfg as in:
linux /vmlinuz-3.11.10-301.fc20.x86_64 resume=/dev/sda2 root=/dev/sda3 ro vconsole.font=latarcyrheb-sun16 nomodeset rhgb quiet
Is this not the right place to have done it?
/etc/sysconfig/grub is the file to edit, since grub.cfg may be overwritten (e.g. when running grub2-mkconfig), and if you are not careful when editing the symlink, it will be replaced with a file and disconnected from its target.
# file /etc/grub2.cfg /etc/grub2.cfg: symbolic link to `../boot/grub2/grub.cfg'
On Sun, 22 Dec 2013 22:47:05 +0100 Michael Schwendt mschwendt@gmail.com wrote:
On Sun, 22 Dec 2013 15:26:32 -0600, Ranjan Maitra wrote:
I removed the new kernel, updated grub2-mkconfig and rebooted into the old kernel. Does this not bring it back to the old setup (before installation of the new kernel). Or if your question was if the problem is reproducible in the sense that grub does not automatically update after a yum update (or downdate) of the kernel, then the answer is yes.
Great! Then you can try running the kernel package's %posttrans scriptlet commands manually and try to determine which part fails. Here it calls the kernel-install shell script:
# rpm -q --scripts kernel|tail -2 posttrans scriptlet (using /bin/sh): /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $?
OK, thanks! I am not sure I understood this correctly, but here is what I did:
sudo yum update -y (this brings back the new kernel and installs it).
rpm -q --scripts kernel|tail -2 posttrans scriptlet (using /bin/sh): /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $?
So, this appears to match whatever you have written above. Now what should I do?
In /etc/grub2.cfg as in:
linux /vmlinuz-3.11.10-301.fc20.x86_64 resume=/dev/sda2 root=/dev/sda3 ro vconsole.font=latarcyrheb-sun16 nomodeset rhgb quiet
Is this not the right place to have done it?
/etc/sysconfig/grub is the file to edit, since grub.cfg may be overwritten (e.g. when running grub2-mkconfig), and if you are not careful when editing the symlink, it will be replaced with a file and disconnected from its target.
So, add this resume=/dev/sda2 to the stuff on GRUB_CMDLINE_LINUX ? Any way to do this without the hardcoding for resume?
Thanks again!
This perhaps needs also to be added onto the heplful bug report in:
https://bugzilla.redhat.com/show_bug.cgi?id=948177
?
Thanks again! Ranjan
# file /etc/grub2.cfg /etc/grub2.cfg: symbolic link to `../boot/grub2/grub.cfg' -- users mailing list users@lists.fedoraproject.org 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
On Sun, 22 Dec 2013 16:04:47 -0600, Ranjan Maitra wrote:
OK, thanks! I am not sure I understood this correctly, but here is what I did:
sudo yum update -y (this brings back the new kernel and installs it).
rpm -q --scripts kernel|tail -2 posttrans scriptlet (using /bin/sh): /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $?
So, this appears to match whatever you have written above. Now what should I do?
Well, it depends. What would you like to do?
You could become superuser root, then run exactly the kernel-install command found above, and check the exit return code and watch out for any warning/error it might print. Next step would be to debug the /bin/kernel-install script in an attempt at finding out where it fails. Perhaps it fails within the /sbin/new-kernel-pkg script, perhaps in grubby (that'll be C code then, however), perhaps due to SELinux, or perhaps because it doesn't recognise a valid template in your grub.cfg.
You could also spend some time in bugzilla and search for whether somebody else is affected.
On Mon, 23 Dec 2013 11:52:13 +0100 Michael Schwendt mschwendt@gmail.com wrote:
On Sun, 22 Dec 2013 16:04:47 -0600, Ranjan Maitra wrote:
OK, thanks! I am not sure I understood this correctly, but here is what I did:
sudo yum update -y (this brings back the new kernel and installs it).
rpm -q --scripts kernel|tail -2 posttrans scriptlet (using /bin/sh): /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $?
So, this appears to match whatever you have written above. Now what should I do?
Well, it depends. What would you like to do?
You could become superuser root, then run exactly the kernel-install command found above, and check the exit return code and watch out for any warning/error it might print.
Thanks! $ sudo rpm -q --scripts kernel|tail -2 posttrans scriptlet (using /bin/sh): /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $?
This is all I get. Not sure what it means/how to check the exit return code.
Next step would be to debug the /bin/kernel-install script in an attempt at finding out where it fails. Perhaps it fails within the /sbin/new-kernel-pkg script, perhaps in grubby (that'll be C code then, however), perhaps due to SELinux, or perhaps because it doesn't recognise a valid template in your grub.cfg.
How does one debug the /bin/kernel-install script?
You could also spend some time in bugzilla and search for whether somebody else is affected.
Thanks! I will look around, but judging by how no one has complained on this list or pointed to a BZ entry, perhaps not.
Many thanks again, and best wishes! Ranjan
-- users mailing list users@lists.fedoraproject.org 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
On Mon, 23 Dec 2013 08:20:53 -0600, Ranjan Maitra wrote:
You could become superuser root, then run exactly the kernel-install command found above, and check the exit return code and watch out for any warning/error it might print.
Thanks! $ sudo rpm -q --scripts kernel|tail -2 posttrans scriptlet (using /bin/sh): /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $?
This is all I get.
You've only queried the kernel package for its scriptlets section. You haven't tried to execute the command you can see in there.
Not sure what it means/how to check the exit return code.
By evaluating/examining the $? variable after running a program.
How does one debug the /bin/kernel-install script?
It's better to stop here right away, since I had assumed you would either be capable of performing a few trouble-shooting tasks or be interested enough to want to learn about it.
On Mon, 23 Dec 2013 18:53:40 +0100 Michael Schwendt mschwendt@gmail.com wrote:
On Mon, 23 Dec 2013 08:20:53 -0600, Ranjan Maitra wrote:
You could become superuser root, then run exactly the kernel-install command found above, and check the exit return code and watch out for any warning/error it might print.
Thanks! $ sudo rpm -q --scripts kernel|tail -2 posttrans scriptlet (using /bin/sh): /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $?
This is all I get.
You've only queried the kernel package for its scriptlets section. You haven't tried to execute the command you can see in there.
sudo /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $? grubby fatal error: unable to find a suitable template
I looked around, but almost all the discussion on the web seems to be circa 2011 when grub moved to grub2 so I am not sure that these seem relevant. (In any case, most of them say run grub2-mkconfig but I was trying to get a more long-term solution.)
Not sure what it means/how to check the exit return code.
By evaluating/examining the $? variable after running a program.
How does one debug the /bin/kernel-install script?
It's better to stop here right away, since I had assumed you would either be capable of performing a few trouble-shooting tasks or be interested enough to want to learn about it.
I guess I am trying to learn by taking the first step of finding the process of getting to it? Hence the questions. Perhaps the background needed is too much to figure out on one's own.
Thanks for your time and patience, though! Best wishes, Ranjan
____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth
On Mon, 23 Dec 2013 13:01:46 -0600, Ranjan Maitra wrote:
sudo /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $? grubby fatal error: unable to find a suitable template
Great! As expected.
Save a backup of the current grub.cfg file. It may make sense to publish it somewhere for others to take a look. Next would be to figure out why "grubby" (from package "grubby") fails as above.
The C source file grubby.c says:
/* Find a good template to use for the new kernel. An entry is * good if the kernel and mkinitrd exist (even if the entry * is going to be removed). Try and use the default entry, but * if that doesn't work just take the first. If we can't find one, * bail. */
Verify that there is an initramfs image for your installed kernels. If not, recreate the image file. Which kernel packages are installed? Did any of the previous kernel packages add a working entry to grub.cfg? Do all of the entries in grub.cfg work for you except for the latest?
What happens if you return to the previous kernel by uninstalling the latest kernel package, then run grub2-mkconfig -o /boot/grub2/grub.cfg, then "yum update kernel"? Does it fail again?
On Mon, 23 Dec 2013 21:18:32 +0100 Michael Schwendt mschwendt@gmail.com wrote:
On Mon, 23 Dec 2013 13:01:46 -0600, Ranjan Maitra wrote:
sudo /bin/kernel-install add 3.12.5-302.fc20.x86_64 /boot/vmlinuz-3.12.5-302.fc20.x86_64 || exit $? grubby fatal error: unable to find a suitable template
Great! As expected.
Thanks!
Save a backup of the current grub.cfg file. It may make sense to publish it somewhere for others to take a look.
Here it is:
# # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub #
### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="${saved_entry}" fi
if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi
function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi }
function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi }
terminal_output console set timeout=5 ### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ### menuentry 'Fedora, with Linux 3.11.10-301.fc20.x86_64' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.11.10-301.fc20.x86_64-advanced-f96397ae-311d-4826-8fb0-6a0fe710dd9c' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 54f94607-a593-4d5c-b03a-356574992f4e else search --no-floppy --fs-uuid --set=root 54f94607-a593-4d5c-b03a-356574992f4e fi linux /vmlinuz-3.11.10-301.fc20.x86_64 resume=/dev/sda2 root=/dev/sda3 ro vconsole.font=latarcyrheb-sun16 nomodeset rhgb quiet } menuentry 'Fedora, with Linux 0-rescue-26b05c2e8b5144b4b396c604c823681b' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-0-rescue-26b05c2e8b5144b4b396c604c823681b-advanced-f96397ae-311d-4826-8fb0-6a0fe710dd9c' { load_video insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 54f94607-a593-4d5c-b03a-356574992f4e else search --no-floppy --fs-uuid --set=root 54f94607-a593-4d5c-b03a-356574992f4e fi linux /vmlinuz-0-rescue-26b05c2e8b5144b4b396c604c823681b resume=/dev/sda2 root=UUID=f96397ae-311d-4826-8fb0-6a0fe710dd9c ro vconsole.font=latarcyrheb-sun16 nomodeset rhgb quiet initrd /initramfs-0-rescue-26b05c2e8b5144b4b396c604c823681b.img }
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_ppc_terminfo ### ### END /etc/grub.d/20_ppc_terminfo ###
### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ### if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ###
Next would be to figure out
why "grubby" (from package "grubby") fails as above.
The C source file grubby.c says:
/* Find a good template to use for the new kernel. An entry is
- good if the kernel and mkinitrd exist (even if the entry
- is going to be removed). Try and use the default entry, but
- if that doesn't work just take the first. If we can't find one,
- bail. */
Verify that there is an initramfs image for your installed kernels.
Sorry not sure what this means or how to go about this.
If not, recreate the image file. Which kernel packages are installed?
rpm -qa kernel* kernel-3.11.10-301.fc20.x86_64 kernel-3.12.5-302.fc20.x86_64 kernel-headers-3.12.5-302.fc20.x86_64
Did any of the previous kernel packages add a working entry to grub.cfg?
This is the first update under F20 so no way for me to know this (this was a fresh install).
Do all of the entries in grub.cfg work for you except for the latest?
No.
What happens if you return to the previous kernel by uninstalling the latest kernel package, then run grub2-mkconfig -o /boot/grub2/grub.cfg, then "yum update kernel"? Does it fail again?
I have actually done this by downdating (previously). And had the same effect.
Sorry if these are not what you wanted. I am totally new to this.
Thanks again! Ranjan
-- users mailing list users@lists.fedoraproject.org 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
On Mon, 23 Dec 2013 19:25:49 -0600, Ranjan Maitra wrote:
### BEGIN /etc/grub.d/10_linux ### menuentry 'Fedora, with Linux 3.11.10-301.fc20.x86_64' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.11.10-301.fc20.x86_64-advanced-f96397ae-311d-4826-8fb0-6a0fe710dd9c' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 54f94607-a593-4d5c-b03a-356574992f4e else search --no-floppy --fs-uuid --set=root 54f94607-a593-4d5c-b03a-356574992f4e fi linux /vmlinuz-3.11.10-301.fc20.x86_64 resume=/dev/sda2 root=/dev/sda3 ro vconsole.font=latarcyrheb-sun16 nomodeset rhgb quiet }
There is no "initrd" parameter for this first boot entry! What are the contents of the /boot directory?
If the initramfs image file for this kernel is missing, it's no surprise that grubby doesn't recognise this boot menu entry. The image may be regenerated using "dracut" (see "man dracut").
That it refers to the root device with UUID and /dev/sda3 is strange, too.
On Dec 24, 2013, at 2:12 AM, Michael Schwendt mschwendt@gmail.com wrote:
On Mon, 23 Dec 2013 19:25:49 -0600, Ranjan Maitra wrote:
### BEGIN /etc/grub.d/10_linux ### menuentry 'Fedora, with Linux 3.11.10-301.fc20.x86_64' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.11.10-301.fc20.x86_64-advanced-f96397ae-311d-4826-8fb0-6a0fe710dd9c' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 54f94607-a593-4d5c-b03a-356574992f4e else search --no-floppy --fs-uuid --set=root 54f94607-a593-4d5c-b03a-356574992f4e fi linux /vmlinuz-3.11.10-301.fc20.x86_64 resume=/dev/sda2 root=/dev/sda3 ro vconsole.font=latarcyrheb-sun16 nomodeset rhgb quiet }
There is no "initrd" parameter for this first boot entry! What are the contents of the /boot directory?
Right, so how is this computer even bootable? These kernels, without an initramfs, will face plant on boot.
I've found that anaconda sometimes issues grub2-mkconfig before the initramfs is built, but it got fixed later once new-kernel-pkg called grubby. Yet grubby is failing on this computer, which might be why this entry was never fixed.
The one other time I've seen this behavior, with a missing initrd entry, and grubby's failure to "fix" it, was when I placed /boot on Btrfs (as its own subvolume). This confuses grubby. But I'm not seeing an insmod btrfs in this grub.cfg. And I'm not seeing that this computer has UEFI firmware or it would have an insmod part_gpt.
So I'd like to see the output from:
grub2-install --debug /dev/sda bash -x grub2-mkconfig -o /boot/grub2/grub.cfg /boot/grub2/grub.cfg #from the above command
Chris Murphy
On Tue, 24 Dec 2013 09:04:27 -0700 Chris Murphy lists@colorremedies.com wrote:
On Dec 24, 2013, at 2:12 AM, Michael Schwendt mschwendt@gmail.com wrote:
On Mon, 23 Dec 2013 19:25:49 -0600, Ranjan Maitra wrote:
### BEGIN /etc/grub.d/10_linux ### menuentry 'Fedora, with Linux 3.11.10-301.fc20.x86_64' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.11.10-301.fc20.x86_64-advanced-f96397ae-311d-4826-8fb0-6a0fe710dd9c' { load_video set gfxpayload=keep insmod gzio insmod part_msdos insmod ext2 set root='hd0,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' 54f94607-a593-4d5c-b03a-356574992f4e else search --no-floppy --fs-uuid --set=root 54f94607-a593-4d5c-b03a-356574992f4e fi linux /vmlinuz-3.11.10-301.fc20.x86_64 resume=/dev/sda2 root=/dev/sda3 ro vconsole.font=latarcyrheb-sun16 nomodeset rhgb quiet }
There is no "initrd" parameter for this first boot entry! What are the contents of the /boot directory?
Right, so how is this computer even bootable? These kernels, without an initramfs, will face plant on boot.
I've found that anaconda sometimes issues grub2-mkconfig before the initramfs is built, but it got fixed later once new-kernel-pkg called grubby. Yet grubby is failing on this computer, which might be why this entry was never fixed.
The one other time I've seen this behavior, with a missing initrd entry, and grubby's failure to "fix" it, was when I placed /boot on Btrfs (as its own subvolume). This confuses grubby. But I'm not seeing an insmod btrfs in this grub.cfg. And I'm not seeing that this computer has UEFI firmware or it would have an insmod part_gpt.
So I'd like to see the output from:
grub2-install --debug /dev/sda
Uploading (452.3KiB)... http://ur1.ca/g93u3 -> http://paste.fedoraproject.org/64213/13879023
bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
Uploading (8.6KiB)... http://ur1.ca/g93u5 -> http://paste.fedoraproject.org/64214/02391138
/boot/grub2/grub.cfg #from the above command
Uploading (5.5KiB)... http://ur1.ca/g93ua -> http://paste.fedoraproject.org/64215/79024291
Thanks again, for all the help! Ranjan
Chris Murphy
-- users mailing list users@lists.fedoraproject.org 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
On Tue, 24 Dec 2013 10:28:37 -0600, Ranjan Maitra wrote:
bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
Uploading (8.6KiB)... http://ur1.ca/g93u5 -> http://paste.fedoraproject.org/64214/02391138
So, the initrd for the F20 release kernel 3.11.10-301.fc20 is missing here, too:
+ echo '### BEGIN /etc/grub.d/10_linux ###' + /etc/grub.d/10_linux Found linux image: /boot/vmlinuz-3.12.5-302.fc20.x86_64 Found initrd image: /boot/initramfs-3.12.5-302.fc20.x86_64.img Found linux image: /boot/vmlinuz-3.11.10-301.fc20.x86_64 Found linux image: /boot/vmlinuz-0-rescue-26b05c2e8b5144b4b396c604c823681b Found initrd image: /boot/initramfs-0-rescue-26b05c2e8b5144b4b396c604c823681b.img + echo '### END /etc/grub.d/10_linux ###'
Have you ever booted with that kernel after installing F20? Probably not. ;)
Everything related to updating grub.cfg should work normally for the next kernel update.
Once you've booted to the latest kernel, you could erase the previous kernel with "yum remove kernel-3.11.10-301.fc20" or generate the missing initrd for it as a fallback:
$ su - # dracut /boot/initramfs-3.11.10-301.fc20.x86_64.img 3.11.10-301.fc20.x86_64
On Tue, 24 Dec 2013 18:53:26 +0100 Michael Schwendt mschwendt@gmail.com wrote:
On Tue, 24 Dec 2013 10:28:37 -0600, Ranjan Maitra wrote:
bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
Uploading (8.6KiB)... http://ur1.ca/g93u5 -> http://paste.fedoraproject.org/64214/02391138
So, the initrd for the F20 release kernel 3.11.10-301.fc20 is missing here, too:
- echo '### BEGIN /etc/grub.d/10_linux ###'
- /etc/grub.d/10_linux
Found linux image: /boot/vmlinuz-3.12.5-302.fc20.x86_64 Found initrd image: /boot/initramfs-3.12.5-302.fc20.x86_64.img Found linux image: /boot/vmlinuz-3.11.10-301.fc20.x86_64 Found linux image: /boot/vmlinuz-0-rescue-26b05c2e8b5144b4b396c604c823681b Found initrd image: /boot/initramfs-0-rescue-26b05c2e8b5144b4b396c604c823681b.img
- echo '### END /etc/grub.d/10_linux ###'
Have you ever booted with that kernel after installing F20? Probably not. ;)
Hmmmm, actually I have. This is a new install, and I rebooted a few times.
Everything related to updating grub.cfg should work normally for the next kernel update.
OK, this means that I should reboot now?
Once you've booted to the latest kernel, you could erase the previous kernel with "yum remove kernel-3.11.10-301.fc20" or generate the missing initrd for it as a fallback:
$ su - # dracut /boot/initramfs-3.11.10-301.fc20.x86_64.img 3.11.10-301.fc20.x86_64
Thanks again! Ranjan
-- users mailing list users@lists.fedoraproject.org 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
On Dec 24, 2013, at 9:28 AM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
grub2-install --debug /dev/sda
Looks good.
bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
FYI: Line 79, I do not see resume= having been added to /etc/default/grub, therefore it won't be in the grub.cfg.
Line 127/128, it found kernel 3.12.5-302 and its initramfs. Line 129 only kernel 3.11.10-301 is found, this probably isn't a bootable kernel option. Line 130/131 is the rescue kernel and initramfs, it should work and chances are it's 3.11.10-301.
/boot/grub2/grub.cfg #from the above command
This looks better than the original one, the root=UUID=<uuid> is present instead of referring to root with /dev/sd3. As expected, contains working 3.12 and rescue kernel boot options. The 3.11.10 option probably ends in a kernel panic, because line 91 lacks an initrd command for this kernel entry.
I suggest you do not yum erase the 3.11.10 kernel, because that will remove all of its modules, which the rescue kernel depends on. To remove this from the grub menu, just rm -f the vmlinuz-3.11.10 kernel from the /boot directory. If you want you can also remove its config file. Then you can rerun: grub2-mkconfig -o /boot/grub2/grub.cfg and it will no longer have the 3.11.10 option, just the working 3.12.5 and rescue options.
When the next kernel update comes out, it ought to update this grub.cfg now. If not report back and we'll try to figure out what's going on.
Chris Murphy
On Tue, 24 Dec 2013 11:52:11 -0700 Chris Murphy lists@colorremedies.com wrote:
On Dec 24, 2013, at 9:28 AM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
grub2-install --debug /dev/sda
Looks good.
bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
FYI: Line 79, I do not see resume= having been added to /etc/default/grub, therefore it won't be in the grub.cfg.
Thanks! I made a mistake in the /boot/grub2/grub.cfg entry. (Forgot to actually put in resume= ... I have now fixed that and it shows in there.
Line 127/128, it found kernel 3.12.5-302 and its initramfs. Line 129 only kernel 3.11.10-301 is found, this probably isn't a bootable kernel option. Line 130/131 is the rescue kernel and initramfs, it should work and chances are it's 3.11.10-301.
/boot/grub2/grub.cfg #from the above command
This looks better than the original one, the root=UUID=<uuid> is present instead of referring to root with /dev/sd3. As expected, contains working 3.12 and rescue kernel boot options. The 3.11.10 option probably ends in a kernel panic, because line 91 lacks an initrd command for this kernel entry.
I suggest you do not yum erase the 3.11.10 kernel, because that will remove all of its modules, which the rescue kernel depends on. To remove this from the grub menu, just rm -f the vmlinuz-3.11.10 kernel from the /boot directory. If you want you can also remove its config file. Then you can rerun: grub2-mkconfig -o /boot/grub2/grub.cfg and it will no longer have the 3.11.10 option, just the working 3.12.5 and rescue options.
When the next kernel update comes out, it ought to update this grub.cfg now. If not report back and we'll try to figure out what's going on.
Thanks very much! This has been an enormous help!
Booting into the 3.12.5 kernel now.
Best wishes, Ranjan
Chris Murphy
users mailing list users@lists.fedoraproject.org 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
On Dec 22, 2013, at 3:04 PM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
So, add this resume=/dev/sda2 to the stuff on GRUB_CMDLINE_LINUX ? Any way to do this without the hardcoding for resume?
/etc/sysconfig/grub is a link to /etc/default/grub. You should use resume=uuid=<swapuuid> and insert the blkid uuid for swap instead as /dev/sdX can change between boots and is not reliable. It's strange that your root= in grub.cfg is not using UUID as well.
grubby fatal error: unable to find a suitable template
This is a generic message indicating that it doesn't understand the existing grub.cfg. Can you look in /boot/grub2 and see if there is only grub.cfg or if there is also a grub.cfg.new?
If you have a grub.cfg.new with a more recent date/time than grub.cfg then this means grub2-mkconfig is failing. To get more information you can use:
bash -x grub2-mkconfig
And post those results somewhere like fpaste.
Chris Murphy
On Mon, 23 Dec 2013 18:52:45 -0700 Chris Murphy lists@colorremedies.com wrote:
On Dec 22, 2013, at 3:04 PM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
So, add this resume=/dev/sda2 to the stuff on GRUB_CMDLINE_LINUX ? Any way to do this without the hardcoding for resume?
/etc/sysconfig/grub is a link to /etc/default/grub. You should use resume=uuid=<swapuuid> and insert the blkid uuid for swap instead as /dev/sdX can change between boots and is not reliable. It's strange that your root= in grub.cfg is not using UUID as well.
Thanks very much! So I will add resume=uuid="...." (gigantic alphanumeric number) to the GRUB_CMDLINE_LINUX? Here is what /etc/default/grub reads currently:
GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="vconsole.font=latarcyrheb-sun16 $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) nomodeset rhgb quiet" GRUB_DISABLE_RECOVERY="true"
Should I put this before the nomodeset?
grubby fatal error: unable to find a suitable template
This is a generic message indicating that it doesn't understand the existing grub.cfg. Can you look in /boot/grub2 and see if there is only grub.cfg or if there is also a grub.cfg.new?
No, there is not. Here is what i have in /boot/grub2:
~$ ll /boot/grub2/ total 25K drwxrwxr-x. 2 root root 1.0K Dec 18 19:05 fonts/ drwxrwxr-x. 2 root root 9.0K Dec 22 08:51 i386-pc/ drwxrwxr-x. 2 root root 1.0K Dec 22 08:51 locale/ drwxr-xr-x. 3 root root 1.0K May 9 2012 themes/ -rw-rw-r--. 1 root root 84 Dec 18 19:05 device.map -rw-------. 1 root root 3.6K Dec 23 13:01 grub.cfg -rw-rw-r--. 1 root root 1.0K Dec 19 01:17 grubenv
(Not sure why I have a i386-pc..but this is an x86_64 machine.)
If you have a grub.cfg.new with a more recent date/time than grub.cfg then this means grub2-mkconfig is failing. To get more information you can use:
bash -x grub2-mkconfig And post those results somewhere like fpaste.
$ fpaste bash -x grub2-mkconfig Uploading (0.1KiB)... http://ur1.ca/g90la -> http://paste.fedoraproject.org/64141/87859483
Thanks very much again!
Best wishes, Ranjan
Chris Murphy
users mailing list users@lists.fedoraproject.org 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
On Dec 23, 2013, at 9:32 PM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
So I will add resume=uuid="...." (gigantic alphanumeric number) to the GRUB_CMDLINE_LINUX?
Correct.
Here is what /etc/default/grub reads currently:
GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="vconsole.font=latarcyrheb-sun16 $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) nomodeset rhgb quiet" GRUB_DISABLE_RECOVERY="true"
Should I put this before the nomodeset?
Or after it, or at the end before the last ". It doesn't matter.
(Not sure why I have a i386-pc..but this is an x86_64 machine.)
GRUB is 32-bit on BIOS, and 64-bit on UEFI.
$ fpaste bash -x grub2-mkconfig Uploading (0.1KiB)... http://ur1.ca/g90la -> http://paste.fedoraproject.org/64141/87859483
That didn't work. I'm not sure how to output it to a file, as 'bash -x grub2-mkconfig > bashgrub.txt' doesn't output the debug output from bash -x, it just creates a file from grub2-mkconfig. So unless you know how to do that, I'd just run the command in gnome-terminal, copy-paste it into a text file. Then fpaste the text file.
Chris Murphy
Thanks!
On Mon, 23 Dec 2013 22:25:52 -0700 Chris Murphy lists@colorremedies.com wrote:
On Dec 23, 2013, at 9:32 PM, Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
So I will add resume=uuid="...." (gigantic alphanumeric number) to the GRUB_CMDLINE_LINUX?
Correct.
Here is what /etc/default/grub reads currently:
GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="vconsole.font=latarcyrheb-sun16 $([ -x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) nomodeset rhgb quiet" GRUB_DISABLE_RECOVERY="true"
Should I put this before the nomodeset?
Or after it, or at the end before the last ". It doesn't matter.
(Not sure why I have a i386-pc..but this is an x86_64 machine.)
GRUB is 32-bit on BIOS, and 64-bit on UEFI.
$ fpaste bash -x grub2-mkconfig Uploading (0.1KiB)... http://ur1.ca/g90la -> http://paste.fedoraproject.org/64141/87859483
That didn't work. I'm not sure how to output it to a file, as 'bash -x grub2-mkconfig > bashgrub.txt' doesn't output the debug output from bash -x, it just creates a file from grub2-mkconfig. So unless you know how to do that, I'd just run the command in gnome-terminal, copy-paste it into a text file. Then fpaste the text file.
Thanks again!
Does this work?
fpaste tmp.txt Uploading (3.9KiB)... http://ur1.ca/g90wb -> http://paste.fedoraproject.org/64157/13878647
Best wishes, Ranjan
Chris Murphy
users mailing list users@lists.fedoraproject.org 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
-
Chris Murphy -
Michael Schwendt -
Ranjan Maitra