Topic: Trying to go to 7.3 - Having an issue

[grattman]

Hey all,

I am having a small  problem when I try and upgrade to 7.3. Everything seems to download fine and then the Transaction check runs and the updates report:

"some update" needs 5MB on the /boot filesystem - or some other amount of space.

A look at the drive reports (d)
Filesystem                       1K-blocks      Used          Available     Use%   Mounted on
/dev/mapper/main-root      138980344    14891868    117028612  12%     /
/dev/md1                        101018         93268         2534          98%     /boot
none                              4116532        0               4116532     0%      /dev/shm

Sure enough I look into /boot and find this:

-rw-r--r--  1 root root   49517 Jul  7  2006 config-2.6.9-34.0.2.EL
-rw-r--r--  1 root root   49268 Jul  7  2006 config-2.6.9-34.0.2.ELsmp
-rw-r--r--  1 root root   49513 Mar  8  2006 config-2.6.9-34.EL
-rw-r--r--  1 root root   49264 Mar  8  2006 config-2.6.9-34.ELsmp
-rw-r--r--  1 root root   50338 Feb 27  2007 config-2.6.9-42.0.10.EL
-rw-r--r--  1 root root   49931 Feb 27  2007 config-2.6.9-42.0.10.ELsmp
-rw-r--r--  1 root root   50337 Aug 23  2006 config-2.6.9-42.0.2.EL
-rw-r--r--  1 root root   49930 Aug 23  2006 config-2.6.9-42.0.2.ELsmp
-rw-r--r--  1 root root   50337 Oct  6  2006 config-2.6.9-42.0.3.EL
-rw-r--r--  1 root root   49879 Oct  6  2006 config-2.6.9-42.0.3.ELhugemem
-rw-r--r--  1 root root   49930 Oct  6  2006 config-2.6.9-42.0.3.ELsmp
-rw-r--r--  1 root root   50337 Jan 30  2007 config-2.6.9-42.0.8.EL
-rw-r--r--  1 root root   49930 Jan 30  2007 config-2.6.9-42.0.8.ELsmp
-rw-r--r--  1 root root   50433 Nov  2 11:12 config-2.6.9-55.0.12.EL
-rw-r--r--  1 root root   50007 Nov  2 11:57 config-2.6.9-55.0.12.ELhugemem
-rw-r--r--  1 root root   50058 Nov  2 11:31 config-2.6.9-55.0.12.ELsmp
-rw-r--r--  1 root root   50432 Jun 26  2007 config-2.6.9-55.0.2.EL
-rw-r--r--  1 root root   50006 Jun 26  2007 config-2.6.9-55.0.2.ELhugemem
-rw-r--r--  1 root root   50057 Jun 26  2007 config-2.6.9-55.0.2.ELsmp
-rw-r--r--  1 root root   50432 Sep  4 21:29 config-2.6.9-55.0.6.EL
-rw-r--r--  1 root root   50006 Sep  4 22:25 config-2.6.9-55.0.6.ELhugemem
-rw-r--r--  1 root root   50057 Sep  4 21:57 config-2.6.9-55.0.6.ELsmp
-rw-r--r--  1 root root   50432 Sep 27 18:23 config-2.6.9-55.0.9.EL
-rw-r--r--  1 root root   50006 Sep 27 18:52 config-2.6.9-55.0.9.ELhugemem
-rw-r--r--  1 root root   50057 Sep 27 18:36 config-2.6.9-55.0.9.ELsmp
drwxr-xr-x  2 root root    1024 Jan 18 11:54 grub
-rw-r--r--  1 root root 1147295 Aug 20  2006 initrd-2.6.9-34.0.2.EL.img
-rw-r--r--  1 root root 1133690 Aug 20  2006 initrd-2.6.9-34.0.2.ELsmp.img
-rw-r--r--  1 root root 1147260 Jul 21  2006 initrd-2.6.9-34.EL.img
-rw-r--r--  1 root root 1133557 Jul 21  2006 initrd-2.6.9-34.ELsmp.img
-rw-r--r--  1 root root 1207866 Mar  6  2007 initrd-2.6.9-42.0.10.EL.img
-rw-r--r--  1 root root 1193187 Mar  6  2007 initrd-2.6.9-42.0.10.ELsmp.img
-rw-r--r--  1 root root 1173949 Nov  7  2006 initrd-2.6.9-42.0.2.EL.img
-rw-r--r--  1 root root 1157983 Nov  7  2006 initrd-2.6.9-42.0.2.ELsmp.img
-rw-r--r--  1 root root 1156519 Jan  6  2007 initrd-2.6.9-42.0.3.ELhugemem.img
-rw-r--r--  1 root root 1173966 Jan  6  2007 initrd-2.6.9-42.0.3.EL.img
-rw-r--r--  1 root root 1157976 Jan  6  2007 initrd-2.6.9-42.0.3.ELsmp.img
-rw-r--r--  1 root root 1207866 Mar  1  2007 initrd-2.6.9-42.0.8.EL.img
-rw-r--r--  1 root root 1193225 Mar  1  2007 initrd-2.6.9-42.0.8.ELsmp.img
-rw-r--r--  1 root root 1398009 Nov 26 22:18 initrd-2.6.9-55.0.12.ELhugemem.img
-rw-r--r--  1 root root 1416326 Nov 26 22:17 initrd-2.6.9-55.0.12.EL.img
-rw-r--r--  1 root root 1397584 Nov 26 22:17 initrd-2.6.9-55.0.12.ELsmp.img
-rw-r--r--  1 root root 1398007 Jul 24 19:09 initrd-2.6.9-55.0.2.ELhugemem.img
-rw-r--r--  1 root root 1416311 Jul 24 19:09 initrd-2.6.9-55.0.2.EL.img
-rw-r--r--  1 root root 1397578 Jul 24 19:09 initrd-2.6.9-55.0.2.ELsmp.img
-rw-r--r--  1 root root 1398006 Sep 15 14:47 initrd-2.6.9-55.0.6.ELhugemem.img
-rw-r--r--  1 root root 1416312 Sep 15 14:47 initrd-2.6.9-55.0.6.EL.img
-rw-r--r--  1 root root 1397582 Sep 15 14:47 initrd-2.6.9-55.0.6.ELsmp.img
-rw-r--r--  1 root root 1398119 Sep 29 07:26 initrd-2.6.9-55.0.9.ELhugemem.img
-rw-r--r--  1 root root 1416323 Sep 29 07:26 initrd-2.6.9-55.0.9.EL.img
-rw-r--r--  1 root root 1397585 Sep 29 07:26 initrd-2.6.9-55.0.9.ELsmp.img
drwx------  2 root root   12288 Jul 21  2006 lost+found
-rw-r--r--  1 root root  733742 Jul  7  2006 System.map-2.6.9-34.0.2.EL
-rw-r--r--  1 root root  761137 Jul  7  2006 System.map-2.6.9-34.0.2.ELsmp
-rw-r--r--  1 root root  733742 Mar  8  2006 System.map-2.6.9-34.EL
-rw-r--r--  1 root root  761137 Mar  8  2006 System.map-2.6.9-34.ELsmp
-rw-r--r--  1 root root  750652 Feb 27  2007 System.map-2.6.9-42.0.10.EL
-rw-r--r--  1 root root  767450 Feb 27  2007 System.map-2.6.9-42.0.10.ELsmp
-rw-r--r--  1 root root  749489 Aug 23  2006 System.map-2.6.9-42.0.2.EL
-rw-r--r--  1 root root  766287 Aug 23  2006 System.map-2.6.9-42.0.2.ELsmp
-rw-r--r--  1 root root  749489 Oct  6  2006 System.map-2.6.9-42.0.3.EL
-rw-r--r--  1 root root  766086 Oct  6  2006 System.map-2.6.9-42.0.3.ELhugemem
-rw-r--r--  1 root root  766287 Oct  6  2006 System.map-2.6.9-42.0.3.ELsmp
-rw-r--r--  1 root root  750652 Jan 30  2007 System.map-2.6.9-42.0.8.EL
-rw-r--r--  1 root root  767450 Jan 30  2007 System.map-2.6.9-42.0.8.ELsmp
-rw-r--r--  1 root root  754717 Nov  2 11:12 System.map-2.6.9-55.0.12.EL
-rw-r--r--  1 root root  771385 Nov  2 11:57 System.map-2.6.9-55.0.12.ELhugemem
-rw-r--r--  1 root root  771586 Nov  2 11:31 System.map-2.6.9-55.0.12.ELsmp
-rw-r--r--  1 root root  754505 Jun 26  2007 System.map-2.6.9-55.0.2.EL
-rw-r--r--  1 root root  771173 Jun 26  2007 System.map-2.6.9-55.0.2.ELhugemem
-rw-r--r--  1 root root  771374 Jun 26  2007 System.map-2.6.9-55.0.2.ELsmp
-rw-r--r--  1 root root  754717 Sep  4 21:29 System.map-2.6.9-55.0.6.EL
-rw-r--r--  1 root root  771385 Sep  4 22:25 System.map-2.6.9-55.0.6.ELhugemem
-rw-r--r--  1 root root  771586 Sep  4 21:57 System.map-2.6.9-55.0.6.ELsmp
-rw-r--r--  1 root root  754717 Sep 27 18:23 System.map-2.6.9-55.0.9.EL
-rw-r--r--  1 root root  771385 Sep 27 18:52 System.map-2.6.9-55.0.9.ELhugemem
-rw-r--r--  1 root root  771586 Sep 27 18:36 System.map-2.6.9-55.0.9.ELsmp
-rw-r--r--  1 root root 1473712 Jul  7  2006 vmlinuz-2.6.9-34.0.2.EL
-rw-r--r--  1 root root 1436516 Jul  7  2006 vmlinuz-2.6.9-34.0.2.ELsmp
-rw-r--r--  1 root root 1473787 Mar  8  2006 vmlinuz-2.6.9-34.EL
-rw-r--r--  1 root root 1436129 Mar  8  2006 vmlinuz-2.6.9-34.ELsmp
-rw-r--r--  1 root root 1504585 Feb 27  2007 vmlinuz-2.6.9-42.0.10.EL
-rw-r--r--  1 root root 1444718 Feb 27  2007 vmlinuz-2.6.9-42.0.10.ELsmp
-rw-r--r--  1 root root 1504411 Aug 23  2006 vmlinuz-2.6.9-42.0.2.EL
-rw-r--r--  1 root root 1444563 Aug 23  2006 vmlinuz-2.6.9-42.0.2.ELsmp
-rw-r--r--  1 root root 1504397 Oct  6  2006 vmlinuz-2.6.9-42.0.3.EL
-rw-r--r--  1 root root 1425897 Oct  6  2006 vmlinuz-2.6.9-42.0.3.ELhugemem
-rw-r--r--  1 root root 1444549 Oct  6  2006 vmlinuz-2.6.9-42.0.3.ELsmp
-rw-r--r--  1 root root 1504589 Jan 30  2007 vmlinuz-2.6.9-42.0.8.EL
-rw-r--r--  1 root root 1444726 Jan 30  2007 vmlinuz-2.6.9-42.0.8.ELsmp
-rw-r--r--  1 root root 1511559 Nov  2 11:12 vmlinuz-2.6.9-55.0.12.EL
-rw-r--r--  1 root root 1430427 Nov  2 11:57 vmlinuz-2.6.9-55.0.12.ELhugemem
-rw-r--r--  1 root root 1451171 Nov  2 11:31 vmlinuz-2.6.9-55.0.12.ELsmp
-rw-r--r--  1 root root 1511833 Jun 26  2007 vmlinuz-2.6.9-55.0.2.EL
-rw-r--r--  1 root root 1429995 Jun 26  2007 vmlinuz-2.6.9-55.0.2.ELhugemem
-rw-r--r--  1 root root 1450563 Jun 26  2007 vmlinuz-2.6.9-55.0.2.ELsmp
-rw-r--r--  1 root root 1511604 Sep  4 21:29 vmlinuz-2.6.9-55.0.6.EL
-rw-r--r--  1 root root 1430332 Sep  4 22:25 vmlinuz-2.6.9-55.0.6.ELhugemem
-rw-r--r--  1 root root 1450984 Sep  4 21:57 vmlinuz-2.6.9-55.0.6.ELsmp
-rw-r--r--  1 root root 1511602 Sep 27 18:23 vmlinuz-2.6.9-55.0.9.EL
-rw-r--r--  1 root root 1430284 Sep 27 18:52 vmlinuz-2.6.9-55.0.9.ELhugemem
-rw-r--r--  1 root root 1451003 Sep 27 18:36 vmlinuz-2.6.9-55.0.9.ELsmp

