Hi Phil,
How odd. Packaged mdadm was version 3.3, I build the latest in the 3.3
branch (3.3.4) Array still did not start, although it found 15 good
drives. Tried again with 3.3 and it worked.
File system mounted OK after recovery (XFS).
Thanks for your help.
Stephen
sudo ./mdadm --assemble --force --readonly /dev/md2
/dev/sd{ac,n,af,g,ae,m,l,i,k,j,h,f,e,d,c} --verbose
mdadm: looking for devices for /dev/md2
mdadm: /dev/sdac is identified as a member of /dev/md2, slot 14.
mdadm: /dev/sdn is identified as a member of /dev/md2, slot 10.
mdadm: /dev/sdaf is identified as a member of /dev/md2, slot 7.
mdadm: /dev/sdg is identified as a member of /dev/md2, slot 13.
mdadm: /dev/sdae is identified as a member of /dev/md2, slot 4.
mdadm: /dev/sdm is identified as a member of /dev/md2, slot 0.
mdadm: /dev/sdl is identified as a member of /dev/md2, slot 1.
mdadm: /dev/sdi is identified as a member of /dev/md2, slot 2.
mdadm: /dev/sdk is identified as a member of /dev/md2, slot 5.
mdadm: /dev/sdj is identified as a member of /dev/md2, slot 12.
mdadm: /dev/sdh is identified as a member of /dev/md2, slot 11.
mdadm: /dev/sdf is identified as a member of /dev/md2, slot 6.
mdadm: /dev/sde is identified as a member of /dev/md2, slot 9.
mdadm: /dev/sdd is identified as a member of /dev/md2, slot 3.
mdadm: /dev/sdc is identified as a member of /dev/md2, slot 8.
mdadm: forcing event count in /dev/sdn(10) from 485381 upto 485397
mdadm: forcing event count in /dev/sdh(11) from 485381 upto 485397
mdadm: forcing event count in /dev/sdj(12) from 485381 upto 485397
mdadm: forcing event count in /dev/sdg(13) from 485381 upto 485397
mdadm: forcing event count in /dev/sdac(14) from 485381 upto 485397
mdadm: added /dev/sdl to /dev/md2 as 1
mdadm: added /dev/sdi to /dev/md2 as 2
mdadm: added /dev/sdd to /dev/md2 as 3
mdadm: added /dev/sdae to /dev/md2 as 4
mdadm: added /dev/sdk to /dev/md2 as 5
mdadm: added /dev/sdf to /dev/md2 as 6
mdadm: added /dev/sdaf to /dev/md2 as 7
mdadm: added /dev/sdc to /dev/md2 as 8
mdadm: added /dev/sde to /dev/md2 as 9
mdadm: added /dev/sdn to /dev/md2 as 10
mdadm: added /dev/sdh to /dev/md2 as 11
mdadm: added /dev/sdj to /dev/md2 as 12
mdadm: added /dev/sdg to /dev/md2 as 13
mdadm: added /dev/sdac to /dev/md2 as 14
mdadm: added /dev/sdm to /dev/md2 as 0
mdadm: /dev/md2 assembled from 15 drives - not enough to start the array.
sudo mdadm --assemble --force --readonly /dev/md2
/dev/sd{ac,n,af,g,ae,m,l,i,k,j,h,f,e,d,c} --verbose
mdadm: looking for devices for /dev/md2
mdadm: /dev/sdac is identified as a member of /dev/md2, slot 14.
mdadm: /dev/sdn is identified as a member of /dev/md2, slot 10.
mdadm: /dev/sdaf is identified as a member of /dev/md2, slot 7.
mdadm: /dev/sdg is identified as a member of /dev/md2, slot 13.
mdadm: /dev/sdae is identified as a member of /dev/md2, slot 4.
mdadm: /dev/sdm is identified as a member of /dev/md2, slot 0.
mdadm: /dev/sdl is identified as a member of /dev/md2, slot 1.
mdadm: /dev/sdi is identified as a member of /dev/md2, slot 2.
mdadm: /dev/sdk is identified as a member of /dev/md2, slot 5.
mdadm: /dev/sdj is identified as a member of /dev/md2, slot 12.
mdadm: /dev/sdh is identified as a member of /dev/md2, slot 11.
mdadm: /dev/sdf is identified as a member of /dev/md2, slot 6.
mdadm: /dev/sde is identified as a member of /dev/md2, slot 9.
mdadm: /dev/sdd is identified as a member of /dev/md2, slot 3.
mdadm: /dev/sdc is identified as a member of /dev/md2, slot 8.
mdadm: added /dev/sdl to /dev/md2 as 1
mdadm: added /dev/sdi to /dev/md2 as 2
mdadm: added /dev/sdd to /dev/md2 as 3
mdadm: added /dev/sdae to /dev/md2 as 4
mdadm: added /dev/sdk to /dev/md2 as 5
mdadm: added /dev/sdf to /dev/md2 as 6
mdadm: added /dev/sdaf to /dev/md2 as 7
mdadm: added /dev/sdc to /dev/md2 as 8
mdadm: added /dev/sde to /dev/md2 as 9
mdadm: added /dev/sdn to /dev/md2 as 10
mdadm: added /dev/sdh to /dev/md2 as 11
mdadm: added /dev/sdj to /dev/md2 as 12
mdadm: added /dev/sdg to /dev/md2 as 13
mdadm: added /dev/sdac to /dev/md2 as 14
mdadm: added /dev/sdm to /dev/md2 as 0
mdadm: /dev/md2 has been started with 15 drives.
On Wed, 12 Dec 2018 at 20:37, Phil Turmel <philip@xxxxxxxxxx> wrote:
>
> Hi Stephen,
>
> On 12/12/18 2:37 PM, Stephen Remde wrote:
> > I've been trying to follow the wiki steps to recover my data, and got
> > to the point where I need to recreate it I believe but would like
> > someone to confirm or offer advice:
> >
> > The controller failed and after reboot, I was left with this (full
> > mdadm -E at bottom of mail):
> >
> > cat /proc/mdstat
> >
> > md2 : inactive sdac[14](S) sdn[15](S) sdaf[7](S) sdg[13](S) sdae[4](S)
> > sdm[0](S) sdl[1](S) sdi[2](S) sdk[5](S) sdj[12](S) sdh[11](S)
> > sdf[6](S) sde[9](S) sdd[3](S) sdc[8](S)
> > 117208432680 blocks super 1.2
> >
> > $ mdadm -E /dev/sd{ac,n,af,g,ae,m,l,i,k,j,h,f,e,d,c} | egrep 'Event|/dev/sd'
> >
> > /dev/sdac:
> > Events : 485381
> > /dev/sdn:
> > Events : 485381
> > /dev/sdaf:
> > Events : 485381
> > /dev/sdg:
> > Events : 485381
> > /dev/sdae:
> > Events : 485381
> > /dev/sdm:
> > Events : 485381
> > /dev/sdl:
> > Events : 485381
> > /dev/sdi:
> > Events : 485381
> > /dev/sdk:
> > Events : 485381
> > /dev/sdj:
> > Events : 485381
> > /dev/sdh:
> > Events : 485381
> > /dev/sdf:
> > Events : 485397
> > /dev/sde:
> > Events : 485397
> > /dev/sdd:
> > Events : 485397
> > /dev/sdc:
> > Events : 485397
> >
> > $ mdadm --stop /dev/md2
> > mdadm: stopped /dev/md2
> >
> > $ mdadm --assemble --readonly /dev/md2
> > /dev/sd{ac,n,af,g,ae,m,l,i,k,j,h,f,e,d,c} --force --verbose
> >
> > mdadm: looking for devices for /dev/md2
> > mdadm: /dev/sdac is identified as a member of /dev/md2, slot 14.
> > mdadm: /dev/sdn is identified as a member of /dev/md2, slot 10.
> > mdadm: /dev/sdaf is identified as a member of /dev/md2, slot 7.
> > mdadm: /dev/sdg is identified as a member of /dev/md2, slot 13.
> > mdadm: /dev/sdae is identified as a member of /dev/md2, slot 4.
> > mdadm: /dev/sdm is identified as a member of /dev/md2, slot 0.
> > mdadm: /dev/sdl is identified as a member of /dev/md2, slot 1.
> > mdadm: /dev/sdi is identified as a member of /dev/md2, slot 2.
> > mdadm: /dev/sdk is identified as a member of /dev/md2, slot 5.
> > mdadm: /dev/sdj is identified as a member of /dev/md2, slot 12.
> > mdadm: /dev/sdh is identified as a member of /dev/md2, slot 11.
> > mdadm: /dev/sdf is identified as a member of /dev/md2, slot 6.
> > mdadm: /dev/sde is identified as a member of /dev/md2, slot 9.
> > mdadm: /dev/sdd is identified as a member of /dev/md2, slot 3.
> > mdadm: /dev/sdc is identified as a member of /dev/md2, slot 8.
> > mdadm: added /dev/sdl to /dev/md2 as 1
> > mdadm: added /dev/sdi to /dev/md2 as 2
> > mdadm: added /dev/sdd to /dev/md2 as 3
> > mdadm: added /dev/sdae to /dev/md2 as 4
> > mdadm: added /dev/sdk to /dev/md2 as 5
> > mdadm: added /dev/sdf to /dev/md2 as 6
> > mdadm: added /dev/sdaf to /dev/md2 as 7
> > mdadm: added /dev/sdc to /dev/md2 as 8
> > mdadm: added /dev/sde to /dev/md2 as 9
> > mdadm: added /dev/sdn to /dev/md2 as 10 (possibly out of date)
> > mdadm: added /dev/sdh to /dev/md2 as 11 (possibly out of date)
> > mdadm: added /dev/sdj to /dev/md2 as 12 (possibly out of date)
> > mdadm: added /dev/sdg to /dev/md2 as 13 (possibly out of date)
> > mdadm: added /dev/sdac to /dev/md2 as 14 (possibly out of date)
> > mdadm: added /dev/sdm to /dev/md2 as 0
> > mdadm: /dev/md2 assembled from 10 drives - not enough to start the array.
>
> [trim /]
>
> The forced assembly should have worked. You are probably using an older
> version of mdadm that had a bug in forced assembly. Please get the
> latest source code and compile it locally -- don't worry about the
> kernel version for this -- and run the forced assembly with it instead
> of your distro version.
>
> DO NOT USE --create.
>
> Phil
--
Dr Stephen Remde
Director, Innovation and Research
T: 01535 280066
M: 07764 740920
E: stephen.remde@xxxxxxxxxxx
W: www.gaist.co.uk
