Still Won’t Boot – Remote Yum Update Aborted With Session Closing – Won’t Boot

Home » General » Still Won’t Boot – Remote Yum Update Aborted With Session Closing – Won’t Boot
General 7 Comments

Always can count on you for good insight, Harald.

But how do I determine what package from the new kernel is not working to erase and reinstall? If I erase it, will yum upgrade really fix it?
Do I erase the new kernel then install it again?

7 thoughts on - Still Won’t Boot – Remote Yum Update Aborted With Session Closing – Won’t Boot

  • Sounds a lot like what Harald was saying. So for the first step I get:

    # yum list kernel*
    Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile
    * base: ftpmirror.your.org
    * epel: less.cogeco.net
    * extras: ftpmirror.your.org
    * updates: ftpmirror.your.org Installed Packages kernel.i686 2.6.32-279.22.1.el6 @Updates/6.3
    kernel.i686 2.6.32-431.20.3.el6 installed kernel-firmware.noarch 2.6.32-431.20.3.el6 installed kernel-headers.i686 2.6.32-431.20.3.el6 installed Available Packages kernel-abi-whitelists.noarch 2.6.32-431.20.3.el6
    updates kernel-debug.i686 2.6.32-431.20.3.el6 updates kernel-debug-devel.i686 2.6.32-431.20.3.el6 updates kernel-devel.i686 2.6.32-431.20.3.el6 updates kernel-doc.noarch 2.6.32-431.20.3.el6 updates

    and

    # grep kernel /var/log/yum.log Jul 01 14:37:18 Installed: kernel-headers-2.6.32-431.20.3.el6.i686
    Jul 01 14:37:22 Updated: kernel-firmware-2.6.32-431.20.3.el6.noarch Jul 01 14:41:31 Updated:
    libreport-plugin-kerneloops-2.0.9-19.el6.CentOS.i686
    Jul 01 14:42:58 Updated: abrt-addon-kerneloops-2.0.8-21.el6.CentOS.i686
    Jul 01 14:47:47 Updated: dracut-kernel-004-336.el6_5.2.noarch Jul 01 14:47:59 Installed: kernel-2.6.32-431.20.3.el6.i686
    Jul 01 23:10:03 Erased: abrt-addon-kerneloops Jul 01 23:10:04 Erased: libreport-plugin-kerneloops Jul 01 23:13:24 Erased: dracut-kernel Jul 01 23:14:43 Erased: kernel-firmware

  • Why does this not supprise me?

    For you it is clear what ‘broken means’. I have the same problem talking secure identities inside my company. It is clear to me, but others just miss the important points. And you get frustrated going back to ‘basic principles’ and teaching them again….

    So thanks for putting up with me, who rarely has to dig into these parts of systems.

    Ah, perhaps my dyslexia, but I was wondering what drivers or other things I might have to contend with. If it is ‘just’ kernel* I can deal with that.

    Again, a bit of ‘magic’ here that ‘yum upgrade’ knows what should be present and sees to it that these packages get installed. Again, thinking that more than kernel* would need to be removed, then how would it get reinstalled?

    So off I go try again. The box had been off for a year; it was a DNSSEC
    tester (I need to replace my router(s), I think to get DNSSEC working right, and that project is on hold). So it was quite back-leveled. If I end up needing to do a reinstall because I stumbled, so be it as a learning lesson.

  • OK. So…

    # yum erase kernel*

    …

    Removing:
    kernel i686 2.6.32-431.20.3.el6
    installed 89 M
    kernel-firmware noarch
    2.6.32-431.20.3.el6 installed 21 M
    kernel-headers i686 2.6.32-431.20.3.el6
    installed 2.5 M
    Removing for dependencies:
    glibc-devel i686 2.12-1.132.el6_5.2
    installed 953 k
    glibc-headers i686 2.12-1.132.el6_5.2
    installed 2.1 M
    irqbalance i686 2:1.0.4-9.el6_5
    installed 64 k
    mod_perl i686 2.0.4-11.el6_5
    installed 6.0 M
    perl-ExtUtils-MakeMaker i686 6.55-136.el6
    installed 608 k
    perl-ExtUtils-ParseXS i686 1:2.2003.0-136.el6
    installed 61 k
    perl-Test-Harness i686 3.17-136.el6
    installed 399 k
    perl-Test-Simple i686 0.92-136.el6
    installed 184 k
    perl-devel i686 4:5.10.1-136.el6
    installed 1.8 M
    redhat-lsb i686 4.0-7.el6.CentOS
    installed 0.0
    redhat-lsb-compat i686 4.0-7.el6.CentOS
    installed 0.0
    redhat-lsb-core i686 4.0-7.el6.CentOS
    installed 22 k
    redhat-lsb-graphics i686 4.0-7.el6.CentOS
    installed 0.0
    redhat-lsb-printing i686 4.0-7.el6.CentOS
    installed 0.0

    Transaction Summary
    ==========================================================================================================Remove 17 Package(s)

    So I am making notes about what is being removed so I can insure that it gets reinstalled with the upgrade.

    thanks for the help.

  • Well the upgrade is NOT reinstalling all that was erased:

    # yum upgrade

    Installing:
    kernel i686 2.6.32-431.20.3.el6
    updates 26 M
    Installing for dependencies:
    kernel-firmware noarch 2.6.32-431.20.3.el6
    updates 13 M

    Transaction Summary
    ==========================================================================================================Install 2 Package(s)

    So looks like I will have to do all the others step by step.

  • Robert Moskowitz wrote:
    May I offer a suggestion, if it’s still not booting on the new kernel? Try bringing it up on the old one, then mkinitrd while running, so the initrd has all necessary drivers.

    mark

  • m.roth@5-cent.us wrote:

    Oh, another thought: when it gets to the grub boot, edit the kernel line to add rdshell at the end; hopefully, if it fails, it will give you the grub shell, and you can find out where the actual root drive *is*, which is, I think, what it’s looking for and not finding in the grub line that tells it where / is.

    mark

  • As typical, you are right, Harald. I have a conference call in 15min where one of the discussions will be putting up my Teredo testbed, and this system is what is handy for the Teredo (Miredo) server. So I
    rushed more than I should have. But I did piece it all together.

    Now I can pull the rpmforge Miredo code and get that up. Too bad that it is not in EPEL 6; the Miredo maintainer has not commented on why it is not there.