On 04/20/2017 09:44 AM, Matthias Dahl wrote: > Hello Artur... > > So, the same thing happened again yesterday: The RAID10 was out of sync > due to an unclean shutdown and while Linux was at 70.8% of the resync, I > restarted to Win 10 with RST 15.2.0.1020 and it recognized the RAID as > clean without any visible/noticeable verification at all. > > I did a manual verification run in Win this time, just for the sake of > it, and it came up fine. > > Nevertheless, this really has me worried. Did you get / see my last mail > with the information you requested? > > By the way, kernel version was 4.10.8 with mdadm/mdmon 4.0. Hi Matthias, This really is strange, I'll try to ask someone from the Windows RST team about this. Unfortunately I don't have any knowledge about the Windows driver. I saw your earlier email and everything looked OK there. Does this happen only when you reboot to Windows? Have you ever rebooted during resync again to Linux and did resync resume as expected? Also, have you noticed what state did the BIOS show for the array when you rebooted? I'm asking because this might not be caused by Windows but maybe the BIOS/UEFI driver or Linux not updating the metadata properly at shutdown. Thanks, Artur -- 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
