From ftpmaster at ftp-master.debian.org  Wed Oct  1 11:13:23 2014
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 01 Oct 2014 11:13:23 +0000
Subject: Processing of mdadm_3.3.2-1_amd64.changes
Message-ID: <E1XZHqV-00057B-UM@franck.debian.org>

mdadm_3.3.2-1_amd64.changes uploaded successfully to localhost
along with the files:
  mdadm_3.3.2-1_amd64.deb
  mdadm-udeb_3.3.2-1_amd64.udeb
  mdadm_3.3.2-1.dsc
  mdadm_3.3.2.orig.tar.xz
  mdadm_3.3.2-1.debian.tar.xz

Greetings,

	Your Debian queue daemon (running on host franck.debian.org)


From ftpmaster at ftp-master.debian.org  Wed Oct  1 11:19:25 2014
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Wed, 01 Oct 2014 11:19:25 +0000
Subject: mdadm_3.3.2-1_amd64.changes ACCEPTED into unstable
Message-ID: <E1XZHwL-000734-RH@franck.debian.org>



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 01 Oct 2014 15:09:07 +0400
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source amd64
Version: 3.3.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian mdadm maintainers <pkg-mdadm-devel at lists.alioth.debian.org>
Changed-By: Michael Tokarev <mjt at tls.msk.ru>
Description:
 mdadm      - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 678691 728804 731884 733574 763080
Changes:
 mdadm (3.3.2-1) unstable; urgency=low
 .
   * new minor/bugfix upstream release (Closes: #731884, #763080)
   * removed remove-bashism-from-makefile.patch (applied upstream)
   * copy 64-md-raid-assembly.rules to initramfs too, this should
     bring us array auto-assemble during initramfs run (Closes: #678691)
   * denote inability to initialize md subsystem in local-top script
     from fatal error to warning (Closes: #733574)
   * create /etc/modprobe.d/mdadm.conf to set start_ro=1 there
     instead of doing it in the initramfs
   * use install -D in d/rules consistently and remove dirs from d/mdadm.dirs
   * remove references to old (2.x and 1.x) mdadm versions (Closes: #728804)
   * remove references to very old (pre-wheeze) breaks/replaces/depends
   * remove support of makedev
   * reformat mdadm-raid initscript a bit
   * remove rebuilding-raid.html (had invisible refs) and
     RAID5_versus_RAID10.txt docs.  Maybe it's a good idea to remove
     other docs shipped with the package, since these becoming stale
     and these days, better alternatives exist online
   * removed debian-specific mdadm-startall script which does nothing more than
     "mdadm --assemble --scan".  Remove docbook-to-man from build-deps.
   * pass dpkg-buildflags to upstream build system and
     stop using our own -O0, -Os etc
   * remove separate CFLAGS for udeb and simplify *FLAGS handling
   * bump Standards-Version to 3.9.5 (no changes needed)
   * fix VCS links to point to anonscm.d.o
Checksums-Sha1:
 5eea3e8abcc584329ff8f2d84343f1991196d4a3 1626 mdadm_3.3.2-1.dsc
 c649601d84553501c2f3b452cf93d1fbc53f976a 410628 mdadm_3.3.2.orig.tar.xz
 348dc0888b8f2434d5b97194e6c5167ddc98e7d0 92184 mdadm_3.3.2-1.debian.tar.xz
 dfd98cea6813c0c04c8fcfcb1aad0e1bf76ead22 438028 mdadm_3.3.2-1_amd64.deb
 0acb2275dc39ded29db0e6053229c2dda493b265 252508 mdadm-udeb_3.3.2-1_amd64.udeb
Checksums-Sha256:
 fcab01ca968284b23ba300d513af94d85cda4f5ad9056ccea305f124b8fe4e43 1626 mdadm_3.3.2-1.dsc
 0f3a7e1a76b13892b79f9fceaf99ecb23513260389a768ac644ffa3ae06e5b8c 410628 mdadm_3.3.2.orig.tar.xz
 e356790d3ab24f31598f4463016794dd6ae8bd494b46575a83a6ca53c211ec18 92184 mdadm_3.3.2-1.debian.tar.xz
 4b7a86939e768455c4102eebcea6201ebbc9d552a9f9b2f31be9eab8e26ba815 438028 mdadm_3.3.2-1_amd64.deb
 e41773817a5c5a50896b2038e393fd46e82f4b25fe942e46f9347c972d506d1c 252508 mdadm-udeb_3.3.2-1_amd64.udeb
Files:
 0cbcb977fd256d8b9cb8d7606e8d740e 438028 admin optional mdadm_3.3.2-1_amd64.deb
 305db44233e6d7a8aef457ad67d4fbda 252508 debian-installer optional mdadm-udeb_3.3.2-1_amd64.udeb
 394cd71c075cfbd836fca38a24448635 1626 admin optional mdadm_3.3.2-1.dsc
 44698d351501cac6a89072dc877eb220 410628 admin optional mdadm_3.3.2.orig.tar.xz
 ac146628623b923f7f6d9d420bd6eeb6 92184 admin optional mdadm_3.3.2-1.debian.tar.xz
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJUK+EgAAoJEL7lnXSkw9fbN/0IAIjA3x+DbkJ6ZcycQalF0Mvu
avMXQV/6x7y5cfayutZcnnmHKEYJK2lpgl2Rqs4+GsJqF1FWBMveYKJ5v+4sG/s9
K6EFuov1tMj/cRgfgxQHWa34v7cdVmKW6YjJKi5WRr1SNskFlvqI7reD1y84k060
Huw9ievo/6bK8FivcZ+OkEm9hf0NTwuE+T7tm5Ayi7Am41vtOgodfcTmquY6mXIl
FPk21BUb2V1KjIgRxmHj6k789fSadbxO9y0PnbZNC3/xOQQzjNzLIuNCTg/UHY5K
lrTWkuWlMFOKkVRTeXcaev72J9Qhw7ktGPzeq91P/96rkPI2rkKnsBffVeUescs=
=rAtr
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Wed Oct  1 11:21:13 2014
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 01 Oct 2014 11:21:13 +0000
Subject: Bug#678691: marked as done (Please add a
 /usr/share/initramfs-tools/scripts/local-block/ script)
References: <E1XZHwL-00073E-T6@franck.debian.org>
 <20120623185703.4479.59038.reportbug@frosties.localnet>
Message-ID: <handler.678691.D678691.14121623693851.ackdone@bugs.debian.org>

Your message dated Wed, 01 Oct 2014 11:19:25 +0000
with message-id <E1XZHwL-00073E-T6 at franck.debian.org>
and subject line Bug#678691: fixed in mdadm 3.3.2-1
has caused the Debian Bug report #678691,
regarding Please add a /usr/share/initramfs-tools/scripts/local-block/ script
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
678691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678691
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Goswin von Brederlow <goswin-v-b at web.de>
Subject: Please add a /usr/share/initramfs-tools/scripts/local-block/ script
Date: Sat, 23 Jun 2012 20:57:03 +0200
Size: 4681
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/d9c530a0/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Tokarev <mjt at tls.msk.ru>
Subject: Bug#678691: fixed in mdadm 3.3.2-1
Date: Wed, 01 Oct 2014 11:19:25 +0000
Size: 6730
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/d9c530a0/attachment-0003.mht>

From owner at bugs.debian.org  Wed Oct  1 11:21:18 2014
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 01 Oct 2014 11:21:18 +0000
Subject: Bug#728804: marked as done (mdadm: warning on package upgrade
 refers to non-existing file)
References: <E1XZHwL-00073K-Ty@franck.debian.org>
 <20131105180113.23867.9758.reportbug@mordor.loewenhoehle.ip>
Message-ID: <handler.728804.D728804.14121623693855.ackdone@bugs.debian.org>

Your message dated Wed, 01 Oct 2014 11:19:25 +0000
with message-id <E1XZHwL-00073K-Ty at franck.debian.org>
and subject line Bug#728804: fixed in mdadm 3.3.2-1
has caused the Debian Bug report #728804,
regarding mdadm: warning on package upgrade refers to non-existing file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
728804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728804
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Tobias Frost <tobi at coldtobi.de>
Subject: mdadm: warning on package upgrade refers to non-existing file
Date: Tue, 05 Nov 2013 19:01:13 +0100
Size: 3201
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/a638a005/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Tokarev <mjt at tls.msk.ru>
Subject: Bug#728804: fixed in mdadm 3.3.2-1
Date: Wed, 01 Oct 2014 11:19:25 +0000
Size: 6730
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/a638a005/attachment-0001.mht>

From owner at bugs.debian.org  Wed Oct  1 11:21:22 2014
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 01 Oct 2014 11:21:22 +0000
Subject: Bug#731884: marked as done (boot from Intel IMSM raid0 often fails)
References: <E1XZHwL-00073Q-Ur@franck.debian.org>
 <20131210203938.3996.39639.reportbug@coal.colmar.atlantech.com>
Message-ID: <handler.731884.D731884.14121623693867.ackdone@bugs.debian.org>

Your message dated Wed, 01 Oct 2014 11:19:25 +0000
with message-id <E1XZHwL-00073Q-Ur at franck.debian.org>
and subject line Bug#731884: fixed in mdadm 3.3.2-1
has caused the Debian Bug report #731884,
regarding boot from Intel IMSM raid0 often fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
731884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731884
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: John Hughes <john at calva.com>
Subject: initramfs-tools: randomly /dev/disk/by-uuid doesn't exits, making boot from crypt partition fail
Date: Tue, 10 Dec 2013 21:39:38 +0100
Size: 10472
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/e70ece4e/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Tokarev <mjt at tls.msk.ru>
Subject: Bug#731884: fixed in mdadm 3.3.2-1
Date: Wed, 01 Oct 2014 11:19:25 +0000
Size: 6729
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/e70ece4e/attachment-0003.mht>

From owner at bugs.debian.org  Wed Oct  1 11:21:26 2014
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 01 Oct 2014 11:21:26 +0000
Subject: Bug#733574: marked as done (partially breaks initramfs when
 modules are not included)
References: <E1XZHwM-00073X-0C@franck.debian.org>
 <20131230010831.GA4120@rotes76.wohnheim.uni-kl.de>
Message-ID: <handler.733574.D733574.14121623673810.ackdone@bugs.debian.org>

Your message dated Wed, 01 Oct 2014 11:19:26 +0000
with message-id <E1XZHwM-00073X-0C at franck.debian.org>
and subject line Bug#733574: fixed in mdadm 3.3.2-1
has caused the Debian Bug report #733574,
regarding partially breaks initramfs when modules are not included
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
733574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733574
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Eduard Bloch <blade at debian.org>
Subject: partially breaks initramfs when modules are not included
Date: Mon, 30 Dec 2013 02:08:31 +0100
Size: 3880
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/9c17cd9c/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Tokarev <mjt at tls.msk.ru>
Subject: Bug#733574: fixed in mdadm 3.3.2-1
Date: Wed, 01 Oct 2014 11:19:26 +0000
Size: 6705
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/9c17cd9c/attachment-0001.mht>

From owner at bugs.debian.org  Wed Oct  1 11:21:39 2014
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 01 Oct 2014 11:21:39 +0000
Subject: Bug#763080: marked as done (Fails to assemble a reshapning raid
 after disk hickup)
References: <E1XZHwM-00073d-13@franck.debian.org>
 <20140927175726.30779.22312.reportbug@frosties.localnet>
Message-ID: <handler.763080.D763080.14121623693880.ackdone@bugs.debian.org>

Your message dated Wed, 01 Oct 2014 11:19:26 +0000
with message-id <E1XZHwM-00073d-13 at franck.debian.org>
and subject line Bug#763080: fixed in mdadm 3.3.2-1
has caused the Debian Bug report #763080,
regarding Fails to assemble a reshapning raid after disk hickup
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
763080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763080
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Goswin von Brederlow <goswin-v-b at web.de>
Subject: Fails to assemble a reshapning raid after disk hickup
Date: Sat, 27 Sep 2014 19:57:26 +0200
Size: 11158
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/a1c8988a/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Tokarev <mjt at tls.msk.ru>
Subject: Bug#763080: fixed in mdadm 3.3.2-1
Date: Wed, 01 Oct 2014 11:19:26 +0000
Size: 6729
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/a1c8988a/attachment-0003.mht>

From rajni.chand at usp.ac.fj  Wed Oct  1 20:37:32 2014
From: rajni.chand at usp.ac.fj (Rajni Chand)
Date: Wed, 1 Oct 2014 20:37:32 +0000
Subject: INQUIRY.
Message-ID: <4B913E85A6ABDC44B063B521A6987AA85DCD38EB@SUVXCH10MB3.usp.ac.fj>

My name is Mr. Andy Chow, I am a trained external auditor working for MayBank Malaysia, a late investor who bears the same last name with you has left monies totaling(?12.5Million)with Our Bank for the past Four  years and no next of kin has come forward all these years,I will like you to acknowledge the receipt of this e-mail so as to present you as the next of kin:(mr.andychow at asia.com) but if not interested kindly delete it immediately.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141001/be22f7e1/attachment.html>

From jan at goneko.de  Fri Oct  3 18:24:54 2014
From: jan at goneko.de (Jan Echternach)
Date: Fri, 3 Oct 2014 20:24:54 +0200
Subject: Bug#763917: mdadm: rounding errors in human_size()
Message-ID: <20141003182454.GA9120@goneko.de>

Package: mdadm
Version: 3.3.2-1
Severity: minor
Tags: patch


While setting up a new system, I noticed an incorrect value in the output
of mdadm --examine:

 Avail Dev Size : 2095080 (1023.16 MiB 1072.68 MB)

The 1023.16 MiB were quite irritating because the underlying partition has
a size of exactly 1023 MiB.

The number of sectors seems plausible: 2095080 sectors * 512 bytes/sector
are 1022.988 MiB or 1072.681 MB. I looked into the code and found an
inaccuracy in human_size() and human_size_brief(). The formula used for
the MiB value is essentially

  long cMiB = (bytes / ( (1LL<<20) / 200LL ) +1) /2;

but (1LL<<20) / 200LL is not an integer. It's rounded down and cMiB becomes
too large. The quick fix would have been multiplying by 200 before dividing
by 1<<20, but that might cause integer overflows in the GiB case.

The following patch uses a more complicated formula that computes the
fractional portion separately from the integer portion. It also changes some
longs to long longs to eliminate a different cause of integer overflows.


