I was uploading a long MP3 when Win98 crashed. I rebooted and tried starting Emplode again. And everytime I try to start up Emplode I get this error message:

In reply to:

---

Download failed while checking media. Error 0xc0041016

---

The player boots up fine but everything has been erased. Even the owner information is erased.

I'm running WIn98, with v2.0b11 with no Hijack. I need some advice ASAP. Anything would be greatly appreciated.

Curly

Doesn't sound good:( Can you hook it up to the serial prompt and capture the text that it's spitting out?

...Look here for steps on how to connect to the serial prompt if you don't already know how:

http://www.riocar.org/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=7&categories=Upgrade%2C+customization%2C+and+third-party+software+questions#82

-mark

OK, that was the first time I've done that. Here's what it said:

In reply to:

---

I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
EXT2-fs error (device ide0(3,4)): ext2_check_descriptors: Block bitmap for group
0 not in group (block 1396520500)!
Remounting filesystem read-only
EXT2-fs: group descriptors corrupted !
Tried to mount /dev/hda4 as ext2 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 ComplyþStart
ing player
player.cpp : 385:empeg-car 2.00-beta11 2002/02/08.
! tags.cpp : 61:Failed to open tags (0xc0041002).
Prolux 4 empeg car - 2.1434 Feb 7 2002
Vcb: 0x4086d000

---

Not good - it's telling you that your drive is corrupted... equivilant of windows telling you to run scandisk..

can you get a shell prompt?
drop to a shell (press "q" when it says to), then try forcing a checkdisk...

umount /dev/hda4
fsck -f /dev/hda4

-m

Ok I'm assuming I did it correctly. Here's the results:

In reply to:

---

empeg:/empeg/bin# umount /dev/hda4
umount: /dev/hda4: not found
empeg:/empeg/bin# fsck -f /dev/hda4
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.
Group descriptors look bad... trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/hda4

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

empeg:/empeg/bin#

---

I'm assuming that "empeg:/empeg/bin#_" is the prompt and "umount /dev/hda4" and "fsck -f /dev/hda4" are commands?

>sigh< doesn't look good..

You might want to wait until someone from Empeg can verify what I'm recommending (or offer a better solution), but you might need to re-initialize that disk (wiping everything) then reload:(

-mark

Yeah - you did it right.. actually, just found an FAQ on that item as well:

http://www.riocar.org/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=8&categories=Known+problems+and+troubleshooting+questions#162

-m

In reply to:

---

>sigh< doesn't look good..

You might want to wait until someone from Empeg can verify what I'm recommending (or offer a better solution), but you might need to re-initialize that disk (wiping everything) then reload:(

---

OMG!!

Maybe there's a problem with the disk drive cable:
http://www.riocar.org/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=8&categories=Known+problems+and+troubleshooting+questions#148

or

http://www.riocar.org/modules.php?op=modload&name=FAQ&file=index&myfaq=yes&id_cat=8#85

I doubt it - if it was a disk drive problem, you wouldn't have gotten as far as you did with the bootup process...

Your drive (I'm assuming that it's a single-drive unit?) is split into seperate partitions; the partition that boot up the empeg is fine, the one holding the music isn't...

...In the case of a disconnected cable, the empeg just doens't boot...

-mark

Ok Mark, thanks for all the help.

I guess I'll just hit the sack and hopefully someone from Empeg, or another brilliant mind, will offer some more advice by the time I wake up

-Curly-

In reply to:

---

Group descriptors look bad... trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/hda4

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

---

Did you try its suggestion?

fsck -b 8193 -f /dev/hda4

I have now. Here is the result:

In reply to:

---

empeg:/empeg/bin# fsck -b 8193 -f /dev/hda4
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.
fsck.ext2: Bad magic number in super-block while trying to open /dev/hda4

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

---

Greetings!

OK. Relax. Don't Panic. Yet.

Please post a complete boot log.

Also, you might want to try the following:

1) - get to shell
2) swapon /swapfile
3) umount /drive0
4) umount /drive1 *
5) fsck -fay /
6) fsck -fay /dev/hda4
7) fsck -fay /dev/hdc4 *
8) swapoff
9) - reboot

* - if two drive model.

Hmm, it looks like fsck doesn't pass the -b parameter through to e2fsck. Try running e2fsck directly:

e2fsck -b 8193 /dev/hda4

If that doesn't work, ask somebody else for ideas, as I'm out of them...

e2fsck -b 8193 /dev/hda4

Does mke2fs always put a backup superblock at 8193? Last I heard, its algorithm was pretty wyrd (all powers of 3 and 5, times some large factor that varies with the size of the drive). There isn't even a "mke2fs --dry-run" that tells you where it's putting them.

Peter

In reply to:

---

Does mke2fs always put a backup superblock at 8193?

---

Dunno - I admit to being on guesswork here.

Here's what the e2fsck manpage on my workstation says:

-b superblock

Instead of using the normal superblock, use an alternative superblock specified by superblock. This option is normally used when the primary superblock has been corrupted. The location of the backup superblock is dependent on the filesystem's blocksize. For filesystems with 1k blocksizes, a backup superblock can be found at block 8193; for filesystems with 2k blocksizes, at block 16384; and for 4k blocksizes, at block 32768.

