|
|
|
|
|
by justinsb
5580 days ago
|
|
I think there's a bigger problem here - this isn't just normal bathub-curve component failure. What seems to be happening is that the firmware panics due to an assertion being hit, and what could be a hiccup that requires a reboot becomes a total data loss event. "gamble" suggested above that this is related to power-saving modes. That fits with our different experiences (laptop vs server). Think about how you would feel if you rebooted your server, it went through a different power mode as part of shutdown, and when it came back all eight of your presumably nicely RAIDed drives were dead. Of course a lightning strike could do the same thing, but you have a surge protector that guards against that. How are you protecting against your SSD's firmware? That's my real concern. As to whether it's SandForce or OCZ, I'm just going to go Intel next time. You're free to go with OCZ or a non-battery-backed ramdisk - it's all the same to me :-) |
|
What part of "unless you can back it up with data" didn't you understand?
How are you protecting against your SSD's firmware?
Just like against any other hardware fault: By having backups and redundancy. Bugs happen. You're making it sound as if this was somehow specific to OCZ - which remains bullshit until you provide data beyond anecdotical evidence.
And FWIW I'm neither affiliated with OCZ, nor emotionally tied to the brand. We also run X-25s in production, my Mac Mini has an X-25 and my Macbook has an OCZ.