--- mdadm-3.3.2/util.c	2014-10-03 19:06:51.000000000 +0200
+++ mdadm-3.3.2/util.c	2014-10-03 19:08:06.000000000 +0200
@@ -671,15 +671,17 @@
 	if (bytes < 5000*1024)
 		buf[0] = 0;
 	else if (bytes < 2*1024LL*1024LL*1024LL) {
-		long cMiB = (bytes / ( (1LL<<20) / 200LL ) +1) /2;
+		long cMiB = bytes / (1LL<<20) * 100
+			    + ((bytes % (1LL<<20)) * 200 / (1LL<<20) +1) /2;
 		long cMB  = (bytes / ( 1000000LL / 200LL ) +1) /2;
 		snprintf(buf, sizeof(buf), " (%ld.%02ld MiB %ld.%02ld MB)",
 			cMiB/100 , cMiB % 100,
 			cMB/100, cMB % 100);
 	} else {
-		long cGiB = (bytes / ( (1LL<<30) / 200LL ) +1) /2;
-		long cGB  = (bytes / (1000000000LL/200LL ) +1) /2;
-		snprintf(buf, sizeof(buf), " (%ld.%02ld GiB %ld.%02ld GB)",
+		long long cGiB = bytes / (1LL<<30) * 100
+				 + ((bytes % (1LL<<30)) * 200 / (1LL<<30) +1) /2;
+		long long cGB  = (bytes / (1000000000LL/200LL ) +1) /2;
+		snprintf(buf, sizeof(buf), " (%lld.%02lld GiB %lld.%02lld GB)",
 			cGiB/100 , cGiB % 100,
 			cGB/100, cGB % 100);
 	}
@@ -706,12 +708,14 @@
 		buf[0] = 0;
 	else if (prefix == IEC) {
 		if (bytes < 2*1024LL*1024LL*1024LL) {
-			long cMiB = (bytes / ( (1LL<<20) / 200LL ) +1) /2;
+			long cMiB = bytes / (1LL<<20) * 100
+				    + ((bytes % (1LL<<20)) * 200 / (1LL<<20) +1) /2;
 			snprintf(buf, sizeof(buf), "%ld.%02ldMiB",
 				cMiB/100 , cMiB % 100);
 		} else {
-			long cGiB = (bytes / ( (1LL<<30) / 200LL ) +1) /2;
-			snprintf(buf, sizeof(buf), "%ld.%02ldGiB",
+			long long cGiB = bytes / (1LL<<30) * 100
+					 + ((bytes % (1LL<<30)) * 200 / (1LL<<30) +1) /2;
+			snprintf(buf, sizeof(buf), "%lld.%02lldGiB",
 					cGiB/100 , cGiB % 100);
 		}
 	}
@@ -721,8 +725,8 @@
 			snprintf(buf, sizeof(buf), "%ld.%02ldMB",
 					cMB/100, cMB % 100);
 		} else {
-			long cGB  = (bytes / (1000000000LL/200LL ) +1) /2;
-			snprintf(buf, sizeof(buf), "%ld.%02ldGB",
+			long long cGB  = (bytes / (1000000000LL/200LL ) +1) /2;
+			snprintf(buf, sizeof(buf), "%lld.%02lldGB",
 					cGB/100 , cGB % 100);
 		}
 	}


From riesebie at lxtec.de  Sat Oct  4 09:38:28 2014
From: riesebie at lxtec.de (Elimar Riesebieter)
Date: Sat, 04 Oct 2014 11:38:28 +0200
Subject: Bug#763959: mdadm: Cannot add dependency job for unit
 mdmonitor.service
Message-ID: <20141004093828.16393.73922.reportbug@gandalf.home.lxtec.de>

Package: mdadm
Version: 3.3.2-1
Severity: normal

journalctl gives:
systemd[1]: Cannot add dependency job for unit mdmonitor.service, ignoring: Unit mdmonitor.service failed to load: No such file or directory.

With Version: 3.3-2 there is no snippet like that.

-- 
   Elimar


From mjt at tls.msk.ru  Sat Oct  4 09:59:21 2014
From: mjt at tls.msk.ru (Michael Tokarev)
Date: Sat, 04 Oct 2014 13:59:21 +0400
Subject: Bug#763959: mdadm: Cannot add dependency job for unit
 mdmonitor.service
In-Reply-To: <20141004093828.16393.73922.reportbug@gandalf.home.lxtec.de>
References: <20141004093828.16393.73922.reportbug@gandalf.home.lxtec.de>
Message-ID: <542FC4F9.5010007@msgid.tls.msk.ru>

Control: tag -1 + moreinfo

04.10.2014 13:38, Elimar Riesebieter wrote:
[]
> journalctl gives:
> systemd[1]: Cannot add dependency job for unit mdmonitor.service, ignoring: Unit mdmonitor.service failed to load: No such file or directory.

Current mdadm package does not provide mdmonitor.service for systemd, it still
relies on sysvinit startup script.

Please provide output from

  systemctl status mdmonitor.service

to understand where this service comes from.

Thanks,

/mjt

> With Version: 3.3-2 there is no snippet like that.


From owner at bugs.debian.org  Sat Oct  4 10:03:20 2014
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 04 Oct 2014 10:03:20 +0000
Subject: Processed: Re: Bug#763959: mdadm: Cannot add dependency job for
 unit mdmonitor.service
References: <542FC4F9.5010007@msgid.tls.msk.ru>
 <20141004093828.16393.73922.reportbug@gandalf.home.lxtec.de>
Message-ID: <handler.s.B763959.141241676521079.transcript@bugs.debian.org>

Processing control commands:

> tag -1 + moreinfo
Bug #763959 [mdadm] mdadm: Cannot add dependency job for unit mdmonitor.service
Added tag(s) moreinfo.

-- 
763959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763959
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From mjt at tls.msk.ru  Sat Oct  4 11:09:03 2014
From: mjt at tls.msk.ru (Michael Tokarev)
Date: Sat, 04 Oct 2014 15:09:03 +0400
Subject: Bug#763959: mdadm: Cannot add dependency job for unit
 mdmonitor.service
In-Reply-To: <20141004093828.16393.73922.reportbug@gandalf.home.lxtec.de>
References: <20141004093828.16393.73922.reportbug@gandalf.home.lxtec.de>
Message-ID: <542FD54F.4090401@msgid.tls.msk.ru>

Control: tag -1 + confirmed - moreinfo

04.10.2014 13:38, Elimar Riesebieter wrote:
> journalctl gives:
> systemd[1]: Cannot add dependency job for unit mdmonitor.service, ignoring: Unit mdmonitor.service failed to load: No such file or directory.
> 
> With Version: 3.3-2 there is no snippet like that.

I see where it comes from.  It is the new udev rules file.
I'll see what can be done.

Meanwhile, the message is harmless, since mdadm monitor is
started from the regular initscript when needed.

Thanks,

/mjt


From owner at bugs.debian.org  Sat Oct  4 11:12:07 2014
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 04 Oct 2014 11:12:07 +0000
Subject: Processed: Re: Bug#763959: mdadm: Cannot add dependency job for
 unit mdmonitor.service
References: <542FD54F.4090401@msgid.tls.msk.ru>
 <20141004093828.16393.73922.reportbug@gandalf.home.lxtec.de>
Message-ID: <handler.s.B763959.141242094713051.transcript@bugs.debian.org>

Processing control commands:

> tag -1 + confirmed - moreinfo
Bug #763959 [mdadm] mdadm: Cannot add dependency job for unit mdmonitor.service
Added tag(s) confirmed.
Bug #763959 [mdadm] mdadm: Cannot add dependency job for unit mdmonitor.service
Removed tag(s) moreinfo.

-- 
763959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763959
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From owner at bugs.debian.org  Sat Oct  4 16:09:47 2014
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 04 Oct 2014 16:09:47 +0000
Subject: Processed: tagging 763959
References: <1412438938.893802.24165.nullmailer@msgid.tls.msk.ru>
Message-ID: <handler.s.C.141243894229210.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tags 763959 + pending
Bug #763959 [mdadm] mdadm: Cannot add dependency job for unit mdmonitor.service
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
763959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763959
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From ftpmaster at ftp-master.debian.org  Sat Oct  4 17:31:46 2014
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 04 Oct 2014 17:31:46 +0000
Subject: Processing of mdadm_3.3.2-2_amd64.changes
Message-ID: <E1XaTBK-0001yc-9k@franck.debian.org>

mdadm_3.3.2-2_amd64.changes uploaded successfully to localhost
along with the files:
  mdadm_3.3.2-2_amd64.deb
  mdadm-udeb_3.3.2-2_amd64.udeb
  mdadm_3.3.2-2.dsc
  mdadm_3.3.2-2.debian.tar.xz

Greetings,

	Your Debian queue daemon (running on host franck.debian.org)


From ftpmaster at ftp-master.debian.org  Sat Oct  4 17:34:42 2014
From: ftpmaster at ftp-master.debian.org (Debian FTP Masters)
Date: Sat, 04 Oct 2014 17:34:42 +0000
Subject: mdadm_3.3.2-2_amd64.changes ACCEPTED into unstable
Message-ID: <E1XaTEA-0002cV-4g@franck.debian.org>



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 04 Oct 2014 20:38:36 +0400
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source amd64
Version: 3.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian mdadm maintainers <pkg-mdadm-devel at lists.alioth.debian.org>
Changed-By: Michael Tokarev <mjt at tls.msk.ru>
Description:
 mdadm      - tool to administer Linux MD arrays (software RAID)
 mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb)
Closes: 763959
Changes:
 mdadm (3.3.2-2) unstable; urgency=medium
 .
   * remove more leftovers from old versions
   * do not embed $VERSION to mkconf and bugscript
   * removed unneeded lintian-overrides file
   * removed examples/mdadd.sh
   * removed references to MAIL_TO from /etc/default/mdadm (pre-2.x mdadm)
   * removed AUTOSTART variable from /etc/default/mdadm
     (system will start arrays listed in mdadm.conf)
   * simplify d/rules, build udeb in a subdir (for now, to be removed)
   * install systemd services and disable some initscripts (mask them)
     when systemd is running (Closes: #763959)
   * build-sys-no-check_rundir.patch: stop (re)linking executables
     at install time
Checksums-Sha1:
 cefb6356fdc2b4a81875f51f47db48f21977b50a 1626 mdadm_3.3.2-2.dsc
 dd5755a79d62d23c3838f576abd5ed755fd6f3f2 85068 mdadm_3.3.2-2.debian.tar.xz
 d7021fac19691e046754eceaaa4fe447694b2b25 431496 mdadm_3.3.2-2_amd64.deb
 b01961862b3dbad35a110c8d934020d0bd4a6092 252364 mdadm-udeb_3.3.2-2_amd64.udeb
Checksums-Sha256:
 f93a324701182bb119de9c10042c588c93cb8d6c7629f8fefc20e69d3d4d1954 1626 mdadm_3.3.2-2.dsc
 3c6f7e552577f11dd1a015cdbb32c999bbe385da0d93632d64244dd1d8e91dec 85068 mdadm_3.3.2-2.debian.tar.xz
 7c981e72076f8a9ec05d07097284c86abbc10bdd3439a4ccf8e4afbed7ee900b 431496 mdadm_3.3.2-2_amd64.deb
 5036ed1bc08d8964130f51fce0cd235e7fd92442ec0c947500cdc502d34eafde 252364 mdadm-udeb_3.3.2-2_amd64.udeb
Files:
 a36d18a0bcbb122635ce0390f2cd3abf 431496 admin optional mdadm_3.3.2-2_amd64.deb
 fa107f9c531cbf5b2ae08b687085ad0e 252364 debian-installer optional mdadm-udeb_3.3.2-2_amd64.udeb
 f7a2ef0489a4a62f19558d34e896ac00 1626 admin optional mdadm_3.3.2-2.dsc
 76365baf0ed77cc518e9629d7a443f00 85068 admin optional mdadm_3.3.2-2.debian.tar.xz
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJUMC6lAAoJEL7lnXSkw9fbET8H/2qzitVJYYLdq52mrzF+Zznp
/h5hZcCtE5zR78TtwQkIaKzIn/6k7EDk+NQe0yIa+VQA32spSMhqbpY1+V7OeDUb
W4RpCkIsFbrDGn9jR5fWrLXYuMUBbqrrvCwoZpHwkSFqKdS1HsNJnbzyTfFVxj6Z
RcLY3vGE5V5HM9nTIx/UDuI+a2ks6mRJDxZgXdWGlHeHbRtw3UzvCLx/JQkeiteW
IddjWy6LtOF4sSxoMfpcYCxAzx+WXRrck2vzmfKJ0jVeKSV72IUXubSribvflaDS
qZR46fPLiqsQIIJLPWOmYb88aPvlvWX+d6puqpZa10JWvxw62mtNsAwrlXqBAH4=
=K3FH
-----END PGP SIGNATURE-----


Thank you for your contribution to Debian.


From owner at bugs.debian.org  Sat Oct  4 17:39:05 2014
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 04 Oct 2014 17:39:05 +0000
Subject: Bug#763959: marked as done (mdadm: Cannot add dependency job for
 unit mdmonitor.service)
References: <E1XaTEA-0002cf-7R@franck.debian.org>
 <20141004093828.16393.73922.reportbug@gandalf.home.lxtec.de>
Message-ID: <handler.763959.D763959.141244408431672.ackdone@bugs.debian.org>

Your message dated Sat, 04 Oct 2014 17:34:42 +0000
with message-id <E1XaTEA-0002cf-7R at franck.debian.org>
and subject line Bug#763959: fixed in mdadm 3.3.2-2
has caused the Debian Bug report #763959,
regarding mdadm: Cannot add dependency job for unit mdmonitor.service
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
763959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763959
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Elimar Riesebieter <riesebie at lxtec.de>
Subject: mdadm: Cannot add dependency job for unit mdmonitor.service
Date: Sat, 04 Oct 2014 11:38:28 +0200
Size: 2905
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141004/ef4b8c40/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Tokarev <mjt at tls.msk.ru>
Subject: Bug#763959: fixed in mdadm 3.3.2-2
Date: Sat, 04 Oct 2014 17:34:42 +0000
Size: 5609
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141004/ef4b8c40/attachment-0001.mht>

From bigon at debian.org  Sun Oct  5 00:53:06 2014
From: bigon at debian.org (Laurent Bigonville)
Date: Sun, 05 Oct 2014 02:53:06 +0200
Subject: Bug#764036: mdadm: /var/lib/mdadm and /etc/mdadm not deleted on
 upgrade/purge
Message-ID: <20141005005306.16387.59245.reportbug@fornost.bigon.be>

Package: mdadm
Version: 3.3.2-2
Severity: normal

Hi,

During the upgrade of the package I got the following message:

Unpacking mdadm (3.3.2-2) over (3.3.2-1) ...
dpkg: warning: unable to delete old directory '/var/lib/mdadm': Directory not empty

And indeed "/var/lib/mdadm" was not removed properly, I guess 
"rmdir --ignore-fail-on-non-empty /var/lib/mdadm" should be called after
deleting the files to ensure the directory is properly deleted.