So my question is...Can I get rid of most or all of that (Iwith the exception of the grub and lost+found directories)? Is it supposed to be there? If not, is there a "house-keeping" aspect of SME that is not working on my machine?

Thanks in advance,
grattman

[stiperstones]

Hi grattman
Search is your friend but i have saved you the problem this will assist you with your problem
http://forums.contribs.org/index.php?topic=39155.msg178781#msg178781

[byte]

Please also make a note that you ran in to the issue on bug:

http://bugs.contribs.org/show_bug.cgi?id=2101

Thanks.

[grattman]

Will do and I tried several searches, but thought putting the actual error in would be too obscure. I was wrong 

Thanks,
grattman

[grattman]

Okay...so I got a bit carried away removing old files....it seems I got rid of vmlinuz-2.6.9-67.0.1.EL and vmlinuz-2.6.9-67.0.1.ELsmp.

I have copied the missing files from an upgraded server over to a USB Key. Now I am trying to figure out how to map the key from the command line (since I cannot boot) and install those files back.

While I am purusing the forums for the answer, if anyone has it readily available, it would be greatly appreciated.

Thanks,
grattman

[william_syd]

Okay...so I got a bit carried away removing old files....it seems I got rid of vmlinuz-2.6.9-67.0.1.EL and vmlinuz-2.6.9-67.0.1.ELsmp.

