06-22-2018, 03:25 AM
Hello everyone,
I experience poor USB3 performance with my rock64 (apparently it happens to other too...)
My setup : - stretch-openmediavault-rock64-0.6.44-239-armhf
- Seagate 3TB USB3 HDD in NTFS (good perf, at least 100MB/s r/w over windows)
The drive have been mounted through omv, and is accessible in samba and ftp.
In any case i get poor speeds (from 10MB/s to 15MB/s)
LAN with my computer is ok (900 to 1000MB/s)
I don't know what's wrong, any help would be great 
First things first: are you sure it's plugged into the USB3 port (blue one by itself)? The other two are just USB2.
Also, could you run this and give us the output?:
Community administrator and sysadmin for PINE64
(Translation: If something breaks on the website, forum, or chat network, I'm a good person to yell at about it)
Yes I'm sur for the USB 3 port
Here is the what you asked for :
Code: dmesg | grep usb
[ 0.550157] usbcore: registered new interface driver usbfs
[ 0.550266] usbcore: registered new interface driver hub
[ 0.550424] usbcore: registered new device driver usb
[ 1.082156] phy phy-ff450000.syscon:usb2-phy@100.0: Looking up phy-supply from device tree
[ 1.082180] phy phy-ff450000.syscon:usb2-phy@100.0: Looking up phy-supply property in node /syscon@ff450000/usb2-phy@100/host-port failed
[ 1.082648] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up phy-supply from device tree
[ 1.082671] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up phy-supply property in node /syscon@ff450000/usb2-phy@100/otg-port failed
[ 1.083103] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up vbus-supply from device tree
[ 1.083126] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up vbus-supply property in node /syscon@ff450000/usb2-phy@100/otg-port failed
[ 1.083150] phy phy-ff450000.syscon:usb2-phy@100.1: Failed to get VBUS supply regulator
[ 1.084092] rockchip-u3phy ff470000.usb3-phy: Looking up vbus-supply from device tree
[ 1.084115] rockchip-u3phy ff470000.usb3-phy: Looking up vbus-supply property in node /usb3-phy@ff470000 failed
[ 1.084139] rockchip-u3phy ff470000.usb3-phy: Failed to get VBUS supply regulator
[ 1.084620] phy phy-ff470000.usb3-phy.2: Looking up phy-supply from device tree
[ 1.084638] phy phy-ff470000.usb3-phy.2: Looking up phy-supply property in node /usb3-phy@ff470000/utmi@ff470000 failed
[ 1.085079] phy phy-ff470000.usb3-phy.3: Looking up phy-supply from device tree
[ 1.085100] phy phy-ff470000.usb3-phy.3: Looking up phy-supply property in node /usb3-phy@ff470000/pipe@ff478000 failed
[ 1.086875] rockchip-u3phy ff470000.usb3-phy: Rockchip u3phy initialized successfully
[ 1.292556] usbcore: registered new interface driver udl
[ 1.485211] usbcore: registered new interface driver cdc_ether
[ 1.493892] usbcore: registered new interface driver rndis_host
[ 1.504455] phy phy-ff470000.usb3-phy.2: u3phy u2 power on
[ 1.512861] phy phy-ff470000.usb3-phy.3: u3phy u3 power on
[ 1.522161] dwc2 ff580000.usb: Looking up vusb_d-supply from device tree
[ 1.522183] dwc2 ff580000.usb: Looking up vusb_d-supply property in node /usb@ff580000 failed
[ 1.522203] ff580000.usb supply vusb_d not found, using dummy regulator
[ 1.530563] dwc2 ff580000.usb: Looking up vusb_a-supply from device tree
[ 1.530584] dwc2 ff580000.usb: Looking up vusb_a-supply property in node /usb@ff580000 failed
[ 1.530601] ff580000.usb supply vusb_a not found, using dummy regulator
[ 1.551277] dwc2 ff580000.usb: DWC OTG Controller
[ 1.559102] dwc2 ff580000.usb: new USB bus registered, assigned bus number 1
[ 1.567084] dwc2 ff580000.usb: irq 41, io mem 0xff580000
[ 1.575024] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.582825] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.590636] usb usb1: Product: DWC OTG Controller
[ 1.598118] usb usb1: Manufacturer: Linux 4.4.126-rockchip-ayufan-239 dwc2_hsotg
[ 1.606005] usb usb1: SerialNumber: ff580000.usb
[ 1.655558] ehci-platform ff5c0000.usb: EHCI Host Controller
[ 1.663325] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 2
[ 1.671246] ehci-platform ff5c0000.usb: irq 42, io mem 0xff5c0000
[ 1.683844] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00
[ 1.691539] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.699055] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.706586] usb usb2: Product: EHCI Host Controller
[ 1.713859] usb usb2: Manufacturer: Linux 4.4.126-rockchip-ayufan-239 ehci_hcd
[ 1.721460] usb usb2: SerialNumber: ff5c0000.usb
[ 1.760421] ohci-platform ff5d0000.usb: Generic Platform OHCI controller
[ 1.768499] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3
[ 1.776596] ohci-platform ff5d0000.usb: irq 43, io mem 0xff5d0000
[ 1.839103] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.847091] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.855100] usb usb3: Product: Generic Platform OHCI controller
[ 1.862999] usb usb3: Manufacturer: Linux 4.4.126-rockchip-ayufan-239 ohci_hcd
[ 1.871119] usb usb3: SerialNumber: ff5d0000.usb
[ 1.929932] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.938161] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.946403] usb usb4: Product: xHCI Host Controller
[ 1.954490] usb usb4: Manufacturer: Linux 4.4.126-rockchip-ayufan-239 xhci-hcd
[ 1.962873] usb usb4: SerialNumber: xhci-hcd.9.auto
[ 2.006145] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM.
[ 2.015045] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
[ 2.023594] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.032188] usb usb5: Product: xHCI Host Controller
[ 2.040501] usb usb5: Manufacturer: Linux 4.4.126-rockchip-ayufan-239 xhci-hcd
[ 2.049091] usb usb5: SerialNumber: xhci-hcd.9.auto
[ 2.076879] usbcore: registered new interface driver iforce
[ 2.085405] usbcore: registered new interface driver xpad
[ 2.094193] usbcore: registered new interface driver usbtouchscreen
[ 2.337775] usbcore: registered new interface driver uvcvideo
[ 2.403018] usbcore: registered new interface driver bfusb
[ 2.410310] usbcore: registered new interface driver btusb
[ 2.602347] of_get_named_gpiod_flags: parsed 'gpios' property of node '/switches/usb-switch[0]' - status (0)
[ 2.612360] usbcore: registered new interface driver usbhid
[ 2.620782] usbhid: USB HID core driver
[ 2.651309] usbcore: registered new interface driver snd-usb-audio
[ 3.000891] usb 5-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 3.016760] usb 5-1: New USB device found, idVendor=0bc2, idProduct=3320
[ 3.020843] usb 5-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 3.024969] usb 5-1: Product: Expansion Desk
[ 3.028799] usb 5-1: Manufacturer: Seagate
[ 3.032544] usb 5-1: SerialNumber: NA4K7DGB
[ 3.571243] usb 5-1: UAS is blacklisted for this device, using usb-storage instead
[ 3.575120] usb-storage 5-1:1.0: USB Mass Storage device detected
[ 3.579330] usb-storage 5-1:1.0: Quirks match for vid 0bc2 pid 3320: 2000000
[ 3.583451] scsi host0: usb-storage 5-1:1.0
[ 3.587591] usbcore: registered new interface driver usb-storage
[ 3.592426] usbcore: registered new interface driver uas
Hi,
The drives UAS support is blacklisted (i.e. it's known to have issues) and then the usb-storage class driver as a known quirk listed as well. That is why the kernel is downgrading the drives throughput. As it's a drive aimed at the desktop market I suspect Seagate/Microsoft have resolved any compatibility issues under windows.
Code: [ 3.571243] usb 5-1: UAS is blacklisted for this device, using usb-storage instead
[ 3.575120] usb-storage 5-1:1.0: USB Mass Storage device detected
[ 3.579330] usb-storage 5-1:1.0: Quirks match for vid 0bc2 pid 3320: 2000000
I use the word drive to mean the products SATAIII to USB3 controller. I stripped the HDD out of the original desktop enclosure I had with the same issues and put it in a USB3 External drive enclosure that is know to work with Linux and the Rock64. Be warned this would invalidate your warranty on the Seagate Expansion Desk.
Hi, thanks for the answer !
So if I understand well, I can't do anything except extracting the HDD and putting it in a new enclosure ?
Nothing suprises me anymore about this Seagate drive... I had trouble to format this drive in the past because it seems like it is 2 disks (1TB+2TB) being united into 1 disk, certainly with a built-in software.
I'll try later with a drive from a friend (samsung M3 1TB) and see if it changes something...
You might want to consider formating the drive partition to ext4 format first. You are paying a performance penalty using NTFS on a Linux environment.
Yes I know about that, I tried in the past, but I almost bricked the drive during formating due to its conception... And I need both Linux and Windows system...
Due to what have been sais in other threads, it seems that ntfs drives with rock64 can reach pretty good perf. I'll try with another drive to see what happend
06-26-2018, 09:25 AM
(This post was last modified: 06-26-2018, 09:42 AM by edupv.)
For your reference :
I upload files from Windows PC (filezilla) to Rock64 ftp server, WD 2.5" harddisk (ext4 or btrfs format) in an USB3.0 enclosure, uas enabled, speed is around 50MB-60MB/sec.
So from the Samsung M3 Portable 1TB:
Through Samba :
Through FTP :
The two drive are behind a 3.0 hub (this one : https://www.amazon.com/UGREEN-Portable-M...B00OQ0CYFE) with an external power supply.
Code: dmesg | grep usb
[ 0.550694] usbcore: registered new interface driver usbfs
[ 0.550804] usbcore: registered new interface driver hub
[ 0.550960] usbcore: registered new device driver usb
[ 1.082771] phy phy-ff450000.syscon:usb2-phy@100.0: Looking up phy-supply fro m device tree
[ 1.082795] phy phy-ff450000.syscon:usb2-phy@100.0: Looking up phy-supply pro perty in node /syscon@ff450000/usb2-phy@100/host-port failed
[ 1.083289] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up phy-supply fro m device tree
[ 1.083312] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up phy-supply pro perty in node /syscon@ff450000/usb2-phy@100/otg-port failed
[ 1.083735] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up vbus-supply fr om device tree
[ 1.083756] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up vbus-supply pr operty in node /syscon@ff450000/usb2-phy@100/otg-port failed
[ 1.083779] phy phy-ff450000.syscon:usb2-phy@100.1: Failed to get VBUS supply regulator
[ 1.084712] rockchip-u3phy ff470000.usb3-phy: Looking up vbus-supply from dev ice tree
[ 1.084735] rockchip-u3phy ff470000.usb3-phy: Looking up vbus-supply property in node /usb3-phy@ff470000 failed
[ 1.084757] rockchip-u3phy ff470000.usb3-phy: Failed to get VBUS supply regul ator
[ 1.085237] phy phy-ff470000.usb3-phy.2: Looking up phy-supply from device tr ee
[ 1.085256] phy phy-ff470000.usb3-phy.2: Looking up phy-supply property in no de /usb3-phy@ff470000/utmi@ff470000 failed
[ 1.085695] phy phy-ff470000.usb3-phy.3: Looking up phy-supply from device tr ee
[ 1.085715] phy phy-ff470000.usb3-phy.3: Looking up phy-supply property in no de /usb3-phy@ff470000/pipe@ff478000 failed
[ 1.087469] rockchip-u3phy ff470000.usb3-phy: Rockchip u3phy initialized succ essfully
[ 1.293108] usbcore: registered new interface driver udl
[ 1.485896] usbcore: registered new interface driver cdc_ether
[ 1.494583] usbcore: registered new interface driver rndis_host
[ 1.505153] phy phy-ff470000.usb3-phy.2: u3phy u2 power on
[ 1.513552] phy phy-ff470000.usb3-phy.3: u3phy u3 power on
[ 1.522842] dwc2 ff580000.usb: Looking up vusb_d-supply from device tree
[ 1.522866] dwc2 ff580000.usb: Looking up vusb_d-supply property in node /usb @ff580000 failed
[ 1.522885] ff580000.usb supply vusb_d not found, using dummy regulator
[ 1.531272] dwc2 ff580000.usb: Looking up vusb_a-supply from device tree
[ 1.531293] dwc2 ff580000.usb: Looking up vusb_a-supply property in node /usb @ff580000 failed
[ 1.531310] ff580000.usb supply vusb_a not found, using dummy regulator
[ 1.551954] dwc2 ff580000.usb: DWC OTG Controller
[ 1.559777] dwc2 ff580000.usb: new USB bus registered, assigned bus number 1
[ 1.567751] dwc2 ff580000.usb: irq 41, io mem 0xff580000
[ 1.575662] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.583461] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 1.591273] usb usb1: Product: DWC OTG Controller
[ 1.598751] usb usb1: Manufacturer: Linux 4.4.126-rockchip-ayufan-239 dwc2_hs otg
[ 1.606635] usb usb1: SerialNumber: ff580000.usb
[ 1.656086] ehci-platform ff5c0000.usb: EHCI Host Controller
[ 1.663848] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 2
[ 1.671767] ehci-platform ff5c0000.usb: irq 42, io mem 0xff5c0000
[ 1.684374] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00
[ 1.692099] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.699608] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 1.707130] usb usb2: Product: EHCI Host Controller
[ 1.714395] usb usb2: Manufacturer: Linux 4.4.126-rockchip-ayufan-239 ehci_hc d
[ 1.721993] usb usb2: SerialNumber: ff5c0000.usb
[ 1.760984] ohci-platform ff5d0000.usb: Generic Platform OHCI controller
[ 1.769084] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3
[ 1.777172] ohci-platform ff5d0000.usb: irq 43, io mem 0xff5d0000
[ 1.839622] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.847615] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 1.855635] usb usb3: Product: Generic Platform OHCI controller
[ 1.855645] usb usb3: Manufacturer: Linux 4.4.126-rockchip-ayufan-239 ohci_hc d
[ 1.855656] usb usb3: SerialNumber: ff5d0000.usb
[ 1.858761] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.858771] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 1.858779] usb usb4: Product: xHCI Host Controller
[ 1.858788] usb usb4: Manufacturer: Linux 4.4.126-rockchip-ayufan-239 xhci-hc d
[ 1.858796] usb usb4: SerialNumber: xhci-hcd.9.auto
[ 1.860581] usb usb5: We don't know the algorithms for LPM for this host, dis abling LPM.
[ 1.860761] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
[ 1.860771] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber= 1
[ 1.860779] usb usb5: Product: xHCI Host Controller
[ 1.860787] usb usb5: Manufacturer: Linux 4.4.126-rockchip-ayufan-239 xhci-hc d
[ 1.860795] usb usb5: SerialNumber: xhci-hcd.9.auto
[ 1.944696] usbcore: registered new interface driver iforce
[ 1.944811] usbcore: registered new interface driver xpad
[ 1.945346] usbcore: registered new interface driver usbtouchscreen
[ 2.168389] usb 4-1: new high-speed USB device number 2 using xhci-hcd
[ 2.329245] usbcore: registered new interface driver uvcvideo
[ 2.347094] usb 4-1: New USB device found, idVendor=05e3, idProduct=0610
[ 2.350969] usbcore: registered new interface driver bfusb
[ 2.351072] usbcore: registered new interface driver btusb
[ 2.404305] of_get_named_gpiod_flags: parsed 'gpios' property of node '/switc hes/usb-switch[0]' - status (0)
[ 2.406058] usbcore: registered new interface driver usbhid
[ 2.406060] usbhid: USB HID core driver
[ 2.409735] usbcore: registered new interface driver snd-usb-audio
[ 2.430548] usb 5-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 2.444304] usb 5-1: New USB device found, idVendor=05e3, idProduct=0612
[ 2.444316] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.444355] usb 5-1: Product: USB3.0 Hub
[ 2.444363] usb 5-1: Manufacturer: GenesysLogic
[ 2.719469] usb 5-1.2: new SuperSpeed USB device number 3 using xhci-hcd
[ 2.731668] usb 5-1.2: New USB device found, idVendor=04e8, idProduct=61b6
[ 2.731679] usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber =3
[ 2.731688] usb 5-1.2: Product: Samsung M3 Portable
[ 2.731696] usb 5-1.2: Manufacturer: Samsung M3 Portable
[ 2.731703] usb 5-1.2: SerialNumber: 59E17DE9010000D0
[ 2.796457] usb 5-1.3: new SuperSpeed USB device number 4 using xhci-hcd
[ 2.808481] usb 5-1.3: New USB device found, idVendor=0bc2, idProduct=3320
[ 2.808492] usb 5-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber =1
[ 2.808500] usb 5-1.3: Product: Expansion Desk
[ 2.808509] usb 5-1.3: Manufacturer: Seagate
[ 2.808516] usb 5-1.3: SerialNumber: NA4K7DGB
[ 3.132629] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.140159] usb 4-1: Product: USB2.0 Hub
[ 3.147379] usb 4-1: Manufacturer: GenesysLogic
[ 3.716580] usb-storage 5-1.2:1.0: USB Mass Storage device detected
[ 3.724764] scsi host0: usb-storage 5-1.2:1.0
[ 3.729504] usb 5-1.3: UAS is blacklisted for this device, using usb-storage instead
[ 3.733423] usb-storage 5-1.3:1.0: USB Mass Storage device detected
[ 3.737696] usb-storage 5-1.3:1.0: Quirks match for vid 0bc2 pid 3320: 200000 0
[ 3.741796] scsi host1: usb-storage 5-1.3:1.0
[ 3.745860] usbcore: registered new interface driver usb-storage
[ 3.750825] usbcore: registered new interface driver uas
[ 4.273232] usb 4-1-port1: Cannot enable. Maybe the USB cable is bad?
[ 509.381200] usb 5-1.3: USB disconnect, device number 4
[ 510.250665] usb 5-1.3: new SuperSpeed USB device number 5 using xhci-hcd
[ 510.266571] usb 5-1.3: New USB device found, idVendor=0bc2, idProduct=3320
[ 510.271355] usb 5-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber =1
[ 510.276132] usb 5-1.3: Product: Expansion Desk
[ 510.280598] usb 5-1.3: Manufacturer: Seagate
[ 510.284989] usb 5-1.3: SerialNumber: NA4K7DGB
[ 510.293108] usb 5-1.3: UAS is blacklisted for this device, using usb-storage instead
[ 510.297922] usb-storage 5-1.3:1.0: USB Mass Storage device detected
[ 510.305538] usb-storage 5-1.3:1.0: Quirks match for vid 0bc2 pid 3320: 200000 0
[ 510.310356] scsi host2: usb-storage 5-1.3:1.0
I redid tests with the seagate and it's quite the same speeds (but poorer on ftp, 10MB/s Write)
It seems some other people reach good speeds through samba : https://forum.pine64.org/showthread.php?tid=4960
The read speed through Samba seems to be about right for the M3 Portable, from what I've read online. The other figures are pretty bad, though. To simply things, can you test again without the hub, with just the M3 plugged in?
Community administrator and sysadmin for PINE64
(Translation: If something breaks on the website, forum, or chat network, I'm a good person to yell at about it)
|
