After database refresh, e200 is dead

[barryg]

I updated my Rockbox version to 3.9 last night and everything went smoothly. I subsequently uploaded several albums. This morning, I selected database on the menu and was prompted to refresh the database and I said "yes". It completed the operation (9/9) but then the screen went black and the Sansa won't respond to the power button now.

Any advice appreciated!
Post Merge: June 29, 2011, 08:13:09 AMI found info on doing a reset by holding power button for 20 seconds and it now powers up!

(sorry for not searching harder sooner)

[sideral]

Glad that it worked out for you. Still, the crash you've seen is worrisome. May I ask a few questions on the exact circumstances, and maybe even to try to reproduce it?

From which version of Rockbox have you upgraded?

Do you have an old /.rockbox/database_changelog.txt file lying around?

If you don't mind, could you please try initializing the database again (database settings → Initialize Now)?

If the crash happens again, could you try the same procedure again after renaming the database_changelog.txt file?  (Please don't remove it, it might be useful for debugging.)

[barryg]

There's no database_changelog.txt file to be found

Version is r30094-110628

I just uploaded a ton of stuff in preparation for a trip I'm just about to leave on.  The database updated fine.  If I see an issue with the initialize, I'll report back.

[[Saint]]

There's no database_changelog.txt file to be found

database_changelog.txt is created manually by going to the Menu option:

Settings - General Settings - Database - Export Modifications

It isn't generated automatically by any means or process that I am personally aware of, so that confused me a little.



[St.]

[sideral]

Version is r30094-110628

I didn't mean to ask which version you were running, assuming it was Rockbox 3.9 as you first said, but this is interesting nonetheless:
 
This is not Rockbox 3.9, but a current build. You may have run into a dircache instability in the post-3.9 branch. We generally do not support unreleased builds here, but you're welcome to file a bug report in the tracker. See also FS#12175 [1].

Which version have you been upgrading from (i.e., which version did you run prior to the upgrade)?

[1] http://www.rockbox.org/tracker/task/12175

[sideral]

database_changelog.txt is created manually by going to the Menu option: [...]
It isn't generated automatically by any means or process that I am personally aware of, so that confused me a little.

I know. I was just speculating that the automated import of an old database_changelog.txt during the (necessary) recreation of the database may have been causing the crash.

[[Saint]]

I'd speculate that a lot of users aren't even aware of the Database import/export feature personally...happy to be proved wrong.
It just surprised me as for that file to be present there needs to have been a deliberate effort to export the Database at some point, and the OP didn't mention doing so at all.


[St.]

[barryg]

I just returned from my trip and wanted to post an update.  I believe I did a database initialize as the last step the night before I left.

When I got on the plane and turned on the e200, it halted with a one line error message and a 6-8 digit hex code - I'm sorry I can't recall what it was.  I did a few cycles of 20 second power resets and it kept halting with the same error when powering on.  A while later I got an idea so I pulled the 8GB microSDHC card and tried powering it on.  It booted fine.  I plugged in the card and it scanned it and everything has been fine since.

[sideral]

Hi barryg,

Thanks for the update. I hope you had a nice trip!

Could you please respond to the questions I asked a few posts back? (clarification which version you're running now, and from which earlier version you upgraded)

If you can still reproduce the issue, could you please try a recent build? SVN revision r30122 contains an important dircache fix for a problem that may have caused the crash.

[barryg]

I'm not sure what previous version was running before the upgrade but I know the previous flash occurred in May 2009.

I can NOT reproduce the error at this point.  Perhaps it will crop up if I add some more files - I'll proceed to flash a recent build if so.