`<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 22, 2014 at 3:17 PM, 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"><br><div class="">
</div>I know, but if I understand it correctly, I need to not only disable a<br>
particular path, I need to disable mpath support entirely to get<br>
sg_write_buffer to talk to mpt_sas directly, instead of going through<br>
the scsi_vhci glob in the middle (which, presumably, is what's causing<br>
this problem). If I'm misunderstanding this, please do set me straight.<br>
<br>
Cheers,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Saso<br>
</font></span></blockquote></div><br></div><div class="gmail_extra">Actually no. Disabling a physical path works too. That is how I stumbled upon the MP issue. I plugged one of my paths into a second server to attempt using Linux to flash the firmware. When the flash started working from the primary server, I never loaded Linux in the second server.<br>
<br></div><div class="gmail_extra">I think the problem is actually in the disk accepting firmware via multipath not so much the OS. The OS throws the error when a message down a second path gets rejected by the drive. <br>
<br></div><div class="gmail_extra">-Chip<br></div></div>
`