Fw: DriveReady SeekComplete problems

Fw: DriveReady SeekComplete problems

[Artur Jasowicz]

I've posted the message below to linux-kernel, but there were no replies. Does anyone here have any suggestions?

I am building a file server with 5 drive software RAID5 array. I am using three IWill SIDE-100 (Highpoint 370A) controllers as my IDE interfaces, not using their RAID functionality. One Maxtor 160GB drive per channel, two channels per controller. I plan on adding hot spare as the sixth drive in the future. There's one 160GB partition on each drive. Linux version 2.4.19-pre7smp-020502b (root@production) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #6 SMP Thu May 2 12:15:34 CDT 2002
This is a dual Athlon 2000+ MP on Tyan Tiger S2466N-4 with 1GB RAM. OS and swap runs on separate drives and controllers. This array will be just for data once it is configured.

Below are the most relevant parts of my logs. I will post further details if anyone is willing to help, just let me know what info you need. Any suggestions greatly appreciated.

Artur

After issuing mkraid the system went to syncing RAID and following appeared in my syslog:

May  7 17:34:39 production kernel: RAID5 conf printout:
May  7 17:34:39 production kernel:  --- rd:5 wd:5 fd:0
May  7 17:34:39 production kernel:  disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hde1
May  7 17:34:39 production kernel:  disk 1, s:0, o:1, n:1 rd:1 us:1 dev:hdg1
May  7 17:34:39 production kernel:  disk 2, s:0, o:1, n:2 rd:2 us:1 dev:hdi1
May  7 17:34:39 production kernel:  disk 3, s:0, o:1, n:3 rd:3 us:1 dev:hdk1
May  7 17:34:39 production kernel:  disk 4, s:0, o:1, n:4 rd:4 us:1 dev:hdm1
May  7 17:34:39 production kernel: md: updating md3 RAID superblock on device
May  7 17:34:39 production kernel: md: hdm1 [events: 00000001]<6>(write) hdm1's sb offset: 160079552
May  7 17:34:39 production kernel: md: syncing RAID array md3
May  7 17:34:39 production kernel: md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.
May  7 17:34:39 production kernel: md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction.
May  7 17:34:39 production kernel: md: using 124k window, over a total of 160079488 blocks.
May  7 17:34:39 production kernel: md: hdk1 [events: 00000001]<6>(write) hdk1's sb offset: 160079552
May  7 17:34:39 production kernel: hde: 0 bytes in FIFO
May  7 17:34:39 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May  7 17:34:39 production kernel: hde: dma_intr: bad DMA status (dma_stat=1)
May  7 17:34:39 production kernel: hde: dma_intr: status=0x50 { DriveReady SeekComplete }
May  7 17:34:39 production kernel: hdi: 4 bytes in FIFO
May  7 17:34:39 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May  7 17:34:39 production kernel: hdi: dma_intr: bad DMA status (dma_stat=1)
May  7 17:34:39 production kernel: hdi: dma_intr: status=0x50 { DriveReady SeekComplete }
May  7 17:34:39 production kernel: hdi: 192 bytes in FIFO
May  7 17:34:39 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May  7 17:34:39 production kernel: hdi: dma_intr: bad DMA status (dma_stat=1)
May  7 17:34:39 production kernel: hdi: dma_intr: status=0x50 { DriveReady SeekComplete }
May  7 17:34:39 production kernel: md: hdi1 [events: 00000001]<6>(write) hdi1's sb offset: 160079552
May  7 17:34:39 production kernel: hdi: 128 bytes in FIFO
May  7 17:34:39 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May  7 17:34:39 production kernel: hdi: dma_intr: bad DMA status (dma_stat=1)
May  7 17:34:39 production kernel: hdi: dma_intr: status=0x50 { DriveReady SeekComplete }
May  7 17:34:39 production kernel: hdk: 128 bytes in FIFO
[...snip...]
May  7 17:34:41 production kernel: hdk: 64 bytes in FIFO
May  7 17:34:41 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May  7 17:34:41 production kernel: hdk: dma_intr: bad DMA status (dma_stat=1)
May  7 17:34:41 production kernel: hdk: dma_intr: status=0x50 { DriveReady SeekComplete }
May  7 17:34:41 production kernel: hdk: recal_intr: status=0xd0 { Busy }
May  7 17:34:41 production kernel: hdk: DMA disabled
May  7 17:34:41 production kernel: ide5: reset: success
May  7 17:34:50 production kernel: hdi: timeout waiting for DMA
May  7 17:34:50 production kernel: hdi: 12 bytes in FIFO
May  7 17:34:50 production kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
May  7 17:34:50 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May  7 17:34:50 production kernel: hdi: drive not ready for command

