On Thursday 20 February 2003 08:42 pm, J. Grant wrote:
> Hi,
>
> Thanks for the quick replies drjung, civilme, rolf and sridhar.
>
> >> > Jus wondering, have up updated ur bios.
> >>
> >> Just wondering, are you using WD harddrives?
> >>
> >> drjung
> >
> > I was wondering the same thing. I am aware that Andre Hedrick has
> > campaigned for a while to keep WDs off of udma3 or higher because they
> > don't exactly comply with the requirements for the CRC protocols for
> > those speeds.
> >
> > ANd My thoughts fall first to WD when I see {DriveReady SeekComplete}
> > because that is the only brand on which I have seen it.
>
> I'm using the latest hpt370 bios
>
> This is my system spec atm.
>
> Abit KT7-RAID (VIA chipset)
> Award BIOS Ver 6.00PG (01/31/2002-8363-686A-6A6LMA19C-7N)
> Highpoint RAID BIOS Ver 1.11.0402
> Triones Technologies, Inc. HPT366 (rev 03)
> Guilmott nVidia Corporation NV15 (Geforce2 GTS) (rev a4)
> VT82C586B USB (rev 10)
>
> I've noticed this problem for a while.. but not found the solution while
> looking. It crashes twice a month or so, not sure if this is related.
> I've not lost any data.. yet...
>
> Below I will paste dmesg and the hd spec. yes there is a WD one...
>
> VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:07.1
> ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:DMA, hdd:pio
> HPT370: IDE controller on PCI bus 00 dev 98
> PCI: Found IRQ 11 for device 00:13.0
> PCI: Sharing IRQ 11 with 00:09.0
> HPT370: chipset revision 3
> HPT370: not 100% native mode: will probe irqs later
> HPT370: using 33MHz PCI clock
> ide2: BM-DMA at 0xe800-0xe807, BIOS settings: hde:DMA, hdf:pio
> ide3: BM-DMA at 0xe808-0xe80f, BIOS settings: hdg:DMA, hdh:DMA
> hda: LG DVD-ROM DRD-8120B, ATAPI CD/DVD-ROM drive
> hdc: CR-48X5TE, ATAPI CD/DVD-ROM drive
> hde: WDC WD800BB-00CAA1, ATA DISK drive
> hdg: IBM-DTLA-307060, ATA DISK drive
> hdh: IBM-DTTA-351010, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> ide2 at 0xd800-0xd807,0xdc02 on irq 11
> ide3 at 0xe000-0xe007,0xe402 on irq 11
> hde: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=155061/16/63,
> UDMA(100)
> hdg: 120103200 sectors (61493 MB) w/1916KiB Cache, CHS=119150/16/63,
> UDMA(44)
> hdh: 19807200 sectors (10141 MB) w/466KiB Cache, CHS=19650/16/63, UDMA(33)
>
>
> These are the HD's
>
>
>
> 80 GB
> Model=WDC WD800BB-00CAA1, FwRev=17.07W17, SerialNo=WD-WMA8E3405796
> Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq
> } RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
> BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=156301488
> IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2
> UDMA modes: udma0 udma1 udma2
> AdvancedPM=no WriteCache=enabled
> Drive conforms to: device does not report version: 1 2 3 4 5
>
>
> hdparm /dev/hde
>
> /dev/hde:
> multcount = 16 (on)
> IO_support = 0 (default 16-bit)
> unmaskirq = 0 (off)
> using_dma = 1 (on)
> keepsettings = 0 (off)
> readonly = 0 (off)
> readahead = 8 (on)
> geometry = 155061/16/63, sectors = 156301488, start = 0
>
>
> DMA is on here, strange.. I thought it was off
>
> hdg: IBM-DTLA-307060, ATA DISK drive 60 GB
> Model=IBM-DTLA-307060, FwRev=TX8OA5AA, SerialNo=YQDYQF8P261
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
> BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=120103200
> 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
> UDMA modes: udma0 udma1 udma2 *udma3 udma4 udma5
> AdvancedPM=yes: disabled (255) WriteCache=enabled
> Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: 2 3 4 5
>
> Superblock backups stored on blocks:
> 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
> 4096000, 7962624, 11239424
>
> [EMAIL PROTECTED] now3d]# hdparm -tT /dev/hde
>
> /dev/hde:
> Timing buffer-cache reads: 128 MB in 0.96 seconds =133.33 MB/sec
> Timing buffered disk reads: 64 MB in 2.38 seconds = 26.89 MB/sec
>
>
>
> hdh: IBM-DTTA-351010, ATA DISK drive 10 GB
> Model=IBM-DTTA-351010, FwRev=T56OA73A, SerialNo=WF0WFHW1710
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=34
> BuffType=DualPortCache, BuffSize=466kB, MaxMultSect=16, MultSect=16
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=19807200
> IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2
> UDMA modes: udma0 udma1 *udma2
> AdvancedPM=no WriteCache=enabled
> Drive conforms to: ATA/ATAPI-4 T13 1153D revision 17: 1 2 3 4
well first of all, if you can split ide drives to one per channel, that would
be more efficient. ONly one device per channel on IDE may be active, and two
disks on the same channel really slows down disk-to-disk operations
Next a DTLA and a DTTA on the same channel is a wide difference in timing
specs. This leaves enough room for echo bounce on a signal gating line to
cause mischief.
It is not that hard to move a drive if the installed systems have the
/etc/fstab modified (of course with any winsystems we have a little more
work) to recognize the new location.
The WD should not be paired on any channel with any other hard drive,because
its timing is very strange compared to the others and data can be eaten by
timing chatter. It is safely default configured as you can see, peaked at
udma2
I would definitely try limiting the DTLA to udma2 as well --it appears to be
set initially for udma3
the DTTA can go to udma4 or perhaps more.
drakopt is in /contribs these days, but it does an alternative test and setup
for tuning, and it runs in python. It may be able to set the drives where
they run reliably. It requires some manual asistance yet because I never had
time to finish the parser for error messages nor to make the settings within
2% of each other in tested speed "brothers" and to choose the brother with
the highest noise immunity. Still you might find the program useful for
performing all the tests of various hdparm settings--none of those are
dangerous to existing data.
I strongly suspect a timing problem between the two IBM drives and I would
suggest splitting them to different channels as a first step. The slow
performance appears to be a fallback setting from probable timing crosstalk.
Civileme
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
