Am 17.07.2015 um 18:15 schrieb Daniel Frey: > Well, I sure haven't had much luck with SSDs. This will be the third one > I've lost. > > On Wednesday I was watching my mythtv frontend when it hardlocked. Last > time this happened the 7-year-old rust recordings drive failed. However, > all that checked out and I found out I couldn't ssh in to the frontend > to kill mythfrontend. > > I checked the CPU & RAM by booting via USB and it all checked out. I > tried booting the SSD and the kernel panicked. After rebooting again, it > started, but every command run ended with a segmentation fault. > > I decided to try flashing the drive's firmware, and that did so > successfully. It booted right away after that with no panic, but the > frontend decided that it couldn't find the backend any longer. I found > this was not true, I (as root) could ping and connect via mysql using > remote credentials. > > After another twenty minutes of fiddling around, I discovered the setUID > root bit on /bin/ping had been removed somehow and this was preventing > mythtv from finding its backend. At this point I restored from backup > and then I discovered after restoring /bin/ping lost it setuid root bit > again. > > After that I gave up (thinking what else has changed on the disk) and > yesterday bought a new SSD, this time a SanDisk model. It was cheap and > I hope I don't regret this in the future. So my frontend is once again > running. > > That aside, the drive that failed is a Crucial m4. I have done some > searching as how to run diagnostics on an SSD. This drive should still > have eight or so months of warranty left. These drive did have a bug if > they ran longer than 51xx hours but: > > 9 Power_On_Hours 0x0032 100 100 001 Old_age Always > - 2382 > > ...there's only 2382 on this drive. It also accesses all media remotely > through the LAN. > > Currently I'm running shred on the affected SSD. I also could run > smartctl on the drive. Do other diagnostic tools even work on SSDs? This > is where I'm sort of lost, I've not tried diagnostics on them. I usually > send them back for warranty, but this time I'm curious. > > Dan > >
you know - this does not sound like ssd failure. Most SSDs bomb out by just becoming completely unacessible. dmesg errors? are you using ecc ram? if not - maybe, just maybe it is your ram at fault. The stuff the kernel sends and the stuff that end on the ssd might not be identical.
