Bug#694513: mdadm splits drives into two arrays with identical UUIDs, starts one

Moshe Yudkowsky speech at pobox.com
Tue Nov 27 03:12:25 UTC 2012


Package: mdadm
Version: 3.2.5-3
Severity: normal

I've just managed to figure out -- I think -- the problem I've been having, but what I saw was very odd indeed. As far as I can tell, the members of my raid5 drives split into two different md drives, each with the same UUID, and of course this resulted in odd behavior.

Here's the informaion I collected.

First, the basic information from /proc/mdstat at the time of the problem:

Personalities : [raid1] [raid6] [raid5] [raid4] 
md_d122 : active raid1 sda2[0] sdc2[2] sdd2[3]
      498004 blocks super 1.0 [3/3] [UUU]
      
md_d123 : active raid1 sdc4[2]
      4506224 blocks super 1.0 [3/1] [__U]
      
md_d124 : inactive sdc3[4](S) sdb3[1](S)
      958742984 blocks super 1.0
       
md_d125 : active raid1 sdb2[1]
      498004 blocks super 1.0 [3/1] [_U_]
      
md_d126 : active raid1 sda4[0] sdd4[3]
      4506224 blocks super 1.0 [3/2] [UU_]
      
md_d127 : active raid5 sda3[0] sdd3[3]
      958742784 blocks super 1.0 level 5, 64k chunk, algorithm 2 [3/2] [UU_]


Cleary, something has gone very wrong here with one of the drives, and the challenge is to figure out what it is. I'll start with /dev/md_d127. The hard part for mdadm (for me, at least) is figuring out what drive is part of which array when all I have  is a list of drive names.

# mdadm --query --detail /dev/md_d127
/dev/md_d127:
        Version : 1.0
  Creation Time : Wed Jan 30 17:27:51 2008
     Raid Level : raid5
     Array Size : 958742784 (914.33 GiB 981.75 GB)
  Used Dev Size : 479371392 (457.16 GiB 490.88 GB)
   Raid Devices : 3
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Mon Nov 26 20:20:05 2012
          State : active, degraded 
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric/dev/md_d124
     Chunk Size : 64K

           Name : newbagpipes:base
           UUID : 959fc2b3:8a86d38c:45e4afda:6695f914
         Events : 23058326

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       3       8       51        1      active sync   /dev/sdd3
       2       0        0        2      removed

"active, degraded" and working with 2 devices. There's no spare according to this. /dev/sd[abcd]3 are all supposed to be part of this drive, so let's check each of them:


# mdadm --examine  /dev/sda3
/dev/sda3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 959fc2b3:8a86d38c:45e4afda:6695f914
           Name : newbagpipes:base
  Creation Time : Wed Jan 30 17:27:51 2008
     Raid Level : raid5
   Raid Devices : 3

 Avail Dev Size : 958742984 (457.16 GiB 490.88 GB)
     Array Size : 958742784 (914.33 GiB 981.75 GB)
  Used Dev Size : 958742784 (457.16 GiB 490.88 GB)
   Super Offset : 958743112 sectors
          State : clean
    Device UUID : 6e778f9e:4610a884:7cb6105c:9955cdd2

    Update Time : Mon Nov 26 20:22:06 2012
       Checksum : dc74df6c - correct
         Events : 23058387

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 0
   Array State : AA. ('A' == active, '.' == missing)

"clean" and "active device 0." That's fine.

Let's go to the next known active device as listed in /proc/mdstat, /dev/sdd3:

# mdadm --examine  /dev/sdd3
/dev/sdd3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 959fc2b3:8a86d38c:45e4afda:6695f914
           Name : newbagpipes:base
  Creation Time : Wed Jan 30 17:27:51 2008
     Raid Level : raid5
   Raid Devices : 3

 Avail Dev Size : 958742856 (457.16 GiB 490.88 GB)
     Array Size : 958742784 (914.33 GiB 981.75 GB)
  Used Dev Size : 958742784 (457.16 GiB 490.88 GB)
   Super Offset : 958743112 sectors
          State : clean
    Device UUID : c111211a:f3030bea:e7ebfae3:17c508ea

    Update Time : Mon Nov 26 20:24:47 2012
       Checksum : 5c8f12d0 - correct
         Events : 23058473

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 1
   Array State : AA. ('A' == active, '.' == missing)


Clean and active, device 1.

Now let's look at what should the failed drive (based on my memory of how I built this):

