b...@bsd.de (Christoph Badura) writes:
>> rootspec is set by config(1) for three cases:
>> config root on major 4 minor 4
>> - sets rootspec to "sd0e" (or maybe "<4/4>") and rootdev to makedev(4,4)
>> config root on sd0e
>> - sets rootspec to "sd0e" and rootdev to makedev(4,4)
>> config root on
On Sun, Jan 13, 2019 at 08:45:31AM -, Michael van Elst wrote:
> b...@bsd.de (Christoph Badura) writes:
> >> So, assuming 'raid0' has a component 'dk0' which is based on 'wd0', it
> >> should work to specify 'wd0' as bootdev.
>
> >That does work. However, that is besides the point bootdev=rai
b...@bsd.de (Christoph Badura) writes:
>> So, assuming 'raid0' has a component 'dk0' which is based on 'wd0', it
>> should work to specify 'wd0' as bootdev.
>That does work. However, that is besides the point bootdev=raid0 is
>supposed to work but it doesn't.
Which is of course is unrelated to
On Tue, Jan 08, 2019 at 09:28:07PM -, Michael van Elst wrote:
> b...@bsd.de (Christoph Badura) writes:
>
> >With "raidctl -A softroot raid0" the XEN3_DOM0 kernel does not detect
> >raid0 as root device.
>
> raidframe checks if the system was booted from one of the raid components
> marked as
b...@bsd.de (Christoph Badura) writes:
>With "raidctl -A softroot raid0" the XEN3_DOM0 kernel does not detect
>raid0 as root device.
raidframe checks if the system was booted from one of the raid components
marked as softroot and only then forces the kernel to mount partition 'a'
of that raid as
I have a Xen server with two disk, gpt partitioned, raidframe mirrors on the
dk(4) devices. That system boots off an USB flash key.
With "raidctl -A softroot raid0" the XEN3_DOM0 kernel does not detect
raid0 as root device.
It also doesn't detect raid0 as root device when
the dom0 kernel is loa