Chuck Claunch

Thanks a ton @JorgeB the steps you outlined worked perfectly 👍

Ok thanks! will give this a try this evening

Ok so just so I'm clear, if I disable Docker/VM services I won't lose all that data? Will it just go over to the main pool?

Here ya go unraid-diagnostics-20210825-0707.zip

I used to run with two cache drives, a Samsung 830 and a PNY, both SSDs. I decided I didn't need both as cache devices anymore and removed the PNY drive as cache. It now shows up in unassigned devices (along with a busted jpg icon). If I physically remove the PNY drive from my system, my remaining Samsung cache drive says unreadable. If I physically put the PNY drive back in, the Samsung cache drive is readable again and the PNY drive still shows up in unassigned devices with the busted icon. See screenshot. How can I release this drive so I can remove it and not lose my cache contents? All of my docker and VM configs are on this and they're totally missing if I boot without the PNY drive (and Samsung cache drive says unreadable).

Ok as I was going to unassign the cache devices as you said, I noticed I'd left the slot number at 2. When I changed it properly to 1 and started the array it loaded the cache drive just fine, then after re-enabling docker and VMs, and a reboot, everything is back up. Thanks a lot for the help!

I left the one disk assigned as cache because it appeared as if the other one never got used at all (no data on it). I suppose I could re-assign it just to see if everything comes back? I can try that once parity finishes syncing I suppose.

Here's the file. Note the cache device I removed is the PNY_CS1311_120GB, the one I kept (which I believe may have my docker stuff on it) is the SAMSUNG_SSD_830. Also note, the Unassiend device ST10000VX0004 a drive set up only for a windows VM (boot + data), which I also seem to have lost, though that drive mounted and is readable. unraid-diagnostics-20201212-1828.zip

Hi, I just followed the directions (for unRAID v6.2 and later) on this page to remove a single 4TB drive from an array which originally had 3 4TB drives (2 + 1 parity). Everything seems to be going as expected, and the parity is currently rebuilding. Is it normal to expect that all my dockers and VM would be lost in this transition? Or will they all re-appear once the parity sync is finished? That's a huge bummer if I've lost it and the instructions had no real warning about loss of data. I did back up a lot of important data but did not back up my docker config as I thought that lived on the flash drive. The only other thing I notice is I removed a completely unused cache device (one remaining) and the remaining one says `Unmountable: No pool uuid`. Any thoughts would be appreciated.

That's just the thing though. I'm not really worried about google tracking or about ads being displayed in unraid. Just curious why unraid borks with a pihole DNS. I don't see any DNS queries in my pihole logs at all when I hit the docker "check for updates" button. Not surprising as I'm sure it's using some docker hub API to grab images, but then that begs the question, why would a DNS server cause issues with the docker update check? I've already solved the issue by just changing DNS on unraid as suggested. My interest at this point is purely academic (and/or bug hunting in unraid). If it borks unraid, it's surely to bork something else. I've only been running pihole for a week or so, so I'd like to shake out kinks as they arise.

Can someone please expand upon the "don't use pihole or a custom dns with unraid" comments? I'd rather just know what dns entries are being blocked than just open the pipe to google.

One note in my example above vs what I do now is I just pass the entire usb bus in. so instead of passing `/dev/bus/usb/001/006` or whatever I pass `/dev/bus/usb`. Makes it a lot easier and even works passing into multiple containers if you're brave enough (or at least only doing read only stuff).

If you just need to use the device in a docker or VM, you can just pass in the entire usb bus. No need to have the BT drivers in the main unraid instance. See my comment above: I've been using bluetooth in a docker for node-red for about six months with no issues.

For what it's worth, I verified that my post above does work. I built a Node-RED docker including Noble (a Bluetooth Low Energy scanning node) and was able to pass in the Bluetooth dongle using the instructions above, even without having the dongle's firmware on the host. That said, obviously it'd be nice to pass it by a proper name e.g. /dev/hci0 So it'd still be nice to add that large chunk of various manufacturer's firwmare I posted.

After messing with this for a bit I realized I could in fact pass the specific USB bluetooth device as yayitazale attempted above. The key was to pass it as a path. Instead of doing --device='/dev/bus/usb/001/006' Pass that device as a path with read/write access and make the container privileged. So under your docker container settings, add a path and enter the device path into both the host and container path values and make it read/write: More specific to the home assistant docker container, it did not start up with the device running so I had to start it. To do that, first run hciconfig (Bluetooth MAC addresses obscured to protect the innocent): # hciconfig hci0: Type: Primary Bus: USB BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1021:8 SCO MTU: 64:1 DOWN RX bytes:1609 acl:0 sco:0 events:74 errors:0 TX bytes:777 acl:0 sco:0 commands:70 errors:0 So we see hci0 is there but is down, so issue the up command: # hciconfig hci0 up # hciconfig hci0: Type: Primary Bus: USB BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:2183 acl:0 sco:0 events:104 errors:0 TX bytes:1145 acl:0 sco:0 commands:100 errors:0 And now with a subsequent hciconfig command see the device is running. So now we can do stuff like lescan: # hcitool lescan LE Scan ... XX:XX:XX:XX:XX:XX bhyve_XXXXXX XX:XX:XX:XX:XX:XX (unknown) XX:XX:XX:XX:XX:XX (unknown) XX:XX:XX:XX:XX:XX (unknown) I haven't gone as far as to get bluetooth devices reading in home assistant yet, but at least this proves that the device can be passed to the docker from unraid regardless of whether the firmware file is there.