ksignorini

Does anyone know if Q1 of the FAQ here: http://lime-technology.com/forum/index.php?topic=45811.msg437673#msg437674 would solve this? I'm not outside my LAN so I'm really not sure if this is the same problem. I don't want to reboot my server right now if I don't have to.

When the docker is running in Host mode I cannot access the UI. If I switch it to Bridge mode (which I don't want, right?) I can get to the login prompt. Why is this happening? Does anyone know how I can fix this?

I cannot get the WebUI for sab to launch. I've tried changing ports for the WebUI and that won't work, either. Ideas?

Ahhh. I understand. I'll give this a try! Thanks!

...my testing says, no. Anyone? If so, how?

I thought I saw an answer to this somewhere but I can't find it anymore. Can the OpenVPN Client be running and connected to a VPN and still allow incoming OpenVPN Server connections to the unRAID's network? Thank you.

I added Lynx text based browser. I tried a couple others but they would require a bunch of other packages. Thanks!

Great plugin--beats having to install all these slackpacks myself! Say, any chance you could include the Lynx text-based browser? Talk about a nerd-only package. Thanks again!

Also does this look right? Should the 2nd cache drive not show a FS format, size, or anything? (If this is correct, the screen is misleading and could give better information--like put the word "pooled" or something in each field showing that it's not just empty.)

What does "No balance found on /mnt/cache" mean in regards to having just added a 2nd SSD to my cache pool? (Was just one SSD until now.) When I added it and looked at the original, it was saying that balance was running and was showing some data in the balance info box. Now it just says "No balance found on /mnt/cache". Is that normal? Do I need to manually run the balance? If not, then why/when do you manually hit that button? Thanks!

How about when adding in Parity 2 to an already working array? I stopped the array, assigned the new disk as Parity 2, then restarted the array and it's rebuilding the parity on that drive. Is that all good? I don't need a new config for that? Thanks again.

This is very good to know. Is this described somewhere? I couldn't find much on Parity 2. (Or I missed it.)

You would just set a New Config without parity2, and check the box that says parity is valid, since it would be. So the two parity drives are independent of each other, right? Either one is a valid parity of the entire system?

All good points. FYI: The 2nd SSD is the same size as the original cache SSD, so I'm covered there. Now the waffling on what to do with the 2nd 4TB drive. How easy is it to pull out the 2nd parity drive and go back to single parity once it's been activated? i.e. I put in 2nd parity until my initial backups are complete, then yank parity 2 and turn it into storage space.

Well, both were such a good deal at a local store that I might now have to figure out what to do with the 2nd 4TB drive. Clearly the 2nd 480GB SSD is going into the cache pool. What is the true value of the 2nd parity drive, then? (Maybe this 2nd 4TB needs to become storage.)

Drives are 1 and 2 TB as you guessed. Parity, however is 4 TB. Another 4 TB is an investment as they will eventually replace the 2's most likely. If I can back up the cache (VMs and appdata) to the array or cloud then it's protected enough for me. Having the extra parity protection seems like a good idea. ...and I'm sitting outside the computer store.

I can do either of the following: 1. Add a 2nd parity drive. 2. Add a 2nd cache SSD. My setup is a 7 disk, 10TB unRAID array with a single 480GB cache SSD. I have a couple VM's on the cache drive and appdata. I'm using the array for personal data and mostly media. Thoughts? What would you do?

Did you get this solved? I'm having the same trouble on 6.2.4. Which solutions solved it?

AVG Free killed my Windows 10 Pro, too. I couldn't even repair the VM. Good thing I was just setting it up.

Yeah, it wasn't. Something must have gone wrong. Knowing that it should have been instantaneous, I SSH'd in and killed the resize process. A few seconds later I got my GUI back. Now I'm rebooting. Thanks.

I changed the size of a Windows 10 VM disk image from 30GB to 60GB about two hours ago. I fear the process is stuck. Since then, I can no longer log into the webGUI, however I can SSH into the server and can access data on it. How long should the resize process take? (Generally.) Thanks.

The key was switching to SeaBIOS. Worked like a charm. Thanks!

All good things to think about and try. I wasn't sure where to go to from here. Thanks!

I'm unable to get Windows 10 to pass through the GPU regardless of VM settings (I've tried every combination I could think of from # of cores, to emulated CPU). Or maybe, it's not just the GPU, maybe it's the whole VM not running. I'm not sure based on the logs. Windows 7 works with default VM settings. Ubuntu works with default VM settings. Both run fine and pass video through to the monitor. With Windows 10 I get a completely black screen and nothing is sent to the monitor at all. Can someone please help me get this working? At least I have Windows 7, but I would like to make Windows 10 work, too. Setup: unRAID 6.2.4 AMD 8320 FX Asus F5A97 R2.0 Asus Radeon R9 280X DIRECTCU II TOP Windows 10 Pro Logs are below. Another weird thing is that the logged time is not correct when I tried this time. Last time I tried I used emulated CPU instead of passthrough and log had correct time. Hostname has been changed to protect the innocent. 2017-01-27 15:45:34.099+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: BigHost LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 10' -S -machine pc-i440fx-2.5,accel=kvm,usb=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/cafb0014-670e-c3a5-5ba2-2a2363294745_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 2048 -realtime mlock=on -smp 1,sockets=1,cores=1,threads=1 -uuid cafb0014-670e-c3a5-5ba2-2a2363294745 -nographic -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.0u.guest_agent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x5 -device usb-host,hostbus=4,hostaddr=2,id=hostdev1 -device usb-host,hostbus=5,hostaddr=2,id=hostdev2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on Domain id=6 is tainted: high-privileges Domain id=6 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 0] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 1] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 2] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 3] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 4] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 5] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 6] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 7] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 8] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 9] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 12] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 13] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 14] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 15] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 16] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 17] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 23] warning: host doesn't support requested feature: CPUID.80000001H:EDX [bit 24]