If the command terminate correctly, then the error was light enough for your disk to be able to read this file and reallocate the bad blocks. Upon rebooting your Mac, directly check the file containing bad blocks: dd if='/.DocumentRevisions-V100/.cs/ChunkStorage/0/0/0/9' of=/dev/null bs=1m If killing it nicely is failing, just crash your Mac. Let's say that this file name is: /.DocumentRevisions-V100/.cs/ChunkStorage/0/0/0/9Īt this point you may have the possibility to kill find quickly by hiting ctrl+ C. Write down this file name on a piece of paper! This file containing bad blocks will be the last name printed by find. This will mostly depend on the hard drive capacity to relocate the bad blocks found on its internal pool dedicated to this usual fix task. Upon hiting the first file containing bad blocks, this find will cause the kernel to log read error on /var/log/system.log, and it will either slow down or bring your system to a total halt.
#How to check for corrupted files mac full#
This heavy find command will print for any plain file its name (thus not reading it, but just its directory entry) and then continue making a full and fast read of all its data blocks. Run the following heavy and risky (in case you do have bad blocks outside of your filesystem structure) command (make sure the " of=/dev/null bs=1m \
Make a full backup of your disk with Time Machine or Carbon Copy Cloner If you are facing a healthy file system at the level of its structure and want to find files which have disk faulty blocks, here is how I would proceed: I don't want to write off the entire disk and start from scratch, as the drive seems otherwise healthy, so I'm looking for repair / diagnostic tools. Disk Utility isn't seeing the problem, and I don't know of any command line or third party tools which will do the job. 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. 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.
#How to check for corrupted files mac 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. 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.
0 kommentar(er)