I have copied the missing files from an upgraded server over to a USB Key. Now I am trying to figure out how to map the key from the command line (since I cannot boot) and install those files back.

While I am purusing the forums for the answer, if anyone has it readily available, it would be greatly appreciated.

Thanks,
grattman

Wild guess...

Boot from the SME CD and select rescue mode?

[raem]

grattman

For the benefit of others who read this, the correct approch is to uninstall the unwanted kernels

df -h
Look at the unused space in /boot

rpm -qa kernel*
To show you all the kernels currently installed

uname -r
Make a note of the currently used kernel

Then uninstall the unwanted kernels making sure not to remove the current used kernel (as noted above)
Do rpm -e kernel.xxx kernel-smp.xxx for all the listed kernels except the currently used one
eg
rpm -e kernel-2.6.9-34.EL kernel-smp-2.6.9-34.EL
rpm -e kernel-2.6.9-34.0.2.EL kernel-smp-2.6.9-34.0.2.EL
rpm -e kernel-2.6.9-42.0.2.EL kernel-smp-2.6.9-42.0.2.EL
rpm -e kernel-2.6.9-42.0.3.EL kernel-smp-2.6.9-42.0.3.EL
rpm -e kernel-2.6.9-42.0.8.EL kernel-smp-2.6.9-42.0.8.EL
rpm -e kernel-2.6.9-42.0.10.EL kernel-smp-2.6.9-42.0.10.EL
rpm -e kernel-2.6.9-55.0.2.EL kernel-smp-2.6.9-55.0.2.EL
rpm -e kernel-2.6.9-55.0.6.EL kernel-smp-2.6.9-55.0.6.EL
rpm -e kernel-2.6.9-55.0.9.EL kernel-smp-2.6.9-55.0.9.EL
rpm -e kernel-2.6.9-55.0.12.EL kernel-smp-2.6.9-55.0.12.EL
signal-event post-upgrade
reboot

[grattman]

Ray -Duly noted. I won't do this again!

William, I have used the CD and gone into rescue, although I am a bit perplexed how to restore the files.

I choose the recue (locates installation) and then mounts to /mnt/sysimage

I select "OK" type in chroot /mnt/sysimage as instructed, reboot and still loads /dev/main/root instead of /mnt/sysimage

Before rebooting, I type mount and it tells me /dev/main/root/ on /mnt/sysimage/

When I reboot it defaults to the broken /dev/main/root without the kernel

I have read as many posts on this subject as I can, but am not enirely clear how to rectify the problem. The closest thing I could find was this:

http://forums.contribs.org/index.php?topic=36123.msg159556#msg159556

Grub is not broken though, so I have not attempted this. I just don't want to make the problem any worse by not knowing what the correct steps are.

What am I doing wrong?

[raem]

grattman

You could boot from the CD and do a upgrade install.

[grattman]

How much of my existing set up will I lose? I have backups, but not a system backup perse.

I din't think it would be that hard to boot - mount a usb drive and copy the files over.

Am I wrong in my understanding of this?

[raem]

grattman

If the system lets you do an upgrade (rather than a fresh install), then it should preserve all your existing configuration & data, and hopefully will replace the "missing bits".

[grattman]

Okay...I think I am getting closer. I have not done an upgrade because I only have 7.1 disk while the server was at 7.2. I am downloading a 7.3 now.

In the meantime, I noticed that the /boot/grub/grub.conf was set to default=2 as well as the list didn't contain the lastest kernels 2.6.9-67.0.1. I amended the grub.conf to reflect the correct settings (default=0 and the correct kernel version).

However, at some point it seems my grub got lost, so now when I booty I get grub>. I am in the process of loading up rescue mode again to be able to get to the command prompt to do a grub-install.

UPDATE 2

Nope...didn't work, reboot just goes to grub> everytime. I am not sure where to go from here. The files are intact under /boot, but I cannot get grub to reference /boot.

In grub "root" returns - (hd0,0): Filesystem type is ext2fs, partition type 0xfd

Then trying to load the kernel: grub> kernel /vmlinuz root=/dev/md1 results in file not found

Ugggggg

