GroxyPod

I have since moved to a different motherboard, but I'm still using the memory I have IBM rebranded micron RDIMM DDR3 modules that a buddy of mine hooked me up with. I only have 128GB installed now as I've borrowed the rest for other projects. P/N: MT36JSF2G72PZ-1G6E1HG

That's funny because I am using firefox and it worked fine for the first browser. My guess is it might be related to whatever ad blocker being used or similar.

Honestly I wish I could remember what exactly happened. I just re-installed and it's working fine when changing https to http. Checks out across all browsers. The only thing I do differently now is I use a custom IP for my dockers (queue the hissing "but mah security" proponents haha)

The only commands that comes to mind would be: dmidecode and lwsh -class memory Not sure if it will give you what you're looking for, but it might point you in the right direction since you have confirmed you're in quad channel.

Not true. 1 is definitely single. 2 is dual 4 can be dual as well Post your motherboard make and model if you want further help.

Memory channel mode is handled by the motherboard and the ram slot population / position. If you only have 4 DIMMs in total on the board, you don't have quad channel memory. You have dual channel. Quad would require 8 DIMM slots in total.

In your settings, you're trying to get an ssl cert for duckdns.org instead of your own custom dns name. You need to use the custom domain name you have on duckdns.org <eg: minecraft.duckdns.org>. By using a dynamic dns provider, I'm not sure if you can use subdomains at that point, I personally haven't used a dynamic dns provider and just go with a cheap .com instead. Nevermind, misread.

I use NVMe drives as a cache pool, they're great. You need to check your board specs to find out if it supports M.2 SATA or M.2 NVMe (PCIe). If it's just M.2 SATA, then it really is up to you on if you want to use them or not, they won't be any faster than your current SATA SSDs in terms of available bandwidth.

This video might answer a lot of your questions regarding hardware transcoding with an nVidia GPU.

What kind of tape are you using? I personally pop the 3.3v pin completely out (no issues with the drive) but I would not recommend it to other people.

This is not related to the docker container. This is related to plex as Constructor mentioned. terminaladdict is your plex user account. You can't delete that. You can however change your username. https://plex.tv/users/edit Under Plex > Settings > Users & Sharing > You can delete the second home user by highlighting and clicking the X. Once deleted, you can then change your username to what you want.

Well what you're experiencing is when CSS can't load on a website. That's usually caused by an ad or script blocker. Try clearing your browser cache and/or using a different web browser for testing (not your mobile device).

Do you have an ad blocker?

Generally, a blade system shares power / networking / cooling in a single chassis for maximizing space. Some systems come with a central management console to control the blades (think IPMI). You can virtualize but at the end of the day, it's still a form factor and each blade is isolated in terms of computing power per server. The idea of having 4 CPUs on a single system is nice though, especially if you plan to use ESXi or unraid on that server blade for VMs. The only issue is the Dell 1955 can only support Xeon 5300s which are 4c/4t.

Can't speak to how well they would work, but they would be individual servers inside a single housing. You'd need a license for each 'blade'.

Your syslog shows: Apr 2 03:46:24 Stacker kernel: mce: [Hardware Error]: Machine check events logged Apr 2 03:46:24 Stacker kernel: EDAC MC0: 1 CE error on CPU#0Channel#1_DIMM#0 (channel:1 slot:0 page:0x0 offset:0x0 grain:8 syndrome:0x0) Looks like there is an issue with one of the sticks of your memory. If it's ECC memory, you should be fine so long as you're not seeing a large amount of errors appear. You can run memtest86 if you want to test things.

You necro’d an near- 4 month old thread that was literally a different animal at the time of posting the information. Clearly it’s changed and I’m well aware how to update containers. Not sure what you’re trying to gain here by doing so. Sent from my iPhone using Tapatalk Pro

This message was posted over 3 months ago, when the post was accurate. BTW, the plexpass tag was update 2 months ago. The latest tag was updated 4 days ago.

Per their own docker hub at: https://hub.docker.com/r/plexinc/pms-docker they're supposed to have separate tagging: latest, plexpass, and public however they haven't updated the plexpass or public one in over a year. Safe to assume you're on the public (regular) version and not plex pass. To utilize plexpass versions (so long as you're a plex pass holder), you'll likely need to use another docker container like linuxserver where they keep it more up to date.

You'll likely need to have a secondary router setup with VPN connectivity that sits behind your main router for it's internet source.

I use that card in my setup. You need to have a motherboard that supports splitting the PCIe lane into 4x4x4x4 in order to utilize all 4 slots. 2 slots should be fine though I believe.

Dec 10 22:35:04 MediaServer kernel: mce: [Hardware Error]: Machine check events logged Dec 10 22:35:04 MediaServer kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: e600000000020408 Dec 10 22:35:04 MediaServer kernel: mce: [Hardware Error]: TSC 0 ADDR fef13dc0 Dec 10 22:35:04 MediaServer kernel: mce: [Hardware Error]: PROCESSOR 0:506c9 TIME 1576017266 SOCKET 0 APIC 0 microcode 38 Looks like you might need to test your memory with memtest86 (available when booting up unRAID)

It would help if the specs of your setup were included and the actual USB drive manufacturers/models were provided. For all we know, you can be using drives you got off Wish. I've been using unRAID for almost 4 years now, never had a single issue with the flash drive dying and I'm using a SanDIsk Cruzer Fit 16GB flash drive.

You might want to look into user scripts. I think you'd have to use bash, but if you're looking to do a re-occurring script, it might be a better solution.

As testdasi said, it is likely a bad DIMM. I just had to deal with this myself and it isn't fun. Best thing to do would to run memtest86 with all memory installed until you start seeing memory errors. Once you see these errors, take a picture / write down where they occur (eg: test 2, test 3, etc..) and how many. That way you only have to run up to those tests and not have to go through the entire testing to find the bad stick. Once you've found out which test you seem to have failures at, remove all but the minimum amount of memory required by your system and then run the test past the test # you were previously getting errors at. Then you just swap one stick in at a time, retest up to the test # after and repeat until you find the bad stick. After you've eliminated the last stick, run through the full memory test gambit to ensure everything checks out.