`<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Hi Steve,</div><div><br></div><div>On Aug 19, 2013, at 9:37 AM, <a href="mailto:steve@linuxsuite.org">steve@linuxsuite.org</a> wrote:</div><br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote>SNIP<br><blockquote type="cite"><blockquote type="cite"><br>c5t5000C50045561CEAd0 Soft Errors: 0 Hard Errors: 1 Transport Errors: 7<br>Vendor: ATA Product: ST3000DM001-9YN1 Revision: CC4H Serial No:<br>W1F09G4Q<br>Size: 3000.59GB <3000592982016 bytes><br>Media Error: 0 Device Not Ready: 0 No Device: 1 Recoverable: 0<br>Illegal Request: 1 Predictive Failure Analysis: 0<br></blockquote><br>Something is sick. Unfortunately, it could be one of the many SATA devices<br>causing disruptions to everyone else -- a good reason to not directly<br>attach<br>SATA devices to SAS expanders. Tracking these down and eliminating a bug<br>in the expander itself, is a tedious task. Is there anything in the JBOD<br>other than<br>the Seagate 3TBs?<br> -- richard<br></blockquote><br> Thanks Richard...<br><br> There are 11 Seagate 3T SATA drives on a single backplane. 10<br>in a RAIDZ-2 and a hot spare. There are no other devices in the JBOD.<br>ZIL is on a separate SSD in a DELL chassis<br><br> So a couple of questions<br><br> i) If there is a single device that has a "large" number of errors<br> compared to the other devices, then perhaps this device is<br> messing up the others? So swapping it out could solve the problem?<br></blockquote><div><br></div><div>In my experience, no. The exact errors and their timeline matters.</div><div>Coincidently, I am looking at methods to approach this problem :-)</div><div>I'll contact you off-alias for details.</div><br><blockquote type="cite"><br> ii) If I had the SATA devices behind SATA port multipliers, will I<br> have the same issues? ie. a single bad device will mess up the others?<br></blockquote><div><br></div><div>Port multipliers are evil, I avoid them at all costs.</div><div><br></div><div>The successful solutions I have seen work are, in no particular order:</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>1. pay the extra $10 and get the SAS version of the disk</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>2. pay $30 and get a SAS-SATA interposer, hopefully your carrier can accommodate</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>3. go direct, get a backplane without an expander (eg Supermicro TQ series)</div><div><br></div><div> -- richard</div><br><blockquote type="cite"><br> iii) Does OmniOS even support SATA HBA connected to SATA port multipliers?<br><br> Perhaps tracking errors on devices will allow for preventative<br>action...<br><br> thanx - steve<br><br><blockquote type="cite"><br>--<br><br>ZFS storage and performance consulting at <a href="http://www.RichardElling.com">http://www.RichardElling.com</a><br><br><br><br><br><br><br><br></blockquote><br><br>_______________________________________________<br>OmniOS-discuss mailing list<br><a href="mailto:OmniOS-discuss@lists.omniti.com">OmniOS-discuss@lists.omniti.com</a><br>http://lists.omniti.com/mailman/listinfo/omnios-discuss<br></blockquote></div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">--</div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br></div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><a href="mailto:Richard.Elling@RichardElling.com">Richard.Elling@RichardElling.com</a><br>+1-760-896-4422<br><br><br></div></span></div></span></div></span></div></span></div>
</div>
<br></body></html>`