civic95man

That's what I do. Granted, I just use mine headless - I still have the monitor attached to the igpu for diagnostics and to mess with the BIOS. I don't even boot up into the GUI mode - all of my admin work is done on another computer (or even my phone in a pinch). Most of the time I have win10 running within the VM and output going to the monitor with it's dedicated mouse/keyboard. I'm assuming you're running the beta version - 6.9? with that new of hardware, I'm sure you must be. Funny enough, i don't remember if there is an option to make the VM autostart on boot, otherwise you will need a way to start the VM - but your ipad will work. I personally don't have anything on mine set to autostart - simply because if the server restarted, it wasn't because of me and I want to track down what caused it before potentially making things worse. It's always better to ask questions when in doubt rather than [potentially] making reckless mistakes, such as when it comes to your data

Probably unrelated to your issues, but why are you using the nvidia build of unraid when you have your gpu isolated and passed through to a VM? It seems like that is your only gpu

I don't know if you've even setup your server yet, let alone booted unraid yet. I would suggest looking up spaceinvaderOne's videos. He has videos on just about everything which are extremely helpful. You would probably want to start with getting the nvidia build (through CA). Then you would want to isolate the 2080ti card that you want the VM to use (again, look up his videos) - this just tells unraid not to use this card/ ignore it. Then, when you setup the VM (again, watch the video) you are given the option to use the 2080ti card. Now for general unraid use, with the nvidia build, you will be able to manage unraid via the 1650 card (assuming you are booting into the gui mode) and still use it for transcoding. This will give you an option to manage the system if you don't have another computer available. In my situation, i have a monitor with two inputs - one from my win10 VM and another from the igpu that unraid uses. So I can manage unraid with one input and interact with windows on the other input. I also pass through several USB ports to the vm and attach the keyboard and mouse to those for win10 use. I run my unraid "headless" in a sense where I don't really use the monitor and have no keyboard for unraid use. Hope this gives you a little information to get started. Good luck!

I was referring to using everything (plex, sonarr, radarr, etc) within docker so that your system (unraid) can better utilize the resources. I'm assuming you are referring to bypassing the 2 transcode limits, yeah, you are on your own, or get the p2000 card to handle unlimited transcodes. It really depends on what you are trying to transcode and how many simultaneous streams you expect to encounter. If you don't anticipate any 4k stuff then gpu/cpu would be fine (2 via gpu, the rest with cpu). you can but gpu is always better than cpu (unless you REALLY care about quality, but thats another debate) no problem, we were all there at one point.

1650 only supports 2 transcodes, thats the only issue. and you would need to use the nVidia build of unraid (many of us do that). with a VM, you are setting aside X cpu cores and Y memory for that virtual computer; whereas with docker, you share the system's cpu and memory between unraid and the different containers (plex, sonarr, etc). so those processes can use as much or less as needed without wasting memory and resources.

# 1 is the easy one. For #2, why not run these natively in unraid with docker? That way you aren't tying up resources for that VM.

While it could be a serious hacking attempt, you mentioned you have netgear router, which is probably performing vulnerability scans as previously mentioned. Check the router's admin page and see if you can disable "armor". That should disable that "feature" of the router, if you don't want it.

