On Tue, May 28, 2002 at 12:32:24PM -0700, Wolfgang Rupprecht wrote:
> 
> > Hmmm...Can you include the errors from syslog? From your other post, It
> > sounds like you're dealing with typical ATA/IDE issues.
> 
> May 26 10:25:56 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784047 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
> May 26 10:25:56 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784047 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
> May 26 10:25:56 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784047 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
> May 26 10:25:56 capsicum /netbsd: wd0e: device timeout reading fsbn 784016 of 784016-784047 (wd0 bn 9267344; cn 9193 tn 12 sn 44), retrying
> May 26 10:25:56 capsicum /netbsd: wd0e: uncorrectable data error reading fsbn 784025 of 784016-784047 (wd0 bn 9267353; cn 9193 tn 12 sn 53), retrying

The timeouts are a driver thing, which detected something went probably
wrong. However, the "uncorrectable data error" is really what the drive
said: the communication between drive and host went fine, and the drive
reported the error.
It's possible that your drive is going bad.
However, as I already said, I've seen drives ressurect when from situations
like this when used with a different power supply ...

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
--