touch-packages team mailing list archive

["John B. Anderson" <johnbanderson@xxxxxxxxx>]

Having just attempted an upgrade to Tahr, I can confirm that the fix is
NOT in place for linux-image-3.13.0-35-generic.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1313169

Title:
  Ubuntu Trusty Tahr cannot boot on RAID5 array

Status in “initramfs-tools” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Raid array is three identical Western Digital Green series 500GB hard
  drives on an NVIDIA controller set to RAID5 for a total of 1TiB
  (931.52GB) storage.

  Installation was done using the Ubuntu LiveCD.

  Partitions on the filesystem was created beforehand using gparted. The
  partition table is set up to be GPT with a 8MB bios_grub partition, a
  256MB fat32 EFIBoot partition (not used for this setup, board does not
  support EFI and is expected to boot from the bios_grub legacy
  partition), a 4GB swap, 80GB root partition, and the rest for /home.
  Then  the installer is invoked and the partitions are set up. GRUB is
  told to install to the root of the RAID array in /dev/mapper . The
  installation went flawlessly.

  Upon reboot, GRUB loads as expected, and loads the kernel and initrd
  as expected. However, the kernel gives up on waiting for the root
  partition and drops to initramfs busybox. "dmesg|grep device" shows
  the following errors:

  device-mapper: table: 252:0: raid: unknown target type
  device-mapper: ioctl: error adding target to table

  Trying to invoke dmraid -a y results in the following error:
  ERROR: device-mapper target type "raid" is not in the kernel
  RAID set "nvidia_babddecf" was not activated.

  nvidia_babddecf is the assigned volume name by the controller.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1313169/+subscriptions