After update to kernel 3.2, from 3.0, can't boot from raid

Bug #936679 reported by XtremXpert
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux-kernel-di-amd64-2.6 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Using update-manager -d to upgrade my 11.10 to 12.04, the kernel fail to busybox initramfs. In the busybox, I can't see my raid drive. Using kernel 3.0 instead of 3.2 give the same error, but it was working before upgrade to 3.2. Using the old 2.6 kernel from 11.04 bring me to a workable environement, so the issue is probably around the kernel or the dm-raid45 module.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-kernel-di-amd64-2.6 (Ubuntu):
status: New → Confirmed
Revision history for this message
Menno (q-menno) wrote :

Upgraded from 10.4 LTS to 12.04LTS; kernels versions 2.6 to 3.2. System has two 1T disks in RAID1, boots from RAID volume. This setup worked perfectly. After upgrade, system won't boot, defaults to busybox/initramfs; mentioning a faild RAID system. Option to continue with degraded RAID is presented but does not work. Booting with (old) 2.6 kernel results in stable 12.04 system. Checked RAID, is fully stable, bothe disks are complete mirror images.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.