The semaphore timeout period has expired (ERROR_SEM_TIMEOUT)

[Ulborn]

I'm getting this almost every time I scan. FFS scans a bunch of files(Over 200k) then it stops for over 10 minutes and gives me the error "The semaphore timeout period has expired."

Anyone know what could be causing this?
The Drives are working fine. I can manually copy LARGE (Over 2TB) amounts of data with no issues. Copy speeds are 100Mbps over the network when FFS works. I can also copy files to a different folder on the disk that's supposed to be scanning without any jitters or slowdowns. (~150MBps)
Canceling the process and restarting it does not fix the issue, it just does the same thing on a different file, same after rebooting both systems.

[therube]

I can manually copy LARGE (Over 2TB) amounts of data with no issues.

You've verified that the copied data is accurate (by hash check or otherwise)?
You've run CHKDSK (or similar) on the disk?


("Wondershare" itself aside) some things to ponder, https://recoverit.wondershare.com/computer-problems/semaphore-timeout-period-has-expired-error.html


What OS?
Tell us about your devices.
Is it only with the >2TB that you see the issue?

every time I scan

So FFS is causing this to happen on the scan, not necessarily on the copy.

[Ulborn]

Processor    : AMD Ryzen Threadripper 2950X 16-Core Processor    3.50 GHz
Installed RAM : 32.0 GB (31.9 GB usable)
Windows 11 Pro
System type : 64-bit operating system, x64-based processor
Graphics : Nvidia GeForce 1070Ti
Internal Storage : 3 - 3TB M2 Drives, 10TB Physical HDD
Ext Storage : 3 - 4TB USB 3 drives, 1 - 16TB USB 3 HDD


FFS is having scanning issues with the 16TB drive, but it passes all CHKDSK and WD Scans. The cable and drive are brand new.

Eventually FFS does scan the drive, but it takes about 40+ minutes WHEN it runs into an issue, if not it scans the drive in ~5 min (for 10TB of data).

The other Ext disks are not powered on while I'm using FFS on this drive as they are backup drives. They are only on while I'm backing up data to/from them.

[xCSxXenon]

If this is the only drive you are experiencing this issue with, there may be an issue with the drive's controller board or its firmware. Make sure to check for firmware updates using whatever manufacturer's tool is for your drive. That semaphore error is really just a catch-all for a device not responding to a request properly, typically hardware issues cause it. I had a RAID machine in my store a while ago where drives were dropping out randomly and no amount of rebuilding or swapping cables or anything worked. When trying to access them directly, we got that semaphore error on one drive, which was the only drive on an old firmware revision. Updated to the newest/matching version and everything was perfect after that

[Zenju]

What is the full error message?


ERROR_SEM_TIMEOUT is probably from STATUS_IO_TIMEOUT at NT kernel level: https://devblogs.microsoft.com/oldnewthing/20140717-00/?p=483