Bug#578352: closed by martin f krafft <madduck at debian.org> (Re: Bug#578352: mdadm: failed devices become spares!)

[Pierre Vignéras]

On lundi 19 avril 2010, you wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the mdadm package:
> 
> #578352: mdadm: failed devices become spares!
> 
> It has been closed by martin f krafft <madduck at debian.org>.
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact martin f krafft
>  <madduck at debian.org> by replying to this email.
> 

Sorry to disturb. I shown in my bug report:

Apr 12 20:10:02 phobos mdadm[3157]: Fail event detected on md device /dev/md2, 
component device /dev/sdf1
Apr 12 20:11:02 phobos mdadm[3157]: SpareActive event detected on md device 
/dev/md2, component device /dev/sdf1 

And at that time I was neither logged in nor did I touch to 
that NFS server (neither the USB drives, nor the server itself). Actually, 
I discovered the problem the day after. So the first question is:

is it normal that after a failure detected on /dev/sdf1 it becomes 
a spare (again if I understand the syslog message correctly)?

Note that the same thing happened on another USB drive (/dev/sdd1) the day after:

Apr 13 08:00:02 phobos mdadm[3157]: Fail event detected on md device /dev/md2, 
component device /dev/sdd1
Apr 13 08:00:02 phobos mdadm[3157]: SpareActive event detected on md device 
/dev/md2, component device /dev/sdd1

Finally, I tried to remove those drives and to insert them afterwards:
(note that name of drives did change after a reboot):

mdadm -A /dev/md2 -f /dev/sdc1 -r /dev/sdc1

But without any success:

phobos:~# mdadm -Q --detail /dev/md2
/dev/md2:
        Version : 00.90
  Creation Time : Thu Aug  6 01:59:44 2009
     Raid Level : raid10
  Used Dev Size : 312568576 (298.09 GiB 320.07 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Tue Apr 13 19:22:21 2010
          State : active, degraded, Not Started
 Active Devices : 2
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 2

         Layout : near=2, far=1
     Chunk Size : 64K

           UUID : b34f4192:f823df58:24bf28c1:396de87f (local to host phobos)
         Events : 0.90612

    Number   Major   Minor   RaidDevice State
       0       0        0        0      removed
       1       0        0        1      removed
       2       8       49        2      active sync   /dev/sdd1
       3       8       65        3      active sync   /dev/sde1

       4       8       81        -      spare   /dev/sdf1
       5       8       33        -      spare   /dev/sdc1
phobos:~#


So the second question is: 

what should I do to recover my data? You suggest to remove previous one. I 
don't get how:

mdadm /dev/md2 --remove ?? (according to /proc/mdstat, /dev/sdf1 and /dev/sdc1 
are now spares).

Thanks four your reply & Regards

PS: since my bug report, I did not touch to this RAID array, I am waiting for 
your input. 
-- 
Pierre Vignéras
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20100420/4695069e/attachment.htm>