On Jun 23, 2014, at 10:34 PM, Mike Hartman <m...@hartmanipulation.com> wrote:
>> >> Firmware 0007 is current for this SSD. > > I assume that's probably not something I should mess with right now > though, right? I would deal with that later. A firmware change now might make things worse if you care about this file system or any data on the drive. But seeing as it "improves reliability" I have no way of knowing if it's related. > Actually, now that I think about it, that may be related to the errors > I saw months ago. I had some bad blocks or something, and when the > system attempted to access them I would get a bunch of errors in the > logs. I believe one of the things the system would do was attempt to > reset the drive connection (maybe multiple times). Yes Ok that's normal. > I zeroed out the drive and ran every smartctl test on it I could find > and it never threw any more errors. Zeroing SSDs isn't a good way to do it. Use ATA Secure Erase instead. The drive is overprovisioned, so there are pages without LBAs assigned, which means they can't be written to by software. Plus "zeros" make SSD pages full of zeros, rather than being empty and ready to be written to. ATA Secure Erase is supposed to make them empty (write ready) and does it for all pages. http://mackonsti.wordpress.com/2011/11/22/ssd-secure-erase-ata-command/ > I'll see if I can track down any of the smartctl results from back > then and compare the "Number of Hardware Resets" value, as well as > UDMA_CRC_Error_Count. It could be a loose or intermittent connection; maybe they are one off events as the laptop was in motion. Hard to say. Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
