Update, in case some future person googles this.
I checked dmesg over SSH while plugging in my not-working mSata enclosure and a normal USB stick.
It seems like the camera doesn't recognize it as mass storage.
I will keep working on it, now that I have SSH access it should go much easier. Thanks Chronos Dev Team!
---------------------------------------Plugged in "Bad" USB Enclosure
[ 0.000000] usbcore: registered new interface driver uas
[ 0.000000] Initializing USB Mass Storage driver...
[ 0.000000] usbcore: registered new interface driver usb-storage
[ 0.000000] USB Mass Storage support registered.
[ 0.000000] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
[ 0.000000] ti81xx_interrupt 1146: VBUS error workaround (delay coming)
[ 0.000000] usb 1-1: new high-speed USB device number 3 using musb-hdrc
[ 0.000000] usb 1-1: New USB device found, idVendor=152d, idProduct=0578
[ 0.000000] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 0.000000] usb 1-1: Product: JMS579
[ 0.000000] usb 1-1: Manufacturer: JMicron
[ 0.000000] usb 1-1: SerialNumber: 341DE20B4122112
[ 0.000000] scsi2 : uas
[ 0.000000] blk_queue_max_segments: set to minimum 1
[ 0.000000] scsi 2:0:0:0: uas_eh_abort_handler tag -1
[ 0.000000] scsi 2:0:0:0: uas_eh_device_reset_handler tag -1
[ 0.000000] scsi 2:0:0:0: uas_eh_target_reset_handler tag -1
[ 0.000000] scsi 2:0:0:0: uas_eh_bus_reset_handler tag -1
[ 0.000000] usb 1-1: URB BAD STATUS -71
[ 0.000000] usb 1-1: reset high-speed USB device number 3 using musb-hdrc
[ 0.000000] scsi 2:0:0:0: Device offlined - not ready after error recovery
----------------------------------------------------------Unplugged "Bad" USB enclosure
[ 0.000000] usb 1-1: USB disconnect, device number 3
----------------------------------------------------------Plugged in Good USB stick
[ 0.000000] usb 1-1: new high-speed USB device number 4 using musb-hdrc
[ 0.000000] usb 1-1: New USB device found, idVendor=0781, idProduct=5583
[ 0.000000] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 0.000000] usb 1-1: Product: Ultra Fit
[ 0.000000] usb 1-1: Manufacturer: SanDisk
[ 0.000000] usb 1-1: SerialNumber: 4C531001581114116183
[ 0.000000] scsi3 : usb-storage 1-1:1.0
[ 0.000000] scsi 3:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6
[ 0.000000] sd 3:0:0:0: Attached scsi generic sg0 type 0
[ 0.000000] sd 3:0:0:0: [sda] 242614272 512-byte logical blocks: (124 GB/115 GiB)
[ 0.000000] sd 3:0:0:0: [sda] Write Protect is off
[ 0.000000] sd 3:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 0.000000] sd 3:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 0.000000] sda: sda1
[ 0.000000] sd 3:0:0:0: [sda] Attached SCSI removable disk
[ 0.000000] kjournald starting. Commit interval 5 seconds
[ 0.000000] EXT3-fs (sda1): using internal journal
[ 0.000000] EXT3-fs (sda1): mounted filesystem with writeback data mode
*EDIT*Found a potential fix by disabling uas (USB attached scsi).
$rmmod uasThen create a new file: /etc/modprobe.d/blacklist-uas.conf, with the line
blacklist uasThis doesn't seem to have broken anything, your mileage may vary, I'm not sure if the RW speeds will be affected.