`<div dir="ltr"><div><div>Are you sure you have SAS multipath disabled on the disk you are trying to flash?<br><br></div>I couldn't get these to flash at all with MP enabled. I too kept getting OS related errors.<br><br>
For one system I did an stmsboot -d, for another I just pulled one of the SAS cables to each JBOD.<br><br></div>-Chip<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 22, 2014 at 4:36 AM, Saso Kiselkov <span dir="ltr"><<a href="mailto:skiselkov.ml@gmail.com" target="_blank">skiselkov.ml@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 4/18/14, 10:49 PM, Schweiss, Chip wrote:<br>
> I used Santools, which is a licensed product.<br>
><br>
> From what I understand lsiutil and sg_buffer_write from sg3-utils can do<br>
> it too. The mode for sg_buffer_write may need to be set to 7 instead of<br>
> 5 as stated in the firmware docs.<br>
><br>
<br>
</div>Sadly, I had no luck with either lsiutil or sg_write_buffer from<br>
sg3-utils. lsiutil is only for older MPT HBAs (I have an MPT 2.0 one)<br>
and sg_write_buffer fails with the following error:<br>
<br>
# sg_write_buffer -v --in=MegalodonES3-SAS-STD-0004.LOD --length=1625600<br>
--mode=5 /dev/rdsk/c9t5000C500578F774Bd0<br>
Write buffer cmd: 3b 05 00 00 00 00 18 ce 00 00<br>
ioctl(USCSICMD) failed with os_err (errno) = 22<br>
write buffer: pass through os error: Invalid argument<br>
Write buffer failed res=-1<br>
<br>
I also tried the following device names:<br>
/dev/rdsk/c9t5000C500578F774Bd0p0<br>
/dev/dsk/c9t5000C500578F774Bd0<br>
/dev/dsk/c9t5000C500578F774Bd0p0<br>
<br>
The OS also printed the following error:<br>
<br>
WARNING: mpt_sas: coding error detected, the driver is using<br>
ddi_dma_attr(9S) incorrectly. There is a small risk of data corruption<br>
in particular with large I/Os. The driver should be replaced with a<br>
corrected version for proper system operation. To disable this warning,<br>
add 'set rootnex:rootnex_bind_warn=0' to /etc/system(4).<br>
<br>
Staring at the code near usr/src/uts/i86pc/io/rootnex.c:3305, this means<br>
that the driver can't submit a DMA job this large, which means that I<br>
can't really fix this at all (this is really way outside of my field).<br>
<br>
Any ideas on what to do next?<br>
<br>
Cheers,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Saso<br>
</font></span></blockquote></div><br></div>
`