Re: opendisk: can't open dev dk0 (16) (was: RAIDframe raidN device order)

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

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

>> tl;dr - the Right Thing should Just Happen
>OK, that's mostly the case.

>However, after all the components of the two arrays have been identified, the 
>arrays have been set up and their partions recognized, I get the following:
>	opendisk: can't open dev dk0 (16)
>	opendisk: can't open dev dk1 (16)
>	opendisk: can't open dev dk2 (16)
>	opendisk: can't open dev dk3 (16)
>	opendisk: can't open dev dk4 (16)
>	opendisk: can't open dev sd0 (16)
>	opendisk: can't open dev sd1 (16)
>	opendisk: can't open dev sd2 (16)
>	opendisk: can't open dev sd3 (16)
>	opendisk: can't open dev sd4 (16)
>just before "boot device: raid0".

That is the kernel searching for a boot disk. The message should
be gone since netbsd-7 but netbsd-6 is a bit noisy.

-- 
-- 
                                Michael van Elst
Internet: mlelstv%serpens.de@localhost
                                "A potential Snark may lurk in every tree."