On Sun, Oct 7, 2012 at 2:36 PM, John Robinson <john.robinson@xxxxxxxxxxxxxxxx> wrote: > On 07/10/2012 07:24, Arun Khan wrote: >> >> Hi John, >> >> I posted the requested info to the list. >> >> I was wondering if you had a chance to go through it. >> >> Either way do let me know. I am anxious to get this solved if possible. > > > Sorry, I was distracted by $realjob... No issues. We all have to worry about putting bread on the dinner table :) > The only thing that occurs to me is: > > >>> # cat /boot/grub/grub.conf >>> # grub.conf generated by anaconda >>> # >>> # Note that you do not have to rerun grub after making changes to this >>> file >>> # NOTICE: You do not have a /boot partition. This means that >>> # all kernel and initrd paths are relative to /, eg. >>> # root (hd0,0) >>> # kernel /boot/vmlinuz-version ro root=/dev/sda1 >>> # initrd /boot/initrd-[generic-]version.img >>> #boot=/dev/sda > > > this. Uncomment it, and change to boot=/dev/md_d0p1, and re-run > `grub-install`. > OK. Will do so and let you know. > Also, just to be sure, if you haven't installed a new kernel since migrating > to RAID, update your initrd - something like `mkinitrd -f > /boot/initramfs-2.6.32-220.el6.x86_64.img 2.6.32-220.el6`. > No I have not updated any package, let alone the kernel. Thanks, -- Arun Khan -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
