>> 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/ Thanks, that's good information to have. I'll definitely do that next time. So, setting aside potential issues with the drive itself... Anything else you can recommend in regards to accessing the data in my image? If I can't repair/rebuild the whole file system I can live with that, but at the very least I have some specific files I'd like to salvage. I've got a backup setup in place, but the files in question are pretty big and recently modified, so the latest and greatest hadn't made it into the backup yet. Even if the metadata got garbled somehow, the actual data should still be buried in there somewhere, right? Are any forensic tools up to the task of finding it? Or is their operation so entwined with the details of the file system that they wouldn't do me any good? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
