I have a mk2 2x18g and a rio 1x30g.
What I've done:
I ordered a 30g HD to upgrade the rio to 60.
empeg drives: e1 & e2
rio drives:r1 & r2
I copied all the empeg (full) onto the rio like this:
e1+r1 in the empeg, e2+r2 in the rio.
then I copied each /drive0 dirs&subdirs into /drive1
then I put e1+e2 in the empeg, and r1+r2 in the rio.
and both are working correctly. (playlists appear & play correctly in emplode & player)
...but ON THE RIO, when I do a sync with emplode, my playlists structure&songs are completely shuffled out. (it could require several weeks to get them right).
For the moment I restored the old database&playlists (in /drive0/var), it works but I can't upload new songs w/o loosing playlist structure (same with jempeg).
Can sb help me?
some questions:
it seams the problem comes from the new drives size, but why?
What is the structure of the playlists file?

it seams the problem comes from the new drives size, but why?

Did you use the empeg DiskBuilder utility on the new drives before loading them with the music?

tanstaafl.

yep

FTP to your unit (or use 'q' to access the developer image "bash" shell).

Mount the drives RW

delete the database:

rm -f /drive*/database
rm -f /drive*/playlists
rm -f /drive*/tags

Remount the drives RO

Reboot the player, run Emplode, and it should rebuild the databases correctly this time.

But of course, if the two merged sets of files included "duplicate" filenames for the tunes/playlists (same hex numbered files..), then this will never work.

-ml

But if I delete the playlists file, I'll loose my playlists don't I?
When emplode do a sync, database is well rebuild, only the playlists are bad.
in fact I made an exact copy of my empeg songs to my rio.
So there's no duplicate.
But maybe I'm wrong somewhere?

But if I delete the playlists file, I'll loose my playlists don't I?

No, you are not deleting the source playlist files, you are only deleting the database file that indexes them. The whole point here is to force the database to do a re-index of all your FID files which includes the playlists themselves (which are not touched by the procedure).

ok thanks guys I try...

I hate to dig up old threads like this, but shouldn't it be:

rm -f /drive*/var/database

etc..?

yes.