[Galaxy Note 10.1 Q&A, Help & Troubleshooting] AlexFG:
I've been dealing with this problem for a couple of weeks now, I have gathered bits and pieces of information but I've had no luck getting this fixed. I was running a 4.3 release of Omni ROM and everything was running ok till I rebooted into recovery (CWM v6.0.3.6) and it asked me to fix root when I tried to reboot back to android. I did that and the tablet rebooted just fine, however the next morning when I woke up I found it stuck on the Samsung Galaxy Note 10.1 logo. I'm still able to get into recovery and download mode but after installing a few other ROMs through recovery and even returning back to stuck with ODIN, nothing has worked yet. Whenever I install a custom ROM in recovery the installation always completes without errors but once I reboot I can't get past the boot logo. On CWM I'm receiving the following errors: "Error Mounting /data!" and "Error mounting /efs!". On ODIN I have tried to return back to stock with and without a PIT file in hopes of re partitioning everything but still no luck. I have also tried to install a different recovery through CWM and ODIN but even though it always completes successfully, I'm unable to override my old CWM recovery partition.

These are the logs I was able to pull with ADB from Recovery:

/tmp # cat recovery.log
Starting recovery on Fri Jan 13 08:13:39 2012
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v6.0.3.6
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p3 (null) 0
2 /boot emmc /dev/block/mmcblk0p5 (null) 0
3 /recovery emmc /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p8 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p12 (null) -16384
7 /preload ext4 /dev/block/mmcblk0p10 (null) 0
8 /modem emmc /dev/block/mmcblk0p7 (null) 0
9 /sdcard datamedia /dev/null (null) 0
10 /external_sd vfat /dev/block/mmcblk1p1 (null) 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
Warning: No file_contexts
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"

ro.boot.debug_level=0x4f4c
ro.boot.emmc_checksum=3
ro.boot.bootloader=N8013UEUCMB3
ro.boot.serialno=41070cd112309f57
ro.serialno=41070cd112309f57
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=N8013UEUCMB3
ro.hardware=smdk4x12
ro.revision=6
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JDQ39E
ro.build.display.id=cm_n8013-userdebug 4.2.2 JDQ39E eng.hudson.20130824.094402 test-keys
ro.build.version.incremental=eng.hudson.20130824.094402
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Aug 24 09:44:46 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=GT-N8013
ro.product.brand=samsung
ro.product.name=GT-N8013
ro.product.device=GT-N8013
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos4
ro.build.product=GT-N8013
ro.build.description=samsung/p4notewifiue/p4notewifi:4.0.4/IMM76D/N8013UEALH2:user/release-keys
ro.build.fingerprint=samsung/p4noterfxx/p4noterf:4.0.4/IMM76D/N8000XWALG9:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=n8013
dalvik.vm.dexopt-data-only=1
ro.sf.lcd_density=160
ro.lcd_min_brightness=20
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10.1-20130824-UNOFFICIAL-n8013
ro.modversion=10.1-20130824-UNOFFICIAL-n8013
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
Error mounting /data!
W:failed to mount /dev/block/mmcblk0p3 (Invalid argument)
Error mounting /efs!
/tmp #

along with this other info regarding the partitions on my device:

CWM Errors:

Error mounting /data!
Error mounting /efs!

~ # find /dev/block -path \*/by-name -exec ls -l {} \;
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 13 08:04 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 13 08:04 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 13 08:04 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 13 08:04 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Jan 13 08:04 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 13 08:04 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 13 08:04 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 13 08:04 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 13 08:04 USERDATA -> /dev/block/mmcblk0p12

/etc # ls
fstab mtab recovery.fstab

/etc # cat recovery.fstab
# mount point	fstype	device
/efs	ext4	/dev/block/mmcblk0p3
/boot	emmc	/dev/block/mmcblk0p5
/recovery	emmc	/dev/block/mmcblk0p6
/cache	ext4	/dev/block/mmcblk0p8
/system	ext4	/dev/block/mmcblk0p9
/data	ext4	/dev/block/mmcblk0p12 length=-16384
/preload	ext4	/dev/block/mmcblk0p10
/modem	emmc	/dev/block/mmcblk0p7

/sdcard	datamedia /dev/null
/external_sd	vfat	/dev/block/mmcblk1p1

/etc # cat fstab
/dev/block/mmcblk0p8 /cache ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
/dev/null /sdcard datamedia rw
/dev/block/mmcblk1p1 /external_sd vfat rw

~ # ls
cache fstab.smdk4x12 sbin
data init sdcard
default.prop init.rc sys
dev lpm.rc system
efs preload tmp
etc proc ueventd.goldfish.rc
extSdCard res ueventd.rc
external_sd root ueventd.smdk4x12.rc

~ # cat fstab.smdk4x12
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/mmcblk0p3 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p8 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait

# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p12 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer

Any help would be greatly appreciated.

Thanks in advance.