I've been having problems with my rio the last couple of days. I first posted in the "bug report" area...the thread titled "Player hangs during emplode startup" if anyone wants to check out the error messages.

Summary:
I started having problems sync'ing a few days ago after the player working fine for about a month or so (many gigs transferred onto and off of it).
The player would work ok when using it directly (though startup seemed to take an excessive amount of time, with much of that stalled on a 'building database' message)
However I couldn't seem to get emplode to sync at all.

First I downgraded from beta11 to 1.03 (some thread said that might help)....but it didn't do anything.
Then I checked the cables/jumpers as per reccommendations. They seem fine as far as I can tell. I made sure they seemed seated well.
Then I used the builder tool to totally erase/rebuild the drives. Put 1.03 back on. Still getting some errors on startup so I tried beta11 and an fsck.
The results of the fsck are below (there are errors)
The results of startup and sync are below (there are errors)
However, I can now seem to sync and use the player. I'm a little worried, however, since some of the errors still appear to indicate problems locating mounting drives (even though the full amount of space shows up on emplode).

Does anyone know what's going on and/or have advice? Things *seem* ok now, but I'm a bit worried by the different messages and am wondering what I can do to make sure everything is working properly before starting the process of loading the music back on and recreating the playlists, etc.
Thank You
-J
****************
//**********************
//trying fsck
//**********************
empeg:/empeg/bin# ro
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 /drive0
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.
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/hda4: 20/228288 files (0.0% non-contiguous), 37727/29219400 blocks

empeg:/bin# fsck -fay /drive1
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 /driv
e1 is mounted.
fsck.ext2: Is a directory while trying to open /drive1

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>

//**********************
//restarting (beta11)
//**********************
empeg pow
empeg:/bin#r initialis
empeg-car bootstrap v1.02 20001106 ([email protected])SU MHL2300AT, 28615MB w/2048kB Cache, CHS=58140/16/
If there is anyone present who wants to upgrade the flash, let them speak now,
hdb: FUJITSU MHL2300AT, 28615MB w/2048kB Cache, CHS=58140/16/63
or forever hold their peace...it seems not. Let fly the Penguins of Linux! 46): Poll result=0 on fd=546):

e000 v1.04mpeg-flash
Copying kernel...d
Calling linux kernel...
smc chip id/r
Uncompressing Linux...................................

RAMDISK: Loading 320 blocks [1 d
Processor: Intel StrongARM-1100 revision 11on fd=5ess.cpp 189 ( 46): Poll result=
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
EXT2-fs warning: checktim
empeg-car player (hardware revision 9, serial number 40103876)
Stressing /dev/hda:
Command line: mem=16mS: Mounted root (ext2
Calibrating delay loop... 207.67 BogoMIPS
Speed
empeg-pump v0.03 (1998
Memory: 15024k/16M available (964k code, 20k reserved, 372k data, 4k init)nter pump...VFS: Mounted root (ext2 filesystem) readonly.9 ( 46):
Dentry hash table entries: 2048 (order 2, 16k)

g player
empeg-car 1.03.
Linux-IrDA: IrCOMM protocol ( revision:Tue May 18 03:11:39 1999 )g up.5
3
ircomm_tty: virtual tty driver for IrCOMM ( revision:Wed May 2
hds
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UARTer 46

3
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART2 DHCP Received DHCPOFFER
Signature is 67706d65 'empg'
3cb85d72 DHCP siaddr=000000
Scheduling custom logo.ip=0101a8c0ll result=0
empeg display initialised.
empeg dsp audio initialised
3cb85d72
empeg dsp mixer initialised92.168.1.103 from server 19
empeg dsp initialisedning up.ng /de
empeg audio-in initialised, CS4231A revision a0
h
empeg remote control/panel button initialised.8c9591

empeg usb initialised, PDIUSBD12

hd
3cb85d72 DH
hda: FUJITSU MHL2300AT, ATA DISK drivecip=0101a8c0
hdb: FUJITSU MHL2300AT, ATA DISK driveressing /dev/hda: Spinning up.ult=0
ide0 at 0x000-0x007,0x038 on irq 63cb85d72 DHCP Re-accepting duplica
hda: FUJITSU MHL2300AT, 28615MB w/2048kB Cache, CHS=58140/16/63

hdb: FUJITSU MHL2300AT, 28615MB w/2048kB Cache, CHS=58140/16/63
68.1.1
Partition check:
hda: hda1 < hda5 hda6 > hda2 hda3 hda4
hdb: hdb1 < hdb5 hdb6 > hdb2 hdb3 hdb4
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: Mounted root (ext2 filesystem) readonly.
change_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
Mounting second music partition
Remounting first music partition read-only
Remounting second music partition read-only
Press 'q' now to go into development mode. You Have Zero Seconds To Comply...
Starting player
player.cpp : 385:empeg-car 2.00-beta11 2002/02/08.
Prolux 4 empeg car - 2.1434 Feb 7 2002
Vcb: 0x4086d000

//**********************
//synch'ing with emplode
//**********************
Adding Swap: 16596k swap-space (priority -1)
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.
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/
hdc4 is mounted.
Restored terminal settings
Remounting first music partition read-only
Remounting second music partition read-only
Restart code received
Starting player
player.cpp : 385:empeg-car 2.00-beta11 2002/02/08.
Prolux 4 empeg car - 2.1434 Feb 7 2002
Vcb: 0x4086d000

Then I checked the cables/jumpers as per reccommendations. They seem fine as far as I can tell. I made sure they seemed seated well.

A bad crimp (ribbon cable to connector connection) isn't really visible, so it could still be the cable...

ext2fs_check_if_mount: No such file or directory while determining whether /dev/hdaX is mounted

Not a problem, the empeg simply doesn't have (by design) the /etc/mtab file which fsck tries to check to see if the filesystem to test is mounted or not.

fsck.ext2: Is a directory while trying to open /drive1

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>

Does your empeg have 2 drives? If not, /drive1 is just a directory, not a place where to find a mounted filesystem.

Hmmm, looking at the boot log you do seem to have 2 drives. The boot log looks corrupted though (attached my boot log as comparison - using hijack and picker, so it's slightly more things in there)

If I were you I'd probably see if I could make each disk work properly alone (one drive player configuration). Test both connectors on teh IDE cable too - the bad crimp seems to be only on the middle connector.

/Michael

David Moss seems to think that I should replace the cable...so we'll see if that straightens things out.

-J