Additional backup superblocks can be determined by using the mke2fs program using the -n option to print out where the superblocks were created. The -b option to mke2fs, which specifies blocksize of the filesystem must be specified in order for the superblock locations that are printed out to be accurate.

If an alternative superblock is specified and the filesystem is not opened read-only, e2fsck will make sure that the primary superblock is updated appropriately upon completion of the filesystem check.

In reply to:

---

There isn't even a "mke2fs --dry-run" that tells you where it's putting them.

---

"man mke2fs" says:

-n causes mke2fs to not actually create a filesystem, but display what it would do if it were to create a filesystem.

Does that not tell you where the superblocks are going? What if you also use -v?

Also,looking at the mke2fs manpage, it mentions rebuilding the superblock if you know the right parameters, using the -S option. Anyone know what incantation to use this on the Empeg?

For filesystems with 1k blocksizes, a backup superblock can be found at block 8193; for filesystems with 2k blocksizes, at block 16384; and for 4k blocksizes, at block 32768.

OK, so all those numbers are worth a try for e2fsck -b number.

-n causes mke2fs to not actually create a filesystem, but display what it would do if it were to create a filesystem.

This is exactly what's needed, but didn't IIRC exist in the e2fsprogs 1.18 that car players are built with.

Peter

Ok here's the boot log that Paul requested. This is all new to me so bare with me if I get things incorrect.

Ok here are the results from what Paul suggested to do:

In reply to:

---

empeg:/empeg/bin# swapon /swapfile
Adding Swap: 16596k swap-space (priority -1)
empeg:/empeg/bin# umount /drive0
umount: /drive0: not mounted
empeg:/empeg/bin# fsck -fay /
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda5 is mounted.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda5: 1510/4096 files (0.5% non-contiguous), 9427/16384 blocks
empeg:/empeg/bin# fsck -fay /dev/hda4
Parallelizing fsck version 1.19 (13-Jul-2000)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.
Group descriptors look bad... trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/hda4

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

empeg:/empeg/bin# swapoff
usage: swapoff [-hV]
swapoff -a [-v]
swapoff [-v] [-p priority] special ...
swapoff [-s]

---

Here's the result from what Toby suggested:

empeg:/empeg/bin# e2fsck -b 8193 /dev/hda4
bash: e2fsck: command not found

Oops - my bad! On the empeg, it's called fsck.ext2, not e2fsck. Sorry! Just change the name, and try again.

here's the result:

empeg:/empeg/bin# fsck.ext2 -b 8193 /dev/hda4
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/
hda4 is mounted.
fsck.ext2: Bad magic number in super-block while trying to open /dev/hda4

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

empeg:/empeg/bin#

Well, that's me out of ideas, then. Sorry.

Greetings!

I tried opening the log file, but it gave a 404 error. I remember seeing a similar superblock error when I was trying to fsck and was using the wrong device name.

A possibility - try reloading the default software. Use the upgrade empeg and the stock developer version. This will not do anything to the music partitions, but will reset your system software to a factory state. Also, are you still running hijack?

Maybe this will help someone. Here's the beginning of the what's displayed at HyperTerminal startup:

e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kerne
l.
Linux version 2.2.14-rmk5-np17-empeg50 ([email protected]) (gcc versi
on 2.95.3 20010315 (release)) #7 Fri Feb 8 18:45:38 GMT 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 10101453)
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15024k/16M available (964k code, 20k reserved, 372k 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 206f6972 'rio '
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 d0005d80).
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-220, ATA DISK drive
hda: IBM-DJSA-220, ATA DISK drive
hda: IBM-DJSA-220, ATA DISK drive
hda: IBM-DJSA-220, ATA DISK drive
hda: IBM-DJSA-220, ATA DISK drive
hda: IBM-DJSA-220, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: IBM-DJSA-220, 19077MB w/1874kB Cache, CHS=38760/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:22:05:a
d
Partition check:
hda: hda1 < hda5 hda6 > 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½Õ¹Ñ•‘�ɽ½Ñ�¡•áÑÉ�™¥±•ÍåÍÑ•µ¥�É•…‘½¹±å¹)5ÿchan
ge_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
EXT2-fs error (device ide0(3,4)): ext2_check_descriptors: Block bitmap for group
0 not in group (block 1396520500)!
Remounting filesystem read-only
EXT2-fs: group descriptors corrupted !
Tried to mount /dev/hda4 as ext2 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
player.cpp : 385:empeg-car 2.00-beta11 2002/02/08.
! tags.cpp : 61:Failed to open tags (0xc0041002).
Prolux 4 empeg car - 2.1434 Feb 7 2002
Vcb: 0x4086d000

Greetings!

Hmm... okay... the boot went through okay... filesystem...

What bothers me is that the fsck -fay looks like it attempted to use an alternative superblock and failed. Although, I just tested this on my empeg. The superblock error you are receiving is the NORMAL error if the command string contains an incorrect device. I remember seeing it before....

Hold...

Edit:

Never mind. The first lines for finding the bad descriptor are new. The superblock paragraph is common. Are you at the factory installation at this point?

I've never run Hijack. So should I uninstall 2.0b11 and reinstall 1.03? If so, is there a procedure to uninstall v2.0b11 from the player or that happens automatically when I install v1.03?

Also attatching log file again.

go here for the log file: http://home.socal.rr.com/astroturf/EMPLODE.nfo

I changed the .log to .nfo