Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Sinister

Members
  • Joined

  • Last visited

Everything posted by Sinister

  1. This is what i am getting.
  2. I am not sure why i am currently getting this error at all i have not changed anything that i am aware of recently, even after adding a script to my go file and restarting the issue still persists. tower-diagnostics-20220121-1404.zip
  3. Good evening all i am back and have re-setup my plex docker, i am interested in ram transcoding and there seems to be several methods out there i just want to make sure i have done this right by sharing screenshots here.
  4. So the last drive finished rebuilding early my time around 5:30am I will keep an eye on it since switching the HBA card and report back in a few days
  5. all the internal drives are connected via a raid card a "LSI 9210-8i 6Gbps SAS SATA 8 Ports HBA PCI-E RAID Controller Card" none of the drives connected to it have failed lately its only been drives that are connected to the disk shelf which has been rock solid for over a year. the drives that keep failing are the ones that are connected via the diskshelf and thats only connected to server via the HBA, i think im gonna change the card since you say its best to avoid it. If nothing else it removes a point of failure.
  6. I have the server plugged into an "APC UPS 1500VA Battery Backup Surge Protector, BR1500G Backup Battery Power Supply with AVR" as well as my personal rig. nothing else seems to be experiencing errors of any kind. im so lost
  7. I am constantly getting disabled disk's I suspect there may be an issue with my HBA card "NetApp PM8003 Sierra 111-00341+B0 4-Port" as it was no longer supported and an individual on the forums created a custom implementation to get it working again. The drives continue to fail even though most are brand new/only days old and got through the clearing process without any errors, i am constantly having to shut the the server, remove the drive or drives, start up the server, have it recognize the drives are there via unassigned devices than do a rebuild to the array. Can someone tell me what i am missing here ? i have attached my diagnostics to help with the issue tower-diagnostics-20220115-1525.zip
  8. Thank you sir, worked like a charm
  9. So if i understand properly then my script would look like this: #!/bin/bash vm1="pfsense" sleep 15 virsh start "$vm1" where i could even move sleep to 30 ?
  10. Hi i dont know the first thing about scripts but am able to follow instructions well. I am looking for a script that will start my pfsense VM when the array is brought up manually, i found something like "virsh start pfsense" which does not seem to work unless i run it manually after the array has started. can anyone assist me with this ?
  11. 1TB samsung NVME only 150GB used not even close to full
  12. I removed the gpu ID and extra parameters settings in hopes it would work like it once did
  13. Sorry if this has been covered but i could not find my specific error message, I thought i was going to be a smart guy and try to add hardware transcoding to plex. It would not start after the setup, i followed youtube guide to the T after finishing plex would not start and when checking the logs i get Error: Unable to set up server: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE here is a screenshot of docker i am using Please help i dont want to set it up all over again
  14. Is GPU passthrough working now on 6.9.2 ? didnt seem to be the case a month ago at least, alot of people had to revert to 6.8.3. I would like to know your experience.
  15. Hello, im not trying to hijack the thread by i am experiencing a similar problem trying to passthrough a GTX 960 to a windows 10 VM. I have dumped my video cards bios per spaceinvader videos, i have tried seabios, ovmf, i have edited the XML every which way i can think of and am using the latest windows 10 ISO from microsoft. when using VNC i am able to create a windows 10 VM following spaceinvader instructions and boot into windows successfully, when passingthrough the GPU i get thrown into the UEFI interactive shell and typing exit and trying to boot from the boot manager does not work. I have tried multiple different bios files IOMMU is enabled, HVM is enabled, the card is in its own IOMMU group with the audio part of the card. at this point i have created well over 70+ VMs trying to get this to work can someone please offer some guidance as to what i am doing wrong. attached is the code for my current VM <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10 Gaming</name> <uuid>af68722e-fe54-4855-f02b-9ffaea16b684</uuid> <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'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='4'/> <vcpupin vcpu='4' cpuset='15'/> <vcpupin vcpu='5' cpuset='16'/> <vcpupin vcpu='6' cpuset='17'/> <vcpupin vcpu='7' cpuset='18'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-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/af68722e-fe54-4855-f02b-9ffaea16b684_VARS-pure-efi.fd</nvram> </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'/> </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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10 Gaming/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Operating Systems/Win10_21H1_English_x64.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.190-1.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:5a:36:5d'/> <source bridge='virbr0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x87' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/vbios/gtx960org.dump'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x87' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc52e'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <memballoon model='none'/> </devices> </domain>
  16. Thank you all, everything is now working as intended
  17. Just the one that was recommended ?
  18. Thank you for responding. So should every tag like ${AppDir} or ${MainDir} be removed ?
  19. Have followed this advice, yet my downloads still seem to still be pointed to inside of the container. This is driving me crazy as i dont know what im doing wrong here and my mappings are similar to this they seem to point to /usr/local/bin/nzbget/data/completed/Movies/name of file. I also have radarr reporting "You are using docker; download client nzbget places downloads in /usr/local/bin/nzbget/data/completed/Movies but this directory does not appear to exist inside the container. Review your remote path mappings and container volume settings." can anyone shed light on what ive messed up here ?
  20. I can confirm re-downloading the ovpn files and adding the datacipher line has resolved the issue for me
  21. Its not something i can fix used AVAST as an antivirus and firewall the only way to get around this issue was to remove the firewall component of the software completely. Not even disabling it was good enough

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.