I've just upgraded one of my drives and the player now rebuilds the music database on every boot.
In Hyperterminal, entering 'q' followed by 'exit' causes a rebuild too. Here is a snippet from Hyperterminal:

player.cpp : 385:empeg-car 2.00-beta13 2002/07/24.
! tags.cpp : 61:Failed to open tags (0xc0041002).
Prolux 4 empeg car - 2.1434 Jul 24 2002
Vcb: 0x4054d000
! mp3_decoder.cpp :1049:Failed to find valid sync after seeking to offset 9735
98, error=0xc0044000

Previously the player was 20GB(hda) + 30GB(hdb), I have upgraded the 20GB to a 40GB so it's now 40GB(hda) + 30GB(hdb).

I used the drive upgrade faq and in particular Step 7 (Copying files) to move the music across to the new 40GB and everything seemed to go ok.


Pressing Down, Down, Down queues 5325 songs (about right) and it plays ok.

I have tried deleting the database but the directory /empeg/var is always empty.

Emplode won't initialise properly, it get's stuck at 'Checking Media' with the following appearing in Hyperterminal:

Adding Swap: 16028k swap-space (priority -1)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hdc4 is mounted.

I'm kindof stuck, any ideas please?

Ok, this is kinda embarrasing....

I left Emplode at the 'checking Media' stage and ~10-mins later it had loaded ok. I edited something in Emplode, resynch'd and the player is fine now!

To hide my embarrasment a little, what about adding something to the FAQ outlining the fact Emplode takes ages to rebuild the db with no discernable progress activity during the initial stages?

Emplode won't initialise properly, it get's stuck at 'Checking Media'

Are you sure it's stuck? Checking media takes a looong time on big discs. (And for some reason, on big full discs it's ages before the first "blip" of progress starts.)

If you've left Emplode for half an hour and it's still stuck, try manually fsck'ing the discs (as per the FAQ), then run Emplode. Emplode will rebuild the database and all will be fine.

Peter

Edit: Sheesh, impatience!

Trust me, I know about those big full disks being slow to fsck. 60GB is about 45 minutes per drive.

what about adding something to the FAQ outlining the fact Emplode takes ages to rebuild the db with no discernable progress activity during the initial stages?

It doesn't, normally. The problem was in the "checking media" stage, not the database rebuild. Two separate issues, usually unrelated, coincidentally happening at the same time for you in this instance.

I'd rather see Emplode give better feedback about the checking media stage. Perhaps warning you that this particular one is gonna take a long time. Or maybe even simply change the name of the stage to "checking media (may take a long time)".