As I have documented in other threads, I've had some problems with an SSD mounted as root recently, and have solved these. My original problems started with a faulty unit (OCZ Agility 3 - which appears to have a massive failure rate). I replaced it with a Crucial M4, and have had a stable system for 4 -5 days now with no ATA errors. However, I've made one or two compromises to achieve this. When I first fitted the new (replacement) drive I set it up much the same way as the faulty one, with three partitions. /boot, /, and a spare. Almost immediately I started getting ata freezes and filesystem corruption (not as bad as the OCZ, but still worrying). I did a factory wipe of the drive, set up the partitions again, but this time I built TRIM into the filesystem, and I have only migrated /. /boot remains on a platter, and the spare is mounted in userspace without issue. It appears for all intents and purposes that if I put /boot on to the SSD that is enough to prompt the ata bus errors (I'll admit I could be wrong and the factory wipe may have settled some stuff down).So, having now migrated my system a total of a dozen times including the faulty drive, I'm reluctant to change things, but I am curious as to whether I am the only person to notice this. I'm 90% certain that /boot on the SSD is the root of the problems. Leaving /boot on a spinner doesn't cost me any noticable difference since only the kernel is loaded from the spinner. Everything else comes from the SSD. It would, however, be useful to document observed failures of SSD and the (probable) fixes or methods to avoid problems. SSDs are gaining popularity, and such problems are likely to surface more and more frequently.
I invite discussion or observations that will show me to be right or wrong, but which will/may help future migrations for others.
]]>