Added Linux-image-3.13.0-24-generic as affected package given the error in dmesg.
** Package changed: ubuntu => linux-lts-trusty (Ubuntu) ** Description changed: 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. + 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. ** Description changed: - Raid array is three identical 500GB hard drives on NVIDIA controller set - to RAID5 for a total of 1TiB (931.52GB) storage. + 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. ** Description changed: 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: + 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. ** Description changed: 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: + 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313169 Title: Ubuntu Trusty Tahr cannot boot on RAID5 array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1313169/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
