Date: Wed, 2 Jan 2019 11:39:04 +0000
From: Patrick Welche <[email protected]>
Message-ID: <20190102113904.GC1124@quark>
| I am reaching the conclusion that it must be "bad disks".
I would doubt that.
| If there were something wrong the MBR or the labels, I wouldn't be able
| to boot the kernel from raid0a.
The MBR, then perhaps yes, the raid labels, no, the bootstrap via raid
is very dumb, knows nothing about raid except the size of the header.
| [The need for netboot to illustrate is that no root filesystem is
| found on normal boot]
My guess, and this is all it is, is that the problem might relate to the
"soft root" config - I'd suggest disabling that, "raicctl -A yes", or
switch it to forceroot ... my suspicion is that perhaps the boot drive
isn't being detected as being part of the raid, and that perhaps
when that happens, the raid doesn't get autoconfigured at all.
kre
