Re: SCSI bus resets w/Linux 2.4.x and Mylex DAC960 RAID

Ulrich.Teichert_at_gmx.de
Date: 07/04/05


Date: Mon, 4 Jul 2005 18:59:47 GMT

In <1120418137.424054.278310@g43g2000cwa.googlegroups.com> thatseattleguy@hotmail.com writes:

>A client has a 3-disk SCSI RAID array attached to an old Mylex DAC960
>controller. About six months ago, they lost one of the disks, which was
>fine, except there was no alarm and they didn't notice... Last
>Wednesday at 9:03AM, they lost a second disk - and believe me, *that*
>got their attention. :}

>They replaced the two failed drives (older 10K IBM models) with newer
>Seagates in the same drive caddies, leaving the remaining working IBM
>drive in place (don't ask...). All drives are 18GB SCSI. After the
>array was rebuild and yours truly resurrected things from backup tapes,
>we noticed that the system was slow and there were huge "gaps" in
>activity where for 5-8 seconds seemingly nothing was getting processed
>and no disk activity was happening. Long story short we found that the
>SCSI bus was undergoing a full reset every minute or so (see dump
>below).

That's not a dump of a SCSI bus reset. This would reveal what drive caused
the reset (reset on behalf of....).

>So here's the question: assuming termination and cables are all fine
>(as the old drive caddies were reused in their same positions, and they
>look OK), could the fact that we've got two different types of drives
>in the same array be causing the resets? I've heard tale tell the
>DAC960 is pretty finicky about the types of drives it likes to talk
>to. And I've never tried to do hardware RAID with dissimilar drives (of
>different generations, no less) before.

Well, all hardware RAID controlers are picky about drive FW and drives
of different types. It would be interesting to see what really collided
in the log.

[del]
> Logical Drives:
> /dev/rd/c0d0: RAID-5, Online, 35844096 blocks, Write Thru
> /dev/rd/c0d1: RAID-5, Online, 35840000 blocks, Write Thru

2 RAID 5's? On 3 drives? Are you sure that's right?

HTH,
Uli

-- 
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Suicide Drive (The Deep Eynde)
24539 Neumuenster, Germany|Public Pervert (Interpol) Cauchemar (Opération S)


Relevant Pages

  • Re: 6.2 not compatible with new sata drives ?!
    ... Some combinations of controller and drive do not play well ... I assume that the new failing disks are ... If your controller works well with your Samsung drives, ... Decided to try my origonal 6.2amd64 iso again, ...
    (freebsd-questions)
  • Re: A8N SLI Deluxe Question
    ... >> Currently the drives are partitioned and my apps are on one partition. ... Someone suggested using RAID 0. ... > The media rates for disks are still in the ~70MB/sec range ... > controller card, into one of the video card slots on an SLI ...
    (alt.comp.periphs.mainboard.asus)
  • SA3200 Disk array controller in PC (was: 5300 Disk array controller in PC)
    ... > during the power-up of the PC and the card on its turn sees the disks. ... the physical drives to a logical array. ... First, you have to go into the controllers BIOS setup (ACU, Array ... Windows requires drivers for the controller. ...
    (comp.sys.hp.hardware)
  • Re: Virus corrupted MBR - how to reset
    ... no disks found; F3 Exit. ... This might happen if your system has SATA drives and a controller that is ... Save, reboot, and the drives should be seen. ... How do I get around this to fix the MBR? ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: CD writing in future Linux (stirring up a hornets nest)
    ... "dual standard" controller firmware. ... SAS is actually a lot more complex than SATA. ... I still don't see why drives are expected to be more reliable than ... I think the most paranoid setup I've seen was six disks holding two disks ...
    (Linux-Kernel)