I was upgrading a system remotely from Centos 6.3 to 6.5 via VNC. Now the system will not boot. Or at least without bringing up the console and switching to the older kernel. The last messages I see in /var/log/messages are:
Jul 1 14:53:51 rigel yum[3220]: Updated: scl-utils-20120927-8.el6.i686 Jul 1 14:53:53 rigel gnome-keyring-daemon[2710]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:53 rigel gnome-keyring-daemon[2710]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:54 rigel gnome-keyring-daemon[2822]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:54 rigel gnome-keyring-daemon[2822]: dbus failure unregistering from session: Connection is closed
yum update reports 'No Packages marked for Update'.
How do I trouble shoot this? I am assuming that I only got a partially completed update.
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.
And for future reference, always run yum in a screen session when updating a remote system.
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.
And for future reference, always run yum in a screen session when updating a remote system.
Careless of me. I learned about screen session some time ago, but forgot with too much going on. No excuses. Just got to fix this system so I can set it up as a Miredo server.
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.
And for future reference, always run yum in a screen session when updating a remote system.
# yum-complete-transaction Loaded plugins: fastestmirror, refresh-packagekit Loading mirror speeds from cached hostfile * base: lug.mtu.edu * epel: less.cogeco.net * extras: lug.mtu.edu * updates: lug.mtu.edu Checking for new repos for mirrors There are 1 outstanding transactions to complete. Finishing the most recent one The remaining transaction had 458 elements left to run
And something seems to be computing right now....
As it has the CPU pegged at 95%
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
On 07/02/2014 02:32 PM, Robert Moskowitz wrote:
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
That is very old kernel. Try removing new kernel, and then reinstalling it, and if that does not work try removing new kernel and installing one before that, then one before that. Something like "yum install kernel-2.6.32-279.22.1.el6.i686" should do it. List all kernels with "yum list kernel*"
On 07/02/2014 09:10 AM, Ljubomir Ljubojevic wrote:
On 07/02/2014 02:32 PM, Robert Moskowitz wrote:
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
That is very old kernel. Try removing new kernel, and then reinstalling it, and if that does not work try removing new kernel and installing one before that, then one before that. Something like "yum install kernel-2.6.32-279.22.1.el6.i686" should do it. List all kernels with "yum list kernel*"
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
Robert Moskowitz wrote:
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
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:
Robert Moskowitz wrote:
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
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.
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
On 07/02/2014 12:19 AM, Robert Moskowitz wrote:
I was upgrading a system remotely from Centos 6.3 to 6.5 via VNC. Now the system will not boot. Or at least without bringing up the console and switching to the older kernel. The last messages I see in /var/log/messages are:
Jul 1 14:53:51 rigel yum[3220]: Updated: scl-utils-20120927-8.el6.i686 Jul 1 14:53:53 rigel gnome-keyring-daemon[2710]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:53 rigel gnome-keyring-daemon[2710]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:54 rigel gnome-keyring-daemon[2822]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:54 rigel gnome-keyring-daemon[2822]: dbus failure unregistering from session: Connection is closed
yum update reports 'No Packages marked for Update'.
How do I trouble shoot this? I am assuming that I only got a partially completed update.
You can do "yum history list" to see the number of the last command, lets say it was 234, and then you can use "yum history info 234 to list all changed packages. "yum history undo 234 would revert the system to previous state, and then you can do "yum update" again. "yum history repeat 234" might help you as well.
I think you have enough info to chose how you want to proceed.
On 07/01/2014 06:42 PM, Ljubomir Ljubojevic wrote:
On 07/02/2014 12:19 AM, Robert Moskowitz wrote:
I was upgrading a system remotely from Centos 6.3 to 6.5 via VNC. Now the system will not boot. Or at least without bringing up the console and switching to the older kernel. The last messages I see in /var/log/messages are:
Jul 1 14:53:51 rigel yum[3220]: Updated: scl-utils-20120927-8.el6.i686 Jul 1 14:53:53 rigel gnome-keyring-daemon[2710]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:53 rigel gnome-keyring-daemon[2710]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:54 rigel gnome-keyring-daemon[2822]: dbus failure unregistering from session: Connection is closed Jul 1 14:53:54 rigel gnome-keyring-daemon[2822]: dbus failure unregistering from session: Connection is closed
yum update reports 'No Packages marked for Update'.
How do I trouble shoot this? I am assuming that I only got a partially completed update.
You can do "yum history list" to see the number of the last command, lets say it was 234, and then you can use "yum history info 234 to list all changed packages. "yum history undo 234 would revert the system to previous state, and then you can do "yum update" again. "yum history repeat 234" might help you as well.
I think you have enough info to chose how you want to proceed.
thanks for both recommendations.
On Wed, 2014-07-02 at 00:42 +0200, Ljubomir Ljubojevic wrote:
You can do "yum history list" to see the number of the last command,
Nice advice :-) but does not work for C 5.10
http://www.if-not-true-then-false.com/2010/yum-history-list-info-summary-rep...
states "commands is added on 3.2.25 version."
C 5.10 yum = 3.2.22
It works on C 6.5
On 07/02/2014 03:55 AM, Always Learning wrote:
On Wed, 2014-07-02 at 00:42 +0200, Ljubomir Ljubojevic wrote:
You can do "yum history list" to see the number of the last command,
Nice advice :-) but does not work for C 5.10
http://www.if-not-true-then-false.com/2010/yum-history-list-info-summary-rep...
states "commands is added on 3.2.25 version."
C 5.10 yum = 3.2.22
It works on C 6.5
On 07/02/2014 12:19 AM, Robert Moskowitz wrote:
I was upgrading a system remotely from Centos 6.3 to 6.5 via VNC. Now
So since Robert has 6.x version, all is good ;)
-
Always Learning -
Frank Cox -
Ljubomir Ljubojevic -
m.roth＠5-cent.us -
Robert Moskowitz