Hi Martin,
On 02/20/2017 12:48 PM, Martin Bosner wrote:
> Hi Phil,
>
>> { Note: convention on kernel.org is reply-to-all, bottom post or
>> interleave, and trim unneeded material. }
> Sorry, hope this one is better.
>
>
>> for x in /dev/sd[a-z] /dev/sda[a-j] ; do mdadm -E ${x}1 ; done
>
> See below for full output.
Not good.
>> Eewwww! You have desktop drives. Which means your array has
>> blown up due to timeout mismatch. You have some reading to do.[1]
Of the 36 original disks, you have 34. You have one incomplete
rebuild, meaning it is still technically a spare. One of the still
active 34 is also showing pending relocations, meaning that disk will
not be able to supply all sectors to complete any recovery.
{ /dev/sdah, serial # S1F0FPYR }
If you have any access to the two "dead" drives, there might be
a slight chance. Since they were likely kicked out due to timeout
mismatch, not a complete failure, this could be possible.
Otherwise, you are utterly screwed. Sorry.
> I will be using so called “NAS” or “enterprise disks in the next
> cluster … especially these seagate disks were a bad decision.
Yes.
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
