archedraft

How about putting the radio on top of a piece of 3/4" plywood with a Lazy Susan Bearing between the two? I am not sure how heavy the radio is so you would have to get a bearing that would support the weight. Also I would want a locking mechanism to stop it from spinning by its self.

Update fixed all the network issues I had to change my plugin location to my cache drive instead of an UD disk for this plugin to start after a boot but that's fine. Thanks!

You could setup a cron script that stopes your VM, rsync the VM, then start it up again. Personally I think doing that is a waste of time. What I do is get my VM (let's say it's a Windows VM) all setup and my core applications installed, all windows updates ect. And then make a copy of that VM. Then I use that VM for a few months and when Windows starts to get slower (bc I installed junk or whatever is causing it to slow down) I just copy back that "fresh" Windows image and it is just like a freshly formatted Windows machine. I don't save anything to my local VM, instead I just save all the important documents to my unRAID server so I never loose anything when I do this. Just my 2 cents.

Peter, are you also having the same issue with the plugin starting at boot?

Absolutely: # Generated settings: IFNAME[0]="br0" BONDNAME[0]="bond0" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BONDING_MODE[0]="1" BONDNICS[0]="eth0" BRNICS[0]="bond0" DESCRIPTION[0]="br0" USE_DHCP[0]="yes" DHCP_KEEPRESOLV="no" MTU[0]="" SYSNICS="1"

I'll double check this afternoon on my first server but I'm pretty sure on my first server my S01.sh script to copy the icons on boot was the same location. I'll double check though. Either way it sounds like something I am messing up.

Yes sir, a few times. I edit the VM to the correct VNC mode as suggested.

Happy to hear it's a common issue and not the normal archedraft is "special" issue.

Yes, backup your flash drive and take note of each of the drive assignments. I have never done this so I could be wrong but my guess would be that you are going to have to reassign each drive once you connect them to the new motherboard. If that does happen I would only assign the data drives first without parity and start the array. Then double check to make sure all your data is there and you didn't accidentally assign the parity drive as a data drive. Assuming all looks good then stop the array and assign parity and then do the parity checks. I would set all VM's to not auto-start. Then once you get all the discs a figured out above, I would use the unRAID editor and re-assign the correct cores to each VM. This will make sure you have the correct cores selected. Windows 10 may detect a hardware change and ask you to activate windows again. I know for sure if you use Microsoft Office 2010 it will ask you to reactive office if it detects the CPU has changed.

I figured out why I was getting the following errors after upgrading from 6.1.9 Warning: libvirt_domain_xml_xpath(): namespace warning : xmlns: URI unraid is not absolute in /usr/local/emhttp/plugins/dynamix.vm.manager/classes/libvirt.php on line 936 Warning: libvirt_domain_xml_xpath(): It was because of the lines in the config that had to do with the VM icon <metadata> <vmtemplate xmlns="unraid" name="OSX" icon="OSX-10.10.png" os="OSX"/> </metadata> I have a second test server I upgraded from 6.1.9 and if I remove the metadata lines above the error goes away, but if I try and use the unRAID VM editor to add another image back the same warning message appears no matter which icon I choose. As of right now my second server just has the metadata lines removed as I do not want to set up that server from scratch like I did on my first server. Could it be because I was using custom icons when I upgraded and once I got into 6.2 it didn't know how to handle that situation?

Issue #2: I can start the OpenVPN server manually; however, once I connect my phone to the VPN I can only access my unRAID webGUI. I cannot remote desktop or access my router on that same network. This was working just fine with the same settings on Version 6.1.9 so I wonder if the new ethernet settings on b23 are conflicting with this plugin? EDIT: Just noticed that I can only access the unRAID webGUI. All other traffic including a google search or local network (ie router page) do not load.

On unRAID 6.2b23 OpenVPN does not start for me on a reboot. I get this error in syslog. Diagnostics attached. Jun 13 17:18:12 Pithos root: Starting OpenVPN Server Jun 13 17:18:12 Pithos root: Starting Openvpn server..... Jun 13 17:18:13 Pithos sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/openvpn --writepid /var/run/openvpnserver/openvpnserver.pid --config /mnt/disks/vmdisk/plugins/openvpn/openvpnserver.ovpn --script-security 2 --daemon Jun 13 17:18:13 Pithos avahi-daemon[13881]: Service "Pithos" (/services/ssh.service) successfully established. Jun 13 17:18:13 Pithos avahi-daemon[13881]: Service "Pithos" (/services/smb.service) successfully established. Jun 13 17:18:13 Pithos avahi-daemon[13881]: Service "Pithos" (/services/sftp-ssh.service) successfully established. Jun 13 17:18:14 Pithos root: An error occurred, server not started!. More info in /var/log/openvpnserver.log or /var/local/emhttp/plugins/openvpnserver/openvpnserver.out Jun 13 17:18:14 Pithos emhttp: Any ideas why it isn't starting? EDIT: Output from /var/local/emhttp/plugins/openvpnserver/openvpnserver.out Options error: In [CMD-LINE]:1: Error opening configuration file: /mnt/disks/vmdisk/plugins/openvpn/openvpnserver.ovpn Use --help for more information. I guess my UD mount is not mounting fast enough?

