Jump to content

dbs179

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

1 Neutral

About dbs179

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. Thank you. I didn't find that in any of my searches. I appreciate it.
  2. I have the same issue as well, dockers show an update. I update but they pull no data, the docker restarts and the "Update Ready" goes away, but if you check for updates again it comes back. My issue is limited to only Dockers from linuxserver, dockers from other Repo's work fine. I've tried all of the different fixes I can find in any of the recent (less than 2 years old) topics, including deleting the Docker Image and creating the dockers again from previous apps but that didn't help. I also tried changing my DNS settings to use Google (8.8.8.8 and 8.8.4.4) instead of my router (router was set to use google already) but that didn't help and I'm not running PiHole. I'm lost on what to do next or where to even begin to fix it. I'm not sure if it was just coincidence, but it seemed to pop up after I upgraded from 6.5.3 to 6.7.2. I've also tried to restore back to 6.5.3 but that didn't help either.
  3. Hi all, I'm trying to get NextCloud set up using MariaDB and Let's Encrypt (all LinuxServer dockers on the same UnRaid box) following the latest videos posted by SpaceInvaderOne's Youtube channel. As of now, I have it up and working almost perfectly, except for one problem. Using WebDAV I can't upload files larger than approx. 500MB. I've changed the File Handling Max Upload size on the Additional Settings page to be 2 GB. I can upload a 1GB file using the Windows NextCloud client with no problems, but using FileSync for Android or WinSCP with WebDAV the same file fails and I get the following error in the NextCloud Web Interface Logging Page. "Fatal webDAV SABRE\DAV\Exception\BadRequest: expected filesize 1087197866 got 603729920" The last number changes between attempts, but the error message is the same other than that. I thought it might have been a setting in Let's Encrypt, but I've set WinSCP to not even use the proxy URL and only the IP and Port of NextCloud, which didn't make any difference in the errors. Googling the error led me to some threads on the NextCloud forums about setting up cache settings and changing the the mysql.connect_timeout settings and setting a temp upload folder. I tried the instructions from this thread: https://help.nextcloud.com/t/cant-upload-files-bigger-512mb-sabre-dav-exception-badrequest-http-1-1-400-expected-filesize/7061 And this one: https://www.techandme.se/increase-max-file-size/ But still didn't have any luck. Any help would be greatly appreciated. Thanks, Dave
  4. Yep, I did, I just double checked it and it was off in the only two locations I could find it. I set it to 5 hours and then back to never, maybe it was just an issue with Windows, but I'll have to just try it and see. Update: Still no luck, with Sleep set to never in the power plan options and in the main power settings menu, I still have the same issue. Update 2: Still had video on the VM even though it wouldn't respond to ping's or remote connections, but didn't have a keyboard and mouse passed through yet to see if it was responsive, looks like it might be something with the network adapter. Update 3: Not sure what the problem was, I ended up building a new VM using a new Windows 10 ISO and using OVMF. This time I didn't have any of the error code 43 issues with my GPU pass through and didn't have the weird unresponsive issues I was having if the VM was idle.
  5. Hi all, I've been struggling to get a Windows 10 VM up and running in my UnRaid for a bit now. The first couple of issue I had can be found here GPU in R710 Server I got past those issues and have the VM starting up and being able to pass through the GT730 I've installed. The problem I'm having now, is that once I start the VM I'm initially able to log in with RDP, Teamviewer or Splashtop. But after I log out and the VM is idle for a bit (normally 5 to 15 minutes) it becomes unresponsive. Ping's to the machine time out, attempts to remote connect to it fail, I haven't hooked up a monitor yet to see what output I get locally (if any), but can if needed. I've tried the VM using just VNC and still have the same results. I did some searching but didn't find anything that stood out on the forums. My XML and VM Logs are below. Any help would be greatly appreciated. Thanks, Dave 2017-05-31 18:01:43.781+0000: starting up libvirt version: 2.4.0, qemu version: 2.7.1, hostname: UNRAID-RACK Domain id=1 is tainted: high-privileges Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2017-05-31T18:28:49.982564Z qemu-system-x86_64: terminating on signal 15 from pid 6586 2017-05-31 18:28:51.383+0000: shutting down, reason=destroyed 2017-05-31 18:29:16.941+0000: starting up libvirt version: 2.4.0, qemu version: 2.7.1, hostname: UNRAID-RACK Domain id=2 is tainted: high-privileges Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) <domain type='kvm' id='2'> <name>Kodi</name> <uuid>d563c503-5aa3-6ff0-ca5c-5fc3f83a8985</uuid> <description>Windows 10 Enterprise - SeaBIOS</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='9'/> <vcpupin vcpu='1' cpuset='10'/> <vcpupin vcpu='2' cpuset='21'/> <vcpupin vcpu='3' cpuset='22'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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='raw' cache='writeback'/> <source file='/mnt/cache/domains/Kodi/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/iso/virtio-win-0.1.126-2.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:37:a8:b8'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 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-2-Kodi/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> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x1'/> </source> <alias name='hostdev0'/> <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> <seclabel type='none' model='none'/> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
  6. I tried that exact google search, but I only found links pertaining to having only one GPU in the machine, or issues with VM being turned on. They were older threads, but SeaBIOS did the trick.
  7. Not a problem at all, I wouldn't be this far without your help. As a follow up for anybody seeing this thread in the future, I ended up ordering two new video cards, both the GT710 and GT730. I had the same results with both of them, error code 43 before nvidia drivers were even installed or the roms were dumped. The R710 has built in graphics and I had both the GT710 and GT730 installed for a total of 3 GPU's, so I knew it wasn't the issue that pops up when you only have one GPU installed. At any rate, I tried everything I could find in the forums and the only thing that fixed it was creating a new VM using SeaBios. Once I did that, the card showed up as it should without any error codes. I'm only RDP'ed in for now, but I suspect the video output is fine. I'm not sure why the cards wouldn't work with OVMF but they wouldn't. I know others say they should work with OVMF, but mine refused to. Anyway, I'll update again once I get a monitor hooked up to the new card.
  8. Ok, I've tried the steps listed in this guide to dump the rom and edit the VM XML, now I show the display adapter as GT610, but it still has an error code 43. I'll keep looking at possible fixes. Thanks again for your help.
  9. You must have a crystal ball! The fix above worked perfect once I put it in the correct place in the .cfg, but as you mentioned, I'm showing a "Windows has stopped this device because it has reported problems. (Code 43)" I've double checked that the "Hyper-V" setting is set to "No" and didn't have any drivers installed. Any ideas where I should go from here? And thanks again for all of the help, it has been very much appreciated. Thanks, Dave
  10. Perfect, thanks for the information. I was able to snip out the back of one of my 8x slots (they are on a riser so and I don't really need them) to fit in a GT610 I had laying around. The Server boots with it, so it must be under the 25W requirement and the card shows up in UnRaid System Devices, but when I try to set it as the Video and Audio cards I get an error starting the VM. With the VM set up to use VNC it works fine. Any thoughts? Thanks, DBS
  11. Hi all, I'm hoping to get some help here. I have a Dell R710 I'm running UnRaid 6.3.3. It is up and working nicely, however I would like to set up a Windows 10 VM on it to replace an aging desktop I use in my living room to stream web videos on. I mostly only use this machine to watch MotoGP from the motogp.com website. I've looked but can find any other simple way to get this content (Raspberry Pi, Plex Channels, etc.). Thus the reason this machine is still in my living room. I can get an HDMI from my living room to where the UnRaid is no problems, but from what I understand the Dell R710's have a maximum current rating of 25 Watts. Also the I/O Risers I have only have 8x PCIE slots, so I'd either have to try and cut the slots for a 16x card or stick with an 8x card. I've read that several folks in R710 threads have GT710's running just fine in their machines, but I've also read that the NVIDIA GeForce series of cards don't support operating in VM's, so I'm a bit lost. Any help finding a 8x card with less that 25 Watts draw, one HDMI on board and that works in VM's would be greatly appreciated. Thanks!
  12. Does anyone have more details on this, specifically what to put into the command line to upgrade? I haven't had any luck following the OwnCloud 9 upgrade instructions, but then again, I'm a rookie at best with this stuff. Thanks, Dave
  13. Thank you very much, At least I know I'm on the right track! I'll check out the bungy one. I quoted Edgar the first time instead of you, but you can use this Docker and have your data on the array. "I'm not very experienced with this at all, but here is what I ended up doing, map the OwnCloud installation data to the cache drive: /var/www/owncloud/data to /mnt/cache/appdata/owncloud Then add another mapping for user data /User Data to /mnt/user/User Data. Once you have OwnCloud up and running, go into the Apps page and enable external storage. You can then map the external storage to the /User Data mapping you set up in the Docker Config. This let me keep my configuration files on my cache drive, but store my uploaded and synced files on my Array."
  14. I'm not very experienced with this at all, but here is what I ended up doing, map the OwnCloud installation data to the cache drive: /var/www/owncloud/data to /mnt/cache/appdata/owncloud Then add another mapping for user data /User Data to /mnt/user/User Data. Once you have OwnCloud up and running, go into the Apps page and enable external storage. You can then map the external storage to the /User Data mapping you set up in the Docker Config. This let me keep my configuration files on my cache drive, but store my uploaded and synced files on my Array.
  15. I've seen this asked a few times, but I don't think I've seen an answer, or if there was I missed it. I'm staring from scratch with no other dockers installed. I'm installing using the community applications plug in. I keep all of the settings at default (volume map: /var/www/owncloud/data - /mnt/user/appdata/owncloud). I edit the subject variable name to contain all of my information and leave the "Edge" Variable at 0. Everything seems fine, but when I start the Docker, I can never get to the WebUI page and the log stops at "Creating DH Parameters File.". I'm sure it is something I'm doing wrong, but have no idea where to start. I've tried removing the container and image, deleting the appdata/owncloud folder and even removing the docker image file, but I still get the same thing each time. I thought it was a matter of being impatient, but I've waited over 15 minutes each time and still see the "Creating DH Parameters File" in the log. Any help would be greatly appreciated. Thanks!!! Update: Not sure what changed but I got it working, perhaps it takes longer than 15 minute to start up initially? At any rate I think I'm past that hurdle.