rhinoman

Found the instructions https://github.com/binhex/documentation/blob/master/docker/faq/plex.md Working now

Well after researching I have added a Nvidia GTX1660Ti for its hardware decoding ability and have ticked the boxes in transcoding for Plex but GPU Stats shows zero decoding and the CPU is still at 100%. Anybody have this working? Any tips?

I'm not sure if this is the right place to ask but I've used this container on my Unraid for many years with very few issues. My server is based on a Intel® Xeon® CPU E3-1275 v3 @ 3.50GHz with 32Gb ECC ram. Yesterday when streaming a movie to a Firestick the server started warning beeps because it was thrashing all the cores of the CPU, film was a large 4K and HD audio being decoded to a TV at 1080p so I'm sure it was working fairly hard. Is there any settings I can check or change? Is there a simple hardware upgrade that may help, maybe a graphics card? Apologies for my ignorance but its just worked so haven't felt the need to keep up with advancements.

appdata and system got a bit missed up with the recent crash and am gradually working through that stuff. Yes I do have ophaned containers.

Thanks for your continued help. sun-diagnostics-20201025-1529.zip

Yes your right, i think I missed that folder but have re-setup the existing dockers as shown and they were initially working pointing at there original appdata, its just when I try and update they go missing?

I swapped to a new one, got the key replaced, copied some of the files and setup what was missing. Its the dockers that seem odd, initially re-installed just fine but went I try to update them they stall and go missing.

Had a bios battery failure the other week and subsequent corrupted flash drive. Seem to have most things back where they should be but the dockers wont update and the VM's are not working as they should. I suspect the appdata folder has the wrong write permissions or something like that...can you advise who to check and correct please?

If I boot to no plugins - gui mode, I still can access the web interface and the root login doesn't work on the gui.

So i have progress, battery replaced, updated bios to newest, reset defaults and then adjusted to suit. I now have a machine that boots to a clean UNRAID OS running 6.8.3 as my system was before the newest issues. If I try and boot from my configured flash the system now boots and gets to the login screen but wont let me logon with root - root. The web browser also doesn't load although the PC name and IP address are shown as expected. I can also ping the machine. Next steps please preferably without having to start the whole config again

Will do thanks.

Cant get as far as the unraid boot menu

Thanks for the replies chaps, didn't get a notification. Yes this system has worked for years and is as per my signature using the Supermicro board. No new hardware in the previous few weeks and no new changes beyond some Docker updates. Yes it suddenly stopped working. I think we recently had a power outage. Its more than possible the cmos battery is low/flat as its a few years old now.

Not sure if this is an Unraid problem or hardware, i suspect the latter but if any body could shed any light on the possible issue I'd appreciate it. My server gets stuck booting and displays efi shell version 2.31 (4.655) current running mode 1.1.2 map: cannot find required map name.

Was wondering the same?

Would love this feature, cant believe it's not done already. What hardware workarounds could I use for an SSD or NVMe mirror raid?

Wounds like a plan, thanks.

Cheers for looking. sun-diagnostics-20181116-0013.zip

Fix common problems has just notified me of "unable to write to cache". It's not full by the way.

Since upgradeing to 6.5.4 last week my machine has become unstable, first thing noticed was that dockers become unavailable, then the web interface. Hard reset then started a parity check and it froze the web interface again but could get to the shares via another machine so updated to 6.5.5. This time parity completed but soon after the dockers become unresponsive again. I've rebooted and the dockers remain unavailable with "docker service was unable to start" and when I try to start a VM i get I'm guessing some folder permissions have got messed up somewhere and causing both issues?

Still had a crash after using RC6.4.1, around the time the parity check completed I think. I'd left a monitor attached and it was frozen with text across the screen. Just rolled back to 6.3.5 and amended my Unifi docker back to bridge mode instead of a dedicated Ip which was the only other change, so I've just stated a parity check again and see how it goes.

Good man, You may be right i think, processor is a Haswell... Xeon(R) CPU E3-1275 v3 @ 3.50GHz

My current system was built around 4/5 years ago, normally running a few dockers, a few plugins, a couple of lightweight VMs. Only hardware changes over the last few years is bigger drives. It usually stays up for months on end. Just before Xmas I started a few drive upgrades, removing some older small ones that were beginning to show errors and create a little more space. All was well untill the recent upgrade to 6.4.0. Upgrade went fine but I had following issues with a pre-clear via the plugin so removed the plugin which I understand seems to be a known issue. Following this I have been getting system hangs. Can't ping the server resulting in a hard power done. Reboot, let parity complete and then soon after another freeze. This happened a couple of times. I downloaded the diagnostics plugin and that showed the only real issue being a couple of SSD's in my array (but they have been there for a couple of years) and Call Traces (whatever that is?) I then removed most plugins except CA type stuff, backup but it completed the parity check and then hung again. I rebooted and successfully run a pass+ of memtest (its ECC ram on the approved list for the M/B) I've now rebooted into safe mode and its running parity again, the last three successive parity checks showed no errors. My diagnostics is attached fi somebody could offer some advice please. unraid-diagnostics-20180130-2132.zip