Because the new Corsair Performance Pro SSD should be especially good for RAID Controllers with it´s Auto Garbage Collection feature we try to use it with an LSI 9240 Controller and VMware ESXi 5.0. Everything works fine until we try to reboot the System (HP ML330 G6). After that the SSD shows "configured bad" and a size of 0 MB in the LSI BIOS display and is not recognized any more from the OS. Even an additional reboot won´t help. Only a complete power cycle (cold boot) resets the Performance Pro 256. A test with another SSD brand shows no problems with rebooting in the same configuration.
This happens not only with ESXi but also with other Linux OS and with Windows 7. Another test with a HP Smart Array P410i controller shows the message "overheated" on reboot. Because we need the auto reboot feature for VMware DRS this SSD is not usable for us. It seems that firmware 1.0 is too early to use for other environments than onboard SATA controllers. Hopefully the firmware improves with the time, because the benchmarks looks very promising for this SSD....
Is this a general problem for SSDs not behaving like a normal HDD on a RAID controller ? If this is the case maybe it´s too ealy to use customers SATA SSD´s in a server environment....
Alex
This happens not only with ESXi but also with other Linux OS and with Windows 7. Another test with a HP Smart Array P410i controller shows the message "overheated" on reboot. Because we need the auto reboot feature for VMware DRS this SSD is not usable for us. It seems that firmware 1.0 is too early to use for other environments than onboard SATA controllers. Hopefully the firmware improves with the time, because the benchmarks looks very promising for this SSD....
Is this a general problem for SSDs not behaving like a normal HDD on a RAID controller ? If this is the case maybe it´s too ealy to use customers SATA SSD´s in a server environment....
Alex
Last edited: