Other How can I present a usable LU to Windows using a QLogic FC HBA?

robroy

robroy

FreeBSD Friends,

I have a Supermicro X10SLL-F with a QLogic QLE2694 on FreeBSD 15.0-RELEASE-p7.

The HBA is on firmware 9.15.1 (both fw_version_run and fw_version_flash).

This host is a target presenting LUs to several initiators (all running QLE2690, also on 9.15.1). Hosts running Linux and ESXi can see and use the LUs with no problems.

But not Windows--both Windows Server 2022 and 2025 have problems:
  • 2022 can boot from the LU, but gives me a BSOD seconds after arriving at the login screen.
  • 2025 (not booted over FC) can see the LU after booting, but the LU cannot be initialized; trying to initialize shows "The device is not connected."
I have toyed with various configurations for hours (and even tried lousy AI suggestions), with no luck.

My configuration looks like this:

Code: 
# ctladm port -o on isp2
# ctladm create -b block -o file=/dev/zvol/s/gem3-win -S MYSERIAL0004 -d MYDEVID0004
# ctladm lunmap -p 5 -L 4 -l 0

How can I present an LU that Windows likes?

Thank you very much.
 
I don't understand. You have a pretty normal sounding machine, with a relatively recent (~5 years old) Marvell/Qlogic FC HBA. It seems you can run FreeBSD on it, and Linux, and ESXi. That all sounds good.

But Windows doesn't work on it. How is this related to FreeBSD? Wouldn't asking on a "Windows forum" (ha ha, if such a thing existed) be more sensible?
 
he's using his freebsd box as a SCSI target over Fibre Channel. a LU is a SCSI term. as we read it, windows is not having a good time talking SCSI to it. therefore we would recommend setting sysctl -w kern.cam.ctl.debug=1 on the freebsd host, booting the windows box, and checking the kernel log for the CAM errors.
 
You must log in or register to reply here.
Back
Top