Compact Flash as Drive

I've seen this done before so I know it works, but it's not working for me and I can't find anything in searches. I built the drive using the builder then loaded the developer image, but Emplode crashes if I try to sync it. I'm using a 128 GB CF card in an IDE adapter set to master. Here is the terminal output:

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...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 /dVFS: Can't find an ext2 filesystem on dev ide0(3,4).
ev/hda4 as reiserfs but got error 19
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 ComStarting player
player.cpp : 385:empeg-car 2.00 2003/04/01.
! tags.cpp : 61:Failed to open tags (0xc0041002).
Prolux 4 empeg car - 2.1434 Mar 26 2003
Vcb: 0x4054d000

Has anyone gotten this to work that can describe the process?

It's the 128GB part that is the trouble.

This normally requires a Hijack kernel to have any chance of working.

EDIT: or maybe not.. it's drives LARGER than 128 * 1024 * 1024 * 1024 (128GB) that have such issues.

It appears from the posted logs that the CF card is working fine. But it also seems that the builder image hasn't done its thing. The /fids/ subdirectories are probably not there, or their partitions have not been formatted.

Try redoing the builder?
Use the "big disk" version?

Thanks! I've tried the standard builder 4x with the same result and the big builder got stuck on making the drive. How long should the big builder take to make the hda4 (I think that's the message I saw)? I left it for half an hour and it was still going.

Thanks again,
Stu

Mmmm.. not sure, but you'd think half an hour would have done it.

I haven't run a builder for maybe 6-7yrs?
Anything useful on the serial port while the builder is running?

Haha. Me either. It consistently stops at inode table 107.

Freeing unused kernel memory: 4k initBuilder image
show_message("Builder image")
Setting up swapspace version 0, size = 16412672 bytes
Adding Swap: 16028k swap-space (priority -1)
Setting up swapspace version 0, size = 24670208 bytes
Adding Swap: 24092k swap-space (priority -2)
Tuning hda5
show_message("Tuning hda5")
tune2fs 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
Setting maximal mount count to -1
Setting interval between check 0 seconds
Making hda4 filesysteshow_message("Making hda4 filesystem")
m
mke2fs 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda4 is mounted.
Linux ext2 filesystem format
Filesystem label=
492544 inodes, 31495432 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Block size=4096 (log=2)
Fragment size=4096 (log=2)
962 block groups
32768 blocks per group, 32768 fragments per group
512 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872,

Writing inode tables: 107/962

Lots of swap space there, so it shouldn't be running out of virtual memory.

Does it really get stuck, or just pause for a very long time?

The slower CF cards I used here take forever to write to, and the inode tables involve tons of writes.

It did finally finish and all is well now! It was a combination of using the bigbuilder and giving it more time.

Thanks for pointing me in the right direction!

Stu