# mdadm --examine  /dev/sdc3
/dev/sdc3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 959fc2b3:8a86d38c:45e4afda:6695f914
           Name : newbagpipes:base
  Creation Time : Wed Jan 30 17:27:51 2008
     Raid Level : raid5
   Raid Devices : 3

 Avail Dev Size : 958742984 (457.16 GiB 490.88 GB)
     Array Size : 958742784 (914.33 GiB 981.75 GB)
  Used Dev Size : 958742784 (457.16 GiB 490.88 GB)
   Super Offset : 958743112 sectors
          State : active
    Device UUID : 52ce655b:e70059a0:89d70e89:e64edcbf

    Update Time : Tue Apr 17 12:37:05 2012
       Checksum : cd216719 - correct
         Events : 10426614

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 2
   Array State : AAA ('A' == active, '.' == missing)

This is device 2 in the array of 3, as seen above in /proc/mdstat, for this array. However, it's not only listed as "active," I see that the array has all three devices active according to the last line - that makes no sense to me.

What I believe I see here is an inconsistency between /proc/mdstat and what mdadm tells me.

When I go to what I thought was the spare, /dev/sdb3, I see this:

# mdadm --examine  /dev/sdb3
/dev/sdb3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 959fc2b3:8a86d38c:45e4afda:6695f914
           Name : newbagpipes:base
  Creation Time : Wed Jan 30 17:27:51 2008
     Raid Level : raid5
   Raid Devices : 3

 Avail Dev Size : 958742984 (457.16 GiB 490.88 GB)
     Array Size : 958742784 (914.33 GiB 981.75 GB)
  Used Dev Size : 958742784 (457.16 GiB 490.88 GB)
   Super Offset : 958743112 sectors
          State : clean
    Device UUID : 09bbd456:8ad89a6f:0652e20e:ecbe43e7

    Update Time : Sun May  1 17:48:15 2011
       Checksum : 433dd706 - correct
         Events : 10420043

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 1
   Array State : AAA ('A' == active, '.' == missing)

So this drive is also "clean" and "active," and the Array state is AAA. Active device 1 in the same array as /dev/sdd3? /dev/sdb3 is shown as a spare in a different array, /dev/md_d124.

To get further down a bit, here's my /etc/mdadm/mdadm.conf:

# cat /etc/mdadm/mdadm.conf 
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=part10 metadata=1.0

# automatically tag new arrays as belonging to the local system
# HOMEHOST <system>
# Ignore homehost to get proper array names 20091110
# solution until we rebuild metadata
HOMEHOST <ignore>

# instruct the monitoring daemon where to send mail alerts
MAILADDR moshe

# This file was auto-generated on Sun, 27 Jan 2008 12:35:08 -0600
# by mkconf $Id: mkconf 261 2006-11-09 13:32:35Z madduck $

# last line added manually, 20080128
ARRAY /dev/md/base auto=part10 level=raid5 num-devices=3 spares=1 name=newbagpipes:base UUID=959fc2b3:8a86d38c:45e4afda:6695f914
#ARRAY /dev/md_d127 auto=part10 level=raid5 num-devices=3 spares=1 name=newbagpipes:base UUID=959fc2b3:8a86d38c:45e4afda:6695f914
ARRAY /dev/md/root auto=part3 level=raid1 num-devices=3 spares=1 name=newbagpipes:root UUID=14ae485f:60ca6705:8558a43a:958b6e38
#ARRAY /dev/md_d126 auto=part3 level=raid1 num-devices=3 spares=1 name=newbagpipes:root UUID=14ae485f:60ca6705:8558a43a:958b6e38
ARRAY /dev/md/boot auto=part3 level=raid1 num-devices=3 spares=1 name=newbagpipes:boot UUID=d00f020f:0fcfe10c:d7f06b15:ed4f7cb1
#ARRAY /dev/md_d125 auto=part3 level=raid1 num-devices=3 spares=1 name=newbagpipes:boot UUID=d00f020f:0fcfe10c:d7f06b15:ed4f7cb1


In other words, there is no /dev/md_d124 to the best of my knowledge.

I interpret this to mean that the devices /dev/sdb3 and /dev/sdc3 have formed their own array with the same UUID, even though there's no such config item. I don't quite see how that's possible.


When I try to get info on /dev/md_d124, I get:

# mdadm --detail  /dev/md_d124
mdadm: md device /dev/md_d124 does not appear to be active.

At this point I realized that I had two drives with the same UUIDs. My guess was that somehow the drives had managed to split apart, and what I needed was to put the drives back into /md/md_p127:

# mdadm --stop  /dev/md_d124
# mdadm --manage /dev/md_d127 --add /dev/sdc3
# mdadm --manage /dev/md_d127 --add /dev/sdb3


This worked. At present,

# cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4] 
md_d122 : active raid1 sda2[0] sdc2[2] sdd2[3]
      498004 blocks super 1.0 [3/3] [UUU]
      
md_d123 : active raid1 sdc4[2]
      4506224 blocks super 1.0 [3/1] [__U]
      
