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.