Page 1 of 1

Migrated from Mandriva with bizarre result

PostPosted: Aug 24th, '12, 19:10
by Will94
I provide technical support for an academic department at a large university. We have four high-end workstations that our faculty and graduate students use to crunch large data sets. These machines are heavily used, so I typically wait until an OS is no longer receiving updates to upgrade it.

This morning I upgraded the machines from Mandriva Linux 2010 to Mageia 1 using the following commands from this document. I have done this numerous times, and it has always gone smoothly.

Migrate from Mandriva Linux to Mageia
http://www.mageia.org/en/1/migrate/

$ su
# urpmi.removemedia -a
# urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.1.x86_64.list'
# urpmi --replacefiles --auto-update --auto


The results were as expected on three of the machines. However, the other machine still has the kernel that Mandriva was using. Other than that, it seems to be working perfectly. I would appreciate any ideas on how this might have happened and how I might correct it. I am using the same repositories on this machine as the other three. I've tried both urpmi and the MCC GUI. Both tell me that I am up to date.


Thank you,

Will N.
Bryan, TX USA

Image

Re: Migrated from Mandriva with birarre result

PostPosted: Aug 25th, '12, 00:49
by tom_
please post the output of

Code: Select all
rpm -qa | grep kernel

Re: Migrated from Mandriva with bizarre result

PostPosted: Aug 28th, '12, 22:05
by Will94
Code: Select all
econ-ptsafe01# 1: [b]rpm -qa | grep kernel[/b]
kernel-server-2.6.38.8-10.mga-1-1.mga1
kernel-server-2.6.33.7-2mnb-1-1mnb2
kernel-server-latest-2.6.38.8-10.mga1
kernel-firmware-20110314-2.mga1


--------------------------------------------------------
Very interesting
If only I could boot to it ...

~edited by moderator, please code-tag terminal output for better readability ;)

Re: Migrated from Mandriva with bizarre result

PostPosted: Aug 29th, '12, 10:25
by tom_
Will94 wrote: I would appreciate any ideas on how this might have happened...


probably in your case some scritpt failed in understanding what it the newest kernel,
so the default kernel is still an old one

Will94 wrote:...and how I might correct it

open a teminal as root and edit the file
Code: Select all
/boot/grub/menu.lst


in that file there is an header

timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 0


and 3 lines lines for each installed kernel,

title ....
kernel ....
initrd ...

the default kernel is the first on the list.

you should put the 3 lines related to the kernel you want to boot at the top of the list,
after the header; then save the file and reboot.