heres the output of /sbin/hdparm -i /dev/hda:
Model=ST310212A, FwRev=3.02, SerialNo=5EG266T9
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=512kB, MaxMultSect=32, MultSect=off
CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=20005650
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4
so far with dma turned off, i get no errors, but my mobo can handle
66,but that info it not really saying if my hdd can handle it, looking
at 'dmesg' it suggests a udma33, how would i tell hdparm to run at 33,
as the only optiop i can find is either off/on, or will it run it at the
designated hdd speed?
Jul 18 23:32:44 ogri kernel: ide: Assuming 33MHz system bus speed for
PIO modes;override with idebus=xx
Mark
On 18 Jul 2001 16:57:16 -0600, Jim Cromie wrote:
> mark wrote:
>
> > I have noticed a lot of these errors in my /var/log/messages
> >
> > Jul 18 01:00:10 ogri kernel: hda: dma_intr: status=0x51 { DriveReady
> > SeekComplete Error }
> > Jul 18 01:00:10 ogri kernel: hda: dma_intr: error=0x84 {
> > DriveStatusError
> > BadCRC }
>
> Ive seen these kind of errors when hacking too hard with
>
> hdparm -X66 -vtT /dev/hda # -tT tests thruput at interface and media
>
>
> I believe I turned it (UDMA) up too far (both drive and mobo must support).
>
> try hdparm -i /dev/hda to see what your hd says it can do.
>
>
> this is not an answer, only an idea.
> hth
>
>
>
>
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list
>
--
----
A penguin a day keeps the fatal exceptions away...
Registered Linux User: 208939
Licq: 119422259
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
