Activity log for bug #1313169

Date Who What changed Old value New value Message
2014-04-26 18:36:46 David Lee bug added bug
2014-04-26 19:58:26 Ubuntu Foundations Team Bug Bot tags bot-comment
2014-04-26 20:24:10 David Lee affects ubuntu linux-lts-trusty (Ubuntu)
2014-04-26 20:26:36 David Lee description Raid array is three identical 500GB hard drives on 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), 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. However, upon reboot, 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. Raid array is three identical 500GB hard drives on 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. However, upon reboot, 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.
2014-04-26 20:29:10 David Lee description Raid array is three identical 500GB hard drives on 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. However, upon reboot, 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. 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. However, upon reboot, 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.
2014-04-26 20:32:22 David Lee 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. However, upon reboot, 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. 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. 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.
2014-04-26 20:33:10 David Lee 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. 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. 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.
2014-04-28 14:57:01 Brian Murray affects linux-lts-trusty (Ubuntu) linux (Ubuntu)
2014-04-28 15:00:18 Brad Figg linux (Ubuntu): status New Incomplete
2014-04-28 15:00:21 Brad Figg tags bot-comment bot-comment trusty
2014-04-29 02:17:38 David Lee linux (Ubuntu): status Incomplete Confirmed
2014-04-30 20:32:18 Joseph Salisbury linux (Ubuntu): importance Undecided High
2014-04-30 20:33:23 Joseph Salisbury bug task added initramfs-tools (Ubuntu)
2014-06-13 19:56:33 Joseph Salisbury linux (Ubuntu): status Confirmed Incomplete
2014-06-13 19:56:36 Joseph Salisbury tags bot-comment trusty bot-comment kernel-request-3.13.0-24.46 trusty
2014-09-07 23:39:12 Launchpad Janitor initramfs-tools (Ubuntu): status New Confirmed
2017-10-31 14:53:39 Phillip Susi marked as duplicate 1683105