macOS 15.5 SANLink3 F2 Xsan: FC Write Timeout and c3timeout Errors
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!
---
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,
