Hi

As some of you might know, I am trying to use my Empeg as secondary storage for images taken with my digicam (stored on Compact Flash cards) when I'm away from my computer.
My secondary harddrive is a CompactFlash card connected to the Empeg using an IDE-CF converter. The CF card is FAT formatted and its partition is seen as /dev/hdc1 from the empeg.

I have now run in to a small problem:
I get this message on the serial port when the Empeg boots:

Mounting second music parattempt to access beyond end of device

tition

03:44: rw=0, want=2, limit=0

dev 03:44 blksize=1024 blocknr=1 sector=2 size=1024 count=1

EXT2-fs: unable to read superblock

Tried to mount /dev/hdc4 but got error 22

Error mounting partitions (possibly already mounted)

I have no entries in my /etc/fstab that mounts /dev/hdc1 at boot (I mount & unmount the CF-partition manually using a script).

I could live with this errormessage, if it was only a problem at boot time. But I have now discovered, that when I try to synchronize the Empeg using Emplode, the Empeg reboots,
Emplode returns the following error: "Synchronize failed while checking media" and I get a similar output on the serial port:

e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09

e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09

/sbin/fsck.ext2: Attempt to read block from filesystem resultattempt to access beyond end of device

ed in sho03:44: rw=0, want=2, limit=0

rt read wdev 03:44 blksize=1024 blocknr=1 sector=2 size=1024 count=1

hile trying tEXT2-fs: unable to read superblock

o open /dev/hdc4

Restored terminal settings

Remounting first music partition read-only

Remounting second music partition read-only

No secondary hard disk

Restart code received

Starting player

It seems to me as if something forces a mount and a fsck on /dev/hdc4.
I tried disabling "Filesystem Check on Sync" and disabling the "Search for a second harddrive" using Hijack, but none of it has helped...

Does anyone know, if it is the player application that does this mount or is it "built into" the kernel ?

If it is located in the kernel I could just build my own special kernel with the fix in it (if someone could tell me where to look), as I'm probably the only person on the planet with this specific problem (at least I have now learned how to compile my own Empeg kernels with FAT support, so I won't be bothering you with THAT when the next version of Hijack is released )

Regards
Nicolai