Support and General Use > Hardware

RB 3.8 Sansa clip+ doesn't terminate generating database

<< < (2/5) > >>

Progweed:
I've updated the Flyspray task concerning this bug:
http://www.rockbox.org/tracker/task/11965

This is what I did:

I tried r29511 again, turned on metadata logging and found that this is the offending file:
http://www.mediafire.com/?76ei0xwou83duel

Other things I noticed:
* foobar's integrity checker does not show any warnings
* I can't enable dircache any longer, it's always turned off after a reset.

aargl:
I've got a recent 2Gb clip+ and went on the same problem.
After spending hours, updating, reinstalling, moving music and so on, I reinstalled the OF and RB 3.8, and initialized the Database from the menu.
It was still buggy and I decided to let it that way, using the File menu instead of the Database menu and switched it off.
Surprisingly, now, a few hours later, I started it and everything works fine! Is it possible that it only needs a loooooooong time to update the database and did it while switched off?  ???
The only issue still present is an <Untagged> artist and inside it an <Untagged> album: when I play the track in it, there's a digital flushing sound and then the display goes incoherent.

It's interresting to notice that when I loaded it back with music, I first tried with a single album and everything was ok, so the bug probably deals with the quantity of space occupied.

Perhapps it has nothing to do with it but before updating to 3.8 yesterday, I cancelled the preloaded songs and folders from within the Clip (as I'm on Mac).
Post Merge: March 06, 2011, 07:24:52 PMI have to mention that the last build I installed was r29533, it probably sorted out something.
I've just installed r29534 and there's still the "Untagged" thing...

lwizard:
I can confirm that till I put one album or two, it was right. When I filled internal memory with albums, the bug appear.
Database generation hang at a very hi-degree of completion.. when almost all files are done..
Anyway now I'm back to 3.7.1 and everything is fine.

Another bug is that if you set as default browsing directory a location on external memory and than you power on rockbox without external memory, pressing the central button does nothing and you can't access the browser. You have to put back in the ext memory

aargl:
It might help someone, maybe in a future bug  ;): I used a utility to visualize the content of the .rockbox directory and erased all the database_*.tcd files (not the database.ignore file).
It's more likely that the last build I installed cured the problem, but just in case... :)

njd:
I got the same thing after I updated my Clip+ from 3.7.1 to 3.8 but now the FAT32 partition is unreadable in Windows.

I updated the Clip+ to 3.8 using RockboxUtility 1.2.8. On restarting, I accepted the prompt to initialize the database.
The database initialization got stuck after about 500 files, though still displaying the "disk write" (lightning) icon.

I guessed the update freeze was caused by lack of free space (about 100MB), and set about deleting some music folders, but everything was moving very slowly, so I canceled the deletions.

The disk write icon was displayed permanently, and I couldn't see how to cancel the db update, so I shut down the device, restarted, declined the update prompt, deleted about 1GB, and was able to complete the db initialization via the menus.

Now I can start up in RB3.8 or in the original firmware, and play everything just fine, but a USB connection to Windows XP (via Sansa f/w, MSC) either is not recognized (WinXP doesn't display the drive icons) or is recognized, but Windows reports the drive as "Not ready" or unreadable.

It seems the internal memory's FAT filesystem is corrupted in some way which doesn't affect normal operation, but it bothers Windows. Clip+ works fine, but I can't update the internal memory from Windows.

Anyone else seen this? And got out of it?

I've considered refomatting using the Sansa OF, but I'm not convinced it'll fix things; the Clip+ still kinda works at the moment, but if I wipe all my music/audiobooks/etc and still can't use USB, then I'll have a (nearly) useless player.

(I have a μSD card, but RB can't read it)

*** Update ***
Yes, I have tried another USB cable ( I have three )
Yes, I have tried other USB ports.

Navigation

[0] Message Index

[#] Next page

[*] Previous page