Guys, I Inserted my Empeg Mark II into my Car slot this morning and it went thru it's normal routine of booting up. I went to select a Playlist and it told me there were "NONE". Well, That's not GOOD I know there is music on the player I have 80gigs worth of music. I drove into work with a very sad face hoping that everything will be okay as soon as I connect it to the network. I added all of the cables and turn on the Empeg device and I get the following message during Checking media......

"Download failed while checking media Error 0xc0041016"


I know now this is not good... Is all of my music gone... Do I have to restart all over... How could this happened that's a lot of work (80 gigs of music) gone down the drain..... I'm have trouble breathing right now..... I may need Medical Attention.... Please wait..... Okay I'm back Hands are shaking alot because of this problem.

Tech Info that you might need.

I'm running the latest software verson 2.00 beta3, I installed it when it first came out and had no problems with it until now. I have not download or sync the player for at least a day and it was last successful. Please tell me what the problem is and I hope it is something easy to fix like re-install the bootcode or something..... I'm DEAD in the water with no music for the Car or my Office and i just added some Christmas music to the player.

HELP!!!!!!!!!. Now is a good time to tell me this is all a Dream and I wake up and a cute woman is beside me and she's feeding me fruit and then she tells me that it's all a dream and your player was in a weird state and it works now.... Please tell me something like that......

Ernest

Greetings!

Are you running the developer version (can you get to shell)? If so, check the /drive0/fids and /drive1/fids directories to see if the files are there. If they are still there, you data is still happy on the drive. If you cannot get to those directories (corrupt, deleted, etc.), then there is a bigger problem.

If the data is there, you might want to try the following possible solutions:

a) manually perform a fsck on the drives
b) grab a boot log, and post for further analysis
c) delete the database and playlist files manually and attempt to rebuild with a sync / reset of player