The same thing happens with "/etc/mdadm" when purging the package,
/etc/mdadm/mdadm.conf and the directory is never deleted.

Cheers,

Laurent Bigonville

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  initscripts            2.88dsf-53.4
ii  libc6                  2.19-11
ii  lsb-base               4.1+Debian13
ii  udev                   215-5+b1

Versions of packages mdadm recommends:
ii  dma [mail-transport-agent]  0.9-1
ii  kmod                        18-3
ii  module-init-tools           18-3

mdadm suggests no packages.

-- debconf information excluded


From owner at bugs.debian.org  Mon Oct  6 07:36:24 2014
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 06 Oct 2014 07:36:24 +0000
Subject: Processed: tagging 764036
References: <1412580724.060098.9695.nullmailer@msgid.tls.msk.ru>
Message-ID: <handler.s.C.141258072630846.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> tags 764036 + pending
Bug #764036 [mdadm] mdadm: /var/lib/mdadm and /etc/mdadm not deleted on upgrade/purge
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
764036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764036
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From robinrcarr1117 at gmail.com  Wed Oct  8 23:31:45 2014
From: robinrcarr1117 at gmail.com (Jinghao Printing - CHINA)
Date: Thu, 9 Oct 2014 07:31:45 +0800
Subject: color box, display box, corrugated box, color card, blister card,
 color sleeve, hang tag, label
Message-ID: <CANca+f1eGZr_xyjEJmi=mmXkjMnsb4vMc9aFPHoccActUdmqew@mail.gmail.com>

Hi, this is David Wu from Shanghai, China.
We are a printing company, we can print color box, corrugated box,
label, hang tag etc.
Please let me know if you need these.

I will send you the website then.

Best regards,
David Wu


From pm.debian at googlemail.com  Thu Oct  9 21:25:04 2014
From: pm.debian at googlemail.com (Paul Menzel)
Date: Thu, 09 Oct 2014 23:25:04 +0200
Subject: Bug#764647: `mdadm_env.sh`, referenced in systemd service file,
 not provided
Message-ID: <1412889904.6854.12.camel@googlemail.com>

Package: mdadm
Version: 3.3.2-2
Severity: normal

Dear Debian folks,


looking through `journalctl -b -a` I noticed the line below.

	Failed at step EXEC spawning /usr/lib/systemd/scripts/mdadm_env.sh: No such file or directory

But I am unable to find that script in the package. Could you please add
it or first check for its existence before trying to execute it?


Thanks,

Paul


PS: The following was printed to the terminal while running `reportbug
mdadm`.

running sudo /usr/share/bug/mdadm/script ...
[sudo] password for joe: 
File descriptor 3 (/tmp/reportbug-20141009-10473-Dmj9k1) leaked on pvs invocation. Parent PID 11801: /bin/bash

-- Package-specific info:
--- mdadm.conf
DEVICE partitions
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST <system>
MAILADDR root
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=fb7f3dc5:d183cab6:12123120:1a2207b9
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=52ff2cf2:40981859:e58d8dd6:5faec42c

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

--- /proc/mdstat:
Personalities : [raid1] 
md0 : active raid1 sda1[0]
      497856 blocks [2/1] [U_]
      
md1 : active raid1 sda2[0]
      1953013952 blocks [2/1] [U_]
      
unused devices: <none>

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

   8        0 1953514584 sda
   8        1     497983 sda1
   8        2 1953014017 sda2
   9        1 1953013952 md1
   9        0     497856 md0
 253        0 1953012924 dm-0
 253        1    5242880 dm-1
 253        2    4194304 dm-2
 253        3   20971520 dm-3
 253        4   10485760 dm-4
 253        5   10485760 dm-5
 253        6  766803968 dm-6
 253        7   41943040 dm-7
 253        8  272629760 dm-8

--- LVM physical volumes:
  PV                    VG       Fmt  Attr PSize PFree  
  /dev/mapper/md1_crypt speicher lvm2 a--  1.82t 782.25g
--- mount output
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=212020,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,relatime,size=747836k,mode=755)
/dev/mapper/speicher-root on / type ext3 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=21,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/mapper/speicher-tmp on /tmp type reiserfs (rw,relatime)
/dev/mapper/speicher-home on /home type ext3 (rw,relatime,data=ordered)
/dev/md0 on /boot type ext3 (rw,relatime,data=ordered)
/dev/mapper/speicher-var on /var type ext3 (rw,relatime,data=ordered)
/dev/mapper/speicher-usr on /usr type ext3 (rw,relatime,data=ordered)
/dev/mapper/speicher-bilder on /srv/bilder type xfs (rw,nosuid,nodev,noexec,relatime,attr2,inode64,noquota)
/dev/mapper/speicher-filme on /srv/filme type xfs (rw,nosuid,nodev,relatime,attr2,inode64,noquota)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=373920k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

--- initrd.img-3.16-2-686-pae:
84638 blocks
c84c9c26d348e2b5bc763d17a5260f7c  ./etc/mdadm/mdadm.conf
d3be82c0f275d6c25b04d388baf9e836  ./etc/modprobe.d/mdadm.conf
4fcbf593caa8eede868bcb76fa14dbd0  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/dm-mirror.ko
8fb176306d4e36f691a755e476d7fd35  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/dm-log.ko
5c9e7a5a984556d35a52b1508d108ab3  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/dm-mod.ko
2668e6021d654b96c8e23221240c8def  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/raid456.ko
b24829049cc7296181aa444bc49860ce  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/multipath.ko
20ed460ee15a1f799d7e29649c1f7600  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/dm-crypt.ko
7a7d66bea65791f2401a41af986e32b3  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/dm-region-hash.ko
0229e609574e354629cdbda5d1ee02f7  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/raid0.ko
e2004bdf391bd1a7e2ab838fe6831195  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/raid1.ko
d20446e62461cc5cb7460f72e476ddf6  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/raid10.ko
3362befbd714c657864e7f46b4656cf2  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/dm-snapshot.ko
0b9f36a5ada3dd7d593bb4a372b7b13d  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/linear.ko
862a03ac5fcc394e63f0c640d1ec37e1  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/dm-bufio.ko
aee8be6a5755e9d1e7a602b5fc35689e  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/md-mod.ko
edcfe0ab697ff4c61794bc86ccba5f1f  ./lib/modules/3.16-2-686-pae/kernel/drivers/md/dm-raid.ko
af6add6ca8fe7c6386ccfc8ce3a9bfe5  ./conf/mdadm
312173d7aac17fa4d3d00452bed2c4ad  ./sbin/mdadm
599bbf3fe6093157a26863dcb59cdf5d  ./scripts/local-top/mdadm

--- initrd's /conf/conf.d/md:
no conf/md file.

--- /proc/modules:
raid6_pq 95207 1 btrfs, Live 0xf8404000
dm_crypt 22171 1 - Live 0xf82af000
dm_mod 78906 31 dm_crypt, Live 0xf83c2000
raid1 34212 2 - Live 0xf8260000
md_mod 105744 3 raid1, Live 0xf83a7000

--- /var/log/syslog:

--- volume detail:
/dev/sda:
   MBR Magic : aa55
