Re: booting from a raid1

[lee]

On Fri, Oct 01, 2010 at 03:49:28PM +0200, lee wrote:
> On Fri, Oct 01, 2010 at 09:25:19AM -0400, Tom H wrote:
> > On Fri, Oct 1, 2010 at 8:50 AM, lee <address@hidden> wrote:
> > > On Fri, Oct 01, 2010 at 12:22:28PM +0200, Emil Micek wrote:
> > >> On Fri, 1 Oct 2010, lee wrote:

> > >> As far as i know grub2 can't boot from raid arrays with version 1.2
> > >> metadata superblock. At least your /boot partition must reside on
> > >> RAID with version 0.9 superblock.
> > >
> >  grub2  (1.98+20100720-1) unstable; urgency=low
> > 
> 
> There seems to be version 1.98+20100 in testing, so it should work:
> 
> 
> yun:~# apt-cache show grub2
> Version: 1.98+20100804-4
> 
> 
> need to/can I somehow use chroot to switch to the new root partition
> and then use grub-install or grub-mkconfig from there so that it will
> create the grub.cfg as needed?

Ok, I tried with chroot, but grub-install doesn't create a grub.cfg at
all. It only warns about improperly nested partitions and an unknown
filesystem as before but says the installation finished with no
errors.

When running grub-mkconfig, I'm getting the following output (letting
aside the warnings and the error message about the unknown filesystem):


#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  insmod vbe
  insmod vga
  insmod video_bochs
  insmod video_cirrus
}

insmod raid
insmod mdraid
insmod part_msdos
insmod part_msdos


... and that's all. The last line when grub-mkconfig prints to stdout is:


/usr/sbin/grub-probe: error: unknown filesystem.


All the partitions use ext4. Doesn't grub know about ext4?