> Second, SMART is only saying its internal test is good. The errors are > related to data transfer, so that implicates the enclosure (bridge > chipset or electronics), the cable, or the controller interface. > Actually it could also be a flaky controller or RAM on the drive > itself too which I don't think get checked with SMART tests. Which test should I do from now on (on a weekly basis?) so as to prevent similar things from happening? -- 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
