yes, you can expand the array on LSI cards with the Online Capacity Extend (OCE).
Back to a question I asked earlier, how are you attaching the SAS drives to the card? They have a different connector, didn't want you to get surprised later on.
Certain desktop drives do not work well the Seagate 3TB Baracuddas for example. The NAS drives almost always work, I have used the WD Red drives and have he Seagate NAS ones now. Just be careful on the desktops.
Based on your comments, I may be in trouble.. I have NO NAS or RED drives... Only desktops.. And a lot of them.
The server currently hosts:
2TB WDC WD20EARX-00PASB0 <= DANGER!! Imminent self-destruct
2TB ST2000DL003-9VT166
2TB HDS5C3020ALA632
2TB HDS5C3020ALA632
2TB ST32000542AS
2TB HDS5C3020ALA632
2TB ST2000DM001-1CH164
2TB ST2000DM001-1CH164
320G WD3200AAKS-75VYA0
320G ST3320620AS
250G ST3250820AS
And 2 other 2TB Hitachi's like the Deskstar 5k3000, and a 3TB Seagate (cant remember the model number but definitely desktop drive)..
I have three scenarios to use all these drives and have the simplest setup (nothing better than the KISS principle!)
Scenario 1:
The M5016 is connected to a SAS expander. One 300GB SAS drive connected to the first SAS port of the M5016, the expander connected to the other SAS port. From the expander, a second SAS drive connected to a port, assembled as RAID1 with the other SAS drive from the M5016. Esxi and critical data onto that array.
Then from the expander, I connect all other drives (except the smaller /older ones) using a SAS to SATA fanout cables.. All drives assembled as a RAID5 array at the controller's level, then passed to a VM for usage...
Finally, the two 320GB & the 250GB are assembled as a RAID0 array or discarded and later replaced by a SSD (which is the intent soon enough..)
Scenario 2:
2X 300GB SAS drives connected to the M5016 and assembled as RAID1, Esxi and critical data onto that array.
The M1015 remains in the server, all 2TB drives connected to it as it is now, the M1015 passed through to the main VM and continue to use the linux RAID5 array.. Problem with this option is that the large RAID5 array wont benefit from the M5016's cache and supercap..
Scenario 3:
Same as scenario 2, but basically the M1015 is eliminated (reused in another build), all 2TB drives are connected to the motherboards SATA ports and passed through to the main VM for a linux RAID5 array. Problem with this is the lack of SATA ports on this motherboard. Only has 6, so increasing the RAID5 array wont be possible..
I overall much prefer scenario 1 due to all drives will be able to benefit from the controller's cache and supercap. The only downside is the necessity of a SAS expander, but I understand a basic one is not too expensive..
DO you see significant issues with the scenario 1? For example, SAS and SATA drives together but NOT in the same arrays...