You would probably need to 'copy' the source file to the destination using the --preserve=all option followed by deleting the source file (move [mv] doesn't allow to preserve timestamps). i.e. cp --preserve=all [source] [destination] rm [source] I'm not big on making scripts so perhaps someone else can help with that, or you can attempt it yourself. Might want to not remove anything until you are sure it works, or create a dummy directory and files to test on.

Plex itself could be consuming only 300MB of memory; however, if it needs to create any temporary files while doing it's work, it might be doing that in your /tmp. That resides only in RAM and is counted separately from what plex reports.

Sorry I couldn't give you better news. You could try to disable VMs and see if it helps some. At least memory is cheap now!

You only have 4 GB of memory, have you considered adding more? 4 GB is okay if you want to *just* run unraid but if you start doing more (dockers, vm, etc) you should consider adding more memory. You could try killing xserver to shutdown the GUI but it would probably be best to reboot into non gui to save resources. Also, you could try disabling anything you aren't using, such as VMs and Docker (I don't know if you are using any dockers, don't see any reference to anything in the diagnostics) - such that they no longer appear in the top menu bar. Good luck

You seem to have a lot going on inside your server... Several plex transcoded streams, boinc, jitsi meet, VM, etc. I don't know much about jitsi meet, but it seems to be node/java based and *could* be a resource hog. If plex is transcoding to /tmp, that will take up memory as well. Boinc is also using a good amount of memory. Have you considered adjusting the resource utilization within boinc to use less memory? Those are my thoughts, don't know if it will be helpful to you

Could Plex be doing housekeeping jobs during the night (scanning media, creating thumbnails, etc) and eating up all of your memory?

Need your diagnostics to troubleshoot further. At the command prompt, type 'diagnostics' and wait for it to finish. When done, power down unraid and plug your USB drive into another computer and submit the entire diagnostic zip file. That will tell us how to proceed.

yikes!! You want that firewall in front of unraid or you are opening yourself up to some serious issues

I'm just quoting what is in the facts... and any system will run fine on an overclock until it doesn't. If your'e trying to troubleshoot an unstable system, its always best to remove any overclock and go from there. runs fine where? windows? or unraid? That linked faq for unraid has this table to identify the supported memory speeds based on configurations

looks like you are overclocking your memory above what is supported for that combination of processor, memory, and board (XMP is considered an overclock). You are running at 3266 and max supported is 2667. Try adjusting your memory speeds to that and see if your'e stability improves.

Coming from my experience, don't do it. I tried this when I first starting with unraid. While it worked and I never had any serious issues, it was a huge pain and it significantly limits what you can do. It would be best to just find a small used or refurbished computer.

I believe you have a second gen Ryzen, but then again AMD's naming convention confuses me. Set the memory speed to 1866 in the bios and try running a few cycles of memtest with all of your RAM installed and see how that goes. If it passes then that was probably the cause of all of your issues. Since you already have it, might as well stick with it and see if the above fixes your problems. My last AMD system was an Athlon 64x2 as well. And I would never have known about the Ryzen memory speed issues if it weren't for this forum. I suspect windows just handles these problems better when the memory is overclocked. either that or people just figure windows is being windows when it crashes.

No prob. and that is the advertised speed that the memory itself can operate at - but it is dependent on if the CPU and motherboard support that speed as well. In the case of Ryzen, there are a lot of factors that come into play.

Just looking through your diagnostics says everything about your configuration, which is nice to spot things like this. Looking at system\meminfo.txt in the diagnostics, it lists details about your memory. Two of the sticks say this: Speed: 2133 MT/s Manufacturer: Unknown Serial Number: E0F78509 Asset Tag: Not Specified Part Number: BLS16G4D32AESB.M16FE Rank: 2 While two other say this: Speed: 2133 MT/s Manufacturer: Unknown Serial Number: 00000000 Asset Tag: Not Specified Part Number: F4-3200C16-8GVKB Rank: 1 Then referring to this for the proper speed

looks like you're mixing single rank with dual between those two types of sticks. Don't know if that is considered a big no-no. But since you're running dual rank in [some] configuration with 4 sticks, try lowering the RAM speed to 1866, since 2133 might be considered an overclock.

I am by no means a network guru, but I *think* you have the subnet mask wrong. Anyway, I had a netgear router that i could never get it to route across two networks. I eventually gave up with that trash and switched to unifi. Best move I ever made!

I had to do this a few weeks back when my logs filled up and didn't want to reboot. If I remember right, I think I was able to delete the current syslog as well. Why? In my case, not entirely sure but it was related to the webgui server and some issues with it - probably because I left a browser window open on a computer for too long. I also had to nuke the web server and restart it. In hind sight, I probably should have just moved the logs off onto the array in case I needed to troubleshoot something. Anyway, I find this to be a good tip in case you don't want to or can't reboot. ymmv

@isrdude Maybe try updating the BIOS, you seem to be a few versions behind. Also try disabling "fast boot" or "quick boot" from the BIOS and see if that helps at all, if its enabled.