Thanks Scott,<br><br>My /dev/md0 is broken, thus the issues.<br><br>=========<br># mdadm --detail /dev/md0<br>/dev/md0:<br> Version : 00.90.03<br> Creation Time : Wed Feb 13 06:43:55 2008<br> Raid Level : raid1<br>
Array Size : 104320 (101.89 MiB 106.82 MB)<br> Used Dev Size : 104320 (101.89 MiB 106.82 MB)<br> Raid Devices : 2<br> Total Devices : 1<br>Preferred Minor : 0<br> Persistence : Superblock is persistent<br><br>
Update Time : Mon Jun 22 16:04:59 2009<br> State : clean, degraded<br> Active Devices : 1<br>Working Devices : 1<br> Failed Devices : 0<br> Spare Devices : 0<br><br> UUID : 5107322d:edf96272:646ce4cb:c4da3a32<br>
Events : 0.990<br><br> Number Major Minor RaidDevice State<br> 0 0 0 0 removed<br> 1 8 17 1 active sync /dev/sdb1<br><br>=========<br><br>Greg<br>
<br><div class="gmail_quote">On Mon, Jun 22, 2009 at 4:37 PM, scott mcbrien <span dir="ltr"><<a href="mailto:smcbrien@gmail.com">smcbrien@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Greg,<div><br></div><div>mdadm --detail /dev/md0 (or whatever your number is for /boot) will tell you the membership</div><div><br></div><div>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.</div>
<div><br></div><div>Based on your updated post, maybe you need to yum remove some old kernels?</div><div><br></div><div>Also check the mdadm --detail /dev/mdwhatever to make sure you don't have a failed device.</div>
<div>
<br></div><div>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.</div>
<div><br></div><div>-Scott</div><div><br></div><div><br></div><div><br><div class="gmail_quote"><div class="im">On Mon, Jun 22, 2009 at 4:18 PM, Jim Kinney <span dir="ltr"><<a href="mailto:jim.kinney@gmail.com" target="_blank">jim.kinney@gmail.com</a>></span> wrote:<br>
</div><div><div></div><div class="h5"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">/boot on raid1 will not cause an issue. The BIOS will connect to what<br>
it's told (sda, sdb, etc NOT md0). It keeps /boot in sync for a manual<br>
bootup with a failed sda.<br>
<br>
Basically, it sounds like the kernel upgrade failed or there is a<br>
block on kernel upgrades (it's a yum plugin - found in<br>
/etc/yum/pluginconf.d/).<br>
<br>
try a removal of the kernel rpm and reinstall and check<br>
/boot/grub/grub.conf to see if it upgraded the file. If not, do it<br>
manually and follow the pattern there.<br>
<div><div></div><div><br>
On Mon, Jun 22, 2009 at 4:02 PM, Greg Freemyer<<a href="mailto:greg.freemyer@gmail.com" target="_blank">greg.freemyer@gmail.com</a>> wrote:<br>
> I just realized my /boot partition is on a raid1 mdraid setup.<br>
><br>
> I've never tried to have my grub setup files on a mdraid setup. I<br>
> suspect it is causing me issues.<br>
><br>
> Advice very welcome about how to proceed.<br>
><br>
> Thanks<br>
> Greg<br>
><br>
> On Mon, Jun 22, 2009 at 3:45 PM, Greg Freemyer<<a href="mailto:greg.freemyer@gmail.com" target="_blank">greg.freemyer@gmail.com</a>> wrote:<br>
>> All,<br>
>><br>
>> I normally run suse, but I've got one appliance that is running Fedora<br>
>> so maybe I'm not troubleshooting this right.<br>
>><br>
>> I upgraded the kernel via rpm a few weeks ago, but now realize I'm<br>
>> still running the old one.<br>
>><br>
>> I've just rebooted and hit the space bar at the right time to see the<br>
>> grub boot menu. It has a single entry for a 2.6.21 kernel. Nothing<br>
>> else to choose.<br>
>><br>
>> But if I look at /boot/grub/menu.lst I see three menu choices. The<br>
>> first one is the default and it is 2.6.22 which is what I want. I<br>
>> guess that file might be corrupt, but it looks okay to me.<br>
>><br>
>> I did a "find / -name menu.lst" but I only have the one file.<br>
>><br>
>> Any ideas on where else to look?<br>
>><br>
>> Thanks<br>
>> Greg<br>
>> --<br>
>> Greg Freemyer<br>
>> Head of EDD Tape Extraction and Processing team<br>
>> Litigation Triage Solutions Specialist<br>
>> <a href="http://www.linkedin.com/in/gregfreemyer" target="_blank">http://www.linkedin.com/in/gregfreemyer</a><br>
>> First 99 Days Litigation White Paper -<br>
>> <a href="http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf" target="_blank">http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf</a><br>
>><br>
>> The Norcross Group<br>
>> The Intersection of Evidence & Technology<br>
>> <a href="http://www.norcrossgroup.com" target="_blank">http://www.norcrossgroup.com</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> Greg Freemyer<br>
> Head of EDD Tape Extraction and Processing team<br>
> Litigation Triage Solutions Specialist<br>
> <a href="http://www.linkedin.com/in/gregfreemyer" target="_blank">http://www.linkedin.com/in/gregfreemyer</a><br>
> First 99 Days Litigation White Paper -<br>
> <a href="http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf" target="_blank">http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf</a><br>
><br>
> The Norcross Group<br>
> The Intersection of Evidence & Technology<br>
> <a href="http://www.norcrossgroup.com" target="_blank">http://www.norcrossgroup.com</a><br>
><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
><br>
<br>
<br>
<br>
</div></div>--<br>
--<br>
<div>James P. Kinney III<br>
Actively in pursuit of Life, Liberty and Happiness<br>
<br>
_______________________________________________<br>
</div><div><div></div><div>Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
</div></div></blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Greg Freemyer<br>Head of EDD Tape Extraction and Processing team<br>Litigation Triage Solutions Specialist<br><a href="http://www.linkedin.com/in/gregfreemyer">http://www.linkedin.com/in/gregfreemyer</a><br>
First 99 Days Litigation White Paper - <a href="http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf">http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf</a><br><br>The Norcross Group<br>
The Intersection of Evidence & Technology<br><a href="http://www.norcrossgroup.com">http://www.norcrossgroup.com</a><br>