So, I recently installed a single 256GB Samsung mSATA card into a 44-pin 2.5" IDE adapter card with a JM20330 bridge chip in my MKIIa and have had some odd superblock mis-match issues when trying to 'rwm' and 'fsck'. I can absolutely not get 'fsck' to run on the disk. This happens when running either Developer 2.01 or Developer v3a11. Here's the gist of what's happening here when I try to mount 'rwm.'

Code:
EXT2-fs error (device ide0(3,4)): read_inode_bitmap: Cannot read inode bitmap - block_group = 1905, inode_bitmap = 62423041
attempt to access beyond end of device
03:04: rw=0, want=249823240, limit=134110620
dev 03:04 blksize=4096 blocknr=62455809 sector=499646472 size=4096 count=1
EXT2-fs error (device ide0(3,4)): read_inode_bitmap: Cannot read inode bitmap - block_group = 1906, inode_bitmap = 62455809
EXT2-fs error (device ide0(3,4)): ext2_check_inodes_bitmap: Wrong free inodes count in super block, stored = 971251, counted = 519155


It's actually quite a bit longer than that as it reports every missing block, but essentially it looks like the superblock thinks the device is half the size that it really is, and fails to "access beyond end of device." Funny that this happens, as sometimes after I've run the BigDiskv6 and installed either v2.01 or v3a11, the unit recognizes only 147GB or so, which it can actually handle without error. If I re-image, it will recognize all 256GB available, but error out on what I can only presume is the last ~100GB of the disc. What the heck?

For the record, this is what happens when I attempt to fsck.

Code:
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.
The filesystem size (according to the superblock) is 62486825 blocks
The physical size of the device is 33527655 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes


So given that each block is 4096k, then the physical size is 33527655x4096=137329274880, or 137GB. Filesystem size would be 62486825x4096=255946031104, or 256GB. So, there's the problem. But, why the problem? It's reporting the physical size as roughly half the actual capacity. Oh and I tried a second, identical mSATA card. Same story. I tried a second, identical adapter card. Same story. They all format to a beautiful 256GB on a normal x86 machine, through the same interfaces. So I feel safe saying there's no faulty equipment here.

Any thoughts?