RE: kernel wont boot

From: Hamilton Andrew (Andrew.Hamilton_at_afccc.af.mil)
Date: 02/04/04

  • Next message: Abhinav Gautam: "respawning error in Red Hat 7.1"
    To: redhat-list@redhat.com
    Date: Wed, 4 Feb 2004 10:19:35 -0500
    
    

    Roger,

    For your grub.conf file look in /boot/grub. Just do an 'ls' of the /boot
    directory to get that. Have you tried reinstalling the new kernel? You may
    give that a shot. I sometimes have things that don't install and it's
    usually because I've modified the configuration. You've stated that you
    haven't messed with anything and I believe you. It could be that something
    you've installed has modified a configuration file and that is preventing it
    from doing a complete install. Usually rpm complains so you know. Seems a
    bit far fetched but still possible, I guess. The exact message would be
    helpful along with the other information. You'll definitely want to get the
    latest kernel for security reasons, especially for a mail server.

    Drew

    -----Original Message-----
    From: roger2 [mailto:roger2@rogernet.net]
    Sent: Wednesday, February 04, 2004 10:06 AM
    To: redhat-list@redhat.com
    Subject: Re: kernel wont boot

    Thanks. In my clumsy way I was saying I had just booted using the previous
    kernel as the simple fix.
    If you could give me the commands to get the info I will have ago tonight.
    It's my mail server but I will risk a reboot to note the exact message.
    But as far as I remember it's the one as posted in the other posting but
    not for the same reason obviously.
    Regards Roger

    On Wed, 4 Feb 2004 08:58:56 -0500, Hamilton Andrew
    <Andrew.Hamilton@afccc.af.mil> wrote:
    > Roger,
    >
    > What exact error are you getting and what does your grub.conf look like?
    > Also what are the contents of your /boot directory? Some of this
    > information might help in tracking down your problem. You can go back to
    > the latest working boot configuration which is a reason I always leave it
    > and try again. That is probably simplest. If that still causes you
    > problems repost and we'll see if we can't help you fix it.
    >
    > Drew
    >
    > -----Original Message-----
    > From: Roger Beever [mailto:roger2@rogernet.net]
    > Sent: Tuesday, February 03, 2004 5:40 PM
    > To: redhat list
    > Subject: RE: kernel wont boot
    >
    >
    > On Tue, 2004-02-03 at 18:27, Hamilton Andrew wrote:
    >> Roger,
    >>
    >> Are you using grub or lilo? Not that it matters but the config is a
    >> little different. Make sure you have the new kernel in the config
    >> file. Make sure you have the initrd to match your version of the
    >> kernel. If not use mkinitrd to create the initrd. Read the manpage
    >> for the syntax, it's pretty simple. I've never had this happen to me
    >> using up2date but that doesn't mean it can't. I don't use labels for
    >> my partitions, I typically just boot the root device so if you are
    >> using labels it may be a function of loading the modules using the
    >> ramdisk(initrd).
    >>
    >> Drew
    > GRUB
    > with a straight off the CD type install spread over 2 drives.
    > root should be on hda1 as far as I remember.
    > Might it be easier to remove the latest kernel and try again?
    > I have made no changes to GRUB
    >
    >

    -- 
    Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    

  • Next message: Abhinav Gautam: "respawning error in Red Hat 7.1"

    Relevant Pages

    • Re: Help 10.3 a mess After YOU Upgrade
      ... GRUB stage1. ... The stage1 goes in boot sector of system root partition. ... sda6=/1st SUSE install ... and kernel as defined for selected menu item. ...
      (alt.os.linux.suse)
    • Re: RHEL kernel update install problem!
      ... Because if you did an install, the previous version should still be there, and it should be simple to get you en route again. ... "root " means that grub is installed on the first partition of the first hard drive. ... All that needs to be done now, is boot the older kernel, remove the potentially defective new one, and free enough space on /boot. ... Each entry in the grub menu starts with the "title" tag, so you can try to construct a new entry along the same lines, referencing your new kernel and corresponding initrd. ...
      (RedHat)
    • Re: 12.04.2 LTS, new install, network broken
      ... Then you can share that between multiple installs, Ubuntu, Kubuntu, ... bug tracker from the networking failed install. ... and I haven't looked to find it other than grub didn't ... Because that xenomai patched kernel build is real time enough to be able to ...
      (Ubuntu)
    • Re: kernel upgrade bug?
      ... It's been doing this for a little while now, I just wanted to double check the new kernel is the same. ... I have no idea what would cause dracut to fail in this way. ... But you can find out the version of grub installed on /dev/sda with: ... # install local /etc/lvm/lvm.conf ...
      (Fedora)
    • RE: EL4 ES kernel recompile
      ... We need to build the source rpm to get the sources. ... Install kernel-.src.rpm (given the default RPM configuration, ... the kernel tree will be located ...
      (RedHat)