Problem with corrupt font filenames.

[wombat]

Hi all,
I downloaded build R122210-070205 for iaudio x5(l) and copied across, as well as the fonts of the same date. Rockbox installed properly and is working nicely. I am particularly excited by the ability to record wav's at 88.2 kHz from vinyl - fantastic sound.
However the fonts copied across with garbled file names and sizes totalling 300Gb (!) - presumably a faulty FAT? I repeated the next day and now have  working fonts. But I was unable to remove the first fonts directory - it had to be renamed.

The faulty fonts directory is becoming a real nuisance, since my linux (Ubuntu & Suse) boxes are labelling the Iaudio as Read-Only so that I cannot move files to it.

Nor can I remove the folder, even using sudo rm -rf gives:
 
rm: cannot lstat `fonts_old/¢>?¥?\023\022Z.)\t?': Input/output error

typical messages from from dmesg | tail upon trying to access the folder on the iaudio gives:

[1736912.069888] FAT: Filesystem panic (dev sdd1)
[1736912.069897]     invalid access to FAT (entry 0x03571892)

and trying to write to the iaudio:

[1744546.040120]  22:0:0:0: rejecting I/O to dead device
[1744546.040124] FAT: Directory bread(block 28242388) failed

and attempting to cut or delete from the iaudio:
[1735845.983961] attempt to access beyond end of device
[1735845.983964] sdd1: rw=0, want=24821175518, limit=39053952


I've also tried Windoze to remove it - again no luck ("Cannot delete: Filename, directory name or volume label syntax is incorrect").

Can someone please advise me on how to be rid of this pesky directory, without having to reformat the entire iaudio hard drive?

many thanks
Karl
(please move this message if on the wrong forum.)

[bluebrother]

have you ran chkdsk /f from windows on the drive?

[Spug]

Or fsck in Linux, if you use Ubuntu/Suse primarily.

[bluebrother]

While I developed a FAT driver some months ago I noticed that linux is much more forgiving with specification breaks in a FAT filesystem. That said, chkdsk usually finds (and can correct) more errors on a FAT volume.
(I usually work using Linux, but for a good check of the drive I would recommend using a windows box and running chkdsk from the command line as that gave the best results for me)

[roolku]

I also had good success deleting files with illegal file names from within rockbox. But I suggest  chkdsk first in case it is not just the filenames, but the fat is corrupted as well.

[Lear]

While I developed a FAT driver some months ago I noticed that linux is much more forgiving with specification breaks in a FAT filesystem. That said, chkdsk usually finds (and can correct) more errors on a FAT volume.

He, my experience is the opposite: I had a file on my DAP "corrupted" by an old Rockbox bug (causing duplicate short filename entries, IIRC). If I tried to delete it (or access it in certain ways), Windows would immediately bluescreen. Chkdsk (at least the GUI version) found nothing. dosfsck found and fixed the problem though.

[wombat]

Thanks to you all for these very helpful comments.
I used chkdsk [drive:] /f and it fixed the problem. The corrupt directory was converted to a file that could be readily deleted, and it fixed some other problems too. Now I can keep recording vinyl  
Thanks to all the Rockbox gang - it's a superb project!
.