I followed the same idea at the 1st instance with the external harddrive at the RaspberryPi (that's my case: "slow network drive"). Filesystem-repair on the external harddrive was successfull. I tested it afterwards as ok and it is now in an error-free and daily use as backup drive for another ~10days. Which means, I can excluded an issue at the storage device.
I bought some
new USB3.0 flash drives (3 pieces) to reproduce the case under the assumption of a "slow network connection" as root cause (this is the case I named "slow USB-drive"):
• I attached the flash drive to another Win10 maschine (an old 32bit ThinkPad-Laptop with USB2.0 only) and made it available throught network
• I ran into the same issue of a broken filesystem, but impossible to repair on both Win+Linux.
So what about the missing 1% in xCSxXenon's answer?
I would love to here on opinion on that before trying to reproduce with logfiles. That's time consuming because of the considerd large files and I'm risking another damaged flash drive. Please get me right, I would do that, if it is of help to prove reasonable ideas on the 1%.
Additional notes to avoid answers on other possible root causes I already considered:
• My "network" is wired with Gigabit wires and Switch.
• All considered devices (Windows Maschines and the RaspberryPI) are equipped with Gigabit network.
• OS-systems are all up-to-date and free of virus or malware.
• No other devices active in the network at occurance of the issue in both cases.
• No other processes active on both maschines in the case "slow USB-drive".
