Hey everyone! I am looking to gather some input, as to experience configuring and using Fibre Channel in Scale. Personally I’ve had no luck, and run Core - because it just works!
Let me know what you think, and thanks in advance for your comments. Have a good one!
Klaus
Adding drivers is not really supported in TrueNAS, Core or SCALE. Just because it worked in Core, does not mean that it is supported. Both are “firmware”, not general purpose OSes or Linux distros.
That said, you can probably enable developer mode and add support packages. Though the FC drivers may not be in the kernel for SCALE.
Have you checked if the FC card has a driver attached?
You can do it with lspci -v from root.
Here we usually suggest sticking with hardware that’s known for working reliably.
I suggest you reading the 10 Gig Networking Primer | TrueNAS Community and giving us more info about your hardware.
Often the compatibility issue is not the system’s fault but manufacturers’ locks.
I wanted to clear things up for this thread, that I’m not looking for troubleshooting of my environment. I am no longer working this problem, as I have a solid solution in TrueNAS Core and my efforts right now are focused upon Openshift/Openstack clusters 
I do however truly appreciate the responses, thanks!
Thus, I am seeking those individuals who have Fiber Channel working on TrueNAS Scale. I look forward to hearing from anyone who has this deployed and running at present.
Thanks again and enjoy the weekend!
Klaus
Op,
You ever get any feedback or see anything other than above?
I have a FC core implementation and was thinking about spinning up a test scale to see if QLA FC and Mellanox IB would work…
…the two most notorious and unsupported methods! 
TN Enterprise reportedly supports Fibre Channel.
Sorry I never responded to this thread! I’ve recently purchased a Dell 8024 for $200 and will do multi-path entirely via iSCSI. This will allow me to make the change to Scale with ease, if so desired. One way of solving for it, I guess. Best of luck to you in all that you do!
FC support for Enterprise customers will be added in 25.04.
Nice, and I would LOVE to run IX gear. Too bad its out of the question to purchase the enterprise box. Guess like others I need to roll my own, for affordability reasons.
Yeah, I’m also just a personal homelab user, so no enterprise support for me either. I’ve always just enabled the components in loader and gone without GUI features.
I have already seen that scale doesn’t like a QLE2460 (which is very old). I might have to see how painful it will be to get a driver (which breaks the appliance mentality).
Get a refurbished Ethernet NIC (Intel X520/540, Chelsio T520, Solarflare). It will be less painful, including on your wallet.
I already have a whole FC fabric, so that’s really cheaper on my wallet other than the watts the switch uses.
This response worries me because I’m not nor will I be an enterprise user since it’s a personal lab.
The middleware controls the SCST.conf file, so even if I CLI add the FC target and LUNs, the GUI will overwrite it.
TN core works fine with FC, just had to add loader tunable.
I think there still needs to be a way to use FC without a contract person use.
I feel you Cory! Home labs don’t typically have a large budget hehehe. However I can tell you that the Dell 8250 24 port 10g switches have come down a bit and usually can be found for around $200. Its still 4 times the cost of a brocade silkworm but it is faster on the plus side…
Best of luck in your usage of FC with IX systems free versions. I’m right here with you, still hanging on to my 4gb fiber in multipath usage
Workaround from a fellow agent of chaos:
install-dev-toolsapt install targetcli-fbsystemctl enable targetclidGo forth and configure…
I was about to suggest re-enabling SCST manually with an edited scst.conf but the middleware continues to manage this file (overwriting changes) even with the service disabled.
Have you done this?
If so, how did you get around the RO? Mount WR and install?
Without modifications, the APT process gets killed immediately, which I haven’t taken the time to look into. Maybe it’s the RO mount or a monitor looking for it?
I was trying to avoid installing anything since “appliance” mentality. I don’t mind coloring outside the lines by doing CLI commands.
Since this is lab and not production, I also wouldn’t mind rigging a way to install custom pieces I could reapply manually or automated with boot scripts between upgrades.
install-dev-tools is sort of a TrueNAS jailbreak – RO is gone-o. From that point you basically have a Debian system until the next upgrade. It won’t stop the middleware from steamrolling configuration changes which are within its scope but in this case you’re moving to an out-of-scope configuration (that you’d still need to re-apply with each upgrade).
It’s annoying but the alternative is abandoning TrueNAS for some other platform.
Some appear to regard ix as a deity. I do not.
, agreed.
A long time ago I couldn’t spell kernel module, now I’m willing to play. There’s no point in spending the money on watts if I can’t do what I want.
I’ll research that now, why not. I haven’t read about it yet, but I’m wondering if you can turn it back off, or commit the changes to the image, until upgrade when naturally needing to reapply changes.
As said, the install-dev-tools basically makes the change for you and installs most of the packages you may need. You can also do it using mount -o remount,rw '/usr' and mount -o remount,ro '/usr' for example.
Hey folks. As mentioned by iX staff in this thread, FC support is a licensed feature for TrueNAS enterprise only. Discussions of how to hack it into the software and circumvent license restrictions are not appropriate for this forum. This thread will be closed.