Hi Mike, 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? I'm just trying to helpfully brainstorm. :) -Rob On Mon, May 7, 2012 at 1:00 AM, Mike Miller <mbmiller+l at gmail.com> wrote: > In my other RAID1s I've had /boot in the RAID. Actually, there was no > separate /boot partition, it was just in / and that seemed to work. Now > that I have a larger HDD, > 2TB, and I have to use GPT instead of DOS, I've > had to make /boot partitions on both physical drives in the RAID1, but the > two /boot partitions are not in the RAID. When I had Ubuntu install grub, > it installed it on both /dev/sda and /dev/sdb, which is where the two /boot > partitions are found. > > The thing that concerns me is that I don't see /boot if I run df, and I'm > not sure how kernel upgrades will be handled. Will they go to the hidden > /boot partitions on both /dev/sda and /dev/sdb? Ubuntu was clearly aware > of them and I told the install that I wanted to be able to boot even with a > degraded drive, so it was supposed to install the boot loader on both > physical drives (and it seemed to do that). > > What do you think? > > Thanks again for answering so many of my questions! > > Mike > ______________________________**_________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/**mailman/listinfo/tclug-list<http://mailman.mn-linux.org/mailman/listinfo/tclug-list> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20120507/2b2e6390/attachment.html>