mdadm crash while examining a disk

Bug #1440474 reported by SKAL
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
New
Undecided
Unassigned

Bug Description

HI all,
I was trying to add a disk which was part of a raid 1 set.

This is what I get.

$ sudo mdadm --examine /dev/sdi2
/dev/sdi2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 152e0bd3:f8bbf60a:521072fd:34d85697
  Creation Time : Mon Nov 4 07:46:01 2013
     Raid Level : raid1
  Used Dev Size : 1951401408 (1861.00 GiB 1998.24 GB)
     Array Size : 1951401408 (1861.00 GiB 1998.24 GB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 127

    Update Time : Tue Dec 9 10:29:32 2059
          State : active
 Active Devices : 90
Working Devices : 0
 Failed Devices : 0
  Spare Devices : 355339219
       Checksum : 527742a9 - expected d3b3e016
         Events : 8381205228728352769

      Number Major Minor RaidDevice State
this 0 0 0 0 spare

   0 -1456779524 0 90 0 spare
   1 -1456779524 0 90 0 spare
   2 -1456779524 0 90 0 spare
   3 -1456779524 0 90 0 spare
   4 0 0 0 0 spare
   5 0 0 0 0 spare
   6 0 0 0 0 spare
   7 0 0 0 0 spare
   8 0 0 0 0 spare
   9 0 0 0 0 spare
  10 0 0 0 0 spare
  11 0 0 0 0 spare
  12 0 0 0 0 spare
  13 0 0 0 0 spare
  14 0 0 0 0 spare
  15 0 0 0 0 spare
  16 0 0 0 0 spare
  17 0 0 0 0 spare
  18 0 0 0 0 spare
  19 0 0 0 0 spare
  20 0 0 0 0 spare
  21 0 0 0 0 spare
  22 0 0 0 0 spare
  23 0 0 0 0 spare
  24 0 0 0 0 spare
  25 0 0 0 0 spare
  26 0 0 0 0 spare
  27 0 0 0 0 spare
  28 0 0 0 0 spare
  29 0 0 0 0 spare
  30 0 0 0 0 spare
  31 0 0 0 0 spare
  32 0 0 114177 0 spare
  33 0 0 0 0 spare
  34 0 0 0 0 spare
  35 0 0 0 0 spare
  36 0 0 0 0 spare
  37 0 0 0 0 spare
  38 0 0 0 0 spare
  39 0 0 0 0 spare
  40 0 0 0 0 spare
  41 0 0 0 0 spare
  42 0 0 0 0 spare
  43 0 0 0 0 spare
  44 0 0 0 0 spare
  45 0 0 0 0 spare
  46 0 0 0 0 spare
  47 0 0 0 0 spare
  48 0 0 0 0 spare
  49 0 0 0 0 spare
  50 0 0 0 0 spare
  51 0 0 0 0 spare
  52 0 0 0 0 spare
  53 0 0 0 0 spare
  54 0 0 0 0 spare
  55 0 0 0 0 spare
  56 0 0 0 0 spare
  57 0 0 0 0 spare
  58 0 0 0 0 spare
  59 0 0 0 0 spare
*** Error in `mdadm': corrupted double-linked list: 0x0000000000c96000 ***
  60 0 0 69777 0 removed write-mostly

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1440474/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
SKAL (sir-kalot) wrote :

Some more info about my system.

mdadm 3.3-2ubuntu1 amd64

uname -a
Linux Server 3.16.0-34-generic #45-Ubuntu SMP Mon Mar 23 17:21:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

---------------
data more related to this problem.

$ sudo mdadm -A -R /dev/md9 /dev/sdi2
mdadm: device 0 in /dev/md9 has wrong state in superblock, but /dev/sdi2 seems ok
mdadm: failed to add /dev/sdi2 to /dev/md9: Invalid argument
mdadm: failed to RUN_ARRAY /dev/md9: Invalid argument
mdadm: Not enough devices to start the array.

sudo mount /dev/sdi2 /mnt/Raid1/
mount: unknown filesystem type 'linux_raid_member'

affects: ubuntu → mdadm (Ubuntu)
Revision history for this message
SKAL (sir-kalot) wrote :

Is there any chance to have some kind of answare about it? :'-(

tags: added: utopic
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.