UPDATE 3

Just got done doing an upgrade with 7.3 disc, crossing fingers..............

UPDATE 4

OMFG...still grub> only

I am done with SME

[raem]

grattman

I am done with SME

Don't blame sme, it was all your own "wrong" doing !

If you cannot fix it, then you do a reinstall of the OS and restore from backups.

[william_syd]

--snip--

UPDATE 4

OMFG...still grub> only

I am done with SME

What have you done...?

Just for the 'thril' of it, I installed SME 7.1 in a VM.

I then deleted everything in /boot except the grub amd 'lost and found' folders.

I then rebooted. It spat the dummy missing 'stuff' and threw me into a grub screen asking me to select a different kernel.

I then booted with a 7.3 iso into rescue mode. Entered network details for a static IP and away it went.

At the prompt, type chroot /mnt/sysimage followed by cd /root. Ah... home sweet home.

I'm sure the kernel rpms are on the disk but what the heck.... lets get a fresh one.

wget http://mirror.pacific.net.au/linux/smeserver/releases/7/smeos/i386/SME/RPMS/kernel-2.6.9-67.0.1.EL.i686.rpm

Bummer, temp DNS error. No problem

wget http://61.8.0.17/linux/smeserver/releases/7/smeos/i386/SME/RPMS/kernel-2.6.9-67.0.1.EL.i686.rpm

Down it came, followed by

yum localinstall kernel-2.6.9-67.0.1.EL.i686.rpm

then exit exit.

Bummer, still wants the -42 kernel. No problem. Follow the prompts at the grub screen to edit two lines.

b to boot....

Yey.... I'm in.

Just have to now tidy up the /boot/grub/grub.conf file.

[grattman]

Ray - I admit whole-heartedly, it was my wrong doing. And the last remark (I am done with SME), had "for the night" before I hit submit, but it didn't post.

Yes I was frustrated because not all of us using SME are linux gurus like many of you. I have been using it for over four years now and have loved it. But sometimes us newbs make a mistake or enounter a problem that is beyond our knowledge. That is when we turn to these forums for the nuggets of wisdom that many of you hold. It's kind of like your car, you can work on some of the things, but not all of them, that is when you would bring it to the mechanic (expert).

William - That is exactly what I was looking for, but I could not find what exactly I was to do in the rescue mode. And using the posts on these forums (some of them probably not a good idea) proceeded to fubar grub and further complicate my problem. Your post clearly explains to me what I was supposed to do. I did try and ftp to another server and get the rpms, but by that point, I had screwed grub up so I could not edit it. I am still curious why I was unable to enter kernel and such (in the grub> command line) and get the machine back up. Always ended up in "file not found."

Suggestion to the team or moderators: It would be really helpful to people like me to have "peer-reviewed" posts that have a "wink-thumbs-up" approval from knowledgable people such as yourselfs. Frankly there is some not so good information in the forums that can cause a novice like me to further destroy their implementation of SME.

Again, I DO LOVE SME and I really do appreciate your posts. Back to work to give it another shot.

[william_syd]

Maybe the solution in this post may help.

solution

I ran through it on my test box and it didn't hurt it (using sme rescue).

Note: there is only one drive in my test box and,

find /boot/grub/stage1 didn't work but find /grub/stage1 did.

I am done with SME for the night.

[grattman]

William,

I tried what you gave as advice. when I try that it says that it is installed and there is nothing to update. So it would seem that the issue now lay in grub.

When I go into rescue and try to configure grub I must be missing something. If grub were completely wiped (as seems is my case), how would one reconfigure/re-install it? I have tried many different things, but to no avail.

I have a duplicate machine at another location (regarding hardware and SME 7.3). I am comparing the two:

The broken server has much more memory, so it should be using the ELhugemem

menu.lst output:

