md fails during install [kernel BUG at /build/buildd/linux-3.2.0/drivers/md/md.c:6920!]; RIP: 0010:[<ffffffff814e7eec>] [<ffffffff814e7eec>] md_write_start+0x1c/0x20

High -> Bug in essential component (md)

From the attached dmesg:

[ 156.969800] md/raid1:md126: active with 2 out of 2 mirrors
[ 156.969813] md126: detected capacity change from 0 to 500104691712
[ 156.970535] md126: unknown partition table
[ 157.034071] md: md0 stopped.
[ 157.034963] md: bind<sdc1>
[ 157.035336] md: bind<sdd1>
[ 157.036078] md/raid1:md0: active with 2 out of 2 mirrors
[ 157.036093] md0: detected capacity change from 0 to 1000202174464
[ 157.037434] md0: unknown partition table
[ 159.001714] ------------[ cut here ]------------
[ 159.001717] kernel BUG at /build/buildd/linux-3.2.0/drivers/md/md.c:6920!
[ 159.001719] invalid opcode: 0000 [#1] SMP
[ 159.001720] CPU 0
[ 159.001721] Modules linked in: raid1 xfs reiserfs jfs btrfs zlib_deflate libcrc32c ntfs vfat fat ext2 e1000e mpt2sas scsi_transport_sas raid_class nls_utf8 isofs vesafb usb_storage usbhid hid
[ 159.001731]
[ 159.001733] Pid: 14365, comm: parted_devices Not tainted 3.2.0-20-generic #33-Ubuntu Supermicro X9SCL/X9SCM/X9SCL/X9SCM
[ 159.001736] RIP: 0010:[<ffffffff814e7eec>] [<ffffffff814e7eec>] md_write_start+0x1c/0x20
[ 159.001742] RSP: 0018:ffff880417edfcb8 EFLAGS: 00010246
[ 159.001743] RAX: 0000000000000010 RBX: 0000000000000001 RCX: 0000000000000001
[ 159.001744] RDX: 0000000000000000 RSI: ffff880417e430c0 RDI: ffff88042179fc00
[ 159.001746] RBP: ffff880417edfcb8 R08: 0000000000000246 R09: 0000000000000077
[ 159.001747] R10: 0000000000000000 R11: 0000000000000000 R12: ffff880417e430c0
[ 159.001748] R13: 0000000000000000 R14: ffff88041accc840 R15: 0000000000000800
[ 159.001750] FS: 00007f1a3af4e740(0000) GS:ffff88043fc00000(0000) knlGS:0000000000000000
[ 159.001751] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 159.001752] CR2: 0000000001d6f098 CR3: 0000000419772000 CR4: 00000000000406f0
[ 159.001754] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 159.001755] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 159.001757] Process parted_devices (pid: 14365, threadinfo ffff880417ede000, task ffff880417c1c4d0)
[ 159.001758] Stack:
[ 159.001759] ffff880417edfda8 ffffffffa01a6eaa 0000000000000000 0000000000000000
[ 159.001762] ffff880417edfce8 ffffffff8105fae2 ffff880417edfd08 0000000000000010
[ 159.001764] ffff880417edfd18 ffffffff81300936 ffff880417e430c0 ffff880417e430c0
[ 159.001767] Call Trace:
[ 159.001771] [<ffffffffa01a6eaa>] make_request+0x4a/0xa60 [raid1]
[ 159.001775] [<ffffffff8105fae2>] ? default_wake_function+0x12/0x20
[ 159.001777] [<ffffffff81300936>] ? throtl_find_tg+0x46/0x60
[ 159.001779] [<ffffffff81301b20>] ? blk_throtl_bio+0x1c0/0x4e0
[ 159.001782] [<ffffffff8104dec3>] ? __wake_up+0x53/0x70
[ 159.001784] [<ffffffff814e1fd0>] md_make_request+0xd0/0x200
[ 159.001788] [<ffffffff8111a035>] ? mempool_alloc_slab+0x15/0x20
[ 159.001791] [<ffffffff812efb24>] generic_make_request.part.50+0x74/0xb0
[ 159.001793] [<ffffffff812eff38>] generic_make_request+0x68/0x70
[ 159.001795] [<ffffffff812effc5>] submit_bio+0x85/0x110
[ 159.001798] [<ffffffff811adf3a>] ? bio_alloc_bioset+0x5a/0xf0
[ 159.001800] ...

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 972960

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

I walked the reporter through this bug on #ubuntu+1 - it's during install (seems to be triggered by parted); the dmesg with the full oops is attached.

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.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. 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.

Note bug was only triggerable on the installer, so can't just try upgrading.

(Atarutin: If you can still trigger this then it might be worth trying the daily install CD).

I believe this is ultimately a bug in the upstream kernel that is triggered by mdadm activating an intel matrix raid, and the Ubuntu mdadm package is missing the mdmon daemon required to support this.

We are getting this same error and just tried the latest daily 12.04.1 LTS CD install from July 27, 2012 with what appeared to be the same error.

I do not think that the latest 12.04.01 CD has the new mdadm yet, see related bug #972960

Atarutin, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in Oneiric from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

Dave,

I can no longer reproduce the setup for this bug.
It was narrowed down to md trying to "wrap" the "fake-ide" controllers
(thanks #ubuntu and #ubuntu+1). I was able to install when I disabled RAID
function on the motherboard.
What was noticeable is that you can enable the RAID function after the
installation (unless you are trying to install onto a software RAID root
partition which was my case). So only the installer is affected.

Thank you,

AT.

On Wed, Aug 1, 2012 at 6:54 PM, Christopher M. Penalver <
<email address hidden>> wrote:

> Atarutin, this bug was reported a while ago and there hasn't been any
> activity in it recently. We were wondering if this is still an issue? If
> so, could you please test for this with the latest development release
> of Ubuntu? ISO CD images are available from
> http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you please run the following command in
> Oneiric from a Terminal (Applications->Accessories->Terminal), as it
> will automatically gather and attach updated debug information to this
> report:
>
> apport-collect -p linux <replace-with-bug-number>
>
> Please let us know your results. Thank you for your understanding.
>
> Helpful Bug Reporting Links:
> https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
>
> https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
>
> https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
>
> https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug
>
> ** Tags removed: kernel-request-3.2.0-22.35
>
> ** Tags added: regression-release
>
> ** Summary changed:
>
> - md fails during install [kernel BUG at
> /build/buildd/linux-3.2.0/drivers/md/md.c:6920!]
> + md fails during install [kernel BUG at
> /build/buildd/linux-3.2.0/drivers/md/md.c:6920!]; RIP:
> 0010:[<ffffffff814e7eec>] [<ffffffff814e7eec>] md_write_start+0x1c/0x20
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/972960
>
> Title:
> md fails during install [kernel BUG at
> /build/buildd/linux-3.2.0/drivers/md/md.c:6920!]; RIP:
> 0010:[<ffffffff814e7eec>] [<ffffffff814e7eec>]
> md_write_start+0x1c/0x20
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> Whenever I try to install ubuntu-12.04, no LVs show up in the
> installer seemingly from the errors in md. See the attached dmesg.
>
> Interstingly, if I upgrade from 11.10 it all works just fine.
>
> Thank you,
>
> AT.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972960/+subscriptions
>

--
AT.

tommy-odom (or anyone else who was experiencing this) - can you try reproducing this on a 12.10 install cd ?

Sorry, the server that I ran into this on went into production use this week so I can't really do any tests on it anymore.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]