Support and General Use > Audio Playback, Database and Playlists

Device shuts down while building database

(1/1)

usernamenumber:
Hello all.

I am running RockBox on my IAudio X5, and am having a problem with the database. Initially I told it to initialize the database and it worked in the background for several minutes and then suddenly shut down. This happens consistently. Sometimes I get a crash error (though unfortunately I can't recall what the text was) and sometimes the screen just goes blank.

I currently have the database set to auto-update, and now when I turn the device on, if I hold it to my ear I can clearly hear the drive whirring away, and the DB seems to be (very slowly) growing, but the decide still just becomes un-responsive after a few minutes.

The really odd thing is that when this happens there is no response to any buttons, the screen is black, and if I hold it to my ear the drive is not going, so as far as I can tell it is off, except that when I try to turn it on, first I have to hold the power trigger up for several seconds (longer, it seems, than it normally takes to shut down, let alone turn on), and then the device shuts off, not on.

At that point I can turn the device on, but this implies that there's something even weirder than a crash/shutdown going on. I think the device remains stable if I turn off auto-update, but I'd really like to be able to use the database.

If anyone can offer some suggestions I'd really appreciate it.

A couple of other things worth noting:
- The device has been plugged in when this happened and come back with the battery still full, so it's not a power thing.

- The reason I switched to Rockbox is that I'd hit the manufacturer's 10k file limit, so to be fair there are a lot of files being indexed.

Thanks!

nls:
Sounds pretty much like it crashes while scaning your files. If this still happens with a current build, I suggest scaning the disk for errors and if it comes back clean, trying to work out which file it crashes on and filing a bug report.
One way to work out which file is crashing the scan is doing i binary search or bisection, where the music library is split in half and rescanned, the half containnig the crashing file is split and scanned again etc.

Navigation

[0] Message Index