(04-02-2017, 01:05 PM)dkryder Wrote: many drives have proprietary software that is used by the O/S to achieve the performance ratings that are given for the device. it's not so much a driver as it is a helper app, at least on windows, not sure how linux handles it if in fact linux supports it at all but i have had usb drives that would not run at all unless the drive software was first installed on windows units and i'm wondering if this may be a drive that operates via installed software?
The drive works in another SBC, using a similar Linux kernel and SoC. I also tried the Android Pine image and that failed, as well. It also works in any laptop/desktop I've tried. I don't think drivers are the issue. I also checked the SSD's firmware and updated it to the latest.
(04-01-2017, 09:01 PM)pfeerick Wrote: Just some questions to try and gather some more information...
Did the Kingston drive work on those USB-SATA controllers on the other SBC? Did this happen when you tried mounting it... or when you were trying to boot from it? And no indication from the dmesg output as to what was going on? Did it report the Kingston drive detected at all? Maybe compare the dmesg output when connecting the USB-SATA controller with another SSD, and see what difference this is in the messages, if any?
Other SBC:
- The drive works, using any of the USB-SATA adapters.
- I did a full test, partitioning, copying and verifying data.
I tried three different USB-SATA interfaces.
- The drive is never available as a device. It is detected (according to dmesg) by never "ready".
- One interface times out and the other two continually disconnect and reconnect the device.
[ 116.755832] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 116.758762] scsi0 : usb-storage 1-1:1.0
[ 117.738320] scsi 0:0:0:0: Direct-Access SABRENT 4101 PQ: 0 ANSI: 6
[ 123.009510] sd 0:0:0:0: [sda] Unit Not Ready
[ 123.009524] sd 0:0:0:0: [sda]
[ 123.009529] Sense Key : 0x4 [current]
[ 123.009537] sd 0:0:0:0: [sda]
[ 123.009542] ASC=0x44 <<vendor>> ASCQ=0x8
The repeated I/O detect and drop looks like this (from dmesg):
[ 284.691383] ehci_irq: highspeed device connect
[ 284.911185] usb 1-1: new high-speed USB device number 35 using sunxi-ehci
[ 285.061345] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 285.061619] scsi33 : usb-storage 1-1:1.0
[ 286.043989] scsi 33:0:0:0: Direct-Access Generic External 0205 PQ: 0 ANSI: 6
[ 286.048014] sd 33:0:0:0: [sda] Attached SCSI removable disk
[ 286.348514] ehci_irq: highspeed device disconnect
[ 286.348636] usb 1-1: USB disconnect, device number 35
[ 287.082449] ehci_irq: highspeed device connect
[ 287.302291] usb 1-1: new high-speed USB device number 36 using sunxi-ehci
Working state, dmesg output from two USB-SATA interfaces on the other SBC:
Interface 1:
[ 31.092689] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 31.092905] scsi1 : usb-storage 1-1.3:1.0
[ 32.088598] scsi 1:0:0:0: Direct-Access KINGSTON SH103S3240G 526A PQ: 0 ANSI: 6
[ 32.089867] sd 1:0:0:0: [sda] 468862124 512-byte logical blocks: (240 GB/223 GiB)
[ 32.090462] sd 1:0:0:0: [sda] Write Protect is off
[ 32.090477] sd 1:0:0:0: [sda] Mode Sense: 31 00 00 00
[ 32.091102] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 32.097106] sda: sda1
[ 32.099836] sd 1:0:0:0: [sda] Attached SCSI disk
Interface 2:
[ 82.707754] usb 1-1.3: new high-speed USB device number 8 using dwc_otg
[ 82.889240] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[ 82.889435] scsi2 : usb-storage 1-1.3:1.0
[ 83.888146] scsi 2:0:0:0: Direct-Access SABRENT 4101 PQ: 0 ANSI: 6
[ 84.599067] sd 2:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/223 GiB)
[ 84.599680] sd 2:0:0:0: [sda] Write Protect is off
[ 84.599686] sd 2:0:0:0: [sda] Mode Sense: 47 00 00 08
[ 84.600301] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 84.603480] sda: sda1
[ 84.606342] sd 2:0:0:0: [sda] Attached SCSI disk