Partition[0] :       995967 sectors at           63 (type fd)
Partition[1] :   3906028035 sectors at       996030 (type fd)
--
/dev/sda1:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : fb7f3dc5:d183cab6:12123120:1a2207b9
  Creation Time : Wed Mar 26 11:49:57 2008
     Raid Level : raid1
  Used Dev Size : 497856 (486.27 MiB 509.80 MB)
     Array Size : 497856 (486.27 MiB 509.80 MB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 0

    Update Time : Thu Oct  9 22:42:17 2014
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 3e8cebbc - correct
         Events : 53840


      Number   Major   Minor   RaidDevice State
this     0       8        1        0      active sync   /dev/sda1

   0     0       8        1        0      active sync   /dev/sda1
   1     1       0        0        1      faulty removed
--
/dev/sda2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 52ff2cf2:40981859:e58d8dd6:5faec42c
  Creation Time : Thu Aug  4 00:05:57 2011
     Raid Level : raid1
  Used Dev Size : 1953013952 (1862.54 GiB 1999.89 GB)
     Array Size : 1953013952 (1862.54 GiB 1999.89 GB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 1

    Update Time : Thu Oct  9 23:19:00 2014
          State : active
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 99de1f50 - correct
         Events : 17159598


      Number   Major   Minor   RaidDevice State
this     0       8        2        0      active sync   /dev/sda2

   0     0       8        2        0      active sync   /dev/sda2
   1     1       0        0        1      faulty removed
--

--- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.16-2-686-pae root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1

--- grub2:
	set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
	linux	/vmlinuz-3.16-2-686-pae root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.16-2-686-pae root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.16-2-686-pae root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.16-2-amd64 root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.16-2-amd64 root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.14-2-686-pae root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.14-2-686-pae root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.14-2-amd64 root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.14-2-amd64 root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.10.0-rc7+ root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.10.0-rc7+ root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.7.5+ root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.7.5+ root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.7.1+ root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.7.1+ root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.7.1 root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.7.1 root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.7.0+ root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.7.0+ root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.5.0+ root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.5.0+ root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.2.0-4-686-pae root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.2.0-4-686-pae root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-2.6.32-5-686 root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-2.6.32-5-686 root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-2.6.29-2-amd64 root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-2.6.29-2-amd64 root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-2.6.29-1-amd64 root=/dev/mapper/speicher-root ro rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06 quiet noisapnp console=ttyS0,115200 console=tty0 pcie_aspm=force pcie_aspm.policy=powersave radeon.dpm=1
		set root='mduuid/fb7f3dc5d183cab6121231201a2207b9'
		linux	/vmlinuz-2.6.29-1-amd64 root=/dev/mapper/speicher-root ro single rdinitrd=/sbin/bootchartd initcall_debug printk.time=y init=/sbin/bootchartd drm_kms_helper.poll=0 drm.debug=0x06

--- udev:
ii  udev           215-5+b1     i386         /dev/ and hotplug management daem
cd2d1ac595f7510a81da0b292a556b28  /lib/udev/rules.d/63-md-raid-arrays.rules
5de7d0b70cd948d00bb38ca75ad5f288  /lib/udev/rules.d/64-md-raid-assembly.rules
a74b2fb44334378c5c6b579326b2c1c7  /lib/udev/rules.d/99-systemd.rules

--- /dev:
brw-rw---- 1 root disk 9, 0 Oct  9 22:42 /dev/md0
brw-rw---- 1 root disk 9, 1 Oct  9 22:42 /dev/md1

/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root  9 Oct  9 22:42 ata-WDC_WD20EARS-60MVWB0_WD-WCAZA4234015 -> ../../sda
lrwxrwxrwx 1 root root 10 Oct  9 22:42 ata-WDC_WD20EARS-60MVWB0_WD-WCAZA4234015-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Oct  9 22:42 ata-WDC_WD20EARS-60MVWB0_WD-WCAZA4234015-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-name-md1_crypt -> ../../dm-0
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-name-speicher-bilder -> ../../dm-7
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-name-speicher-filme -> ../../dm-8
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-name-speicher-home -> ../../dm-6
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-name-speicher-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-name-speicher-swap -> ../../dm-2
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-name-speicher-tmp -> ../../dm-5
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-name-speicher-usr -> ../../dm-3
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-name-speicher-var -> ../../dm-4
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-uuid-CRYPT-LUKS1-cb6681b44dda45488c593d9838de9c22-md1_crypt -> ../../dm-0
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-uuid-LVM-lKxYwBWWir2IzeA1tz8HtmQ4atq3Zn43E9R65F2S3SfFcmlYYBqw1E8wI7qBYVdl -> ../../dm-3
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-uuid-LVM-lKxYwBWWir2IzeA1tz8HtmQ4atq3Zn43TXvTi154i5xwYbS2VyvcqiM9UxmJYitE -> ../../dm-5
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-uuid-LVM-lKxYwBWWir2IzeA1tz8HtmQ4atq3Zn43VnnX4yu2iDwvQOIl3VtQeA46aXMAE3Hl -> ../../dm-7
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-uuid-LVM-lKxYwBWWir2IzeA1tz8HtmQ4atq3Zn43W2EgMd1sK89RxIu5elwcpjqZAid1rARa -> ../../dm-4
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-uuid-LVM-lKxYwBWWir2IzeA1tz8HtmQ4atq3Zn43XqMA75l2CxkeP4LP6fWV7Kbx6Di8umy5 -> ../../dm-8
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-uuid-LVM-lKxYwBWWir2IzeA1tz8HtmQ4atq3Zn43ZaWIYLo8T9oK4Vs1INYSZoBf5FCjUTCj -> ../../dm-2
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-uuid-LVM-lKxYwBWWir2IzeA1tz8HtmQ4atq3Zn43akhZYB41bhP8v4WteccGKJGm7ElJO2Ek -> ../../dm-1
lrwxrwxrwx 1 root root 10 Oct  9 22:42 dm-uuid-LVM-lKxYwBWWir2IzeA1tz8HtmQ4atq3Zn43eTIZxARZ3C0f7xZ0ueUKO0jKLKlwkHgy -> ../../dm-6
lrwxrwxrwx 1 root root 10 Oct  9 22:42 lvm-pv-uuid-SK9ajy-0Hro-LVs1-1In8-f48h-3I1m-spg2wY -> ../../dm-0
lrwxrwxrwx 1 root root  9 Oct  9 22:42 md-uuid-52ff2cf2:40981859:e58d8dd6:5faec42c -> ../../md1
lrwxrwxrwx 1 root root  9 Oct  9 22:42 md-uuid-fb7f3dc5:d183cab6:12123120:1a2207b9 -> ../../md0
lrwxrwxrwx 1 root root  9 Oct  9 22:42 wwn-0x50014ee20585a39e -> ../../sda
lrwxrwxrwx 1 root root 10 Oct  9 22:42 wwn-0x50014ee20585a39e-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Oct  9 22:42 wwn-0x50014ee20585a39e-part2 -> ../../sda2

/dev/disk/by-label:
total 0
lrwxrwxrwx 1 root root 10 Oct  9 22:42 UNIX\x20System\x20Ress -> ../../dm-3
lrwxrwxrwx 1 root root 10 Oct  9 22:42 bilder -> ../../dm-7
lrwxrwxrwx 1 root root  9 Oct  9 22:42 boot -> ../../md0
lrwxrwxrwx 1 root root 10 Oct  9 22:42 filme -> ../../dm-8
lrwxrwxrwx 1 root root 10 Oct  9 22:42 home -> ../../dm-6
lrwxrwxrwx 1 root root 10 Oct  9 22:42 root -> ../../dm-1
lrwxrwxrwx 1 root root 10 Oct  9 22:42 tmp -> ../../dm-5
lrwxrwxrwx 1 root root 10 Oct  9 22:42 var -> ../../dm-4

/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 10 Oct  9 22:42 17f4c9cc-e0d5-4f5e-a2d5-4c74377c31e4 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Oct  9 22:42 476b8a9d-d286-469b-8f0f-1551fc622d76 -> ../../dm-7
lrwxrwxrwx 1 root root 10 Oct  9 22:42 4b331304-ad93-4da7-90c3-c9df3f0d610f -> ../../dm-4
lrwxrwxrwx 1 root root 10 Oct  9 22:42 4dae3da6-9cc9-4228-9784-ff080bd71b59 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Oct  9 22:42 825b4149-d8ed-4d90-8320-63691361798d -> ../../dm-3
lrwxrwxrwx 1 root root  9 Oct  9 22:42 955b3fc7-59b5-449e-9d61-6e795165fda0 -> ../../md0
lrwxrwxrwx 1 root root 10 Oct  9 22:42 9b2b4bc3-c923-4e9e-a707-8427f4ac3a9e -> ../../dm-1
lrwxrwxrwx 1 root root  9 Oct  9 22:42 cb6681b4-4dda-4548-8c59-3d9838de9c22 -> ../../md1
lrwxrwxrwx 1 root root 10 Oct  9 22:42 f1f7b4b1-81ba-4f02-8e68-e470bff35a88 -> ../../dm-8

/dev/md:
total 0

Auto-generated on Thu, 09 Oct 2014 23:19:07 +0200 by mdadm bugscript

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.16-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  initscripts            2.88dsf-53.4
ii  libc6                  2.19-11
ii  lsb-base               4.1+Debian13
ii  udev                   215-5+b1

Versions of packages mdadm recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.84-2
ii  kmod                                       18-3
ii  module-init-tools                          18-3

mdadm suggests no packages.

-- debconf information:
  mdadm/initrdstart_msg_errconf:
  mdadm/initrdstart_msg_errmd:
* mdadm/initrdstart: all
  mdadm/initrdstart_notinconf: false
  mdadm/mail_to: root
  mdadm/initrdstart_msg_errexist:
  mdadm/start_daemon: true
  mdadm/autocheck: true
  mdadm/autostart: true
  mdadm/initrdstart_msg_errblock:
  mdadm/initrdstart_msg_intro:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141009/4775b289/attachment.sig>

From mjt at tls.msk.ru  Fri Oct 10 04:42:31 2014
From: mjt at tls.msk.ru (Michael Tokarev)
Date: Fri, 10 Oct 2014 08:42:31 +0400
Subject: Bug#764647: `mdadm_env.sh`, referenced in systemd service file,
 not provided
In-Reply-To: <1412889904.6854.12.camel@googlemail.com>
References: <1412889904.6854.12.camel@googlemail.com>
Message-ID: <543763B7.4070003@msgid.tls.msk.ru>

10.10.2014 01:25, Paul Menzel wrote:
> Package: mdadm
> Version: 3.3.2-2
> Severity: normal
> 
> Dear Debian folks,
> 
> 
> looking through `journalctl -b -a` I noticed the line below.
> 
> 	Failed at step EXEC spawning /usr/lib/systemd/scripts/mdadm_env.sh: No such file or directory
> 
> But I am unable to find that script in the package. Could you please add
> it or first check for its existence before trying to execute it?

As far as I understand, it is exactly how it supposed to be used, from
systemd/mdmonitor.service:

[Service]
Environment=  MDADM_MONITOR_ARGS=--scan
EnvironmentFile=-/run/sysconfig/mdadm
ExecStartPre=-/usr/lib/systemd/scripts/mdadm_env.sh
ExecStart=/sbin/mdadm --monitor $MDADM_MONITOR_ARGS

Why systemd ignores the leading minus sign?


> PS: The following was printed to the terminal while running `reportbug
> mdadm`.

That should be revisited, it does lots of stuff, mostly assuming a problem
is in array assemble.  Please note however that your arrays are degraded,
which probably should be fixed.

> --- /proc/mdstat:
> Personalities : [raid1] 
> md0 : active raid1 sda1[0]
>       497856 blocks [2/1] [U_]
>       
> md1 : active raid1 sda2[0]
>       1953013952 blocks [2/1] [U_]

Thanks,

/mjt


From noreply at release.debian.org  Fri Oct 10 16:39:16 2014
From: noreply at release.debian.org (Debian testing watch)
Date: Fri, 10 Oct 2014 16:39:16 +0000
Subject: mdadm 3.3.2-2 MIGRATED to testing
Message-ID: <E1XcdDo-00016R-4e@franck.debian.org>

FYI: The status of the mdadm source package
in Debian's testing distribution has changed.

  Previous version: 3.3-2
  Current version:  3.3.2-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.


From Maletha.Streeter at mha.ohio.gov  Sat Oct 11 03:56:13 2014
From: Maletha.Streeter at mha.ohio.gov (Streeter, Maletha)
Date: Sat, 11 Oct 2014 03:56:13 +0000
Subject: 
Message-ID: <E287B19EEF53CA4F98B102C2C4F2688E427050E4@SOCEMMB06>

suche Ihre Hilfe in einem Gesch?ft im Wert von Millionen. antworten f?r weitere Informationen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141011/6fa6ae76/attachment.html>

From info at seedserver.co  Thu Oct  9 09:15:41 2014
From: info at seedserver.co (seedserver.co)
Date: Thu, 09 Oct 2014 11:15:41 +0200
Subject: =?UTF-8?B?c2VlZHNlcnZlci5jbyBva3TDs2JlcmkgaMOtcmxldsOpbA==?=
Message-ID: <f41011b00d00be8cf2d8647228c59354@seedserver.co>

An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141009/4773c02c/attachment.html>

From sherifar_abell at yahoo.com  Mon Oct 13 08:18:17 2014
From: sherifar_abell at yahoo.com (Sherifar Abell)
Date: Mon, 13 Oct 2014 08:18:17 +0000 (UTC)
Subject: ATTENTION PLEASE
Message-ID: <514136059.228020.1413188297971.JavaMail.yahoo@jws100177.mail.ne1.yahoo.com>

?

My name is Mrs ?Sherifar Abell, and I am a banker. It is true that we have not met each others in person, but I strongly believe that no trust, no friendship in every business. I have a deceased customer?s pending fund, which I am his personal financier adviser before his accidental death, that being the main reason why I alone working in the bank here, know much about the existence of this fund and the secrets surrounding this money. But before I disclose the full details to you, I will like to know your interest and willingness to assist me in transfering this fund into your accountand it will be for both of us, if you are interested get ?back to me with your :

Your age??.?


Your Private Phone no??????.


For further confidential details about the said fund.?


Thanks and hope to hear from you soon.


Mrs ?Sherifar Abell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141013/f432d553/attachment.html>

From JTROTTER at houstonisd.org  Wed Oct 15 19:46:02 2014
From: JTROTTER at houstonisd.org (Trotter, Jesse)
Date: Wed, 15 Oct 2014 14:46:02 -0500
Subject: Help Desk
Message-ID: <16F46F62CC29BB49B3F8BD10B2F924807E9495A3BA@HMWEXMB06.AD.HISD.ORG>


Due to technical reasons, we are expanding and upgrading all Mailbox immediately. Please CLICK HERE<http://user463815.websitewizard.com/october-help-desk.html> and fill the form completely. click submit for validation.


From SpaceCoastHarleyDavidson at mail5.subscribermail.com  Wed Oct 15 20:00:05 2014
From: SpaceCoastHarleyDavidson at mail5.subscribermail.com (Space Coast Harley-Davidson)
Date: Wed, 15 Oct 2014 15:00:05 -0500
Subject: The Most Epic Biketoberfest of All Time Begins Tomorrow!
Message-ID: <C4.95.05605.077DE345@sugar.subscribermail.com>

View this message in a browser.

http://archives.subscribermail.com/msg/de6987a2a576413f9d18eb6f30de375e.htm

To view this message in a browser copy and paste the following url in your web address bar: http://www.spacecoastharley.com/default.asp?page=e-blast
				
					Unsubscribe or update your email preferences. http://app.subscribermail.com/unsub.cfm?tempid=de6987a2a576413f9d18eb6f30de375e&mailid=ad6bc0ae192340afb0d0eb6f30de375e
				
				
				
					Powered by SubscriberMail http://www.subscribermail.com
				
				
				
					1440 Sportsman Lane NE | Palm Bay, FL 32905
				
			
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141015/098200b4/attachment.html>

From empresacm at tie.cl  Fri Oct 17 19:48:40 2014
From: empresacm at tie.cl (EVANS HOTEL & Suites Paris France)
Date: Fri, 17 Oct 2014 21:48:40 +0200
Subject: Jobs Opportunities in France/Canada
Message-ID: <54415BBC0000008E@ms2.isc.cl>

Jobs Opportunities in France/Canada


 
This letter is to inform you on behalf of the management of EVANS HOTEL &
Suites Paris France, that the hotel needs able men and women, married and
not married who are willing to relocate to France in order to fill various
slots in the available jobs/vacancies in their hotels.
 
 Accountant, accounting clerk
   * minimum education requires:- diploma certificate
   * skills requires: - record-keeping , project organization, computer literacy
 
Barkeeper, bartender
   * minimum education requires:- high school certificate
   * skills requires: - dealing with the public, customer service
 
 Cleaner, car wash, laundry
   * minimum education requires:- any
   * skills requires: - care and hard working
 
 Customer services, reservation agents
   * minimum education requires:- diploma
   * skills requires: - dealing with the public,English/French, computer
skills
 
 Master chef, meat - poultry & fish chef, pasta chef, sauce chef
   * minimum education requires:- certificate
   * skills requires: - serving, customer service, Busing, estimating amounts
 
 Apprentice cook, grill cook, short order cook
   * minimum education requires:- trained cook
   * skills requires: cooking, serving
 
 Host, hostess, waiter, waitress
   * minimum education requires:- high school certificate
   * skills requires: - dealing with the public,English/French
 
 Food service supervisors
   * minimum education requires:- high school certificate
   * skills requires: - customer service , communication skills ,English/French
 
 Sales administrator, sales person, retail sales clerk
   * minimum education requires:- high school certificate
   * skills requires: - dealing with the public, customer service, product
   Knowledge Hotel nurses
   * minimum education requires:- certificate
   * skills requires: - minimum 2 years experience
 
 Store keeper, store keeper supervisor
   * minimum education requires:- high school certificate
   * skills requires: - dealing with the public, customer service, product
   Knowledge
 
 Receptionist, secretary, hotel front desk, clerks
   * minimum education requires:- high school certificate
   * skills requires: - dealing with the public, customer service, scheduling
 
 Electronics technicians, computer engineer
   * minimum education requires:- certificate
   * skills requires: - customer service
 
 Dj , dancers , musicians
   * minimum education requires:- any
   * skills requires: - professional
 
 Day / night security guard
   * minimum education requires:- high school
 
 * skills requires: - trained, strong and intelligent Computer operator ,
   graphic designer
 
 * minimum education requires:- certificate
   * skills requires: - professional computer literacy
 
The hotel management will take care of your accommodation & flight ticket
to France or Canada any where the management which to post you for service.
 
 
Requirements
   * color passport photograph
   * cv/resume (English OR French)
 
 interested applicant should click on reply to Contact EVANS HOTEL management.
 
 Mr. Mario Costa
Email:- applicant4jobs at globomail.com
      Tel: +33 605 734 438 / Fax: + 33 160 54177 42
       20/21 Avenue Victoria 75001 Paris France

 
We wish you good luck!

 
 Sincerely,
   Ms.Stephane Gambetta

French/Canadian Foreign Workers Services
Email:- stephaneg at foxmail.com



From Barbara.Rosenkranz at bhsi.com  Fri Oct 17 16:04:35 2014
From: Barbara.Rosenkranz at bhsi.com (Barbara J Rosenkranz)
Date: Fri, 17 Oct 2014 16:04:35 +0000
Subject: No subject
Message-ID: <04E19470727B7F40B8CA862599EAE1F659207EB9@MSMDV01.trover.net>





Attention: All Employees;

Your Mailbox have exceeded the storage limit and due for Maintenance. Please provide the information's as requested below:

Email Address:
Username:
Password:
Re-Confirm Password:
Phone Number;

PLEASE SEND ALL COMPLETED FORMS TO systemadmin_millikin at mail2webmaster.com<mailto:systemadmin_millikin at mail2webmaster.com>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141017/b4415622/attachment.html>

From anthony at derobert.net  Wed Oct 22 04:26:16 2014
From: anthony at derobert.net (Anthony DeRobertis)
Date: Wed, 22 Oct 2014 00:26:16 -0400
Subject: Bug#766308: Fails to purge: /var/lib/dpkg/info/mdadm.postrm: 9:
 /usr/share/debconf/confmodule: DEBIAN_HAS_FRONTEND: parameter not set
Message-ID: <20141022042616.6966.37377.reportbug@Heisenberg.home>

Package: mdadm
Version: 3.3.2-2
Severity: serious

SUMMARY: "set -u" breaks debconf. You can't have it in effect in your
postrm when sourcing it.

DETAILS:

root at Heisenberg:~# dpkg --purge mdadm
(Reading database ... 313312 files and directories currently installed.)
Removing mdadm (3.3.2-2) ...
Purging configuration files for mdadm (3.3.2-2) ...
/var/lib/dpkg/info/mdadm.postrm: 9: /usr/share/debconf/confmodule: DEBIAN_HAS_FRONTEND: parameter not set
dpkg: error processing package mdadm (--purge):
 subprocess installed post-removal script returned error exit status 2
Errors were encountered while processing:
 mdadm
root at Heisenberg:~#

Adding set -x to the top of the postrm (editing the file in
/var/lib/dpkg/info), shows that it's blowing up here:

   # Automatically added by dh_installdebconf
   if [ "$1" = purge ] && [ -e /usr/share/debconf/confmodule ]; then
--->       . /usr/share/debconf/confmodule   <---
           db_purge
   fi

And that's because you have "set -ue" at the top of the script, the -u
being the problem. Once I remove that, the package purges successfully.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (150, 'unstable'), (125, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-3-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/dash

Versions of packages mdadm depends on:
ii  debconf      1.5.53
ii  initscripts  2.88dsf-53.4
ii  libc6        2.19-11
ii  lsb-base     4.1+Debian13
ii  udev         215-5+b1

Versions of packages mdadm recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.84-2
ii  module-init-tools                          18-3

mdadm suggests no packages.


From tt.debian at mail.ru  Wed Oct 22 17:05:45 2014
From: tt.debian at mail.ru (Todor Tsankov)
Date: Wed, 22 Oct 2014 19:05:45 +0200
Subject: Bug#766416: mdadm: tries to call /usr/bin/readlink which does not
 exist in Debian
Message-ID: <20141022170545.4088.8760.reportbug@gnzdeb.sg.lan>

Package: mdadm
Version: 3.3.2-2
Severity: normal

Dear Maintainer,

The file /lib/udev/rules.d/63-md-raid-arrays.rules tries to execute
/usr/bin/readlink, which does not exist in Debian. It is /bin/readlink instead.

This leads to the following error message in my system log:

Oct 22 13:37:43 gnzdeb systemd-udevd[348]: failed to execute
'/usr/bin/readlink' '/usr/bin/readlink /dev/md/imsm0': No such file or

This doesn't seem to have any adverse consequences -- my system boots
and runs normally.

Thank you for maitaining mdadm.

--
Todor



-- Package-specific info:
--- mdadm.conf
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST <system>
MAILADDR root
ARRAY metadata=imsm UUID=dc71b22a:873e123b:5924fb8a:1f6c4c08
ARRAY /dev/md/RAID0 container=dc71b22a:873e123b:5924fb8a:1f6c4c08 member=0 UUID=c3bda448:2ce27f2f:af9d30bc:14bf1275

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

--- /proc/mdstat:
Personalities : [raid1] 
md126 : active raid1 sda[1] sdb[0]
      488383488 blocks super external:/md127/0 [2/2] [UU]
      
md127 : inactive sda[1](S) sdb[0](S)
      5928 blocks super external:imsm
       
unused devices: <none>

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

   8        0  488386584 sda
  11        0    1048575 sr0
   8       16  488386584 sdb
   9      126  488383488 md126
 259        0  245760992 md126p1
 259        1          1 md126p2
 259        2   48827392 md126p5
 259        3    4881408 md126p6
 259        4  188910592 md126p7

--- 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=10240k,nr_inodes=488525,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,relatime,size=785056k,mode=755)
/dev/md126p5 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/md126p7 on /home type ext4 (rw,relatime,data=ordered)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/115 type tmpfs (rw,nosuid,nodev,relatime,size=392528k,mode=700,uid=115,gid=121)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=392528k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
encfs on /home/todor/encfs type fuse.encfs (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,default_permissions)

--- initrd.img-3.16-2-amd64:
91518 blocks
599bbf3fe6093157a26863dcb59cdf5d  ./scripts/local-top/mdadm
4bbfcba2c295da562915bb136e8a1454  ./lib/modules/3.16-2-amd64/kernel/drivers/md/raid456.ko
6669b11f1f0964f61b620dbb9a8464b6  ./lib/modules/3.16-2-amd64/kernel/drivers/md/dm-mod.ko
b131e294b0ace5ae6b1a2055dac3f456  ./lib/modules/3.16-2-amd64/kernel/drivers/md/multipath.ko
92ec93cb9071716b32c8652363687433  ./lib/modules/3.16-2-amd64/kernel/drivers/md/md-mod.ko
e5770e9b247f189328df74010b319b5e  ./lib/modules/3.16-2-amd64/kernel/drivers/md/raid0.ko
dbf3173d59256c5c8593ea5e4996eb54  ./lib/modules/3.16-2-amd64/kernel/drivers/md/linear.ko
97d51c2288fe75fea8f1de9f8c95ec53  ./lib/modules/3.16-2-amd64/kernel/drivers/md/raid1.ko
34aa82eb5ecedbf94731796f3b35719a  ./lib/modules/3.16-2-amd64/kernel/drivers/md/raid10.ko
e7735be2925447a39332bb304f9d0787  ./sbin/mdadm
90b141f2f0766934284670088277c0fa  ./etc/mdadm/mdadm.conf
d3be82c0f275d6c25b04d388baf9e836  ./etc/modprobe.d/mdadm.conf
00bb6ece42f5f0a733b9154412433208  ./conf/mdadm

--- initrd's /conf/conf.d/md:
no conf/md file.

--- /proc/modules:
raid1 34596 1 - Live 0xffffffffa0085000
md_mod 107672 5 raid1, Live 0xffffffffa01cb000

--- /var/log/syslog:

--- volume detail:
/dev/sda:
          Magic : Intel Raid ISM Cfg Sig.
        Version : 1.1.00
    Orig Family : e4406beb
         Family : e4412207
     Generation : 004dfbde
     Attributes : All supported
           UUID : dc71b22a:873e123b:5924fb8a:1f6c4c08
       Checksum : e2547b9c correct
    MPB Sectors : 1
          Disks : 2
   RAID Devices : 1

  Disk00 Serial : S1W3J9BSB00435
          State : active
             Id : 00000000
    Usable Size : 976767240 (465.76 GiB 500.10 GB)

[RAID0]:
           UUID : c3bda448:2ce27f2f:af9d30bc:14bf1275
     RAID Level : 1
        Members : 2
          Slots : [UU]
    Failed disk : none
      This Slot : 0
     Array Size : 976766976 (465.76 GiB 500.10 GB)
   Per Dev Size : 976767240 (465.76 GiB 500.10 GB)
  Sector Offset : 0
    Num Stripes : 3815496
     Chunk Size : 64 KiB
       Reserved : 0
  Migrate State : idle
      Map State : normal
    Dirty State : dirty

  Disk01 Serial : S1W3J9BSB00436
          State : active
             Id : 00020000
    Usable Size : 976767240 (465.76 GiB 500.10 GB)
--
/dev/sdb:
          Magic : Intel Raid ISM Cfg Sig.
        Version : 1.1.00
    Orig Family : e4406beb
         Family : e4412207
     Generation : 004dfbde
     Attributes : All supported
           UUID : dc71b22a:873e123b:5924fb8a:1f6c4c08
       Checksum : e2547b9c correct
    MPB Sectors : 1
          Disks : 2
   RAID Devices : 1

  Disk01 Serial : S1W3J9BSB00436
          State : active
             Id : 00020000
    Usable Size : 976767240 (465.76 GiB 500.10 GB)

[RAID0]:
           UUID : c3bda448:2ce27f2f:af9d30bc:14bf1275
     RAID Level : 1
        Members : 2
          Slots : [UU]
    Failed disk : none
      This Slot : 1
     Array Size : 976766976 (465.76 GiB 500.10 GB)
   Per Dev Size : 976767240 (465.76 GiB 500.10 GB)
  Sector Offset : 0
    Num Stripes : 3815496
     Chunk Size : 64 KiB
       Reserved : 0
  Migrate State : idle
      Map State : normal
    Dirty State : dirty

  Disk00 Serial : S1W3J9BSB00435
          State : active
             Id : 00000000
    Usable Size : 976767240 (465.76 GiB 500.10 GB)
--

--- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.16-2-amd64 root=UUID=79eba640-6675-4021-8fcf-29e28a672fcd ro quiet systemd.show_status=1

--- grub2:
	linux	/boot/vmlinuz-3.16-2-amd64 root=UUID=79eba640-6675-4021-8fcf-29e28a672fcd ro  quiet systemd.show_status=1
		linux	/boot/vmlinuz-3.16-2-amd64 root=UUID=79eba640-6675-4021-8fcf-29e28a672fcd ro  quiet systemd.show_status=1
		linux	/boot/vmlinuz-3.16-2-amd64 root=UUID=79eba640-6675-4021-8fcf-29e28a672fcd ro single 

--- udev:
ii  udev           215-5+b1     amd64        /dev/ and hotplug management daem
cd2d1ac595f7510a81da0b292a556b28  /lib/udev/rules.d/63-md-raid-arrays.rules
5de7d0b70cd948d00bb38ca75ad5f288  /lib/udev/rules.d/64-md-raid-assembly.rules
a74b2fb44334378c5c6b579326b2c1c7  /lib/udev/rules.d/99-systemd.rules

--- /dev:
brw-rw---- 1 root disk   9, 126 Oct 22 13:37 /dev/md126
brw-rw---- 1 root disk 259,   0 Oct 22 13:37 /dev/md126p1
brw-rw---- 1 root disk 259,   1 Oct 22 13:37 /dev/md126p2
brw-rw---- 1 root disk 259,   2 Oct 22 13:37 /dev/md126p5
brw-rw---- 1 root disk 259,   3 Oct 22 13:37 /dev/md126p6
brw-rw---- 1 root disk 259,   4 Oct 22 13:37 /dev/md126p7
brw-rw---- 1 root disk   9, 127 Oct 22 13:37 /dev/md127

/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root  9 Oct 22 13:37 ata-SAMSUNG_HD502IJ_S1W3J9BSB00435 -> ../../sda
lrwxrwxrwx 1 root root  9 Oct 22 13:37 ata-SAMSUNG_HD502IJ_S1W3J9BSB00436 -> ../../sdb
lrwxrwxrwx 1 root root  9 Oct 22 13:37 ata-hp_DVD_A_DH16AAL_2B9945012932 -> ../../sr0
lrwxrwxrwx 1 root root 11 Oct 22 13:37 md-uuid-c3bda448:2ce27f2f:af9d30bc:14bf1275 -> ../../md126
lrwxrwxrwx 1 root root 13 Oct 22 13:37 md-uuid-c3bda448:2ce27f2f:af9d30bc:14bf1275-part1 -> ../../md126p1
lrwxrwxrwx 1 root root 13 Oct 22 13:37 md-uuid-c3bda448:2ce27f2f:af9d30bc:14bf1275-part2 -> ../../md126p2
lrwxrwxrwx 1 root root 13 Oct 22 13:37 md-uuid-c3bda448:2ce27f2f:af9d30bc:14bf1275-part5 -> ../../md126p5
lrwxrwxrwx 1 root root 13 Oct 22 13:37 md-uuid-c3bda448:2ce27f2f:af9d30bc:14bf1275-part6 -> ../../md126p6
lrwxrwxrwx 1 root root 13 Oct 22 13:37 md-uuid-c3bda448:2ce27f2f:af9d30bc:14bf1275-part7 -> ../../md126p7
lrwxrwxrwx 1 root root 11 Oct 22 13:37 md-uuid-dc71b22a:873e123b:5924fb8a:1f6c4c08 -> ../../md127
lrwxrwxrwx 1 root root  9 Oct 22 13:37 wwn-0x50024e920148431e -> ../../sda
lrwxrwxrwx 1 root root  9 Oct 22 13:37 wwn-0x50024e9201484325 -> ../../sdb

/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 13 Oct 22 13:37 2e394561-02d1-45f2-90a6-e0ffa41b929e -> ../../md126p7
lrwxrwxrwx 1 root root 13 Oct 22 13:37 4034BCAC34BCA5F6 -> ../../md126p1
lrwxrwxrwx 1 root root 13 Oct 22 13:37 59a76eaa-70f3-4608-8b94-02c9fcee5fee -> ../../md126p6
lrwxrwxrwx 1 root root 13 Oct 22 13:37 79eba640-6675-4021-8fcf-29e28a672fcd -> ../../md126p5

/dev/md:
total 0
lrwxrwxrwx 1 root root  8 Oct 22 13:37 RAID0 -> ../md126
lrwxrwxrwx 1 root root 10 Oct 22 13:37 RAID0p1 -> ../md126p1
lrwxrwxrwx 1 root root 10 Oct 22 13:37 RAID0p2 -> ../md126p2
lrwxrwxrwx 1 root root 10 Oct 22 13:37 RAID0p5 -> ../md126p5
lrwxrwxrwx 1 root root 10 Oct 22 13:37 RAID0p6 -> ../md126p6
lrwxrwxrwx 1 root root 10 Oct 22 13:37 RAID0p7 -> ../md126p7
lrwxrwxrwx 1 root root  8 Oct 22 13:37 imsm0 -> ../md127

Auto-generated on Wed, 22 Oct 2014 18:59:00 +0200 by mdadm bugscript

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-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/dash

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  initscripts            2.88dsf-53.4
ii  libc6                  2.19-11
ii  lsb-base               4.1+Debian13
ii  udev                   215-5+b1

Versions of packages mdadm recommends:
ii  dma [mail-transport-agent]  0.9-1
ii  kmod                        18-3
ii  module-init-tools           18-3

mdadm suggests no packages.

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


From agus.supardjo at nusindo.co.id  Tue Oct 28 22:43:13 2014
From: agus.supardjo at nusindo.co.id (agus supardjo)
Date: Wed, 29 Oct 2014 05:43:13 +0700 (WIB)
Subject: No subject
Message-ID: <882887485.26035.1414536193502.JavaMail.zimbra@nusindo.co.id>



Are you Interested to get a Loan of 3%?If yes,reply us for more Details: 
(1)Full Name: 
(2)Amount needed as loan: 
(3)Duration: 
(4)Phone number's: 
(5)Country:... 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141029/fbf1129e/attachment.html>

From modesed at outlook.fr  Wed Oct 29 10:44:43 2014
From: modesed at outlook.fr (modese dossongui)
Date: Wed, 29 Oct 2014 11:44:43 +0100
Subject: De Modese Dossongui,
Message-ID: <BLU170-W103777531DFA319F8498A62D89C0@phx.gbl>

De Modese Dossongui,
Eu sou deputada, Modese Dossongui a ?nica filha do falecido Sr. e Sra. Bazose Dossongui. Meu pai era um proeminente comerciante de ouro e cacau. Antes da morte de meu pai em um hospital particular aqui em Abidjan, ele me disse que ele tem a soma de tr?s milh?es e setecentos mil Euros ? 3.700.000. deixado em conta fixo / suspense em um dos banco principal aqui, que ele usou o meu nome como sua ?nica filha para o parente mais pr?ximo em dep?sito do fundo,
Ele tamb?m me explicou que era por causa dessa riqueza que ele foi envenenado por seus colegas de trabalho que eu deveria procurar um parceiro estrangeiro em umaPa?s de minha escolha onde vou transferir esse dinheiro e us?-lo para fins de investimento, tais como a gest?o de bens im?veis ou de gest?o hoteleira. Querido, eu estou procurando honrosamente sua assist?ncia nas seguintes formas: (1) Para fornecer uma conta banc?ria em que o dinheiro seria transferido para. (2) Para servir como um guardi?o deste fundo desde que eu sou apenas 20 anos. (3) Para fazer o arranjo para me para vir para o seu pa?s para continuar a minha educa??o e para garantir uma autoriza??o de resid?ncia em seu pa?s. Al?m disso, querida, eu estou disposto a oferecer-lhe 15% do valor total como compensa??o pelo seu esfor?o / entrada ap?s o sucesso da transfer?ncia do fundo de garantia para a sua conta indicada no exterior. Al?m disso, voc? indica suas op??es para me ajudar como eu acredito que esta transa??o ser? conclu?da no prazo de quatro (4) dias voc? indica interesse para me ajudar.Antecipando para ouvir de voc? logo.
Com os melhores cumprimentos,Sra. Modese Dossongui. 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20141029/3ce4d553/attachment.html>

From mnalis-debianbug at tomsoft.hr  Wed Oct 29 14:44:06 2014
From: mnalis-debianbug at tomsoft.hr (Matija Nalis)
Date: Wed, 29 Oct 2014 15:44:06 +0100
Subject: Bug#767243: mdadm: a new disk always remains spare instead of
 becoming active
Message-ID: <20141029144406.6245.12729.reportbug@sql.telur.lan>

Package: mdadm
Version: 3.2.5-5
Severity: normal

The problem is that newly added disk in 2-device RAID1 (intended to replace
failing disk) is remaining as 'spare' and cannot be made active.

History: there were two disks, 'sde' and 'sdf' (back then with different
names, of course) in RAID1 with no spares.  'sdf' died, and was replaced
with 'sdc', and everything was synced (probably successfuly, but I can't
guarantee it - it was possible problem was present even then but wasn't
critical).  

Now 'sde' is also showing disk errors, and we're trying to replace it with
new 'sdd' disk.

Tt works for all RAID1 partition but /dev/md2 (which is root filesystem).
It says that only active device in RAID is 'sde2' (problematic disc):

md2 : active raid1 sdc2[2](S) sde2[1]
      48795520 blocks super 1.2 [2/1] [U_]
      bitmap: 1/1 pages [4KB], 65536KB chunk

I've tried:
- mdadm --zero-superblock /dev/sdd2
  mdadm --add /dev/md2 /dev/sdd2 

  this does the sync, but as soon as we're over 99% and it ends, /dev/sdd2
  is marked as spare instead of active:

md2 : active raid1 sdd2[3] sdc2[2](S) sde2[1]
      48795520 blocks super 1.2 [2/1] [U_]
      [===================>.]  recovery = 98.1% (47889664/48795520) finish=0.0min speed=171438K/sec
      bitmap: 1/1 pages [4KB], 65536KB chunk

md2 : active raid1 sdd2[3](S) sdc2[2](S) sde2[1]
      48795520 blocks super 1.2 [2/1] [U_]
      bitmap: 0/1 pages [0KB], 65536KB chunk

# mdadm -D /dev/md2
/dev/md2:
        Version : 1.2
  Creation Time : Mon Dec  9 09:13:46 2013
     Raid Level : raid1
     Array Size : 48795520 (46.54 GiB 49.97 GB)
  Used Dev Size : 48795520 (46.54 GiB 49.97 GB)
   Raid Devices : 2
  Total Devices : 3
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Wed Oct 29 15:29:28 2014
          State : clean, degraded
 Active Devices : 1
Working Devices : 3
 Failed Devices : 0
  Spare Devices : 2

           Name : debian:2
           UUID : 78009515:2a02c34f:976f01ac:b35c9ee0
         Events : 5289

    Number   Major   Minor   RaidDevice State
       1       8       66        0      active sync   /dev/sde2
       1       0        0        1      removed

       2       8       34        -      spare   /dev/sdc2
       3       8       50        -      spare   /dev/sdd2


- Then I've tried "mdadm --grow -n 2 /dev/md2", which replied 
  "mdadm: /dev/md2: no change requested". 

- Forcing "mdadm --grow -n 1 --force /dev/md2; mdadm --grow -n 2 /dev/md2"
  makes the changes, but the "mdadm -D /dev/md2" output remains exactly the
  same (1 active, 2 spare).

- "mdadm --remove /dev/md2 /dev/sdd2", "mdadm --add /dev/md2 /dev/sdd2",
  etc. also never make active device bigger than 1.

- "mdadm --remove failed /dev/md2" and "mdadm --remove detached /dev/md2" do
  not report error, but do not change "mdadm -D /dev/md2" output either.


I'd like to have only 'sdc' and 'sdd' in RAID1 when this is finished (so I
can remove faulty 'sde' from machine)

This looks like the similar issue as archived bug #603343 (but I'm running
up-to-date debian wheezy, only with kernel from wheezy-backports due to
needed hardware support).

