jumperalex

That's fair. But for now I'm sticking with Dockers. And FWIW I just bit the bullet and 10.3.55 loaded up and is running. We'll see if something bad happens since I threw a few weird errors like about memory and swap not being enabled [shrug].

Weirdly my plex wasn't seeing or using the GPU despite getting my GPU working in Immich after some driver update shenanigans. To get Immich working I had to uninstall the driver, reboot, reinstall the driver, reboot, stop docker service, restart docker service. That was yesterday. Today I saw your post and chedked, boom Plex wasn't transcoding or even seeing the GPU. A restart of Plex just seemed to magically fix it. Crazy to think you haven't tried that already, but just in case you haven't [shrug]. I'm still on 7.2.4 also though.

Is there any reason not to update to 10.3.55-unraid?

[FACEPALM] I could have swore I checked that! I know I did it for 10.0.162 when I first upgraded to 10.x but I must have lost it in all the churn when I realized I had lost access due to an unintended 10.1.85 upgrade. THANK YOU!!!!!!!!!!!!!!

I ran into the auto-upgrade problem but was able to restore a working 10.0.162 version and took a backup from inside unifi. I also found some older 9.x backups in my snapshots. The problem is I then wiped unifi again, reinstalled 10.1.85 clean, got to the restore page, selected my 10.0.162 backup and ... nothing, white screen it goes no where. I tried with a 9.5 backup, same. I tried using Edge instead of Firefox, same. I waited and stopped/restarted the container, back to the new welcome page. Any advice how to get past selecting the restore file => blank white screen dead end? ETA: I also tried just making it as a fully new instance and restoring from Settings|Backups|Restore as others have suggested. But all I get is a way-too-fast toast notification in the top right that loooook like I see the file name of my backup, but then nothing happens. I'm just sitting at a free install with "managed by others" devices. I even tried shuttig it down and restarting at that point, but no change. I also tried other backup files I have from 10.0.162 and 9.5.21 all the same results.

Updated without fanfare. Which is a little disappointing have to say. I expected balloons at least! :)

Ah well that's fair haha. I "think" compose is actually pretty easy especially one the docker compose add-in is installed. I've been using it for Immich for a bit now with success. "So do it yourself" you say. Well using immich, and knowing how to set it up from scratch were two difference things. As for the other way setting up mongo separate, I think that's the point of using compose. It packages it all in one for management, dependancies, etc etc. Immich actually runs 4 dockers! but it's all managed from a single compose file (okay and an env file). Anyway, like I said above, I'm not poking or demanding. Was just curious about the art of the possible because "yeah sure that is doable" means I wait. "Yeah naw I tried and it failed" means I really look into a VM or using my spare rpi4.

Oh wow sorry, I wasn't specifically asking for support. More just replying to the idea that there's not much else to be done but, "You have 2 options - either migrate to the version on this forum that keeps mongodb as a separate docker container and run 2 dockers for your Unifi deployment or migrate to what Unifi want you to use - Unifi OS Server." I mean it isn't anyone's responsibility to keep supporting the community for free, so I wasn't asking that. Just asking out loud about what's possible and why it might/might not be. and also, I think 11notes has done exactly the docker compose concept here: https://github.com/11notes/docker-unifi-network-application or am I wrong? All of THAT said, thank YOU for taking the time to write all that; really I appreciate it!!!

Sorry if I'm asking a dumb question but couldn't this be an "easy" docker compose to have the OS and mongodb stood up as needed? or is that you mean by, "either migrate to the version on this forum that keeps mongodb as a separate docker container and run 2 dockers for your Unifi deployment" but also, what about this, from you? https://github.com/11notes/docker-unifi-network-application sorry just a bit confused here :-;

All else aside, isn't the correct answer to "I don't want to risk listing my library" is to make a duplicate of your library in a safe place?

That is sad and I understand your reasoning. And nothing I say below should be read as a call to change your current plan. That said, I disagree that LT has made it self tuning. Default settings for even the one main tunable, md_num_stripes, makes a difference for my 7 disk array. Setting it to 5120 improved my parity by 10% from default. Not sure if this is the best speed:memory option, but i also guess I don't need a full script to test out a few options. But for sure default is slower than tweaked. FWIW, I'm getting same speed in 6.8 tweaked as 6.7 tweaked which was the same speed as 6.6 tweaked nr_requests I'm not so sure but I did increase mine from default to 256. This is where maybe a script might help to see if there is an interaction. Though my research of what nr_requests does leads me to believe there probably isn't any covariance. In any case, thank you for all your time and effort. Even if it ends up being the stuff of legend, your contribution to the community really is greatly appreciated. Thank You Pauven!

so is this now dead?

Upgraded from 6.7.2 without difficulty.

okay, I get it now. Sorry for the noise.

Yeah that's where I looked and the only two files that I see are screen.conf and settings.conf settings only has this # # MakeMKV settings file, written by MakeMKV v1.14.5 linux(x64-release) # app_DataDir = "/config/data" app_DestinationDir = "/output" app_DestinationType = "3" app_ExpertMode = "1" app_Java = "" app_UpdateEnable = "0" app_ccextractor = "/usr/bin/ccextractor" sdf_Stop = ""