RE: 3ware driver errors

RE: 3ware driver errors

[Adam Radford]

This is fixed in driver 1.02.00.032, the scsi layer is looping on sense key
'aborted command' after you lost power to a jbod drive, and not checking the
ASC 
which is 0x04 (Logical Unit Not Ready).  If you want to fix it by hand in
your
driver before .032 comes out, in 3w-xxxx.h, change:

{0x37, 0x0b, 0x04, 0x00},

to:

{0x37, 0x02, 0x04, 0x00}

This will return sense key 'Not Ready', and you will will not infinitely
loop.
If I were you, I would jiggle the power cables on that box and replace flaky
ones.

-Adam

-----Original Message-----
From: Steven Pritchard [mailto:steve@silug.org]
Sent: Monday, March 24, 2003 1:28 PM
To: linux-kernel@vger.kernel.org
Subject: 3ware driver errors


(Apparently 3w-xxxx in the Subject gets caught as spam.  Somebody
might want to adjust that regular expression.  :-)

I have a server that is locking up every day or two with a console
full of this error:

    3w-xxxx: scsi0: Command failed: status = 0xcb, flags = 0x37, unit #0.

This is on a Dell PowerEdge 1400SC (dual PIII/1.13GHz, 1.1GB RAM),
with a 3ware Escalade 7000-2 and two WD1600JB drives, running Red Hat
8.0 with kernel-smp 2.4.18-27.8.0.

I plan to report this to Red Hat's bugzilla, but I'm hoping for some
ideas or big red flags to jump out at somebody here...  I use this box
for a UML hosting server, so all this downtime is affecting *way* too
many people.

This box has been having other stability problems, so I'm guessing
this might not be directly related to the 3ware card/driver.  It did
survive a memtest86 pass.

Steve
-- 
steve@silug.org           | Southern Illinois Linux Users Group
(618)398-7360             | See web site for meeting details.
Steven Pritchard          | http://www.silug.org/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 3ware driver errors

[Jeff V. Merkey]

Adam,

They also need to upgrade the firmware on the WD drives.  There's a known problem with WD drives and 3Ware.  

Jeff

On Mon, Mar 24, 2003 at 01:44:23PM -0800, Adam Radford wrote:
> This is fixed in driver 1.02.00.032, the scsi layer is looping on sense key
> 'aborted command' after you lost power to a jbod drive, and not checking the
> ASC 
> which is 0x04 (Logical Unit Not Ready).  If you want to fix it by hand in
> your
> driver before .032 comes out, in 3w-xxxx.h, change:
> 
> {0x37, 0x0b, 0x04, 0x00},
> 
> to:
> 
> {0x37, 0x02, 0x04, 0x00}
> 
> This will return sense key 'Not Ready', and you will will not infinitely
> loop.
> If I were you, I would jiggle the power cables on that box and replace flaky
> ones.
> 
> -Adam
> 
> -----Original Message-----
> From: Steven Pritchard [mailto:steve@silug.org]
> Sent: Monday, March 24, 2003 1:28 PM
> To: linux-kernel@vger.kernel.org
> Subject: 3ware driver errors
> 
> 
> (Apparently 3w-xxxx in the Subject gets caught as spam.  Somebody
> might want to adjust that regular expression.  :-)
> 
> I have a server that is locking up every day or two with a console
> full of this error:
> 
>     3w-xxxx: scsi0: Command failed: status = 0xcb, flags = 0x37, unit #0.
> 
> This is on a Dell PowerEdge 1400SC (dual PIII/1.13GHz, 1.1GB RAM),
> with a 3ware Escalade 7000-2 and two WD1600JB drives, running Red Hat
> 8.0 with kernel-smp 2.4.18-27.8.0.
> 
> I plan to report this to Red Hat's bugzilla, but I'm hoping for some
> ideas or big red flags to jump out at somebody here...  I use this box
> for a UML hosting server, so all this downtime is affecting *way* too
> many people.
> 
> This box has been having other stability problems, so I'm guessing
> this might not be directly related to the 3ware card/driver.  It did
> survive a memtest86 pass.
> 
> Steve
> -- 
> steve@silug.org           | Southern Illinois Linux Users Group
> (618)398-7360             | See web site for meeting details.
> Steven Pritchard          | http://www.silug.org/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 3ware driver errors

[Ezra Nugroho]

yeah, but that's IBM drives, We were talking about the WDC -JB/BB.

I would be interested to listen to other WDJ sub 180G users who have the
same problem.
Anyone?



