spencers

I tried this as well before deleting the .key and .cert files but every time I started sabnzbd back up again, HTTPS would be enabled in the GUI. Perhaps the combination of disabling HHTPS in the .ini file fixed it for me instead of just deleting the files alone.

I too updated the sabnzbd container today and now i cannot access it. Appears to be same as WonkoTheSane. 2017-05-24 19:40:34,503 DEBG 'sabnzbd' stderr output: 2017-05-24 19:40:34,503::ERROR::[_cplogging:219] [24/May/2017:19:40:34] ENGINE Shutting down due to error in start listener: Traceback (most recent call last): File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 245, in start self.publish('start') File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 225, in publish raise exc ChannelFailures: SSLError(336245134, u'[SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2699)') Edit: FIXED! Stop sabnzbd, remove server.key and server.cert from the /sabnzbd/config/admin folder, then start back up sabnzbd.

+1 on reddit person talking smoke Run it all on one machine. That's what unRAID is for! One stop shop to run all of those services in Dockerized format, all on top of a parity protected array. Only issue I would see is if you're running a gaming VM on the unRAID box and Plex docker handling transcode jobs simultaneously while gaming.

I had similar problems last week that first showed itself with my unRAID box. Have the 2 LAN ports set up as LACP aggregated on my switch. unRAID pulled a 169 address, even after each reboot. I tried to break the bond but that didn't help. Then other clients, like my laptop, phone, etc dropped off the network with 169 addresses. Only way I was able to get unRAID back was to set a static IP in network.cfg (unplugged the flash drive and put it in my laptop to change the file). After that, I found the problem was my router (a Ubiquiti Edgerouter Lite), rebooted it and downgraded from a recently applied firmware (which I believe was the root cause). Had to restart all my client devices to pull DHCP. Long story short, as another person said, try manually setting a static IP in unRAID's network.cfg file.

Check my post above to see what I did. Basically, let it go until it finishes trying (and failing) to move files to the cache. Verify by watching the log. Then manually shut down/reboot. Fix the offending share's cache settings. Finally, invoke the mover to move data back to the array. There needs to be a way to stop the mover in situations like this.

Now the mover has gone through all the directories and files of the offending share and finished trying to move them to the cache (and failed due to being full). But the mover still says its running and I cannot stop it or the array. edit: I held the power button and the server shut down. Powered back up and activated the mover to move the files BACK to the array. The bigger question is how "Cache: prefer" got set on this share when I only changed permissions on the share yesterday. And if the mover can indeed be stopped. None of the commands in this thread worked for me.

Can this please be revisited? None of the commands in this thread stopped the mover. Somehow yesterday one of my shares got set to cache: prefer. The only settings I changed yesterday were user permissions. Now this morning I woke to notifications that my cache drive is FULL. And I cannot stop the mover!!!

Thank you for this script! I hope all is well danioj

I am not sure. But if you use ls -al from the command line, it will show all of the files. Vdisk is a single file, but I recommend using cp to keep the vdisk sparse, you'll lose that using MC. Good to know. Thanks.

Make sure that you didn't miss any system or hidden files when you did the copy. (Some file managers don't automatically display/transfer those files.) I used midnight commander to copy the .qcow2 file from cache to array. Would that miss any files?

After copying the VM disk from my array back to my SSD, the VM boots but is stuck at the windows 10 logo and spinning circle. I've turned off the GTX 1070 passthrough and just using VNC for simplicity's sake. I'm baffled as to what is wrong! The VM disk on the array boot just fine last night as a test. Why on earth won't it boot now after I copied it with midnight commander to my SSD?

I just experienced my first hiccup with my Win10 VM (nvidia 1070 passed through) in a long long time. Only thing I did recently was update to 6.2.4. I rebooted the VM from the Windows GUI and after logging in, the screen just goes black. So then I tried a shut down of the VM from the unRAID GUI and it wouldn't shut down. I had to force stop the VM. Upon reboot of the VM, it goes to the same black screen after logging in. I'm rebooting the unRAID server to see if that does anything. edit: Now my VM is just hanging at logging on. This was after seeing two blue screens: one about trying to write memory to read only followed by a system exception not handled. I'm stuck with a non-working VM now! edit2: Luckily I had a backup of the VM on the array from two weeks ago. I pointed the VM to use that disk and it boot fine. Do qcow2 files go bad? It's a 300GB whopper!

32GB now. My VM's love it.

C236 WSI + E3-1245 = the bees knees Best upgrade I've done so far in my Q25B setup!

Forgot to follow up. Moving to liftmaster2 solved the issue.

Lack of integrated graphics sticks out to me. But I'm not sure if it's required.

Just following up. I never got time to try the hack mentioned above. I replaced the CPU with a Xeon E3-1245 v5 and the GPU passes through wonderfully to my Windows 10 VM!

Ran across that earlier. Nice hack! I'll try it tomorrow

I'm kicking myself now. I think this is because the Xeon E3-1230 v5 doesn't have onboard graphics, therefore I can't passthrough the GTX 1070. Oversight on my part. Will send back and replace with a Xeon E3-1245 v5 (contains onboard graphics)

Hi all, Trying to figure out what's going on with my new setup. Went from Intel i5-4430, Asus H87I-PLUS, and 16GB RAM to a nice new Intel Xeon E3-1230 v5, Asrock C236 WSI, and 32GB RAM. I had a GTX 1070 passed through to a Windows 10 VM on my prior setup without any problem. Now with the new cpu/mobo/ram, upon boot of the VM, I get a Code 43 error in the Device Manager. I've changed nothing in my KVM settings. Is this because the Xeon does not have onboard graphics and unRAID is preventing KVM from taking over? I'm struggling to figure out what changed that is preventing passthrough! Attached is the System information screenshot. Current XML <domain type='kvm' id='1'> <name>win10</name> <uuid>ced4866f-ced8-dd49-e697-2b644628770f</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/ced4866f-ced8-dd49-e697-2b644628770f_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='2'/> </cpu> <clock offset='localtime'> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/cache/apps/kvm/win10/vdisk1.qcow2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:3e:28:96'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-win10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>

Thats a great setup and for a really nice price. Well done! "non-ECC" ==> WHY would you build a fault-tolerant server with a server-grade motherboard, a Xeon, and NOT take advantage of the error correcting memory support these components provide !!?? Not sure if it's fate, but my Amazon package with the non-ECC RAM was lost in transit. So I ordered 32gb of ECC RAM instead!

Here's Apple's official guide for Time Machine over SMB. https://developer.apple.com/library/content/releasenotes/NetworkingInternetWeb/Time_Machine_SMB_Spec/ Is unRAID's SMB version 3.x?

What's weird is that it'll take only one command, from either Nest OR MyQ. Any subsequent command goes to deaf ears. I'll have to try the liftmaster2 module rather than the MyQ. I do recall homebridge saying the MyQ module was deprecated but it installed anyway.

Check in to the Corsair SF450 as well. Great little tiny power supply!

I'm using Adair's homebridge docker and it seems to only work only once until I restart it. I've got mine loaded with Nest and Chamberlain MyQ. If I issue a command to Siri to close the garage door, it will close. But if I try another command, like change the temperature to 75 degrees, Siri doesn't get a response and therefore doesn't carry out the command. It will work after restarting the homebridge docker, but only one command works and then I have to restart it again. Shame as this could be very nifty! Any ideas?