Energen

There is an option to enable/disable (specific) dockers from stopping.. so I guess you could just prevent them all from stopping.

What would happen if you edited /boot/config/rsyslog.cfg and changed (mine) server_folder="/mnt/user/appdata" to server_folder="/mnt/disks/(WHATEVER-UD-DRIVE)"

Don't think so..... the floppy driver thing is for a storage driver, i.e. hard drive. The fact that it's installing means something else is the problem.. as far as what that problem is.... can't say.

What are your VM settings? I just installed an XP VM without anything special and it installed fine. No issues. IDE for all controllers.

I don't have this file and it appears that every link to this file on the internet is dead... unless someone here still has this file and can mirror it, you may need to find a new way of installing with something more recent/updated.

Not sure when your problem started but as of right now duckdns.org is down so that probably has something to do with it. My log is filled with the same message. I'd wait for the server to be up and then check. I've never had an issue with the default times.

Don't know if this is a starting point but you'd have to 1) implement your button into the GUI initially for testing, and 2) make it so that it is recreated upon reboot... then you may be able to get some ideas here https://stackoverflow.com/questions/44443164/execute-a-shell-script-from-html

I would start by removing the /series/ folder and only use the /downloads/ folder. Even if you are somehow downloading or moving tv (only) into the series folder it's creating a path of failure and sonarr doesn't care if your files are in /downloads or /downloads/series/, it will find them either way. All of your Syncthing downloads should (and most likely are) going into the same /downloads folder so don't create any extra work by using additional subfolders. If you somehow have your seedbox separating tv shows into a series folder -- stop that. Just making things messy and more complicated. Try that and see if it helps.

While it's entirely possible to have a gaming machine hosted on Unraid --- a few people do -- I personally feel that it's too much trouble to get working good and still will never have the full experience of a dedicated gaming machine. I could be completely wrong. If you plan on gaming then you 100% need a graphics card. If you plan on gaming with modern, intensive games, you 100% need a powerful CPU. A lot of / some of / a few, I don't really know, have gaming rigs using a Threadripper processor.. which means money. You need the performance. Is it possible with a Ryzen 9? Probably. I can't say for sure. If you go ahead with this build .. I'd probably change your configuration to use one of the M2 nvme as a passthrough for the gaming VM since you need fast disk access, or at the least add a SATA SSD drive. Are you planning on using a parity drive? That will be one of the 4TB drives leaving you with 3 for data. For gaming -- 64GB RAM is probably sufficient but I still / always believe more is better so I'd jump up to 128GB, and give 64GB to the VM. SATA expansions cards are cheap if you need one.. nothing major there.

I was having this problem as well............. it SEEMS to be down to the startup order of the docker containers. My startup order is now influxdb -> telegraf -> tautulli -> varken -> grafana Previously varken was somewhere closer to influxdb and was always not-running. Changed the order and haven't had a problem since. * if this is accurate then it's a good tip for a guide to setting this up!

I finally took the time to set this up and it's pretty cool... I saw it when it was first announced but never had time to figure out what to do with it. I will say that I thought I had Plex stats working, and then they weren't.. so did I ever have them working? IDK... so I was thinking to myself "hmm".. and started looking around... on page 24, I think, of this thread I saw to create a varken data source for UUD which I guess I never created... or wasn't saved? Not sure... Someone, really, absolutely, needs to create a new, updated, step by step installation guide for every single aspect of this and get it posted in the first thread... There are way too many steps involved and too many pages to go through to find every little detail of this. Very neat addon but very detailed to install, but not worth scouring 32+ pages of information.. Also, don't know how useful it would be to add or display, but since this is the "ultimate" dashboard, is there a way to integrate stats from / like this:

I don't know if this would be useful to you at all ... Not sure if it would give you the ability to do what you want, or give you a starting point. For actual scripting you may want "wol" tools that are not currently available through the nerdpack plugin but could possibly be added..

That's clean AF, very nice. I don't have power near my closet or I would totally think about redoing it...

So I would suggest to you that https security is rather important for you since you are on a university LAN... ANYONE on the network could intercept your traffic and potentially do whatever they wanted with it.

TeamViewer Been using it for years.

As jonathanm said you can't use an internal network ip (192.168.1.10) as a dns forward ip.. every single person on the internet, in the entire world, could have their own devices on 192.168.1.10 .. so how would it forward to you? Set your router's DHCP settings to have Unraid use a static ip (set the mac address of your Unraid motherboard/network card) to 192.168.10.1 or whatever you want. Then use DuckDNS to forward your domain to your PUBLIC IP address -- which always routes to you. Access to services is directed by your router's open ports and/or reverse proxy...

