Run interrupt driven hooks: still waiting for xpt_config

[Submaster]

Hi everyone
I'm trying to install fresh XigmaNAS, using latest distro, 12.1.0.4.7091
After some usual bootup process I get errors "Run interrupt driven hooks: still waiting for xpt_config" with timeout in seconds, starting from 30 and freeze after 300

As I tried to google it, it has to be some problem with SAS adapter drivers, but I couldn't find any solutions
My config is:
Supermicro X7SBA
Xeon X3330
Adaptec ASR-8405E
Supermicro SC836TQ-R800B case, SAS backplane with expander

I've got same error with or without any drives attached
I've got same error if I attach no cables at all to Adaptec
I've got NO error with Windows system
I"ve got NO error if I'm removing Adaptec adapter
I've flashed latest firmware to Adaptec and motherboard

Also, same problem goes with ald installation of FreeNAS, also based on FreeBSD

Thanks in advance !

[cookiemonster]

Hi and welcome to the forums. Could you try an installation with 11.3 ? Looks like you've narrowed it to the Adaptec card. I'm sure you have also read the advice about RAID cards in XigmaNAS, where is normally advised to let ZFS access to raw disks.

[Submaster]

Thanks for answer !
I've tried with 11.3.0.4.7014, same result

Also, Adaptec is set to HBA mode, thanks for suggestion

[cookiemonster]

A quick google search for your adapter suggests that there is freebsd support for it on 12.1 : https://www.freebsd.org/cgi/man.cgi?que ... &sektion=4 but there might be a need to load the driver at boot time. Do you want to give that a try?
Hopefully there'll be a developer helping with the thread.

[Submaster]

I've tried to load driver manually (escape to boot prompt - load aacraid) but got "Can't find aacraid", maybe it's not available during install boot ?

[Submaster]

So, I've made it through New Year's and get back to experiments

I've managed to put aacraidu.ko from Microsemi site to USB stick with XigmaNAS 11 installation. Module was in "freebsd 11" folder of FreeBSD driver, so I assume that should work

Boot from XigmaNAS installation - 3 to enter boot prompt, then "load /boot/kernel/kernel" and then "load /boot/aacraidu.ko" - successful
But next step was far from celebrating. I'm entering "boot" command and I can see that controller is up, it even found all of attached hard drives. But then there's prompt to enter loader path. Only sane option is ufs:/ufs/liveboot, but it gets me "unable to load" and reboot

What could be next step ? Could it be that FreeNAS installation somehow intervenes boot process ? I'm planning to install XigmaNAS instead of existing FreeNAS installation, should I format it beforehand ?
Any other ideas ?

[Submaster]

I've opened thread on a FreeBSD forum, since FreeBSD 12.1 installation fails with same error (no surprise here ) and got wonderful link stating that it's confirmed driver bug, known since 05-2016.
Good part is - there's FreeBSD 12.1-Stable build with patched driver and it's able to boot with my configuration.
Is there any method to apply this solution to XigmaNAS ? I've tried to replace aacraid.ko with updated and even all /boot/kernel folder with same from 12.1-Stable - and got different errors I don't know how to deal with. How can I implement updated aacraid.ko to XigmaNAS installation media ?

[Submaster]

A quick google search for your adapter suggests that there is freebsd support for it on 12.1 : https://www.freebsd.org/cgi/man.cgi?que ... &sektion=4 but there might be a need to load the driver at boot time. Do you want to give that a try?
Hopefully there'll be a developer helping with the thread.

I've build two versions of new aacraid driver, one from FreeBSD 12.1-Current and other from sources downloaded from Microsemi site. Then I put them to /cf/boot/kernel of installed XigmaNAS 12.1. After pressing 3 in loader menu I type load /boot/kernel/kernel and then load /boot/kernel/aacraid_f.ko - this is one of new driver modules. And then boot - XigmaNAS boots to some extent, but after device initialization I've got "Manual root filesystem specification" prompt. Why is it so and how could I avoid it ?
It doesn't matter, what module I load and it doesn't matter if controller plugged into system or not