sure. layout is simple for now.<br>
Device<br>
/dev/sda1&nbsp; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 13&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; 104391&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 82&nbsp;&nbsp;&nbsp; Linux<br>
/dev/sda2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 14&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 743 &nbsp; &nbsp; &nbsp; 5863725&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 82&nbsp;&nbsp;&nbsp; Linux swap<br>
/dev/sda3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 744&nbsp;&nbsp;&nbsp;&nbsp; 19209&nbsp; 148328145&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 83&nbsp;&nbsp;&nbsp; Linux<br><br>
I reinstalled and am using the Centos 5 driver again.&nbsp; I get the same
type of error messages. I think it is related to SMP but I&#39;m not
positive.<br><br><div><span class="gmail_quote">On 10/1/07, <b class="gmail_sendername"><a href="mailto:Patrick_Boyd@dell.com">Patrick_Boyd@dell.com</a></b> &lt;<a href="mailto:Patrick_Boyd@dell.com">Patrick_Boyd@dell.com
</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">








<div link="blue" vlink="purple" lang="EN-US">

<div>

<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">If you have SAS drives you have to use the SAS 5/iR. The
motherboard will control SATA drives independently of the SAS 5/iR.</span></p>

<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">&nbsp;</span></p>

<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Can you tell me how you have the drives configured? Output from
fdisk l would be ideal.</span></p>

<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">&nbsp;</span></p>

<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Thanks,</span></p>

<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Patrick Boyd</span></p>

<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">&nbsp;</span></p>

<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">

<p><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> Jobe Bittman
[mailto:<a href="mailto:jbittman@chewcorp.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">jbittman@chewcorp.com</a>] <br>
<b>Sent:</b> Monday, October 01, 2007 10:39 AM<br>
<b>To:</b> Boyd, Patrick<br>
<b>Cc:</b> linux-poweredge-Lists<br>
<b>Subject:</b> Re: PowerEdge 860 SAS5/iR mptlinux driver crashing repeatedly</span></p>

</div><div><span class="e" id="q_1155c3ae30701823_1">

<p>&nbsp;</p>

<p style="margin-bottom: 12pt;"><a href="http://4.00.00.01" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">4.00.00.01</a>
mptlinux from dell. i also got a similar crash with te centos 5 supplied
mptlinux. there is soemthing wrong with this controller i think. If I enable
SAS in BIOS do I need to open up the server to configure it as 2 separate disks
and use linux software raid? </p>

<div>

<p><span>On 10/1/07, <b><a href="mailto:Patrick_Boyd@dell.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">Patrick_Boyd@dell.com</a></b> &lt;<a href="mailto:Patrick_Boyd@dell.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Patrick_Boyd@dell.com</a>&gt; wrote: </span></p>

<div>

<div>

<p style="text-indent: -0.25in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);">1)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
There is no caching on the SAS 5/iR controllers. Therefore it will always be
write-through.</span></p>

<p style="text-indent: -0.25in;"><span style="font-size: 11pt; color: rgb(31, 73, 125);">2)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
What version of the driver are you using?</span></p>

<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">&nbsp;</span></p>

<div style="border-style: solid none none; border-color: -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">

<p><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:linux-poweredge-bounces@dell.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">linux-poweredge-bounces@dell.com
</a>[mailto:<a href="mailto:linux-poweredge-bounces@dell.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">linux-poweredge-bounces@dell.com</a>]
<b>On Behalf Of </b>Jobe Bittman<br>
<b>Sent:</b> Friday, September 28, 2007 11:30 PM<br>
<b>To:</b> linux-poweredge-Lists<br>
<b>Subject:</b> PowerEdge 860 SAS5/iR mptlinux driver crashing repeatedly</span></p>

</div>

<div>

<p>&nbsp;</p>

