This is a repeat of the "can't bring up a raid set with missing members"
On Fri, May 22, 2009 at 05:01:40AM +0000, Uwe Dippel wrote: > Marco Peereboom <slash <at> peereboom.us> writes: > > > > Correct. If this isn't the case then I need to see a dmesg before & > > after rebooting and bioctl output before and after reboot. > > This is as well supported by the post > http://vext01.blogspot.com/2007/11/playing-with-new-softraid-driver-in.html > > "[...] > Bioctl is the utility used for managing both hardware and software RAID in > OpenBSD, the transparency is superb. > > # bioctl softraid0 > Volume Status Size Device > softraid0 0 Online 1023009 sd0 RAID1 > 0 Online 1023009 0:0.0 noencl > 1 Online 1023009 0:1.0 noencl > 2 Online 1023009 0:2.0 noencl > > Lets break things and see what happens. First I will simulate a missing disk > at > boot, by detaching wd3. After a reboot I see this: > > # dmesg | grep softraid0 > softraid0 at root > softraid0: not assembling partial disk that used to be volume 0 > # bioctl softraid0 > # > > Our RAID array was not registered by the kernel, as a disk was missing. I > imagine this will be changed at some point. As I said, the softraid driver is > not finished. > > Shutdown the system and put the disk back: > > # dmesg | grep softraid > softraid0 at root > scsibus0 at softraid0: 1 targets > # bioctl softraid0 > Volume Status Size Device > softraid0 0 Online 1023009 sd0 RAID1 > 0 Online 1023009 0:0.0 noencl > 1 Online 1023009 0:1.0 noencl > 2 Online 1023009 0:2.0 noencl > > It's back." > > Isn't this what you said it shouldn't? (Be back 'Online' after an earlier > breakage of the mirror) > > Uwe
