Author Topic: mSATA USB Enclosure, not recognized.  (Read 1730 times)

nik282000

  • Full Member
  • ***
  • Posts: 103
    • View Profile
mSATA USB Enclosure, not recognized.
« on: January 02, 2020, 03:36:12 PM »
I had an mSATA drive laying around and I thought I might get better saving speeds from my Chronos. When I plug the drive in it is not recognized by the camera. All of my conventional USB drives are recognized just fine (from 16gb to 128gb in size).

The Chronos is running the latest firmware v0.3.2-patch1. The drive is an mSATA, Samsung 860 EVO, 250gb. The enclosure is an HD6011-1s (Amazon, eBay, Alli), its based around the JMS578  USB 3.0 to SATA 6.0Gb/s Bridge Controller.

I tried formatting the drive to both FAT32 and EXT3, I also tried making the partition smaller (120gb) with the same results.

If anyone has any ideas as to what I can test or check next I would very much appreciate it.

nik282000

  • Full Member
  • ***
  • Posts: 103
    • View Profile
Re: mSATA USB Enclosure, not recognized.
« Reply #1 on: March 12, 2020, 02:07:28 PM »
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!

Quote
---------------------------------------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 uas

Then create a new file: /etc/modprobe.d/blacklist-uas.conf, with the line

blacklist uas

This doesn't seem to have broken anything, your mileage may vary, I'm not sure if the RW speeds will be affected.
« Last Edit: March 12, 2020, 06:01:35 PM by nik282000 »