panic: APIC: CPU with APIC ID 0 is not enabled
"ZFS can not fully protect the user's data when using a hardware RAID controller, as it is not able to perform the automatic self-healing unless it controls the redundancy of the disks and data. ZFS prefers direct, exclusive access to the disks, with nothing in between that interferes. If the user insists on using hardware-level RAID, the controller should be configured as JBOD mode (i.e. turn off RAID-functionality) for ZFS to be able to guarantee data integrity.
The problem is that if the underlying RAID controller detects an error it will try to do its own recovery of the data. If it's unable to do so it will declare the volume dead and it won't permit the ZFS file system to access the data in order to recover at that level.
If a drive dies (the error), you replace it and the RAID controller rebuilds the set (the recovery). But if, during the course of the rebuild, it can't read required data from one of the other surviving disks then as far as the controller is concerned the whole volume is toast.
All of this takes place below the ZFS level - the ZFS file system has no ability to control or recover from this process."
"One might be inclined to try using single-drive RAID 0 arrays to try to use a RAID controller like a HBA, but this is not recommended for many of the reasons listed for other hardware RAID types. It is best to use a HBA instead of a RAID controller, for both performance and reliability."
That would be welcome news. In the DL360/380 Gen 5 and Gen 6 servers I've been working with, I installed LSI-based add-in controllers and bypassed the built-in controllers that Jarek6 mentioned. Perhaps when I finally outgrow the Gen 6 hardware I'll be able to take advantage of this...In the UEFI setup there's a SmartArray configuration utility, where it will allow you to switch the controller into IT mode. It will then act as a plain SAS HBA without RAID.