Fake problems with external hard drive.

[mzee]

I have a 1TB USB hard drive which I use on Linux & Windows 10. Every time I plug it in to W10 it notifies me that it needs to be scanned. If I let it do a scan it can find nothing wrong. Linux never has any problem with it. I get the same with any USB stick which has been used on Linux. What is causing this waste of time?

[wainuitech]

Thats often caused by not unmounting / Disconnecting drives correctly. Have a read https://www.howtogeek.com/184640/ask...ould-i-let-it/ as well as the following article: https://www.diskpart.com/articles/th...his-drive.html

Seen happen countless times people just pull out a Drive and next thing you know all the data is corrupted on that drive.

This may not the the exact way to say this but windows and linux mount drives differently. Had many times plug in a USB drive into a linux OS, an Icon pops up on the desktop, and when clicking it comes up with a error message saying it cant mount the drive.

One of my workshop PC's does that always, and every time without fail if ANY USB drive is plugged into the Linux OS, and even unmounted correctly the next time it plugs into any windows OS it pops up the message to scan.

[wainuitech]

Wouldn't say those were fake. Just had the same thing, a USB drive was in a Linux OS, unmounted it correctly, then put the drive in One of the Windows 10 OS, up came a scan etc, said it was OK, but when looking at the actual Log file it obviously wasn't. unmounted the drive then Put the drive into another W10 OS - No problems.

The log showing corruption caused by Linux.

Checking file system on F:
Volume label is USB.

Stage 1: Examining basic file system structure ...
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x9cd for possibly 0x306 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x2b is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x2B.
256 file records processed. File verification completed.
Phase duration (File record verification): 20.14 milliseconds.
0 large file records processed. Phase duration (Orphan file record recovery): 2.34 milliseconds.
0 bad file records processed. Phase duration (Bad file record checking): 1.90 milliseconds.

[Agent_24]

Sounds like your Linux may have some outdated & buggy program etc that's not actually unmounting or it's doing it improperly, or maybe the drive is waiting to flush its write cache, but Linux is not telling you this or is ignoring it due to a bug etc.

Triggering a Windows chkdsk shouldn't normally happen.