oh-tomo

My Nvidia Shield auto-updated to Kodi 19. I noticed this because when I launched Kodi the launch screen is different and at the bottom of the screen there's the message "Database migration in progress - please wait." I guess I have to uninstall 19 and manually install 18.9 until there's a headless update to support Kodi 19? Or maybe Kodi isn't stuck I'm just not waiting long enough. But the current compatibility notes for headless don't mention compatibility beyond 18.

Thanks! Trying this: <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/disks/SSD_1TB/domains/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader> <nvram>/mnt/disks/SSD_1TB/domains/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram> </os>

I tried deleting the topology line. Changing the CPU and RAM. Still distorted. Any other suggestions? <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>MacinaboxCatalina</name> <uuid>bf4c91f6-cd91-464a-a7dc-f01d09138e03</uuid> <description>MacOS Catalina</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="Catalina"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/bf4c91f6-cd91-464a-a7dc-f01d09138e03_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <cache mode='passthrough'/> </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='qcow2' cache='writeback'/> <source file='/mnt/disks/SSD_1TB/domains/MacinaboxCatalina/Clover.qcow2'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/SSD_1TB/domains/MacinaboxCatalina/Catalina-install.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/disks/SSD_1TB/domains/MacinaboxCatalina/macos_disk.img'/> <target dev='hde' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </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='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </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> <interface type='bridge'> <mac address='52:54:00:de:ec:a2'/> <source bridge='br0'/> <model type='vmxnet3'/> <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='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <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='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='************************'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain>