md_d125 : active raid1 sdb2[1]
      498004 blocks super 1.0 [3/1] [_U_]
      
md_d126 : active raid1 sda4[0] sdd4[3]
      4506224 blocks super 1.0 [3/2] [UU_]
      
md_d127 : active raid5 sdb3[5](S) sdc3[4] sda3[0] sdd3[3]
      958742784 blocks super 1.0 level 5, 64k chunk, algorithm 2 [3/2] [UU_]
      [=>...................]  recovery =  5.0% (24113024/479371392) finish=211.4min speed=35888K/sec

and the drives are in place.


# mdadm --query --detail /dev/md_d127
/dev/md_d127:
        Version : 1.0
  Creation Time : Wed Jan 30 17:27:51 2008
     Raid Level : raid5
     Array Size : 958742784 (914.33 GiB 981.75 GB)
  Used Dev Size : 479371392 (457.16 GiB 490.88 GB)
   Raid Devices : 3
  Total Devices : 4
    Persistence : Superblock is persistent

    Update Time : Mon Nov 26 20:57:44 2012
          State : clean, degraded, recovering 
 Active Devices : 2
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 2

         Layout : left-symmetric
     Chunk Size : 64K

 Rebuild Status : 5% complete

           Name : newbagpipes:base
           UUID : 959fc2b3:8a86d38c:45e4afda:6695f914
         Events : 23059718

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       3       8       51        1      active sync   /dev/sdd3
       4       8       35        2      spare rebuilding   /dev/sdc3

       5       8       19        -      spare   /dev/sdb3

       
I'm about to repeat this process for the other drives that are having trouble. I'll bet a nickel that they've got the same problem in some way.


I don't know if this is a bug or if this is a bad configuration on my part, but I have been running with this configuration for several years (2008 according to my last change) so I suspect this split happened as a result of a bug or a failure to properly update the mdadm.conf file for a new version (a different sort of bug).




-- Package-specific info:
--- mdadm.conf
DEVICE partitions
CREATE owner=root group=disk mode=0660 auto=part10 metadata=1.0
HOMEHOST <ignore>
MAILADDR moshe
ARRAY /dev/md/base auto=part10 level=raid5 num-devices=3 spares=1 name=newbagpipes:base UUID=959fc2b3:8a86d38c:45e4afda:6695f914
ARRAY /dev/md/root auto=part3 level=raid1 num-devices=3 spares=1 name=newbagpipes:root UUID=14ae485f:60ca6705:8558a43a:958b6e38
ARRAY /dev/md/boot auto=part3 level=raid1 num-devices=3 spares=1 name=newbagpipes:boot UUID=d00f020f:0fcfe10c:d7f06b15:ed4f7cb1

--- /etc/default/mdadm
INITRDSTART='all'
AUTOSTART=true
AUTOCHECK=true
START_DAEMON=true
DAEMON_OPTIONS="--syslog"
VERBOSE=false

--- /proc/mdstat:
Personalities : [raid1] [raid6] [raid5] [raid4] 
md_d122 : active raid1 sda2[0] sdc2[2] sdd2[3]
      498004 blocks super 1.0 [3/3] [UUU]
      
md_d123 : active raid1 sdc4[2]
      4506224 blocks super 1.0 [3/1] [__U]
      
md_d125 : active raid1 sdb2[1]
      498004 blocks super 1.0 [3/1] [_U_]
      
md_d126 : active raid1 sda4[0] sdd4[3]
      4506224 blocks super 1.0 [3/2] [UU_]
      
md_d127 : active raid5 sdb3[5](S) sdc3[4] sda3[0] sdd3[3]
      958742784 blocks super 1.0 level 5, 64k chunk, algorithm 2 [3/2] [UU_]
      [=>...................]  recovery =  7.5% (36384900/479371392) finish=210.2min speed=35113K/sec
      
unused devices: <none>

--- /proc/partitions:
major minor  #blocks  name

   8        0  488386584 sda
   8        1    4008186 sda1
   8        2     498015 sda2
   8        3  479371567 sda3
   8        4    4506232 sda4
   8       16  488386584 sdb
   8       17    4008186 sdb1
   8       18     498015 sdb2
   8       19  479371567 sdb3
   8       20    4506232 sdb4
   8       32  488386584 sdc
   8       33    4008186 sdc1
   8       34     498015 sdc2
   8       35  479371567 sdc3
   8       36    4506232 sdc4
   8       48 1953514584 sdd
   8       49    4008186 sdd1
   8       50     498015 sdd2
   8       51  479371567 sdd3
   8       52    4506232 sdd4
 254     8128  958742784 md_d127
 254     8129   15728639 md_d127p1
 254     8130   10485760 md_d127p2
 254     8131    8388608 md_d127p3
 254     8133  209715199 md_d127p5
 254     8134    5247999 md_d127p6
 254     8135  367001599 md_d127p7
 254     8136  209715199 md_d127p8
 254     8064    4506224 md_d126
 254     8000     498004 md_d125
 254     7872    4506224 md_d123
 254     7808     498004 md_d122

