> > That can't be true, at least not for the IBM DeskStars I own, I've
> > NEVER EVER seen them do that, one proof should be:
>
> same here
>
> wdc0: unit 0 (wd0): <IBM-DTTA-350840>, DMA, 32-bit, multi-block-16
> wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S
> wdc0: unit 1 (wd1): <IBM-DTTA-351010>, DMA, 32-bit, multi-block-16
> wd1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S
> wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
> wdc1: unit 0 (wd2): <IBM-DTTA-351010>, DMA, 32-bit, multi-block-16
> wd2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S
I ran into this exact problem on a small LAN server with a single deskstar
drive. Usually I would just see the error in the logs once or twice a
month without incident, but one time it took down the server hard enough
to munge quite a few files. The drive is now in a dualboot win98/freebsd
multimedia box and I haven't seen the error again (the box isn't up for a
week at a time).
- Mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
