[ale] Fedora Booting experts

[scott mcbrien]

Greg,
mdadm --detail /dev/md0 (or whatever your number is for /boot) will tell you
the membership

What's a df -h look like?  I notice you have a BOATLOAD of kernels sitting
out there, and the typical Fedora install makes a 100MB boot filesystem.
 Obviously you did your own thing for partitioning, with the RAID, but you
might do a df -h to make sure you have room.

Based on your updated post, maybe you need to yum remove some old kernels?

Also check the mdadm --detail /dev/mdwhatever to make sure you don't have a
failed device.

Finally, make sure that your default setting in /boot/grub/grub.conf points
to the right kernel, sometimes they'll not make the most recent one the
default based on your other settings in the file.

-Scott



On Mon, Jun 22, 2009 at 4:18 PM, Jim Kinney <jim.kinney at gmail.com> wrote:

> /boot on raid1 will not cause an issue. The BIOS will connect to what
> it's told (sda, sdb, etc NOT md0). It keeps /boot in sync for a manual
> bootup with a failed sda.
>
> Basically, it sounds like the kernel upgrade failed or there is a
> block on kernel upgrades (it's a yum plugin - found in
> /etc/yum/pluginconf.d/).
>
> try a removal of the kernel rpm and reinstall and check
> /boot/grub/grub.conf to see if it upgraded the file. If not, do it
> manually and follow the pattern there.
>
> On Mon, Jun 22, 2009 at 4:02 PM, Greg Freemyer<greg.freemyer at gmail.com>
> wrote:
> > I just realized my /boot partition is on a raid1 mdraid setup.
> >
> > I've never tried to have my grub setup files on a mdraid setup.  I
> > suspect it is causing me issues.
> >
> > Advice very welcome about how to proceed.
> >
> > Thanks
> > Greg
> >
> > On Mon, Jun 22, 2009 at 3:45 PM, Greg Freemyer<greg.freemyer at gmail.com>
> wrote:
> >> All,
> >>
> >> I normally run suse, but I've got one appliance that is running Fedora
> >> so maybe I'm not troubleshooting this right.
> >>
> >> I upgraded the kernel via rpm a few weeks ago, but now realize I'm
> >> still running the old one.
> >>
> >> I've just rebooted and hit the space bar at the right time to see the
> >> grub boot menu.  It has a single entry for a 2.6.21 kernel.  Nothing
> >> else to choose.
> >>
> >> But if I look at /boot/grub/menu.lst I see three menu choices.  The
> >> first one is the default and it is 2.6.22 which is what I want.  I
> >> guess that file might be corrupt, but it looks okay to me.
> >>
> >> I did a "find / -name menu.lst" but I only have the one file.
> >>
> >> Any ideas on where else to look?
> >>
> >> Thanks
> >> Greg
> >> --
> >> Greg Freemyer
> >> Head of EDD Tape Extraction and Processing team
> >> Litigation Triage Solutions Specialist
> >> http://www.linkedin.com/in/gregfreemyer
> >> First 99 Days Litigation White Paper -
> >>
> http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf
> >>
> >> The Norcross Group
> >> The Intersection of Evidence & Technology
> >> http://www.norcrossgroup.com
> >>
> >
> >
> >
> > --
> > Greg Freemyer
> > Head of EDD Tape Extraction and Processing team
> > Litigation Triage Solutions Specialist
> > http://www.linkedin.com/in/gregfreemyer
> > First 99 Days Litigation White Paper -
> >
> http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf
> >
> > The Norcross Group
> > The Intersection of Evidence & Technology
> > http://www.norcrossgroup.com
> >
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://mail.ale.org/mailman/listinfo/ale
> >
>
>
>
> --
> --
> James P. Kinney III
> Actively in pursuit of Life, Liberty and Happiness
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20090622/fe5bfd24/attachment-0001.html