archedraft

Community Developer
  • Posts

    2070
  • Joined

  • Last visited

Everything posted by archedraft

  1. Why do I always have to be special lol??? EDIT: added diagnostics since I appear to be special again
  2. Appears that 6.2b23 lost the year in my parity check history log (see attached). EDIT: added diagnostics since I appear to be special again
  3. Very nice. You want me to redirect the output of the script to a log file with the option to display it? Lol, squid your so good at this point, you can anticipate user requests before they are even asked.
  4. Just double checking--is this still the case? Every time I reboot my Windows VM (e.g., to install windows updates), my USB devices no longer show up and I have to reboot the whole server. Honestly, I'm having a hard time remembering the context of that post. Since then I now PCI-stub my USB controllers on boot so that they show up in unraids 6.2 VM editor. Therefore unRAID isn't even aware they exist. That said I can stop my windows 10 VM and then start my win 7 VM with the same USB controller and t works just fine. I wonder if you did the same if they would work after a VM reboot?
  5. Never say never so I'll give you a less than 1% chance that 6.2 final will be out by the end of July.
  6. You will have to manually edit the XML code per my instructions (If you are using 6.2 then the instructions are a little out of date regarding GPU and USB passthrough and I will not be updating them until 6.2 is released as final because so much can and probably will change). As far as someone creating a template, someone *might* be able to create a plugin that would modify unRAID's XML editor but that is way over my head. The time it would take for someone to create such a plugin would be a wasted effort in my opinion when we can just manually edit the XML.
  7. But the following XML just isn't even able to go to it: <domain type='kvm' id='20' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>OSX-El-Capitan-10.11-VNC</name> <uuid>0ba39646-7ba1-4d41-9602-e2968b2fe36d</uuid> <metadata/> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.5'>hvm</type> <kernel>/mnt/disk2/hackintosh/enoch_rev2795_boot</kernel> <boot dev='hd'/> <bootmenu enable='yes'/> </os> <features> <acpi/> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>core2duo</model> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/mnt/disk2/hackintosh/ElCapitan.img'/> <backingStore/> <target dev='hda' bus='sata'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:00:20:30'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='e1000-82545em'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <memballoon model='none'> <alias name='balloon0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <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=0000:01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on' /> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=0000:01:00.1,bus=root.1,addr=00.1'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> </qemu:commandline> </domain> I recieve the following error message: I tried several things, but it doesn't seem to like the whole qemu vfio-pci stuff. If I use the GT 710 for other VM's (which ofcourse are just done through this kind of XML: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </hostdev> It works fine. Anyone got experience or a solution for this? Cheers! Below is how you can get qemu working with 6.2, if the GPU is working with hostdev I personally wouldn't mess with it. The reason I did was I needed to pass through my USB controller and OS X only seems to pass through an USB controller with the qemu xml. http://lime-technology.com/forum/index.php?topic=49667.msg476287#msg476287
  8. Why not just use the hostdev code if it's working fine?
  9. Haha, I was thinking the same thing. 10 years is a long time though.
  10. 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.
  11. 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!
  12. 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.
  13. Peter, are you also having the same issue with the plugin starting at boot?
  14. 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"
  15. 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.
  16. Yes sir, a few times. I edit the VM to the correct VNC mode as suggested.
  17. Happy to hear it's a common issue and not the normal archedraft is "special" issue.
  18. 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.
  19. 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?
  20. That's pretty awesome! I would guess you are going to have to wait for nvidia to release newer drivers for OS X or attempt to install the 346.03.06 driver and see what happens. If you do, make sure you backup your OS X image so that if you break it you can just put the old image back and try again.
  21. 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.
  22. 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?
  23. 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
  24. If a parity check finds 1563 errors shouldn't the history status say something other than "OK" in the status?