Searching: SANLink3 T1 - 62 Results Found

VESS A6000 Series Compatibility Issue with ST12000VN0008 on Promise A6120 (SR1.5)
weerachai rojanaburanon posted this 31 July 2025 - Last edited 31 July 2025

I am currently using a Seagate IronWolf 12TB drive (Model: ST12000VN0008) with a Promise A6120 system, running firmware SR1.5.

I would like to report that:

  • The drive is not being detected properly under CLI command phydrv -v or during initialization.

  • I have confirmed with Seagate that the drive's firmware is up to date, and it uses a standard SATA interface under the IronWolf NAS line.

  • However, this model is not explicitly listed in the SR1.5 compatibility list.

Given that IronWolf drives are generally supported, and similar models function properly, I would like to know:

  1. Does SR1.5 officially support ST12000VN0008 drives, even if not listed?

  2. Is there any known workaround or patch to allow detection of this drive on the A6120?

  3. Are there future firmware updates planned that will add support for this drive model?

Thank you for your help in resolving this compatibility issue.

 

  • 0
SANLink3 macOS 15.5 + SANLink3 F2 + Xsan: FC Write Timeout and c3timeout Errors
terry wang posted this 11 July 2025

Hi all,

 

We’ve recently encountered a serious Fibre Channel I/O timeout issue when using macOS 15.5 with a Promise SANLink3 F2 adapter in an Xsan environment.

 

### Environment:

- macOS Sequoia 15.5 (latest public release)

- Promise SANLink3 F2 (dual-port 16Gb FC)

- Apple Xsan with MDC + metadata LUNs + data LUNs on FC storage

- Brocade FC switch (with zoning configured)

- Multipath (MPIO) enabled

 

### Problem Description:

On macOS 15.5 systems connected to Xsan via SANLink3 F2, we consistently observe **write I/O timeouts**, followed by **abort and chip timeout errors**. These show up in the system log as:

 

This corresponds to failed write operations (SCSI op 0x2A) and eventually causes the mount point to hang or file system-level errors in Xsan volumes.

 

### Diagnostics Performed:

- `log show --last 5m | grep sanlink` confirms repeated timeouts.

- FC switch shows **extremely high c3timeout counts** on port 32 (~89,900).

- However, port 32 is **not physically connected** or zoned — it’s unused.

- No CRC, sync loss, or PCS errors were found on other active FC ports (32–47).

- Disabling port 32 on the switch improves system behavior temporarily.

- Suspected residual MPIO paths pointing to nonexistent targets may be involved.

 

### Attempts to Resolve:

- Re-seated SFPs and fibre cables

- Reinstalled latest Promise SANLink drivers (still no official macOS 15.5 support)

- Disabled unused FC ports at the switch level

- Verified zoning is correct for active LUNs

- Tried removing/rebuilding volume metadata in Xsan

 

### Key Question:

Has anyone else seen **write timeouts or c3timeout-related errors** with macOS 15.5 and SANLink3 F2 in an Xsan setup? Could this be due to compatibility issues with SANLink drivers on macOS 15.5?

 

Any insight or suggestions would be much appreciated!

 

---

 

Thanks in advance,

 

  • 0
Search
Categories
Close