All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Nettingsmeier" <nettings@stackingdwarves.net>
To: adam radford <aradford@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: 3ware 9690SA: raid6 array blows up under opensuse 11.2 (2.6.31)
Date: Sun, 13 Dec 2009 23:24:13 +0100	[thread overview]
Message-ID: <4B25698D.5030202@stackingdwarves.net> (raw)
In-Reply-To: <b1bc6a000912131238y2539a1ccrdd008b79876164da@mail.gmail.com>

hi adam!


thanks for your reply!

adam radford wrote:
> 2009/12/13 Jörn Nettingsmeier <nettings@stackingdwarves.net>:
>> do you know of any known regressions in the 3ware driver or userspace
>> utilities since 2.6.27 (because that was the latest kernel that passed
>> the tests) that could be causing this issue?
>>
> 
> The 3ware driver and userspace utilities do make the decision of whether

i guess that should read "do *not*" ?

> disks get kicked out of the array, the 3ware firmware does.  Make sure
> you are running the 9.5.3 (latest) firmware.

i will check this first thing tomorrow and report back.
(the vendor assured me that the firmware was at the latest version, but
i didn't have a chance to check it myself.)

>> here are some screenshots of the dmesg buffer and the controller bios
>> during the error condition:
>>
>> http://stackingdwarves.net/download/3ware-9690SE-crash/
>>
> 
> I believe you have bad hardware, or a drive cabling issue. 

as i said before, this issue has occurred with two identical controller
cards, and the vendor claims to also have swapped backplane and cabling.
i'll try and get their technician on the phone tomorrow to confirm that.

> I will
> forward this email
> to 3ware support.  They should be able to tell you if you have a known flakey
> drive firmware rev, enclosure, etc.

great, i appreciate your interest and support in this issue!

i'll try and fend off my client for another few days (who is kind of
eager to get the system up and running), but i do want to get this thing
sorted out - i had always been using 3ware gear on linux with great
success...
after spending more than 18 work hours just waiting for the array to
initialize, fall apart, start over, this is getting personal :-D



-- 
Jörn Nettingsmeier
Lortzingstr. 11, 45128 Essen, Tel. +49 177 7937487

Meister für Veranstaltungstechnik (Bühne/Studio), Elektrofachkraft
Audio and event engineer - Ambisonic surround recordings

http://stackingdwarves.net

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-12-13 22:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13 15:08 3ware 9690SA: raid6 array blows up under opensuse 11.2 (2.6.31) Jörn Nettingsmeier
2009-12-13 20:38 ` adam radford
2009-12-13 22:24   ` Jörn Nettingsmeier [this message]
2009-12-14  0:45     ` adam radford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B25698D.5030202@stackingdwarves.net \
    --to=nettings@stackingdwarves.net \
    --cc=aradford@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.