crazykidguy
-
Posts
35 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by crazykidguy
-
-
9 hours ago, jonathanm said:
It emulates a physical keyboard, mouse and monitor. Whatever comes up on a monitor connected locally is what you will see with a pikvm. It doesn't change any capabilities of the connected system.
Thanks, I was referring to the issue of having only 1 GPU in the system. I remember that it was necessary that no video out was connected to the GPU if I wanted to pass it through to a VM or Docker -- which is why my server is running headless actually. My understanding is that if I plug in the pikvm to that GPU, Unraid will use that GPU for video out and I may not be able to use it for other things.
Is that tracking or am I misunderstanding? I've always ran Unraid headless so I don't know if certain things have changed that would mitigate this.
-
On 4/29/2021 at 3:07 AM, NGDM said:
Have you ever found a reason/solution to this?
I'm encountering this issue also.
On 5/2/2021 at 2:47 AM, NVS1 said:Did you ever get an answer to this? It seems as though I'm encountering this issue too... only solution right now is to restart my container, and then everything clears up. After a couple days, my trackers will start showing HnR's and such, and they're not seeing any of my torrents being seeded.
Unfortunately I never got an answer to my issue. I ended up routinely going into Deluge to pause all the torrents and then restarting them, then I would verify it's being seen by the trackers.
It doesn't seem to have been happening since I made my last post about this but I would say probably check if there's any updates you can make to the image or if everything is ok with your VPN port-forwarding service. I was using PIA and believe the endpoint for my port-forwarding went down and I had to update that.
-
On 1/6/2021 at 8:57 PM, gfjardim said:
Hey I was just looking into pikvm for my use case. Do run an Intel CPU with an iGPU?
I'm not sure if pikvm would work for me since I'm running a Ryzen 2600, and my only GPU is reserved for transcoding. As far as I know, Unraid won't allow that GPU to be passed through if an output is connected to it upon reboot. Other than that, I'm not sure where the pikvm video in would be connected to for me.
-
I'm running a Ryzen 7 2700X and had a windows 10 vm running fine. I was looking to update the Windows Subsystem for Linux to WSL 2 following this guide: https://docs.microsoft.com/en-us/windows/wsl/install-win10
I ran the enable virtual machine command:
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestartand after restarting, the VM no longer boots to Windows login screen. I've had a similar thing happen before when I tried to enable Docker within a Win 10 VM and I ended up having to scrap that vdisk entirely.
Is there anyway to restore this VM? Using VNC Remote, I only get the "Guest hasn't initialized display yet" message and there also doesn't seem to be anything in the vm log:
-no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=0xb,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x3 \ -device pcie-root-port,port=0xc,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x4 \ -device pcie-pci-bridge,id=pci.7,bus=pci.1,addr=0x0 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/windows/windows10/Windows.iso","node-name":"libvirt-3-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":true,"driver":"raw","file":"libvirt-3-storage"}' \ -device ide-cd,bus=ide.0,drive=libvirt-3-format,id=sata0-0-0,bootindex=2 \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.173-2.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device ide-cd,bus=ide.1,drive=libvirt-2-format,id=sata0-0-1 \ -blockdev '{"driver":"file","filename":"/mnt/disks/Samsung_850_EVO/VMdisks/Multi-use VM/vdisk1.img","node-name":"libvirt-1-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-hd,bus=ide.2,drive=libvirt-1-format,id=sata0-0-2,bootindex=1,write-cache=on \ -netdev tap,fd=37,id=hostnet0,vhost=on,vhostfd=38 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:f5:3f:fa,bus=pci.3,addr=0x0 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=39,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -vnc 0.0.0.0:1,websocket=5701 \ -k en-us \ -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.7,addr=0x1 \ -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2021-02-10 04:06:30.179+0000: Domain id=15 is tainted: high-privileges 2021-02-10 04:06:30.179+0000: Domain id=15 is tainted: host-cpu char device redirected to /dev/pts/1 (label charserial0) -
14 hours ago, onufry said:
hey,
any updates on this?
i've experienced same "missing NVMe cache drive" situation with 1 of the 2 cache drives (in a pool) goes missing. using 2x Samsung 980_PRO 1TB. it happens often enough to be annoyed.
from the log i can see these lines when it happened:
Jan 20 18:32:54 JJ-NAS kernel: nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x2010
Jan 20 18:33:51 JJ-NAS login[402]: ROOT LOGIN on '/dev/pts/0'
Jan 20 18:33:56 JJ-NAS kernel: nvme nvme0: I/O 16 QID 0 timeout, disable controller
Jan 20 18:34:16 JJ-NAS kernel: nvme nvme0: Device not ready; aborting reset
Jan 20 18:34:16 JJ-NAS kernel: nvme nvme0: Identify Controller failed (-4)
Jan 20 18:34:16 JJ-NAS kernel: nvme nvme0: Removing after probe failure status: -5
Jan 20 18:34:16 JJ-NAS kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 75281, rd 7, flush 15132, corrupt 0, gen 0
Jan 20 18:34:16 JJ-NAS kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 75282, rd 7, flush 15132, corrupt 0, gen 0errors continue...
after a drive goes missing i still can see Cache "active" and SMART showing healthy, but no temp showing. Entering Cache Self-test shows that disk is not available and must be spun up, clicking "Spin Up" does nothing.
reboot does not bring back the drive. it looks like a shutdown and hard press start does (i did enter the BIOS though and exited without save).
thanks in advance for any help / suggestions
mobo: ASROCK X570M Pro4 (BIOS P3.30)
CPU: Ryzen 3400G
RAM: 32GB
Cache Pool: 2x Samsung NVMe 980 PRO 1TB
Array: 4x 8TB Seagate IronWolf
Parity: 1x 12TB Seagate IronWolf
Yea it sounds like the same kind of error I was seeing. Rebooting the entire array multiple times can sometimes bring the cache back -- otherwise I usually had to do a hard reset. Even adding
nvme_core.default_ps_max_latency_us=0as suggested by JorgeB didn't help. I also tried switching the file system on the NVME from btrfs to xfs, no success. It could have been a power state issue could sometimes pop up without any activity on the drive (so the temp of the drive would just be at idle temp).
Perhaps a BIOS update could help like JorgeB mentioned. My motherboard is a MSI Tomahawk B450 MAX v.7C02v35 paired with a Ryzen 2700X but I've never tried updating the BIOS to resolve this issue.
Eventually I gave up trying to diagnose the problem and switched over to a WD NVME drive. Have been solid ever since. Interestingly, I don't have a heat sink on this one whereas I did on the ADATA but temps have been fine.
-
I have a few cameras that send video recordings and images via Unraid's FTP server to a UD disk. Eventually that disk will fill up and I manually go in to delete the oldest files which is cumbersome. I know pretty much all NVR systems have a function to delete the oldest files as storage space is used up but how are people using systems like Blue Iris / dockers (Shinobi/Zoneminder) / or even just a spare disk like me, manage their storage space?
I've never used Blue Iris so I'm not sure if that offers a similar feature of removing the oldest files automatically.
-
Is the key in the CA template correct for the username and pass? On a fresh pull, the keys DB_USER and DB_PASS don't seem to flow over to www/.env. Took me a couple hours of fidgeting to check .env and see the values weren't matching what I was passing through.
I edited the keys on the template to DB_USERNAME and DB_PASSWORD and was able to hit the login page.
-
Thanks, I added it last time when I brought this up but realize now that I had it in the incorrect order, after the initrd section. I'll make the fix and see if the issue resolves.
-
Picking back up on this old thread since the problem still persists and has been appearing here and there since the last time I posted. I was able to grab the diagnostics from the most recent time when this happened and it seems to start with the I/O errors on the nvme drive, similar to the linked post. However I don't think the drive temperatures ever exceeded 40C in my case.
The system logs are unfortunately cluttered with a lot of FTP logs so the first error starts around line 8980.
My array is on xfs and I've since switched the cache drive in question to xfs from btrfs. However, I do have xfs, ntfs, and btrfs drives in use through UD.
-
@rjlan were you able to set up totp 2fa using that frontend repo you linked to? I've got everything working but 2fa using totp.
I've tried passing through an EXTENSION:auth-totp variable with no luck. Every time I'm still able to log in as the cloned admin user without the 2fa prompt.
-
Can anyone advise on how do you properly configure a reverse proxy host to use websockets in a reverse proxy? I'm trying to put code-server behind a reverse proxy and Authelia. I can get authenticated and hit the code-server container but I think something is not being routed correctly for websocket since I see the browser kicking out a bunch of script related errors. I have it enabled in the GUI and below is my config. I'm aware that depending on how the application was written, I have to proxy absolute paths as well for to get the appropriate resources and that's what the additional locations are doing (hopefully).
-
What are some apps you use to start/organize a personal knowledge library? Something to store notes/screenshots and just a place to keep track of things. I've been looking around on the Community Apps page but there doesn't seem to be too many readily available. Preferably something dockerized would be great.
-
On 8/7/2020 at 7:38 PM, aptalca said:
That's really a question for code-server
Thanks, I opened an issue with code-server and they weren't able to reproduce the problem with a fresh install and on the same version. Here are some additional logs from the remote extension host in vscode when I try to run the command.
According to code-server, it seems like packages were missing during installation in /node_modules/code-server/lib/vscode/extensions/emmet. I followed their suggested workaround and ran sudo yarn in /node_modules/code-server/lib/vscode/extensions/emmet and that has properly installed the missing packages and Emmet is working again.
[2020-08-11 15:54:20.929] [exthost] [error] [vscode.emmet] provider FAILED [2020-08-11 15:54:20.931] [exthost] [error] Error: Cannot find module 'vscode-emmet-helper' Require stack: - /node_modules/code-server/lib/vscode/extensions/emmet/dist/extension.js - /node_modules/code-server/lib/vscode/out/vs/loader.js - /node_modules/code-server/lib/vscode/out/bootstrap-amd.js - /node_modules/code-server/lib/vscode/out/bootstrap-fork.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15) at Function.Module._load (internal/modules/cjs/loader.js:842:27) at Function.t._load (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:956:846) at Function.n._load (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:926:106) at Function.i._load (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:922:391) at Module.require (internal/modules/cjs/loader.js:1026:19) at require (internal/modules/cjs/helpers.js:72:18) at Object.<anonymous> (/node_modules/code-server/lib/vscode/extensions/emmet/dist/extension.js:1:59931) at n (/node_modules/code-server/lib/vscode/extensions/emmet/dist/extension.js:1:158) at Object.t.getEmmetHelper (/node_modules/code-server/lib/vscode/extensions/emmet/dist/extension.js:1:3341) at t.DefaultCompletionItemProvider.provideCompletionItemsInternal (/node_modules/code-server/lib/vscode/extensions/emmet/dist/extension.js:1:53050) at t.DefaultCompletionItemProvider.provideCompletionItems (/node_modules/code-server/lib/vscode/extensions/emmet/dist/extension.js:1:52275) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:675:521 at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:51:988 at new Promise (<anonymous>) at Object.t.asPromise (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:51:960) at H.provideCompletionItems (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:675:492) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:694:883 at e._withAdapter (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:685:862) at e.$provideCompletionItems (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:694:861) at e._doInvokeHandler (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:790:363) at e._invokeHandler (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:790:55) at e._receiveRequest (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:788:688) at e._receiveOneMessage (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:787:518) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:785:754 at e.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:67) at v.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:232:615) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:958:347 at e.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:67) at v.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:232:615) at t.PersistentProtocol._receiveMessage (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:237:17) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:234:155 at e.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:67) at p.acceptChunk (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:230:129) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:229:483 at e.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:67) at f._acceptChunk (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:241:182) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:239:346 at Socket.t (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:238:565) at Socket.emit (events.js:315:20) at addChunk (_stream_readable.js:295:12) at readableAddChunk (_stream_readable.js:271:9) at Socket.Readable.push (_stream_readable.js:212:10) at TCP.onStreamRead (internal/stream_base_commons.js:186:23) [2020-08-11 15:55:01.133] [exthost] [error] TypeError: s.updateExtensionsPath is not a function at c (/node_modules/code-server/lib/vscode/extensions/emmet/dist/extension.js:1:2978) at Object.t.getEmmetHelper (/node_modules/code-server/lib/vscode/extensions/emmet/dist/extension.js:1:3348) at Object.t.expandEmmetAbbreviation (/node_modules/code-server/lib/vscode/extensions/emmet/dist/extension.js:1:41608) at /node_modules/code-server/lib/vscode/extensions/emmet/dist/extension.js:1:48572 at e._executeContributedCommand (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:627:753) at e.$executeContributedCommand (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:628:104) at e._doInvokeHandler (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:790:363) at e._invokeHandler (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:790:55) at e._receiveRequest (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:788:739) at e._receiveOneMessage (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:787:518) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:785:754 at e.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:67) at v.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:232:615) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:958:347 at e.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:67) at v.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:232:615) at t.PersistentProtocol._receiveMessage (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:237:17) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:234:155 at e.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:67) at p.acceptChunk (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:230:129) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:229:483 at e.fire (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:67) at f._acceptChunk (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:241:182) at /node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:239:346 at Socket.t (/node_modules/code-server/lib/vscode/out/vs/workbench/services/extensions/node/extensionHostProcess.js:238:565) at Socket.emit (events.js:315:20) at addChunk (_stream_readable.js:295:12) at readableAddChunk (_stream_readable.js:271:9) at Socket.Readable.push (_stream_readable.js:212:10) at TCP.onStreamRead (internal/stream_base_commons.js:186:23) emmet.expandAbbreviation
From the
-
Hi, I'm getting the following error trying to use Emmet expansions:
Running the contributed command: 'emmet.expandAbbreviation' failed.
Here are my setting configs:
I thought it was because I messed up some config but I removed the docker + wiped appdata folder but the issue persists. I get the expansion error trying to expand ! or anything like ul>li*3 for example.
Is this a code-server issue?
-
I bought a ADATA SX8100NP to replace my smaller capacity Samsung 850 EVO a while back. The Adata drive has been running fine but recently it will just disappear from the array and won't show until I completely shutdown and restart the server. I tried re-seating it the very first time it happened but recently the issue kept coming back. I forgot to grab the full diagnostics from last time before I restarted the server but I've attached SMART report. I've been reading mixed info about SMART tests on NVME drives so I'm not sure if this is an indication there's something wrong with the drive's functionality.
The drive is plugged in directly to my motherboard (B450 Tomahawk Max) via the M.2 slot.
-
Anyone else getting an issue like below where the torrents stop announcing/ updating to the trackers? They seed perfectly normal for an amount of time and when I happen to check it after some time, they look like the ones below with (0) on Seeds and Peers. I have to manually pause and restart the seed to get the Seeds and Peers to display and the Tracker Status to read OK.
Any idea what's causing this? I'm behind PIA and again, things seem to seed perfectly find initially after I restart the torrents. It's after some unknown time for some unknown reason they stop announcing.
-
Love the community aspect of Unraid. The wide user-base that ranges from beginners to enterprise sys-admins and the amazing third-party devs really drew me to explore the software and be more comfortable with Linux.
Would love to see an out-of-the-box, user opt-in function for system stats reporting so users who'd like to gain more insight into what their systems are doing won't have to rely on multiple third-party dockers/apps/plugins.
-
Hi, I've gotten everything working according to detailed post on reddit and have Telegraf configured to report every 30s to InfluxDB. But I'm noticing that my disks are not spinning down ever since I started using Telegraf, InfluxDB, Grafana, and HDDTemp. Are the disks unable to be spun down because Telegraf and HDDTemp is collecting disk info? I tried disabling HDDTemp for now but it doesn't seem to be allowing the disks to be kept spun down.
To be clear, I mean to keep the disks spun down within the array and on Unassigned Devices. I can spin down the disks in the array perfectly fine but they don't stay spun down even when nothing is accessing the array.
-
12 hours ago, testdasi said:
You need to clarify what you meant by "couldn't get it to boot". It's ambiguous.
Does the VM errors out when you click Start? Does it show the Tianocore screen but get stuck there? Does it boot into a command line interface? Does it get in a boot loop?
You can change machine type with no issue (but you have to create a new template - the GUI can't handle changing machine type on an existing template).
The exception to that is if you were on SeaBIOS (default for typical guide with i440fx) and switching to OVMF (required for Q35). From my experience, that won't work out of the box.
Also make sure your vdisk settings is of the right format (check your xml), especially if you were using qcow2 in the old template.
Sorry, I should've clarified. I've set up 2 VM templates with Q35 and i440fx machine types to test the vdisk. No pass-throughs, VNC only, 4cores/8threads, Ryzen 2700x.
On the Q35 machine, the VM gets to the TianoCore load screen and then kicks me into the standard Win10 recovery menu. I try hitting the Diagnose option and it will go to the screen where it runs the disk check but eventually I will get an error that the disk check failed. I then tried loading the driver based on this thread but it didn't work either:
If I ignore it and tell the machine to restart anyway, it will go back to the TianoCore screen and spin until it freezes.
On i440fx, the VM doesn't get pass the TianoCore screen and continues to do the load up spinning animation.
I've let both tests spin for over 4 hours and nothing ever comes up.
-
I recently upgraded my system from Intel to Ryzen and didn't save the XML for my Win10 VM but I still have its vdisk. I fired up a different VM with a different machine type (i440fx to Q35) and CPU cores (increased cores) and pointed the primary vdisk to the old disk location but I couldn't get it to boot. I tried decreasing the core count and no GPU passthrough to try to make sure it's nothing funny with the GPU.
Is it not possible to boot an old vdisk with different VM settings as the original VM?
Once you've created a VM, are you not able to change its machine type and add/remove cores with the same vdisk? I tried doing this with a new VM and it would not boot after I changed the machine type.
-
On 7/3/2019 at 9:18 PM, crazykidguy said:
I've this weird issue where season searches from within Sonarr will return results from my indexers but they don't get forwarded to SABnzbd. However everything works fine if I search each episode individually using the auto search function.
Any idea why? The logs indicate there were results returned but it's just missing that last step of pushing it to SAB.
The yellow logs are from the manual search.
So I think I've found the problem which is when a batch search doesn't return results for any particular search, it botches for some reason and nothing gets piped over to sab, even if there were legit hits before.
-
I've this weird issue where season searches from within Sonarr will return results from my indexers but they don't get forwarded to SABnzbd. However everything works fine if I search each episode individually using the auto search function.
Any idea why? The logs indicate there were results returned but it's just missing that last step of pushing it to SAB.
The yellow logs are from the manual search.
-
I have been using the RDP built into Windows to connect. I did a bit of research and realized RDP may not be able to deliver the smoothest experience and graphics performance but I'm only expecting a smooth user-experience and not trying to run games here.
Are there other RDP clients I can try that may give better results than the built-in Windows one? I've tried splashtop but I think I'm running into the black-screen issue because I'm only using an iGPU instead of a dedicated GPU. Tried installing mirrordrivers and still no screen.
My ultimate goal is for this VM to accessible via a dummy terminal or low-powered HTPC for simple media consumption/web browsing without plugging anything into the server.
Edit: I'd also add that the windows RDP connection is currently ran through ethernet to the VM itself so I don't think it's a connection/speed issue.
-
I've had my box for about a year and I've got Windows 10 set up on a VM, doing mostly browsing/non-intensive development work. I set up the Windows 10 VM using spaceinvader's very popular video series. However I've noticed that the aesthetics/ general feel of the usage experience is very laggy + choppy. When I see other VM's running on unRaid, it seems to be butter smooth and indistinguishable from just a regular PC build. I'm relying solely on my integrated graphics on the Xeon E3-1245 v5 with the P530 integrated graphics for my VM.
My question is, could using an iGPU vs a dedicated GPU be a cause for that big of difference in usage experience? The choppiness I'm talking about just from dragging windows around or scrolling in <5 tabs in Chrome on the VM. I'm not sure if it's this is a GPU issue or an issue with how I set up the VM itself.
[Support] binhex - DelugeVPN
in Docker Containers
Posted · Edited by crazykidguy
clarifying functionality
I noticed that the container was outputting a lot of logs very frequently and most of the logs seem to be for debugging purposes. What could be causing these logs to be written so often? I don't remember seeing this behavior before, at least not this level of frequency.
Quick edit add: the container is working perfectly (WebUI, seeding, VPN, etc), just the log size is significantly bigger than other dockers and a lot of writing to cache.
2022-03-08 14:52:52,702 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2022-03-08 14:52:52,859 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.2.196' 2022-03-08 14:52:52,860 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2022-03-08 14:52:52,872 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2022-03-08 14:52:52,882 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 43701 [debug] Deluge incoming port is 43701 [debug] VPN IP is 10.11.112.4 2022-03-08 14:52:52,882 DEBG 'watchdog-script' stdout output: [debug] Deluge IP is 10.11.112.4 2022-03-08 14:53:22,885 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2022-03-08 14:53:23,037 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.2.196' 2022-03-08 14:53:23,038 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2022-03-08 14:53:23,048 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2022-03-08 14:53:23,061 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 43701 [debug] Deluge incoming port is 43701 [debug] VPN IP is 10.11.112.4 2022-03-08 14:53:23,061 DEBG 'watchdog-script' stdout output: [debug] Deluge IP is 10.11.112.4 2022-03-08 14:53:53,064 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2022-03-08 14:53:58,219 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '172.217.2.196' 2022-03-08 14:53:58,220 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2022-03-08 14:53:58,234 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2022-03-08 14:53:58,249 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 43701 [debug] Deluge incoming port is 43701 [debug] VPN IP is 10.11.112.4 2022-03-08 14:53:58,250 DEBG 'watchdog-script' stdout output: [debug] Deluge IP is 10.11.112.4 2022-03-08 14:54:28,252 DEBG 'watchdog-script' stdout output: [debug] Checking we can resolve name 'www.google.com' to address... 2022-03-08 14:54:28,378 DEBG 'watchdog-script' stdout output: [debug] DNS operational, we can resolve name 'www.google.com' to address '216.58.209.164' 2022-03-08 14:54:28,379 DEBG 'watchdog-script' stdout output: [debug] Waiting for iptables chain policies to be in place... 2022-03-08 14:54:28,390 DEBG 'watchdog-script' stdout output: [debug] iptables chain policies are in place 2022-03-08 14:54:28,405 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 43701 [debug] Deluge incoming port is 43701 [debug] VPN IP is 10.11.112.4 2022-03-08 14:54:28,405 DEBG 'watchdog-script' stdout output: [debug] Deluge IP is 10.11.112.4