Simillar messages were reported for /dev/hdm, hdi, hde, hdk

I've mdstopped the process and disbled DMA for all RAID members with hdparm -d 0. Tried mdrun again and got following messages:

May  7 18:43:26 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May  7 18:43:26 production kernel: hdi: drive not ready for command
May  7 18:44:40 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May  7 18:44:40 production kernel: hdi: drive not ready for command
May  7 18:44:52 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May  7 18:44:52 production kernel: hdi: drive not ready for command
May  7 18:46:45 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May  7 18:46:45 production kernel: hdi: drive not ready for command
May  7 18:47:11 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May  7 18:47:11 production kernel: hdi: drive not ready for command
May  7 18:47:32 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May  7 18:47:32 production kernel: hdi: drive not ready for command
May  7 18:47:57 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May  7 18:47:57 production kernel: hdi: drive not ready for command
May  7 18:48:09 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May  7 18:48:09 production kernel: hdi: drive not ready for command
May  7 18:48:18 production kernel: hdk: write_intr error1: nr_sectors=128, stat=0xd0
May  7 18:48:18 production kernel: hdk: write_intr: status=0xd0 { Busy }
May  7 18:48:18 production kernel: ide5: reset: success
May  7 18:48:27 production kernel: hdi: status error: status=0x58 { DriveReady SeekComplete DataRequest }
May  7 18:48:27 production kernel: hdi: drive not ready for command
May  7 18:48:27 production kernel: hdi: status timeout: status=0xd0 { Busy }
May  7 18:48:27 production kernel: hdi: drive not ready for command
May  7 18:48:28 production kernel: ide4: reset: success
May  7 18:48:43 production kernel: raid5: parity resync was not fully finished, restarting next time.
May  7 18:48:43 production kernel: md: md_do_sync() got signal ... exiting
May  7 18:48:44 production kernel: raid5: resync aborted!

Re: Fw: DriveReady SeekComplete problems

[Karsten Becker]

Artur Jasowicz wrote:

>I've posted the message below to linux-kernel, but there were no replies. Does anyone here have any suggestions?
>
>I am building a file server with 5 drive software RAID5 array. I am using three IWill SIDE-100 (Highpoint 370A) controllers as my IDE interfaces, not using their RAID functionality. One Maxtor 160GB drive per channel, two channels per controller. I plan on adding hot spare as the sixth drive in the future. There's one 160GB partition on each drive. Linux version 2.4.19-pre7smp-020502b (root@production) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #6 SMP Thu May 2 12:15:34 CDT 2002
>This is a dual Athlon 2000+ MP on Tyan Tiger S2466N-4 with 1GB RAM. OS and swap runs on separate drives and controllers. This array will be just for data once it is configured.
>
>Below are the most relevant parts of my logs. I will post further details if anyone is willing to help, just let me know what info you need. Any suggestions greatly appreciated.
>
I Had the same problem on my old Server. I found out that gigabyte said, 
this is a 33UDMA-Board but linux tried to run the disk in UDMA66. 
Throtteling down the disks using HDPARM -X was the solution for me.
cheers,
Karsten

Re: Fw: DriveReady SeekComplete problems

[Artur Jasowicz]

