On Thursday 05 January 2006 22:47, Manuel Bouyer wrote:
> On Thu, Jan 05, 2006 at 05:55:44PM +0100, Thierry Lacoste wrote:
> > I was able to complete the installation but I now hit the problem
> > described in
> > http://mail-index.netbsd.org/netbsd-docs/2005/08/16/0001.html I can boot
> > from sd1 but not from sd0 which renders the whole thing rather pointless.
> > Does someone know a workaround?
>
> Did you run installboot on both drives ?
Yes. I followed to the letter chapter 15 of the NetBSD guide
except that I have to align my swap partitions on cylinders boundaries.

Apparently I didn't cut them correctly because when I boot from sd1 I have
Jan  5 17:23:16 algol /netbsd: raid0: WARNING: raid0: total sector size in 
disklabel (4197248) != the size of raid (4196736)
Jan  5 17:23:16 algol /netbsd: raid0: WARNING: raid0: end of partition `b' 
exceeds the size of raid (4196736)
Jan  5 17:23:16 algol /netbsd: raid0: WARNING: raid0: end of partition `c' 
exceeds the size of raid (4196736)

However RAID seems to be functional:
algol# raidctl -v -s raid0
Components:
           /dev/sd0a: optimal
           /dev/sd1a: optimal
No spares.
Component label for /dev/sd0a:
   Row: 0, Column: 0, Num Rows: 1, Num Columns: 2
   Version: 2, Serial Number: 2005010401, Mod Counter: 90
   Clean: No, Status: 0
   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
   Queue size: 100, blocksize: 512, numBlocks: 4196736
   RAID Level: 1
   Autoconfig: Yes
   Root partition: Yes
   Last configured as: raid0
Component label for /dev/sd1a:
   Row: 0, Column: 1, Num Rows: 1, Num Columns: 2
   Version: 2, Serial Number: 2005010401, Mod Counter: 90
   Clean: No, Status: 0
   sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1
   Queue size: 100, blocksize: 512, numBlocks: 4196736
   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.

> What's the error when you try booting from sd0 ?
  .Inode not directory
  Fast Data Access MMU Miss
This is exactly the error described in
http://mail-index.netbsd.org/netbsd-docs/2005/08/16/0001.html

Regards,
Thierry.