Problem in Jemplode

I was updating my Empeg in Jemplode(USB) when my windows crashed. When I went to update my player again, at the beginning Sync it sits at the Checking Player Media part for a long time and seems not to move. Also when the player itself boots up it sits for a while a Building Music Databse section before proceding. Any help on how to fix this please

I looked around in past post and saw some info on Hard disk builder. So Im running this right now. Any idea how long it shoud take? I have a 50 gig and 20 gigs being used of it. After its done Im guessing I have to reload the consumer image the Hijack. Should this work?

You have to let jemplode do a full DB rebuild...can take 15-60 minutes, depending on size of drive...

...and I don't think jemplode works over USB, it's ethernet only, right?

Try a manual fsck and then sync again...

/Michael

I had to many fcsk cause I got this error:
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended. When I run this command it takes a really long time fsck -fay /dev/hdc4, it shows numbers running down the screen, is this normal?

If you ran the hard disk builder, you erased all of your music. If you're now having fsck problems, then maybe you only let it get halfway through the hard disk build. You might as well just do it again.

When I run the disk builder it goes on for a long time with this stuff. How long should it take?
Stressing /dev/hda: Spinning down.
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
Drive length is 19640880 blocks, seek testing
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
Seek test complete: 38.54 seconds.
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
Stressing /dev/hda: Spinning down.
hdstress.cpp 189 ( 46): Poll result=0 on fd=5
Stressing /dev/hda: Spinning up.
hdstress.cpp 189 ( 46): Poll result=0 on fd=5

You may terminate the stress test at any time by removing the power from the player.

I don't know why people are so quick to want to use the disk builder whenever they have disk trouble. It's rarely a solution to any possible problem, and it erases all your music.

I did the disk builder, loaded the development BIOS, then Hijack and everything is back to normal, thank god. I tried everything before disk builder and nothing worked. But now I have to load 30 gigs of music. Crappy

But now I have to load 30 gigs of music. Crappy

You mosat likely wouldn't have had to to that if you hadn't jumped the gun and run the hard disk builder. It's the equivalent of formatting your hard drive and reinstalling Windows. In 99.9% of the cases, it's easily solvable without erasing all your music.

Empeg guys, is it possible to change the warning on the builder download page to read "you will erase all the music on your player" instead of "you might if you use it wrong"?