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.

Xafloc

Members
  • Joined

  • Last visited

  1. I've suddenly, within the last week, had an issue with the plex instance I've been running for years go unclaimed. I've tried _numerous_ methods/efforts to reclaim the server, but continue to hit roadblocks. I have a reddit thread with my current efforts and debug, and would love to get some input. Based on my debugging, it appears that I'm potentially hitting either a DNS issue, or a docker network routing issue, in addition to it appears that plex may have removed or changed an API endpoint such that it doesn't exist anymore. Multiple posts on the internet found using this API URL, which now throws a 404: https://plex.tv/api/claim/exchange?token=12345 I've found another API that I'd like to try, but unRAID can't connect to it, and just times out, yet my other devices on the network can resolve and hit the endpoint with no issue: https://plex.tv/api/claim/token.json?token=12345 Would love a set of eyes on it that may know more...
  2. All, my UnRAID build has been fairly rock solid, except for I've been having some issues with my "Disk 1" getting some random failures. The disk would fail to mount occasionally, then get emulated from Parity. From there I would need to stop the array, rebuild the disk, etc. I suspected a bad drive, so I replaced the physical drive (Had no smart errors), and proceeded to have the same issue with random failures/lock-ups in UnRAID. I did some googling, and came across an obscure thread on a potential power problem, causing similar lockups. I opened up the server, and found that Disk 1 was at the end of the power supply chain for one of the connectors to the PSU. The secondary connector from the PSU (Each has 4 power connectors for HDs) only had 1 disk on it, so I switched Disk 1 to the 2nd connector, on the 2nd set of plugs to the PSU (Confusing??). Since then, no more issues. Okay, obviously a PSU problem. So... Looking for recommendations on a PSU I should be using instead. Here is my completed build: https://pcpartpicker.com/b/VK3bt6 And here is my current PSU: https://www.newegg.com/Product/Product.aspx?Item=N82E16817139051&nm_mc=AFC-C8Junction&cm_mmc=AFC-C8Junction-PCPartPicker, LLC-_-na-_-na-_-na&cm_sp=&AID=10446076&PID=3938566&SID= Thoughts?
  3. New user, just installed the docker, and the docker fails to start at all. No error in the UI, just says "Exited" right after starting it.
  4. Hoping someone can point me in the right direction. I followed the new "easy" Sierra method, but first installing on a Mac in Fusion, then converting the disk, etc. After that, tweaking the XML with the instructions and the osk from the original host, etc. To that point, all went well. It would boot fine, and via splashtop I'd have mouse/keyboard working great. From here, I'd now gone down the path of trying to get GPU passthrough, which has gone horribly. I'm going to try to provide as much info as possible, so that hopefully my problem is obvious and someone can tell me which direction to go. System: Dell T110 II -On-board video worked fine -Installed EVGA GT 610 2GB I went down two paths, one just using the hostdev config in the XML, and two using the qemu commandline arguments in the XML. Both end up with my unraid server becoming completely unresponsive to the point where I have to hard-power the server, and reboot. In the BIOS of the server, my only options for the embedded video controller are "Standard" and "Distributed". I've only been able to test Standard thus far. With distributed set, I don't get output to the embeded controller VGA port, so not sure what it is actually doing. Here is a fresh XML after clicking on "Edit", and then selecting the GT 610 for Video and Sound: <domain type='kvm'> <name>OSX</name> <uuid>0e173767-6e0e-a28c-1454-f594f779768c</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="libreelec.png" os="linux"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </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> <os> <type arch='x86_64' machine='pc-q35-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/0e173767-6e0e-a28c-1454-f594f779768c_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='2'/> </cpu> <clock offset='utc'> <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/user/domains/Sierra/Sierra.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <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> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:51:66:48'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </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='0x02' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> Here is the VNC config that worked for me, before I started down the GPU passthrough path: <interface type='bridge'> <mac address='52:54:00:51:66:48'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </interface> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' 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'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='none'/> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=REMOVED'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel'/> </qemu:commandline> </domain> Here are the changes I attempted, which locked up my system by putting the GPU settings in the commandline args: <interface type='bridge'> <mac address='52:54:00:51:66:48'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=02:00.0,bus=pcie.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=02:00.1,bus=pcie.0'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=REMOVED'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel'/> </qemu:commandline> </domain> Here is the non-commandline settings I used which also resulted in a locked up system: <interface type='bridge'> <mac address='52:54:00:51:66:48'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface> <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='0x02' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd'/> <qemu:arg value='-device'/> <qemu:arg value='usb-mouse'/> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=REMOVED'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel'/> </qemu:commandline> </domain> Hoping for any pointers here. Maybe given my BIOS limitations for the embedded video controller it won't work, but it would be good to know either way. Thanks!

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.