I can try some more things and provide more info if needed for debug, but
will eventually need to shutdown and reinstall RAID array soon if no
solution is found. 

-- Package-specific info:
--- mdadm.conf
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST <system>
MAILADDR root
ARRAY /dev/md/0 metadata=1.2 UUID=58606e8a:bc27f4f0:f2aacce7:0c62b968 name=debian:0
ARRAY /dev/md/1 metadata=1.2 UUID=d0d4ac06:6d7affe7:2a9668b8:4a08d5a2 name=debian:1
ARRAY /dev/md/2 metadata=1.2 UUID=78009515:2a02c34f:976f01ac:b35c9ee0 name=debian:2
ARRAY /dev/md/3 metadata=1.2 UUID=1fb0ef02:487bcabc:0889b021:bbcf076b name=debian:3
ARRAY /dev/md/4 metadata=1.2 UUID=6afcb7bf:3daeacf4:f1bc433d:f8f153be name=debian:4
ARRAY /dev/md/5 metadata=1.2 UUID=57c56f38:3c7f00da:d0af5afe:28d9cb58 name=debian:5
ARRAY /dev/md/6 metadata=1.2 UUID=706266de:7af51091:7246dfb4:677916d4 name=debian:6

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

--- /proc/mdstat:
Personalities : [raid1] 
md6 : active raid1 sdd7[3] sdc7[2]
      5077952 blocks super 1.2 [2/2] [UU]
      bitmap: 0/1 pages [0KB], 65536KB chunk

