Database not building on Gigabeat x30

[piglett]

I did a software update over the weekend and since then when I go to the database I get a message saying Database is not ready initialize now, when I say yes, it says building database, gets to 7179 found, it says comitting database & counts up from 1/9 to 9/9 & then stays on the building database screen and then stops. There's a message saying left to return. If I press left I go back to main menu but every time i go to the database I get the same message, ie building dtabase...7179 found, (left to return)

When I restart the machine and go back to the database, it starts the whole initialize database routine again

Not sure how to resolve this.

Any help greatly appreciated

[karashata]

Try removing the existing database files from the .rockbox folder (will have .tcd extension and have database in the filename), then reinitializing the database. It could be that the files have been corrupted in some way.

[vocrobot]

I have this on my iPod video whenever I update. When I try to update it doesn't work and I have to delete all the database files and start again so it aint just the Gigabeat that's affected.

[piglett]

Thanks for the advice.

I've tried removing the .tcd files dut i'm still getting exactly the same issue when I initialise the database though this time it's getting to 7188 files found instead of 7179

 

[vocrobot]

It sounds just like mine. It gets to a certain number of files but this won't clear off the screen and when I switch off then on again the database gets as far as 4/9 then stops. The only way to fix it is then remove all the database files friom with rockbox then start again which is a pain.

[piglett]

i've deleted all the database.tcd files 3 times now and it makes no difference. It is just not building the database, i've noticed that the "building database" countdown only gets to 3/9 before it disappears

Looking on the forums it clearly isn't just my make of player that this is affecting!

I;ve also tried to reinstall rockbox and getting no joy there either

[max242]

Hi all,

Exactly the same thing over here.  Running Rockbox on my Sansa Fuze 1.0. 

The way how i 'solve' the issue, is to go back to a previous version of the daily build, which i always keep lying around.  For me, the latest one i got which does not have this particular issue, is the 25255 build, the other builds i kept is 25371 and 25438, and both of these builds do have the issue.

Since the daily build service has been set up, i don't compile my own builds anymore. Maybe somebody else is brave enough to try to pinpoint when this particular issue showed up, so that we (rockbox users _and_ devs) have a better understanding what happened in the code, and real coders (not me, i'm not a coder) can try to write a patch to resolve this particular issue.

Maybe one of the forum admins can move/re-title the whole thread, as this seems to be not model specific, but happens on different kinds of rockbox players.

Hope this helps solving the issue,

Happy rockboxing!

Marc

[Chronon]

Hi.  I can't reproduce this with r25652 on an F40.  I'm initializing again on r25683 as I write this.

Edit: That worked fine too (also on F40).  I can try with other players too but it seems not to be an intrinsic problem with the database code since it works on at least one player using a current build.  Can those with trouble see if the current build can properly initialize the database?  If not, then it seems like the most obvious factor to investigate is the files that are being scanned.  Building the database has been known to fail under certain situations.  It would be good to know if any subset of the files will build.  You can try a binary search to try to isolate tracks that prevent the database from being built.