"readdirent" error for a folder on an external SSD.

[cecoates]

This error started about 2 months ago, but I’ve been out of town so mostly ignoring it.

I have a folder named “Movies” that syncs to my QNAP NAS.

However, on my desktop, SyncThing always displays the following error:

"Filesystem Watcher Errors

For the following folders an error occurred while starting to watch for changes. It will be retried every minute, so the errors might go away soon. If they persist, try to fix the underlying issue and ask for help if you can’t. Support

Movies readdirent: input/output error"

Then, under the entry for that folder, SyncThing also says this under “Rescans”:

"1h Failed to setup, retrying

Periodic scanning at given interval and failed setting up watching for changes, retrying every 1m: readdirent: input/output error "

It only seems to affect that one folder, which is on that one external SSD, a Crucial MX500 2TB disk.

As far as I can tell, the folder does still sync correctly, and changes are synced to the destination folder on my QNAP NAS as expected.

But overall I’m still puzzled about that error and haven’t been able to find out more about it. Has anyone else experienced something similar before?

[calmh (Jakob Borg)]

readdirent: input/output error

This should mean roughly “the disk is bad”. I’d run some fsck / chkdsk / similar thing on it.

[Catfriend1]

Uh oh, this drive seems to have a bad reputation, see https://www.amazon.de/gp/aw/reviews/B078C515QL/ref=cm_cr_getr_mb_paging_btm_3?ie=UTF8&filterByStar=one_star&pageNumber=3 where two out of three units fail within the first two months according to user reviews.

[cecoates]

Thanks for the feedback, y’all. Following the advice here I ran all the SMART tests via Gnome-Disks, and so far everything came back as “OK”.

Waiting on:

sudo smartctl -t long -a /dev/sda

To see what that yields, but:

sudo smartctl -t short -a /dev/sda

Came back as “completed without error” too.

That’s what’s odd, is the drive seems to be functioning fine, and Syncthing seems to be syncing it fine, I just can’t figure out why the one error persists.

Are there any better SSD tests I should run, or other items I could check for?

[cecoates]

So far all the tests have come back as OK/no errors detected. A bit befuddled.

[Catfriend1]

If I were in unclear situation with open doubts I’d create md5 hash files from the large files on both sides and compare them with a tool if bit rot had taken place or not.