[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: Why does old kernel boot when new kernel installed?



Hello Juri & Others,

I have found a difference between the setups of the machines that upgraded
kernel OK and the 1 that did not.

We thought we had setup all these machines as:

[root co1 /]# df -k
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/md0              38480340    505032  36020604   2% /
/dev/hdb1                69973     17976     48384  28% /boot
none                    511552         0    511552   0% /dev/shm

Where md0 is a large RAID1 partition for everything but /boot

But the machine with the problem has:

[root ns5 boot]# df -k
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/md0              36463784   5642076  28969420  17% /
none                    510400         0    510400   0% /dev/shm

Where /boot is ALSO on the RAID1 partition ( this must have been a mistake
at setup time ..... although the machine works fine apart from a LOT of
kjournald activity (up to 60% CPU!).)

Could this be causing GRUB not to see the other kernels & if so what can we
do?

This is a busy public server with several 100 users ......... we have to be
v careful doing anything.

Regards,
Nico Morrison
nico morrison micronicos com
___________________________________________
Micronicos Limited  -  London, UK.
Tel: +44 20 8870 8849 Fax: +44 20 8870 5290
___________________________________________

From: Juri Haberland [mailto:juri koschikode com]
Sent: 06 February 2003 12:53
To: ext3 users list
Subject: Re: Why does old kernel boot when new kernel installed?


Nico Morrison wrote:
> Hello,
> 
> Yes - verified with uname -a

> Last night I did kernel upgrades of 3 other machines & all went through
just
> fine ..... only this 1 machine has this problem?
> 
> In answer - only 1 grub.conf

Is it possible that you have a /boot partition that get's mounted over
the real /boot?
I noticed looking at your grub.conf that it tells something about your
server not having a separate /boot partition. So everything is setup to
be on the / partition. If, for some unknown reason, you do have a /boot
partition that gets mounted, all changes to the kernels and grub.conf
will be on that partition but at boot time grub will look at the /
partition where no changes occurred.
Uhm, is it understandable what I just wrote?

Regards,
Juri



_______________________________________________
Ext3-users mailing list
Ext3-users redhat com
https://listman.redhat.com/mailman/listinfo/ext3-users





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]