[OmniOS-discuss] Sneak modified scsi_vhci.conf in under installer ?

[sergei]

Richard

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.

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.


On Sat, Dec 27, 2014 at 10:54 AM, Richard Elling <
richard.elling at richardelling.com> wrote:

>
> > On Dec 26, 2014, at 2:36 PM, sergei <sergei25 at gmail.com> wrote:
> >
> > Hi
> >
> > 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 ?
>
> easy -- don't rebuild the install ISO image :-)
>
> >
> > 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 ?
>
> ugh, too much work.
> Try this (I'm sure I blogged this a few times, or maybe in the Nexenta
> knowledge base?)
> I'm sure the procedure is in the email archives...
>
> 1. go ahead and do the installation.
> 2. boot into newly installed OS
> 3. edit scsi_vhci.conf
> 4. shutdown
> 5. boot from install media, go to shell
> 6. import rpool
> 7. export rpool
> 8. reboot into newly installed OS
>
> ZFS is tolerant of path changes, but you have to trick the boot process.
>
> >
> > 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.
>
> The root cause is a deficiency in detecting multiple ports. The workaround
> is to override
> in scsi_vhci.conf. The fix is known, just need to find the time...
>  -- richard
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20141227/25e317a3/attachment.html>