On 07/02/2014 10:25 AM, Robert Moskowitz wrote: > On 07/02/2014 10:20 AM, Robert Moskowitz wrote: >> On 07/02/2014 09:35 AM, Reindl Harald wrote: >>> Am 02.07.2014 15:19, schrieb Robert Moskowitz: >>>> On 07/02/2014 08:41 AM, Reindl Harald wrote: >>>>> Am 02.07.2014 14:32, schrieb Robert Moskowitz: >>>>>> On 07/01/2014 06:25 PM, Frank Cox wrote: >>>>>>> On Tue, 01 Jul 2014 18:19:32 -0400 >>>>>>> Robert Moskowitz wrote: >>>>>>> >>>>>>>> How do I trouble shoot this? I am assuming that I only got a partially >>>>>>>> completed update. >>>>>>> Try yum-complete-transaction and see what happens. >>>>>> Well it looks like all the updates 'took' /etc/redhat-release now >>>>>> reports ver 6.5. >>>>>> >>>>>> But still getting a kernel panic and boot failing. I can fall back to >>>>>> the prior kernel and it will boot. So I tried to copy the lines off the >>>>>> monitor, as nothing is getting logged: >>>>>> >>>>>> IOMMU: failed to mpa dmn 0 >>>>>> kernel panic - not syncing: VFS: Unable to mount root fs on >>>>>> unknown_block (0,0) >>>>>> Pid:1, comm swapper Tainted: G -------------} 2.6.32-431.20.3.el6.i686 #1 >>>>>> >>>>>> then a a number of dump lines. >>>>>> >>>>>> The kernel that is working (only other one listed in menu) is: >>>>>> 2.6.32-279.22.1.el6.i686 >>>>> why don' t you just remove any package from the new kernel >>>>> which don't work anyways and after that "yum upgrade" again? >>>> But how do I determine what package from the new kernel >>> i said: and after that "yum upgrade" again man if you remove that >>> broken packages a "yum upgrade" pulls them simply as if they where >>> never be installed and the rpmscripts will generate a new initrd >> 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. > 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. So I made sure that all the packages were reinstalled. I did it step by step and did 'yum install' on: kernel-headers glibc-devel irqbalance mod_perl perl-Test-Simple redhat-lsb I then did a reboot and ran down to my NOC in the basement to watch the reboot. I did catch a message on the console about rebuilding initrd, but I don't see a matching message in /var/log/messages. Anyway I am now up and running. Thank you for the help. And Harald, I agree that if the system boots, it should be possible to get through a recovery to the proper point and not have to reinstall. Now remember. No big updates when vnced into the remote system. Use 'screen'. Remember use 'screen'. :-)'