<p style="margin-bottom: 12pt;">I am having issues with the PowerEdge 860
SAS5/iR controller. I am running Centos5 64bit and running latest update kernel
2.6.18-8.1.14.el5. I have 2 72G drives striped. I started out using the linux
supplied driver but the dmesg always showed that I write-through caching was
being used. After installing OMSA 5.2 from the Dell hw/sw repos, i discovered
the linux raid driver was hanging and crashing when attempting to connect to
the OMSA web interface. I reloaded the machine and tried installing the
mptlinux driver from the dell repo. It seemed to work great for the day. I even
saw that write-back caching was working. But now I&#39;m running into issues while
running bonnie++ to benchmark my io. The errors in /var/log/messages are below.
I didnt capture the error with the linux driver but it was very similar. <br>
<br>
Has anyone run into this?<br clear="all">
<br>
<br>
Sep 28 21:07:26 san1-test1 kernel: mptscsih: ioc0: attempting task abort!
(sc=ffff810051291e40)<br>
Sep 28 21:07:26 san1-test1 kernel: sd 0:1:0:0: <br>
Sep 28 21:07:26 san1-test1
kernel:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command: Write(10): 2a
00 01 d4 1a 0a 00 01 40 00 <br>
Sep 28 21:07:26 san1-test1 kernel: mptscsih: ioc0: WARNING - TM Handler for
type=1: IOC Not operational (0x40001600)!<br>
Sep 28 21:07:26 san1-test1 kernel:&nbsp; Issuing HardReset!!<br>
Sep 28 21:07:26 san1-test1 kernel: mptbase: Initiating ioc0 recovery <br>
Sep 28 21:07:26 san1-test1 kernel: mptbase: ioc0: WARNING - IOC is in FAULT
state!!!<br>
Sep 28 21:07:26 san1-test1
kernel:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FAULT
code = 1600h<br>
Sep 28 21:07:28 san1-test1 kernel: mptbase: ioc0: Recovered from IOC FAULT <br>
Sep 28 21:07:42 san1-test1 kernel: mptscsih: ioc0: task abort: FAILED
(sc=ffff810051291e40)<br>
Sep 28 21:07:43 san1-test1 kernel: mptscsih: ioc0: attempting target reset!
(sc=ffff810051291e40)<br>
Sep 28 21:07:43 san1-test1 kernel: sd 0:1:0:0: <br>
Sep 28 21:07:43 san1-test1
kernel:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command: Write(10): 2a
00 01 d4 1a 0a 00 01 40 00<br>
Sep 28 21:07:45 san1-test1 kernel: mptscsih: ioc0: target reset: SUCCESS
(sc=ffff810051291e40)<br>
Sep 28 21:09:26 san1-test1 kernel: mptbase: Initiating ioc0 recovery <br>
Sep 28 21:09:36 san1-test1 kernel: BUG: soft lockup detected on CPU#0!<br>
Sep 28 21:09:36 san1-test1 kernel: <br>
Sep 28 21:09:36 san1-test1 kernel: Call Trace:<br>
Sep 28 21:09:36 san1-test1 kernel:&nbsp; &lt;IRQ&gt;&nbsp; [&lt;ffffffff800b2c30&gt;]
softlockup_tick+0xdb/0xed <br>
Sep 28 21:09:36 san1-test1 kernel:&nbsp; [&lt;ffffffff800933ec&gt;]
update_process_times+0x42/0x68<br>
Sep 28 21:09:36 san1-test1 kernel:&nbsp; [&lt;ffffffff80073d61&gt;]
smp_local_timer_interrupt+0x23/0x47<br>
Sep 28 21:09:36 san1-test1 kernel:&nbsp; [&lt;ffffffff80074423&gt;]
smp_apic_timer_interrupt+0x41/0x47 <br>
Sep 28 21:09:36 san1-test1 kernel:&nbsp; [&lt;ffffffff8005bcc2&gt;]
apic_timer_interrupt+0x66/0x6c<br>
Sep 28 21:09:36 san1-test1 kernel:&nbsp; &lt;EOI&gt;&nbsp;
[&lt;ffffffff8000c4d2&gt;] __delay+0x8/0x10<br>
Sep 28 21:09:36 san1-test1 kernel:&nbsp; [&lt;ffffffff880c2e4d&gt;]
:mptbase:WaitForDoorbellInt+0x5b/0x86 <br>
Sep 28 21:09:36 san1-test1 kernel:&nbsp; [&lt;ffffffff880c3023&gt;]
:mptbase:mpt_handshake_req_reply_wait+0x138/0x296<br>
Sep 28 21:09:36 san1-test1 kernel:&nbsp; [&lt;ffffffff8000c4d2&gt;]
__delay+0x8/0x10<br>
Sep 28 21:11:00 san1-test1 kernel:&nbsp; [&lt;ffffffff880c39df&gt;]
:mptbase:SendIocInit+0x229/0x310 <br>
Sep 28 21:11:01 san1-test1 shutdown[12201]: shutting down for system reboot<br>
Sep 28 21:11:17 san1-test1 kernel:&nbsp; [&lt;ffffffff880c33a7&gt;]
:mptbase:GetIocFacts+0x7e/0x2d6<br>
Sep 28 21:12:07 san1-test1 init: Switching to runlevel: 6 <br>
Sep 28 21:12:35 san1-test1 kernel:&nbsp; [&lt;ffffffff880c459f&gt;]
:mptbase:MakeIocReady+0x635/0xa29<br>
Sep 28 21:12:37 san1-test1 kernel:&nbsp; [&lt;ffffffff880c71f6&gt;]
:mptbase:mpt_do_ioc_recovery+0xf0d/0xf4d<br>
Sep 28 21:12:38 san1-test1 kernel:&nbsp; [&lt;ffffffff80072a51&gt;]
smp_send_reschedule+0x4e/0x53 <br>
Sep 28 21:12:38 san1-test1 kernel:&nbsp; [&lt;ffffffff8013b1b2&gt;]
__next_cpu+0x19/0x28<br>
Sep 28 21:12:39 san1-test1 kernel:&nbsp; [&lt;ffffffff800857cf&gt;]
find_busiest_group+0x20d/0x621<br>
Sep 28 21:12:39 san1-test1 kernel:&nbsp; [&lt;ffffffff8006290e&gt;]
__kprobes_text_start+0xfe/0x230 <br>
Sep 28 21:12:39 san1-test1 kernel:&nbsp; [&lt;ffffffff800627d1&gt;]
__reacquire_kernel_lock+0x2c/0x45<br>
Sep 28 21:12:39 san1-test1 shutdown[12243]: shutting down for system reboot<br>
Sep 28 21:12:39 san1-test1 kernel:&nbsp; [&lt;ffffffff80060b5f&gt;]
thread_return+0xb7/0xea <br>
Sep 28 21:12:40 san1-test1 kernel:&nbsp; [&lt;ffffffff880c72e7&gt;]
:mptbase:mpt_HardResetHandler+0xb1/0x109<br>
Sep 28 21:12:40 san1-test1 kernel:&nbsp; [&lt;ffffffff88220df1&gt;]
:mptctl:mptctl_timeout_expired+0x1b4/0x1dc<br>
Sep 28 21:12:41 san1-test1 kernel:&nbsp; [&lt;ffffffff800613bf&gt;]
schedule_timeout+0x92/0xad <br>
Sep 28 21:12:41 san1-test1 kernel:&nbsp; [&lt;ffffffff80092e02&gt;]
process_timeout+0x0/0x5<br>
Sep 28 21:12:41 san1-test1 kernel:&nbsp; [&lt;ffffffff882225ce&gt;]
:mptctl:mptctl_do_mpt_command+0x7b6/0x998<br>
Sep 28 21:12:42 san1-test1 kernel:&nbsp; [&lt;ffffffff8009b681&gt;]
autoremove_wake_function+0x0/0x2e <br>
Sep 28 21:12:42 san1-test1 kernel:&nbsp; [&lt;ffffffff882290cb&gt;]
:mptctl:compat_mpctl_ioctl+0x230/0x31f<br>
Sep 28 21:12:42 san1-test1 kernel:&nbsp; [&lt;ffffffff8822903b&gt;]
:mptctl:compat_mpctl_ioctl+0x1a0/0x31f<br>
Sep 28 21:12:42 san1-test1 kernel:&nbsp; [&lt;ffffffff800e8cb8&gt;]
compat_sys_ioctl+0xc5/0x2b1 <br>
Sep 28 21:12:42 san1-test1 kernel:&nbsp; [&lt;ffffffff8005f013&gt;]
sysenter_do_call+0x1b/0x67<br>
Sep 28 21:12:58 san1-test1 kernel: <br>
Sep 28 21:12:59 san1-test1 kernel: mptscsih: ioc0: attempting task abort!
(sc=ffff8101005429c0) <br>
Sep 28 21:12:59 san1-test1 kernel: sd 0:1:0:0: <br>
Sep 28 21:12:59 san1-test1
kernel:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command: Write(10): 2a
00 02 2a df 8a 00 01 40 00<br>
Sep 28 21:12:59 san1-test1 kernel: mptscsih: ioc0: WARNING - TM Handler for
type=1: IOC Not operational (0x40001600)! <br>
Sep 28 21:12:59 san1-test1 kernel:&nbsp; Issuing HardReset!!<br>
Sep 28 21:12:59 san1-test1 kernel: mptbase: Initiating ioc0 recovery<br>
Sep 28 21:12:59 san1-test1 kernel: mptbase: ioc0: WARNING - IOC is in FAULT
state!!!<br>
Sep 28 21:13:00 san1-test1
kernel:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FAULT
code = 1600h<br>
Sep 28 21:13:00 san1-test1 kernel: mptbase: ioc0: Recovered from IOC FAULT<br>
Sep 28 21:13:00 san1-test1 kernel: mptscsih: ioc0: task abort: FAILED
(sc=ffff8101005429c0) <br>
Sep 28 21:13:00 san1-test1 kernel: mptscsih: ioc0: attempting target reset!
(sc=ffff8101005429c0)<br>
Sep 28 21:13:00 san1-test1 kernel: sd 0:1:0:0: <br>
Sep 28 21:13:01 san1-test1
kernel:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command: Write(10): 2a
00 02 2a df 8a 00 01 40 00 <br>
Sep 28 21:13:01 san1-test1 kernel: mptscsih: ioc0: target reset: SUCCESS
(sc=ffff8101005429c0)<br>
Sep 28 21:13:01 san1-test1 kernel: mptbase: Initiating ioc0 recovery<br>
Sep 28 21:13:01 san1-test1 kernel: BUG: soft lockup detected on CPU#0! <br>
Sep 28 21:13:01 san1-test1 kernel: <br>
Sep 28 21:13:01 san1-test1 kernel: Call Trace:<br>
Sep 28 21:13:01 san1-test1 kernel:&nbsp; &lt;IRQ&gt;&nbsp;
[&lt;ffffffff800b2c30&gt;] softlockup_tick+0xdb/0xed<br>
Sep 28 21:13:01 san1-test1 kernel:&nbsp; [&lt;ffffffff800933ec&gt;]
update_process_times+0x42/0x68 <br>
Sep 28 21:13:02 san1-test1 kernel:&nbsp; [&lt;ffffffff80073d61&gt;]
smp_local_timer_interrupt+0x23/0x47<br>
Sep 28 21:13:02 san1-test1 kernel:&nbsp; [&lt;ffffffff80074423&gt;]
smp_apic_timer_interrupt+0x41/0x47<br>
Sep 28 21:13:02 san1-test1 kernel:&nbsp; [&lt;ffffffff8005bcc2&gt;]
apic_timer_interrupt+0x66/0x6c <br>
Sep 28 21:13:02 san1-test1 kernel:&nbsp; &lt;EOI&gt;&nbsp;
[&lt;ffffffff8000c4d2&gt;] __delay+0x8/0x10<br>
Sep 28 21:13:02 san1-test1 kernel:&nbsp; [&lt;ffffffff880c2e4d&gt;]
:mptbase:WaitForDoorbellInt+0x5b/0x86<br>
Sep 28 21:13:02 san1-test1 kernel:&nbsp; [&lt;ffffffff880c3023&gt;] :mptbase:mpt_handshake_req_reply_wait+0x138/0x296
<br>
Sep 28 21:13:02 san1-test1 kernel:&nbsp; [&lt;ffffffff8000c4d2&gt;]
__delay+0x8/0x10<br>
Sep 28 21:13:03 san1-test1 kernel:&nbsp; [&lt;ffffffff880c39df&gt;]
:mptbase:SendIocInit+0x229/0x310<br>
Sep 28 21:13:03 san1-test1 kernel:&nbsp; [&lt;ffffffff880c33a7&gt;]
:mptbase:GetIocFacts+0x7e/0x2d6 <br>
Sep 28 21:13:03 san1-test1 kernel:&nbsp; [&lt;ffffffff880c459f&gt;]
:mptbase:MakeIocReady+0x635/0xa29<br>
Sep 28 21:13:03 san1-test1 kernel:&nbsp; [&lt;ffffffff880c71f6&gt;]
:mptbase:mpt_do_ioc_recovery+0xf0d/0xf4d<br>
Sep 28 21:13:03 san1-test1 kernel:&nbsp; [&lt;ffffffff80072a51&gt;]
smp_send_reschedule+0x4e/0x53 <br>
Sep 28 21:13:03 san1-test1 kernel:&nbsp; [&lt;ffffffff8011735a&gt;]
avc_has_perm+0x43/0x55<br>
Sep 28 21:13:03 san1-test1 kernel:&nbsp; [&lt;ffffffff80117a1b&gt;]
ipc_has_perm+0x59/0x67<br>
Sep 28 21:13:04 san1-test1 kernel:&nbsp; [&lt;ffffffff8006290e&gt;]
__kprobes_text_start+0xfe/0x230 <br>
Sep 28 21:13:04 san1-test1 kernel:&nbsp; [&lt;ffffffff800862e7&gt;]
dequeue_task+0x18/0x37<br>
Sep 28 21:13:04 san1-test1 kernel:&nbsp; [&lt;ffffffff800627d1&gt;]
__reacquire_kernel_lock+0x2c/0x45<br>
Sep 28 21:13:04 san1-test1 kernel:&nbsp; [&lt;ffffffff80060b5f&gt;]
thread_return+0xb7/0xea <br>
Sep 28 21:13:04 san1-test1 kernel:&nbsp; [&lt;ffffffff880c72e7&gt;]
:mptbase:mpt_HardResetHandler+0xb1/0x109<br>
Sep 28 21:13:04 san1-test1 kernel:&nbsp; [&lt;ffffffff88220df1&gt;]
:mptctl:mptctl_timeout_expired+0x1b4/0x1dc<br>
Sep 28 21:13:04 san1-test1 kernel:&nbsp; [&lt;ffffffff800613bf&gt;]
schedule_timeout+0x92/0xad <br>
Sep 28 21:13:05 san1-test1 kernel:&nbsp; [&lt;ffffffff80092e02&gt;]
process_timeout+0x0/0x5<br>
Sep 28 21:13:05 san1-test1 kernel:&nbsp; [&lt;ffffffff882225ce&gt;]
:mptctl:mptctl_do_mpt_command+0x7b6/0x998<br>
Sep 28 21:13:05 san1-test1 kernel:&nbsp; [&lt;ffffffff8009b681&gt;]
autoremove_wake_function+0x0/0x2e <br>
Sep 28 21:13:05 san1-test1 kernel:&nbsp; [&lt;ffffffff8002dd9c&gt;]
__wake_up+0x38/0x4f<br>
Sep 28 21:13:05 san1-test1 kernel:&nbsp; [&lt;ffffffff882290cb&gt;]
:mptctl:compat_mpctl_ioctl+0x230/0x31f<br>
Sep 28 21:13:05 san1-test1 kernel:&nbsp; [&lt;ffffffff8822903b&gt;]
:mptctl:compat_mpctl_ioctl+0x1a0/0x31f <br>
Sep 28 21:13:05 san1-test1 kernel:&nbsp; [&lt;ffffffff800e8cb8&gt;]
compat_sys_ioctl+0xc5/0x2b1<br>
Sep 28 21:13:05 san1-test1 kernel:&nbsp; [&lt;ffffffff8005f013&gt;] sysenter_do_call+0x1b/0x67<br>
<br>
-- <br>
Jobe Bittman</p>

</div>

</div>

</div>

</div>

<p><br>
<br clear="all">
<br>
-- <br>
Jobe Bittman<br>
Chief Network Architect<br>
Stage6 </p>

</span></div></div>

</div>


</blockquote></div><br><br clear="all"><br>-- <br>Jobe Bittman<br>Chief Network Architect<br>Stage6