From: Karsten Becker <KB@Karsten-Becker.de>
> Artur Jasowicz wrote:
>
> >I've posted the message below to linux-kernel, but there were no replies.
Does anyone here have any suggestions?
> >
> >I am building a file server with 5 drive software RAID5 array. I am using
three IWill SIDE-100 (Highpoint 370A) controllers as my IDE interfaces, not
using their RAID functionality. One Maxtor 160GB drive per channel, two
channels per controller. I plan on adding hot spare as the sixth drive in
the future. There's one 160GB partition on each drive. Linux version
2.4.19-pre7smp-020502b (root@production) (gcc version 2.96 20000731 (Red Hat
Linux 7.1 2.96-98)) #6 SMP Thu May 2 12:15:34 CDT 2002
> >This is a dual Athlon 2000+ MP on Tyan Tiger S2466N-4 with 1GB RAM. OS
and swap runs on separate drives and controllers. This array will be just
for data once it is configured.
> >
> >Below are the most relevant parts of my logs. I will post further details
if anyone is willing to help, just let me know what info you need. Any
suggestions greatly appreciated.
> >
> I Had the same problem on my old Server. I found out that gigabyte said,
> this is a 33UDMA-Board but linux tried to run the disk in UDMA66.
> Throtteling down the disks using HDPARM -X was the solution for me.
> cheers,
> Karsten

Thanks for the comment. Actually, the card is 100-capable and the drives are
133s, but hdparm indicates that they run at 100. I've tried taking the
drives down to UDMA2 (33M) with hdparm -X66, but same problem occured.
I wonder if that's not the PCI getting killed with too much traffic.
Artur

Re: Fw: DriveReady SeekComplete problems

[Artur Jasowicz]

Actually, I did something along these lines early on in testing. I had four
diferent drives plugged in. I had one 6GB, two 80GB and one 160GB. I've
tried doing dd if=/dev/hd... of=/dev/null. This was with DMA on. Everything
seemed to work fine with up to three drives, but after I've issused above
command for the fourth drive, I started getting errror messages. Now, to my
knowledge I'm not using a Highpoint driver. I'm just letting Kernel detect
whatever it sees and use it.

Today, I've tried mkraid on 4-drive config. With DMA disabled it seemed to
work without errors at miserable 500K/s reported by /proc/mdstat. Even my
old K6-2 333 with four 80GB on two IWills ran at 800+K/s. You would expect
more from a dual 2GHz. With DMA enabled I got 2000K/s with log full of the
same errors again.

Another odd thing is that both CPUs are running at 99% usage when trying to
sync array. Strange for 4GHz total clock speed. I was expecting that such
fast CPU's would barely break the sweat doing IDE I/O.

Any other IDE controllers I should be looking at?

Artur

