hey thanks for replying.
I can't see the drive in bios and I do not know how to use UEFI shell, simply wanted to install via USB flash drive. in the M3 seems to be the opposite, it shows SATA options and can be installed via USB but no mega raid even with the same chassis and SIOC
It seems you are mixing up some terms here; to know if a disk is usable or not it doesn't really matter what a boot menu thinks about it, that stuff can be modified as you see fit anyway.
There are two ways a disk attached to a controller can be used:
1. As a raw disk where the controller doesn't interfere with the communication between the host OS and the disk, effectively meaning the controller plays the role of a Host Bus Adaptor (HBA)
2. As a volume managed by the controller, which in some vendor terminology means different things. This is not a directly accessible disk and all you'll see in the firmware (be it legacy BIOS or UEFI) is the controller presenting itself with volume options
There are two ways your current machine can boot:
1. Legacy BIOS where it just runs a random bit of code on the first few bytes of a disk, hoping that someone put a boot loader in there. (the boot loader or boot manager then uses either a loader specific configuration or looks for the 'active' partition to boot from - some firmwares used to look for the 'active' partition by itself)
2. UEFI boot manager where a persistent list of paths are configured in the UEFI interface that point to specific locations on specific devices.
Before you do either of those you'd need to know what the controller is doing to your disk, and you'd need to know if your OS can actually talk to the controller at all. In some cases the controller isn't usable at all from BIOS of UEFI land, and can only be used inside a full OS or post-bootloader.
If you are doing something like trying to install a desktop OS like windows server, you are likely going to need a driver disk during setup before it can see anything. If you are using Linux, it's possible that the RAID controller needs special drivers too if it doesn't use a standard SATA or SCSI command set to interact with it. Lastly there is the vendor-specific disk configuration, perhaps your controller calls an unused disk a RAW disk, which isn't the same as passing the disk through to the OS in raw form. Sometimes it's pretending JBOD isn't JBOD but a single disk RAID0 (or the other way around). Sometimes it has a real HBA mode. The problem is not really which one it is, but mainly selecting the right option.
In the rare case where the vendor thought it would be fun to not include hardware drivers in UEFI for that RAID card's storage, you can sometimes only see the OptionROM for it over the bus, but not the disks (be it physical or virtual LUNs) at which point you can launch the config but never boot from it because the UEFI can never read the storage directly. This is generally not really what happens but it's still something I come across from time to time on onder and 'pretend-proprietary' setups (like whitebox HP and Dell based systems).
So before continuing, try to get a picture of the way the controller is currently configured.