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

[pcanham]

Architecture: amd64
BootDmesg: (Nothing has been logged yet.)
DistroRelease: Ubuntu 11.04
MDadmExamine.dev.sda: Error: command ['/sbin/mdadm', '-E', '/dev/sda'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda.
MDadmExamine.dev.sda1: Error: command ['/sbin/mdadm', '-E', '/dev/sda1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda1.
MDadmExamine.dev.sda3: Error: command ['/sbin/mdadm', '-E', '/dev/sda3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sda3.
MDadmExamine.dev.sdb: Error: command ['/sbin/mdadm', '-E', '/dev/sdb'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb.
MDadmExamine.dev.sdb1: Error: command ['/sbin/mdadm', '-E', '/dev/sdb1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb1.
MDadmExamine.dev.sdb3: Error: command ['/sbin/mdadm', '-E', '/dev/sdb3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdb3.
MDadmExamine.dev.sdc: Error: command ['/sbin/mdadm', '-E', '/dev/sdc'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdc.
MDadmExamine.dev.sdc1: Error: command ['/sbin/mdadm', '-E', '/dev/sdc1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdc1.
MDadmExamine.dev.sdc3: Error: command ['/sbin/mdadm', '-E', '/dev/sdc3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdc3.
MDadmExamine.dev.sdc5: Error: command ['/sbin/mdadm', '-E', '/dev/sdc5'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdc5.
MDadmExamine.dev.sdd: Error: command ['/sbin/mdadm', '-E', '/dev/sdd'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd.
MDadmExamine.dev.sdd1: Error: command ['/sbin/mdadm', '-E', '/dev/sdd1'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd1.
MDadmExamine.dev.sdd3: Error: command ['/sbin/mdadm', '-E', '/dev/sdd3'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd3.
MDadmExamine.dev.sdd5: Error: command ['/sbin/mdadm', '-E', '/dev/sdd5'] failed with exit code 1: mdadm: No md superblock detected on /dev/sdd5.
Package: mdadm 3.1.4-1+8efb9d1ubuntu4.1
PackageArchitecture: amd64
ProcCpuinfo: Error: [Errno 2] No such file or directory: '/proc/cpuinfo'
ProcEnviron: Error: [Errno 2] No such file or directory: '/proc/7461/environ'
ProcInterrupts: Error: [Errno 2] No such file or directory: '/proc/interrupts'
ProcKernelCmdLine: Error: [Errno 2] No such file or directory: '/proc/cmdline'
ProcMDstat: Error: [Errno 2] No such file or directory: '/proc/mdstat'
ProcModules: Error: [Errno 2] No such file or directory: '/proc/modules'
ProcMounts: Error: [Errno 2] No such file or directory: '/proc/mounts'
ProcPartitions: Error: [Errno 2] No such file or directory: '/proc/partitions'
Tags:  natty natty
UdevDb:
 
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 2.6.38-8-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'


** Tags added: apport-collected natty

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm 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
Status in “mdadm” 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