Hi Phil,
usbcore.autosuspend=-1
This might be the solution! I'll test it and let you know.
And regarding power issues:
- this was the first thing I notices and I bought a powered usb-hub to
provide enough current to the HDs.
Using USB drives is kind of a home user scenario. I understand that
MDADM might be more focused on large data centers, but would be great
to have such a great tool also available for the average joe.
Best!
Juan Carlos Carvajal Bermúdez
+43 650 477 0005
juca@xxxxxxxxxxxxxxxx
Beingasse 17/2/3
AT 1150, Wien
www.juan-carlos.info
On 12 December 2016 at 04:17, Phil Turmel <philip@xxxxxxxxxx> wrote:
> On 12/11/2016 05:14 PM, Adam Goryachev wrote:
>> On 12/12/16 04:14, juca@xxxxxxxxxxxxxxxx wrote:
>> If you are still having problems after that, then please try to post
>> more details on what happens when the drives vanish (eg, kernel logs,
>> system logs, etc).
>>
>> Also, you might consider an alternative SBC, some have SATA ports
>> already available (RPi are the only SBC's I've used, but there are many
>> other options/variations).
>
> There's also a kernel boot parameter that can cut off all USB
> auto-suspend, which I suspect is part of the problem. It has been known
> for a long time that USB is not robust enough to be trusted in MD arrays.
>
> { looking around..... }
>
> usbcore.autosuspend=-1
>
> is what you need in your bootloader or builtin to the kernel.
>
> 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
