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

[Brian Buhrow <buhrow%nfbcal.org@localhost>]

	hello.  I think I can shed light on this issue.  Some years ago I
added the ability for raidframe to host raid components on raw disks.  So,
right now, raidframe can have components on disk partitions, i.e. old
disklabel partitions, gpt wedges and raw disks.  I think these messages are
a result of the raidframe code digging around on the disk devices trying to
determine if and where components for raid devices might reside on them.  On
systems where I have raidframe components on raw disks, I get those
messages at boot time.  Since they're harmless, I didn't worry about them.

-thanks
-Brian

On Apr 22, 12:32pm, Edgar =?iso-8859-1?B?RnXf?= wrote:
} Subject: opendisk: can't open dev dk0 (16) (was: RAIDframe raidN device or
} > 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".
} 
} dk0~=sd0 through dk4~=sd4 are the components of raid1.
} The components of raid0 are sd5a and sd6a (no GPT on those) and I don't get 
} similar messages for sd5/sd6.
} 
} Apart from the messages, everything seems to work fine.
>-- End of excerpt from Edgar =?iso-8859-1?B?RnXf?=