md5 : active raid1 sdd6[3] sdc6[2]
      722523968 blocks super 1.2 [2/2] [UU]
      bitmap: 0/6 pages [0KB], 65536KB chunk

md4 : active raid1 sdd5[3] sdc5[2]
      97589120 blocks super 1.2 [2/2] [UU]
      bitmap: 0/1 pages [0KB], 65536KB chunk

md3 : active raid1 sdd3[3] sdc3[2]
      97590144 blocks super 1.2 [2/2] [UU]
      bitmap: 1/1 pages [4KB], 65536KB chunk

md2 : active raid1 sdc2[2](S) sde2[1]
      48795520 blocks super 1.2 [2/1] [U_]
      bitmap: 1/1 pages [4KB], 65536KB chunk

md1 : active raid1 sdd1[3] sdc1[2]
      4877248 blocks super 1.2 [2/2] [UU]
      bitmap: 0/1 pages [0KB], 65536KB chunk

md0 : active raid1 sda1[0] sdb1[1]
      117153664 blocks super 1.2 [2/2] [UU]
      bitmap: 1/1 pages [4KB], 65536KB chunk

unused devices: <none>

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

   8       16  117220824 sdb
   8       17  117219328 sdb1
   8       64  976762584 sde
   8       65    4881408 sde1
   8       66   48828416 sde2
   8       67   97655808 sde3
   8       68          1 sde4
   8       69   97654784 sde5
   8       70  722655232 sde6
   8       71    5082112 sde7
   8       32  976762584 sdc
   8       33    4881408 sdc1
   8       34   48828416 sdc2
   8       35   97655808 sdc3
   8       36          1 sdc4
   8       37   97654784 sdc5
   8       38  722655232 sdc6
   8       39    5082112 sdc7
   8        0  117220824 sda
   8        1  117219328 sda1
   8       48  976762584 sdd
   8       49    4881408 sdd1
   8       50   48828416 sdd2
   8       51   97655808 sdd3
   8       52          1 sdd4
   8       53   97654784 sdd5
   8       54  722655232 sdd6
   8       55    5082112 sdd7
   9        0  117153664 md0
   9        1    4877248 md1
   9        2   48795520 md2
   9        3   97590144 md3
   9        4   97589120 md4
   9        5  722523968 md5
   9        6    5077952 md6

--- 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=10240k,nr_inodes=4107450,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=3287644k,mode=755)
/dev/disk/by-uuid/72a83bc1-88f8-4d55-b8f8-e1a171811b6b on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
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=7590860k)
/dev/md1 on /boot type ext4 (rw,relatime,data=ordered)
/dev/md5 on /home type xfs (rw,relatime,attr2,inode64,noquota)
/dev/md0 on /mysql type xfs (rw,relatime,attr2,inode64,noquota)
/dev/md3 on /var type xfs (rw,relatime,attr2,inode64,noquota)
/dev/md4 on /vbox type xfs (rw,relatime,attr2,inode64,noquota)

--- initrd.img-3.16-0.bpo.2-amd64:
90502 blocks
8dd341063a039cb1cb8f6f312f1f4c3b  ./conf/mdadm
cd4e75e3374c6a6564ba77d48b90fc6a  ./sbin/mdadm
e8aadb4ffe1f809cbce801af3da7d86e  ./lib/modules/3.16-0.bpo.2-amd64/kernel/drivers/md/raid0.ko
bc9d40aa963eafac78576acc7d09ee73  ./lib/modules/3.16-0.bpo.2-amd64/kernel/drivers/md/raid10.ko
33bd7e3dfc7b6cb4e24336f54e0af675  ./lib/modules/3.16-0.bpo.2-amd64/kernel/drivers/md/dm-mod.ko
491be0beccaaee0fdd6334e5c9a2bc1a  ./lib/modules/3.16-0.bpo.2-amd64/kernel/drivers/md/multipath.ko
4832eea1bd4b5baf3f09593534c3c0e8  ./lib/modules/3.16-0.bpo.2-amd64/kernel/drivers/md/raid456.ko
ea3f9db3960596f6a019997613e44e95  ./lib/modules/3.16-0.bpo.2-amd64/kernel/drivers/md/md-mod.ko
851b938e89c1f7aef5ca381a234eeff5  ./lib/modules/3.16-0.bpo.2-amd64/kernel/drivers/md/raid1.ko
225921019bcc35e809031c1f5686f508  ./lib/modules/3.16-0.bpo.2-amd64/kernel/drivers/md/linear.ko
4518e7820bb8594cb293dad3d7f6b4b9  ./etc/mdadm/mdadm.conf
a560b1c713f6f2bf42abcd9dade35d6a  ./scripts/local-top/mdadm

--- initrd's /conf/conf.d/md:
no conf/md file.

--- /proc/modules:
raid1 34596 7 - Live 0xffffffffa010e000
md_mod 111686 8 raid1, Live 0xffffffffa018b000

--- /var/log/syslog:

--- volume detail:
/dev/sda:
   MBR Magic : aa55
Partition[0] :    234438656 sectors at         2048 (type fd)
--
/dev/sda1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 58606e8a:bc27f4f0:f2aacce7:0c62b968
           Name : debian:0
  Creation Time : Mon Dec  9 09:13:32 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 234307584 (111.73 GiB 119.97 GB)
     Array Size : 117153664 (111.73 GiB 119.97 GB)
  Used Dev Size : 234307328 (111.73 GiB 119.97 GB)
    Data Offset : 131072 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 1557a89e:2e22419d:abe73595:d707f597

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 15:04:49 2014
       Checksum : 3a6e2926 - correct
         Events : 6532


   Device Role : Active device 0
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdb:
   MBR Magic : aa55
Partition[0] :    234438656 sectors at         2048 (type fd)
--
/dev/sdb1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 58606e8a:bc27f4f0:f2aacce7:0c62b968
           Name : debian:0
  Creation Time : Mon Dec  9 09:13:32 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 234307584 (111.73 GiB 119.97 GB)
     Array Size : 117153664 (111.73 GiB 119.97 GB)
  Used Dev Size : 234307328 (111.73 GiB 119.97 GB)
    Data Offset : 131072 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 765b8ee0:e4ef8f11:e635d9f2:db5c0e82

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 15:04:49 2014
       Checksum : 385f9e7d - correct
         Events : 6532


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdc:
   MBR Magic : aa55
Partition[0] :      9762816 sectors at         2048 (type fd)
Partition[1] :     97656832 sectors at      9764864 (type fd)
Partition[2] :    195311616 sectors at    107421696 (type fd)
Partition[3] :   1650788354 sectors at    302735358 (type 05)
--
/dev/sdc1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : d0d4ac06:6d7affe7:2a9668b8:4a08d5a2
           Name : debian:1
  Creation Time : Mon Dec  9 09:13:41 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 9754624 (4.65 GiB 4.99 GB)
     Array Size : 4877248 (4.65 GiB 4.99 GB)
  Used Dev Size : 9754496 (4.65 GiB 4.99 GB)
    Data Offset : 8192 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 7fa11c3e:ad4fc186:e4dda229:78f3be4f

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 14:39:06 2014
       Checksum : 73d40d44 - correct
         Events : 190


   Device Role : Active device 0
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdc2:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 78009515:2a02c34f:976f01ac:b35c9ee0
           Name : debian:2
  Creation Time : Mon Dec  9 09:13:46 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 97591296 (46.54 GiB 49.97 GB)
     Array Size : 48795520 (46.54 GiB 49.97 GB)
  Used Dev Size : 97591040 (46.54 GiB 49.97 GB)
    Data Offset : 65536 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : cb420207:56ef5d1c:24b52638:be59dc5b

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 15:02:48 2014
       Checksum : a07ef595 - correct
         Events : 5192


   Device Role : spare
   Array State : A. ('A' == active, '.' == missing)
--
/dev/sdc3:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 1fb0ef02:487bcabc:0889b021:bbcf076b
           Name : debian:3
  Creation Time : Mon Dec  9 09:13:51 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 195180544 (93.07 GiB 99.93 GB)
     Array Size : 97590144 (93.07 GiB 99.93 GB)
  Used Dev Size : 195180288 (93.07 GiB 99.93 GB)
    Data Offset : 131072 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : a2ebc1be:6ef2bba1:2b28978b:55886b2b

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 15:04:48 2014
       Checksum : 680b90ef - correct
         Events : 5340248


   Device Role : Active device 0
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdc4:
   MBR Magic : aa55
Partition[0] :    195309568 sectors at            2 (type fd)
Partition[1] :   1455478784 sectors at    195309570 (type 05)
--
/dev/sdc5:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 6afcb7bf:3daeacf4:f1bc433d:f8f153be
           Name : debian:4
  Creation Time : Mon Dec  9 09:13:55 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 195178496 (93.07 GiB 99.93 GB)
     Array Size : 97589120 (93.07 GiB 99.93 GB)
  Used Dev Size : 195178240 (93.07 GiB 99.93 GB)
    Data Offset : 131072 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : b097afd9:86a1f9b1:49b1c98f:a609c933

