Disks are 1 sector smaller with USB bridge

[Dieter BSD]

FreeBSD reports that disks are 1 sector smaller when connected via
a usb-to-sata bridge than when connected to a sata controller.
This creates a problem when migrating a disk from a sata controller
to a usb bridge, the data in the last sector is no longer accessable.

How do I access the disk's last sector when connected via usb?
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: Disks are 1 sector smaller with USB bridge

[Dieter BSD]

[ ml didn't get cc-ed ]

 - Original Message -
 From: Dieter BSD
 Sent: 09/07/12 11:28 AM
 To: Warner Losh
 Subject: Re: Disks are 1 sector smaller with USB bridge
 
  - Original Message -
  From: Warner Losh
  Sent: 09/06/12 08:27 PM
  To: Dieter BSD
  Subject: Re: Disks are 1 sector smaller with USB bridge
  
  On Sep 6, 2012, at 12:41 PM, Dieter BSD wrote:
   FreeBSD reports that disks are 1 sector smaller when connected via
   a usb-to-sata bridge than when connected to a sata controller.
   This creates a problem when migrating a disk from a sata controller
   to a usb bridge, the data in the last sector is no longer accessable.
   
   How do I access the disk's last sector when connected via usb?
  
  Which version? I fixed this exact bug years ago, I thought...
  
  Warner
 
 FreeBSD 8.2 amd64
 Disk is recent Seagate 3TB external, the bridge provides 4KiB
 sectors, but I recall seeing the same off-by-one problem
 with an older bridge with 512 byte sectors. (Don't recall offhand
 what version of FreeBSD I was running at the time.)
 If it matters, bridge is usb3 but host is only usb2.

___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

PCIe to USB to PCIe

[Dieter BSD]

A very small PCIe x1 card with USB 3.0 controller, a USB cable,
and a small pcb with a PCIe x16 slot.  Intended to allow using
x16 video cards with x1 slots, and reducing power/space/cooling
demands on mainboard.

Claim: "No Driver necessary"

Can these things possibly work?

If they do, it seems to me that this would be a great way to
add additional general purpose PCIe slots to any computer that has
USB ports, which nearly all do these days.  If no driver is needed,
they should work with any OS.  Obviously there is a speed limitation,
but many applications can live with that.

Sounds too good to be true.  Am I missing something?

http://kaishijia.en.alibaba.com/product/1869213364-221855851/PCIE_PCI_E_Riser_Card_to_USB3_0_and_SATA_Power_Cable_with_PCB_Board_for_Bitcoin_Machine.html

More here:
http://kaishijia.en.alibaba.com/productgrouplist-221855851/Bitcoin_Mining_cables.html
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

AX88179 USB-to-Ethernet is slow and silently corrupts data

[Dieter BSD]

10.3-RELEASE
amd64 with ECC memory
VIA VL805 USB 3.0 controller
ue0 is Siig USB-to-Ethernet  Chipset: AX88179

ugen0.7:  at usbus0, cfg=0 md=HOST
   spd=SUPER (5.0Gbps) pwr=ON (124mA)

ue0: flags=8c43 metric 0
 mtu 1500
options=8000b
inet 10.0.210.66 netmask 0xff00 broadcast 10.0.210.255
nd6 options=29
media: Ethernet autoselect (1000baseT )
status: active

If media is set to "1000baseT " it "works", but slowly, and
received data is silently corrupted. :-(  Transmitted data is not
corrupted (tested with > 30 GB).

ifconfig ue0 -txcsum
"works", but still gives silent data corruption

ifconfig ue0 -rxcsum  (acts the same with or without txcsum)
  ping out
netstat sees packets both directions, but ping doesn't see the response:
8 packets transmitted, 0 packets received, 100.0% packet loss
  ping in
   netstat sees packets in, but no responses going out

I can see that some Ethernet controllers would not support checksum offloading,
but it seems to me that turning the checksum offloading off should always
work? (at the expense of more cpu load)

Previously (2016 May):
  # ifconfig ue0 media 100baseTX-FDX
  fixed the input error problem and the data corruption problem,
  at the expense of making it even slower.

  Sent data from machine A with 10Mbps Ethernet.  (Netgear Ethernet switch
  converts 10Mbps to 1000Mbps) Netstat did not report any input errors on
  ue0 and there was no data corruption.  So ue0 can handle gigabit data rate,
  but gets input errors if packets arrive too frequently.

  I tried moving it to a USB-2 port.  No data corruption, but USB-2 is slow.

  The chip performs a lot better for tweaktown:
  
http://www.tweaktown.com/reviews/7243/vantec-cb-u300gna-usb-3-gigabit-network-adapter-review/index.html
  (Vantec CB-U300GNA with the same Asix AX88179 chip)
  "full duplex gigabit with 952 Mbps consistently across the chart"

http://www.vantecusa.com/products_detail.php?p_id=143_name=USB+3.0+Gigabit+Ethernet+Adapter_id=21_name=Network_id=5_name=Accessories

  Asix AX88179 chip:
  http://www.asix.com.tw/products.php?op=pItemdetail=131;71;112
  "Supports Jumbo frame up to 4KB"

  But ifconfig rejects any value > 1500:
  ifconfig ue0 mtu 1501
  ifconfig: ioctl SIOCSIFMTU (set mtu): Invalid argument

I tried mtu of 100, 500, 1000, 1400 but they all give
rcp: lost connection

USB disks are fast, so the USB controller seems to work ok.

I also tried a Tek Republic TUN-300 which has the same AX88179,
and it acts the same as the Siig.

So, transmit works, but is slow.  Receive works if the amount of traffic
is low enough (limit rate of data sent, limit Ethernet speed, or
use USB-2). But if data is received too fast it gets silently corrupted.
Setting -rxcsum does not work, and cannot set mtu other than 1500.

Questions:
 Why does -rxcsum not work?
 Why does attempting to set a larger mtu fail?
 Why does setting a smaller mtu make rcp fail?
 Why is the chip acting slow?
 How do I get it to work properly? (fast and without data corruption)
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"