`<div dir="ltr">Richard<div><br></div><div>The thing is - installer does not show those two disks in the list. So I can't install into the disks that are supposed to be boot disks. There only larger Seagate drives offered as install target. My guess was that installed filters disks by their device path, not letting /pci ones through ? That is why I wanted to have proper scsi_vhci before the installer. Was hoping this can be done with mdb.</div><div><br></div><div>Re: scsi_vhci.conf - systems with 3+ years uptime now are very picky about disk replacements (model/vendor). Almost have to feed them Seagate exclusively. If I told anyone that this server won't take TOSHIBA SAS drive but will be more happy with Seagate - I doubt many people would take it seriously. And these days I see lots of TOSHIBA disks that come as replacements. Almost makes one wish for a *some* tool to add entries to vhci and make them active at runtime.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 27, 2014 at 10:54 AM, Richard Elling <span dir="ltr"><<a href="mailto:richard.elling@richardelling.com" target="_blank">richard.elling@richardelling.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On Dec 26, 2014, at 2:36 PM, sergei <<a href="mailto:sergei25@gmail.com">sergei25@gmail.com</a>> wrote:<br>
><br>
> Hi<br>
><br>
> The disks I want to install OmniOS to are TOSHIBA AL13SEB300 model which scsi_vhci won't take over without proper conf file listing this model under "scsi-vhci-failover-override" line. Right now those disk device path starts with /pci instead of /scsi_vhci. Yet they are showing up in format output ok. What is the trick to fix this without rebuilding install ISO image ?<br>
<br>
</span>easy -- don't rebuild the install ISO image :-)<br>
<span class=""><br>
><br>
> I could install into one of (larger) Seagates and then mirror/remove mirror to move boot OS to the proper disks. Is there any easier way ?<br>
<br>
</span>ugh, too much work.<br>
Try this (I'm sure I blogged this a few times, or maybe in the Nexenta knowledge base?)<br>
I'm sure the procedure is in the email archives...<br>
<br>
1. go ahead and do the installation.<br>
2. boot into newly installed OS<br>
3. edit scsi_vhci.conf<br>
4. shutdown<br>
5. boot from install media, go to shell<br>
6. import rpool<br>
7. export rpool<br>
8. reboot into newly installed OS<br>
<br>
ZFS is tolerant of path changes, but you have to trick the boot process.<br>
<span class=""><br>
><br>
> I think it would benefit Omni if you could keep scsi_vhci with at least some updates. I see Nexenta does include bunch of models into it's default scsi_vhci.conf.<br>
<br>
</span>The root cause is a deficiency in detecting multiple ports. The workaround is to override<br>
in scsi_vhci.conf. The fix is known, just need to find the time...<br>
<span class="HOEnZb"><font color="#888888"> -- richard<br>
<br>
</font></span></blockquote></div><br></div>
`