--- LVM physical volumes:
LVM does not seem to be used.
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=3801236k,nr_inodes=950309,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=768164k,mode=755)
/dev/md/root on / type reiserfs (rw,relatime,notail,data=journal)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3139580k)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/md_d125 on /boot type reiserfs (rw,relatime,notail)
/dev/md_d127p1 on /usr type reiserfs (rw,relatime,notail,data=journal)
/dev/md_d127p2 on /tmp type reiserfs (rw,relatime,notail,data=journal)
/dev/md_d127p3 on /var type reiserfs (rw,relatime,notail,data=journal)
/dev/md_d127p5 on /home type reiserfs (rw,relatime,notail,data=journal)
/dev/md_d127p6 on /home/svn type reiserfs (rw,relatime,notail,data=journal)
/dev/md_d127p7 on /backup type reiserfs (rw,relatime,notail,data=journal)
/dev/md_d127p8 on /unbacked type xfs (rw,relatime,delaylog,noquota)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)

--- initrd.img-3.1.0-1-amd64:
65322 blocks
dbe8291e0bd16a564633782c8ea58535  ./etc/mdadm/mdadm.conf
7756817483fd4a107bcd00acf0f5c32f  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/dm-mirror.ko
e9d258f1a42679a20d53f6d0b9b8632a  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/dm-log.ko
fcac99130c17c3d9be24262c281264fc  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/dm-mod.ko
420c6fe352a288f49eb2c9dfab95db16  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/raid456.ko
e78080af91a818d198f656f0f9cfb997  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/multipath.ko
099a1f2e53ab9c9434be9af35ce01adb  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/dm-region-hash.ko
11d3071442df862bb9035335d492ed75  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/raid0.ko
338d2ded2763e8f617d59ce064892d9f  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/raid1.ko
36c523d032fb10f8d408c42e5f59b09b  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/raid10.ko
c7351558c79fe97e91fbedd1c6b48fca  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/dm-snapshot.ko
fbc4c7c6820195e751a954525b203772  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/linear.ko
7a5156649da498888c1303f1ca674ffd  ./lib/modules/3.1.0-1-amd64/kernel/drivers/md/md-mod.ko
c3beb0a215e8c507f1b43de188c67b21  ./sbin/mdadm
f4fbd9099399ab08ba9b9f6c71d77595  ./scripts/local-top/mdadm

--- initrd's /conf/conf.d/md:
MD_DEVPAIRS='/dev/md/base:raid5 /dev/md/root:raid1 /dev/md/boot:raid1'
MD_LEVELS='raid5 raid1 raid1'
MD_DEVS=all
MD_MODULES='raid1 raid456'

--- /proc/modules:
dm_mod 63353 0 - Live 0xffffffffa01af000
raid456 48363 1 - Live 0xffffffffa019d000
async_raid6_recov 12526 1 raid456, Live 0xffffffffa0198000
async_pq 12605 2 raid456,async_raid6_recov, Live 0xffffffffa0193000
raid6_pq 82591 2 async_raid6_recov,async_pq, Live 0xffffffffa017d000
async_xor 12422 3 raid456,async_raid6_recov,async_pq, Live 0xffffffffa0178000
async_memcpy 12387 2 raid456,async_raid6_recov, Live 0xffffffffa014c000
async_tx 12566 5 raid456,async_raid6_recov,async_pq,async_xor,async_memcpy, Live 0xffffffffa0068000
raid1 30716 4 - Live 0xffffffffa0125000
md_mod 87742 12 raid456,raid1, Live 0xffffffffa015c000

--- /var/log/syslog:

--- volume detail:
/dev/sda is not recognised by mdadm.
/dev/sda1 is not recognised by mdadm.
/dev/sda2 is not recognised by mdadm.
/dev/sda3 is not recognised by mdadm.
/dev/sda4 is not recognised by mdadm.
/dev/sdb is not recognised by mdadm.
/dev/sdb1 is not recognised by mdadm.
/dev/sdb2 is not recognised by mdadm.
/dev/sdb3 is not recognised by mdadm.
/dev/sdb4 is not recognised by mdadm.
/dev/sdc is not recognised by mdadm.
/dev/sdc1 is not recognised by mdadm.
/dev/sdc2 is not recognised by mdadm.
/dev/sdc3 is not recognised by mdadm.
/dev/sdc4 is not recognised by mdadm.
/dev/sdd is not recognised by mdadm.
/dev/sdd1 is not recognised by mdadm.
/dev/sdd2 is not recognised by mdadm.
/dev/sdd3 is not recognised by mdadm.
/dev/sdd4 is not recognised by mdadm.
/dev/sde is not recognised by mdadm.

