On Tue, Feb 27, 2007 at 03:11:40PM -0500, Michael Watters wrote:
> Greg Oster wrote:
> >Does:  raidctl -v -R /dev/wd2e raid0
> >work any better? :) 
> >
> >Later...
> >
> >Greg Oster
> >  
> Ok, now it starts to rebuild but it fails around 90%.
> 
> Feb 27 13:14:36 nfs /netbsd: wd2e: error writing fsbn 268435392 of 
> 268435392-268435519 (wd2 bn 268435455; cn 266305 tn 0 sn 15), retrying
> Feb 27 13:14:36 nfs /netbsd: wd2: (id not found)
> Feb 27 13:14:36 nfs /netbsd: wd2e: error writing fsbn 268435392 of 
> 268435392-268435519 (wd2 bn 268435455; cn 266305 tn 0 sn 15), retrying
> Feb 27 13:14:36 nfs /netbsd: wd2: (id not found)
> Feb 27 13:14:37 nfs /netbsd: wd2e: error writing fsbn 268435392 of 
> 268435392-268435519 (wd2 bn 268435455; cn 266305 tn 0 sn 15), retrying
> Feb 27 13:14:37 nfs /netbsd: wd2: (id not found)
> Feb 27 13:14:38 nfs /netbsd: wd2e: error writing fsbn 268435392 of 
> 268435392-268435519 (wd2 bn 268435455; cn 266305 tn 0 sn 15), retrying
> Feb 27 13:14:38 nfs /netbsd: wd2: (id not found)
> Feb 27 13:14:38 nfs /netbsd: wd2e: error writing fsbn 268435392 of 
> 268435392-268435519 (wd2 bn 268435455; cn 266305 tn 0 sn 15), retrying
> Feb 27 13:14:38 nfs /netbsd: wd2: (id not found)
> Feb 27 13:14:39 nfs /netbsd: wd2e: error writing fsbn 268435392 of 
> 268435392-268435519 (wd2 bn 268435455; cn 266305 tn 0 sn 15)wd2: (id not 
> found)
> Feb 27 13:14:39 nfs /netbsd:
> Feb 27 13:14:39 nfs /netbsd: raid0: Recon write failed!
> Feb 27 13:14:39 nfs /netbsd: raid0: reconstruction failed.
> 
> I'm not sure what these errors mean.

What OS release, and what drives ? It looks like the 128GB seagate bug.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--