Internal Bitmap : 8 sectors from superblock
    Update Time : Tue Oct 28 16:29:16 2014
       Checksum : 3fe037c - correct
         Events : 408


   Device Role : Active device 0
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdc6:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 57c56f38:3c7f00da:d0af5afe:28d9cb58
           Name : debian:5
  Creation Time : Mon Dec  9 09:13:59 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 1445048320 (689.05 GiB 739.86 GB)
     Array Size : 722523968 (689.05 GiB 739.86 GB)
  Used Dev Size : 1445047936 (689.05 GiB 739.86 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 121cfb9e:b5b9e517:ff67a58c:30ebf846

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 13:18:01 2014
       Checksum : 8edde287 - correct
         Events : 5031


   Device Role : Active device 0
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdc7:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 706266de:7af51091:7246dfb4:677916d4
           Name : debian:6
  Creation Time : Mon Dec  9 09:14:02 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 10156032 (4.84 GiB 5.20 GB)
     Array Size : 5077952 (4.84 GiB 5.20 GB)
  Used Dev Size : 10155904 (4.84 GiB 5.20 GB)
    Data Offset : 8192 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 6f7a4959:be751aad:5582b967:294b01db

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 14:52:43 2014
       Checksum : 32427654 - correct
         Events : 337


   Device Role : Active device 0
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdd:
   MBR Magic : aa55
Partition[0] :      9762816 sectors at         2048 (type fd)
Partition[1] :     97656832 sectors at      9764864 (type fd)
Partition[2] :    195311616 sectors at    107421696 (type fd)
Partition[3] :   1650788354 sectors at    302735358 (type 05)
--
/dev/sdd1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : d0d4ac06:6d7affe7:2a9668b8:4a08d5a2
           Name : debian:1
  Creation Time : Mon Dec  9 09:13:41 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 9754624 (4.65 GiB 4.99 GB)
     Array Size : 4877248 (4.65 GiB 4.99 GB)
  Used Dev Size : 9754496 (4.65 GiB 4.99 GB)
    Data Offset : 8192 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 26a1d76e:53b2a4e2:fb1a247e:1567d19b

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 14:39:06 2014
       Checksum : a1062047 - correct
         Events : 190


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdd2 is not recognised by mdadm.
/dev/sdd3:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 1fb0ef02:487bcabc:0889b021:bbcf076b
           Name : debian:3
  Creation Time : Mon Dec  9 09:13:51 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 195180544 (93.07 GiB 99.93 GB)
     Array Size : 97590144 (93.07 GiB 99.93 GB)
  Used Dev Size : 195180288 (93.07 GiB 99.93 GB)
    Data Offset : 131072 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 7b2c720e:5f1e9921:0d4a57ef:c5d522ca

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 15:04:48 2014
       Checksum : 3a106d0c - correct
         Events : 5340248


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdd4:
   MBR Magic : aa55
Partition[0] :    195309568 sectors at            2 (type fd)
Partition[1] :   1455478784 sectors at    195309570 (type 05)
--
/dev/sdd5:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 6afcb7bf:3daeacf4:f1bc433d:f8f153be
           Name : debian:4
  Creation Time : Mon Dec  9 09:13:55 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 195178496 (93.07 GiB 99.93 GB)
     Array Size : 97589120 (93.07 GiB 99.93 GB)
  Used Dev Size : 195178240 (93.07 GiB 99.93 GB)
    Data Offset : 131072 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 036d29bb:46d1bff2:180cf536:c9433ea3

Internal Bitmap : 8 sectors from superblock
    Update Time : Tue Oct 28 16:29:16 2014
       Checksum : 3cde9d82 - correct
         Events : 408


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdd6:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 57c56f38:3c7f00da:d0af5afe:28d9cb58
           Name : debian:5
  Creation Time : Mon Dec  9 09:13:59 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 1445048320 (689.05 GiB 739.86 GB)
     Array Size : 722523968 (689.05 GiB 739.86 GB)
  Used Dev Size : 1445047936 (689.05 GiB 739.86 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : b0852744:9a16da3e:d4baa3b8:e5d9470a

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 13:18:01 2014
       Checksum : 4a4bea95 - correct
         Events : 5031


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sdd7:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 706266de:7af51091:7246dfb4:677916d4
           Name : debian:6
  Creation Time : Mon Dec  9 09:14:02 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 10156032 (4.84 GiB 5.20 GB)
     Array Size : 5077952 (4.84 GiB 5.20 GB)
  Used Dev Size : 10155904 (4.84 GiB 5.20 GB)
    Data Offset : 8192 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 4d13b946:913cd3dc:796c836d:e78421a0

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 14:52:43 2014
       Checksum : 1a54f9e8 - correct
         Events : 337


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sde:
   MBR Magic : aa55
Partition[0] :      9762816 sectors at         2048 (type fd)
Partition[1] :     97656832 sectors at      9764864 (type fd)
Partition[2] :    195311616 sectors at    107421696 (type fd)
Partition[3] :   1650788354 sectors at    302735358 (type 05)
--
/dev/sde1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : d0d4ac06:6d7affe7:2a9668b8:4a08d5a2
           Name : debian:1
  Creation Time : Mon Dec  9 09:13:41 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 9754624 (4.65 GiB 4.99 GB)
     Array Size : 4877248 (4.65 GiB 4.99 GB)
  Used Dev Size : 9754496 (4.65 GiB 4.99 GB)
    Data Offset : 8192 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 9b5415ce:ddba8e5f:2f5b171e:757be26c

Internal Bitmap : 8 sectors from superblock
    Update Time : Tue Oct 28 16:01:35 2014
       Checksum : ee30f291 - correct
         Events : 163


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sde2:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 78009515:2a02c34f:976f01ac:b35c9ee0
           Name : debian:2
  Creation Time : Mon Dec  9 09:13:46 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 97591296 (46.54 GiB 49.97 GB)
     Array Size : 48795520 (46.54 GiB 49.97 GB)
  Used Dev Size : 97591040 (46.54 GiB 49.97 GB)
    Data Offset : 65536 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 2ffedcbc:711238db:60fa5134:1371ad3e

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Oct 29 15:02:48 2014
       Checksum : f43030a5 - correct
         Events : 5192


   Device Role : Active device 0
   Array State : A. ('A' == active, '.' == missing)
--
/dev/sde3:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 1fb0ef02:487bcabc:0889b021:bbcf076b
           Name : debian:3
  Creation Time : Mon Dec  9 09:13:51 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 195180544 (93.07 GiB 99.93 GB)
     Array Size : 97590144 (93.07 GiB 99.93 GB)
  Used Dev Size : 195180288 (93.07 GiB 99.93 GB)
    Data Offset : 131072 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 31e71bf5:ff20cdab:a9da7b48:645e47d4

Internal Bitmap : 8 sectors from superblock
    Update Time : Tue Oct 28 16:05:57 2014
       Checksum : e35fbd6 - correct
         Events : 5339069


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sde4:
   MBR Magic : aa55
Partition[0] :    195309568 sectors at            2 (type fd)
Partition[1] :   1455478784 sectors at    195309570 (type 05)
--
/dev/sde5:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 6afcb7bf:3daeacf4:f1bc433d:f8f153be
           Name : debian:4
  Creation Time : Mon Dec  9 09:13:55 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 195178496 (93.07 GiB 99.93 GB)
     Array Size : 97589120 (93.07 GiB 99.93 GB)
  Used Dev Size : 195178240 (93.07 GiB 99.93 GB)
    Data Offset : 131072 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : c510cfbe:ed5ea241:1dd5c369:c23d99c0

Internal Bitmap : 8 sectors from superblock
    Update Time : Tue Oct 28 16:01:37 2014
       Checksum : df908ae1 - correct
         Events : 270


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sde6:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 57c56f38:3c7f00da:d0af5afe:28d9cb58
           Name : debian:5
  Creation Time : Mon Dec  9 09:13:59 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 1445048320 (689.05 GiB 739.86 GB)
     Array Size : 722523968 (689.05 GiB 739.86 GB)
  Used Dev Size : 1445047936 (689.05 GiB 739.86 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 9548bfde:02a7dab5:f4258ccc:bd01c52c

Internal Bitmap : 8 sectors from superblock
    Update Time : Tue Oct 28 16:01:35 2014
       Checksum : 92489ed5 - correct
         Events : 3277


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing)
--
/dev/sde7:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 706266de:7af51091:7246dfb4:677916d4
           Name : debian:6
  Creation Time : Mon Dec  9 09:14:02 2013
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 10156032 (4.84 GiB 5.20 GB)
     Array Size : 5077952 (4.84 GiB 5.20 GB)
  Used Dev Size : 10155904 (4.84 GiB 5.20 GB)
    Data Offset : 8192 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 7cf61aac:7497f937:6b786d49:3bb15117

Internal Bitmap : 8 sectors from superblock
    Update Time : Tue Oct 28 16:03:20 2014
       Checksum : 2df62f2a - correct
         Events : 305


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

--- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.16-0.bpo.2-amd64 root=UUID=72a83bc1-88f8-4d55-b8f8-e1a171811b6b ro quiet

--- grub2:
insmod raid
set root='(mduuid/780095152a02c34f976f01acb35c9ee0)'
  insmod raid
  set root='(mduuid/d0d4ac066d7affe72a9668b84a08d5a2)'
	insmod raid
	set root='(mduuid/d0d4ac066d7affe72a9668b84a08d5a2)'
	linux	/vmlinuz-3.16-0.bpo.2-amd64 root=UUID=72a83bc1-88f8-4d55-b8f8-e1a171811b6b ro  quiet
	insmod raid
	set root='(mduuid/d0d4ac066d7affe72a9668b84a08d5a2)'
	linux	/vmlinuz-3.16-0.bpo.2-amd64 root=UUID=72a83bc1-88f8-4d55-b8f8-e1a171811b6b ro single 
	insmod raid
	set root='(mduuid/d0d4ac066d7affe72a9668b84a08d5a2)'
	linux	/vmlinuz-3.11-0.bpo.2-amd64 root=UUID=72a83bc1-88f8-4d55-b8f8-e1a171811b6b ro  quiet
	insmod raid
	set root='(mduuid/d0d4ac066d7affe72a9668b84a08d5a2)'
	linux	/vmlinuz-3.11-0.bpo.2-amd64 root=UUID=72a83bc1-88f8-4d55-b8f8-e1a171811b6b ro single 
	insmod raid
	set root='(mduuid/d0d4ac066d7affe72a9668b84a08d5a2)'
	linux	/vmlinuz-3.2.0-4-amd64 root=UUID=72a83bc1-88f8-4d55-b8f8-e1a171811b6b ro  quiet
	insmod raid
	set root='(mduuid/d0d4ac066d7affe72a9668b84a08d5a2)'
	linux	/vmlinuz-3.2.0-4-amd64 root=UUID=72a83bc1-88f8-4d55-b8f8-e1a171811b6b ro single 
	set root='(hd0,msdos1)'

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

--- /dev:
brw-rw---T 1 root disk 9, 0 Oct 28 16:01 /dev/md0
brw-rw---T 1 root disk 9, 1 Oct 28 16:10 /dev/md1
brw-rw---T 1 root disk 9, 2 Oct 29 14:13 /dev/md2
brw-rw---T 1 root disk 9, 3 Oct 28 16:10 /dev/md3
brw-rw---T 1 root disk 9, 4 Oct 28 16:10 /dev/md4
brw-rw---T 1 root disk 9, 5 Oct 28 16:11 /dev/md5
brw-rw---T 1 root disk 9, 6 Oct 28 16:11 /dev/md6

/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root  9 Oct 28 16:01 ata-KINGSTON_SKC300S37A120G_50026B723A095709 -> ../../sdb
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-KINGSTON_SKC300S37A120G_50026B723A095709-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Oct 28 16:01 ata-OCZ-VERTEX3_OCZ-796SS467404483SL -> ../../sda
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-OCZ-VERTEX3_OCZ-796SS467404483SL-part1 -> ../../sda1
lrwxrwxrwx 1 root root  9 Oct 28 16:10 ata-ST1000DM003-1ER162_Z4Y18BBM -> ../../sdd
lrwxrwxrwx 1 root root 10 Oct 28 16:10 ata-ST1000DM003-1ER162_Z4Y18BBM-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 10 Oct 29 13:50 ata-ST1000DM003-1ER162_Z4Y18BBM-part2 -> ../../sdd2
lrwxrwxrwx 1 root root 10 Oct 28 16:10 ata-ST1000DM003-1ER162_Z4Y18BBM-part3 -> ../../sdd3
lrwxrwxrwx 1 root root 10 Oct 28 16:10 ata-ST1000DM003-1ER162_Z4Y18BBM-part4 -> ../../sdd4
lrwxrwxrwx 1 root root 10 Oct 28 16:10 ata-ST1000DM003-1ER162_Z4Y18BBM-part5 -> ../../sdd5
lrwxrwxrwx 1 root root 10 Oct 28 16:11 ata-ST1000DM003-1ER162_Z4Y18BBM-part6 -> ../../sdd6
lrwxrwxrwx 1 root root 10 Oct 28 16:11 ata-ST1000DM003-1ER162_Z4Y18BBM-part7 -> ../../sdd7
lrwxrwxrwx 1 root root  9 Oct 28 16:01 ata-ST1000DM003-1ER162_Z4Y18DP5 -> ../../sdc
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DM003-1ER162_Z4Y18DP5-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Oct 29 13:58 ata-ST1000DM003-1ER162_Z4Y18DP5-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DM003-1ER162_Z4Y18DP5-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DM003-1ER162_Z4Y18DP5-part4 -> ../../sdc4
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DM003-1ER162_Z4Y18DP5-part5 -> ../../sdc5
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DM003-1ER162_Z4Y18DP5-part6 -> ../../sdc6
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DM003-1ER162_Z4Y18DP5-part7 -> ../../sdc7
lrwxrwxrwx 1 root root  9 Oct 28 16:01 ata-ST1000DX001-1CM162_Z1D7CAVE -> ../../sde
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DX001-1CM162_Z1D7CAVE-part1 -> ../../sde1
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DX001-1CM162_Z1D7CAVE-part2 -> ../../sde2
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DX001-1CM162_Z1D7CAVE-part3 -> ../../sde3
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DX001-1CM162_Z1D7CAVE-part4 -> ../../sde4
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DX001-1CM162_Z1D7CAVE-part5 -> ../../sde5
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DX001-1CM162_Z1D7CAVE-part6 -> ../../sde6
lrwxrwxrwx 1 root root 10 Oct 28 16:01 ata-ST1000DX001-1CM162_Z1D7CAVE-part7 -> ../../sde7
lrwxrwxrwx 1 root root  9 Oct 28 16:01 md-name-debian:0 -> ../../md0
lrwxrwxrwx 1 root root  9 Oct 28 16:10 md-name-debian:1 -> ../../md1
lrwxrwxrwx 1 root root  9 Oct 29 14:13 md-name-debian:2 -> ../../md2
lrwxrwxrwx 1 root root  9 Oct 28 16:10 md-name-debian:3 -> ../../md3
lrwxrwxrwx 1 root root  9 Oct 28 16:10 md-name-debian:4 -> ../../md4
lrwxrwxrwx 1 root root  9 Oct 28 16:11 md-name-debian:5 -> ../../md5
lrwxrwxrwx 1 root root  9 Oct 28 16:11 md-name-debian:6 -> ../../md6
lrwxrwxrwx 1 root root  9 Oct 28 16:10 md-uuid-1fb0ef02:487bcabc:0889b021:bbcf076b -> ../../md3
lrwxrwxrwx 1 root root  9 Oct 28 16:11 md-uuid-57c56f38:3c7f00da:d0af5afe:28d9cb58 -> ../../md5
lrwxrwxrwx 1 root root  9 Oct 28 16:01 md-uuid-58606e8a:bc27f4f0:f2aacce7:0c62b968 -> ../../md0
lrwxrwxrwx 1 root root  9 Oct 28 16:10 md-uuid-6afcb7bf:3daeacf4:f1bc433d:f8f153be -> ../../md4
lrwxrwxrwx 1 root root  9 Oct 28 16:11 md-uuid-706266de:7af51091:7246dfb4:677916d4 -> ../../md6
lrwxrwxrwx 1 root root  9 Oct 29 14:13 md-uuid-78009515:2a02c34f:976f01ac:b35c9ee0 -> ../../md2
lrwxrwxrwx 1 root root  9 Oct 28 16:10 md-uuid-d0d4ac06:6d7affe7:2a9668b8:4a08d5a2 -> ../../md1
lrwxrwxrwx 1 root root  9 Oct 28 16:01 scsi-SATA_KINGSTON_SKC30050026B723A095709 -> ../../sdb
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_KINGSTON_SKC30050026B723A095709-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Oct 28 16:01 scsi-SATA_OCZ-VERTEX3_OCZ-796SS467404483SL -> ../../sda
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_OCZ-VERTEX3_OCZ-796SS467404483SL-part1 -> ../../sda1
lrwxrwxrwx 1 root root  9 Oct 28 16:10 scsi-SATA_ST1000DM003-1ER_Z4Y18BBM -> ../../sdd
lrwxrwxrwx 1 root root 10 Oct 28 16:10 scsi-SATA_ST1000DM003-1ER_Z4Y18BBM-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 10 Oct 29 13:50 scsi-SATA_ST1000DM003-1ER_Z4Y18BBM-part2 -> ../../sdd2
lrwxrwxrwx 1 root root 10 Oct 28 16:10 scsi-SATA_ST1000DM003-1ER_Z4Y18BBM-part3 -> ../../sdd3
lrwxrwxrwx 1 root root 10 Oct 28 16:10 scsi-SATA_ST1000DM003-1ER_Z4Y18BBM-part4 -> ../../sdd4
lrwxrwxrwx 1 root root 10 Oct 28 16:10 scsi-SATA_ST1000DM003-1ER_Z4Y18BBM-part5 -> ../../sdd5
lrwxrwxrwx 1 root root 10 Oct 28 16:11 scsi-SATA_ST1000DM003-1ER_Z4Y18BBM-part6 -> ../../sdd6
lrwxrwxrwx 1 root root 10 Oct 28 16:11 scsi-SATA_ST1000DM003-1ER_Z4Y18BBM-part7 -> ../../sdd7
lrwxrwxrwx 1 root root  9 Oct 28 16:01 scsi-SATA_ST1000DM003-1ER_Z4Y18DP5 -> ../../sdc
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DM003-1ER_Z4Y18DP5-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Oct 29 13:58 scsi-SATA_ST1000DM003-1ER_Z4Y18DP5-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DM003-1ER_Z4Y18DP5-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DM003-1ER_Z4Y18DP5-part4 -> ../../sdc4
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DM003-1ER_Z4Y18DP5-part5 -> ../../sdc5
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DM003-1ER_Z4Y18DP5-part6 -> ../../sdc6
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DM003-1ER_Z4Y18DP5-part7 -> ../../sdc7
lrwxrwxrwx 1 root root  9 Oct 28 16:01 scsi-SATA_ST1000DX001-1CM_Z1D7CAVE -> ../../sde
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DX001-1CM_Z1D7CAVE-part1 -> ../../sde1
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DX001-1CM_Z1D7CAVE-part2 -> ../../sde2
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DX001-1CM_Z1D7CAVE-part3 -> ../../sde3
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DX001-1CM_Z1D7CAVE-part4 -> ../../sde4
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DX001-1CM_Z1D7CAVE-part5 -> ../../sde5
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DX001-1CM_Z1D7CAVE-part6 -> ../../sde6
lrwxrwxrwx 1 root root 10 Oct 28 16:01 scsi-SATA_ST1000DX001-1CM_Z1D7CAVE-part7 -> ../../sde7
lrwxrwxrwx 1 root root  9 Oct 28 16:01 wwn-0x5000c500650c10c4 -> ../../sde
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c500650c10c4-part1 -> ../../sde1
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c500650c10c4-part2 -> ../../sde2
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c500650c10c4-part3 -> ../../sde3
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c500650c10c4-part4 -> ../../sde4
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c500650c10c4-part5 -> ../../sde5
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c500650c10c4-part6 -> ../../sde6
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c500650c10c4-part7 -> ../../sde7
lrwxrwxrwx 1 root root  9 Oct 28 16:01 wwn-0x5000c5007906d0a0 -> ../../sdc
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c5007906d0a0-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Oct 29 13:58 wwn-0x5000c5007906d0a0-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c5007906d0a0-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c5007906d0a0-part4 -> ../../sdc4
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c5007906d0a0-part5 -> ../../sdc5
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c5007906d0a0-part6 -> ../../sdc6
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5000c5007906d0a0-part7 -> ../../sdc7
lrwxrwxrwx 1 root root  9 Oct 28 16:10 wwn-0x5000c5007906ec1f -> ../../sdd
lrwxrwxrwx 1 root root 10 Oct 28 16:10 wwn-0x5000c5007906ec1f-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 10 Oct 29 13:50 wwn-0x5000c5007906ec1f-part2 -> ../../sdd2
lrwxrwxrwx 1 root root 10 Oct 28 16:10 wwn-0x5000c5007906ec1f-part3 -> ../../sdd3
lrwxrwxrwx 1 root root 10 Oct 28 16:10 wwn-0x5000c5007906ec1f-part4 -> ../../sdd4
lrwxrwxrwx 1 root root 10 Oct 28 16:10 wwn-0x5000c5007906ec1f-part5 -> ../../sdd5
lrwxrwxrwx 1 root root 10 Oct 28 16:11 wwn-0x5000c5007906ec1f-part6 -> ../../sdd6
lrwxrwxrwx 1 root root 10 Oct 28 16:11 wwn-0x5000c5007906ec1f-part7 -> ../../sdd7
lrwxrwxrwx 1 root root  9 Oct 28 16:01 wwn-0x50026b723a095709 -> ../../sdb
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x50026b723a095709-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Oct 28 16:01 wwn-0x5e83a97e6c896c1f -> ../../sda
lrwxrwxrwx 1 root root 10 Oct 28 16:01 wwn-0x5e83a97e6c896c1f-part1 -> ../../sda1

/dev/disk/by-label:
total 0
lrwxrwxrwx 1 root root 9 Oct 28 16:10 boot -> ../../md1
lrwxrwxrwx 1 root root 9 Oct 28 16:11 home -> ../../md5
lrwxrwxrwx 1 root root 9 Oct 28 16:01 mysql -> ../../md0
lrwxrwxrwx 1 root root 9 Oct 29 14:13 root -> ../../md2
lrwxrwxrwx 1 root root 9 Oct 28 16:11 swap -> ../../md6
lrwxrwxrwx 1 root root 9 Oct 28 16:10 var -> ../../md3
lrwxrwxrwx 1 root root 9 Oct 28 16:10 vbox -> ../../md4

/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root  9 Oct 28 16:10 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sdd
lrwxrwxrwx 1 root root 10 Oct 28 16:10 pci-0000:00:1f.2-scsi-0:0:0:0-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 10 Oct 29 13:58 pci-0000:00:1f.2-scsi-0:0:0:0-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Oct 28 16:10 pci-0000:00:1f.2-scsi-0:0:0:0-part3 -> ../../sdd3
lrwxrwxrwx 1 root root 10 Oct 28 16:10 pci-0000:00:1f.2-scsi-0:0:0:0-part4 -> ../../sdd4
lrwxrwxrwx 1 root root 10 Oct 28 16:10 pci-0000:00:1f.2-scsi-0:0:0:0-part5 -> ../../sdd5
lrwxrwxrwx 1 root root 10 Oct 28 16:11 pci-0000:00:1f.2-scsi-0:0:0:0-part6 -> ../../sdd6
lrwxrwxrwx 1 root root 10 Oct 28 16:11 pci-0000:00:1f.2-scsi-0:0:0:0-part7 -> ../../sdd7

/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 9 Oct 28 16:11 008a2787-5695-435e-a457-701c22153072 -> ../../md6
lrwxrwxrwx 1 root root 9 Oct 28 16:01 0e89c4de-9c80-43fb-b7aa-48689aafb675 -> ../../md0
lrwxrwxrwx 1 root root 9 Oct 28 16:10 322d6ef7-6c62-49ae-82a6-1891dd5fff11 -> ../../md1
lrwxrwxrwx 1 root root 9 Oct 29 14:13 72a83bc1-88f8-4d55-b8f8-e1a171811b6b -> ../../md2
lrwxrwxrwx 1 root root 9 Oct 28 16:10 75a766d2-30d1-45d0-8e38-f976fadaeb00 -> ../../md4
lrwxrwxrwx 1 root root 9 Oct 28 16:11 bac1ee95-404a-4a3b-b1a0-2a0e9a1fd239 -> ../../md5
lrwxrwxrwx 1 root root 9 Oct 28 16:10 edb3491b-c76e-4159-8d53-96692c3fb193 -> ../../md3

/dev/md:
total 0
lrwxrwxrwx 1 root root 6 Oct 28 16:01 0 -> ../md0
lrwxrwxrwx 1 root root 6 Oct 28 16:10 1 -> ../md1
lrwxrwxrwx 1 root root 6 Oct 29 14:13 2 -> ../md2
lrwxrwxrwx 1 root root 6 Oct 28 16:10 3 -> ../md3
lrwxrwxrwx 1 root root 6 Oct 28 16:10 4 -> ../md4
lrwxrwxrwx 1 root root 6 Oct 28 16:11 5 -> ../md5
lrwxrwxrwx 1 root root 6 Oct 28 16:11 6 -> ../md6

Auto-generated on Wed, 29 Oct 2014 15:04:52 +0100
by mdadm bugscript 3.2.5-5

-- System Information:
Debian Release: 7.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages mdadm depends on:
ii  debconf      1.5.49
ii  initscripts  2.88dsf-41+deb7u1
ii  libc6        2.13-38+deb7u6
ii  lsb-base     4.1+Debian8+deb7u1
ii  udev         175-7.2

Versions of packages mdadm recommends:
ii  module-init-tools                  9-3
ii  nullmailer [mail-transport-agent]  1:1.11-2

mdadm suggests no packages.

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


From mjt at tls.msk.ru  Wed Oct 29 15:43:38 2014
From: mjt at tls.msk.ru (Michael Tokarev)
Date: Wed, 29 Oct 2014 18:43:38 +0300
Subject: Bug#767243: mdadm: a new disk always remains spare instead of
 becoming active
In-Reply-To: <20141029144406.6245.12729.reportbug@sql.telur.lan>
References: <20141029144406.6245.12729.reportbug@sql.telur.lan>
Message-ID: <54510B2A.5050102@msgid.tls.msk.ru>

29.10.2014 17:44, Matija Nalis wrote:
> Package: mdadm
> Version: 3.2.5-5
> Severity: normal
> 
> The problem is that newly added disk in 2-device RAID1 (intended to replace
> failing disk) is remaining as 'spare' and cannot be made active.
[...]

Just a quick note, so you wont wait for a reply.

>From the description in your email it looks like you have some prob
on one of the disks (either the one FROM which you're syncing data,
or the one TO which you write, ie, new), that's why you can't make
2 devices active.

But the whole thing does not look like a bug really, not at all,
and you've shown multiple user/usage errors (eg, mdadm --grow -n 2 --
ofcourse mdadm tells you there's nothing to change because the
array already is configured to be 2-way mirror).

It looks much more like a user support question.  But please understand
that BTS is definitely not the right place to ask for support, it is
a bug tracking system.

I haven't read your problem report in full details, just because I
don't have time now to understand your situation properly.  And since
it does not look like a bug, I'll close this bugreport soon (after
letting it to idle for some time, just in case).

