Reply to thread

Message

<blockquote data-quote="MacInWin" data-source="post: 1631494">1. Might be. If it copies over, it's probably ok. No test I know, just use the copied data and see how it looks to you. If you want to try to fix it, open Disk Utility and run Verify against the drive. If it can fix it, it will offer to do so.2. Probably not.3. L+F files are the rough equivalent of what CHKDSK files are in Windows; files or fragments of files that the directory information was incomplete or inaccurate. OS X gathers them into L+F for the user to decide.4. Again, only by inspection of the files. Most are probably temporary work files that were in some sort of scratch storage when you force ejected the drive (That is, BTW, the source of all of the troubles. Don't do that.)5. Well, if you note the time of the files and want to look the logs in Console, you can then look at the same time to see if anything was going on, but I suspect the problem was really the force eject of the drive. That's brutal, particularly if the drive was in the process of writing at the time you did that.6. You can run Disk Utility Verify and/or Onxy on the drive to test it. But if it partitions and formats, it's probably ok.7. Use it minimally. The more you mess with it, the more writes to it and the potential for overwriting something you want.</blockquote>

[QUOTE="MacInWin, post: 1631494"] 1. Might be. If it copies over, it's probably ok. No test I know, just use the copied data and see how it looks to you. If you want to try to fix it, open Disk Utility and run Verify against the drive. If it can fix it, it will offer to do so. 2. Probably not. 3. L+F files are the rough equivalent of what CHKDSK files are in Windows; files or fragments of files that the directory information was incomplete or inaccurate. OS X gathers them into L+F for the user to decide. 4. Again, only by inspection of the files. Most are probably temporary work files that were in some sort of scratch storage when you force ejected the drive (That is, BTW, the source of all of the troubles. Don't do that.) 5. Well, if you note the time of the files and want to look the logs in Console, you can then look at the same time to see if anything was going on, but I suspect the problem was really the force eject of the drive. That's brutal, particularly if the drive was in the process of writing at the time you did that. 6. You can run Disk Utility Verify and/or Onxy on the drive to test it. But if it partitions and formats, it's probably ok. 7. Use it minimally. The more you mess with it, the more writes to it and the potential for overwriting something you want. [/QUOTE]

Verification

Name this item. 🍎