ERROR_INVALID_NAME: The filename, directory name, or volume label syntax is incorrect. [CopyFileEx]

[Cojeff]

Hi,
I've been trying to figure out what the issue is when this pops up syncing files. The volume is NTFS on a RAID. OS is Windows 10. Updated to the latest version of FreeFileSync. I have checked the files and they seem to be okay, I don't have any issues playing them back and Plex doesn't seem to have any issues with them as well.

[xCSxXenon]

What happens if you disable "fail-safe copying" in Tools --> Options ?

[Cojeff]

Same error message.

[xCSxXenon]

What are you syncing from and to?

[Cojeff]

A 8TB SATA drive formatted in NTFS to a 8TB RAID 5 formatted in NTFS and is setup using Storage Spaces. I have copied 3.5TB of video files to the RAID and it's just the ones listed in the log that have an issue.

[therube]

(For reference, since I didn't know:
https://www.partitionwizard.com/resizepartition/windows-storage-spaces.html
https://techgenix.com/windows-10-storage-spaces/)

So your 8TB is RAID 5, & on top of that you are using Storage Spaces there also?
Which SS type are you using (simple)?

And if if fact your 8TB is RAID 5, may I ask why you are also using SS?

Odd (I'd think) that in some cases the error is with "filename" to "filename" & other times it is ".DS_Store" to "~guid.ffs_tmp"?

[Cojeff]

There are two 8TB volumes. Storage Spaces is setup as parity using (3) 4TB drives giving 8TB of storage. The other 8TB is just a regular spinning hard drive.

When mirror the data, it copies it over correctly from what I see but it then I think it's trying to rename the copied file and something is going wrong. Unfortunately it doesn't provide anymore messages on the error. Windows System logs don't show anything.

[Cojeff]

Screenshot 2022-11-28 103245.png (50.3 KiB) Viewed 1536 times

Looks like it is an OS issue. How bizarre.

[xCSxXenon]

That's interesting... I wonder if there is a weird character in the names

[Cojeff]

I have no idea. In all my years of working with NT and NTFS, I have never seen anything like this. I tried copying it off the computer using filesharing and it gave up there as well. I shortened the file name, same issue. I have it playing in VLC to see if maybe it's corrupt somewhere.

[therube]

I have it playing in VLC to see if maybe it's corrupt somewhere.

I wonder if it might not be an actual disk issue? CHKDSK.

Media players are generally resilient, & may just skip over (glitch over) "bad spots" in a corrupted file.
If you have other copies of the file, you could check hashes & see if they compare.


This is not an end-all (by far), but I'll use something like this, at times, to check a media file for "problems":

:: ffmpeg check to see if a video is good
:: SjB
:: 05/23/2019


@echo off
echo.
echo CHECKING VIDEO FOR ERRORS:
echo %1
if [%2] NEQ [] echo [Output to screen only.]
echo.
pause
echo.

if [%2] NEQ [] goto 2screenonly



@echo on
ffmpeg  -i "%~1"       -v error -f null -   2>&1  | tee  "%~1_ERROR.log"
echo    DONE  >>  "%~1_ERROR.log"

pause
exit



:2screenonly
@echo on
ffmpeg  -i "%~1"       -v error -f null -   2>&1
echo    DONE

pause
:exit
:do NOT (specifically) exit, rather just do "nothing"
:such that the command prompt window simply "exits" rather then closes


If you get only "DONE" (or output to a file that only contains the word "DONE"), then ffmpeg found no issues with the file (for as far as this particular check goes).