[OmniOS-discuss] 2x acctual disk quantity

[Hafiz Rafibeyli]

Saso  I did as you said,
but on my test 24x chassis(everything same with prod chassis,only difference test chassis has 1 LSI controller)

I added following lines to /kernel/drv/scsi_vhci.conf(being careful with spaces)

device-type-scsi-options-list =
   "HP      EG0300FARTT", "f_sym",
   "HP      EG0300FARTT", "f_sym",
   "HP      EG0300FARTT", "f_sym",
   "HP      EG0300FARTT", "f_sym";

after omnios reboot,format output was same as before.
as you see last 4 HP  disks(wich I added to test chassis for testing) starting with /pci@
am I doing something wrong?

:~# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c1t5000C5004FEB5CD4d0 <ATA-ST2000NM0033-9ZM-0001-1.82TB>
          /scsi_vhci/disk at g5000c5004feb5cd4
       1. c1t5000C5004FEB205Ad0 <ATA-ST2000NM0033-9ZM-0001-1.82TB>
          /scsi_vhci/disk at g5000c5004feb205a
       2. c1t5000C5004FEBCDA1d0 <ATA-ST2000NM0033-9ZM-0001-1.82TB>
          /scsi_vhci/disk at g5000c5004febcda1
       3. c1t5000C5004FED9BE6d0 <ATA-ST2000NM0033-9ZM-0001-1.82TB>
          /scsi_vhci/disk at g5000c5004fed9be6
       4. c1t5000C5004FF4A4AEd0 <ATA-ST2000NM0033-9ZM-0001-1.82TB>
          /scsi_vhci/disk at g5000c5004ff4a4ae
       5. c1t5000C5004FF4E0F9d0 <ATA-ST2000NM0033-9ZM-0001-1.82TB>
          /scsi_vhci/disk at g5000c5004ff4e0f9
       6. c1t50000393DB700B6Ad0 <ATA-TOSHIBA MK2002TS-MT2A-1.82TB>
          /scsi_vhci/disk at g50000393db700b6a
       7. c1t50000393DB700B6Bd0 <ATA-TOSHIBA MK2002TS-MT2A-1.82TB>
          /scsi_vhci/disk at g50000393db700b6b
       8. c1t50000393DB700B68d0 <ATA-TOSHIBA MK2002TS-MT2A-1.82TB>
          /scsi_vhci/disk at g50000393db700b68
       9. c1t50000393DB700B69d0 <ATA-TOSHIBA MK2002TS-MT2A-1.82TB>
          /scsi_vhci/disk at g50000393db700b69
      10. c1t500003944B703F9Bd0 <ATA-TOSHIBA MK2002TS-MT4A-1.82TB>
          /scsi_vhci/disk at g500003944b703f9b
      11. c1t500003944B703F9Dd0 <ATA-TOSHIBA MK2002TS-MT4A-1.82TB>
          /scsi_vhci/disk at g500003944b703f9d
      12. c1t500003944B703F9Fd0 <ATA-TOSHIBA MK2002TS-MT4A-1.82TB>
          /scsi_vhci/disk at g500003944b703f9f
      13. c1t500003944B783D3Fd0 <ATA-TOSHIBA MK2002TS-MT4A-1.82TB>
          /scsi_vhci/disk at g500003944b783d3f
      14. c1t500003944B80451Ed0 <ATA-TOSHIBA MK2002TS-MT4A-1.82TB>
          /scsi_vhci/disk at g500003944b80451e
      15. c1t500003944B80451Fd0 <ATA-TOSHIBA MK2002TS-MT4A-1.82TB>
          /scsi_vhci/disk at g500003944b80451f
      16. c1t500003944B704306d0 <ATA-TOSHIBA MK2002TS-MT4A-1.82TB>
          /scsi_vhci/disk at g500003944b704306
      17. c1t500003944B804521d0 <ATA-TOSHIBA MK2002TS-MT4A-1.82TB>
          /scsi_vhci/disk at g500003944b804521
      18. c1t500003944B804534d0 <ATA-TOSHIBA MK2002TS-MT4A-1.82TB>
          /scsi_vhci/disk at g500003944b804534
      19. c3t0d0 <Unknown-Unknown-0001 cyl 1953 alt 2 hd 255 sec 63>
          /pci at 0,0/pci15d9,100 at 1f,2/disk at 0,0
      20. c3t1d0 <ATA-SATASSD-.02c cyl 1953 alt 2 hd 255 sec 63>
          /pci at 0,0/pci15d9,100 at 1f,2/disk at 1,0
      21. c4t500000E1168BB382d0 <HP-EG0300FARTT-HPDA-279.40GB>
          /pci at 0,0/pci8086,340e at 7/pci15d9,691 at 0/iport at f/disk at w500000e1168bb382,0
      22. c4t500000E11693F232d0 <HP-EG0300FARTT-HPDA-279.40GB>
          /pci at 0,0/pci8086,340e at 7/pci15d9,691 at 0/iport at f/disk at w500000e11693f232,0
      23. c4t500000E11696D5A2d0 <HP-EG0300FARTT-HPDA-279.40GB>
          /pci at 0,0/pci8086,340e at 7/pci15d9,691 at 0/iport at f/disk at w500000e11696d5a2,0
      24. c4t500000E116974FB2d0 <HP-EG0300FARTT-HPDA-279.40GB>
          /pci at 0,0/pci8086,340e at 7/pci15d9,691 at 0/iport at f/disk at w500000e116974fb2,0
	
On 12/3/13, 8:13 AM, Hafiz Rafibeyli wrote:
> Saso ,I will try edit /kernel/drv/scsi_vhci.conf as you described and will inform you.
> 
> why these new disks not dedected by scsi_vhci automatically?
> 
> is this because of settings in my /kernel/drv/mpt.conf and /kernel/drv/mpt_sas.conf files?

No, it has nothing to do with mpt.conf (which is a different
configuration file for a different driver altogether). The reason is
that scsi_vhci contains a whitelist of devices and associated failover
modules (i.e. methods for implementing multipathing). If your device
isn't whitelisted, then scsi_vhci doesn't know which failover module to
use and instead, as a failsafe, decides to do nothing. You can find more
info on the scsi_vhci man page:
http://docs.oracle.com/cd/E19253-01/816-5177/6mbbc4gal/index.html

Cheers,
-- 
Saso