[Galaxy Note 8.0 (Tablet) Original Android Developm] titanshadow:
That is actually very revealing - do you have a 2nd microsd card that you can attempt to load? I'll tell you why...

Here is what a log looks like when it see's a card inserted:

12-12 15:36:20.030 D/Vold ( 1843): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)
12-12 15:36:20.035 D/DirectVolume( 1843): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 17, PARTN 1
12-12 15:36:20.035 D/Vold ( 1843): Volume sdcard1 state changing 2 (Pending) -> 1 (Idle-Unmounted)
12-12 15:36:20.040 D/MountService( 2267): volume state changed for /storage/sdcard1 (removed -> unmounted)
12-12 15:36:20.045 D/MountService( 2267): sendStorageIntent Intent { act=android.intent.action.MEDIA_UNMOUNTED dat=file:///storage/sdcard1 (has extras) } to UserHandle{-1}
12-12 15:36:20.060 I/Vold ( 1843): /dev/block/vold/179:17 being considered for volume sdcard1
12-12 15:36:20.060 D/Vold ( 1843): Volume sdcard1 state changing 1 (Idle-Unmounted) -> 3 (Checking)
12-12 15:36:20.060 D/Vold ( 1843): Trying to get filesystem type for /dev/block/vold/179:17
12-12 15:36:20.060 D/MountService( 2267): volume state changed for /storage/sdcard1 (unmounted -> checking)
12-12 15:36:20.065 D/MountService( 2267): sendStorageIntent Intent { act=android.intent.action.MEDIA_CHECKING dat=file:///storage/sdcard1 (has extras) } to UserHandle{-1}
12-12 15:36:20.080 D/ExternalStorage( 3382): After updating volumes, found 1 active roots
12-12 15:36:20.095 D/MediaScannerReceiver(12481): action: android.intent.action.MEDIA_UNMOUNTED path: /storage/sdcard1
12-12 15:36:21.120 D/Vold ( 1843): Found vfat filesystem on /dev/block/vold/179:17
12-12 15:36:21.135 I/fsck_msdos( 1843): ** /dev/block/vold/179:17
12-12 15:36:21.135 I/fsck_msdos( 1843): Primary/Backup bootblock miscompare
12-12 15:36:21.135 I/fsck_msdos( 1843): Primary:
12-12 15:36:21.135 I/fsck_msdos( 1843): 00 02 40 20 00 02 00 00 00 00 f0 00 00 10 00 04 00 00 00 00 00 00 1c b7 03 b8 1d 00 00 00 00 00 00 02 00 00 00 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 29 ec 1a 83 20 4d 4f 47 48 45 44 49 45 4e 20 20 46 41 54 33 32 20 20 20
12-12 15:36:21.135 I/fsck_msdos( 1843): Backup:
12-12 15:36:21.135 I/fsck_msdos( 1843): 00 02 40 20 00 02 00 00 00 00 f0 00 00 10 00 04 00 00 00 00 00 00 1c b7 03 b8 1d 00 00 00 00 00 00 02 00 00 00 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 29 ec 1a 83 20 4e 4f 20 4e 41 4d 45 20 20 20 20 46 41 54 33 32 20 20 20
12-12 15:36:21.135 I/fsck_msdos( 1843): ** Phase 1 - Read and Compare FATs
12-12 15:36:21.140 I/fsck_msdos( 1843): Attempting to allocate 3804 KB for FAT
12-12 15:36:21.480 I/fsck_msdos( 1843): Attempting to allocate 3804 KB for FAT
12-12 15:36:21.925 I/fsck_msdos( 1843): ** Phase 2 - Check Cluster Chains
12-12 15:36:21.995 I/fsck_msdos( 1843): ** Phase 3 - Checking Directories
12-12 15:36:24.640 I/fsck_msdos( 1843): ** Phase 4 - Checking for Lost Files
12-12 15:36:24.685 I/fsck_msdos( 1843): 4990 files, 1126240 free (166267 clusters)
12-12 15:36:24.725 I/Vold ( 1843): Filesystem check completed OK
12-12 15:36:24.740 W/Vold ( 1843): blkid failed to identify /dev/block/vold/179:17
12-12 15:36:24.740 D/Vold ( 1843): Volume sdcard1 state changing 3 (Checking) -> 4 (Mounted)
12-12 15:36:24.740 D/MountService( 2267): volume state changed for /storage/sdcard1 (checking -> mounted)
12-12 15:36:24.745 E/VoldConnector( 2267): NDC Command {83 volume mount /storage/sdcard1} took too long (4688ms)
12-12 15:36:24.745 D/MountService( 2267): sendStorageIntent Intent { act=android.intent.action.MEDIA_MOUNTED dat=file:///storage/sdcard1 (has extras) } to UserHandle{-1}

So what we see here (if it isn't obvious) is the VOLD service detects that something has been inserted into the card slot. Then it goes about the process of finding out what. The bulk of the log is the fsck service checking the FAT32 partition to see if it can find out if it is a good partition. It is a good partition so the last line shows that the card is mounted. I don't know what the error in there for NDC Command is.

Your log... I do a search in the logcat you provided for "vold" and "mount" or even "fsck" it should find at least something by vold as realizing a card was physically inserted into the storage slot. There is nothing. The only mention of /storage/sdcard1 is here:

12-12 15:13:13.555 D/MtpService(9732): updating state; isCurrentUser=true, mMtpLocked=false
12-12 15:13:13.560 D/MtpService(9732): addStorageLocked 65537 /storage/emulated/0
12-12 15:13:13.560 D/MtpService(9732): addStorageLocked 131073 /storage/sdcard1

Which is probably connecting the device to the computer via USB, at least, I would imagine. What this seems to say is that the tablet isn't even recognizing that the card has been inserted into the slot, doesn't see it at all.

Can you confirm if you actually physically removed the card from the slot and then physically reinserted it? I did have a problem once on my S3 with CM 10.2 in the early days where I had to do that (physically remove and reinsert the card) to get it to work. I didn't get a logcat of the incident but if you've got another card to try, I'd be very interested to see the results.

You said the card is NTFS correct? I know that NTFS is really upsetting for linux systems to read, even with ntfs3g package on an Ubuntu to Red Hat box. But Windows should give you the option to format in FAT, exFAT, or NTFS - the FAT option would be FAT32 as it is greater than the capacity for a FAT16 partition.

---------- Post added at 12:54 PM ---------- Previous post was at 12:49 PM ----------

Can someone confirm if they can send a simply text file via bluetooth to a desktop computer or another device? Mine keeps failing and I need to find out if it is my system or not.