TagCashe Question

[LanceUppercut]

So,  I've been using Rockbox for about 2 weeks now, and I love it for the most part!  but, For some reason, the last 2 days or so, I've had TagCashe problems.  It seems like sometimes it'll just stop working, saying TagCashe not ready. 

If I try to update, it freezes, saying Runtime Error and a bunch of numbers.  So, I formated , and reinstalled, and it worked a few times, then the same thing. 

When I look in the .rockbox folder, there is a bunch of random files, named a bunch of ascii symbols, that can't be deleted.  Chkdsk does nothing.  Any ideas?  Thanks!

[Llorean]

I will tell you right now that I am 100% sure it has never once said to you "TagCashe not ready"

Anyway, a couple questions. The first being: What build were you running when this happened?

The second being: By "Chkdisk does nothing" what exactly do you mean? It scans and comes up with no errors, or it fails to scan?

[LanceUppercut]

I'm using CVS-060805

Chkdsk finds a bunch of errors, converts them to files, and I still can't delete the garbled data.  Usually, the files I can't delete are about 2 GB in size.

And yes, It does say TagCashe not ready, or something to that effect.  It says that when I reboot the Ipod, and try to access anything in tag cashe.  i.e. when I attempt to browse by Artist, or album, or whatever.

[Llorean]

You missed the point. It doesn't say "TagCashe not ready" it says "TagCache not ready". I was trying to subtly correct your spelling by pointing out that the proper spelling of the word has clearly been shown to you at a minimum once, and possibly several more times than that.

Anyway, that's not "chkdisk does nothing" that's "My drive has problems beyond the abilities of chkdisk to fix". Have you tried running a surface scan? I'm not even sure if that's an option with chkdisk...

[LanceUppercut]

Oh, Sorry about the spelling, i've never been to good with that, Although, I didn't think that this was a spelling bee.

Anyway,  I don't think that chkdsk doesn't offer a surface scan.  But since then I've formated the drive completely.  Any Truncated files should have been wiped out with that.  I doubt that there's any physical problems with the disk, as it's pretty new.  And besides that, it would be pretty wierd if damaged clusters only got written to with tag cache. 

[Llorean]

It's hardly a spelling be, but really, when the software is telling you how it's spelled in the error message you clearly have been shown how to spell it. Plus, misspelled words can be read differently by text-readers being used by the blind.

Did you have evidence that *only* TagCache causes this problem, or is it merely that it showed up while using TagCache, and that seems the best way to bring it out?

[Yotto]

I doubt that there's any physical problems with the disk, as it's pretty new.  And besides that, it would be pretty wierd if damaged clusters only got written to with tag cache.

You'd be surprised. FAT (The File system) absolutely LOVES to write files in the same spot on the disk.  If you delete a file and recreate it, it will likely get put on the same bad sector.  I've seen it hundreds of times (Yes, hundreds, I used to work in a nationwide helpdesk). And new drives have bad sectors more frequently than you'd think.  I'm not saying /yours/ has a bad sector, just that I'm not all that surprised, and it fits the profile.

[LanceUppercut]

Fair enough.  Spelling point well taken.

Hmmm...Interesting.  Maybe I should find something to do a surface scan?  Tag Cache is the only aspect that seems to act funny.  Also, the last 2 times it's happened (yesterday and today) all my settings reset.  No Wps, small font, that kind of thing.  And i'm not booting up with the hold switch on. 

I'll do a surface scan and report back.  Thanks for the help guys!