--- /proc/cmdline
root=/dev/md/root data=journal ro 

--- grub2:
	linux	/vmlinuz-2.6.31-1-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.31-1-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.30-2-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.30-2-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.30-1-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.30-1-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.29-2-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.29-2-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.29-1-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.29-1-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.26-2-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.26-2-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.26-1-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.26-1-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.25-2-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.25-2-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.24-1-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.24-1-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.22-3-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.22-3-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.18-6-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.18-6-amd64 root=/dev/md_d126 ro single 
	linux	/vmlinuz-2.6.18-5-amd64 root=/dev/md_d126 ro  quiet
	linux	/vmlinuz-2.6.18-5-amd64 root=/dev/md_d126 ro single 
	set root=(hd0,1)
	linux /boot/vmlinuz-2.6.18-5-amd64 root=/dev/sda1 ro
	set root=(hd0,1)
	linux /boot/vmlinuz-2.6.18-5-amd64 root=/dev/sda1 ro single

--- grub legacy:
kernel		/vmlinuz-3.2.0-4-amd64 root=/dev/md/root data=journal ro 
kernel		/vmlinuz-3.2.0-4-amd64 root=/dev/md/root data=journal ro single
kernel		/vmlinuz-3.2.0-3-amd64 root=/dev/md/root data=journal ro 
kernel		/vmlinuz-3.2.0-3-amd64 root=/dev/md/root data=journal ro single
kernel		/vmlinuz-3.2.0-2-amd64 root=/dev/md/root data=journal ro 
kernel		/vmlinuz-3.2.0-2-amd64 root=/dev/md/root data=journal ro single
kernel		/vmlinuz-3.2.0-1-amd64 root=/dev/md/root data=journal ro 
kernel		/vmlinuz-3.2.0-1-amd64 root=/dev/md/root data=journal ro single
kernel          /vmlinuz-3.1.0-1-amd64 root=/dev/md/root data=journal ro 
kernel          /vmlinuz-3.1.0-1-amd64 root=/dev/md/root data=journal ro single
kernel		/vmlinuz-2.6.32-2-amd64 root=/dev/md/root data=journal ro 
kernel		/vmlinuz-2.6.32-2-amd64 root=/dev/md/root data=journal ro single
kernel		/boot/vmlinuz-2.6.18-5-amd64 root=/dev/sda1 ro single

--- udev:
ii  udev           175-7        amd64        /dev/ and hotplug management daem
6df86db16655769fa94086d3ee13453a  /lib/udev/rules.d/64-md-raid.rules

--- /dev:
brw-rw---T 1 root disk 254, 7808 Nov 26 19:16 /dev/md_d122
brw-rw---T 1 root disk 254, 7872 Nov 26 19:16 /dev/md_d123
brw-rw---T 1 root disk 254, 7936 Nov 26 21:03 /dev/md_d124
brw-rw---T 1 root disk 254, 8000 Nov 26 19:16 /dev/md_d125
brw-rw---- 1 root disk 254, 8001 Nov 25 16:35 /dev/md_d125p1
brw-rw---- 1 root disk 254, 8002 Nov 25 16:35 /dev/md_d125p2
brw-rw---- 1 root disk 254, 8003 Nov 25 16:35 /dev/md_d125p3
brw-rw---T 1 root disk 254, 8064 Nov 26 19:16 /dev/md_d126
brw-rw---- 1 root disk 254, 8065 Nov 25 16:35 /dev/md_d126p1
brw-rw---- 1 root disk 254, 8066 Nov 25 16:35 /dev/md_d126p2
brw-rw---- 1 root disk 254, 8067 Nov 25 16:35 /dev/md_d126p3
brw-rw---T 1 root disk 254, 8128 Nov 26 20:46 /dev/md_d127
brw-rw---T 1 root disk 254, 8129 Nov 25 16:36 /dev/md_d127p1
brw-rw---- 1 root disk 254, 8138 Nov 25 16:35 /dev/md_d127p10
brw-rw---T 1 root disk 254, 8130 Nov 25 16:37 /dev/md_d127p2
brw-rw---T 1 root disk 254, 8131 Nov 25 16:37 /dev/md_d127p3
brw-rw---T 1 root disk 254, 8132 Nov 25 16:35 /dev/md_d127p4
brw-rw---T 1 root disk 254, 8133 Nov 25 16:37 /dev/md_d127p5
brw-rw---T 1 root disk 254, 8134 Nov 25 16:37 /dev/md_d127p6
brw-rw---T 1 root disk 254, 8135 Nov 25 16:37 /dev/md_d127p7
brw-rw---T 1 root disk 254, 8136 Nov 25 16:35 /dev/md_d127p8
brw-rw---- 1 root disk 254, 8137 Nov 25 16:35 /dev/md_d127p9

