> There is also a SMART error log reporting mechanism. The disks have > ability to report the last 5 commands that errored on each disk, which > includes timestamp, op code, input parameters and reason for error. I pulled the logs from the drives. Four showed no errors whatsoever, and three showed 1, 2, and 3 errors, respectively. The others ranged from 408 to 1871. I then triggered a halt with a mv command, and checked the logs again. The values all remain the same, with no new errors reported whatsoever. > This runs instantly, and it is possible that just having these last 5 > errors will tell you exactly what problem is. The errors are also I presume a sector remapping would be caught by the log file, yes? If so, bad sector mapping is pretty much completely eliminated as a cause for this issue. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
