← Back to team overview

kernel-packages team mailing list archive

[Bug 1313169] Re: Ubuntu Trusty Tahr cannot boot on RAID5 array


Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm
if this bug is still present. Please test again with the newer kernel
and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the
following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to
Confirmed. If the bug no longer exists, change the bug status from
Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add
a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

** Tags added: kernel-request-3.13.0-24.46

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Ubuntu Trusty Tahr cannot boot on RAID5 array

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

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: