On 09/21/2017 09:22 AM, Vojtěch Kletečka wrote:
> I tried both reasonable versions without success:
There is only one reasonable version. The one that leaves out the
out-of-sync device. Your device letters might be changing, as your
mdadm -E reports indicate the one to leave out is /dev/sdd1, active
device #2.
> sudo mdadm --assemble --verbose --force /dev/md127 /dev/sd[ce]1
> [sudo] password for vojtech:
> mdadm: looking for devices for /dev/md127
> mdadm: /dev/sdc1 is identified as a member of /dev/md127, slot 2.
> mdadm: /dev/sde1 is identified as a member of /dev/md127, slot 1.
> mdadm: no uptodate device for slot 0 of /dev/md127
> mdadm: added /dev/sdc1 to /dev/md127 as 2 (possibly out of date)
> mdadm: added /dev/sde1 to /dev/md127 as 1
> mdadm: /dev/md127 assembled from 1 drive - not enough to start the array.
I would have thought this would be the correct incantation, but it
identified sdc1 as slot 2.
> sudo mdadm --assemble --verbose --force /dev/md127 /dev/sd[de]1
> mdadm: looking for devices for /dev/md127
> mdadm: /dev/sdd1 is identified as a member of /dev/md127, slot 0.
> mdadm: /dev/sde1 is identified as a member of /dev/md127, slot 1.
> mdadm: added /dev/sde1 to /dev/md127 as 1
> mdadm: no uptodate device for slot 4 of /dev/md127
> mdadm: added /dev/sdd1 to /dev/md127 as 0
> mdadm: failed to RUN_ARRAY /dev/md127: Input/output error
This has slots 0 and 1 as expected, but is asking for slot #4. Which
shouldn't be necessary with a 3-device raid10. Your metadata seems
badly corrupted.
Which means that --create --assume-clean is the right answer, and you
have complete mdadm -E reports to supply the right parameters
(especially chunk size and data offsets) to get it right. You just have
to make sure you use the correct devices for slots 0 and 1 and supply
'missing' for slot 2. {Do not use shell [] notation as a shortcut in
any --create command, as [] notation can reorder the letters.}
Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