Is it normal to get these notifications periodically in your syslog? Jun 12 15:49:43 unRAID kernel: unregister_netdevice: waiting for lo to become free. Usage count = 1 Jun 12 15:49:53 unRAID kernel: unregister_netdevice: waiting for lo to become free. Usage count = 1

If a parity check finds 1563 errors shouldn't the history status say something other than "OK" in the status?

I ended up deleting everything off of my flash drive and putting on a fresh install of 6.2. After getting everything back to normal the VM's are working just fine. Something must have transferred wrong from 6.1. Honestly though it was kind of nice to start over, the flash drive looks much cleaner

I am setting up unRAID from new with default settings. You know a plugin is awesome when it's the first one you install! I really like how easy this makes installing everything again; plugins and dockers. THANK YOU Squid for all the time spent working on this plugin.

You can, but you just have to edit the qemu.conf and add the iommu groups See here: https://lime-technology.com/forum/index.php?topic=43428.0 I had to do that for the El Capitan VM :-) Just edit the file /etc/libvirt/qemu.conf, find the line for "cgroup_device_acl" and add "/dev/vfio/5" to the list, restart VM manager and it should work Ah, very nice. The post that is linked makes it sound like it was an early bug in 6.2 that was suppose to have been fixed?

On a side note: in 6.2 are we not allowed to pass through devices with the following code? <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=02:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:1a.0,bus=root.1,addr=00.1'/> </qemu:commandline> I keep getting this error which I was not getting in 6.1? 2016-06-10T01:43:42.236119Z qemu-system-x86_64: -device vfio-pci,host=00:1a.0,bus=root.1,addr=00.1: vfio: error opening /dev/vfio/5: Operation not permitted 2016-06-10T01:43:42.236161Z qemu-system-x86_64: -device vfio-pci,host=00:1a.0,bus=root.1,addr=00.1: vfio: failed to get group 5 2016-06-10T01:43:42.236169Z qemu-system-x86_64: -device vfio-pci,host=00:1a.0,bus=root.1,addr=00.1: Device initialization failed

It's not liking something in your xml. Are they set to autostart? The 6.2 beta18 thread said to turn off autostart before update. Then after update edit the VM and do some stuff for 6.2. I would backup all the configs first. You could also rename your libvirt.img No I turned off autostart. Been messing around with this for a few hours, I have tried stoping libvirt then deleting the libvirt.img file and recreating it. This allows me to select VMs again and I tried setting them all to VNC like it says in the other post but that doesn't fix the errors. I have tried deleting every single VM and starting from scratch but then once I try and create a new vm it gives that error. I wonder if I need to revert back to 6.1 and delete all my VM and then try and upgrade back to 6.2 so it is a fresh start?

Upgraded from 6.1 and I believe I followed the instructions on the VMs but I am getting the message below. I tried removing my old VM's completely but I know a few are not shown on the VM page. Anyone know how to get the add VM button back and remove this message? I also attached a screen shot. Warning: libvirt_domain_xml_xpath(): namespace warning : xmlns: URI unraid is not absolute in /usr/local/emhttp/plugins/dynamix.vm.manager/classes/libvirt.php on line 936 Warning: libvirt_domain_xml_xpath():

Shhhh! You'll scare it away!!

I've made a feature req to have new perms not mess with appdata, and am considering creating a "docker safe" new perms tool in conjunction with fix common problems (but next on my plate is some changes to CA) Not a bad idea. Pain in the butt to figure out the permissions were messed up. I used to have all my dockers on an "UD" attached drive, I may consider moving my docker files back to it.

This morning I ran the new permissions script. Unraid then modified all my permissions including all my docker files. Then I noticed that this OpenVPN docker was no longer starting. I copied my old config folder and ended up recreating this docker with a new config folder. I then chmod --reference=newconfig_file oldconfig_file every folder/file and then copied back the old config file to get it to work. It is working now but I wonder if this docker should check the folder permissions at start and change them back to the correct ones?

Yeah, you made that one up in your head. Next rev or two however I was already planning on changing the logging and making it less verbose Lol, well good to know that I make up stuff. I was searching though the posts and was like hmmm where did that go...