<html><head></head><body bgcolor="#FFFFFF"><div><br><br>On May 8, 2012, at 2:08 AM, Robert Nesius <<a href="mailto:nesius@gmail.com">nesius@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><br><br><div class="gmail_quote">On Tue, May 8, 2012 at 1:54 AM, Mike Miller <span dir="ltr"><<a href="mailto:mbmiller+l@gmail.com" target="_blank">mbmiller+l@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, 7 May 2012, Robert Nesius wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Perhaps my memory is fuzzy, but I had thought you had created to small partitions named boot or /boot that were outside of the raid for the sole purpose of giving your bootloader a home that your BIOS can deal with. So, I'm not surprised you don't see it when you run df, as I'm guessing you haven't added that little partition to your fstab?<br>
<br>
I'm just trying to helpfully brainstorm. :)<br>
</blockquote>
<br>
Aha! That makes sense. So it isn't being mounted. I'll study this further. Does it have to be mounted for kernel upgrades to work properly?<br><br></blockquote><div><br></div><div>No - I don't think it does. When you upgrade your kernel, your boot-loader configs should get updated automagically. </div>
<div><br></div><div>-Rob</div><div> </div></div></div></blockquote><br><div><br></div><div><br></div><div>What!?!?</div><div><br></div><div>How can the kernel upgrade process put the new kernel in the correct /boot partition if it isn't mounted?</div><div><br></div><div>What I suspect is that the upgrade process might (silently?) create a /boot directory in the RAID-ed / which would not be useful because the BIOS might not be able to see into it. If you have a separate partition for /boot then you would want the /boot mount point directory to exist AND be empty on the RAID-ed / partition. </div><div><br></div><div><br></div><div>That said, I thought that GRUB (grub2?) had been updated so that non-RAID /boot partitions were no longer required. </div><div><br></div><div>Thomas </div><div><br></div></body></html>