Strangely, last night I had a similar error but with a different code (it started with 0800, I can't remember the rest of it.) I think it said "synchronise failed while checking media" instead of download failed. Anyway the "Synchronising" display on the Empeg was frozen (not moving around as it usually does) and the whole thing was locked. I gave it ten minutes in the hopes that disk caches would empty and such, and pulled the plug. I retried my sync, the file system check went okay, and I haven't seen any ill effects so far.

I would try to drop to a shell (assuming you have the developer version installed) and see if you've got your FID files out there. If so, I think you might be able to connect via Emplode, and I think it tries to check the database integrity when it connects. It should detect that something is out of wack and try to rebuild the database (I think.)

Wait for one of the Empeg guys to give you more solid advice, though... 80 gigs is too much to lose.

It might just be a loose cable or a loose jumper. Check those first.

Greetings!

Would it get through the boot in that case, though?

Would it get through the boot in that case, though?

If somehow drive0 became disconnected/deactivated and drive1 took over as the primary, yes. Remember that the drive replacement FAQ recommends installing a kernel/player to drive1 for just such an eventuality.

This would also explain the empty playlist at boot time (scratch partition on drive1 blank 'cause nothing ever wrote to it).

Remember that the drive replacement FAQ recommends installing a kernel/player to drive1 for just such an eventuality.

Really? Was this suggestion in the "old" pre-Riocar.org FAQ in the FAQ forum? I ask because I don't remember seeing that, and it's really a good idea. I didn't know the Empeg would fail-over to /drive1 in case of a /drive0 failure. Interesting.

Any way that I can prep my /drive1 with a kernel/filesystem without swapping drives or opening the Empeg?

Cool!

In that case, I would really like to see a boot log.

Was this suggestion in the "old" pre-Riocar.org FAQ in the FAQ forum? I ask because I don't remember seeing that, and it's really a good idea.

Yes.

I didn't know the Empeg would fail-over to /drive1 in case of a /drive0 failure.

That's not what I meant. I mean that if, at the hardware level, drive0 disappears, then the only other drive plugged into the IDE cable just becomes drive0. It's not an empeg-specific thing, it's just the IDE controller doing it.

If drive0 is ok, but drive1 is not (and happens to contain the root playlist) you'll see this behaviour. Does anything appear if you do a search?

It does sound like cable/jumper related, though.

Hugo

Hey Guys,

I sure hope Tony is correct, I guess you don't miss the well until the well runs dry. I am at work right now and I don't have the tools to remove the facia and side screws. I do indeed hope that the cable somehow came off and all I have to do is re-connect it and I'm back in the saddle again. If not I will capture a boot log and post it to the BBS I will also check to see if my FIDS are still on the drive ( I sure hope so, 80 gigs and POOF!!!!).

Ernest

but drive1 is not (and happens to contain the root playlist)

Oh, wow, that's a good point. Maybe the jumper just came off of drive1?

Hello All....

The problem happens randomly... Which sounded like the IDE cable on the unit is not firmly connected... So it prompt me to remove the cover and see if this was indeed the problem. I really was hoping this was the case. I removed the top case and I saw that both IDE cable were firmly on the hard-drives.

Q1: Did I lose my music and hard work...
No, I can see that the music is still on the MKII, because when the MKII works I see and can hear the music as normal. The problem that I have is it is random and it happens mostly in the car. I can pull the MKII unit out and some times re-insert it and it and the problem goes away. I know when the problem occurs because the unit boots really quick and the display that I get is no title display but I see the time/remaining section lite up....The next time it fails I hope I'm in the office or home and I can perform a dump of the boot-up and send it to the BBS for review.


Ernest

What about the jumper on the slave drive? Maybe it's loose. Even if it looks like it's attached OK, perhaps it ratlles a little and the pins need to be bent to make it connect firmly. Also, you might want to check the IDE connection on the motherboard. Finally, as stated in the FAQ, it's possible the cable itself might be a bad one.

Hello Guys,

I have the problem again and I now have dump the Boot-up messages from the Mark II Player... It looks like the Hard-drives are not being found upon boot up.


Boot - File Starts here: Ingnore DHCP info below it was not attached to a network.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

empeg-car bootstrap v1.00 20000601 ([email protected])
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!

e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kerne
l.
Linux version 2.2.14-rmk5-np17-empeg49 ([email protected]) (gcc versi
on 2.95.3 20010315 (release)) #127 Wed Oct 17 16:02:35 BST 2001
Processor: Intel StrongARM-1100 revision 11
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 7, serial number 80000457)
Command line: mem=12m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 10968k/12M available (964k code, 20k reserved, 332k data, 4k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Linux-IrDA: IrCOMM protocol ( revision:Tue May 18 03:11:39 1999 )
ircomm_tty: virtual tty driver for IrCOMM ( revision:Wed May 26 00:49:11 1999 )
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 67706d65 'empg'
Scheduling custom logo.
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0004080).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
hda: IBM-DJSA-232, ATA DISK drive
hda: IBM-DJSA-232, ATA DISK drive
hda: IBM-DJSA-232, ATA DISK drive
hda: IBM-DJSA-232, ATA DISK drive
hda: IBM-DJSA-232, ATA DISK drive
hda: IBM-DJSA-232, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: IBM-DJSA-232, 30520MB w/1874kB Cache, CHS=62010/16/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected])

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:10:01:c
9
Partition check:
hda: [PTBL] [4134/240/63] hda1 < hda5 > hda2 hda3 hda4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...þŒŽ•Ô¥j½Õ¹Ñ•‘�root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k initI see this is a developer image!
Mounting proc
Mounting first music partition
VFS: Can't find an ext2 filesystem on dev ide0(3,4).
Tried to mount /dev/hda4 but got error 22
Error mounting partitions (possibly already mounted)
Remounting first music partition read-only
No primary hard disk
Remounting second music partition read-only
No secondary hard disk
Press 'q' now to go into development mode. You Have Zero Seconds To ComplùStarti
ng player
empeg-car 2.00-beta3 2001/10/17.
E !! tags.cpp 61: Failed to open tags (0xc0041002).
Rebuild 0ms
3c15be7c DHCP name = lo
3c15be7c DHCP index = 1
3c15be7c DHCP flags = 0x8
3c15be7c DHCP addr = 0.0.0.0
3c15be7c DHCP bcast = 0.0.0.0
3c15be7c DHCP mask = 0.0.0.0
3c15be7c DHCP name = eth0
3c15be7c DHCP index = 2
3c15be7c DHCP flags = 0x1002
3c15be7c DHCP addr = 0.0.0.0
3c15be7c DHCP bcast = 0.0.0.0
3c15be7c DHCP mask = 0.0.0.0
3c15be7c DHCP Our mac is 00:02:d7:10:01:c9
3c15be7c DHCP Current IP address is 0.0.0.0
3c15be7c DHCP Broadcast address is 0.0.0.0
3c15be7c DHCP Attempting to open Autonet socket for eth0
3c15be7c DHCP Adding interface eth0
3c15be7c DHCP Sending DHCP discover (eth0)
3c15be7c DHCP Extensions present: 61 53 55 57
3c15be7c DHCP Testing Autonet address 169.254.199.231
Prolux 4 empeg car - 1.1090 Oct 17 2001
Vcb: 0x405ae000
3c15be7d DHCP Sending DHCP discover (eth0)
3c15be7d DHCP Extensions present: 61 53 55 57
E !! local_audio_component.cpp 543: Invalid tune information for FID 0x0. This i
s bad.
3c15be7e DHCP Sending DHCP discover (eth0)
3c15be7e DHCP Extensions present: 61 53 55 57
3c15be7f DHCP Sending DHCP discover (eth0)
3c15be7f DHCP Extensions present: 61 53 55 57
3c15be80 DHCP Sending DHCP discover (eth0)
3c15be80 DHCP Extensions present: 61 53 55 57
3c15be81 DHCP Sending DHCP discover (eth0)
3c15be81 DHCP Extensions present: 61 53 55 57
3c15be82 DHCP Sending DHCP discover (eth0)
3c15be82 DHCP Extensions present: 61 53 55 57
3c15be83 DHCP Sending DHCP discover (eth0)
3c15be83 DHCP Extensions present: 61 53 55 57
3c15be83 DHCP Testing Autonet address 169.254.199.231
3c15be84 DHCP Sending DHCP discover (eth0)
3c15be84 DHCP Extensions present: 61 53 55 57
3c15be85 DHCP Sending DHCP discover (eth0)
3c15be85 DHCP Extensions present: 61 53 55 57
3c15be86 DHCP Sending DHCP discover (eth0)
3c15be86 DHCP Extensions present: 61 53 55 57
3c15be87 DHCP Sending DHCP discover (eth0)
3c15be87 DHCP Extensions present: 61 53 55 57

