hammondses

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by hammondses

  1. I guess we never got anywhere with this huh?
  2. +1 I have this exact use case also, It doesn't really make sense to make a VM with a docker container (home assistant) inside it just to be able to use a bluetooth dongle with unraid. Please add support for it at the OS level.
  3. @limetech @kmwoleyThis is my use case exactly too. Please provide some insight!
  4. I've just been banging my head against the same issue for a few days, thank god I found your post @kmwoley, it gives me the exact answer that I was looking for! T: Bus=03 Lev=02 Prnt=03 Port=02 Cnt=01 Dev#= 10 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0a12 ProdID=0001 Rev=88.91 S: Product=CSR8510 A10 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none) I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=(none) root@Sven:/dev# modprobe -v btusb modprobe: FATAL: Module btusb not found in directory /lib/modules/4.14.13-unRAID Now we just need some smart cookie to come up with a solution to the issue.
  5. After a bit more digging I've done the following: root@Sven:~# lsusb Bus 003 Device 010: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) added --device=/dev/bus/usb/003/010 to my extra parameters, no change. From within the docker container root@Sven:/usr/src/app# bluetoothd -n bluetoothd[133]: Bluetooth daemon 5.43 D-Bus setup failed: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory bluetoothd[133]: Unable to get on D-Bus Not sure what that means root@Sven:/usr/src/app# lsmod | grep bt ebtable_filter 16384 0 ebtables 32768 1 ebtable_filter This shows there is a lack of BT devices? root@Sven:/usr/src/app# hcitool scan Device is not available: Address family not supported by protocol
  6. I'm having big issues trying to pass through my bluetooth dongle to docker containers, I'm using homeassistant and it spits a nice error for me: Error setting up platform bluetooth_tracker Traceback (most recent call last): File "/usr/src/app/homeassistant/components/device_tracker/__init__.py", line 183, in async_setup_platform disc_info) File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run result = self.fn(*self.args, **self.kwargs) File "/usr/src/app/homeassistant/components/device_tracker/bluetooth_tracker.py", line 72, in setup_scanner for dev in discover_devices(): File "/usr/src/app/homeassistant/components/device_tracker/bluetooth_tracker.py", line 50, in discover_devices lookup_class=False) File "/config/deps/lib/python3.6/site-packages/bluetooth/bluez.py", line 26, in discover_devices device_id = _bt.hci_get_route() OSError: [Errno 97] Address family not supported by protocol I have --net=host as a an extra parameter which I understand should just pass through all usb devices. Does anyone have suggestions on how I could test whether or not the dongle is actually being passed to all dockers or not? Thanks
  7. What kind of read speeds are you getting from unraid? My write speeds reflect yours when writing to shares that are on the array sometimes, direct cache writes give me 350mb/s sustained. I can read from cache only at 1.1-1.2gb/s. Reading direct from the array I am limited to drive speed, which is anywhere from 170mb/s - 100mb/s. I noticed issues with the 10gbit links slowing down randomly for no apparent reason and kind of gave up trying to find a solution for it. If you find one i'l love to know what's going on. My specs - Xeon D-1541 32gb 2400ddr4, 256gb 960 evo cache 8tb seagate ironwolf x4 See here my thread here Slow NVME transfers
  8. I've been fiddling around with it for months and no result change, 1.1gb/s read speed burst but 350mb/s write max on the ssd still.
  9. The only option my Asus NIC gives above ~4k is 9014 & my unraid box nics support it.
  10. I did as you said, same result. 350mb/s write to Cache on NVME drive from RAM disk and 650mb/s read from NVME drive to RAM disk. Both ends set to 9014 unfortunately.
  11. Simple question - What is the max speed I can expect to write to a cache only shared folder on a 256gb 960 Evo? In my testing it seems to be 350mb/s no matter what I do. Testing the NVME drive in a windows 7 VM shows 3200mb/s read and 1100mb/s write. I setup a ramdisk on both my PC and the Unraid & I can achieve full 10gbe speeds. (1.15gb/s) PC Ramdisk -> shared cache only folder = 350mb/s.. Cache -> PC Ramdisk = 1.15gb/s I've tried direct IO which increases the write speed of the cache to around 400mb/s but drops the read to around 180mb/s. Any help would be greatly appreciated.