Re: RAID 10 array won't assemble ... spare ... metadata - Disappointing Report Back

[Dave Fisher <davef@davefisher.co.uk>]

On Sat, Apr 18, 2009 at 08:38:59AM +1000, Neil Brown wrote:
> So:
> 
>   mdadm -S /dev/md1
>   mdadm -A /dev/md1 -fv /dev/sd[abcde]4
> 
> and report the result.

Output transcribed by hand:

    mdadm: looking for devices for /dev/md1
    mdadm: /dev/sda4 is identified as a member of /dev/md1 slot 0
    mdadm: /dev/sdb4 is identified as a member of /dev/md1 slot 1
    mdadm: /dev/sdc4 is identified as a member of /dev/md1 slot 2
    mdadm: /dev/sdd4 is identified as a member of /dev/md1 slot 3
    mdadm: /dev/sde4 is identified as a member of /dev/md1 slot 4
    mdadm: forcing event count in /dev/sdb4(1) from 219 upto 221

But when I ran mdadm -E on each of the partitions the counts were
competely unchanged, i.e. sd[bcde]4 were still all at 219.

sda4 was still at 221

Everything else looked exactly the same, including the summary tables at
the end.

Any thoughts?

Do I need to start/run the array to affect the changes?

Dave