I Tried adding a Different Home Logo to player and now get the message"No Hard Disc Found Contact support" While i try to contact support anything else i can do to get it working again Please Mike

Probably coincidence - I would guess you have a bad disk cable. Contact support - your empeg knows best

Rob

... since i've added a second hdd my mk2 sometimes doesn't really know..
sometimes it boots, sometimes it says ... contact support.. then i've to pull it out od sled and put it back again...

those damn toshiba disks...

That sounds like that bug where it timeouts waiting for one of the hard drives. Perhaps someone else can elaborate, but I seem to remember that a possible fix was to switch master/slave settings on the hard drives.

i already thought about that...
but as far as i remember for some reason it was not possible to exchange/select master/slave on one of the disks...
i don't remember any more...
i think i'll have to give it a try... well... let's see tomorrow...

but thanks for reminding for the idea

It is weird as I have the exact same problem. It only happens on occasion. It never happened at all until I upgraded from 1.03 to the 2.0Bx builds (and also used the logo editor. I requested a new cable and it is on the way. Hope that it fixes it.

Steve

Well I just got my new cable and I am still getting the same intermittent problem. On bootup I get the screen saying no hard disk found and to call support. I ran my empeg for about 4 weeks running 1.03 (no Hijack) and never saw it. As soon as I upgraded to 2.0B7 and B11 both with Hijack it began. I have not yet gone back to 1.03. My empeg has 2 48GB IBM drives. It really seems like some kind of timing issue. I double checked the master/slave settings on the drives. There is no rhyme or reason on when it happens. The interesting thing is once it happens, it usually won't work until I unplug and replug multiple times. Sometimes I do it up to 10 times and it still happens. I have had it not happen for up to a few days. I also never had it happen on AC. I guess I will try to troubleshoot by install only 2.0B11 and then go back to 1.03 if it continues. Any thoughts would be appreciated. Thanks!

Steve

did you put spacers under the drives ? mine didn't have them under one of the drives and was causing the no disk found errors

Quick question to all...This might sound stupid, but it did affect me. Is the cable fimly plugged into the HD. I mean, no gap where the pins on the HD connector is visible. I had this issue myself, and the replacment cable I got didn't change anything, but when I pushed that connector all the way down so there was no gap, I've not had a failed boot. (searches for wood to knock on) but YMMV.

Get a serial log - once the drive cable has been replaced, the serial log can be very helpful in narrowing down where the problem is.

Yes there are spacers under both drives. The cable is in very firm with no gap. Where is the serial log? Next time it happens I can bring it in to pull the log. Let me know. Thanks!

Steve

I had this happen on a single drive empeg unit. Opened the unit to check the cables and they were fine. I think it is software related.

First of all here are the syptoms:

Never happens with 1.03
Never happens on AC power
With any version of 2 and with or without HiJack
Happens after several hours of use.
Also would get lots of lockups and 'failed to unmask IDE problem'
Added a cooling fan to make sure of the temp situation.
Temp sensor not showing anything outside the range.
Once the unit starts to act up, nothing helps except sleep.

I was on a long road trip when it first gave me issues. Didn't have a laptop with me to figure out the serial logs and such. Did everything possible and sometimes it would boot and sometimes it wouldn't. On AC power it was fine. Go back tot he vehicle and it would act up. The next day it was all cured on it own. Until about two hours on the road, acted up again.

Never found the solution. Never does it on shorts road trips less than two hours.


I have a new Rio player now as well. With the same software installed, but hav't been on a road trip over two hours yet. So I can't confirm that it is software and not hardware.

doulve check that cable.. i had simialr problem.. and i switched the drive links.. like so

orginal cable config

______________Drive0___no drive
Mainboard ||-----||--------||

Switch It To This:

______________no drive___drive0
Mainboard ||-----||--------||

just to see if its the cable thats what i did.. and it works now.. till i get my new cable..

Sounds like hardware to me, not software.

Especially indicative is that the unit has to "warm up" for a couple of hours to produce the problem, and then it has to "cool down" for the problem to go away again.

Definitely hardware, dude. A bad solder joint somewhere, perhaps.

-ml

I also have the same problem. The Mk2a originally came with a fujitsu 30 gb drive. I had a number of different issues occuring with this drive so while I was waiting to receive a new cable I replaced it with a 12gb hitachi drive I had laying around. Well, the problems all disappeared. I had also installed the latest versions of Hijack with the jiffy fix installed. When the cable came I installed it just to be sure. After it worked well in this configuration for a while and I was getting close to filling my 12gb drive. I added the 30 back to the system. I am now experiencing occasional pauses in music, can't find drive error, and other strange phenomenon. I'm pretty sure that the fujitsu drive has a problem. FYI, I also did the builder process on both drives before installing them. I also did it on the 30 before I removed it just to eliminate any chance of drive corruption as the cause of my woes. I also installed the jumper when adding the 30 the make it the slave(drive1).

I was the original poster here.I received my replacement cable and installed it on Friday. I also have the 30gb fujitsu drive.Have not had any problems since,I am using hijackv233 also.

I replaced my cable and still have the issue. Mine happens on boot and usually after sitting overnight. It happened today. I plugged it over 10 times with no luck. Went out for lunch and it fired right up. It has never happened on AC or with 1.03 software. I have 2 48GB drives. Someone mentioned to look at the serial log. Can someone tell me where that is so I can upload the log after the next time it happens? Thanks!

Steve

As a further note on this, on occasion I would hear the hard drive seeking when it starts up, clickity click, clickity click, clickity click. It might do this for some time before finding what it was looking for.

did you try this: empeg.comms.net/php/showthreaded.php?Cat=&Board=empeg_tech&Number=77605&page=0&view=collapsed&sb=5&o=14?

In reply to:

---

I would hear the hard drive seeking when it starts up, clickity click, clickity click, clickity click. It might do this for some time before finding what it was looking for

---

Sounds to me very much like a HDD headed south - backup your files while you can and contact support.

Rue

Have not tried that yet. I still don't understand why this only started after updating from 1.03 to 2.0B7&11. Also it only happens on occasion. Very weird. Is there anyway to log what is happening? Thanks!

Steve

Connect terminal emulator (for instance Hyperterminal in Windows) to the serial port (instructions and settings are in the FAQ) and see what gets written there on boot...

/Michael

Yes, you just have to :
- connect the empeg through COM port to your PC,
- run hyperterminal (or an other COM terminal) with default parameters, except bitrate:115200 and Handshaking:None
- start your empeg
that's the serial log. (you can save or copy it)
...but as Tony says, it's in the FAQs ;-)

cheers michael!

Cheers!

Are you on for the european users meet? In that case we can complete it properly, with a beer, then...

/Michael

PS. Looks like you got your 'e' and 'u' transposed in you sig tags

Ohh I didn't know! I checked the BBS and found it's the 14-15-16 of june... so my agenda is booked, yet!
tnx for the tags, but there's a bug in the marker help page: tags are translated, this way 'blue' becomes 'bleu' in french, and that's what I typed... I seen some mispelled tags on the bbs, and I think that's the origin.
So CU in Amersfort (that's it?) and no problem for the beer(s).

better like this...

No. Maybe my poor english is not good enough for the marker-html translator... I think I'll replace the lense by an other orange one
What about an other section: BBS bugs? just kidding...

that does sound like either low power or a bad drive... ? but one thing to note is that I did a cable upgrade once and thought I was still having the problem.. ends up that I simply hadn't firmly attatched the cable to the main board (checking the connections to the drives was 2nd nature - but somehow I kept forgetting to check the connection to the board! )

Like I said this never happens on AC. I would have to remove my sled to connect to the serial running DC. Any other thoughs on this?

Steve

I have a very similar problem to 94cobra and skamp's on a 30GB Rio - same boot error, occurs mostly during car use, maybe for half an hour it might not boot and then *woo* it works again. It DOES occur during AC use, but far less frequently. It has also been getting worse and worse. It feels like a dying HDD...but I'm so trying not to accept this

I've replaced the IDE cable with a new one from support and I've double checked it's tightly fitted.

After a great deal of "why won't it break when I WANT it to?!" frustration I have gotten a serial log from the little beast.

Here it is: It doesn't *feel* like it gives much away, but here goes:



empeg-car bootstrap v1.02 20001106 (hugo@empeg.com)
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
kernel.
Linux version 2.2.14-rmk5-np17-empeg50-hijack-v225 (root@tbird.localnet)
(gcc version 2.95.3 20010315 (release)) #2 Sat Mar 2 09:22:29 EST 2002
Processor: Intel StrongARM-1100 revision 11
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 30103054)
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 14968k/16M available (1008k code, 20k reserved, 384k 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 20706d65 'emp '
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 d0004b00).
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...
Probing primary interface...
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman (erik@vt.edu)

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC
00:02:d7:26:0b:ee
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...VFS: Cannot open root device 03:05
Kernel panic: VFS: Unable to mount root fs on 03:05


There. Any comments? Email support and cry for mercy?

Drives not found.

Triple check the connections.. make sure everything is aligned.

Can you hear the drives spin up?

Email support.