Really bad FS errors on mmcblk0p24

[eris170]

Hello. I was in the process of going from Stock GB on my T989 to JB but got caught in a boot loop using CM-10.1.2. I then tried flashing CM-10.0.0 and CM-9.1 however neither of them completed booting either. I ended up restoring from my CWM backup and everything appeared fine. I booted into recovery and tried to run a second backup but it locked up. Getting into the device over adb I ran dmesg and found this:

<4>[ 71.804931] EXT4-fs (mmcblk0p24): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 71.808410] zcache: created ephemeral tmem pool, id=1, client=65535
<6>[ 71.808746] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mode. Opts:
<2>[ 75.416381] EXT4-fs error (device mmcblk0p24): ext4_init_inode_table:1296: comm ext4lazyinit: Something is wrong with group 0
<2>[ 75.416412] Used itable blocks: 479itable unused count: 0
<2>[ 75.416442]
<3>[ 75.848297] Aborting journal on device mmcblk0p24-8.
<2>[ 75.862945] EXT4-fs (mmcblk0p24): Remounting filesystem read-only
<6>[ 157.712677] zcache: destroyed pool id=1, cli_id=65535

When I tried running e2fsck on mmcblk0p24 I got many errors and not sure if it's fixable:

(some output snipped for brevity)
HTREE directory inode 15291 has an invalid root node.
Clear HTree index? no
Inode 15291, i_size is 1479702133161773, should be 0. Fix? no
Inode 15291, i_blocks is 343944, should be 0. Fix? no
Inode 15292 has illegal block(s). Clear? no

Illegal block #0 (345615) in inode 15292. IGNORED.
Illegal block #1 (345628) in inode 15292. IGNORED.
Illegal block #2 (345728) in inode 15292. IGNORED.
Illegal block #3 (345756) in inode 15292. IGNORED.
Illegal block #4 (345789) in inode 15292. IGNORED.
Illegal block #5 (345808) in inode 15292. IGNORED.
Illegal block #6 (345826) in inode 15292. IGNORED.
Illegal block #7 (345841) in inode 15292. IGNORED.
Illegal block #8 (345857) in inode 15292. IGNORED.
Illegal block #9 (345874) in inode 15292. IGNORED.
Illegal block #10 (345887) in inode 15292. IGNORED.
Too many illegal blocks in inode 15292.
Clear inode? no

Suppress messages? no

Illegal block #11 (345904) in inode 15292. IGNORED.
Illegal indirect block (345923) in inode 15292. IGNORED.
Illegal double indirect block (345932) in inode 15292. IGNORED.
Illegal triple indirect block (345946) in inode 15292. IGNORED.
Error while iterating over blocks in inode 15292: Illegal triply indirect block found
e2fsck: aborted
~ #

When I mount the partition, I can see some system directories on it which I assume are the stock GB Samsung files:

~ # mount /dev/block/mmcblk0p24 /mnt -o ro
~ # ls mnt
CSCFiles.txt build.prop lost+found
CSCVersion.txt csc media
SW_Configuration.xml etc tts
T9DB fonts usr
app framework vsc
bin lib xbin

What should I do next here? I could format the partition but that's pretty much going to hose the installed ROM. It's likely screwed anyway but trying to figure out what the best option is. CWM is working and I think that's on partition mmcblk0p22 so possibly I could format mmcblk0p24 to fix the errors and then re-flash Cyanogenmod from CWM? Gah! Please help!