/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root  9 Nov 26 19:16 ata-SAMSUNG_HD204UI_S2H7JD1ZB02914 -> ../../sdd
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-SAMSUNG_HD204UI_S2H7JD1ZB02914-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-SAMSUNG_HD204UI_S2H7JD1ZB02914-part2 -> ../../sdd2
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-SAMSUNG_HD204UI_S2H7JD1ZB02914-part3 -> ../../sdd3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-SAMSUNG_HD204UI_S2H7JD1ZB02914-part4 -> ../../sdd4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 ata-ST3500320AS_5QM060J8 -> ../../sdc
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-ST3500320AS_5QM060J8-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-ST3500320AS_5QM060J8-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Nov 26 20:45 ata-ST3500320AS_5QM060J8-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-ST3500320AS_5QM060J8-part4 -> ../../sdc4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 ata-ST3500320AS_5QM0694K -> ../../sdb
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-ST3500320AS_5QM0694K-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-ST3500320AS_5QM0694K-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Nov 26 20:46 ata-ST3500320AS_5QM0694K-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Nov 26 19:16 ata-ST3500320AS_5QM0694K-part4 -> ../../sdb4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 ata-ST3500320AS_5QM06EPX -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-ST3500320AS_5QM06EPX-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-ST3500320AS_5QM06EPX-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-ST3500320AS_5QM06EPX-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 ata-ST3500320AS_5QM06EPX-part4 -> ../../sda4
lrwxrwxrwx 1 root root  9 Nov 26 17:20 ata-TSSTcorp_CDDVDW_SH-S222L -> ../../sr0
lrwxrwxrwx 1 root root 13 Nov 26 20:46 md-name-newbagpipes:base -> ../../md_d127
lrwxrwxrwx 1 root root 15 Nov 25 16:36 md-name-newbagpipes:base-part1 -> ../../md_d127p1
lrwxrwxrwx 1 root root 15 Nov 25 16:37 md-name-newbagpipes:base-part2 -> ../../md_d127p2
lrwxrwxrwx 1 root root 15 Nov 25 16:37 md-name-newbagpipes:base-part3 -> ../../md_d127p3
lrwxrwxrwx 1 root root 15 Nov 25 16:37 md-name-newbagpipes:base-part5 -> ../../md_d127p5
lrwxrwxrwx 1 root root 15 Nov 25 16:37 md-name-newbagpipes:base-part6 -> ../../md_d127p6
lrwxrwxrwx 1 root root 15 Nov 25 16:37 md-name-newbagpipes:base-part7 -> ../../md_d127p7
lrwxrwxrwx 1 root root 15 Nov 25 16:35 md-name-newbagpipes:base-part8 -> ../../md_d127p8
lrwxrwxrwx 1 root root 13 Nov 26 19:16 md-name-newbagpipes:boot -> ../../md_d125
lrwxrwxrwx 1 root root 13 Nov 26 19:16 md-name-newbagpipes:root -> ../../md_d126
lrwxrwxrwx 1 root root 13 Nov 26 19:16 md-uuid-14ae485f:60ca6705:8558a43a:958b6e38 -> ../../md_d126
lrwxrwxrwx 1 root root 13 Nov 26 20:46 md-uuid-959fc2b3:8a86d38c:45e4afda:6695f914 -> ../../md_d127
lrwxrwxrwx 1 root root 15 Nov 25 16:36 md-uuid-959fc2b3:8a86d38c:45e4afda:6695f914-part1 -> ../../md_d127p1
lrwxrwxrwx 1 root root 15 Nov 25 16:37 md-uuid-959fc2b3:8a86d38c:45e4afda:6695f914-part2 -> ../../md_d127p2
lrwxrwxrwx 1 root root 15 Nov 25 16:37 md-uuid-959fc2b3:8a86d38c:45e4afda:6695f914-part3 -> ../../md_d127p3
lrwxrwxrwx 1 root root 15 Nov 25 16:37 md-uuid-959fc2b3:8a86d38c:45e4afda:6695f914-part5 -> ../../md_d127p5
lrwxrwxrwx 1 root root 15 Nov 25 16:37 md-uuid-959fc2b3:8a86d38c:45e4afda:6695f914-part6 -> ../../md_d127p6
lrwxrwxrwx 1 root root 15 Nov 25 16:37 md-uuid-959fc2b3:8a86d38c:45e4afda:6695f914-part7 -> ../../md_d127p7
lrwxrwxrwx 1 root root 15 Nov 25 16:35 md-uuid-959fc2b3:8a86d38c:45e4afda:6695f914-part8 -> ../../md_d127p8
lrwxrwxrwx 1 root root 13 Nov 26 19:16 md-uuid-d00f020f:0fcfe10c:d7f06b15:ed4f7cb1 -> ../../md_d125
lrwxrwxrwx 1 root root  9 Nov 26 19:16 scsi-SATA_SAMSUNG_HD204UIS2H7JD1ZB02914 -> ../../sdd
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_SAMSUNG_HD204UIS2H7JD1ZB02914-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_SAMSUNG_HD204UIS2H7JD1ZB02914-part2 -> ../../sdd2
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_SAMSUNG_HD204UIS2H7JD1ZB02914-part3 -> ../../sdd3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_SAMSUNG_HD204UIS2H7JD1ZB02914-part4 -> ../../sdd4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 scsi-SATA_ST3500320AS_5QM060J8 -> ../../sdc
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_ST3500320AS_5QM060J8-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_ST3500320AS_5QM060J8-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Nov 26 20:45 scsi-SATA_ST3500320AS_5QM060J8-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_ST3500320AS_5QM060J8-part4 -> ../../sdc4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 scsi-SATA_ST3500320AS_5QM0694K -> ../../sdb
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_ST3500320AS_5QM0694K-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_ST3500320AS_5QM0694K-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Nov 26 20:46 scsi-SATA_ST3500320AS_5QM0694K-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Nov 26 19:16 scsi-SATA_ST3500320AS_5QM0694K-part4 -> ../../sdb4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 scsi-SATA_ST3500320AS_5QM06EPX -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_ST3500320AS_5QM06EPX-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_ST3500320AS_5QM06EPX-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_ST3500320AS_5QM06EPX-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 scsi-SATA_ST3500320AS_5QM06EPX-part4 -> ../../sda4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 wwn-0x5000c5000832878c -> ../../sdc
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x5000c5000832878c-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x5000c5000832878c-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Nov 26 20:45 wwn-0x5000c5000832878c-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x5000c5000832878c-part4 -> ../../sdc4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 wwn-0x5000c50008329d0a -> ../../sdb
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x5000c50008329d0a-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x5000c50008329d0a-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Nov 26 20:46 wwn-0x5000c50008329d0a-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Nov 26 19:16 wwn-0x5000c50008329d0a-part4 -> ../../sdb4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 wwn-0x5000c5000832a055 -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x5000c5000832a055-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x5000c5000832a055-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x5000c5000832a055-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x5000c5000832a055-part4 -> ../../sda4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 wwn-0x50024e90044d2a5c -> ../../sdd
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x50024e90044d2a5c-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x50024e90044d2a5c-part2 -> ../../sdd2
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x50024e90044d2a5c-part3 -> ../../sdd3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 wwn-0x50024e90044d2a5c-part4 -> ../../sdd4

