[Bug 803749] Re: grub-install fails during d-i installation when /boot/grub is located on md raid device

[pcanham]

Also seeing this issue as well but only when i try and preseed the disk
partitions, if i manually enter in the partitions things work OK


d-i partman-auto/disk string /dev/sda /dev/sdb /dev/sdc /dev/sdd
d-i partman-auto/expert_recipe string multiraid :: 989999 9899999 989999 raid $primary{ } $bootable{ } method{ raid } . 1 1 1 raid method{ biosgrub } . 10000 10000 10000 raid  method{ raid } .
d-i partman-auto-raid/recipe string  1 2 0 ext4 / /dev/sda1#/dev/sdb1 . 1 2 0 swap - /dev/sda5#/dev/sdb5 . 1 2 0 ext4 /app1 /dev/sdc1#/dev/sdd1 .
d-i partman-basicfilesystems/mountoptions multiselect noatime
d-i mdadm/boot_degraded boolean true
d-i partman-md/confirm boolean true
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman-md/confirm_nooverwrite true

Following Bug #743136 looks simular so could be a regression some where.

Work around is to drop into the shell and run the following

chroot /target
ln -s /dev/md0 /dev/md/0
ln -s /dev/md1 /dev/md/1
ln -s /dev/md2 /dev/md/2
grub-install /dev/sda
grub-install /dev/sdb

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/803749

Title:
  grub-install fails during d-i installation when /boot/grub is located
  on md raid device

Status in “grub2” package in Ubuntu:
  New

Bug description:
  I have experienced a failure to install Ubuntu natty, using the d-i
  (alternate, not ubiquity) installer.

  The actual failure occurs when the installer executes grub-install.
  Debugging a bit shows that the actual failing command is "grub-probe
  -t fs /boot/grub". Debugging a bit more shows that /boot/grub is in my
  situation, located on /dev/md0, and the failure involves grub-probe
  attempting to execute /dev/md/0 (note: md/0, not md0) which does not
  exist during the installer run.

  A further point of interest found by looking into the grub code is
  that grub only ends up looking for md/0 rather than md0 if the array
  is using a version 1 md superblock - i.e. my problem is worked around
  by using a version 0.90 md superblock.

  But, there seems to be some other wrinkle involved that I have not yet
  diagnosed, as the above problems were experienced on real hardware,
  using a partman-auto-raid recipe, whilst attempting a kvm test install
  without the preseed resulted in the md/0 symlink being created. More
  info to come...

  Other notes - the following bugs may be related to some degree:
  bug 713874
  bug 789226
  bug 701351

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/803749/+subscriptions