I'll try putting some music on my newly-formatted player with emplode, and see what happens.

Well, it worked fine. Odds are that there's nothing wrong with the way the disk's built.

Greetings!

Problems:

Okay...

- Can't access the Empeg via Emplode. Emplode crashes after Rubuilding the databases.

This is a similar situation to what I see with emplode on my machine. I always thought it was too many fids, but it might be a memory (or lack thereof) problem.

You should find that your new changes made it to your player successfully. All you need to do is rebuild the databases manually. Exit to shell, set your drives read/write, turn on swap (in case it is the lack of memory) and run the player application from shell. It will rebuild the databases this way. Once the player application completes building the databases, exit the player application with a "q", turn off swap, set your drives read only again and reboot. A resync at that point should show everything correct.

- Everything Empeg is rebooted it will Rebuild the databases. Even incar, takes ~2 minutes... I was wondering if there went something from in the mke2fs -part of the hda4 formatting After the format it said that partition is checked after 30 (or was it 60?) mounts or 180 days, whichever occurs first.

This could be two different things.

1) If you do not have permanent database files (from the emplode crash) the player is building these files on the fly. You can tell the difference if the boot text says "building" or "reading" for the music database, playlists and tags files. If this is the case, the above fix will take care of this.

2) Lots of fids or a big database. fidsift will likely help this, but I suspect it is more likely item 1...

Still struggling with the problems. Tried to rebuild the databases manually with the swap activated and all, but still can't make it work. I have no clue where to continue. I found this odd:

empeg:/empeg/bin# ls -la /drive0
total 177
drwxr-xr-x 4 0 0 4096 Jan 2 08:03 .
drwxr-xr-x 15 502 220 1024 Jul 24 2002 ..
drwxr-xr-x 2 0 0 155648 Jan 1 09:24 fids
drwx------ 2 0 0 16384 Mar 25 2004 lost+found
empeg:/empeg/bin#

I thought the databases were under /drive0/var ? the /drive0 was empty after the manually partitioning/formatting/flashing, I copied the fids dir from the old drives. Is this ok?

And the player is building the database and playlists in everyboot, not reading them.
Attached Emplode's crashing log. Emplode crashes after the rebuilding databases -bar has completed.
Also attached the serial output of empeg booting, captured with hyperterminal, the breaks are screwed up I guess...

Waiting desperately for new guides d=/

Attachment 2.

Weird....

Try manually creating a var directory under drive0 and rebuild the database. The lack of a config.ini will be a problem until your first emplode sync, but it should at least save the database files for you.

Hey, it worked!
Thanks pgrzelak!

Any other directories under /drive0 I might want to create?-)
Guess I'll be going to install Hijack next, to disable the waitingfor2ndhd. And I'm just going to hope MK1's mem can handle the database long enough. Maybe I need to do some mp3 cleaning on the unit when it becomes unstable again d=)

Greetings!

I think you should be fine at this point. The only directories that are usually under /drive0 are the fids and var. Plus lost+found, but I don't think of that one very often. Try a sync with emplode now - that should recreate your config.ini file.

As for database size, you should be okay for a little while anyway...

Hey, it worked!
Thanks pgrzelak!

Ah. Of course, I did my testing with the disk as /dev/hdc, so I didn't need a var directory.

I'll update my page to include this.