It appears as though it is only finding one disk drive. If you have a two-drive player, then the problem is most likely either the drive, the cable, or the jumper.

I got the identical message when using using a kernal with the one drive patch on a two drive player. If this is the problem maybe a note (or a bigger one) should go in the drive install FAQ.

Q1: What do you mean by the one drive patch?
I'm running version 2.0 Beta3 I would think that any patches would be included in the latest version code.

Q2: Do you still see this problem in Version 2.0 and is it still happening?
I have not had any problems until the last 2 weeks the problem happens randomly mostly in the auto. I've had my MKII player for almost an year. I started with (2) 18 gigs and added (2) IBM 30 gigs that been running fine since Feb 01.

Q1: Is there a backup program that I can use so if the Hard-drive is going to go bad I don't lose all of the work that I have on that bad drive.

1) The one-drive patch would be part of a custom kernel (like MLord's hijack). It tells the kernel not to look for a 2nd drive, thus not having to wait for it to spin up and decreasing boot time by a couple seconds. If you're running the standard 2.0b3 kernel, this is not an issue.
2) If the problem is intermittent (sic?), then it may be a loose jumper on one of your drives. An inch of Electrical tape, placed correctly, goes a long way.
3) There are a few backup options. If you have 2 drives with enough space, you can just copy the FIDs from one drive to the other and force a rebuild of the database. If you want to backup to your PC, check out the FAQ

If the problem is intermittent (sic?), then it may be a loose jumper on one of your drives. An inch of Electrical tape, placed correctly, goes a long way.

If I recall correctly, he said he already put electrical tape over the jumper. But if the jumper is loose (i.e., the pins don't make solid contact against the jumper), then electricaly tape will only prevent it from falling off, it won't take care of the intermittency. If this is the case, bending the pins slightly might help.

Although I would say it's more likely to be a "dodgy cable" at this point. Ernest, have you contacted Support yet about replacing the cable?

The issue here is people using the wrong sized jumpers; the jumper for a 2.5" drive is a 2mm jumper, whereas people seem to be using 2.54mm (0.1") jumpers.

It's not just the pin pitch that's wrong, it's the pin dimensions too (which means it's easy to get it wrong. The correct jumpers are the little ones that feature on the empeg main board (near the docking plug connectors). Don't steal these though, as it needs them :)

The correct jumpers are sold by farnell, in packs of 25: code 510-920 (blue), 510-932 (black) and 510-944 (red). These are *amazingly* expensive though - £4.99 for 25 jumpers (yes, that's about 30 cents *each*).

Hugo

Thanks, I will add that to the FAQ.