+ecanderson Posted August 22, 2016 Share Posted August 22, 2016 Device has corrupted GPX\Archive folder. Windows claims content 86.6GB (obviously impossible). Folders and files within have corrupted names. GPX\Archive folder is Read-Only. Any attempt to reset that flag (in order to delete the folder) shows Read-Only again when returning to folder properties. Master reset doesn't touch this folder (nor my valid files in the GPX folder, like geocaches.gpx -- always thought it would). Suggestions? Quote Link to comment
+GeoTrekker26 Posted August 22, 2016 Share Posted August 22, 2016 Get a live Linux distribution and delete the file from inside Linux; there are several flavors available. I would suggest a backup of as much as you can before you do the delete and again after but before you do anything else. Good luck. Quote Link to comment
+Viajero Perdido Posted August 22, 2016 Share Posted August 22, 2016 Or take a chance with the Windows disk-repair utility, scandisk I think it's called. (What's a Linux guy like me doing recommending a Windows utility?!?) Quote Link to comment
+ecanderson Posted August 23, 2016 Author Share Posted August 23, 2016 Or take a chance with the Windows disk-repair utility, scandisk I think it's called. (What's a Linux guy like me doing recommending a Windows utility?!?) Creating a solution, I guess! I was hesitant to run Scandisk against something with a structure so messy that it reported absurd usage figures, but after a full backup of good content, voila. Errant folder rendered into a 16K file that can be deleted. FOUND.000 created as read-only folder in device root of only 64K. Flag easily reset and 'sticks'. Both deleted, and I'm a happy camper. Quote Link to comment
+Viajero Perdido Posted August 23, 2016 Share Posted August 23, 2016 Whew! I figured, since Windows invented that file format (FAT), it should be able to fix it too. Glad it worked. Quote Link to comment
+ecanderson Posted August 23, 2016 Author Share Posted August 23, 2016 Likewise. The device was functional, but few things bother me more than operating any piece of gear that has a known corrupt file system. Knowing what a FAT directory looks like and how space is allocated and deallocated within that structure, it could have been a ticking time bomb. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.