Sync/Mirror Error: Cannot read file attributes. Bad sectors?

[jodee]

Hi.

I'm using FFS on Linux and was able to successfully mirror one pair of drives. However, when I try to sync another pair of drives, I get the following error for the destination:

"Cannot create directory... Cannot read file attributes of... ENOENT: No such file or directory [lstat]."

I initially thought it had something to do with the folder permissions or with the destination drive being fully encrypted, but the first pair of drives (I was able to sync) has the exact same setup. After launching Disks utility, I see that the assessment says: "Disk is OK, 24 bad sectors."

Is 24 bad sectors really a lot and is that the reason why I'm getting the FreeFileSync error? By the way, I was able to get around this issue by manually copy-pasting the files into the destination, so I know the disk is fine in that sense. Other than with FFS, I have no problems reading and [manually] writing to it.

Is there anything else I can try? Should I try wiping and encrypting it again, or do I need to replace it with a new one?

Thanks for any help.

[xCSxXenon]

I would check the SMART health using something like GSmartControl, to confirm. I use Windows, but I've used it in Parted Magic before. I can guarantee there's a way to view it either way, and if you run Linux, I'm sure you can figure it out. I would consider any number of bad sectors to be reason for replacement. Typically, there are more bad sectors than what has been reported yet. It may or may not be directly related to this issue with FFS, but drives don't ever get better ¯\_(ツ)_/¯

[jodee]

I would check the SMART health using something like GSmartControl, to confirm. I use Windows, but I've used it in Parted Magic before. I can guarantee there's a way to view it either way, and if you run Linux, I'm sure you can figure it out. I would consider any number of bad sectors to be reason for replacement. Typically, there are more bad sectors than what has been reported yet. It may or may not be directly related to this issue with FFS, but drives don't ever get better ¯\_(ツ)_/¯

Hi. Thanks for the response and pointing to GSmartControl. Never used it before but I ran Short Self-Test on the drive and result said "Completed with read failure." Just to compare, I ran the same test on the other drives and they all came out OK. So I guess this confirms the drive needs to be replaced, which is too bad since it's less than 2 years old :(

[xCSxXenon]

Might be under warranty then, look into it

[jodee]

Might be under warranty then, look into it

Thanks again. Will do.