dchamb

You need to go into your motherboard BIOS. I just selected "Load optimal settings " and hit save and restart. That reset any CPU or memory overclocking.

I know I had some stability issues with mine, but I discovered the motherboard settings had overclocking turned on. I turned it off and it has been solid as a rock!

Did this start happening after updating to 7.0.0?

I am glad I have all my REISERFS drives converted to XFS just before the holidays. One less thing to worry about.

So just adding that to the container is all that is needed? I have PlexPass. I thought there was a setting in the configuration.

OK great! I will give this a try. I have a lifetime Plex Pass so that should work.

I'm sorry. I know this question or a variant has been asked, but it isn't clear to sift through all the various answers without knowing what would apply in my situation. I have an Unraid server running 6.12.13 on a 12th Gen Intel® Core™ i7-12700K. I am not overclocking. I am running the Linux server/plex with an extensive library, mostly Bluray, a growing number of 4KUHD, and several DVD titles. I have been contemplating using hardware transcoding but trying to decide: Don't worry about transcoding Use the Intel GPU transcoding. Acquire a NVIDIA card and use its GPUs for transcoding What would be your recommendation if it was your Unraid system or if you have done it? If I go down the NVIDIA route, I am unsure how much NVIDIA power I should consider. Thanks in advance, Dale

I booted the new server to get the MAC address and then shut it down. I then went to the router, changed the address reservation table entry for the IP address used by the old server, and changed the MAC address to match the new server's MAC address. I took the old server out of the network and booted the new server, and it received the same IP address as the old one. It would have been easier if I could have found a sticker showing the MAC address of the NIC card I was using.

Running memtest did identify a problem. Thanks for the suggestion for both my posts about issues I was having. I think the BIOS version of my motherboard was the root problem, particularly since the memory was being overclocked.

Well, I didn't think I was overclocking, but I also didn't build this system. Microcenter built it and apparently set the BIOS XMP1 mode for RAM. I ran a Memtest and it failed on test #7 on the first pass. I shut it down, changed the RAM setting to "Let BIOS decide" and the speed dropped down to 4700 Mhz. Then, I ran Memtest again. Let it go for three passes and no failure. I've read several posts on other forums that the Asus Prime Z690-P had issues with XMP. Brought up Unraid and although it detected an abnormal shutdown, parity was showing okay. I decided to run parity check to be certain. It is halfway through with no errors reported. After a little further digging, I discovered that my BIOS firmware is the original version, and there have been 25 updates most of them related to RAM compatibility and stability. My next move is to update the BIOS after the parity check is finished. I think my RAM is okay, but I will avoid overclocking. I haven't turned on GPU transcoding for Plex yet. I have no NVIDIA card in the chassis so I hope it won't be an issue.

I am running Unraid 6.12.13 on an ASUS PRIME Z690-P motherboard with a 12th Gen Intel® Core™ i7-12700K @ 4653 MHz. It has become increasingly unreliable with parity errors, and just now, none of the dockers (Plex, iPerf) would not run or shut down. I could not get Diagnostics to run or even shut down the array. Shutdown and restart were unresponsive. However, the WebGUI was still accessible. I was able to download the system log. Several CPU cores were showing pegged out at 100% with an overall load of 51%. I hope someone can pinpoint the problems I am having. This has been very frustrating. Thank you Dale syslog-192.168.1.99.log Tower_Dashboard.pdf

When my Unraid system used reiserfs as the array file system I almost never got a parity error correction. Now since I have converted everything to xfs I notice one or two hundred errors being corrected each month when the scheduled parity check runs. Why is that?

Thank you. That gives me some peace of mind. I set the levels to 60 and 70 since the specs say operating temps are from 0 to 70C

I am using a Samsung 990 4TB NVMe M.2 drive as a cache drive on my Asus Dark Hero VIII motherboard. When I transfer a hundred gigabytes or more of data to the cache, the drive is overheating to the point of about 57C. It has a heat sink installed but it's not doing the job. Any suggestions on how to solve this? Thanks!

If I use rsync to copy folders from an array share to a mounted unassigned drive, then delete those folders from the array share, then use rcopy to copy those folders back to the array, will parity be intact? In other words is parity maintained even when rsync is used?