[SanDisk Sansa e280] Database-problems [official daily build: r13661-070618]

[w-k]

Hi ;-)

I have very hard Database-problems with my SanDisk Sansa e280.

The database never worked properly, equal if I selected "Load To Ram" and/or "Auto Update" and/or "Initialise now" and/or "Update Now" with "Directory  Cache" enabled or disabled. I nearly tried every combination.
Sometimes, after many many reboots, it's actualizing the database in parts (no, the actualisizing in the background couldn't ever take so long).
This means I get a correct structure with the "artists", but they are empty, maybe at 40% of all files. But it is possible for me to find, select and play these unshown files via the filebrowser [and no problem via original Sansa-Software].
[found this post http://forums.rockbox.org/index.php?topic=9538.0  but that changed absolutely nothing]

I tried "initialize now" today again (magically, it might have worked *lol*), but that got punished immediately: "*PANIC* Stkov dircache", and that's the last and only thing my player is telling me.  Freeze.

Copying the last official daily build "r13661-070618" to the rockbox-directory changed nothing, deleting the database-files in the rockbox-directory changed nothing.  

Does somebody has an idea?
Regards,
w-k

[Vortex]

Maybe deleting the whole .rockbox directory and then making a clean reinstall with the most recent build might help.

I also have problems with the database. The "Update Now" feature simply does not work. When I select the "Update Now" menu entry it says "Updating in Background" and I can tell that it is working on something, because you can hear electrical noise in the headphones.

However, newly added songs won't show up in the Database, no matter how long I wait. The worst thing is that after a reboot the database is corrupted. It only shows a few entries and large parts of the database are missing. Sometimes even rebuilding the database doesn't work unless I delete all the database files from the .rockbox folder.

However, as long as I'm not using the update feature I'm not having any problems with the database. It is somehow annoying though, because I have to re-initialize the whole database every time I load new songs on the player.

[w-k]

@ Vortex:
Very good idea! Deleting the rockbox-directory and putting in a new clean build worked, and, first time ever, I got a full working database. 8-)

[DECO1]

W-K

I too have had periodic problems with my Sandisk sansa e280. Every now and then I would load a "Bad" track to the database and this causes all sorts of problems, mainly ALL my music "dissappearing" from my album folder, and constant lockups. One way of fixing this is to firstly reset the player by holding down the menu button for the customary 12 seconds then if you have access, put your player in to MSC mode using SETTINGS  then USB MODE then choose MSC ( try connecting to computer and then disconnecting if you still have no access to the player menu)

Once connection is established, go and find the drive listed in My Computer and right click on the Icon. Choose Properties then Tools and you will see "Check Now"  Click on this and windows will check the drive for errors and fix them.  When you then restart the player it will rebuild the database. it may do this more than once to fully reset. Everything should now be ok.  The bad track will still be there so remove it  DO NOT PLAY IT AGAIN.    
I now always load only one album at a time, and then check all tracks will play. its not really great, but at least i will spot any bad tracks before I leave the house. If you load a lot of albums in one go without checking them, you may have loaded a few "bad tracks" and this will cause a lock up when you are out and about, and a lot of these problems require you to be connected to your computer to sort them.  The "Bad Track" issue is the only thing i have come across so far.

Hope this helps

[jurrie]

I installed the 070622 official Sansa build and also experienced database problems.  I'd previously been running an official build from June 9th.

After installing the new drop the database would not update correctly.  An explicit database init would eventually lead to "illegal instruction" errors around address 00000400 after "committing database step 1 of 8" (text wording is not exact, but similar).  I was ready to enter a bug report when I saw this thread.

As suggested, removing .rockbox and performing a fresh rockbox + fonts + themes install seems to have taken care of the problem.