BurntOC

Is this working with the new v7 beta?

It is the same stated capacity, so hopefully so. I'm actually wondering if I should format the new drive for ZFS per the beta notes, to take advantage of some features unsupported by xfs. I'm not on v7 on that server atm, but I'm considering it after my primary server upgrade has seemingly gone quite well so far. Maybe I could use a USB SSD enclosure then use mover to move everything over, remove the original drive and pop the new one into the m.2 socket? If not this approach, I take it if I've cloned the drive with Macrium that I can reset and reimport, and the shares and permissions should be fine due to the /mnt/user mappings Unraid uses?

One of my servers is unlike the others in that it is a SFF device with a single M.2 slot and drive running some containers and a VM. The SSD is throwing read errors so I bought another. Usually I'd try to image a drive like this in Macrium Reflect (I'm usually on Windows), but even if it can clone the xfs drive I think Unraid uses the serial number to track it, so just cloning and swapping wouldn't fix it, right? If not, what's the easiest approach?

Yep, you're right - thanks!

Ah, attempted to manually execute the install script you referenced and it returns: Version is for qemu.d 6.12.8 No other output given.

This server, and the other one I referenced, are on 6.12.8. I checked the usb.ini file and I think it looks okay (pasted code block below). I'm not sure I follow on the USB Manager code block. Are you suggesting I copy the code from one or both of the replies above into a manually created path and file, then assign the executable permission? If I uninstalled the plugin altogether and reinstalled, would I be able to get it to automatically create the startup stuff and restore my current assignments? [001/002] connected = "" bus = 001 dev = 002 ID_VENDOR_FROM_DATABASE = "Ports=4 Power=0mA " ID_VENDOR_ID = "0bda" ID_MODEL = "" ID_MODEL_ID = 5411 USBPort = "1-1" class = "hub" parents = "usb1,0000:00:15.0,pci0000:00" ID_SERIAL = "Generic_4-Port_USB_2.0_Hub" isSerial = "" isSerialPath = "" [001/004] connected = 1 bus = 001 dev = 004 ID_VENDOR_FROM_DATABASE = "Silicon Labs" ID_VENDOR_ID = "10c4" ID_MODEL = "CP2102N_USB_to_UART_Bridge_Controller" ID_MODEL_ID = "ea60" USBPort = "1-1.1" class = "interface" parents = "1-1,usb1,0000:00:15.0,pci0000:00" ID_SERIAL = "Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_5e2708b05fbcea11944693e368aed703" isSerial = 1 isSerialPath = "usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_5e2708b05fbcea11944693e368aed703-if00-port0" virsherror = "" VM = "Home Assistant" virsh = "Device attached successfully " connectmethod = "Manual" connectmap = "Device" [001/006] connected = 1 bus = 001 dev = 006 ID_VENDOR_FROM_DATABASE = "Silicon Labs" ID_VENDOR_ID = "10c4" ID_MODEL = "SkyConnect_v1.0" ID_MODEL_ID = "ea60" USBPort = "1-1.2" class = "interface" parents = "1-1,usb1,0000:00:15.0,pci0000:00" ID_SERIAL = "Nabu_Casa_SkyConnect_v1.0_9c33dedc57e2ed11b233ec5162c613ac" isSerial = 1 isSerialPath = "usb-Nabu_Casa_SkyConnect_v1.0_9c33dedc57e2ed11b233ec5162c613ac-if00-port0" virsherror = "" VM = "Home Assistant" virsh = "Device attached successfully " connectmethod = "Manual" connectmap = "Device" [002/001] connected = "" bus = 002 dev = 001 ID_VENDOR_FROM_DATABASE = "Ports=7 Power=0mA " ID_VENDOR_ID = "1d6b" ID_MODEL = "" ID_MODEL_ID = 0003 USBPort = "2-0" class = "roothub" parents = "0000:00:15.0,pci0000:00" ID_SERIAL = "Linux_6.1.74-Unraid_xhci-hcd_xHCI_Host_Controller_0000:00:15.0" isSerial = "" isSerialPath = "" [002/002] connected = "" bus = 002 dev = 002 ID_VENDOR_FROM_DATABASE = "Ports=4 Power=0mA " ID_VENDOR_ID = "0bda" ID_MODEL = "" ID_MODEL_ID = 0411 USBPort = "2-1" class = "hub" parents = "usb2,0000:00:15.0,pci0000:00" ID_SERIAL = "Generic_4-Port_USB_3.0_Hub" isSerial = "" isSerialPath = "" [002/003] connected = "" bus = 002 dev = 003 ID_VENDOR_FROM_DATABASE = "Ports=2 Power=0mA " ID_VENDOR_ID = "0bda" ID_MODEL = "" ID_MODEL_ID = 0415 USBPort = "2-6" class = "hub" parents = "usb2,0000:00:15.0,pci0000:00" ID_SERIAL = "Generic_2-Port_USB_3.0_Hub" isSerial = "" isSerialPath = "" [004/001] ishub = 1 connected = "" parents = "vhci_hcd.0,platform" bus = 004 dev = 001 ID_VENDOR_FROM_DATABASE = "Linux Foundation" ID_VENDOR_ID = "1d6b" ID_MODEL = "USB_IP_Virtual_Host_Controller" ID_MODEL_ID = 0003 USBPort = "usb4" class = "" ID_SERIAL = "Linux_6.1.74-Unraid_vhci_hcd_USB_IP_Virtual_Host_Controller_vhci_hcd.0" isSerial = "" isSerialPath = "" bNumInterfaces = ""

