• Status Closed
  • Percent Complete
  • Task Type Bugs
  • Category Database
  • Assigned To No-one
  • Operating System Iriver H300 series
  • Severity Low
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by darksaboteur - 2007-07-11
Last edited by jdgordon - 2008-06-03

FS#7424 - Music Database Failure

Building the database on my iRiver H340 with current SVN (13852) build results in getting an error message of ‘Database is not ready’ ‘Initialize now’. No amount of rebooting or changing of database settings (Load to RAM, Auto Update) will fix the problem. I am unsure if this affects other players.

Closed by  jdgordon
2008-06-03 13:07
Reason for closing:  Out of Date
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

no response from user in 6 months… assume its fixed

My config files as requested on IRC

Tracked down the bug. It Was caused by certain non-music files on the player. I Will find out exactly which ones and report back

did you find out which files caused the problem? If you did we can try to have the bug actually fixed.

Any news, Nick?

Every now and then, I experience a similar malfunction with my Cowon X5 (SVN 15608). The database update (be it manual or automatic) gets stuck in a “blind loop” while parsing the metatags. No message, but the WPS HDD icon remains steady and one can clearly hear the HDD scratching over and over like mad, overheating and, of course, sucking the battery dry. Then, after 5 minutes or so, the OS usually freezes, requiring a reboot.

After some investigation, I too put the blame on some corrupted MP3 files (one was actually a MP2 file with a wrong extension, the others contained junk data). After removing the first one and cleaning the rest with foobar (header fixing + stream rebuilding), everything went back to normal… till the next time.

Actually, it seems to me that the parsing code is missing a basic mechanism to prevent such dead end. In case of error, it would simply ignore the file and move on to the next one. Then, once finished, it would display a message such as “Error reading files, a log is being created.” and create a log listing the problematic files.

PS: i checked the changelog of all the SVN posterior to the one I’m using and saw nothing of relevance to this problem. Yet, I will definitely test the lastest available built as soon as I have more time (and bad files at hand).

Could either one of you test this again please?


Available keyboard shortcuts


Task Details

Task Editing