umack Posted July 25, 2010 Share Posted July 25, 2010 Hi, I have been trialling a Corsair CSSD-F60GB2 for 3 weeks now and while it is brilliantly fast running as a system disk for Server 2008 R2 and really underlines the value of using SSDs for servers, the Corsair SSD itself is a total disaster as a server system disk because of it's unreliability. The server is turned on 24/7 and every couple of days the SSD goes offline, causing a BSOD and inaccessible boot device error. A reboot fails with the drive not visible in the system BIOS. It the server is powered off and back on again the SSD is visible, the system boots and everything works perfectly for the next couple of days. There are a number of other references to this sort of thing happening, both on this forum and elsewhere. That suggests this is not an uncommon problem with the firmware/hardware of this model SSD. To quote an article on SSDs: The issue here is that Corsair's recently released Force series of SSDs are shipping (and continue to ship) with v3.0.1 installed, which -- according to SandForce -- will never be viewed as the final version ready for mass consumption. As the story goes, v3.0.1 may experience a reliability issue with a power management state, but v3.0.5 caps small file random write performance as to better separate the SF-1200 drives from the pricier SF-1500 drives. See http://www.legitreviews.com/article/1312/1/ This suggests that there could be an issue with the Sandforce firmware revision. When I looked for a firmware update I found the 60GB drive is not in the support list (SSDs > select your product from the list). I can get a replacement drive by RMA, but if it behaves in the same way, Corsair have lost an opportunity to become a standard for our servers. Do these drives have a known problem that Corsair are willing to fix? Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted July 27, 2010 Corsair Employee Share Posted July 27, 2010 We are looking into the problem, it seems the there are a few who have reported problems and we are checking now to see what the issue and or solution might be. Link to comment Share on other sites More sharing options...
asteriskstar Posted October 1, 2010 Share Posted October 1, 2010 has this problem too, any update ? Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted October 2, 2010 Corsair Employee Share Posted October 2, 2010 There are several threads talking about this, if you still need more information please bump the post on Monday. Link to comment Share on other sites More sharing options...
sandy901 Posted October 5, 2010 Share Posted October 5, 2010 I too have had some problems where a complete power cycle of the drive causes it to fail to be detected during boot. If I give the drive an extra few seconds and hit ctrl+alt+del to reboot, I can usually get it back up and running. This seems to be a firmware issue with the drive and is definitely deserving of a firmware update or workaround. I have the following drive: Corsair CSSD-F120GB2 FW Rev 1.1 Link to comment Share on other sites More sharing options...
Corsair Employee RAM GUY Posted October 5, 2010 Corsair Employee Share Posted October 5, 2010 What is the make and model of MB you are using and did you try and Disable Suspend to Ram and Hybrid suspend? Link to comment Share on other sites More sharing options...
sandy901 Posted October 8, 2010 Share Posted October 8, 2010 The system is a Thinkpad T410 using BIOS 6IET72WW (1.32 ) PCI bus devices: 00:00.0 0600: 8086:0044 (rev 02) 00:02.0 0300: 8086:0046 (rev 02) 00:16.0 0780: 8086:3b64 (rev 06) 00:16.3 0700: 8086:3b67 (rev 06) 00:19.0 0200: 8086:10ea (rev 06) 00:1a.0 0c03: 8086:3b3c (rev 06) 00:1b.0 0403: 8086:3b56 (rev 06) 00:1c.0 0604: 8086:3b42 (rev 06) 00:1c.1 0604: 8086:3b44 (rev 06) 00:1c.3 0604: 8086:3b48 (rev 06) 00:1c.4 0604: 8086:3b4a (rev 06) 00:1d.0 0c03: 8086:3b34 (rev 06) 00:1e.0 0604: 8086:2448 (rev a6) 00:1f.0 0601: 8086:3b07 (rev 06) 00:1f.2 0106: 8086:3b2f (rev 06) 00:1f.3 0c05: 8086:3b30 (rev 06) 00:1f.6 1180: 8086:3b32 (rev 06) 03:00.0 0280: 8086:0089 (rev 35) 0d:00.0 0805: 1180:e822 (rev 01) 0d:00.1 0880: 1180:e230 (rev 01) 0d:00.3 0c00: 1180:e832 (rev 01) ff:00.0 0600: 8086:2c62 (rev 02) ff:00.1 0600: 8086:2d01 (rev 02) ff:02.0 0600: 8086:2d10 (rev 02) ff:02.1 0600: 8086:2d11 (rev 02) ff:02.2 0600: 8086:2d12 (rev 02) ff:02.3 0600: 8086:2d13 (rev 02) Specifically the SATA controller when inside Linux: 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06) (prog-if 01 [AHCI 1.0]) Subsystem: Lenovo Device 2168 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 45 Region 0: I/O ports at 1860 Region 1: I/O ports at 1814 Region 2: I/O ports at 1818 Region 3: I/O ports at 1810 Region 4: I/O ports at 1840 Region 5: Memory at f2827000 (32-bit, non-prefetchable) Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0100c Data: 4189 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] SATA HBA <?> Capabilities: [b0] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.