@SimonF Thanks for the quick response. Under hooks I don't have any subfolders - qemu.d or otherwise - so that cat command is giving me an error. Only thing there atm is a qemu file. I checked one of my other servers and it actually doesn't even have the hooks folder under libvirt (but it's not running USB Manager either, just an FYI).

Anyone having a problem with devices auto-attaching on server or VM start? I've had it configured that way since Day 1 and it worked great for almost a year, but the last couple of months it seems to ignore that setting and I still have to go in to click "VM ATTACH" to get my Zwave and Zigbee sticks to show up in my HA VM. Maybe something got corrupted when I was tweaking to switch my Zigbee stick out for a newer one with a better chipset. Open to any fixes, even blowing it away and starting over but IIRC I tried that from the GUI about 6 weeks ago and it didn't resolve this for me.

@Vynlovanth Did you ever figure this out? Mine go missing as well during updates from 6.11.5 and it's driving me mad.

That's what I figured as I worked my slow mind through it, but I'm glad I asked to be sure. Thanks for the response, and for the great plugin.

Greetings, all. I have a Home Assistant VM running and I've been passing my Z-wave and Zigbee dongles to it successfully for a long time. Now Zigbee2MQTT is getting twitchy, which appears to be an open issue with the newer versions and my hardware, but I am trying to minimize any hiccups. As passing both dongles seem to work whether or not I map them both as ports, both as devices, or one of each (even though they both show as CP210N UART Bridges in the USB Manager mapping, my question is this: Is one of those configurations preferable over the others? Even when I pass as port I set the devices /dev/serial/by-id in Home Assistant, so it doesn't seem to matter but I just wanted to double-check.

Fixed it myself. In case this helps others, here's my template, through you'd want to verify the network type and paths match what you want. <?xml version="1.0"?> <Container version="2"> <Name>NextPVR</Name> <Repository>nextpvr/nextpvr_amd64:stable</Repository> <Registry>https://hub.docker.com/r/nextpvr/nextpvr_amd64</Registry> <Network/> <MyIP/> <Shell>bash</Shell> <Privileged>false</Privileged> <Support/> <Project/> <Overview>NextPVR TV recording and video player software.</Overview> <Category>MediaApp:Video</Category> <WebUI>http://[IP]:[PORT:8866]/index.html</WebUI> <TemplateURL/> <Icon>https://hub.docker.com/r/nextpvr/nextpvr_amd64</Icon> <ExtraParams>--security-opt=no-new-privileges</ExtraParams> <PostArgs/> <CPUset/> <DateInstalled>1695046806</DateInstalled> <DonateText/> <DonateLink/> <Requires/> <Config Name="Recordings" Target="/recordings" Default="" Mode="rw" Description="Recordings Folder" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/media/recordings</Config> <Config Name="Buffer" Target="/buffer" Default="" Mode="rw" Description="Live TV Folder" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/nextpvr/buffer</Config> <Config Name="Configuration" Target="/config" Default="" Mode="rw" Description="Configuration Path" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/nextpvr/config/</Config> </Container>

Got it working, thanks.

Based on older comments here, and much more recent ones in the NextPVR forum, it looks like some folks have had success with this, but I can't find an actual working template from the last 2 years. Anyone willing to share one?

Alrighty then, LOL

Hi all, revisiting this after some successful tests a couple years back. I'm ready to migrate from Unifi and I've gotten one of my two new switches adopted, though I did enable cloud access to do that. I'd strongly prefer NOT to enable cloud access, so now that I've disabled it I cannot for the life of me get the controller to show the second switch I want to adopt. The controller and the switches are on different subnets and VLANs, but I believe the port for the container (Unraid GUEST interface VLAN/net) and the switch (INFRA VLAN/net) have the PVID and tagged VLANs set properly, and I can ping back and forth both ways. I also have all the 29810-29816 ranges,18043, 27001 (and actually just all the dang high ports for now) opened between the two on the firewall. Lastly, I've gone into the new switch interface and told it the IP of the controller. All that done and I just cannot get it to show. I figure many of you are running standalone with cloud access disabled. Any advice on how I can resolve this?

Seems like deleting my docker image fixed it.

Did y'all ever fix this? The ongoing instability issues I have had with 6.12.x on my 11th gen i5 drove me to downgrade back to 11.5, but none of my containers will start. They are giving the same messages you were seeing.

Okay, thanks. I mounted in maintenance mode and did a file system check without the -n flag on those drives and the error hasn't shown back up yet. I'll give it a bit more time and them mark this as solved if it doesn't happen again.

I noticed a FCP error today that said my /var/log was getting full. In looking at it, the culprit seems to be that the logs are getting spammed by these 3 messages over and over. Aug 9 07:41:58 myunraidserver kernel: XFS (dm-0): Internal error !xfs_dir2_namecheck(dep->name, dep->namelen) at line 466 of file fs/xfs/xfs_dir2_readdir.c. Caller xfs_dir2_leaf_getdents+0x220/0x322 [xfs] Aug 9 07:41:58 myunraidserver kernel: CPU: 10 PID: 1579 Comm: find Tainted: P BU W O 6.1.38-Unraid #2 Aug 9 07:41:58 myunraidserver kernel: Call Trace: Any idea what might cause this, and how I can fix it? My array is xfs, as you can see from the message, and I have a single parity. Also a cache drive that's xfs, fwiw. Also, the 6.1.38 reference looks interesting to me. I'm not sure what that's referencing, but I'm on version 6.12.3.

So weird....I'm on vacation and thought I'd pop it to check for an update and it seems I somehow didn't post the reply I'd typed out somewhere. Anyway, I'm not routing any containers through another container. I have a quad NIC with each port having one or two VLANs and each of those with their on /24 subnet. The *arrs and this container are on the same VLAN and each has a static IP assigned in the same subnet. It is working for over 20 other containers, but I can't get them to be able to connect to this one for some reason.

What is the secret to getting other containers (like Sonarr) to be able to connect to this?? I had hotio's version running, then decided to switch to OpenVPN to avoid some logging issues. Each of my *arrs and this container are on the same /24 subnet and I even just used the same IP and login credentials as the hotio container. No dice, they won't connect. They can ping this container, but not access it. I'm using the default ports (except for the peer of course) and I've tried putting 8080 in vpn input ports, output ports, both, neither, and it fails every time.

Sorry for the delay - I'm not getting notifications on this. Been a crazy month so my memory is shot, honestly, but IIRC I just restored via my appdata backups.