Yeah. I did some testing last night - to know avail. When it bailed
today, I restarted it, expecting the raid to rebuild as it always
does. This time it didn't! It booted right up using wd1 and failed
wd0 in raid0.
Kinda makes me happy I built it that way (special thanks to this
page: http://www.argon18.com/raid_openbsd.html ).
So, I think that wd0 may be the cause of the whole problem, and I'll
replace it right away and keep an eye on it to make sure that there
aren't other problems.
Thanks everyone for your great suggestions. I've been exploring them
all.
Best Regards,
Stephen
On 17-Dec-06, at 12:48 PM, Artur Grabowski wrote:
Stephen Schaff <[EMAIL PROTECTED]> writes:
wd0(pciide1:0:0): timeout
type: ata
c_bcount: 65536
c_skip: 0
pciide1:0:0: bus-master DMA error: missing interrupt, status=0x21
wd0d: device timeout reading fsbn 234162112 of 234162112-234162239
(wd0 bn 235334857; cn 14648 tn 233 sn 58), retrying
wd0: soft error (corrected)
wd0(pciide1:0:0): timeout
type: ata
c_bcount: 65536
c_skip: 0
pciide1:0:0: bus-master DMA error: missing interrupt, status=0x21
wd0d: device timeout reading fsbn 234997440 of 234997440-234997567
(wd0 bn 236170185; cn 14700 tn 233 sn 6), retrying
wd0: soft error (corrected)
wd0(pciide1:0:0): timeout
type: ata
c_bcount: 65536
c_skip: 0
pciide1:0:0: bus-master DMA error: missing interrupt, status=0x21
wd0d: device timeout reading fsbn 235719872 of 235719872-235719999
(wd0 bn 236892617; cn 14745 tn 225 sn 17), retrying
wd0: soft error (corrected)
This is a pretty good indication of what's going wrong. Your disk
is sad.
//art