From: Pieter Hollants <pieter@hollants.com>
> I'd say it's a driver problem (had nothing but trouble with Highpoint
> myself).
> To verify this: try creating an ordinary partition on one of the disks and
> do some mass copying & reading onto it, with and without DMA disabled.
> You'll most certainly still get these errors.
>
> Artur Jasowicz sagte:
> > I am building a file server with 5 drive software RAID5 array. I am
> > using three IWill SIDE-100 (Highpoint 370A) controllers as my IDE
> > interfaces, not using their RAID functionality. One Maxtor 160GB drive
> > per channel, two channels per controller. I plan on adding hot spare as
> > the sixth drive in the future. There's one 160GB partition on each
> > drive. Linux version 2.4.19-pre7smp-020502b (root@production) (gcc
> > version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #6 SMP Thu May 2
> > 12:15:34 CDT 2002
>  This is a dual Athlon 2000+ MP on Tyan Tiger
> > S2466N-4 with 1GB RAM. OS and swap runs on separate drives and
> > controllers. This array will be just for data once it is configured.
> [...]
> > 17:34:39 production kernel: md: hdk1 [events: 00000001]<6>(write)
> > hdk1's sb offset: 160079552
>  May  7 17:34:39 production kernel: hde: 0
> > bytes in FIFO
> > May  7 17:34:39 production kernel: ide_dmaproc: chipset supported
> > ide_dma_timeout func only: 14
>  May  7 17:34:39 production kernel: hde:
> > dma_intr: bad DMA status (dma_stat=1)
>  May  7 17:34:39 production
> > kernel: hde: dma_intr: status=0x50 { DriveReady SeekComplete }
>  May  7
> > 17:34:39 production kernel: hdi: 4 bytes in FIFO
> [...]
> >
> > I've mdstopped the process and disbled DMA for all RAID members with
> > hdparm -d 0. Tried mdrun again and got following messages:
>
> > May  7 18:43:26 production kernel: hdi: status error: status=0x58 {
> > DriveReady SeekComplete DataRequest }
>  May  7 18:43:26 production
> > kernel: hdi: drive not ready for command
>  May  7 18:44:40 production
> > kernel: hdi: status error: status=0x58 { DriveReady SeekComplete
> > DataRequest }
>  May  7 18:44:40 production kernel: hdi: drive not ready
> > for command

Re: Fw: DriveReady SeekComplete problems

[Artur Jasowicz]

From: Maurice Hilarius
> With regards to your message at 03:13 PM 5/9/02, Artur Jasowicz. Where you
> stated:
> >I am building a file server with 5 drive software RAID5 array. I am using
> >three IWill SIDE-100 (Highpoint 370A) controllers as my IDE interfaces,
> >not using their RAID functionality. One Maxtor 160GB drive per channel,
> >two channels per controller. I plan on adding hot spare as the sixth
drive
> >in the future. There's one 160GB partition on each drive. Linux version
> >2.4.19-pre7smp-020502b (root@production) (gcc version 2.96 20000731 (Red
> >Hat Linux 7.1 2.96-98)) #6 SMP Thu May 2 12:15:34 CDT 2002
> >This is a dual Athlon 2000+ MP on Tyan Tiger S2466N-4 with 1GB RAM. OS
and
> >swap runs on separate drives and controllers. This array will be just for
> >data once it is configured.
> >
> >Below are the most relevant parts of my logs. I will post further details
> >if anyone is willing to help, just let me know what info you need. Any
> >suggestions greatly appreciated.
>
> Probably cable problem..
May be, although I've used original, 18in cables, changed the config to use
diferent controllers, the errors came from all drives, randomly. Isn't it
unlikely, that all cables are bad?

>
> Maybe cards not getting a clean IRQ status.
>
I'm not sure what you mean by that, here's my IRQs is that ok?
[root@production root]# cat /proc/interrupts
           CPU0       CPU1
  0:    1060111     900968    IO-APIC-edge  timer
  1:       2223       1623    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  5:     475613     476603   IO-APIC-level  ide2, ide3, eth1
  8:          1          0    IO-APIC-edge  rtc
  9:     464960     465255   IO-APIC-level  ide4, ide5, eth2
 10:      12405      11231   IO-APIC-level  eth0
 11:      69567      67494   IO-APIC-level  ide6
 12:        159       1172    IO-APIC-edge  PS/2 Mouse
 14:      48388      44855    IO-APIC-edge  ide0
 15:      48907      47090    IO-APIC-edge  ide1
NMI:          0          0
LOC:    1961162    1961161
ERR:          0
MIS:          0

Re: Fw: DriveReady SeekComplete problems

[Diamon]

----- Original Message -----
From: "Artur Jasowicz" <arturj@mousebusiness.com>
To: <linux-raid@vger.kernel.org>
Cc: "Maurice Hilarius" <maurice@harddata.com>
Sent: Thursday, May 09, 2002 11:16 PM
Subject: Re: Fw: DriveReady SeekComplete problems


> From: Maurice Hilarius
> > With regards to your message at 03:13 PM 5/9/02, Artur Jasowicz. Where
you
> > stated:
> > >I am building a file server with 5 drive software RAID5 array. I am
using
> > >three IWill SIDE-100 (Highpoint 370A) controllers as my IDE interfaces,
> > >not using their RAID functionality. One Maxtor 160GB drive per channel,
> > >two channels per controller. I plan on adding hot spare as the sixth
> drive
> > >in the future. There's one 160GB partition on each drive. Linux version
> > >2.4.19-pre7smp-020502b (root@production) (gcc version 2.96 20000731
(Red
> > >Hat Linux 7.1 2.96-98)) #6 SMP Thu May 2 12:15:34 CDT 2002
> > >This is a dual Athlon 2000+ MP on Tyan Tiger S2466N-4 with 1GB RAM. OS
> and
> > >swap runs on separate drives and controllers. This array will be just
for
> > >data once it is configured.
> > >
> > >Below are the most relevant parts of my logs. I will post further
details
> > >if anyone is willing to help, just let me know what info you need. Any
> > >suggestions greatly appreciated.
> >
> > Probably cable problem..
> May be, although I've used original, 18in cables, changed the config to
use
> diferent controllers, the errors came from all drives, randomly. Isn't it
> unlikely, that all cables are bad?
>

    Unless those aren't ATA-100 cables and it's still using ATA-100 mode...
I think ATA-66 or higher you need those 80-wire cables...  Just a thought.
And the solid-core 80 pin cables don't handle folding well at all, maybe
something's gone flaky in them?

> >
> > Maybe cards not getting a clean IRQ status.
> >
> I'm not sure what you mean by that, here's my IRQs is that ok?
> [root@production root]# cat /proc/interrupts
>            CPU0       CPU1
>   0:    1060111     900968    IO-APIC-edge  timer
>   1:       2223       1623    IO-APIC-edge  keyboard
>   2:          0          0          XT-PIC  cascade
>   5:     475613     476603   IO-APIC-level  ide2, ide3, eth1
>   8:          1          0    IO-APIC-edge  rtc
>   9:     464960     465255   IO-APIC-level  ide4, ide5, eth2
>  10:      12405      11231   IO-APIC-level  eth0
>  11:      69567      67494   IO-APIC-level  ide6
>  12:        159       1172    IO-APIC-edge  PS/2 Mouse
>  14:      48388      44855    IO-APIC-edge  ide0
>  15:      48907      47090    IO-APIC-edge  ide1
> NMI:          0          0
> LOC:    1961162    1961161
> ERR:          0
> MIS:          0
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: Fw: DriveReady SeekComplete problems

[Artur Jasowicz]

From: Diamon 
> 
>     Unless those aren't ATA-100 cables and it's still using ATA-100 mode...
> I think ATA-66 or higher you need those 80-wire cables...  Just a thought.
> And the solid-core 80 pin cables don't handle folding well at all, maybe
> something's gone flaky in them?
> 
True, although all ATA-66 + devices I've seen detected 40 wire cables and refused to work at high speed. But there might be an exception to that. That's no the case here though. They're all 80 pin, installed correctly - master drive connector on master drive, controller connector on controller end. The only possible part of your theory in my case may be problems with bending. I kept the cables fairly flat and straight, but they came tightly folded in the box.

The more I think about it the more it seems like the system not keeping up with the drives though. Isn't it strange that both my 2000+ Athlons MP run at < 2% idle when syncing array? Even in PIO mode, at 500K resync speed reported by /proc/mdstat. And nothing else runs on the machine, Just three consoles, raidrun on one, top on the other and occasional tail /var/log/messages on third to monitor log for error msgs.

When I let the drives supply data faster by enabling DMA (100 by default, but I've tried switching to 33 with same results), i start getting errors at 2000K resync speed. In slower PIO ar 500K resync things work ok with 4 drives, but 5 is too much - errors.

Artur

Re: Fw: DriveReady SeekComplete problems

[Danilo Godec]

On Fri, 10 May 2002, Artur Jasowicz wrote:

> The more I think about it the more it seems like the system not
> keeping up with the drives though. Isn't it strange that both my 2000+

It's a wild guess, but you might want to try disabling one of the
processors using 'nosmp' kernel parameter. Maybe Athlons have some issues
with SMP configuration.

Next would be testing a single drive. If the problem exists using a single
drive, you should try some other controller (I never used a HPT, but a
friend of mine has a problem with it - dunno what exactly though).

OR, having three IDE controllers sharing one IRQ just might be a problem.
I remember that on my SMP motherboards I had a lot more available IRQs
(over 25), available through APIC (whatever that is).

   D.

Re: Fw: DriveReady SeekComplete problems

[Alvin Oga]

hi ya artur

On Sat, 11 May 2002, Danilo Godec wrote:

> On Fri, 10 May 2002, Artur Jasowicz wrote:
> 
> > The more I think about it the more it seems like the system not
> > keeping up with the drives though. Isn't it strange that both my 2000+

make sure that all your disks on the same ide cable is of the same
speed...  and its options defined similarly...
	ata33 on one cable...
	ata66 on a 80-pin ide cable - no other disk speeds
	ata100 on a different ide cable
	ata133 on a different ide cable..
	-- do NOT mix drives of different ata speeds..

	hdparam -iv /dev/hdxx  will tell you what speed it is

make sure that your cables are good/clean and not bent out of shape..

http://www.linux-1u.net/Disks

c ya
alvin

> It's a wild guess, but you might want to try disabling one of the
> processors using 'nosmp' kernel parameter. Maybe Athlons have some issues
> with SMP configuration.
> 
> Next would be testing a single drive. If the problem exists using a single
> drive, you should try some other controller (I never used a HPT, but a
> friend of mine has a problem with it - dunno what exactly though).
> 
> OR, having three IDE controllers sharing one IRQ just might be a problem.
> I remember that on my SMP motherboards I had a lot more available IRQs
> (over 25), available through APIC (whatever that is).
> 

Re: Fw: DriveReady SeekComplete problems

[Mikael Abrahamsson]

On Thu, 9 May 2002, Artur Jasowicz wrote:

> I am building a file server with 5 drive software RAID5 array. I am
> using three IWill SIDE-100 (Highpoint 370A) controllers as my IDE
> interfaces, not using their RAID functionality. One Maxtor 160GB drive
> per channel, two channels per controller. I plan on adding hot spare as
> the sixth drive in the future. There's one 160GB partition on each
> drive. Linux version 2.4.19-pre7smp-020502b (root@production) (gcc
> version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #6 SMP Thu May 2
> 12:15:34 CDT 2002 This is a dual Athlon 2000+ MP on Tyan Tiger S2466N-4
> with 1GB RAM. OS and swap runs on separate drives and controllers. This
> array will be just for data once it is configured.

I get the exact same errors you get with my VP-6 SMP board when using its 
onboard HPT370 controller.

cat /proc/interrupts 
           CPU0       CPU1       
  0:    6197040    6197246    IO-APIC-edge  timer
  1:        440        380    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  8:          0          1    IO-APIC-edge  rtc
 14:      63320      61241    IO-APIC-edge  ide0
 15:    3548204    3537369    IO-APIC-edge  ide1
 16:     429475     430742   IO-APIC-level  aic7xxx
 18:    4602335    4601175   IO-APIC-level  ide2, ide3, aic7xxx
 19:   30045123   30046213   IO-APIC-level  eth0

My theory is that it's the interrupt sharing that is causing some of the 
problems, or some kind of DMA channel mixup. I have no problem with any of 
the other drives connected to the primary IDE controller (ide0 and ide1).

Anyone know if I can force the kernel to not share interrupts.

I am using the Red Hat supplied 2.4.18 kernel that comes with redhat 7.3. 
When I used the 2.4.9-31 kernel with redhat 7.2 before I got no errors but 
instead data corruption on the ide2 and ide3 drives (which are two 120 gig 
maxtors in a raid0 config). This could be due to a faulty cable though, I 
swapped that one too.

Currently I have stability problems with the box, if I use the ide2 and 
ide3 drives a lot the machine freezes.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

Re: Fw: DriveReady SeekComplete problems

[Artur Jasowicz]

> Anyone know if I can force the kernel to not share interrupts.
I think that Highpoint chip only uses one IRQ for both channels, but it
might be helpfull to move your SCSI card's IRQ to another slot.

> Currently I have stability problems with the box, if I use the ide2 and
> ide3 drives a lot the machine freezes.
If your DMA is on on the Highpoint drives, this might cause lockups. That's
what I was getting with another machine I have. It is a M571 mobo (Chinese
cheapo generic crap) with two IWills driving four 80 GB Maxtors in RAID 5.
As long as DMA was on, I couldn't complete syncing array after configuring
it. Contstant lockups. After I did hdparm -d 0 /dev/hd[e,g,i,k] the arrays
synced and seem to be working correctly now. I need to develop a way of
checking for data corruption. Of course the price is the speed. With DMA on
I was getting 2000K/s syncing speed. without DMA - 800K. I am running plain
RH 7.2 on this machine. It may be worth trying hdparm -X to set drives to a
slower DMA, although this is just a patch, not a solution. Before trying to
use this configuration I had a single IWill with two Maxtors in RAID1.
Worked without a glitch. I wish I remembered if the controlled had it's own
IRQ. Although I doubt it. I was running RH 7.1 back then.

Is your CPU usage also close to 100% when using RAID?

Artur

Re: Fw: DriveReady SeekComplete problems

[Mikael Abrahamsson]

On Sun, 12 May 2002, Artur Jasowicz wrote:

> > Anyone know if I can force the kernel to not share interrupts.
> I think that Highpoint chip only uses one IRQ for both channels, but it
>
> might be helpfull to move your SCSI card's IRQ to another slot.

How?

> Is your CPU usage also close to 100% when using RAID?

Nope, I barely have any CPU usage at all. If you turn off DMA though, I am 
not surprised you have high CPU usage problems.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

Re: Fw: DriveReady SeekComplete problems

[Danilo Godec]

On Sun, 12 May 2002, Artur Jasowicz wrote:

> As long as DMA was on, I couldn't complete syncing array after configuring
> it. Contstant lockups. After I did hdparm -d 0 /dev/hd[e,g,i,k] the arrays
> synced and seem to be working correctly now. I need to develop a way of
> checking for data corruption. Of course the price is the speed. With DMA on
> I was getting 2000K/s syncing speed. without DMA - 800K. I am running plain

I'm used to sync speeds above 20000K/s these days. With DMA, of course.

> Is your CPU usage also close to 100% when using RAID?

Nope, not even close. But having the DMA turned off is certanly a way to
put a lot of load on your CPU(s).

It seems that either the HPTs have a design flaw or the driver is not
fully supporting them.


  D.

Re: Fw: DriveReady SeekComplete problems

[Artur Jasowicz]

Andre,
I've been away from the office for a few days. I am getting back to you
with results after applying the patch.

The patch applied cleanly, but did not fix the problem. I am still getting
bad DMA status (dma_stat=1) and status=0x50 { DriveReady SeekComplete }
messages with DMA on.

I've done further tests and observed following:

-creating RAID1 array of 5 drives does not produce errors
-creating RAID5 array causes errors
-doing dd if=/dev/hdx of=/dev/null bs=512 with x=one of the drives in array
 works fine as long as the drives are on the same controller. I've tried
this
 with up to 10 dd commands, 5/drive 2 drives on same controller
-the above command causes errors when used with drives on diferent
 controllers. i.e. if I start dd on hde - works fine, then I execute dd on
hdi
 and see errors

Creating RAID1 is mostly writing to drives, while doing dd and creating
RAID5 involves intense reading from drives. This de me think that the
system can't keep up with reading flood of data comming from the drives.

I've tried limiting speed of resyncing array by doing
#echo 1000 > /proc/sys/dev/raid/speed_limit_max
This slowed down pace at which error messages appeared in logs, but
did not eliminate them. I've tried diferent values instead of 1000,
the higher, the worse things were.

What else can I try?

Artur

From: Andre Hedrick <andre@linux-ide.org>
>
> Please try the latest driver changes on www.linuxdiskcert.org
>
> If it still presists let me know, again!
>
> Cheers,
>
> On Mon, 13 May 2002, Artur Jasowicz wrote:
>
> > ----- Original Message -----
> > From: Artur Jasowicz <arturj@mousebusiness.com>
> > To: <linux-kernel@vger.kernel.org>
> > Sent: Wednesday, May 08, 2002 12:34 PM
> > Subject: DriveReady SeekComplete problems
> >
> >
> > > I am building a file server with 5 drive software RAID5 array. I am
using
> > three IWill SIDE-100 (Highpoint 370A) controllers as my IDE interfaces,
not
> > using their RAID functionality. One Maxtor 160GB drive per channel, two
> > channels per controller. I plan on adding hot spare as the sixth drive
in
> > the future. There's one 160GB partition on each drive. Linux version
> > 2.4.19-pre7smp-020502b (root@production) (gcc version 2.96 20000731 (Red
Hat
> > Linux 7.1 2.96-98)) #6 SMP Thu May 2 12:15:34 CDT 2002
> > > This is a dual Athlon 2000+ MP on Tyan Tiger S2466N-4 with 1GB RAM. OS
and
> > swap runs on separate drives and controllers. This array will be just
for
> > data once it is configured.
> > >
[snip lengthy description of error messages]