[prev in list] [next in list] [prev in thread] [next in thread]
List: linux-poweredge
Subject: RE: Sporadic drive problems on PE1950
From: <Nico_Terrey () dell ! com>
Date: 2007-05-29 14:59:46
Message-ID: E43F00B9547D224380BFBD79EE9FB288295212 () lejx3m3 ! lej ! emea ! dell ! com
[Download RAW message or body]
--===============1783340528==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C7A201.FF31C4AC"
This is a multi-part message in MIME format.
Hi Randy,
please check the model number of your harddrives and take a look at the
dell support website.
There are many FW updates available for SAS harddrives which will fix
timeout issues. Just search
for the model number on the dell website.
Sorry for my english.
Thanks,
Nico
________________________________
From: linux-poweredge-bounces@dell.com
[mailto:linux-poweredge-bounces@dell.com] On Behalf Of
Shyam_Iyer@dell.com
Sent: Dienstag, 29. Mai 2007 16:29
To: wolf@clemson.edu; linux-poweredge-Lists
Subject: RE: Sporadic drive problems on PE1950
Hi Randy,
OS version : ?
What Card are you using ?
Which PowerEdge Server ?
Are you using dkms packaged mptlinux drivers from support.dell.com
or the native drivers of the OS?
Thanks,
Shyam
________________________________
From: linux-poweredge-bounces@dell.com
[mailto:linux-poweredge-bounces@dell.com] On Behalf Of Randy Martin
Sent: Tuesday, May 29, 2007 6:13 PM
To: linux-poweredge-Lists
Subject: Sporadic drive problems on PE1950
I keep getting the following errors sporadically on different compute
nodes. I end up having to power cycle the nodes to recover. Any ideas
on how to fix this? I have applied the latest BIOS update and patches
FRMW_LX_R149666.BIN/FRMW_LX_R149730.BIN, but I still see the problems
occasionally.
Thanks,
Randy
May 22 20:03:24 compute-2-14.local syslogd: /var/log/kern: Read-only
file system
May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0: attempting
task abort! (sc=00000102011271c0)
May 22 20:03:24 compute-2-14.local kernel: scsi0 : destination target 0,
lun 0
May 22 20:03:24 compute-2-14.local kernel: command = Write (10)
00 00 91 19 2d 00 00 08 00
May 22 20:03:24 compute-2-14.local kernel: mptbase: ioc0:
LogInfo(0x31140000): Originator={PL}, Code={IO Executed},
SubCode(0x0000)
May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0: removing sata
device, channel 0, id 0, phy 0
May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0: task abort:
SUCCESS (sc=00000102011271c0)
May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0: attempting
bus reset! (sc=00000102011271c0)
May 22 20:03:24 compute-2-14.local kernel: scsi0 : destination target 0,
lun 0
May 22 20:03:24 compute-2-14.local kernel: command = Write (10)
00 00 91 19 2d 00 00 08 00
May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0: bus reset:
SUCCESS (sc=00000102011271c0)
May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0: Attempting
host reset! (sc=00000102011271c0)
May 22 20:03:24 compute-2-14.local kernel: mptbase: Initiating ioc0
recovery
May 22 20:03:24 compute-2-14.local kernel: scsi: Device offlined - not
ready after error recovery: host 0 channel 0 id 0 lun 0
May 22 20:03:24 compute-2-14.local kernel: sd 0:0:0:0: Illegal state
transition cancel->offline
May 22 20:03:24 compute-2-14.local kernel: Badness in
scsi_device_set_state at drivers/scsi/scsi_lib.c:1700
May 22 20:03:24 compute-2-14.local kernel:
May 22 20:03:24 compute-2-14.local kernel: Call
Trace:<ffffffffa000802e>{:scsi_mod:scsi_device_set_state+241}
May 22 20:03:24 compute-2-14.local kernel:
<ffffffffa00063d5>{:scsi_mod:scsi_error_handler+2567}
May 22 20:03:24 compute-2-14.local kernel:
<ffffffff80110e17>{child_rip+8}
<ffffffffa00059ce>{:scsi_mod:scsi_error_handler+0}
May 22 20:03:24 compute-2-14.local kernel:
<ffffffff80110e0f>{child_rip+0}
May 22 20:03:24 compute-2-14.local kernel: scsi: Device offlined - not
ready after error recovery: host 0 channel 0 id 0 lun 0
May 22 20:03:24 compute-2-14.local kernel: sd 0:0:0:0: Illegal state
transition cancel->offline
May 22 20:03:24 compute-2-14.local kernel: Badness in
scsi_device_set_state at drivers/scsi/scsi_lib.c:1700
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3086" name=GENERATOR>
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-compose
}
.MsoChpDefault {
mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=925215714-29052007><FONT face=Arial
color=#0000ff size=2>Hi Randy,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925215714-29052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=925215714-29052007><FONT face=Arial
color=#0000ff size=2>please check the model number of your harddrives and take a
look at the dell support website.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925215714-29052007><FONT face=Arial
color=#0000ff size=2>There are many FW updates available for SAS harddrives
which will fix timeout issues. Just search</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925215714-29052007><FONT face=Arial
color=#0000ff size=2>for the model number on the dell
website.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925215714-29052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=925215714-29052007><FONT face=Arial
color=#0000ff size=2>Sorry for my english.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925215714-29052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=925215714-29052007><FONT face=Arial
color=#0000ff size=2>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=925215714-29052007><FONT face=Arial
color=#0000ff size=2>Nico</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> linux-poweredge-bounces@dell.com
[mailto:linux-poweredge-bounces@dell.com] <B>On Behalf Of
</B>Shyam_Iyer@dell.com<BR><B>Sent:</B> Dienstag, 29. Mai 2007
16:29<BR><B>To:</B> wolf@clemson.edu; linux-poweredge-Lists<BR><B>Subject:</B>
RE: Sporadic drive problems on PE1950<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=718325712-29052007><FONT face=Arial
color=#0000ff size=2>Hi Randy,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=718325712-29052007> <FONT
face=Arial color=#0000ff size=2>OS version : ?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=718325712-29052007> <FONT
face=Arial color=#0000ff size=2>What Card are you using ?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN
class=718325712-29052007> <FONT face=Arial><FONT
color=#0000ff size=2>Which PowerEdge Server ?</FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN
class=718325712-29052007> <FONT face=Arial color=#0000ff
size=2>Are you using dkms packaged mptlinux drivers from support.dell.com
or the native drivers of the OS?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=718325712-29052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=718325712-29052007><FONT face=Arial
color=#0000ff size=2>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=718325712-29052007><FONT face=Arial
color=#0000ff size=2>Shyam</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> linux-poweredge-bounces@dell.com
[mailto:linux-poweredge-bounces@dell.com] <B>On Behalf Of </B>Randy
Martin<BR><B>Sent:</B> Tuesday, May 29, 2007 6:13 PM<BR><B>To:</B>
linux-poweredge-Lists<BR><B>Subject:</B> Sporadic drive problems on
PE1950<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal>I keep getting the following errors sporadically on different
compute nodes. I end up having to power cycle the nodes to recover.
Any ideas on how to fix this? I have applied the latest BIOS update and
patches FRMW_LX_R149666.BIN/FRMW_LX_R149730.BIN, but I still see the problems
occasionally.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Thanks,<o:p></o:p></P>
<P class=MsoNormal>Randy<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local syslogd: /var/log/kern:
Read-only file system <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0:
attempting task abort! (sc=00000102011271c0) <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: scsi0 :
destination target 0, lun 0 <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local
kernel: command = Write (10) 00
00 91 19 2d 00 00 08 00 <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: mptbase: ioc0:
LogInfo(0x31140000): Originator={PL}, Code={IO Executed}, SubCode(0x0000)
<o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0:
removing sata device, channel 0, id 0, phy 0 <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0:
task abort: SUCCESS (sc=00000102011271c0) <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0:
attempting bus reset! (sc=00000102011271c0) <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: scsi0 :
destination target 0, lun 0 <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local
kernel: command = Write (10) 00
00 91 19 2d 00 00 08 00 <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0:
bus reset: SUCCESS (sc=00000102011271c0) <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: mptscsih: ioc0:
Attempting host reset! (sc=00000102011271c0) <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: mptbase:
Initiating ioc0 recovery <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: scsi: Device
offlined - not ready after error recovery: host 0 channel 0 id 0 lun 0
<o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: sd 0:0:0:0:
Illegal state transition cancel->offline <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: Badness in
scsi_device_set_state at drivers/scsi/scsi_lib.c:1700 <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel:
<o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: Call
Trace:<ffffffffa000802e>{:scsi_mod:scsi_device_set_state+241}
<o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local
kernel:
<ffffffffa00063d5>{:scsi_mod:scsi_error_handler+2567}
<o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local
kernel:
<ffffffff80110e17>{child_rip+8}
<ffffffffa00059ce>{:scsi_mod:scsi_error_handler+0} <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local
kernel:
<ffffffff80110e0f>{child_rip+0} <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: scsi: Device
offlined - not ready after error recovery: host 0 channel 0 id 0 lun 0
<o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: sd 0:0:0:0:
Illegal state transition cancel->offline <o:p></o:p></P>
<P class=MsoNormal>May 22 20:03:24 compute-2-14.local kernel: Badness in
scsi_device_set_state at
drivers/scsi/scsi_lib.c:1700<o:p></o:p></P></DIV></BODY></HTML>
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq
--===============1783340528==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic