Leaderboard

Hab das Netzteil, zufällig gekauft weils bei Mindfactory im Preisfehler für 59€ zukaufen gab. 2 Tage später kam der Tweakpc test. Bin froh ein Schnapper gemacht zu haben. Viel sagen kann man dazu nicht, leise und ordentlich verarbeitet.

Karl Dönitz, leading another wave of unraid community U-boats raiding the unraid offices, was able to send us this information, before @SpencerJ sank them again. Damn magnometer 😏😉 @doron, ja ja Herr Kapitän 😏😏👍 "B-G-1-2-4" "plugboard empty" "qgcj vhkw ajju aari czdr zemm buwm anmk ehrj xarq psgl ijdh kybp lnaq mjjh drld avu"

It is working now. Thanks guys

I submitted a PR to the Polish translations. It crashed the entire Main tab.

--- Google translator thanks, that's how it worked

Not really related but thought I would mention these repeated in your syslog: Jul 28 07:23:13 Mongo root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token This is caused by having another browser session from a previous reboot. Best if you try to work with your server from a single browser session just to make there is no confusion and one UI isn't out-of-sync with your actual server state. You might close all of them on all computers and start over with just one new browser session.

I would suggest you try downloading the zip file for the release and then extract all the bz* type files over-writing those on the flash.

Yes Simpy forward to ip.of.your.vm:portofyourapp does not need to be on the same host

Thanks @alturismo. As I said, I am suspecting this is a Plex issue, but because I had the update and the hardware change on the same day, I wanted to rule out an Unraid/ Plugin issue. I tried using TVheadend, and wasn't able to get it working. However I was able to see all 4 tuners in there. I will head over to the Plex forums and see if anyone has an idea there. Thanks.

Ich hatte dann entsprechend mehr "sg*" devices in den Docker gemappt. Nicht schön, aber funktionell

支持!看到了你们的进步,继续加油.

Hab ich grad auch selbst bemerkt, sah irgendwie nicht richtig aus.

Mounted unRAID das Laufwerk oder übergibt man das über /dev/... ? Sonst könnte man es ja unmounten und wieder mounten. Wenn nicht müsste man das Gerät rauswerfen und den richtigen SCSI Host neu scannen (in dem Link hat er "host1" ermittelt): https://www.skytale.net/blog/archives/24-Resetting-SATA-devices-under-Linux.html

I can't believe it, but I fixed my severe Windows 10 VM stuttering issue. I was really hopeful that the MSI fix proposed above (I used MSI_util_v3.exe to enable msi, and set the interrupt priority to "High") was going to work for me, since lspci told me that my gpu+audio passthrough didn't have MSI enabled. Applied the fix, no dice. Then I resumed my two-day Google-fu and read like a thousand and one posts with all sorts of purported arcane fixes. I'm one post removed from sacrificing a virgin and using his blood to consecrate my VM. It turns out that this was my problem (see attached picture). I enabled this to run WSL, and I didn't suspect that it would cause a major issue with lag and stuttering. This was my last hail-mary, and I disabled it, rebooted the VM thinking it wouldn't do anything. VOILA. SLICK BUTTERY GOODNESS. Granted, I can't use WSL in my VM anymore but it wasn't that important compared to having the VM run smoothly. Now I'm streaming 4K videos on youtube on the VM through Parsec and everything works perfectly. Host setup: i7-7820x, Gigabyte X299 Gaming 3, 32GB RAM, Gigabyte AORUS Xtreme 1080ti (Single GPU passthrough), UEFI boot, ixgbe network bridge. VM setup: Windows 10, 4 isolated cores / 8 threads passthrough, GPU+HD Audio passthrough, 16GB RAM, network bridged to host ixgbe interface. tl;dr: Killing "Virtual Machine Platform" under "Windows Features" fixed my extreme stuttering/lagging problem with my Windows 10 VM.

All worked seamless and I am now a happy license holder.... thanks

@c_miceli see one post above, same suggestion from my side therefore

@Dchod about Plex and LiveTV ... its still not really the best option therefore, nevermind now, as its basically working inside Plex may as note, no EPG Data for a channel means no Channel, so may start try to refresh EPG in 1st place if that helps. what do you see when you click on the available channels ? are the "missing" ones may still there but greyed out ? in the end, as soon the tuners are there and working, its basically a plex thing, you will get further by debugging (logs) and ask in plex forums therefore. Best crosscheck is to look if a tv server like tvheadend can see and use the tuners, if so, tuners are fine.

Hey everyone, please go to your Plugins tab and check for updates, we have a small but mighty set of improvements for you: ## 2021.07.27 ### This version resolves: - issues with Local Access urls - issues booting when Internet is down ### This version adds: - more Unraid 6.10 compatibility

This last update has crashed this whole image. Upon fresh install I get server error. I never got this before with the last version.

Hi, I haven't tried this myself, but heard from some it works. Try copying the entire mainnet folder over from Windows and placing it here: /mnt/user/appdata/machinaris/mainnet Do that with the Machinaris container stopped, then restart. I would take a backup of your existing /mnt/user/appdata/machinaris/mainnet folder before you do this though.

Ok... It seems the be getting back together. I stopped the VM manager and update the "Default Windows VirtIO driver ISO (optional)" and now it is starting with the VM's showing up again. Thank God!

可以这样： 1、虚拟机linux或者win系统，并安装相应的百度云客户端。 2、安装unraid的网页浏览器docker，使用网页浏览器版百度云。 3、虚拟机黑群晖使用群晖的百度云插件。 推荐1。

Same error on my 6.9.2 box after the latest container update. Looks like there is already a GitHub issue targeting a fix in Glances 3.2.3 release: https://github.com/nicolargo/glances/issues/1905. Workaround would be to add a version tag to the container config like this:

ijqk kfwt dvya ugcv qmlr

Got it to work! Thanks to Ghost82 and glennv. Here are the steps I used, I will try to keep it simple so everyone can try it out. -Install macinabox just as normal (default settings)-- Test to make sure it bootloops for you -Shutdown the macinabox VM -Connect to Unraid terminal -Mount the opencore image file modprobe nbd max_part=8 qemu-nbd --connect=/dev/nbd0 /mnt/user/isos/BigSur-opencore.img mkdir /mnt/user/isos/temp/ mount /dev/nbd0p1 /mnt/user/isos/temp/ -Edit the config.plist nano /mnt/user/isos/temp/EFI/OC/config.plist -Paste the patch after the PENRYN entry - glennv has a post on page 80 that explains it -Save you file -Dismount the image file umount /mnt/user/isos/temp/ rm -r /mnt/user/isos/temp/ qemu-nbd --disconnect /dev/nbd0 rmmod nbd -Rerun the user script - make sure you change the name in the settings of the script to match your VM name (I also set REMOVETOPOLOGY="yes" , not sure if that is needed) -Test it out! Macinabox PENRYN Patch 11_3.txt

Yes it is needed as /transcode will be created, even it is not mapped through the containers settings. So I will hopefully update my guide for the last time ^^ EDIT: Done.

i have a freeRadius on top of pfSense running as VM...

I'm passing through my serial port fine to a Windows 10 VM, try this xml:- <serial type='dev'> <source path='/dev/ttyS0'/> <target port='0'/> </serial> obviously you need to ensure /dev/ttyS0 is your serial port on the server. It appeared as COM2 for me in Windows.