Well, I don't know a lot about this, but I hate to see anyone go unanswered.
When you boot off your USB stick, that kernel loads the RAID driver for the SRCSASRB, therefore you can see everything
When you boot to EFI, it's a fairly primitive shell, with no RAID driver loaded, so you can't see the RAID volume
However, since you're using hardware RAID, you should be able to set the primary hard drive partition as bootable. You'd have to edit your grub files inside that partition, naturally, but you could then boot straight up to the kernel installed on your RAID 6 hard drives, without using any USB.
Am I coming close?
You have the right idea, but not the right solution
I had not set the partition as bootable, so I have just tried that, with exactly the same results
It seems like the EFI shell cannot see the raid array at all.
Should the raid bios pass an EFI driver to the EFI subsystem?
Is there a way to load extra drivers in the EFI shell so I can see the raid array?
A 'map' command only shows USB devices, and no PCI attached devices
Any extra insight?
I think what you need is booting from a GPT partition right?
Since EFI can only access FAT partitions, normally an EFI-aware OS will create a small EFI partition (like 100MB) and install the EFI boot loader on that partition.
Take a look at the white paper below. It's for Windows but Linux should work the same way. Note that when installing the OS, do NOT boot from the CD directly. Instead, enable "EFI Optimized Boot" from BIOS and boot to EFI shell, and then launch the boot loader from the CD. Then the OS installation program should take care of the rest. Hope that helps.
I had already read the indicated white paper. It states that it is for uEFI, whereas the S5000PAL only supports EFI as far as I can tell.
In my BIOS, I do not see the options referenced in the paper:
EFI Optimised Boot
Use Legacy Video for EFI OS
In my bios, those options do not appear at all. I am using the latest available update for my motherboard.
I had manually created a 256MB FAT partition as the first partition on the raid array (using GPT), The EFI shell cannot see this partition at all.
Oh sorry I missed the server board part... Indeed the white paper doesn't work with EFI. EFI doesn't have embedded RAID driver and thus can't see any partitions on the RAID array.
One workaround is to create a small VD on the RAID controller and make it a MBR disk. Install OS on it, and then create a second VD with the rest of your drive capacity, and make it a GPT drive for data storage.
I had thought of creating a smaller VD in the raid device, but could find no options to do that in the raid bios, or via the MegaCLI command
I have a single RAID6, taking up all 5 drive slots in the chassis.
Does the SRCSASRB raid controller support breaking a large RAID logical device into smaller virtual devices?
Yes SRCSASRB does support breaking a large RAID logical device into smaller virtual devices.
When creating the VD, you can type the size of the VD:
For example, type 100 and select MB, and then click Accept to create a 100MB VD. Now click Back, and then Next to go to this screen again, you'll be able to create a 2nd VD.
I did some more researches and found that for Linux, uEFI is not really required to boot from a GPT disk. Instead, what you need is a kernel supporting GPT, and a GPT-aware boot loader.
See if the following links are helpful for you:
Your suggestions have been most helpful
Splitting the raid device would would work, but I don't want to redo the entire installation
What I have done instead is create a Bios Boot partition: http://en.wikipedia.org/wiki/BIOS_Boot_partition
This allows me to install grub2 directly to the device and boot directly into grub