The USB key will require more than just saving the key file --- you'd have to change the GUID with Limtech and get a new key for the new USB -- I wouldn't change your flash drive unless there was a reason you absolutely needed to... 1) Preclear drives 2) Add them to array (add 2 more slots to drive configuration and add them to those slots) 3) Move data off drives you want to remove... make sure to move data properly so that it doesn't end up on other drives you want to remove. 4) new config and drive locations -- i forget now which order to do this in even though I just did it a couple weeks ago. - make sure your parity drive (if you have one) is the same drive in the same location

Well it sounds like you essentially already know what you need.. I'll provide you with some of my thoughts though. So before even getting into the hardware I would caution you on only expecting to limit yourself to NAS type storage with Unraid. I thought that as well and ultimately ended up spending 2x more money later to buy new hardware that was more capable for what I was doing with Unraid. Do you have a price range in mind for hardware that you were expecting to be at? You may get the best of both worlds through your budget. For a legitimately storage only Unraid, you don't need much CPU power. I was running a dual core G4560 for the longest time, lower power cost efficient. And it actually ran a lot of stuff without any problems .. I just wanted an upgrade for better performance, which led me to what I have now. You also don't need much RAM for storage only.. RAM would come into play with more docker containers and such. Storage ONLY -- 8GB I'd bet is sufficient, but if you were playing with Dockers I'd say 32GB should be the minimum. Your drive configuration would end up like this: - 512GB SSD as cache drive - 1x 16TB as parity drive - 2x 16TB data drives - 3x 10TB data drives 62TB data capacity. I know you said you keep one 16TB as a backup drive but you're wasting it by not using it. I don't know the reliability statistics for the large drives but I'd take a guess at the chance of a failure is somewhat low. You might as well use it. This disk setup would give you one parity drive for a single failed disk at a time, you could use dual parity drives to handle double disk failure if you wanted with the 2x 16TB drives. The fact that you have an empty 16TB drive is going to help you initially as well with data transfer. Setup Unraid with the empty drive and start moving data off of it until you clear another drive, move that drive over, and repeat, until all drives are added to Unraid. As for the case to use -- well, there's literally thousands of cases out there so I can't recommend anything to you off the top of my head. You say you want small so it's your preference as to the style/design of the case that you want. You just already know you need a case that will hold at least 6 full size drives and 1 ssd. If you want to add drives later you need one that can hold 8+. You move further away from "small" cases with these numbers of drives. Do you want a tower case? Are you open to a 2U/3U/4U server chassis? All kinds of options.

What happens when you sign into https://app.plex.tv/desktop ?

To my knowledge a GPU would only be useful if it Plex were transcoding media at the same time... it has nothing to do with the number of streams at any one time. Being able to handle multiple streams would be more connected to CPU power, RAM to some degree, and internet speed.

Really depends on what your script is doing... and what you're trying to accomplish. As far as I know you would not be able to have a script access either docker.. might be possible but it might not be worth the effort.

I'd say that any of those will be fine. They appear to all use CMR which is an important factor. The only one I would knock from that list is the Toshiba. I can't give you any reasons other than my own personal preference. Over the years every time I've looked at reviews of Toshiba drives they always put me off from buying any of them. Seemed to be more bad reviews than good. So now I just don't even consider them.

Why do you want to map Plex to a symlink rather than just to /user/A? What's the purpose for that? That's not a work-around or a temporary solution.. that's how you are "supposed" to have Plex mapped.. Give Plex access to the share or shares that has your media. Correct.

Does your backup directory (/mnt/user/NCloud/Mihle/files/Filer/Backup/NAS Flash Backup/) already exist? If not, it needs to be created before the script runs. I learned this making my Plex script that you cannot move a file to a destination that does not exist. Also, I'm not clear on whether it's actually needed or not, but it's good practice to enclose your backup path in quotes since it has spaces in the path: dir="/mnt/user/NCloud/Mihle/files/Filer/Backup/NAS Flash Backup/" The error message on the mv command indicates that one or both of these are the problem. It's probably also why the rm is failing as well. During the creation of my Plex script I had this rm command mis-formed and had the same errors as you, and the GUI was totally unresponsive due to it.. had to pull the power plug to reset the server since I couldn't restart it any other way... was not a good time! So I'd change your section 1 to this and see if it helps: #dir = WHATEVER FOLDER PATH YOU WANT TO SAVE TO dir="/mnt/user/NCloud/Mihle/files/Filer/Backup/NAS Flash Backup/" mkdir -p "$dir" The mkdir -p just ensures that if the path does not exist that it is created.

You could create a user script to do this and set it to run at the start of the array -- it would take a test or two to see exactly when the script was fired off, the actual start of the array when you push the button or after drives are unlocked, and modify it accordingly to adjust for it if necessary.