"Paul Wright" writes: > Hi all, > > I've followed a set of instructions[1] describing a method of > installing OpenBSD onto a RAID 1 array created with raidctl using only > 2 disks (sd0b + sd1b). The basic premise is to first install normally > onto one disk (sd0b) and then created a degraded RAID 1 array using > the second disk (sd1b) and a fake third disk (sd2b). After booting > off the array you then add the original first (sd0b) disk to the array > and rebuild. > > This works but the changes don't 'stick' between reboots, the array > promptly forgets about sd0b: > > # raidctl -s raid0 > raid0 Components: > component0: failed > /dev/sd1b: optimal > No spares. > Parity status: clean > Reconstruction is 100% complete. > Parity Re-write is 100% complete. > Copyback is 100% complete. > > # raidctl -a /dev/sd0b raid0 > # raidctl -F component0 raid0 > > # raidctl -s raid0 > raid0 Components: > component0: spared > /dev/sd1b: optimal > Spares: > /dev/sd0b: used_spare > Parity status: clean > Reconstruction is 100% complete. > Parity Re-write is 100% complete. > Copyback is 100% complete.
Try doing a: raidctl -i 605190 raid0 here before rebooting. I seem to recall a bug related to component labels on used spares not being updated properly after a reconstruct, and I think re-running the '-i' option was the workaround... Later... Greg Oster
