Subject: Re: Upgrading a RAIDframe system with sysinst?
To: None <netbsd-users@NetBSD.org>
From: Stephen Borrill <firstname.lastname@example.org>
Date: 11/27/2006 17:17:39
On Mon, 27 Nov 2006, Greg Oster wrote:
> Christoph Kaegi writes:
>> On 27.11-14:26, Stephen Borrill wrote:
>>>>> If all the RAIDframe volumes are autoconfigured (and not via
>>>>> "/etc/raind<x>.conf") booting of the CD and using "sysinst" should
>>>>> work fine.
>>>> When Booting a 3.0 install CD, I made the experience that only
>>>> raid0 was detected (I had / on raid0, /usr on raid2, /var on raid3)
>>> It's probably that /dev only contains the raid0 devices. You could try:
>>> cd /dev
>>> sh MAKEDEV raid1 raid2 raid3
>> Hm, would this help the kernel recognize more raid devices when
>> I thought the / fs isn't yet mounted when the kernel autoconfigures
>> the raid devices.
> You are correct. If raid2 and raid3 are "autoconfigure", then they
> should have been picked up and configured automatically, regardless
> of what's in /dev.
But you won't be able to do much with them and the error message along the
lines of "device not configured" could refer to both situations.
Does dmesg show only the one? How about sysctl hw.disknames?