The only time I've seen that, is when using non-validated hard drives. Check out the list at http://www.intel.com/support/motherboards/server/sb/CS-030804.htm - it was updated this year, so it should be pretty current.
Thanks for the hint,
but my drives are not in that document. Before the update of the firmware it runs perfectly for about 6 months. After the firmware upgrade, it doesnt boot. So for my case, there is something wrong with the firmware, cant see the point of incompatiblity. The firmware needs to get fixed.
I would like to say, that not the harddisks are incompatible, but the controller is incompatible to disks. If this situation is ongoing, i will
change to another brand and product. I use raid controllers since 20 years, never had such an issue with lots of different harddisks. if there is a defect disk, i need to change to the next harddisk available, if that is not possibl,e i wouldn't use it for any valuable data. The raid controller should handle every standard or SAS Disk available. This is not an reliable product.
I experienced a similar issue on a Intel desktop board, the DH67CFB3, with the card installed in the only available slot which was an X16 PCIe.
I installed the card, drivers, and web management utility with no attached HDDs. Everything worked, the card was detected and the LSI bios displayed on boot up.
The firmware was updated successfully from Windows 2008 without a problem, then on the next reboot the system hung. Adding drives made no difference. It will no longer boot on this mb.
I will move the controller to a compatible motherboard (Intel S5500BC) and repost on whether the card is recognized.
While the mobo is not certified for use with this controller I can certainly relate to those who had a working configuration which was rendered dysfunctional by an 'update'. I did not find this to be an exercise in confidence building in the robustness of Intel RAID controllers, as I'm sure is the case for others who have similar experiences.
This RS2BL080 controller is my attempt to address an issue with a SRCSASLS4I controller (with a S5500BC mobo) which has a tendancy to not POST on restart, and sometimes (about 50% of the time, in fact) even when it does it loses all information about the array configuration forcing a rebuild of all the drive arrays after reboot.
On the subject of the Intel Server Configurator and 'compatible' configurations the unstable SRCSASLS4I controller I'm replacing is paired with an AXX6DRV3GEXP backplane (which finally got a FW update this July) and is using WD RE3 HDDs. As these were all items chosen using the Intel Server Configurator as compatible, only later to be identified by Intel as having issues specific to each part of this configuration (WD RE3 drives must have a jumper installed to ensure they run at 1.5 Mb/s or drives may drop from the array, AXX6DRV3GEXP requires a FW update and is not stable when used with unjumpered RE3s, and BTW, even after jumpering the drives down to 1.5Mb/s the above problems are still manifest) I am no longer feeling incompetent, unlucky, inobservant, or unprofessional that I have configured a server which has never been stable.
If I were an engineer in the storage group at Intel that advised on the compatibility of these not-quite-ready for prime time components, and having made your resellers look somewhat less than competent, I would not shed my feelings of guilt or inadequacy so quickly.
Right about now, however, I am beginning to question my sanity for spec'ing another Intel RAID controller to address the multitude of issues with the first one. In hindsight this is not in spite of the fact that all of the configuration I'm putting in place is shown as compatible on the Intel website, but because having gone through that exercise in the first place I still ended up in this mess.