I don't know if it is the 8G driver, but the system complained that it prevented a Promise extension from loading.
A. Are you running driver 2.0.7 and do you have any logs indicating why the kernel extension can't load?
B. Did you try to manually start the kernel extension? If so, what error did you receive?
C. Please document your issue, contact Promise Technical Support, and create a case via https://support.promise.com
1. The current SL2 kernel extension (2.0.7) does load properly on the official release of macOS 10.13 (17A365).
kextstat | grep -i sanlink 182 0 0xffffff7f80f50000 0x90000 0x90000 com.promise.SANLink-FC (2.0.7) 34C49629-A3DA-377A-A705-A2BEBF2FD758 <78 12 5 4 3 1>
2. macOS 10.13 Build Info:
sw_vers
ProductName: Mac OS X ProductVersion: 10.13 BuildVersion: 17A365
3. SANLink2 Utility Info:
mdls -name kMDItemVersion /Applications/SANLink\ Utility.app/ kMDItemVersion = "1.04.0000.08"
4. Kernel logs illustrating the driver initialization phase/sequences:
Note - The same driver can detect the SANLink3 F2; therefore, you will see log entries indicating it could not detect a SANLink3 model.
2017-09-27 01:57:39.037082-0400 localhost kernel[0]: (SANLink-FC) [SL] SANLink2 Driver Loaded 2017-09-27 01:57:40.586824-0400 localhost kernel[0]: (SANLink-FC) [SL] : No SANLink3 F2 connect to the system ... 2017-09-27 01:57:40.907589-0400 localhost kernel[0]: (SANLink-FC) [SL] : No SANLink3 F2 connect to the system ... 2017-09-27 01:57:43.179426-0400 localhost kernel[0]: (SANLink-FC) [SL] ocs_lnx_xport_new_tgt to tgt 0 ctrl:2 2017-09-27 01:57:43.179456-0400 localhost kernel[0]: (SANLink-FC) [SL] begin tgt #0 ctrl:2 2017-09-27 01:57:43.498592-0400 localhost kernel[0]: (SANLink-FC) [SL] ocs_lnx_xport_new_tgt to tgt 0 ctrl:1 2017-09-27 01:57:43.498674-0400 localhost kernel[0]: (SANLink-FC) [SL] begin tgt #0 ctrl:1 2017-09-27 01:57:43.995536-0400 localhost kernel[0]: (SANLink-FC) [SL] finish tgt #0 1 ctrl:2 2017-09-27 01:57:44.314438-0400 localhost kernel[0]: (SANLink-FC) [SL] finish tgt #0 1 ctrl:1
5. mpioutil list (Example with A-Class - A3800f)
Alias Vendor Product LUN Identifier Algorithm 1 A_DATA2 Promise VTrak A3800f 22A7000155EBFECD Least Bytes 2 A_DATA1 Promise VTrak A3800f 2272000155237605 Least Bytes
6. System Profiler Fibre Channel Domain Excerpt (for security reasons, I have used 'X' place holders for the Node & Port WWNs):
system_profiler SPFibreChannelDataType
Fibre Channel:
Fibre Channel Domain 1:
Vendor: Promise
Product: SANLINK
Revision: Firmware 1.1.58.0 Hardware b
Initiator Identifier: 3791655135
Node World Wide Name: XX:XX:XX:XX:XX:XX:XX:XX
Port World Wide Name: XX:XX:XX:XX:XX:XX:XX:XX
Address Identifier: 00:00:02
Description: Port 1
Speed: 8 Gigabit
Topology: Automatic (Point-to-Point)
Status: Link Established
Cable Type: Fiber Optic
Fibre Channel Domain 0:
Vendor: Promise
Product: SANLINK
Revision: Firmware 1.1.58.0 Hardware b
Initiator Identifier: 3791655135
Node World Wide Name: XX:XX:XX:XX:XX:XX:XX:XX
Port World Wide Name: XX:XX:XX:XX:XX:XX:XX:XX
Address Identifier: 00:00:02
Description: Port 0
Speed: 8 Gigabit
Topology: Automatic (Point-to-Point)
Status: Link Established
Cable Type: Fiber Optic
