On Wed, 25 Jun 2014, Rodney D. Myers wrote:
> Well 2 hours later, failed;
Please examine dmesg, and see precisely what the failure messages were.
[The entries in dmesg corresponding to the drives being detected at
early boot will aul.]
Secondly, please show us the output of:
mdadm --detail /dev/sd{c,d,e}1;
It's possible that you have either bad controllers, bad cables, a bad
multiplexer, or bad harddrives... but only the dmesg output will give us
an idea of what the problem is.
--
Don Armstrong http://www.donarmstrong.com
"I'm a rational being--of a sort--rational enough, at least, to see the
symptoms of insanity around me. And I'm human, the same as the people
I think of as victims when my guard drops. It's at least possible I'm
even crazier than my fellows, whom I'm tempted to pity.
"There seems only one thing to do, and that's get drunk"
-- Chad C. Mulligan (John Brunner _Stand On Zanzibar_ p390)