On Thu, 10 May 2012 11:19:30 +0100 John Robinson <john.robinson@xxxxxxxxxxxxxxxx> wrote: > On 10/05/2012 10:20, NeilBrown wrote: > > On Thu, 10 May 2012 10:07:21 +0200 Lars Schimmer<l.schimmer@xxxxxxxxxxxxx> > > wrote: > [...] > >> mdadm -E tells me e.g. for md1: > >> > >> /dev/sdh1: > >> Events : 206286 > >> > >> /dev/sdf1: > >> Events : 206273 > >> > >> /dev/sdi1: > >> Events : 197114 > >> > >> /dev/sdj1: > >> Events : 206286 > [...] > >> > >> > >> So all 4 disks see some diff state. Any chance on getting raid5 > >> running again and read some data from it? > >> > >> Does the mdadm -C --assume-clean option help me in that case anyhow? > > > > Just add --force the to --assemble command. > > I think I'd assemble from only 3 drives, sdh, sdf and sdj, because sdi's > event count is so much lower it must be the one that was knocked out > first and you probably want to resync onto it (or a fresh drive if it's > actually faulty). correct. And that is exactly what "mdadm --assemble --force" will decide too. :-) It will assemble from h, f, j and exclude i. NeilBrown
Attachment:
signature.asc
Description: PGP signature
