sjaak

thnx for replay.

is it an idea to put the patch back in unRAID? and to use it, you need to type in commando in the "syslinux.cfg" file? i would love to test it... my win10 vm can't update to any driver higher then 17.3.x (latest driver that asus profited at there website for the vega64 strix) every driver after 17.x result in a black screen. but on the other side, with v17 a can reboot the vm without any problems. my linux VM still suffers from this "bug"

i know. but disabled cache use on the share, that also works (i disabled netbios, so no v1 here) i prefer to lose some write speed instead of security...

you can change which device is eth0, scroll down on your network settings to "interface rule", change the mac address for interface eth0 to the pcie card.

yeah, and at this time of writing this message, the server is 23hours "stable" without suspicious notifications in the logs, however almost 18hours are Parity sync (its slower on 6.8) Dockers and VM are on.

its the first time this "half freeze" problem happens. (beside the freezes i had with Ryzen) i running 6.8 now +/- 2 weeks, i don't have a high uptime because the annoying AMD reset bug (vega64).

i not sure if this is to right spot to place this, but there did something goes wrong on my server running 6.8. (there are NO diagnostics!!) this morning i had a "half" freezed system. i tried to login on my VM (its always on) after put password in and pressed 'enter' its stops working, only the mouse was working, no keyboard command was accepted. i tried to gain access thought the GUI boot, but firefox freezed while loading the webgui. then i tried to open terminal but i cant type anything there. so, booted my notebook to gains access through ssh, did successful login to it en tried to force a reboot, got the message that says system is going to do a reboot. waited.... well reboot not started, it did nothing. opened en new ssh terminal to get "diagnostic", waited about 30mins and no diagnostics... so there was nothing else then a dirty reboot (i really don't like that) it rebooted and its now doing a paritysync, no strains thing going on... but, now i didn't got any diagnostics, so i setup a remote syslog server, but when i config the syslog service on unraid and saved it i had to restart rsyslog by my self, Unraid didn't restart it after i changed something in the GUI. why doesn't unraid restart it after some gui change?? "sudo /etc/rc.d/rc.rsyslogd restart" did the trick. now i'm going to monitor the system logs remotely, hopefully this was a onetime thing.... edit: Thnx to Domoticz (its running on unRAID) i found out that around 0:15h AM there where no activity recorded from my energy meter (youless LS120), around 9:55h AM it started working again (the moment i did a dirty reboot) no i know why Plex didn't do it scheduling programs... so Docker was "dead", and VM manager was almost dead...

just make a full backup of your unraid usb drive before upgrade. i see in the screenshot that you are using Unraid server basic, so there is a key? you can check this here: tools -> registration

there are a lot of Unraid servers exposed to the www, shodan shows a lot of them, they are mostly secured with password (the default login page) i totally don't understand why people are expose the gui config to the www go use a VPN... if i found an unprotected server i turn them off. is it legal? not sure, i'm not hacking them, there is no login required, so....

VRAM is used for the transcode but the finished transcode data will be temporary stored in RAM. (one 2.5hour 4k stream can eat 12G of RAM, it looks like Plex doesn't remove old transcode data unless the stream ended...)

here it still transcode to RAM, no problems or whatsoever... if it not eating all its RAM its fine... You can limit the amount of ram use with a script. (so Plex won't use all the ram that result in a server crash) #!/bin/bash mkdir /tmp/PlexRam mount -t tmpfs -o size=18g tmpfs /tmp/PlexRam set it with the User scripts, scheduler "at first array start only" and you fine ('size=Xg' is max allowed ram use)

"vers=v1.0" in the mount command (on Linux, i don't know how it handled in windows)

i just switched my ubuntuVM from nfs to smb and i got this problem too, the windows vm are still fine. however, steam can still see and use the share, i just cant browser it anymore. umount and mount will "fix" it for some time... now i changed the share to data array only and its fine... really hope this will be fixed in a later unraid version...

with "nvidia-smi dmon -s u" you can see more details what the gpu is doing (decode/encode)

there are many thing what i like with Unraid, but at highest like, i am going to say; The Community (the Plugin/Docker/VM developers and Tutorial creators!) what i like to say in 2020; more stuff in the Unraid GUI boot, like a (easy) File Browser, more monitor stuff. an another thing; Multi-pool support (for the Cachepool and Datapool)

i had some troubles with GPU passthough with Q35, switched it to I440FX and it worked with Win10 and my Linux based VM's. and i did use the Graphics ROM BIOS option. (hardware i'm using: Threadripper and AMD Vega64)

what your network settings?

why are you exposing 2 ports? bold for Nextcloud??? whut?? and why port 80 and 443? Unraid itself is using them by default...? (to using https (443), there are some extra steps to taken.) (my nextcloud install is out-of-the-box using 1 port? inside docker its 443, outside docker you can put your own port, and in your router you can also using an another port for outside connection) why did you open port 22? control Unraid outside your local network? why? by reading this topic i pretty sure you don't know what your doing, or using ssh, so get rid of those port forwards... if you want to control Unraid outside your network, go start using VPN (its also using 1 port...) much safer... you did ask in this topic if it better to reinstall Unraid, do you still trust your server? did they managed to get access to your server? are there some strange activities ongoing? Malware? spyware? Bitcoin miner? botnet? No Trust? -> get rid off everything and reinstall/format it... looking on the brightside (well... its not good...), your are not the onlyone who exposed there server to the WWW, Shodan (its a search machine for exposed services) is showing a lot! (funfact; i can't find my server, and i do have some open ports.)

me too, one of the 2 is running "OK" for about 2 years now, so i "trust" them another month before replace...

i have 2 of them, it works but i can confirm they can be dropping hdd's offline. 2 weeks ago i lost 1 hdd (its not dead, just corrupt) and the 3 other connected hdd's did have 1k+ errors on the Unraid main page... i going to replace them with a LSI 9201-16i... (parity and cache devices are connected to MB directly)

currently 41TB + 1.6TB cache. soon it will be 45TB, waiting on a sas => sata cable... probably it will run out off space in between 6 months... the pic missing the 3rd GPU (GTX1050ti), didn't make pictures at the installation of it... yeah, cable management can be much better, will improve it do soon... (probably not 😇 )

just type "linuxserver" in the community application and every lsio docker is there? LSIO = linuxserver.io

i don't know, i use al lot of the lsio dockers, mostly because of the easy understandable documentation

this plugin (unraid nvidia) and the LSIO plex docker, nothing more.