bobbintb

Members
  • Posts

    1295
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • MSN Messenger
    roberttheed@gmail.com

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

bobbintb's Achievements

Collaborator

Collaborator (7/14)

16

Reputation

  1. Unfortunately, that's an issue with qBittorrent itself. The webUI is lacking in some features and that is one of them. It is on their wishlist though, and will likely be added at some point. You can follow the progress here: https://github.com/qbittorrent/qBittorrent/issues/5614
  2. Sure, I can try and write something up. I tend to overcommit myself however so if you don't hear back from me soon, just PM me. Sorry for the late reply. I must have missed the notification for your post.
  3. I don't know of any containers that use that specific tool but there are others that support OneDrive. I'm sure you know that but I would recommend trying one of those and seeing if that would meet your needs (if you haven't already) before you try to build a new one.
  4. root@Tower:~# ls -lah /mnt/disk9/Docker total 0 drwxrwxrwx 2 nobody users 6 Mar 26 2017 ./ drwxrwxrwx 5 nobody users 71 Aug 29 04:30 ../ root@Tower:~# ls -lah /mnt/disk8/VMs total 0 drwxrwxrwx 2 nobody users 6 Nov 28 2018 ./ drwxrwxrwx 5 nobody users 84 Aug 29 04:30 ../ root@Tower:~#
  5. I don't even know anymore. I know I need to go through and take another look at how I have things configured. I didn't think I had anything related to the dockers on the array. I mean, many of them save files to the array, but there shouldn't be any sort of config files or anything anywhere other than the docker share on the cache drive.
  6. tower-diagnostics-20210830-2124.zip I wasn't sure when it was occurring so it took a while to figure it out. Nagios noticed a change on 08-30-2021 05:58:51 to the qbittorrent docker.
  7. Every once in a while, I will go to the docker tab and there will be an orphaned image or two. I remove them and reinstall with the previous template but it keeps happening. I've looked at threads with similar issues. I don't have the Advanced Buttons plugin installed. I've deleted the img before. I have CA set to update my dockers automatically at around 3am or so. I'm not sure why they get orphaned. It's not frequent, but it happens occasionally. I don't see anything in the logs that's blatantly obvious to someone that doesn't know what to look for. Any ideas?
  8. Yes, I saw there were some on docker hub. I was just hoping there was something similar already on CA because I won't have a lot of time to adapt one to unRAID for a while. Nagios might be a little overkill anyway.
  9. Occasionally, I get a docker image that quits responding. I restart it and everything is fine. I'm a little familiar with Nagios from my work. I'm looking for something similar but don't necessarily need it to be as robust. I also don't see Nagios on CA, so there's that. I just need to monitor the docker containers and restart them if the don't respond to a ping after a certain amount of time. I could make a simple script for this but would rather not spend the time if I don't have to. Is there anything on CA that will do this? Uptime Kuma looks like it might work but I don't its capabilities. It looks like it will notify me but not take action.
  10. I converted it to qcow2, left it as OVMF, and put it as SATA and it seems to work fine now. EDIT: spoke to soon. it only worked for one VM. I don't know why the other isn't working. It's the same config.
  11. I am trying to import a couple VMs that are vmdk. I used seabios as that seems to be what is recommended for vmdks and OVMF did not work at all. Anyway, it tells me there is no bootable disk. If I convert the vmdk to img using qemu-img it will boot but just go through the repair options and wont boot into Windows. I tried setting it to SATA, VirtIO, SCSI. Pretty sure I tried them all. I've done this before but I don't know what I'm missing. Any ideas? Perhaps I should try qcow2?
  12. Adding the correct registry entries fixed my issue but now I am just having trouble getting the GPO to run it on start up. I made a bat file that adds the registry entries. I can run it manually as admin and it works. Running it manually without admin does not, nor does having the GPO run the script on start up.
  13. Mine is i440fx-5.1. I'll see if I can find something on that or try the registry. Here is my XML: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='7'> <name>Windows 10</name> <uuid>68b80ce7-d359-e5d3-3d22-67d0d80d7012</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/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='32'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='33'/> <vcpupin vcpu='4' cpuset='2'/> <vcpupin vcpu='5' cpuset='34'/> <vcpupin vcpu='6' cpuset='3'/> <vcpupin vcpu='7' cpuset='35'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/68b80ce7-d359-e5d3-3d22-67d0d80d7012_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/cache/VMs/virtio-win-0.1.190.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:51:1f:d5'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <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-7-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <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> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' 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='0x02' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x23' slot='0x00' function='0x3'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
  14. I am having the same issue. I really don't want my kids ejecting the boot drive by mistake. I'm sure they won't be able to because it's in use bit I don't want to take that chance or test that theory.
  15. I know one can overprovision when creating a VM but I like to strictly assign cores and threads to each VM. When creating a new VM, I have to check with the other VMs to make sure I am assigning unassigned cores. It would be nice if the template showed already assigned cores, similar to how the Docker template shows already assigned ports.