Mysticle31

Got it. This probably doesn't help the community, mods can remove. https://askubuntu.com/questions/63594/mount-encrypted-volumes-from-command-line

I bought a new hdd for encrypted offline storage. I can create the XFS encrypted volume in Unassigned Devices but it refuses to mount the partition. No errors, no logs, just click mount and nothing. I cannot see my device under /dev/mapper. How can I mount this manually? Where do I start to diagnose?

Gotcha! Thanks Thanks!

Ever get anywhere with this? I never did for me. What I did notice was that my USB Switch has an impact on the issue. It's worked great for months now, sometimes will die but if I unplug the switch then plug a device directly into the usb port, sometimes it comes back. Then sometimes I can put the switch back on and continue for awhile, sometimes the switch wont work and I'll have to reboot. It's strange. I've thought about getting an external USB card (I'm using MB only ports) and seeing if it behaves differently.

Newbie question I suppose... Why does my missing disk have data on it? I can see and access the data on it...? The drive is physically not there! I think I disabled it in the bios, but maybe I just took it out of the array. Is Unraid putting data on it? Disk 2 is showing 3.02 GB used... but it's empty? Background: My drives are developing bad sectors and the array was full so moved all the data I never use to offline cold storage, and consolidated everything to disk3. The system is deciding to put stuff on disk1 which I removed. Bonus question... I built my rig in 2014 (I think) as a Desktop/Game system that saw Unraid use right away. It's an i5-4690K, 4th Gen with 32gb ram. I think the ram is the only thing keeping it alive, if I had a 16gb limit I might have replaced it already! The hardware is still fairly capable...I haven't ran into any limits with it running my dockers and a couple VMs. More cores could be nice...I could get an 8 core cpu used and run it some more... Should I just update the drives or build a new server? I was hoping to get a couple more years out of the hardware I have... but I'd say that a couple of years from now too! Now that it's an server, I'd like to build a smaller 4-5 external drive bay rig I can hide somewhere rather than my full tower.

I just saw it happen, and fortunately had the console open. I dont always see unraid reporting anything. My Linux VM reported Unraid reported lspcid'd it Sure enough IRQ 18 Tried to rmmod and modprobe vfio-pci. Didn't work

I'm having the exact same issue with my VMs as Elie above. Intel passthru only works with Seabios. Mine doesn't show anything. Is there a place in logs we can check? Tips tricks?

TLDR Summary: USB Switch switching between two laptops and an unraid VM. The VM doesn't always connect back when being switched. Sometimes it picks up right away, sometimes takes a minute, mostly requires a server reboot. Linux VM, Windows VM doesn't seem to matter. Would like to avoid the server reboot at the very least! Is there a way to reset the hardware stack or drivers via command line? How can I begin to diagnose and address this USB VM Passthru issue? Details: In a fit of irony, I've been watching lsmod and lspci to look for changes for the past few hours, but it's worked EVERY TIME. I'll try and grab working and not working logs... Interestingly, I can know when the system freaks out because I have this corded optical mouse and I can watch the light flash instead of being solid. Just unplugging and re-plugging the mouse sometimes makes the mouse work, but when it doesn't...time to reboot the server. Here is a process, Server off. Start Server USB device connected Start VM USB device connected + passthru enabled VM Recognizes Device, usable in VM Switch off the VM to one of the laptops and the laptop will recognize the device instantly. 5. Switch back to the VM and several things could happen Recognizes the device instantly (fairly rare) Recognizes the device in a minute. Wont recognize at all and have to switch back and forth a few times to make it recognize. Have to reboot the server and start this process over. Rebooting the VM does not help.

Recently updated my server to the latest versions of everything. Quarantine Fun! Is there a way to reset the hardware stack or drivers via command line? I'm passing though a USB controller and graphics card to some VMs. USB devices on the VM are attaced to the USB controller with a switch so I can switch between another computer and the VM. Sometimes the controller freaks out... a server reboot takes care of the issue. Linux/Windows VMs will report: Is there a way to reset the hardware stack or drivers via command line? Thanks!!!

I'm having this same permissions issue. I just ran DockerSafeNewPerms which fixed all the files created by syncthing, however, I can't modify new files created by syncthing. Can I somehow pass to the docker to create the files as 777 or some such thing? Worst off maybe schedule DockerSafeNewPerms to run daily at night... not an ideal solution. FYI my speed seems fine. I had to turn off everything but local discovery, and changed my server's ip from dynamic to it's actual ip. Things go much faster now, although still slower than transferring files in windows explorer.

I have BRNAME in domain.cfg and it's set to BR0. Bridging is enabled in settings. I guess something just went funky. Or maybe I messed with it some point while poking around with unraid. I remember removing an reinstalling the plugin though after when I was done messing with things.

6.6.2 not latest...I just installed like...2 days ago. Anyhow, works! For some reason, the script was using virbr0. I even have br0 specified in the default network for VMs. Thanks! ps aux and grep...my linux/unix knowledge is so bad..need to mess around some more. Would virbr0 even work? I thought that was like a NAT for VMs you dont want to directly expose to the network. The script is looking at the packets coming in off eth0 and then looking up a mac address from the specified network (br0/virbr0/whatever) and running the command to start the vm, right?

6.6.2. Should be the latest one. No change with your latest update that I just installed.

Hi All! New to unraid. Been setting up my new box. Loving it so far!! Having some problems setting up the wake on lan plugin for VMs. This is all some background on my investigation of the problem. See the update below When I generate WOL packets through several means from a computer on the same subnet, I can see the packet get picked up by the nic. I dont like that is says disgard at the end. tcpdump -i br0 udp port 9 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes 19:18:39.609149 IP ScubaSteve.56209 > 255.255.255.255.discard: UDP, length 102 19:19:47.380846 IP ScubaSteve.64090 > 192.168.1.255.discard: UDP, length 102 19:19:47.380855 IP ScubaSteve.64090 > 255.255.255.255.discard: UDP, length 102 tcpdump -i br0 udp port 7 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes 19:25:42.838792 IP ScubaSteve.50330 > 192.168.1.255.echo: UDP, length 102 19:25:42.838803 IP ScubaSteve.50330 > 255.255.255.255.echo: UDP, length 102 19:25:50.215074 IP ScubaSteve.50331 > 255.255.255.255.echo: UDP, length 102 My /var/log/libvirt/libvirtwakeonlan.log remains empty and my VM's powered off. I have verified that the command "virsh start "My Windows 7 VM"" will start the vm. My VMs are all using BR0 not VIRBR0. UPDATE!! Running python /usr/local/emhttp/plugins/libvirtwol/scripts/libvirtwol.py br0 allows the VM to start via WOL, and shows entries in the log! This happens regardless of what the plugin status is under VM Manager settings. I've tried it being reported as Running and being reported as Stopped. I'm guessing that when I start the plugin something is not running properly (and reporting that it is), or it's not listening on the correct interface. How can I investigate this further?