On Tue, 2003-03-25 at 10:26, Roy Sigurd Karlsbakk wrote:
> I'm running 2x8-port 3ware with 8 IBM 120gig disks on each controller in raid 
> 5. this has been running stably for half a year (that is - since I installed 
> it).
> 
> On Tuesday 25 March 2003 16:25, Ezra Nugroho wrote:
> > I have 8 120GB in a raid 5.
> > Although the site doesn't say that the 120s are affected, I have gotten
> > my raid to be degraded because one drive disappeared.
> > I got the same error message.
> >
> > I am not sure if I want to upgrade the firmware, however, I am not sure
> > my array is stable either...
> >
> > On Mon, 2003-03-24 at 22:12, Steven Pritchard wrote:
> > > On Mon, Mar 24, 2003 at 06:25:08PM -0700, Jeff V. Merkey wrote:
> > > > The person at WD to contact with specifics is listed below.
> > >
> > > Thanks for the pointer.  I have a lot of these WD drives...
> > >
> > > > We have seen it on the 180GB drives, but the 200GB are also affected.
> > >
> > > I don't suppose you've heard if the 160GB drives are affected, have
> > > you?  The page on support.wdc.com that someone else referred to
> > > specifically mentions the 200s and the 180s, but I see no mention of
> > > the 160s.
> > >
> > > Steve
> > > --
> > > steve@silug.org           | Southern Illinois Linux Users Group
> > > (618)398-7360             | See web site for meeting details.
> > > Steven Pritchard          | http://www.silug.org/
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> > > in the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > > Please read the FAQ at  http://www.tux.org/lkml/
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> 
> -- 
> Roy Sigurd Karlsbakk, Datavaktmester
> ProntoTV AS - http://www.pronto.tv/
> Tel: +47 9801 3356
> 
> Computers are like air conditioners.
> They stop working when you open Windows.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 3ware driver errors

[Roy Sigurd Karlsbakk]

I'm running 2x8-port 3ware with 8 IBM 120gig disks on each controller in raid 
5. this has been running stably for half a year (that is - since I installed 
it).

On Tuesday 25 March 2003 16:25, Ezra Nugroho wrote:
> I have 8 120GB in a raid 5.
> Although the site doesn't say that the 120s are affected, I have gotten
> my raid to be degraded because one drive disappeared.
> I got the same error message.
>
> I am not sure if I want to upgrade the firmware, however, I am not sure
> my array is stable either...
>
> On Mon, 2003-03-24 at 22:12, Steven Pritchard wrote:
> > On Mon, Mar 24, 2003 at 06:25:08PM -0700, Jeff V. Merkey wrote:
> > > The person at WD to contact with specifics is listed below.
> >
> > Thanks for the pointer.  I have a lot of these WD drives...
> >
> > > We have seen it on the 180GB drives, but the 200GB are also affected.
> >
> > I don't suppose you've heard if the 160GB drives are affected, have
> > you?  The page on support.wdc.com that someone else referred to
> > specifically mentions the 200s and the 180s, but I see no mention of
> > the 160s.
> >
> > Steve
> > --
> > steve@silug.org           | Southern Illinois Linux Users Group
> > (618)398-7360             | See web site for meeting details.
> > Steven Pritchard          | http://www.silug.org/
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Roy Sigurd Karlsbakk, Datavaktmester
ProntoTV AS - http://www.pronto.tv/
Tel: +47 9801 3356

Computers are like air conditioners.
They stop working when you open Windows.

Re: 3ware driver errors

[Ezra Nugroho]

I have 8 120GB in a raid 5.
Although the site doesn't say that the 120s are affected, I have gotten
my raid to be degraded because one drive disappeared.
I got the same error message.

I am not sure if I want to upgrade the firmware, however, I am not sure
my array is stable either...

On Mon, 2003-03-24 at 22:12, Steven Pritchard wrote:
> On Mon, Mar 24, 2003 at 06:25:08PM -0700, Jeff V. Merkey wrote:
> > The person at WD to contact with specifics is listed below.
> 
> Thanks for the pointer.  I have a lot of these WD drives...
> 
> > We have seen it on the 180GB drives, but the 200GB are also affected.
> 
> I don't suppose you've heard if the 160GB drives are affected, have
> you?  The page on support.wdc.com that someone else referred to
> specifically mentions the 200s and the 180s, but I see no mention of
> the 160s.
> 
> Steve
> -- 
> steve@silug.org           | Southern Illinois Linux Users Group
> (618)398-7360             | See web site for meeting details.
> Steven Pritchard          | http://www.silug.org/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 3ware driver errors

[Steven Pritchard]

On Mon, Mar 24, 2003 at 06:25:08PM -0700, Jeff V. Merkey wrote:
> The person at WD to contact with specifics is listed below.

Thanks for the pointer.  I have a lot of these WD drives...

> We have seen it on the 180GB drives, but the 200GB are also affected.

I don't suppose you've heard if the 160GB drives are affected, have
you?  The page on support.wdc.com that someone else referred to
specifically mentions the 200s and the 180s, but I see no mention of
the 160s.

Steve
-- 
steve@silug.org           | Southern Illinois Linux Users Group
(618)398-7360             | See web site for meeting details.
Steven Pritchard          | http://www.silug.org/

Re: 3ware driver errors

[Kevin P. Fleming]

Steven Pritchard wrote:
> I don't suppose you've heard if the 160GB drives are affected, have
> you?  The page on support.wdc.com that someone else referred to
> specifically mentions the 200s and the 180s, but I see no mention of
> the 160s.
> 

