On Wed, Nov 05, 2008 at 12:30:58PM +0100, Christophe Rioux wrote: > > > I redone the procedure with the new released version, and > > it seems to be > > > better: > > > > > > Extraction of dmesg: > > > > > > softraid0 at root > > > root on wd0a swap on wd0b dump on wd0b > > > raid0: Component /dev/wd0d being configured at row: 0 col: 0 > > > Row: 0 Column: 0 Num Rows: 1 Num Columns: 2 > > > Version: 2 Serial Number: 100 Mod Counter: 128 > > > Clean: Yes Status: 0 > > > raid0: Component /dev/wd1d being configured at row: 0 col: 1 > > > Row: 0 Column: 1 Num Rows: 1 Num Columns: 2 > > > Version: 2 Serial Number: 100 Mod Counter: 128 > > > Clean: Yes Status: 0 > > > raid0 at root > > > > > > The last question I have is: it seems that I actually boot > > on wd0a, which is > > > not a RAID disk. How can I boot on raid0a ? > > > > > > > It seems the raid autoconfig does not work. > > What does raidctl -vs raid0 say? > => same as your result > > raid0 Components: > /dev/wd0d: optimal > /dev/wd1d: optimal > No spares. > Component label for /dev/wd0d: > Row: 0, Column: 0, Num Rows: 1, Num Columns: 2 > Version: 2, Serial Number: 100, Mod Counter: 143 > Clean: No, Status: 0 > sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1 > Queue size: 100, blocksize: 512, numBlocks: 17799936 > RAID Level: 1 > Autoconfig: Yes > Root partition: Yes > Last configured as: raid0 > Component label for /dev/wd1d: > Row: 0, Column: 1, Num Rows: 1, Num Columns: 2 > Version: 2, Serial Number: 100, Mod Counter: 143 > Clean: No, Status: 0 > sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1 > Queue size: 100, blocksize: 512, numBlocks: 17799936 > RAID Level: 1 > Autoconfig: Yes > Root partition: Yes > Last configured as: raid0 > Parity status: clean > Reconstruction is 100% complete. > Parity Re-write is 100% complete. > Copyback is 100% complete. > > > > Did you build your kernel with RAID autoconfig support? > > I build the kernel with following options: > option RAID_AUTOCONFIG > pseudo-device raid 4 > > And my /etc/raid0.conf: > > START array > 1 2 0 > START disks > /dev/wd0d > /dev/wd1d > START layout > 128 1 1 1 > START queue > fifo 100 > > The creation of the RAID: > raidctl -C /etc/raid0.conf raid0 > raidctl -I 100 raid0 > raidctl -iv raid0
Have you tried boot -a to see if you can select raid0a? http://marc.info/?l=openbsd-misc&m=122153087119929&w=2 If that works it seems raidframe root disk is still not operational. http://marc.info/?l=openbsd-misc&m=120855938821758&w=2 Note that you can still create a setup that does not raid the root disk, just all others. And then use the /altroot backup for the root disk, preferably /altroot on wd1a. Raided root disk might be regarded as a doubtful feature anyway since the kernel will be loaded from wd0 anyway, and if it dies you need a bootable wd1. -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