Good Machine
#          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/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/smeserver.xpm.gz
foreground 000000
background 4E95D3
hiddenmenu
title SME Server (2.6.9-67.0.1.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.1.ELsmp ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.1.ELsmp.img
title SME Server (2.6.9-67.0.1.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.1.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.1.EL.img
title SME Server (2.6.9-55.0.12.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-55.0.12.ELsmp ro root=/dev/main/root
        initrd /initrd-2.6.9-55.0.12.ELsmp.img

Bad Machine
less /boot/grub/grub.conf
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/main/root
#          initrd /initrd-version.img
#boot=/dev/sda
default=2
timeout=5
splashimage=(hd0,0)/grub/smeserver.xpm.gz
foreground 000000
background 4E95D3
hiddenmenu
title SME Server (2.6.9-67.0.1.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.1.ELhugemem ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.1.ELhugemem.img
title SME Server (2.6.9-67.0.1.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.1.ELsmp ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.1.ELsmp.img
title SME Server (2.6.9-67.0.12.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.1.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.1.EL.img

MTAB

Good Machine
/dev/mapper/main-root / ext3 rw,usrquota,grpquota 0 0
none /proc proc rw 0 0
none /sys sysfs rw 0 0
none /dev/pts devpts rw,gid=5,mode=620 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/md1 /boot ext3 rw 0 0
none /dev/shm tmpfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0

Bad Machine
/dev/main/root / ext3 rw,usrquota,grpquota 0 0
/dev/md1 /boot ext3 rw 0 0
none /proc proc rw 0 0
none /sys sysfs rw 0 0


FSTAB

Good Machine
#------------------------------------------------------------
# BE CAREFUL WHEN MODIFYING THIS FILE! It is updated automatically
# by the SME server software. A few entries are updated during
# the template processing of the file and white space is removed,
# but otherwise changes to the file are preserved.
# For more information, see http://www.e-smith.org/custom/ and
# the template fragments in /etc/e-smith/templates/etc/fstab/.
#
# copyright (C) 2002 Mitel Networks Corporation
#------------------------------------------------------------
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/main/root          /                       ext3    usrquota,grpquota        1 1
/dev/md1                /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/main/swap          swap                    swap    defaults        0 0
/dev/hdc                /media/cdrom            auto    pamconsole,exec,noauto,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,exec,noauto,managed 0 0

Bad Machine
#------------------------------------------------------------
# BE CAREFUL WHEN MODIFYING THIS FILE! It is updated automatically
# by the SME server software. A few entries are updated during
# the template processing of the file and white space is removed,
# but otherwise changes to the file are preserved.
# For more information, see http://www.e-smith.org/custom/ and
# the template fragments in /etc/e-smith/templates/etc/fstab/.
#
# copyright (C) 2002 Mitel Networks Corporation
#------------------------------------------------------------
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/main/root          /                       ext3    usrquota,grpquota        1 1
/dev/md1                /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/main/swap          swap                    swap    defaults        0 0
/dev/hdc                /media/cdrom            auto    pamconsole,exec,noauto,managed 0 0
/dev/fd0                /media/floppy           auto    pamconsole,exec,noauto,managed 0 0


Contents of /boot

Good Machine
-rw-r--r--  1 root root    49517 Jul  7  2006 config-2.6.9-34.0.2.EL
-rw-r--r--  1 root root    49268 Jul  7  2006 config-2.6.9-34.0.2.ELsmp
-rw-r--r--  1 root root    49513 Mar  8  2006 config-2.6.9-34.EL
-rw-r--r--  1 root root    49264 Mar  8  2006 config-2.6.9-34.ELsmp
-rw-r--r--  1 root root    50338 Feb 27  2007 config-2.6.9-42.0.10.EL
-rw-r--r--  1 root root    49931 Feb 27  2007 config-2.6.9-42.0.10.ELsmp
-rw-r--r--  1 root root    50337 Aug 23  2006 config-2.6.9-42.0.2.EL
-rw-r--r--  1 root root    49930 Aug 23  2006 config-2.6.9-42.0.2.ELsmp
-rw-r--r--  1 root root    50337 Oct  6  2006 config-2.6.9-42.0.3.EL
-rw-r--r--  1 root root    49930 Oct  6  2006 config-2.6.9-42.0.3.ELsmp
-rw-r--r--  1 root root    50337 Jan 30  2007 config-2.6.9-42.0.8.EL
-rw-r--r--  1 root root    49930 Jan 30  2007 config-2.6.9-42.0.8.ELsmp
-rw-r--r--  1 root root    50433 Nov  2 11:12 config-2.6.9-55.0.12.EL
-rw-r--r--  1 root root    50058 Nov  2 11:31 config-2.6.9-55.0.12.ELsmp
-rw-r--r--  1 root root    50432 Jun 26  2007 config-2.6.9-55.0.2.EL
-rw-r--r--  1 root root    50057 Jun 26  2007 config-2.6.9-55.0.2.ELsmp
-rw-r--r--  1 root root    50432 Sep  4 21:29 config-2.6.9-55.0.6.EL
-rw-r--r--  1 root root    50057 Sep  4 21:57 config-2.6.9-55.0.6.ELsmp
-rw-r--r--  1 root root    50432 Sep 27 18:23 config-2.6.9-55.0.9.EL
-rw-r--r--  1 root root    50057 Sep 27 18:36 config-2.6.9-55.0.9.ELsmp
-rw-r--r--  1 root root    50924 Dec 19 15:58 config-2.6.9-67.0.1.EL
-rw-r--r--  1 root root    50549 Dec 19 16:12 config-2.6.9-67.0.1.ELsmp
drwxr-xr-x  2 root root     1024 Jan 18 17:09 grub
-rw-r--r--  1 root root  1146334 Oct 17  2006 initrd-2.6.9-34.0.2.EL.img
-rw-r--r--  1 root root  1131312 Oct 17  2006 initrd-2.6.9-34.0.2.ELsmp.img
-rw-r--r--  1 root root  1146291 Oct 17  2006 initrd-2.6.9-34.EL.img
-rw-r--r--  1 root root  1131267 Oct 17  2006 initrd-2.6.9-34.ELsmp.img
-rw-r--r--  1 root root  1207493 Mar  1  2007 initrd-2.6.9-42.0.10.EL.img
-rw-r--r--  1 root root  1192157 Mar  1  2007 initrd-2.6.9-42.0.10.ELsmp.img
-rw-r--r--  1 root root  1172380 Nov  7  2006 initrd-2.6.9-42.0.2.EL.img
-rw-r--r--  1 root root  1156992 Nov  7  2006 initrd-2.6.9-42.0.2.ELsmp.img
-rw-r--r--  1 root root  1207502 Jan  3  2007 initrd-2.6.9-42.0.3.EL.img
-rw-r--r--  1 root root  1192042 Jan  3  2007 initrd-2.6.9-42.0.3.ELsmp.img
-rw-rw-rw-  1 root admin 1207524 Feb 21  2007 initrd-2.6.9-42.0.8.EL.img
-rw-rw-rw-  1 root admin 1192205 Feb 21  2007 initrd-2.6.9-42.0.8.ELsmp.img
-rw-r--r--  1 root root  1414262 Nov  4 09:49 initrd-2.6.9-55.0.12.EL.img
-rw-r--r--  1 root root  1397939 Nov  4 09:49 initrd-2.6.9-55.0.12.ELsmp.img
-rw-r--r--  1 root root  1414300 Jul 22 11:53 initrd-2.6.9-55.0.2.EL.img
-rw-r--r--  1 root root  1397836 Jul 22 11:52 initrd-2.6.9-55.0.2.ELsmp.img
-rw-r--r--  1 root root  1414313 Sep 14 23:58 initrd-2.6.9-55.0.6.EL.img
-rw-r--r--  1 root root  1397945 Sep 14 23:58 initrd-2.6.9-55.0.6.ELsmp.img
-rw-r--r--  1 root root  1414307 Sep 28 23:43 initrd-2.6.9-55.0.9.EL.img
-rw-r--r--  1 root root  1397954 Sep 28 23:43 initrd-2.6.9-55.0.9.ELsmp.img
-rw-r--r--  1 root root  1351038 Jan 12 06:16 initrd-2.6.9-67.0.1.EL.img
-rw-r--r--  1 root root  1334474 Jan 12 06:16 initrd-2.6.9-67.0.1.ELsmp.img
drwx------  2 root root    12288 Oct 17  2006 lost+found
-rw-r--r--  1 root root    64308 Dec 19 15:58 symvers-2.6.9-67.0.1.EL.gz
-rw-r--r--  1 root root    65129 Dec 19 16:12 symvers-2.6.9-67.0.1.ELsmp.gz
-rw-r--r--  1 root root   733742 Jul  7  2006 System.map-2.6.9-34.0.2.EL
-rw-r--r--  1 root root   761137 Jul  7  2006 System.map-2.6.9-34.0.2.ELsmp
-rw-r--r--  1 root root   733742 Mar  8  2006 System.map-2.6.9-34.EL
-rw-r--r--  1 root root   761137 Mar  8  2006 System.map-2.6.9-34.ELsmp
-rw-r--r--  1 root root   750652 Feb 27  2007 System.map-2.6.9-42.0.10.EL
-rw-r--r--  1 root root   767450 Feb 27  2007 System.map-2.6.9-42.0.10.ELsmp
-rw-r--r--  1 root root   749489 Aug 23  2006 System.map-2.6.9-42.0.2.EL
-rw-r--r--  1 root root   766287 Aug 23  2006 System.map-2.6.9-42.0.2.ELsmp
-rw-r--r--  1 root root   749489 Oct  6  2006 System.map-2.6.9-42.0.3.EL
-rw-r--r--  1 root root   766287 Oct  6  2006 System.map-2.6.9-42.0.3.ELsmp
-rw-r--r--  1 root root   750652 Jan 30  2007 System.map-2.6.9-42.0.8.EL
-rw-r--r--  1 root root   767450 Jan 30  2007 System.map-2.6.9-42.0.8.ELsmp
-rw-r--r--  1 root root   754717 Nov  2 11:12 System.map-2.6.9-55.0.12.EL
-rw-r--r--  1 root root   771586 Nov  2 11:31 System.map-2.6.9-55.0.12.ELsmp
-rw-r--r--  1 root root   754505 Jun 26  2007 System.map-2.6.9-55.0.2.EL
-rw-r--r--  1 root root   771374 Jun 26  2007 System.map-2.6.9-55.0.2.ELsmp
-rw-r--r--  1 root root   754717 Sep  4 21:29 System.map-2.6.9-55.0.6.EL
-rw-r--r--  1 root root   771586 Sep  4 21:57 System.map-2.6.9-55.0.6.ELsmp
-rw-r--r--  1 root root   754717 Sep 27 18:23 System.map-2.6.9-55.0.9.EL
-rw-r--r--  1 root root   771586 Sep 27 18:36 System.map-2.6.9-55.0.9.ELsmp
-rw-r--r--  1 root root   759989 Dec 19 15:58 System.map-2.6.9-67.0.1.EL
-rw-r--r--  1 root root   776963 Dec 19 16:12 System.map-2.6.9-67.0.1.ELsmp
-rw-r--r--  1 root root  1473712 Jul  7  2006 vmlinuz-2.6.9-34.0.2.EL
-rw-r--r--  1 root root  1436516 Jul  7  2006 vmlinuz-2.6.9-34.0.2.ELsmp
-rw-r--r--  1 root root  1473787 Mar  8  2006 vmlinuz-2.6.9-34.EL
-rw-r--r--  1 root root  1436129 Mar  8  2006 vmlinuz-2.6.9-34.ELsmp
-rw-r--r--  1 root root  1504585 Feb 27  2007 vmlinuz-2.6.9-42.0.10.EL
-rw-r--r--  1 root root  1444718 Feb 27  2007 vmlinuz-2.6.9-42.0.10.ELsmp
-rw-r--r--  1 root root  1504411 Aug 23  2006 vmlinuz-2.6.9-42.0.2.EL
-rw-r--r--  1 root root  1444563 Aug 23  2006 vmlinuz-2.6.9-42.0.2.ELsmp
-rw-r--r--  1 root root  1504397 Oct  6  2006 vmlinuz-2.6.9-42.0.3.EL
-rw-r--r--  1 root root  1444549 Oct  6  2006 vmlinuz-2.6.9-42.0.3.ELsmp
-rw-r--r--  1 root root  1504589 Jan 30  2007 vmlinuz-2.6.9-42.0.8.EL
-rw-r--r--  1 root root  1444726 Jan 30  2007 vmlinuz-2.6.9-42.0.8.ELsmp
-rw-r--r--  1 root root  1511559 Nov  2 11:12 vmlinuz-2.6.9-55.0.12.EL
-rw-r--r--  1 root root  1451171 Nov  2 11:31 vmlinuz-2.6.9-55.0.12.ELsmp
-rw-r--r--  1 root root  1511833 Jun 26  2007 vmlinuz-2.6.9-55.0.2.EL
-rw-r--r--  1 root root  1450563 Jun 26  2007 vmlinuz-2.6.9-55.0.2.ELsmp
-rw-r--r--  1 root root  1511604 Sep  4 21:29 vmlinuz-2.6.9-55.0.6.EL
-rw-r--r--  1 root root  1450984 Sep  4 21:57 vmlinuz-2.6.9-55.0.6.ELsmp
-rw-r--r--  1 root root  1511602 Sep 27 18:23 vmlinuz-2.6.9-55.0.9.EL
-rw-r--r--  1 root root  1451003 Sep 27 18:36 vmlinuz-2.6.9-55.0.9.ELsmp
-rw-r--r--  1 root root  1518785 Dec 19 15:58 vmlinuz-2.6.9-67.0.1.EL
-rw-r--r--  1 root root  1458873 Dec 19 16:12 vmlinuz-2.6.9-67.0.1.ELsmp

Bad Machine

drwxr-xr-x  3 root root    1024 Jan 19 14:18 boot
-rw-r--r--  1 root root    50924 Dec 19 15:58 config-2.6.9-67.0.1.EL
-rw-r--r--  1 root root    50498 Dec 19 15:58 config-2.6.9-67.0.1.ELhugemem
-rw-r--r--  1 root root    50549 Dec 19 16:12 config-2.6.9-67.0.1.ELsmp
drwxr-xr-x  2 root root     1024 Jan 18 17:09 grub
-rw-r--r--  1 root root  1351038 Jan 12 06:16 initrd-2.6.9-67.0.1.EL.img
-rw-r--r--  1 root root  1333584 Jan 12 06:16 initrd-2.6.9-67.0.1.ELhugemem.img
-rw-r--r--  1 root root  1334474 Jan 12 06:16 initrd-2.6.9-67.0.1.ELsmp.img
drwx------  2 root root    12288 Oct 17  2006 lost+found
-rw-r--r--  1 root root    64308 Dec 19 15:58 symvers-2.6.9-67.0.1.EL.gz
-rw-r--r--  1 root root    6092 Dec 19 15:58 symvers-2.6.9-67.0.1.ELhugemem.gz
-rw-r--r--  1 root root    65129 Dec 19 16:12 symvers-2.6.9-67.0.1.ELsmp.gz
-rw-r--r--  1 root root   759989 Dec 19 15:58 System.map-2.6.9-67.0.1.EL
-rw-r--r--  1 root root   776762 Dec 19 15:58 System.map-2.6.9-67.0.1.ELhugemem
-rw-r--r--  1 root root   776963 Dec 19 16:12 System.map-2.6.9-67.0.1.ELsmp
-rw-r--r--  1 root root  1518785 Dec 19 15:58 vmlinuz-2.6.9-67.0.1.EL
-rw-r--r--  1 root root  1437120 Dec 19 15:58 vmlinuz-2.6.9-67.0.1.ELhugemem
-rw-r--r--  1 root root  1458873 Dec 19 16:12 vmlinuz-2.6.9-67.0.1.ELsmp

So upon gathering all of this info, I did find the problem I think. The errent boot directory in *bad machine /boot is obviously the one that comes up during start-up. How do I point grub to the correct directory?

[grattman]

WILLIAM....I LOVE YOU...Thank you, you to Ray!

[warren]

For future reference:
Load 7.1, remove files from boot as per this post;

Then;

I tried  successfully on test machine  2 approaches;
1.Boot from 7.3 ISO and upgrade ; System reboots and is working

2. Followed  code below ; also got back to a working system

Code: [Select]

Just for the 'thril' of it, I installed SME 7.1 in a VM.

I then deleted everything in /boot except the grub amd 'lost and found' folders.

I then rebooted. It spat the dummy missing 'stuff' and threw me into a grub screen asking me to select a different kernel.

I then booted with a 7.3 iso into rescue mode. Entered network details for a static IP and away it went.

At the prompt, type chroot /mnt/sysimage followed by cd /root. Ah... home sweet home.

I'm sure the kernel rpms are on the disk but what the heck.... lets get a fresh one.

wget http://mirror.pacific.net.au/linux/smeserver/releases/7/smeos/i386/SME/RPMS/kernel-2.6.9-67.0.1.EL.i686.rpm

Bummer, temp DNS error. No problem

wget http://61.8.0.17/linux/smeserver/releases/7/smeos/i386/SME/RPMS/kernel-2.6.9-67.0.1.EL.i686.rpm

Down it came, followed by

yum localinstall kernel-2.6.9-67.0.1.EL.i686.rpm

then exit exit.

Bummer, still wants the -42 kernel. No problem. Follow the prompts at the grub screen to edit two lines.

b to boot....

Yey.... I'm in.

Just have to now tidy up the /boot/grub/grub.conf file.

[raem]

grattman

A few suggestions.
Don't play or do anything on a production server unless you are 100% sure of what you are doing, and know that the method you plan to use is correct.
If in doubt, don't.
If in doubt, ask first.

Have a test server that is configured similarly to your production server, so you can test any changes you are planning to make.
Even a standard install of the OS only is sufficient for testing.
This could be an old retired (underpowered) box or a "virtual" install using VMWare etc.
If you do something wrong, then you know not to do that on the production server.
A test server will also allow you to work out what is the right way of doing things, as William has demonstrated. He recreated the scenario you "inadvertantly" created, and then worked out how to fix it.

Read the forums carefully and as you say, don't blindly accept everything that has been written, there is much wrong information out there.
Learn more about Linux and about installing & unistalling rpms etc.
I don't know of any operating system that recommends deleting files, there are usually correct procedures to follow for file removal eg rpm -e packagename in this case. On this note even though many people are suggesting to use yum remove (and that is even in quite a few howtos), the recommended method is
rpm -e packagename
as yum remove can remove a lot of other wanted rpms.

Also read & search bugzilla, if you had done this you would have found the correct method for removing kernels (which I pasted earlier in this thread).
When you do searches, don't give up because nothing was found or there were no results, do an advanced search as that is often required to find what you want.

Reading the many howtos & contribs articles also gives an insight into correct methods to use, and although you may not be interested in a certain contrib, the method of installing and configuring is universal.

A test server is also a good idea as you can see what files are supposed to be in certain places, and you could even retrieve missing config file(s) from the test server and transfer then to the real server.


Your comment about peer reviewed posts has been raised before
http://forums.contribs.org/index.php?topic=38573.0
although it seems the karma points has disappeared again.


If you are still having problems then you need to be very specific about what procedure you followed and what commands you entered, as no-one can guess what you do.

[raem]

grattman

Not sure if you have fixed your problem yet or not ?

The errent boot directory in *bad machine /boot is obviously the one that comes up during start-up. How do I point grub to the correct directory?

You can directly edit
/boot/grub/grub.conf

Bad Machine
less /boot/grub/grub.conf
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/main/root
#          initrd /initrd-version.img
#boot=/dev/sda
default=2
timeout=5
splashimage=(hd0,0)/grub/smeserver.xpm.gz
foreground 000000
background 4E95D3
hiddenmenu
title SME Server (2.6.9-67.0.1.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.1.ELhugemem ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.1.ELhugemem.img
title SME Server (2.6.9-67.0.1.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.1.ELsmp ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.1.ELsmp.img
title SME Server (2.6.9-67.0.12.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.1.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.1.EL.img

This line appears to be incorrect
title SME Server (2.6.9-67.0.12.EL)
it should be
title SME Server (2.6.9-67.0.1.EL)

You appear to have incorrectly edited an earlier kernel entry ie
SME Server (2.6.9-55.0.12.EL)
and mixed up the numbers
You system is set to boot to that incorrectly named kernel ie default=2

You might also like to hash out hiddenmenu so you can see the kernel choices at startup time, and increase the time the menu is displayed for
eg do
#hiddenmenu
timeout=15

[grattman]

Ray,

To answer your question, yes I have solved the issue. Thanks to you and William, I pieced enough together to locate that when I screwed up grub, it had installed a /boot/boot/grub which was what the MBR was pointing to. That is why I could not make grub see the kernel. I know about the production server/test server idea. Education does not always allow for that to happen unfortunately.

Thanks to you, William, and my screw up, I have learned a ton about 'nix in the last 48+ hours.

As for removing the kernels, a simple rpm -e kernel-x.x.old will result in a "not installed" if it is not an active kernel. This is one of the things that lead to my issue. I followed that advice and you cannot uninstall a kernel that seems to have been superseded. I may be wrong, but I did an rpm -e of the oldest kernel I had and got the "not installed." So even the sagest of advice was incorrect at the time.

I have been very careful over the years not to fubar my live server. This is how we learn, and I presume I am not the first one to have brought down a production server. I do appreciate the reminder about "measure twice, cut once" Ray.

Thansk for all your help and I have documented everything I did wrong, as well as what I did right (with some help  )

[william_syd]

I have learned a ton about 'nix in the last 48+ hours.

That makes two of us.

Now I need to know more about grub and RAID.

grub> find /grub/stage1
 (hd0,0)
 (hd1,0)

grub>

[raem]

grattman

As for removing the kernels, a simple rpm -e kernel-x.x.old will result in a "not installed" if it is not an active kernel. This is one of the things that lead to my issue. I followed that advice and you cannot uninstall a kernel that seems to have been superseded. I may be wrong, but I did an rpm -e of the oldest kernel I had and got the "not installed."

The rpm command to remove has always been
rpm -e packagename
where for the rpm
kernel-smp-2.6.9-67.0.1.EL.i586.rpm
you would substitute packagename with kernel-smp-2.6.9-67.0.1.EL
so
rpm -e kernel-smp-2.6.9-67.0.1.EL

Note you cannot insert wildcards eg ** , and if you do then you will get a message like the one you did get ie
"package not installed"
which is then misleading as you believe the package is not installed.

Currently as new kernels are installed old ones are not removed, so
rpm -qa kernel*
will show you a list of all still installed kernels
which you can then manually uninstall with the correct rpm -e commands.
The active kernel is found with
uname -r
which of course you do not uninstall.

Some work is being discussed in bugzilla to automatically remove old kernels as new ones are installed, as the /boot partition is only 100Mb which eventually gets filled.

[stiperstones]

grattman

The rpm command to remove has always been
rpm -e packagename
where for the rpm
kernel-smp-2.6.9-67.0.1.EL.i586.rpm
you would substitute packagename with kernel-smp-2.6.9-67.0.1.EL
so
rpm -e kernel-smp-2.6.9-67.0.1.EL

Note you cannot insert wildcards eg ** , and if you do then you will get a message like the one you did get ie
"package not installed"
which is then misleading as you believe the package is not installed.

Currently as new kernels are installed old ones are not removed, so
rpm -qa kernel*
will show you a list of all still installed kernels
which you can then manually uninstall with the correct rpm -e commands.
The active kernel is found with
uname -r
which of course you do not uninstall.

Some work is being discussed in bugzilla to automatically remove old kernels as new ones are installed, as the /boot partition is only 100Mb which eventually gets filled.

Hi Ray
Maybe a good one to put it in the wiki FAQ has it appears i did'nt explain the method in my post to remove old kernels i just pointed grattman to the procedure i used and created grattman some servere problems with his installation.

Has you have pointed out we need to follow the instructions in this post http://forums.contribs.org/index.php?topic=38573.0

And to grattman i apologize for the problem i have created for you

[gasparraposo]

Can someone please help me. I am having the same problem and i dont know what to do. I went through everything that was done here, except what is did not understand was,

---------------------
Bummer, still wants the -42 kernel. No problem. Follow the prompts at the grub screen to edit two lines.

b to boot....

Yey.... I'm in.

Just have to now tidy up the /boot/grub/grub.conf file.
---------------------------

what is the procedure to follow the prompt a tthe grub screen and get this working. Please help someone.

[SoftDux]

incase you couldn't get it working.

Boot up with the installation CD (or Knopping Live CD / Ubuntu / RescueCD - Everyone should have one!!), copy the needed kernerl rpm to the HDD with a USB memory stick (which you have downloaded to the SAME PC that you're reading this ), install it with rpm, and then edit /boot/grub/grub.conf - the make sure it's looking for the SAME FILE


Here's my grub.conf file:

[root@intranet ~]# more /boot/grub/grub.conf
# 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/hdd
default=0
timeout=5
splashimage=(hd0,0)/grub/smeserver.xpm.gz
foreground 000000
background 4E95D3
hiddenmenu
title CentOS (2.6.9-67.0.1.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.1.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.1.EL.img
title SME Server (2.6.9-55.0.2.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-55.0.2.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-55.0.2.EL.img
[root@intranet ~]#

As you can see, it's looking for either vmlinuz-2.6.9-67.0.1.EL OR vmlinuz-2.6.9-55.0.2.EL to boot, and these both need to be in the /root parition:

[root@intranet ~]# ll /boot/vmlinuz-2.6.9-55.0.2.EL
-rw-r--r--  1 root root 1511833 Jun 26  2007 /boot/vmlinuz-2.6.9-55.0.2.EL
[root@intranet ~]# ll /boot/vmlinuz-2.6.9-67.0.1.EL
-rw-r--r--  1 root root 1518785 Dec 19 22:58 /boot/vmlinuz-2.6.9-67.0.1.EL

I'm almost sure you can copy the kernels from an existing SME installation as well.