Hi Bernd, Il 17-08-2017 15:18 Bernd Schubert ha scritto:
So for Gionatan the root cause was an instable power supply, but in my case there wasn't any power loss, there were just failed sata commands.
I tried many times to replicate the error by briefly disconnecting/reconnecting the SATA cable, but I had *no* corruption in this case. Sure, this was my experience, but a bad-behaving disk firmware can do all sort of bad things with the volatile cache, especially when renegotiating the host link.
I my case, I did *not* change the power supply, rather the SATA power cable: my theory is that, as the previous cable was shared between the two disks, somewhat low-voltage spiked find their ways and the second disk simply "rebooted". The new cable is dedicated to the SATA disk wich was previously failing.
What concern my is that, reading the linux-raid mailing list, many user have historycally reported high mismatch count in RAID1 arrays. These mismatches were generally discarded saying "RAID1 is prone to false positives" but, in my experience, these "false mismatches" are quite rare. What it means is that many users *are probably suffering* from my (and your) problem, without never realizing that...
Regards. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti@xxxxxxxxxx - info@xxxxxxxxxx GPG public key ID: FF5F32A8 -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
