my 18 gig HD has crapped out on me but fortunately my 30 gig HD is fine. I have been running the player off of this one drive and it works...partially. About every other song, it will display the song title etc but will not play it. I then press forward to the next track and if the track is there, it will be automatically paused. I un-pause it and the song begins to play.

I can only guess that what is happening is that the database still lists some of the songs that were on the dead drive which is not even plugged in anymore and can't find them.

I can't figure out why emplode decided to store some songs on the 18 and others on the 30. I added the songs by 'album' yet some albums will have only half the songs available (I assume on the 30 gig drive).

I was wondering how I can 'force' my player to examine the contents of working 30 gig and rebuild the database to reflect what is on the 30 gig drive only. Is this possible?

Greetings!

If you delete the /drive0/var/database, tags and playlists files and it will rebuild the DB automatically next sync.

I can't figure out why emplode decided to store some songs on the 18 and others on the 30.

This is FAQ entry. Please click here.

some albums will have only half the songs available

For this reason, and because there is no function in Emplode to tell which drive the songs are on, I recommend you simply wipe the drive and re-load the music from your PC from scratch. "Dust off and nuke the site from orbit. It's the only way to be sure."

I begged The Guys for a Drive0/Drive1 indicator in Emplode. I tried to explain that it would be very useful in some situations (such as yours), but they didn't see a need for it so they didn't implement it.

>>(snip)If you delete the /drive0/var/database, tags and playlists files and it will rebuild the DB automatically next sync

does this involve command line stuff? how do i do this?

does this involve command line stuff? how do i do this?

Click here for instructions.

However, if you just want to wipe the drive completely and start over from scratch as I recommended, use the builder image instead (instructions in the disk upgrade guide).

How exactly would it help in this situation?

Rob

How exactly would it help in this situation?

He would be able to see, immediately, via a simple column-sort, which songs were originally on drive1 and needed to be re-added to the player after the second drive died.

The reason that it's not useful in this situation is that it is perfectly possible for the *0 file to be stored on a different drive from the *1 file, so the value would be meaningless.

In reply to:

---

I begged The Guys for a Drive0/Drive1 indicator in Emplode.

---

While developing the next version of mp3tofid, my second 40G drive crashed. So I added some options to handle this situation. By default, mp3tofid will now save all playlists on drive 0, and will only spread tunes acress both drives. Furthermore, there will be an option to skip all references to tunes in drive 1, so all playlists and database files are valid while the drive is being repaired.

This was proven to be useful. When my drive arrived back from warranty repair, I only had to re-sync the tunes on drive 1 and the playlists on drive 0.

Pim