This is to tell you to not expect replies, at least from me, at least
in a reasonable timeframe.

Thanks,

/mjt


From mnalis-debianbug at tomsoft.hr  Wed Oct 29 23:30:56 2014
From: mnalis-debianbug at tomsoft.hr (Matija Nalis)
Date: Thu, 30 Oct 2014 00:30:56 +0100
Subject: Bug#767243: mdadm: a new disk always remains spare instead of
 becoming active
In-Reply-To: <54510B2A.5050102@msgid.tls.msk.ru>
References: <20141029144406.6245.12729.reportbug@sql.telur.lan>
 <54510B2A.5050102@msgid.tls.msk.ru>
Message-ID: <20141029233056.GA27444@C3PO.home.lan>

Summary: Thanks for your quick feedback! You can close this as invalid.

I do understand BTS is not general support forum, and I was genuinely
believing that there was bug in mdadm, as I though both source and
destination disks were without errors (despite SMART errors I've got
on /dev/sde, it looked undamaged and it's removal was supposed to be
preemptive).  That belief was reinforced by seeing /proc/mdstat
showing sync progress going above 99.9% without aborting.

The steps I've tried that look like usage errors (-G -n2, ...) were
my last-resort (perhaps misguided) attempts to force mdadm to realize
there are supposed to be two ACTIVE disks in the array (aand not
active+spare) - and I've only tried them the because regular way
(mdadm --add, --remove) didn't work when I though it really should.

That being said, you were correct afterall :-)

Your response prompted me to doublecheck, and I've run badblocks(8)
on both destination disks (both ok) and source /dev/sde2 disk.
And the source disk was really having bad sectors - about 80 of them,
at 99.97%. That last 0.03% was visually too quick to notice, so I was
fooled by /proc/mdstat showing how it progresses from 0% to 99.9%+
without error and I wrongly assumed it did manage to finish the sync
(but somehow didn't update the active/spares, due to some bug)

Some hammering with hdparm --write-sector managed to zero-out that
few sectors (which didn't appear to be used by any files), and after
that mdadm did finish the sync.

Anyway, may the bug be archived for future adventurers with same
problem.

-- 
Opinions above are GNU-copylefted.