Can anyone help? I tried to sync a bunch of stuff onto my empeg, got a bunch of errors rebuilding the database, and now my entire playlist looks like one giant listing. Problem is also that none of the entries have files associated with them. I need help! Can anyone that thinks they can help please email me at [email protected] asap and give me their number? I'll call and we can try and sort this out???

Please??

- Thanx
- Jon

No one? I'm dyin! Help!

- Jon

Maybe rebuilding the database will fix it. Roger, isnt there some way to do this from the bash prompt?

Sean

Ok, I was able to see by looking in the drive0 and drive1 fids directories that all of my songs are there. It's just the playlist that's hosed... any suggestions?

- Jon

Good deal then. Dont try anything else, just go to sleep. When you wake up in the morning someone that knows what they are talking about will have answers! Sorry im not much of a help.

Sean

I think this is good advice. I'm a bit freaked out as I've spent the better part of 2 years "perfecting" my playlist... I attached the bootup file to this message. It's funny and scary to me that the last line says:

! local_audio_component.cpp: 573:Invalid tune information for FID 0x0. This is bad.

- Jon

After looking at your attachment, I'd definitely reapply the 2b7 upgrade again and see if it still stalls at that point.

The other interesting item is the message "Tried to mount /dev/hda4 as reiserfs but got error 19"

Hmmmmm.

Other than that it looks like the music/playlist partitions are safe. Ain't it grand that the music partitions are set to RO...

Best wishes on this one...

Don't Panic over this message about Fid 0x0 it looks bad.

The message looks bad but if you search the forum for that message you'll see a reply from Roger (from Empeg) about it.

Its caused when your RioCar does not have any song currently playing from any playlist.
Normally this would be the case when you've just uploaded songs and have never played any of them and the unit is new.

hmm, sounds like you doesn't it - new player, just uploaded some songs, never played any yet, harmless, but serious looking message.

Wait until tomorrow morning before you do anything else.

And rest easy - its probably easy to fix.

Ok, am reapplying 2.0b7 now. Hm. Both drives appear to be working. Wonder what error 19 is...

I'll give an update in a minute...

- Jon

In reply to:

---

Tried to mount /dev/hda4 as reiserfs but got error 19

---

Don't panic over this message - every empeg/rioCar running 2.0B7 gets this.
Its simply a message that /dev/hda4 is not formatted with reiserfs, its a normal ext2fs filesystem and not a reiserfs formatted one.

Its safe to ignore it as its not related to any problems you're having now.

Thank you Tim, Number6, and Terminator for the emails and help.

I did re-install 2.0b7 but no luck. Same problem.

I'm going to wait for Rob or another tech support person to call. Thank you all again!

I love it when a user community is so focused on assisting their fellow users. You guys rock.

- Jon

Does the player rebuild its database every time you turn it on? If so, delete your /empeg/var/database, playlists and tags files. This problem can sometimes be caused by a corrupt 'playlists' file.

I'm sure this is due to code from the HSX unit leaking into the player code. Because as I found out, the ReiserFS won't work on the empeg currently without a major hack.

I'm still looking into ext3 on the player though in some of my spare time.

I've just hacked on the code, so that the player no longer complains about this if the FID is 0x0. The error message is alarmist.

Update: downgraded to 1.03 and now my entire playlist is flat and it looks like all of my songs are in the "unattached files" folder.

I'm waiting for Hugo to call and help me try and get it sorted out further.

If anyone from empeg reads this, am I waiting in vein? Should I be speaking with anyone else at this point? I worked with David this morning, but we hit a dead end after the dd procedure didn't help. Downgrading was a good suggestion as I think we did make some progress...

- Thanx
- Jon

Hm, your message seems to have been drowned in a recent deluge of posts.

Try this: drop to shell, go to /drive0/fids and see whether you have any short *0 files (less than few kb). Try to 'cat' corresponding *1 files; they should have a line 'type=playlist'. If there are no such files, then you (meaning your emplode) really managed to delete playlists, and you are out of luck. You may want to use emplode 2.0b3 soup views to help you find tunes that go to respective playlists (2.0b7 emplode has that nasty 'delete while moving' bug).

However, if there are playlist files around, do as Roger suggested: go to /empeg/var and delete files database, fids and playlists. Reboot the player and notice it is rebuilding database (from playlist and *1 files) upon start. Go to playlists menu on the player to verify playlists are there. Resync. Let us know what happened.

Good luck!

Thanks for the note. I tried everything to get my playlists back, but to no avail. I had David Moss and Hugo trying to help with this.

I ended up downgrading to 1.03, and then I had all of the mp3 entries in the Unattached Item folder and the rest of my artist names and album names in a flat format. I then drag and dropped for days getting the structure and the files back to where they should have been.

I re-upgraded to 2.0b7 and now am pretty much back to normal. I'm just afraid that if it happens again, that I would have to go through that again. I'd really like it if the empeg could keep older copies of the playlist on its hard drive so that you could fall back if you needed to...

- Jon

Oh, sorry to hear that Have you found out what actually happened?

If you are even halfway comfortable with Linux, it is quite simple to write a script that will archive your playlists in situ (and you can later download the archive for safe storage using Mark's kftpd). The only reason I am not doing it is that I currently have two empegs with the same contents