/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root  9 Nov 26 17:20 pci-0000:00:04.0-scsi-0:0:0:0 -> ../../sr0
lrwxrwxrwx 1 root root  9 Nov 26 19:16 pci-0000:00:05.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.0-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.0-scsi-0:0:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.0-scsi-0:0:0:0-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.0-scsi-0:0:0:0-part4 -> ../../sda4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 pci-0000:00:05.0-scsi-1:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.0-scsi-1:0:0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.0-scsi-1:0:0:0-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Nov 26 20:46 pci-0000:00:05.0-scsi-1:0:0:0-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Nov 26 19:16 pci-0000:00:05.0-scsi-1:0:0:0-part4 -> ../../sdb4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 pci-0000:00:05.1-scsi-0:0:0:0 -> ../../sdc
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.1-scsi-0:0:0:0-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.1-scsi-0:0:0:0-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Nov 26 20:45 pci-0000:00:05.1-scsi-0:0:0:0-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.1-scsi-0:0:0:0-part4 -> ../../sdc4
lrwxrwxrwx 1 root root  9 Nov 26 19:16 pci-0000:00:05.1-scsi-1:0:0:0 -> ../../sdd
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.1-scsi-1:0:0:0-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.1-scsi-1:0:0:0-part2 -> ../../sdd2
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.1-scsi-1:0:0:0-part3 -> ../../sdd3
lrwxrwxrwx 1 root root 10 Nov 25 16:35 pci-0000:00:05.1-scsi-1:0:0:0-part4 -> ../../sdd4

