Simon Burge writes:
> Michael Watters wrote:
> 
> > Greg Oster wrote:
> > > Good catch... you're probably quite right... 
> > >
> > > Michael: what does "dmesg | grep wd2" say (after the machine boots)? 
> > > Is it a Seagate drive?  And what version of NetBSD are you running?
> > >
> > > Later...
> > >
> > > Greg Oster
> > >
> > >
> > >   
> > They're Seagate 160 GB drives, here's what dmesg says.
> > 
> > wd2 at atabus2 drive 0: <ST3160812AV>
> > wd2: drive supports 16-sector PIO transfers, LBA48 addressing
> > wd2: 149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sector
> s
> > wd2: 32-bit data port
> > wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
> > wd2(viaide0:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA
> )
> > 
> > Is there a limit on RAID sizes?  I'm running NetBSD 3.0.2.
> 
> Some Seagate drives seem to have an issue on the 128GB boundary - look
> around line 230ish of your sys/dev/ata/wd.c.  NetBSD 3.0.2 should have
> an extry for ST3160812A* though which should catch your drive...
> 
> I've been using a pair of ST3320620As in a mirror here with no problems
> on the netbsd-3 branch since last July.

Looks like 3.0.2 was cut just days before the fix for his drive went 
in :(  

Michael: You need a kernel with  revision 1.298.2.7.2.6 of sys/dev/ata/wd.c.
If you have a 3.0.2 source tree handy, just drop in this diff:
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/ata/wd.c.diff?r1=1.298.2.7.2.5&r2=1.298.2.7.2.6

then build a kernel and you should be set...

Later...

Greg Oster