Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: jatan on September 04, 2006, 02:09:42 PM
-
I have a problem that the latest updates (SME 7) did not "finish" successfully.
Basically the system was updated but the new kernel does not show in the boot options. (Causing VPN problems ...)
How can I get the updates to re-install or revert back to the previous setup.
Thanks
-
Login as root.
Try..
yum clean all
yum --enablerepo=smeos --enablerepo=smeupdates --enablerepo=smeaddons update
If it installs anything, do the commands that yum tells you to do.
-
Unfortunately nothing was installed...
Any further help will be appreciated!
Thank you.
[root@fileserver ~]# yum clean all
==============================================================
WARNING: Additional commands may be required after running yum
==============================================================
Cleaning up Everything
66 headers removed
66 packages removed
9 metadata files removed
0 cache files removed
3 cache files removed
================================================================
No new rpms were installed. No additional commands are required.
================================================================
[root@fileserver ~]# yum --enablerepo=smeos --enablerepo=smeupdates --enablerepo =smeaddons update
==============================================================
WARNING: Additional commands may be required after running yum
==============================================================
Setting up Update Process
Setting up repositories
smeaddons 100% |=========================| 951 B 00:00
smeos 100% |=========================| 951 B 00:00
smeupdates 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 157 B 00:00
Added 0 new packages, deleted 0 old in 0.02 seconds
primary.xml.gz 100% |=========================| 254 kB 00:04
smeos : ################################################## 481/481
Added 481 new packages, deleted 0 old in 36.30 seconds
primary.xml.gz 100% |=========================| 51 kB 00:00
smeupdates: ################################################## 77/77
Added 77 new packages, deleted 0 old in 8.09 seconds
No Packages marked for Update/Obsoletion
================================================================
No new rpms were installed. No additional commands are required.
================================================================
-
What does /boot/grub/grub.conf have in it ?
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/main/root
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.9-42.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.2.ELsmp ro root=/dev/main/root
initrd /initrd-2.6.9-42.0.2.ELsmp.img
title CentOS (2.6.9-42.0.2.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.2.EL ro root=/dev/main/root
initrd /initrd-2.6.9-42.0.2.EL.img
title CentOS (2.6.9-34.0.2.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.0.2.EL ro root=/dev/main/root
initrd /initrd-2.6.9-34.0.2.EL.img
title CentOS (2.6.9-34.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.0.2.ELsmp ro root=/dev/main/root
initrd /initrd-2.6.9-34.0.2.ELsmp.img
title SME Server (2.6.9-34.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.ELsmp ro root=/dev/main/root
initrd /initrd-2.6.9-34.ELsmp.img
title SME Server-up (2.6.9-34.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.EL ro root=/dev/main/root
initrd /initrd-2.6.9-34.EL.img
And which kernel are you after ?
-
Thanks for the quick reply!!!
I am after kernel 2.6.9-34.0.2.EL
The "boot menu" only shows options for the 2x 2.6.9-34.EL / ELsmp options.
Even if I edit /boot/grub/grub.conf the "boot menu" stays unchanged ...
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/main/root
# initrd /initrd-version.img
#boot=/dev/hda
default=3
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.9-34.0.2.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.0.2.EL ro root=/dev/main/root
initrd /initrd-2.6.9-34.0.2.EL.img
title CentOS (2.6.9-34.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.0.2.ELsmp ro root=/dev/main/root
initrd /initrd-2.6.9-34.0.2.ELsmp.img
title SME Server (2.6.9-34.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.ELsmp ro root=/dev/main/root
initrd /initrd-2.6.9-34.ELsmp.img
title SME Server-up (2.6.9-34.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.EL ro root=/dev/main/root
initrd /initrd-2.6.9-34.EL.img
-
Change default to 0, save and reboot.
Then do uname -a
to check.
-
Or remove hiddenmenu and press esc at the splash screen.
Helpfull info
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/ref-guide/s1-grub-configfile.html
-
I made the changes suggested.
If I edit /boot/grub/grub.conf and save, it has absolutely no effect on the brub menu at boot.
I have no clue why...
Any further suggestions please.
-
Just for info: I am using software raid, but I assume that should not have any effect ?
-
jatan
Just try
yum update
at the command prompt
-
jatan
Just try
yum update
at the command prompt
Wouldn't yum update
on a stock SME7 be the same as yum --enablerepo=smeos --enablerepo=smeupdates --enablerepo=smeaddons update
?
-
Just for info: I am using software raid, but I assume that should not have any effect ?
Does..
yum list kernel*
show the kernel as installed ?
In /boot do you see about 4 files associated with each kernel ?
Removing hiddenmenu from grub.conf is IMHO your best option and increasing the timeout value.
I just comment out the following..
#default=3
#timeout=5
#splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
and now it sits there waiting for me to select something.
(http://magicwilly.webhostingpal.com/ContribsForumPictures/grub/smegrub.png)
Oh, this is with a test SME7 install as a VM so don't ask about all those kernels. I just wanted something for the screenshot :-D .
-
I did a test and broke the RAID - removed the primary hdd and reboot the machine.
The second hdd came up with the new kernel as a boot option...
If I do this with the primary hdd the new kernel is not in the boot options anymore ... Very strange ...
It seems to be a RAID problem. I have now made the secondary master the primary master and rebuilt the RAID.
I will do some more tests.
Thanks for your input and suggestions, it is much appreciated!
-
I did a test and broke the RAID - removed the primary hdd and reboot the machine.
The second hdd came up with the new kernel as a boot option...
If I do this with the primary hdd the new kernel is not in the boot options anymore ... Very strange ...
It seems to be a RAID problem. I have now made the secondary master the primary master and rebuilt the RAID.
I will do some more tests.
Thanks for your input and suggestions, it is much appreciated!
So grub is a little confused.
grub
grub> root (hd0,0)
grub> setup (hd0)
grub> root (hd1,0)
grub> setup (hd1)
grub> quit
Had to do the above(or something similar) once on another linux distro to get raid working. Don't know what it would do to SME.