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):
Soren Schmidt wrote:
[SNIP]
Have you tried putting disks on the UDMA66 channel ?? I think it
should work in upto WDMA mode now with the ata driver...
I have first to install 4.0 and from my wd2 (I've got a little help from
RNordier, I should make do)
Then, I'll get a UDMA-66 drive (any
It seems Thierry Herbelot wrote:
Soren Schmidt wrote:
[SNIP]
Have you tried putting disks on the UDMA66 channel ?? I think it
should work in upto WDMA mode now with the ata driver...
I have first to install 4.0 and from my wd2 (I've got a little help from
RNordier, I should make
In message [EMAIL PROTECTED], Garrett Wollman writes:
On Tue, 10 Aug 1999 12:38:02 -0700 (PDT), Doug White [EMAIL PROTECTED]
said:
You've got to be kidding. That makes them totally useless for server
operation -- at some random time every week, down goes your server for a
few minutes. :(
An unrelated question:
I get the following in my dmesg:
/kernel: ata0: master: setting up UDMA2 mode on PIIX4 chip OK
/kernel: ad0: TOSHIBA MK6409MAV/F5.01 A ATA-4 disk at ata0 as master
/kernel: ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T,
512 B/S
/kernel: ad0: piomode=4,
Soren Schmidt wrote:
[SNIP]
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
I'm starting to see the following errors more frequently on my 3
servers running current dated July 30.
Aug 6 14:08:36 kern.crit /kernel: wd0: interrupt timeout
(status 58rdy,seekdone,drq error 1no_dam)
Aug 6 14:08:38 kern.crit /kernel: wd0: wdtimeout() DMA status 4
All 3
