I made the mistake of accessing my player through ftp while launching emplode. Both connections died, and now I can no longer reflash the player with .upgrade files. It says No hard disk found contact support when plugged in to the AC adapter. (occasionally. it boots up and gives the error msg "Unable to unmask IDE"). However, to top it all off, the player works flawlessly in the car! In fact, occasionally after booting the unit in the car, it works once on the AC adapter, and then reverts to the No hard disk found error. While i was using the player in ftp, i didn't give the literal site ro command before it disconnected, so maybe that was a problem. Regardless, how can i get my player to work in the house again?

Here's what hyperterminal says:
empeg-car bootstrap v1.02 20001106 ([email protected])rror:
Starting kswapd v 1.5
h
S
If there is anyone present who wants to upgrade the flash, let them speak now,ed
hda: read_intr: status=0x7
ttyS00 at 0xf8010000 (irq = 1
or forever hold their peace...it seems not. Let fly the Penguins of Linux!at 0xf8050000 (irq = 17) is a SA1100 UART

e000 v1.04
h
ttyS02
Copying kernel...q = 16) is a SA11
Calling linux kernel...tr: error=0x24
Uncompressing Linux..................................... done, booting the kernenitialised.
hda: r
empeg dsp audio initialised
l.
i
Linux version 2.2.17-rmk5-np17-empeg51-hijack-v301 ([email protected]) (gcc ve
hda: read_intr: error=0x24
end_request: I/
rsion 2.95.3 20010315 (release)) #2 Sun Dec 15 09:48:22 EST 2002
hda: read_intr: status=0x71
Processor: Intel StrongARM-ead_intr: e
IP Protocols: ICMP, UDP, TCPda: read_intr: error=0x24
TCP: Hash tables configured (ehash 16384 bhash 16384)
hda: read_intr: status=0x71
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
end_request: I/O error, dev 03:
IrCOMM protocol (Dag Brattli)
Starting kswapd v 1.5da: read_intr: status
SA1100 serial driver version 4.27 with no serial options enabled
ide0: reset: failed
hda:
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
hda: read_intr: error=0x24
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 d0004180).
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 ([email protected])

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

I think the errors you've mentioned are usually the result of a dodgy drive cable.

That's so strange though! Everything worked perfectly before I got into the command line ftp and started messing with it. It doesn't seem like messing with the software could physically "mess up" the drive cable or anything. And why would it work flawlessly in the car, but not at all in the house?

Greetings!

If you got into command line ftp and left the filesystems read/write, the filesystems would be marked as dirty / needing sync. Unless you were in the middle of something really severe, it should not have caused damage. I have personally FTPed while syncing with emplode. It did not cause any damage.

Can you boot at all and get a prompt? If so, you might want to fsck the drives manually. Also, if you have any preinit software, or if you were FTPing system files at the time (new kernel, init software, etc.), you might want to flash a new version of the kernel in place. Clarification - not the .upgrade, since that requires the disks to be in place to pump the partition. Try one of the hijack kernels, or the base kernel and the logo editor software to flash it.

Tbussman:

As was mentioned elsewhere in this thread, the error messages you're receiving are associated with disk drive hardware trouble such as a bad cable or bad IDE header. They would not usually happen just because of a RW/RO mistake on your part. The fact that they happened while you were mucking about at the shell is likely just a coincidence. Please click here for complete details.