On Fri, Oct 8, 2010 at 4:12 AM, lee <[email protected]> wrote: > On Fri, Oct 08, 2010 at 12:40:59AM -0700, Jordan Uggla wrote: >> On Fri, Oct 8, 2010 at 12:25 AM, lee <[email protected]> wrote: >> > Hmm ... Ok, I just tried with a separate /boot partition mounted >> > directly under /boot on the root partition, but grub-install doesn't >> > create a grub.cfg. >> >> grub-install never creates a grub.cfg, that's what grub-mkconfig is for. > > Hm, well, ok, I created a grub.cfg with grub-mkconfig and edited it: > > > [...] > menuentry 'Debian GNU/Linux, with Linux 2.6.35.6-tst' --class debian --class > gnu-linux --class gnu --class os { > insmod part_msdos > insmod ext2 > insmod raid > insmod mdraid > set root='(/dev/sdd,msdos1)' > search --no-floppy --fs-uuid --set e62e0c56-2531-4ec4-a839-1835b8b0a8cc > echo 'Loading Linux 2.6.35.6-tst ...' > linux /vmlinuz-2.6.35.6-tst iommu=noaperture root=/dev/md0p2 ro > } > [...] > > > Now I can boot from /dev/sdd, but the kernel panics because it can't > mount the root filesystem (/dev/md0p2). Entries in /etc/fstab on md0p2 > are correct. I take it the md-devices aren't up/accessible in time. > > Any idea what's missing? Like there's no RAID support in grub? > > _______________________________________________ > Help-grub mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/help-grub >
Have you made a new initrd that has md and/or raid support? I ran into a similar problem when using grub2 to boot off of an LVM partition. I had to add a couple modules to the initrd /lib and edit the init script to load them. _______________________________________________ Help-grub mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-grub
