Re: [expert] Abit KT7 RAID MB (VIA chipset)
Hi Civilme, Thanks for the reply. 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 ok, I will give this a go soon. 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. no more winbloat here :) 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 ok, so is this what the linux kernel does when it boots up? it gives all those errors DriveSeek etc, then says device reset DMA disabled i think it was. 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. in the hpt bios I noticed some strange config. WD80GB can be set upto UDMA2 only. DTLA 60GB can be set upto UDMA5 max, DTLA 10GB can be set upto UDMA2 max. So it seems strange that the WD can not go upto a faster speed as its ata100 hpt etc. 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 downloaded drakopt. Unfortunatly it does not support my drives: OPTIONS: (A)--Abort (N)--New (or you changed disks around) (C)--Continue from a previous run Your Choice (N/c/a) n Drive WDCWD800BB00CAA1 not found in database Attempting to use capabilities line in hdparm -i Please report driveid to [EMAIL PROTECTED] Capabilities line not available this drive model No optimizations possible this program Drive IBMDTLA307060 not found in database Attempting to use capabilities line in hdparm -i Please report driveid to [EMAIL PROTECTED] Capabilities line not available this drive model No optimizations possible this program Drive IBMDTTA351010 not found in database Attempting to use capabilities line in hdparm -i Please report driveid to [EMAIL PROTECTED] Capabilities line not available this drive model No optimizations possible this program I tried it on my laptop and the same problem existed. I emailed [EMAIL PROTECTED] with my aditions from my laptop and it bounced back. Is there no maintainer now? Are you still working on it at all? I added my laptop drive to the config but it still would not run... 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 Also, there were some interesting logs about my system for you. Strange that: /dev/hdh1 /mnt/backup ext3 defaults,user,auto 1 2 only works when uncomented after boot, it will not mount at all during bootup for some reason. Feb 23 12:50:34 now1g kernel: ext3: No journal on filesystem on ide3(34,65) Feb 23 12:50:34 now1g mount: mount: wrong fs type, bad option, bad superblock on /dev/hdh1, Feb 23 12:50:34 now1g mount:or too many mounted file systems Feb 23 12:50:34 now1g netfs: Mounting other filesystems: failed Feb 23 12:50:31 now1g kernel: hda: DMA disabled Feb 23 12:50:31 now1g kernel: hdc: DMA disabled Feb 23 12:50:31 now1g kernel: ide2: BM-DMA at 0xe800-0xe807, BIOS settings: hde:DMA, hdf:pio Feb 23 12:50:31 now1g kernel: ide3: BM-DMA at 0xe808-0xe80f, BIOS settings: hdg:DMA, hdh:DMA Feb 23 12:50:31 now1g kernel: hda: LG DVD-ROM DRD-8120B, ATAPI CD/DVD-ROM drive Feb 23 12:50:31 now1g kernel: hdc: CR-48X5TE, ATAPI CD/DVD-ROM drive Feb 23 12:50:31 now1g kernel: hde: WDC WD800BB-00CAA1, ATA DISK drive Feb 23 12:50:31 now1g kernel: hdg: IBM-DTLA-307060, ATA DISK drive Feb 23 12:50:31 now1g kernel: hdh: IBM-DTTA-351010, ATA DISK drive Feb 23 12:50:31 now1g kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Feb 23 12:50:31 now1g kernel: ide1 at 0x170-0x177,0x376 on irq 15 Feb 23 12:50:31 now1g kernel: ide2 at 0xd800-0xd807,0xdc02 on irq 11 Feb 23 12:50:31 now1g kernel: ide3 at 0xe000-0xe007,0xe402 on irq 11 Feb 23 12:50:31 now1g kernel: hde: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=155061/16/63, UDMA(100) Feb 23 12:50:31 now1g
Re: [expert] Abit KT7 RAID MB (VIA chipset)
On Fri, 28 Feb 2003 00:19:24 +, you wrote: in the hpt bios I noticed some strange config. WD80GB can be set upto UDMA2 only. DTLA 60GB can be set upto UDMA5 max, DTLA 10GB can be set upto UDMA2 max. So it seems strange that the WD can not go upto a faster speed as its ata100 hpt etc. The UDMA setting is controlled by the manufacturer's software utility. I don't work with WD drives but I'll bet yours is set to UDMA2. Go to WD's Web site and there is probably a utility you can download to change the UDMA setting. IBM's utility runs under PCDOS on a single boot floppy. Steve Stephen B. Browne [EMAIL PROTECTED] Veritas odit moras Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Abit KT7 RAID MB (VIA chipset)
Steve Browne wrote: On Fri, 28 Feb 2003 00:19:24 +, you wrote: in the hpt bios I noticed some strange config. WD80GB can be set upto UDMA2 only. DTLA 60GB can be set upto UDMA5 max, DTLA 10GB can be set upto UDMA2 max. So it seems strange that the WD can not go upto a faster speed as its ata100 hpt etc. The UDMA setting is controlled by the manufacturer's software utility. I don't work with WD drives but I'll bet yours is set to UDMA2. Go to WD's Web site and there is probably a utility you can download to change the UDMA setting. IBM's utility runs under PCDOS on a single boot floppy. Steve Stephen B. Browne [EMAIL PROTECTED] Veritas odit moras If you grep the kernel changelog, you will see some evidence of how WD drives are not always capable of running in linux at high dma settings: $ rpm -q --changelog kernel-2.4.21.0.pre3.2mdk-1-1mdk| grep -i WD * put another WD disk in the ide-dma black list. - Modify the wdelay handling. Civileme has written a lot on this topic and maybe he can speak more to your case. You could search the list archives for this and Google will turn up some background. Here are a couple of archived posts: http://www.mail-archive.com/[EMAIL PROTECTED]/msg60691.html http://www.mail-archive.com/[EMAIL PROTECTED]/msg65800.html Rolf Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Abit KT7 RAID MB (VIA chipset)
On Thursday 27 February 2003 03:19 pm, J. Grant wrote: Hi Civilme, Thanks for the reply. 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 ok, I will give this a go soon. 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. no more winbloat here :) 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 ok, so is this what the linux kernel does when it boots up? it gives all those errors DriveSeek etc, then says device reset DMA disabled i think it was. 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. in the hpt bios I noticed some strange config. WD80GB can be set upto UDMA2 only. DTLA 60GB can be set upto UDMA5 max, DTLA 10GB can be set upto UDMA2 max. So it seems strange that the WD can not go upto a faster speed as its ata100 hpt etc. 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 downloaded drakopt. Unfortunatly it does not support my drives: OPTIONS: (A)--Abort (N)--New (or you changed disks around) (C)--Continue from a previous run Your Choice (N/c/a) n Drive WDCWD800BB00CAA1 not found in database Attempting to use capabilities line in hdparm -i Please report driveid to [EMAIL PROTECTED] Capabilities line not available this drive model No optimizations possible this program Drive IBMDTLA307060 not found in database Attempting to use capabilities line in hdparm -i Please report driveid to [EMAIL PROTECTED] Capabilities line not available this drive model No optimizations possible this program Drive IBMDTTA351010 not found in database Attempting to use capabilities line in hdparm -i Please report driveid to [EMAIL PROTECTED] Capabilities line not available this drive model No optimizations possible this program I tried it on my laptop and the same problem existed. I emailed [EMAIL PROTECTED] with my aditions from my laptop and it bounced back. Is there no maintainer now? Are you still working on it at all? I added my laptop drive to the config but it still would not run... 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 Also, there were some interesting logs about my system for you. Strange that: /dev/hdh1 /mnt/backup ext3 defaults,user,auto 1 2 only works when uncomented after boot, it will not mount at all during bootup for some reason. Feb 23 12:50:34 now1g kernel: ext3: No journal on filesystem on ide3(34,65) Feb 23 12:50:34 now1g mount: mount: wrong fs type, bad option, bad superblock on /dev/hdh1, Feb 23 12:50:34 now1g mount:or too many mounted file systems Feb 23 12:50:34 now1g netfs: Mounting other filesystems: failed Feb 23 12:50:31 now1g kernel: hda: DMA disabled Feb 23 12:50:31 now1g kernel: hdc: DMA disabled Feb 23 12:50:31 now1g kernel: ide2: BM-DMA at 0xe800-0xe807, BIOS settings: hde:DMA, hdf:pio Feb 23 12:50:31 now1g kernel: ide3: BM-DMA at 0xe808-0xe80f, BIOS settings: hdg:DMA, hdh:DMA Feb 23 12:50:31 now1g kernel: hda: LG DVD-ROM DRD-8120B, ATAPI CD/DVD-ROM drive Feb 23 12:50:31 now1g kernel: hdc: CR-48X5TE, ATAPI CD/DVD-ROM drive Feb 23 12:50:31 now1g kernel: hde: WDC WD800BB-00CAA1, ATA DISK drive Feb 23 12:50:31 now1g kernel: hdg: IBM-DTLA-307060, ATA DISK drive Feb 23 12:50:31 now1g kernel: hdh: IBM-DTTA-351010, ATA DISK drive Feb 23 12:50:31 now1g kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Feb 23 12:50:31 now1g kernel: ide1 at 0x170-0x177,0x376 on irq 15 Feb 23 12:50:31 now1g kernel: ide2 at 0xd800-0xd807,0xdc02 on irq 11 Feb 23 12:50:31 now1g kernel: ide3 at
Re: [expert] Abit KT7 RAID MB (VIA chipset)
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 HdSw15uSec SpinMotCtl Fixed DTR5Mbs 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 HdSw15uSec Fixed DTR10Mbs }
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 HdSw15uSec Fixed DTR10Mbs }
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
[expert] Abit KT7 RAID MB (VIA chipset)
Hi,
I've got one Abit KT7 RAID MB system running stock mdk9 kernel. Its running, however, the hd speed is slow because it only works with no dma etc. I am using the correct ata100 cables with only a single drive on each channel.
Has anyone else experienced this with this motherboard using the raid channels?
Cheers
JG
Journalled Block Device driver loaded
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Re: [expert] Abit KT7 RAID MB (VIA chipset)
J. Grant wrote: Hi, I've got one Abit KT7 RAID MB system running stock mdk9 kernel. Its running, however, the hd speed is slow because it only works with no dma etc. I am using the correct ata100 cables with only a single drive on each channel. Has anyone else experienced this with this motherboard using the raid channels? Cheers JG I see you have the hpt370 onboard controller. Although not an exact match, I have hpt372 onboard Iwill XP-333R and it works well as an extra ide controller for me with the newer kernels in RC1 or in cooker. Alan Cox's ide patches from 2.4.20-ac1 have been merged and it enables my controller to work this way w/o having to build Highpoint's driver for the first time. Don't know if that carries over to your controller but someone said they use the same BIOS. I am running the lates BIOS for my board, as well. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Abit KT7 RAID MB (VIA chipset)
Grant,
I was using the same board until a couple of days ago, it now has
windows. Well, I was using my IBM HD on the ata100 HPT 370 channels and
I had around 35 Mb/sec txr rate using hdparm.
-Fridhar
J. Grant wrote:
Hi,
I've got one Abit KT7 RAID MB system running stock mdk9 kernel. Its
running, however, the hd speed is slow because it only works with no
dma etc. I am using the correct ata100 cables with only a single drive
on each channel.
Has anyone else experienced this with this motherboard using the raid
channels?
Cheers
JG
Journalled Block Device driver loaded
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Re: [expert] Abit KT7 RAID MB (VIA chipset)
J. Grant wrote:
Hi,
I've got one Abit KT7 RAID MB system running stock mdk9 kernel. Its
running, however, the hd speed is slow because it only works with no
dma etc. I am using the correct ata100 cables with only a single drive
on each channel.
Has anyone else experienced this with this motherboard using the raid
channels?
Cheers
JG
Journalled Block Device driver loaded
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Jus wondering, have up updated ur bios.
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Re: [expert] Abit KT7 RAID MB (VIA chipset)
Sridhar wrote:
J. Grant wrote:
Hi,
I've got one Abit KT7 RAID MB system running stock mdk9 kernel. Its
running, however, the hd speed is slow because it only works with no
dma etc. I am using the correct ata100 cables with only a single drive
on each channel.
Has anyone else experienced this with this motherboard using the raid
channels?
Cheers
JG
Journalled Block Device driver loaded
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
Jus wondering, have up updated ur bios.
Just wondering, are you using WD harddrives?
drjung
--
J. Craig Woods
UNIX Network/System Administration
http://www.trismegistus.net/resume.html
Character is built upon the debris of despair --Emerson
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Re: [expert] Abit KT7 RAID MB (VIA chipset)
On Thursday 20 February 2003 05:51 pm, J. Craig Woods wrote:
Sridhar wrote:
J. Grant wrote:
Hi,
I've got one Abit KT7 RAID MB system running stock mdk9 kernel. Its
running, however, the hd speed is slow because it only works with no
dma etc. I am using the correct ata100 cables with only a single drive
on each channel.
Has anyone else experienced this with this motherboard using the raid
channels?
Cheers
JG
Journalled Block Device driver loaded
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide2: reset: success
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.
Civileme
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Re: [expert] Abit KT7 RAID MB (VIA chipset)
Hi, Thanks for the info. I did download the propreitary hpt370 kernel module, but it was only binary and I could not get the root disk to work. Perhaps I should try a newer kernel than 2.4.19-16mdk, have you tried with the default mdk9 kernel on your board at all? I have the latest bios for my board, I don't think much of highpoint's support. Cheers JG I see you have the hpt370 onboard controller. Although not an exact match, I have hpt372 onboard Iwill XP-333R and it works well as an extra ide controller for me with the newer kernels in RC1 or in cooker. Alan Cox's ide patches from 2.4.20-ac1 have been merged and it enables my controller to work this way w/o having to build Highpoint's driver for the first time. Don't know if that carries over to your controller but someone said they use the same BIOS. I am running the lates BIOS for my board, as well. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Abit KT7 RAID MB (VIA chipset)
J. Grant wrote: Hi, Thanks for the info. I did download the propreitary hpt370 kernel module, but it was only binary and I could not get the root disk to work. Perhaps I should try a newer kernel than 2.4.19-16mdk, have you tried with the default mdk9 kernel on your board at all? I have the latest bios for my board, I don't think much of highpoint's support. Cheers JG The default 9.0 kernel was one I had to rebuild for the hpt driver. The patches that allow me to use this controller as jbod w/o building a kernel came in at 2.4.21-0.pre3.2mdk. You could try installing the cooker kernel. Also, if these drives are WD, see the other posts about WD drives. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] Abit KT7 RAID MB (VIA chipset)
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...
When booting bios if hardrive is on hda,hdb,hdc or hdd normal speed channe:
Primary IDE channel no 80 conductor cable installed. It boots, and even
with new cables I saw this error. My fried also has this on another
abit board, and his works ok too. Not sure what it means though.
dmesg|less had lots of usb stuff and not much bootup, is this meant to
be wiped out when the computer is running for a while?
usb-uhci.c: interrupt, status 28, frame# 1427
usb-uhci.c: Host controller halted, trying to restart.
Also some hdh stuff
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: DMA disabled
ide3: reset: success
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide3: reset: success
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev 22:41 (hdh), sector 32
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdh: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide3: reset: success
here is the real /var/log/dmesg file,
Linux version 2.4.19-16mdk ([EMAIL PROTECTED]) (gcc version
3.2 (Mandrake Linux 9.0 3.2-1mdk)) #1 Fri Sep 20 18:15:05 CEST 2002
BIOS-provided physical RAM map:
BIOS-e820: - 000a (usable)
BIOS-e820: 000f - 0010 (reserved)
BIOS-e820: 0010 - 17ff (usable)
BIOS-e820: 17ff - 17ff3000 (ACPI NVS)
BIOS-e820: 17ff3000 - 1800 (ACPI data)
BIOS-e820: - 0001 (reserved)
383MB LOWMEM available.
Advanced speculative caching feature not present
On node 0 totalpages: 98288
zone(0): 4096 pages.
zone(1): 94192 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=linux-2.4.19mdk ro root=2102 devfs=mount
hdc=ide-scsi
ide_setup: hdc=ide-scsi
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
Detected 1000.070 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 1992.29 BogoMIPS
Memory: 386360k/393152k available (1176k kernel code, 6408k reserved,
444k data, 136k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: Before vendor init, caps: 0183fbff c1c7fbff , vendor = 2
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After vendor init, caps: 0183fbff c1c7fbff
Intel machine check architecture supported.
Intel machine check
