![check for corrupted files on another hdd check for corrupted files on another hdd](https://www.thewindowsclub.com/wp-content/uploads/2017/08/Recuva-600x466.png)
My question is really how I go about marking those broken files as properly broken and fixing or purging them, so that a clone of the disk will succeed and not get hung up on files / blocks it can't access.
![check for corrupted files on another hdd check for corrupted files on another hdd](https://www.nucleustechnologies.com/blog/wp-content/uploads/2009/09/How-to-backup-and-restore-files-from-corrupt-drive-1200x900.jpg)
I'm assuming the worst case, and that most likely I'll have to get a slightly larger HDD and clone the existing drive to avoid having to rebuild the system. At this point I don't know if it's really the drive dying, just some bad sectors due to the drive being moved while writing, or some other minor corruption that can be worked around. While it would be nice to retrieve the data, I don't mind reinstalling or going to backups. As far as I can tell, no system files or crucial data are affected. There are maybe a hundred or more corrupted files, but still a very small fraction of the drive. No SMART errors reported, and while there were some permissions errors, they weren't with the files iDefrag is complaining about, and Disk Utility claims to have fixed them without complaint.
#CHECK FOR CORRUPTED FILES ON ANOTHER HDD CODE#
Output of cp is:Ĭp: unity_nophysx.nexe: Input/output errorĮrror code 5 is 'access denied' as far as I'm aware, but the defrag process is running as administrator and running cp using sudo on the suspect file makes no difference.ĭisk Utility, fsck and the Apple Hardware Test all claim the disk is fine. Picking one at random and trying to copy the file to another location in the shell also reports an error, which makes me think the problem is real and with the disk / FS.
![check for corrupted files on another hdd check for corrupted files on another hdd](https://www.wintips.org/wp-content/uploads/2018/03/image-19.png)
IDefrag reports a POSIX error code of 5 when accessing the files. It's still running reasonably well, but in running a defragment pass on it, I've identified that there are a bunch of files which are refusing to be moved by the defragmenter (iDefrag). Its sole HDD is a 750GB drive, formatted with Bootcamp. I have a late 2011 Macbook Pro, running Mavericks 10.9.2.