/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 13 Nov 26 19:16 08773c30-f8c6-425a-a9bb-6f2c85702a76 -> ../../md_d125
lrwxrwxrwx 1 root root 15 Nov 25 16:36 1f6d1b98-77ce-4828-8e63-5c52e8540a87 -> ../../md_d127p1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 35f41417-c26b-4991-a4c0-9edc63e80f4b -> ../../sdc1
lrwxrwxrwx 1 root root 15 Nov 25 16:37 36e93d79-e145-42ce-a0d1-b159c87859ec -> ../../md_d127p2
lrwxrwxrwx 1 root root 10 Nov 25 16:35 5b07fa4c-cbb3-42a3-8490-886659abe033 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Nov 25 16:35 7d00dc54-b3c1-497c-b8d9-b4e7a59fb557 -> ../../sda1
lrwxrwxrwx 1 root root 15 Nov 25 16:37 93f43905-14d8-4b23-a615-76cb355680b2 -> ../../md_d127p5
lrwxrwxrwx 1 root root 15 Nov 25 16:37 98e5f877-5bd4-4646-a87f-64b988d5470f -> ../../md_d127p7
lrwxrwxrwx 1 root root 15 Nov 25 16:35 a349922e-b913-4dc4-a9e5-822573178237 -> ../../md_d127p8
lrwxrwxrwx 1 root root 13 Nov 26 19:16 a889f772-abdf-4c73-bded-59de1a002aee -> ../../md_d126
lrwxrwxrwx 1 root root 15 Nov 25 16:37 f9374869-c154-4d09-ba8d-b858bbcba4c2 -> ../../md_d127p6
lrwxrwxrwx 1 root root 15 Nov 25 16:37 fe39e69e-863d-4d42-b55f-025c6fb4c4f2 -> ../../md_d127p3

/dev/md:
total 0
lrwxrwxrwx 1 root root 10 Nov 26 20:46 base -> ../md_d127
lrwxrwxrwx 1 root root 12 Nov 25 16:36 base1 -> ../md_d127p1
lrwxrwxrwx 1 root root 15 Nov 25 16:35 base10 -> /dev/md_d127p10
lrwxrwxrwx 1 root root 12 Nov 25 16:37 base2 -> ../md_d127p2
lrwxrwxrwx 1 root root 12 Nov 25 16:37 base3 -> ../md_d127p3
lrwxrwxrwx 1 root root 12 Nov 25 16:37 base5 -> ../md_d127p5
lrwxrwxrwx 1 root root 12 Nov 25 16:37 base6 -> ../md_d127p6
lrwxrwxrwx 1 root root 12 Nov 25 16:37 base7 -> ../md_d127p7
lrwxrwxrwx 1 root root 12 Nov 25 16:35 base8 -> ../md_d127p8
lrwxrwxrwx 1 root root 14 Nov 25 16:35 base9 -> /dev/md_d127p9
lrwxrwxrwx 1 root root 10 Nov 26 19:16 boot -> ../md_d125
lrwxrwxrwx 1 root root 14 Nov 25 16:35 boot1 -> /dev/md_d125p1
lrwxrwxrwx 1 root root 14 Nov 25 16:35 boot2 -> /dev/md_d125p2
lrwxrwxrwx 1 root root 14 Nov 25 16:35 boot3 -> /dev/md_d125p3
lrwxrwxrwx 1 root root 10 Nov 26 19:16 root -> ../md_d126
lrwxrwxrwx 1 root root 14 Nov 25 16:35 root1 -> /dev/md_d126p1
lrwxrwxrwx 1 root root 14 Nov 25 16:35 root2 -> /dev/md_d126p2
lrwxrwxrwx 1 root root 14 Nov 25 16:35 root3 -> /dev/md_d126p3

Auto-generated on Mon, 26 Nov 2012 21:03:46 -0600
by mdadm bugscript 3.2.5-3

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages mdadm depends on:
ii  debconf      1.5.46
ii  initscripts  2.88dsf-32
ii  libc6        2.13-35
ii  lsb-base     4.1+Debian7
ii  makedev      2.3.1-92
ii  udev         175-7

Versions of packages mdadm recommends:
ii  module-init-tools             9-2
ii  ssmtp [mail-transport-agent]  2.64-7

mdadm suggests no packages.

-- debconf information:
* mdadm/initrdstart: all
  mdadm/initrdstart_msg_errexist:
  mdadm/start_daemon: true
  mdadm/mail_to: moshe
  mdadm/initrdstart_msg_errmd:
  mdadm/autocheck: true
  mdadm/autostart: true
  mdadm/initrdstart_notinconf: false
  mdadm/initrdstart_msg_intro:
  mdadm/initrdstart_msg_errblock:
  mdadm/initrdstart_msg_errconf:



More information about the pkg-mdadm-devel mailing list