kernel-packages team mailing list archive

[Ben McCann <1210104@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu
12.04 for months. I'm using the MDADM version and not DMRAID. It has
been working fine other than a couple minor issues with clean shutdowns
that I fixed by tweaking a couple of the scripts under /etc.

I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID stopped
working, probably because auto-detection failed to see the RAID array.
Everything works fine with the previous kernel image, 3.2.0-49.

Here is /proc/mdstat with the 3.2.0-49 generic kernel image:

Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] 
md126 : active raid1 sdb[1] sdc[0]
976758784 blocks super external:/md127/0 [2/2] [UU]

md127 : inactive sdb[1](S) sdc[0](S)
6306 blocks super external:imsm

The /proc/mdstat file is empty (other than listing personalities) in
3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51,
and their partition tables look reasonable, so I don't see any issues
with 3.2.0-51 actually seeing the physical drives. The problem appears
to be that the MD driver doesn't detect the external RAID (aka 'imsm')
metadata created by Intel fakeraid.

Here's the additional data requested for new bug reports:

lsb_release -rd
Description:    Ubuntu 12.04.2 LTS
Release:        12.04

apt-cache policy linux-image-3.2.0-51-generic
linux-image-3.2.0-51-generic:
  Installed: 3.2.0-51.77
  Candidate: 3.2.0-51.77
  Version table:
 *** 3.2.0-51.77 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages
        100 /var/lib/dpkg/status

FWIW, here's the apt-cache data on the previous kernel where fakeraid
worked correctly:

apt-cache policy linux-image-3.2.0-49-generic
linux-image-3.2.0-49-generic:
  Installed: 3.2.0-49.75
  Candidate: 3.2.0-49.75
  Version table:
 *** 3.2.0-49.75 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        100 /var/lib/dpkg/status

I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've
looked at them and all I see is that 3.2.0-49 'binds' the RAID array
components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where
it starts my RAID. This is absent in 3.2.0-51.

Aug  6 06:53:46 canopus kernel: [    2.088509] md: bind<sdb>
Aug  6 06:53:46 canopus kernel: [    2.150987] md: bind<sdc>
Aug  6 06:53:46 canopus kernel: [    2.151022] md: bind<sdb>
Aug  6 06:53:46 canopus kernel: [    2.151746] md: raid1 personality registered for level 1
Aug  6 06:53:46 canopus kernel: [    2.152167] bio: create slab <bio-1> at 1
Aug  6 06:53:46 canopus kernel: [    2.152239] md/raid1:md126: active with 2 out of 2 mirrors
Aug  6 06:53:46 canopus kernel: [    2.152249] md126: detected capacity change from 0 to 1000200994816
Aug  6 06:53:46 canopus kernel: [    2.153111]  md126: p1 p2 p3 p4 < p5 p6 p7 >

Any suggestions on how to troubleshoot and/or fix this? There's no point
bisecting the kernel images given the regression has just appeared in
3.2.0-51 and, AFAIK, there was never a release of a '3.2.0-50' kernel.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete


** Tags: needs-kernel-logs needs-upstream-testing regression-release

** Attachment added: "Kernel.log from 3.2.0-49 (that works)"
   https://bugs.launchpad.net/bugs/1210104/+attachment/3764808/+files/3.2.0-49.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1210104

Title:
  Intel FakeRAID *Regression* in Kubuntu 12.04 with Linux 3.2.0-51

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I have been using Intel FakeRAID on an Asus Z77 motherboard on Kubuntu
  12.04 for months. I'm using the MDADM version and not DMRAID. It has
  been working fine other than a couple minor issues with clean
  shutdowns that I fixed by tweaking a couple of the scripts under /etc.

  I upgraded to the latest Linux kernel (3.2.0-51) and my FakeRAID
  stopped working, probably because auto-detection failed to see the
  RAID array. Everything works fine with the previous kernel image,
  3.2.0-49.

  Here is /proc/mdstat with the 3.2.0-49 generic kernel image:

  Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] 
  md126 : active raid1 sdb[1] sdc[0]
  976758784 blocks super external:/md127/0 [2/2] [UU]

  md127 : inactive sdb[1](S) sdc[0](S)
  6306 blocks super external:imsm

  The /proc/mdstat file is empty (other than listing personalities) in
  3.2.0-51. Note that the sdb and sdc drives are recognized by 3.2.0-51,
  and their partition tables look reasonable, so I don't see any issues
  with 3.2.0-51 actually seeing the physical drives. The problem appears
  to be that the MD driver doesn't detect the external RAID (aka 'imsm')
  metadata created by Intel fakeraid.

  Here's the additional data requested for new bug reports:

  lsb_release -rd
  Description:    Ubuntu 12.04.2 LTS
  Release:        12.04

  apt-cache policy linux-image-3.2.0-51-generic
  linux-image-3.2.0-51-generic:
    Installed: 3.2.0-51.77
    Candidate: 3.2.0-51.77
    Version table:
   *** 3.2.0-51.77 0
          500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
          500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages
          100 /var/lib/dpkg/status

  FWIW, here's the apt-cache data on the previous kernel where fakeraid
  worked correctly:

  apt-cache policy linux-image-3.2.0-49-generic
  linux-image-3.2.0-49-generic:
    Installed: 3.2.0-49.75
    Candidate: 3.2.0-49.75
    Version table:
   *** 3.2.0-49.75 0
          500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
          100 /var/lib/dpkg/status

  I will attach the kernel.log for booting 3.2.0-49 and 3.2.0-51. I've
  looked at them and all I see is that 3.2.0-49 'binds' the RAID array
  components and 3.2.0-51 doesn't. Here's a snippet from 3.2.0-49 where
  it starts my RAID. This is absent in 3.2.0-51.

  Aug  6 06:53:46 canopus kernel: [    2.088509] md: bind<sdb>
  Aug  6 06:53:46 canopus kernel: [    2.150987] md: bind<sdc>
  Aug  6 06:53:46 canopus kernel: [    2.151022] md: bind<sdb>
  Aug  6 06:53:46 canopus kernel: [    2.151746] md: raid1 personality registered for level 1
  Aug  6 06:53:46 canopus kernel: [    2.152167] bio: create slab <bio-1> at 1
  Aug  6 06:53:46 canopus kernel: [    2.152239] md/raid1:md126: active with 2 out of 2 mirrors
  Aug  6 06:53:46 canopus kernel: [    2.152249] md126: detected capacity change from 0 to 1000200994816
  Aug  6 06:53:46 canopus kernel: [    2.153111]  md126: p1 p2 p3 p4 < p5 p6 p7 >

  Any suggestions on how to troubleshoot and/or fix this? There's no
  point bisecting the kernel images given the regression has just
  appeared in 3.2.0-51 and, AFAIK, there was never a release of a
  '3.2.0-50' kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210104/+subscriptions