Be vary of RAID controllers on newer chipsets (all which are pure UEFI). There is no guarantee whatsoever from any of the vendors that RAID/HBA card will work properly. Most consumer boards don't support Int15 which is required for normal operation. Only server grade chipsets are supported like e.g. C6xx family.
I felt this rubbish myself when 7 series outright refused to work, nobody cared about fix. 6 series also for most part didn't worked properly on X99. 8 series Adaptecs work on X99 100%, I know that most of LSI cards are trouble free. I haven't got a clue about Z270 tho, but like I've said be very vary of RAID controllers on UEFI powered consumer boards. Old school BIOS retained irq, int and all addressing stuff in same space for decades. With "invention" of UEFI, outside basic ground work supplied by Intel (or AMD) there are NO rules.
Every UEFI detection procedure is different across the range. What will work on EVGA may or may not work on other vendors boards. It's that stupid. No other word for it.
"No int13 drive found" is normal in two cases:
1. You haven't defined any arrays on the controller (it doesn't matter if volume is bootable or not)
2. Using RAID controller in HBA mode and in this mode you can't create Int13 volumes - all drives are detected as a singular devices, like using ordinary SATA ports off the motherboard.
My current main workstation running in HBA mode (drive pool as RAID is by now totally archaic) and I get "no int13 drive found - bios not installed" every time when PC is POSTing.
32b driver won't work on 64b system. I don't know if KL is limited only to 64b, but 32b is by now prehistoric. Monitoring suite from Adaptec requires about 800MB-1GB of RAM just to run in the background. Accommodating this inside 32b system is not possible.
If you planning to install OS on normal SSD (recommended) please remove everything from the system except SSD and CD drive. You can install controller later. I don't recommend installing RAID card during OS installation process. Sometimes controller forces itself on booting process and you'll end in world of pain. When system is installed and running controller can't takeover Windows Boot Manager.
post edited by ypsylon - 2017/07/20 05:00:51