Hello! I am new to this Forum, however not to ffs. A warm hello!
The question:
Are there any settings to tell ffs that it should simply skip a certian (damaged) file if it takes more than X minutes/seconds/hours to sync it? Like a threshold before timeout or so?
ffs version 11.29 x 86-64 on MB Pro mid 2012 with mac OS Catalina 10.15.7
The backgroud:
I've got a corrupt hdd (WD my Passport 1TB, Version 2011), I can access it normally via Finder and see whats on there, but if I try to copy things off it, it gives me terrible copy times (via Finder and also via ffs). Terrible times are more than an hour for less than one megabyte (it will finish on some point, but that can take up to 10 hours for tiny files...). But just in some cases, other folders can be copied in normal speed (couple of hundred megabytes in under a minute).
I used the HDD as a second backup, as my computer broke I needed to access my backup disk but that had overwritten already some of the old stuff (I know, I am stupid :( ). So I took my second backup disk which seems to be corrupt, too.
FirstAid on Disk Utility says its all ok.
Its all family pictures and old vidoes of holidays on that disk and I know exactly what I need to "recover" but with those times ffs tells me the coping takes more than 150days - if it gives me some time at all.
I have already filtered only for *jpg and a certain timespan but in total it would still be more than 8GB.
I am running:
ffs Version 11.29 x 86-64 on MB Pro mid 2012 with mac OS Catalina 10.15.7 (as I said, my other computer broke)
I have done a lot of syncing over that last days to my NAS with other WD my passport who all went fine. So it must be the HDD.
I hope some if you might have an answer or some alternative advices maybe?
If this question is answered already somewhere else, let me know. I tried google as well at the forum search but couldn't find what I was looking for - maybe I just typed the wrong words.
Thank you very much in advance!
Stype
Can I skip corrupt files
- Posts: 2
- Joined: 21 Dec 2022
-
- Posts: 4867
- Joined: 11 Jun 2019
Nothing built-in. To do this in the past, I just run a comparison and then do manual syncs in chucks from the results window. You can do that by highlighting a section and pushing ENTER. Once I hit a spot where it gets stuck, I just add it to the exclude filter so I can continue on
- Posts: 1202
- Joined: 8 May 2006
I don't know what FirstAid is, but don't believe it.FirstAid on Disk Utility says its all ok.
Your real life experience tells otherwise ;-).
I would think that drive is toast.
Recover from it what you can.
And even after that you'd have to treat anything recovered as suspect - until you can compare the recovered files against known good copies.
(That a file, media file in particular, may happen to "work", i.e., play, is not a particularly good indicator that it is "correct".)
There are utilities out there that can limit "retries".
-r:n retry reading n times on CRC or IO error (default 10, 0 means abort on error)
You might throw FFC at one of those "corrupt" ("hard to read") files, set the -r:n option on it & see if it thinks the file is corrupt, i.e., if it skips over that file. If it does, then that could be an indicator that with FFC the usage of the -r:n switch may be of benefit in a situation like yours.
- Posts: 2
- Joined: 21 Dec 2022
I am sure its toast!I would think that drive is toast.
Recover from it what you can.
And even after that you'd have to treat anything recovered as suspect - until you can compare the recovered files against known good copies.
I have copied folders manually and with ffs in small pieces to check if copied data is realable after the recover. That seems fine.
I have set the filter to "only *.jpg" so I get smallers amouts frist.
I have had it running now for just over 35 hours and it keeps going (already 26% done). There is no problem that crashed ffs or anything... its just talking 1-2 hours, than it copies a couple of hundred megabytes, gets stuck for another file for 1-3 hours, another few hundred megabytes and so on... I will just have it running for now but I thought or hoped there could be an option like "if file size <10mb and copytime reaches >180sec then skip file" or something like that. On the other hand I can see a lot of problems with such a function, too.
But for a recovery or partly broken harddisks that could be a good thing for the future :)
Thats a good idea one my current session has ended around christmas or so :)Nothing built-in. To do this in the past, I just run a comparison and then do manual syncs in chucks from the results window. You can do that by highlighting a section and pushing ENTER. Once I hit a spot where it gets stuck, I just add it to the exclude filter so I can continue on
