Hi Tony,
{Convention on kernel.org is to trim posts & bottom or interleave posts}
On 11/14/2014 09:08 AM, DeadManMoving wrote:
> Hi Phil,
>
> Unfortunately, that does not work :
>
> # mdadm --assemble --force /dev/md127 /dev/sd[fhi]
> mdadm: /dev/md127 assembled from 2 drives - not enough to start the
> array.
That's quite surprising.
> I don't think that booting with an alternate boot media will help me out
> as kernel and mdadm software are quite recent :
>
> # uname -r
> 3.14.14-gentoo
> # mdadm -V
> mdadm - v3.3.1 - 5th June 2014
Indeed.
At this point, I would use --create --assume-clean, along with
"missing". You have a recent enough mdadm to specify
--data-offset=2048, which you definitely need. Something like:
mdadm --create /dev/mdX --assume-clean --data-offset=2048 \
--level=5 --raid-devices=4 --chunk=512 \
missing /dev/sd{f,i,h}
You should verify the Device Role numbers with mdadm -E again, as your
drive letters have changed from the initial report. To be absolutely
sure, I suggest you record drive serial numbers for each role #. Also
note the use of braces instead of square brackets--bash re-orders the
latter, and that would break your array. For this type of recovery, it
is vital that the devices be listed precisely in device role order,
starting with zero.
After creation, verify that the space before and space after stats for
each device match the original report, before fsck or mount.
(--data-offset controls space before, that plus --size controls space
after.)
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
