[Bug 1309639] Re: grub confused by named md raid arrays

[PMOverfield]

Wow! This is going back somewhat. My recollection is as follows:

Home-built PC:
     PROBABLY based on Asus M4A89TD PRO MoBo, with 8GB Kingston RAM, 
nVidia Graphics with Quadro NVS285 GPU, AMD Phenom II X4 960T CPU, and 
TWO-off Western Digital 1TB HDDs in RAID-1 configuration for most of the 
installation partitions. Unfortunately this system is now my principal 
computer, and unlikely to be available for further experimentation. I'm 
trying to get another, simpler, build to operate as an alternative 
experimental vehicle, with two-off WD 512GB HDDs, and could make this 
available for trials if necessary.

                 Regards

                         Peter


On 07/05/15 22:20, Mathieu Trudel-Lapierre wrote:
> I think for this we should simply figure out a way to reproduce this
> issue in the smallest; more reduced way possible in virtual machines,
> and test it carefully.
>
> @PMOverfield; what kind of system are you using? Are there only two
> disks being mirrored, or are you using a different kind of setup?
>
> ** Changed in: grub2 (Ubuntu)
>         Status: Confirmed => Incomplete
>
> ** Changed in: grub2 (Ubuntu)
>     Importance: Undecided => Medium
>

-- 
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/1309639

Title:
  grub confused by named md raid arrays

Status in grub2 package in Ubuntu:
  Incomplete

Bug description:
  Am installing Trusty (AMD-64 Desktop), with /boot as a RAID-1 set
  (ext2fs) under mdadm on a GPT partition, with a separate, non-RAID,
  unformatted partition for BIOS-grub. At the stage of attempting to
  install GRUB it fails, reporting fatal error. I get the window
  offering the option (among others) to continue without installing GRUB
  anywhere. I select this option, but the "OK" button never becomes
  active and no further progress occurs. The installer shows signs of
  having "crashed" or "locked-up", so I cannot be confident that the
  remainder of the installation has been completed, otherwise I could
  assemble the RAID-sets at a mount-point, then chroot and complete the
  installation of GRUB that way. I know that this build isn't intended
  for RAID installations, but a clean failure would be helpful. Thank
  you.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.18.7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  Date: Fri Apr 18 17:38:08 2014
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_GB.UTF-8
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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