I'd like to know this too; I've got a pair of WD1600JB drives (less than 
two weeks old) attached to a 3Ware 7000-2. They've been working fine so 
far, but I'm not keen on finding a problem later...

Re: 3ware driver errors

[Jeff V. Merkey]

The person at WD to contact with specifics is listed below.  We have seen it 
on the 180GB drives, but the 200GB are also affected.

Suresh.Chekuri@wdc.com

Jeff

On Mon, Mar 24, 2003 at 03:44:10PM -0800, Larry McVoy wrote:
> On Mon, Mar 24, 2003 at 06:01:07PM -0700, Jeff V. Merkey wrote:
> > There is a firmware upgrade you need to obtain from WD if you are using their 
> > drives with a 3Ware controller.  The WD drives were optimized for desktop use
> > and they go into a "powersave" mode of sorts which will cause them to disappear
> > and reappear mysteriously with all sorts of strange errors.  WD is aware of 
> > this problem and so is 3Ware.
> 
> Is this for all WD drives or just some?  I've got some wd400 drives that 
> I've been using for a long time behind a 3ware in jbod mode.  I have seen
> some errors but they seem to have settled down.  Is there any way to know?
> -- 
> ---
> Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

Re: 3ware driver errors

[Jeff V. Merkey]

There is a firmware upgrade you need to obtain from WD if you are using their 
drives with a 3Ware controller.  The WD drives were optimized for desktop use
and they go into a "powersave" mode of sorts which will cause them to disappear
and reappear mysteriously with all sorts of strange errors.  WD is aware of 
this problem and so is 3Ware.

Jeff

On Mon, Mar 24, 2003 at 03:28:13PM -0600, Steven Pritchard wrote:
> (Apparently 3w-xxxx in the Subject gets caught as spam.  Somebody
> might want to adjust that regular expression.  :-)
> 
> I have a server that is locking up every day or two with a console
> full of this error:
> 
>     3w-xxxx: scsi0: Command failed: status = 0xcb, flags = 0x37, unit #0.
> 
> This is on a Dell PowerEdge 1400SC (dual PIII/1.13GHz, 1.1GB RAM),
> with a 3ware Escalade 7000-2 and two WD1600JB drives, running Red Hat
> 8.0 with kernel-smp 2.4.18-27.8.0.
> 
> I plan to report this to Red Hat's bugzilla, but I'm hoping for some
> ideas or big red flags to jump out at somebody here...  I use this box
> for a UML hosting server, so all this downtime is affecting *way* too
> many people.
> 
> This box has been having other stability problems, so I'm guessing
> this might not be directly related to the 3ware card/driver.  It did
> survive a memtest86 pass.
> 
> Steve
> -- 
> steve@silug.org           | Southern Illinois Linux Users Group
> (618)398-7360             | See web site for meeting details.
> Steven Pritchard          | http://www.silug.org/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: 3ware driver errors

[Mark Hahn]

> > and reappear mysteriously with all sorts of strange errors.  WD is aware of 
> > this problem and so is 3Ware.
> 
> Is this for all WD drives or just some?  I've got some wd400 drives that 
> I've been using for a long time behind a 3ware in jbod mode.  I have seen
> some errors but they seem to have settled down.  Is there any way to know?

I haven't seen the problem myself, but:
http://support.wdc.com/download/index.asp#raid3ware

Re: 3ware driver errors

[Larry McVoy]

On Mon, Mar 24, 2003 at 06:01:07PM -0700, Jeff V. Merkey wrote:
> There is a firmware upgrade you need to obtain from WD if you are using their 
> drives with a 3Ware controller.  The WD drives were optimized for desktop use
> and they go into a "powersave" mode of sorts which will cause them to disappear
> and reappear mysteriously with all sorts of strange errors.  WD is aware of 
> this problem and so is 3Ware.

Is this for all WD drives or just some?  I've got some wd400 drives that 
I've been using for a long time behind a 3ware in jbod mode.  I have seen
some errors but they seem to have settled down.  Is there any way to know?
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

3ware driver errors

[Steven Pritchard]

(Apparently 3w-xxxx in the Subject gets caught as spam.  Somebody
might want to adjust that regular expression.  :-)

I have a server that is locking up every day or two with a console
full of this error:

    3w-xxxx: scsi0: Command failed: status = 0xcb, flags = 0x37, unit #0.

This is on a Dell PowerEdge 1400SC (dual PIII/1.13GHz, 1.1GB RAM),
with a 3ware Escalade 7000-2 and two WD1600JB drives, running Red Hat
8.0 with kernel-smp 2.4.18-27.8.0.

I plan to report this to Red Hat's bugzilla, but I'm hoping for some
ideas or big red flags to jump out at somebody here...  I use this box
for a UML hosting server, so all this downtime is affecting *way* too
many people.

This box has been having other stability problems, so I'm guessing
this might not be directly related to the 3ware card/driver.  It did
survive a memtest86 pass.

Steve
-- 
steve@silug.org           | Southern Illinois Linux Users Group
(618)398-7360             | See web site for meeting details.
Steven Pritchard          | http://www.silug.org/