Tried doing MacinaboxCatalina and see the distorted 4/12 screens (don't know the technical term for this video anomaly) during the boot of the MacOS recovery stage. Maybe I should try High Sierra?

I am remotely connected to my WIndows 10 VM using Chrome Remote Desktop and the highest resolution listed in Window's settings is 2560 x 1600. Is that the limit? Is there a way to connect matching my laptop's resolution of 3200 x 1800? Who is setting that limit? Windows or the Remote Desktop software?

So I guess MediaElch doesn't work for TV anymore because it uses thetvdb ? MediaElch 2020-09-04 23:29:04.901 WARN : [TheTvDb][ApiRequest] Network Error: "Error downloading https://api.thetvdb.com/episodes/ - server replied: Not Found" for URL QUrl("https://api.thetvdb.com/episodes/")

Just installed this to see if I could get the VisualEditor to work but I'm getting this error when I try to invoke it when editing my first page: Any hint at getting this to work? I see there's a /mnt/user/appdata/mediawiki/parsoid folder -- parsoid is what I understand is necessary for VisualEditor to work. Is there additional configuration necessary? My version page lists VisualEditor 0.1.1 as one of the editors. Update: stopping and starting MediaWiki in Docker seemed to fix it.

Turns out turning off this extension restored the page: https://chrome.google.com/webstore/detail/googlescope/gnnlgfolofpjdgjhfejmlcabaedmdfcn

Just noticed this today that the unRAID WebUI is blank (empty white page) in Chrome Version 83.0.4103.97 (Official Build) (64-bit). Checked in Firefox and the WebUI it intact there. How to fix for Chrome?

Google Backup and Sync is another heavy CPU user. Plus I run Evernote & Picasa, whose databases are saved on "symlinks" to unRAID shares created using Directory Linker, an app outlined in SpaceInvader's VM tutorial video. Is 15 above average for tabs open? On tech podcasts, the journalists claim they have so many tabs open that they can no longer read the names of the websites or see the icons. So I thought 15 seemed low by comparison. Going back to the 90's, I've used lynx, Navigator, Internet Explorer, and Firefox before settling on Chrome. I like Chrome. It lets me install handy extensions like Context Menu Search and saves my settings and history across devices. Also nowadays, whenever website tech support reps recommend a browser for optimal experience of their website, it's Chrome.

I've been getting daily Chrome crashes in my Win10 VM ( ~15 tabs open). Would a CPU upgrade fix that? Current CPU is Intel Core i3-8100 3.6 GHz Quad-Core Processor which I paid $159 for 14 months ago. Current RAM is G.Skill Ripjaws V Series 32 GB (2 x 16 GB) DDR4-3000 Memory. How much would I have to spend to stop the Chrome crashes? CPU usage in Win10 VM goes as high as 90 to 99% and Physical RAM looks around 50%.

I get "forwarding not set" when activated. OpenVPN works but can't get WireGuard to work in its place. Am I supposed to remove OpenVPN before WireGuard can work? They have different port settings.

How do I delete a tunnel? I have two. edit: found it in advanced.

I got this: https://www.amazon.ca/gp/product/B01E9Z2D60/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 it works

I have added an additional drive, would that have halted the autostart? Or maybe I read something back when I set up the server back in 2018 about not enabling autostart and left it like that. First I shut down. Added drive. Powered on. Began drive clearing process. Saw notification about OS 6.7 being vulnerable. Upgraded to 6.8.2. Remotely stopped clearing drive process and rebooted. Now I can't VPN in. Is Wireguard the 6.8 feature that I wouldn't have had yet and it works prior to starting the array? I don't know why I never saw notifications for updating to 6.8.

I wanted to VPN into my unRAID dashboard to start it after an upgrade reboot from OS 6.7 to 6.8.2, but VPN isn't connecting. So I guess Docker items like OpenVPN don't start until the unRAID has been manually started by me on site? Or Docker items won't autostart after an OS update? Makes remotely updating the OS kind of difficult....

Well it says Frodo/Gotham compatible, and Leia is the current version.... The top most post was written in 2011 and updated 2014. And the download link page doesn't have the executable.

When I log into my Win10 VM and launch Kodi, this message pops up "ERROR: Unable to create GUI. Exiting"

I would like to run Kodi on my Win10 VM. Not to play video, just to do database additions/corrections remotely. Would any PCIe x1 Video Card allow me to do it? One x1 slot is all I have left open on my motherboard. (x16 and x1 are taken for SATA and USB.) What's a good x1 video card to get? And I assume I'd get a side benefit of audio playback over HDMI from the video card for programs like Winamp too, no?

Well I can't login to the WD site. I can't rest my password on the WD site. And the WD site's customer portal apologizes for the inconvenience when my case details won't go through. And my email to [email protected] bounces back with "this email is not monitored, please use customer portal." And unRAID now says "Disk 6 in error state (disk dsbl)" This is the third time I've tried, the first with a new drive cage. But I guess the new drive cage ain't helping. Any other ideas?

"Last smart test result: Completed without error" Now what? WDC_WD60EFRX-68MYMN1_WD-WX21DC43D5UZ-20190804-0808.txt

So I got a new iStar dock and have now re-added this same HDD yesterday as a new disk and this morning I see a "Array has 1 disk with read errors" warning. How can the same HDD pass the WD Diagnostics extended test and then get read errors in unRAID, now connected via a brand new dock? Currently 10% into a SMART extended self-test of HDD.

Tried to print for the first time in my Win 10 VM and Brother printer driver wouldn't install. Microsoft support suggested updating Windows because I wasn't on the latest Windows and the latest is supposed to have printer fixes, so we downloaded and ran the Microsoft Windows MediaCreation updater a few hours ago. Checked on it just now via VNC and screen is Tianocore over black. Forced stop VM (because normal stop didn't stop) and restarted to just see Tianocore and spinning dots over black for a while. Forced stop again and unchecked CPU 1 and 2 leaving 3 checked and 0 unchecked. Spinning dots frozen. Forced stop again and checked CPU 0 and unchecked 1-3. Two frozen dots on black Tianocore. (Four single CPUs) Any ideas? Back to CPUs 1-3 checked because then the dots were at least spinning? update: Went to CPUs 0-3 checked and unplugged all USB devices and finally got to blue update screen and spinning white dots with 90% "working on updates" message.

New HDD in Disk 4 position working fine so far. Ran an extended test on the old HDD with WD Diagnostics in Windows (connected via USB 3.0 HDD dock) and it passed. So not sure why it got disabled twice in unRAID array if WD Diagnostics can't find a problem. I'll wait until new iStar dock arrives and add it as a new disk and see if it fails a third time.

Disk 4 disabled again. Replaced with new disk and reconstruction started again. Still waiting for replacement iStar dock to arrive. I’ll feel safer adding more drives when that arrives.