Re: raidctl -A softroot and a failed component

[mlelstv%serpens.de@localhost (Michael van Elst)]

ef%math.uni-bonn.de@localhost (Edgar =?iso-8859-1?B?RnXf?=) writes:

>I had a RAIDframe level 1 RAID with the first component marked as failed, e,g,
>	component0: failed
>	/dev/dkN: optimal
>and although the set was configured -A softroot, the kernel didn't configure 
>raid0a as the root file system, presumably because the dk numbers didn't match.

The kernel will collect disks into raid sets based on the raidframe label
and use the found partitions or wedges on the raid sets, it then checks
each raid set if the booted_device matches a component device and choses
partition 0 from it (wedges don't have partitions, but "partition 0"
is the wedge itself).

IMHO the builroothack should just go away, same for lots of "guesswork"
done by the machdep code.

If you use unique wedge names, you can specify the root volume by name
at least on some archs, e.g. x86 and arm are fine.