Problem with IMSM Raid

Bug #1030333 reported by inode77 on 2012-07-28
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Medium
Unassigned
Precise
Medium
Unassigned
Quantal
Medium
Unassigned

Bug Description

I use two 2TB Enterprise WD Disks on a Intel Server Board SK1200KP with E3-1220L CPU.

I created a container array for IMSM metadata.
mdadm --create --verbose /dev/md/0 /dev/sd[c-d] --raid-devices 2 --metadata imsm

Then I created an array based on the imsm container.
mdadm --create /dev/md/1 /dev/md/0 --raid-devices 2 --level 1 -c 128 -z $((1836*1024*1024))

Then I tried to access /dev/md1 using parted and the kernel panic occured.
...
[ 150.883146] md/raid1:md1: not clean -- starting background reconstruction
[ 150.883150] md/raid1:md1: active with 2 out of 2 mirrors
[ 150.883181] md1: detected capacity change from 0 to 1971389988864
[ 150.885868] md1: unknown partition table
[ 211.123566] ------------[ cut here ]------------
[ 211.123582] kernel BUG at /build/buildd/linux-3.2.0/drivers/md/md.c:6923!
[ 211.123592] invalid opcode: 0000 [#1] SMP
[ 211.123602] CPU 1
[ 211.123607] Modules linked in: snd_hda_codec_hdmi joydev hid_logitech ff_memless bridge stp usbhid nouveau hid psmouse ttm serio_raw drm_kms_helper drm snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc i2c_algo_bit mxm_wmi wmi video mei(C) mac_hid lp parport raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx e1000e raid1 raid0 multipath linear
[ 211.123741]
[ 211.123747] Pid: 1724, comm: parted Tainted: G C 3.2.0-27-generic #43-Ubuntu /S1200KP
...

# mdadm --detail-platform
       Platform : Intel(R) Matrix Storage Manager
        Version : 11.1.0.1413
    RAID Levels : raid0 raid1 raid10 raid5
    Chunk Sizes : 4k 8k 16k 32k 64k 128k
      Max Disks : 6
    Max Volumes : 2
 I/O Controller : /sys/devices/pci0000:00/0000:00:1f.2 (SATA)
          Port0 : /dev/sda (EL125500W6******)
          Port1 : /dev/sdb (J8400076******)
          Port2 : /dev/sdc (WD-WCAVY7******)
          Port3 : /dev/sdd (WD-WCAVY7******)
          Port4 : - no device attached -
          Port5 : - no device attached -

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-27-generic 3.2.0-27.43
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D2', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D9p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Sat Jul 28 18:05:02 2012
HibernationDevice: RESUME=UUID=a0c53194-877d-46b4-8c91-bd964e679cb9
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 003: ID 046d:c50c Logitech, Inc. Cordless Desktop S510
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=rxvt
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-27-generic root=UUID=a6f09155-f838-44fd-b8db-b30c630649db ro
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-27-generic N/A
 linux-backports-modules-3.2.0-27-generic N/A
 linux-firmware 1.79
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/18/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KPC2060H.86B.0022.2012.0518.1049
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: S1200KP
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG34877-102
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrKPC2060H.86B.0022.2012.0518.1049:bd05/18/2012:svn:pn:pvr:rvnIntelCorporation:rnS1200KP:rvrAAG34877-102:cvn:ct3:cvr:

inode77 (simon-gerber) wrote :
Dimitri John Ledkov (xnox) wrote :

Thank you for testing this. I will try to look into this.

Dimitri John Ledkov (xnox) wrote :

After creating the container does `mdadm --assemble --scan` show anything useful?

As an experiment, do you have options to setup ISMS Raid devices in the ROM (BIOS/UEFI boot screens) and then boot into ubuntu and see if `mdadm --details --scan` changes / makes the containers useful?

Changed in mdadm (Ubuntu):
status: New → Confirmed
inode77 (simon-gerber) wrote :

I tried it, rebooted once more and created the raidset using Intel OROM (CTRL+I).
Afterwards there are still two seperate disks visible and they cannot be assembled using mdadm.

After recreating container and array the array it stays like this:
# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active (read-only) raid1 sdd[1] sdc[0]
      1925185536 blocks super external:/md0/0 [2/2] [UU]
       resync=PENDING

md0 : inactive sdd[1](S) sdc[0](S)
      2210 blocks super external:imsm

unused devices: <none>

Trying to write to the generated /dev/md1 using sfdisk and parted leads to the reported kernel bug.

Changed in mdadm (Ubuntu Precise):
status: New → Confirmed
Dimitri John Ledkov (xnox) wrote :

What is the package version of mdadm? E.g. $ dpkg -l mdadm
Are you using precise or quantal?
If you are using precise, can you try mdadm from precise-proposed?

Changed in mdadm (Ubuntu Precise):
status: Confirmed → Incomplete
Changed in mdadm (Ubuntu Quantal):
status: Confirmed → Incomplete
Changed in mdadm (Ubuntu Precise):
importance: Undecided → Medium
Changed in mdadm (Ubuntu Quantal):
importance: Undecided → Medium
zzeroo (co) wrote :

Same behavior on Debian Wheezy testing.

dmesg shows "invalide opcode: 0000 [#] SMP ..."

Launchpad Janitor (janitor) wrote :

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

Changed in mdadm (Ubuntu Precise):
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

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

Changed in mdadm (Ubuntu):
status: Incomplete → Expired
Launchpad Janitor (janitor) wrote :

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

Changed in mdadm (Ubuntu Quantal):
status: Incomplete → Expired
Changed in mdadm (Ubuntu):
status: Expired → Confirmed
inode77 (simon-gerber) wrote :

I tested again with 12.10 (updated BIOS to last version available.

       Platform : Intel(R) Matrix Storage Manager
        Version : 11.2.0.1527
    RAID Levels : raid0 raid1 raid10 raid5
    Chunk Sizes : 4k 8k 16k 32k 64k 128k
    Max Disks : 6
    Max Volumes per array : 2
    Max Volumes per controller: 4
    2TB Volumes: supported
      2TB Disks: supported
 I/O Controller : /sys/devices/pci0000:00/0000:00:1f.2 (SATA)
          Port2 : /dev/sdc (WD-WCAVY7369087)
          Port1 : /dev/sdb (EL125500W6120CGN)
          Port0 : /dev/sda (WD-WMC1T1652582)
          Port3 : /dev/sdd (WD-WCAVY7369135)
          Port4 : - no device attached -
          Port5 : - no device attached -

RAID can be assembled using the imsm conatiner, BUT it does not get resammbled automaticaly upon boot and is considered degraded and has to be rebuild, thus is not usable right now.

There's support coming into debian for IMSM Raid on installer level, maybe useable in ubuntu too.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699430

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

Other bug subscribers

Remote bug watches

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