Ross

Got it. I was thinking that a dual parity drive setup would allow the system to figure out which drive was the “odd man out”, and therefore the one drive needing to be corrected. But that would not be true if the parity process had an issue and wrote the wrong parity to both parity drives. I think I’m going to look at that file checksum program to see if that is the way to go. What is the theoretical cause of a stable array (for years) developing over 500,000 parity errors in one week? Ross

Thanks for the quick reply. But is that assumption, that the data drives are always good, valid? Why do we believe the data drives are always valid and only the parity drive can be wrong? Maybe the app that creates file checksums is the way to go… It’s a little disconcerting to see over 500,000 errors need correction on a system that aside from auto updates of the software is just being read. And the drives are old enough that failure is definitely getting to be more likely soon. I’m not sure how I can validate that I do not have file corruption… Thanks again for any information or suggestions. Ross

So after rebooting the array I ran a correcting parity check and it corrected thousands of errors. I have since run two non- correcting parity checks and they finished without errors. None of the drives have any SMART errors reported. After years of no parity errors, I’m contemplating about this situation. The array is mostly a media file server and some backup storage, so not a lot of write activity. So when parity is “corrected”, I’m not sure I understand how it determines truth. If there were drive errors, then I could see how I might figure out which drive was the source of error. I’m assuming that either a data drive or the parity drive could develop an issue. So even in my small array I was thinking now that having a second parity drive might help figure out which drive has the “bad” data needing to be corrected. I also saw discussions about an app that calculates a checksum that allows detection of file degradation aside from disk failure. So my server seems fine now but I’m not sure I did not lose something… Is a second parity drive a good idea? Thanks for any guidance! Ross

I can do that, but I have figured out that there were two correcting parity checks run, and both reported a lot of errors (first time was a week ago), and the server was not rebooted between those two runs. The latest non-correcting one I ran for a few minutes and aborted and it logged over 3k errors. I realize now that my scheduled checks should not have correcting on, but they did.n. So have have had repeat of this error. So I can run two more back to back, will take over a day, but I am wondering if the above information confirms the issue?. I suppose now that I have run two correcting ones already, that if I corrupted my data, it is probably already too late? That's why my next addition will be a secondary parity drive... Thanks again for any help! Ross

I manually started a parity check and immediately got errors: Feb 3 11:31:59 WServer1 kernel: md: recovery thread: check P ... Feb 3 11:32:00 WServer1 kernel: md: recovery thread: P incorrect, sector=2488 Feb 3 11:32:00 WServer1 kernel: md: recovery thread: P incorrect, sector=12720 Feb 3 11:32:00 WServer1 kernel: md: recovery thread: P incorrect, sector=14768 Feb 3 11:32:00 WServer1 kernel: md: recovery thread: P incorrect, sector=15792 Feb 3 11:32:00 WServer1 kernel: md: recovery thread: P incorrect, sector=16824 Feb 3 11:32:00 WServer1 kernel: md: recovery thread: P incorrect, sector=10680 Feb 3 11:32:00 WServer1 kernel: md: recovery thread: P incorrect, sector=24656 Feb 3 11:32:00 WServer1 kernel: md: recovery thread: P incorrect, sector=30192 Feb 3 11:32:00 WServer1 kernel: md: recovery thread: P incorrect, sector=39408 Feb 3 11:32:00 WServer1 kernel: md: recovery thread: P incorrect, sector=47264

I have been running Unraid for years without any issue, but the day has finally arrived. A scheduled parity check finished but reported: Last check completed on Wed 02 Feb 2022 03:30:45 PM CST (yesterday) Finding 511132 errors Duration: 14 hours, 30 minutes, 44 seconds. Average speed: 153.2 MB/sec I have three 8TB WD Red drives, and a small SSD cache drive. There are no SMART errors reported and all disks report as "Healthy". Parity was reported as Valid. When the errors were emailed to me I did shutdown the server, because I did not know when I would have time to get to it. I guess that was a mistake since it emptied the log files... So I think I need to run another parity check, without correction, and see what I get? I also think I may want to get a second parity drive after correcting this problem, because I realize how important it might be to identify which disk is having issues... I thought having parity check report errors would be a common problem and that there would be a guide setup for my scenario, but under the troubleshooting areas, I did not yet find a guide for my situation. Is there one out there? Thanks in advance for any help! Ross

Current Nvidia setup help needed. I had my Nvidia card working with the special build of Unraid, but I see that Unraid now supports the Nvidia driver directly. I deleted the unsupported Nvidia setup, upgraded to the latest Unraid, and loaded the new Nvidia driver. I restarted everything. I looked and the setup for the new driver looked very similar to the old one. But currently I do not have hw encoding working, so something is amiss. I did see a suggestion to setup an environmental variable, but no photo of where that goes. Is there a special field for environmental variables or does the -e specify it? When the Nvidia setup changed, I wondered if this version of Plex Server is still being supported, but it looks like it is, and it was working well for me. Can I get this to work with the new Nvidia driver setup in Unraid? Thanks, Ross

But that’s not in the 4 steps (with two numbered as step 3) listed if you are using the linuxserver.io container. That’s part of the reason I posted this, is that step missing. ———————- from top of forum ” With new installs of any of these containers from LinuxServer.io we have simplified the process of getting this working.  1. Add the desired Application from CA. 2. Switch the template to advanced mode 3. Copy the GPU UUID to the existing NVIDIA_VISIBLE_DEVICES parameter 3. Start the container.” ———— I checked above that and it only discusses installing the Nvidia plugin. Is there a step missing? thanks Ross

I checked the Plex checkbox I added the GPU I’d from the nvidia plugin to the field in the plex docker setup. I initially also added the runtime ref in the extra spot, but reading the latest directions, because I am using the linuxserver.io Plex docker, it sounded like all I had to do was put in the GPU info in the one spot and restart. Do I need to do the other items even though I am using the linuxserver.io Plex docker? thanks for any suggestions Ross

I tried to get an Nvidia P2000 installed and working today, but came up short. I switched to the linuxserver.io Plex app. I installed the P2000, installed the Nvidia plugin and the card was found and installed. I watched one of the youtube tutorials, and maybe that introduced a problem. I initially added the --runtime... line in the extra parameters, but reading this forum later, it looks like if I am using the Linuxserver.io Plex app, that was not necessary, so I deleted that line later. It took me a few unfortunate hours trying to figure out how to get the command window to work, turns out I think it is a Safari bug as it works find under Firefox, ... In that process I tried to redo security, etc, thinking it was some other issue. Complete waste of time. So after moving to FireFox, I thought I was all set. But no matter what I do, when I watch nvidia-smi, no process is running on the GPU card. Most everything I tried to play was direct stream, but downgraded the video quality on one of my players and it is transcoding, just not using the P2000. I am hoping when I finally figure it out that it will use the GPU for transcoding movies syncing to my iPad. So I am giving up for today. I have gone through the setup steps a few times, no good.

Thanks, I saw that the linuxserver.io version had GPU capabilities, so I went with that one for now. Not sure if that feature is too new to be stable enough for me... The last good summary of the Plex options seemed to be from years ago, so I appreciate your input. Ross

I had an issue with my Unraid server and in the process of evaluating I tried to update my Plex docker. The update screen stopped changing, and so the next morning I just hit refresh and the docker was gone. I decided to re-add, selected the default template (rather than user, thinking maybe better to take defaults). Now my media is not mapped. I think I can address all of that. My question for the the general area is, now that I am redoing my Plex setup, what are the current recommendations? It looks like there is a limetech version, and a LinuxServer.io version of a Plex docker? I cant find a good summary of the reasons to pick one over the other for Unraid use. There is obviously some confusion among those using the different versions, as I see posts in the wrong forums because people assume Plex is Plex. Funny thing is, I’m not even sure now what Plex version/source I uninstalled. Any current recommendations on what Plex source / version to use with the latest Unraid version? Does standard stable Unraid support Nvidia GPU passthrough for Plex transcoding (if not, will it soon)? Thanks! Ross

I have reset the memory, swapped slots, and it appear stable for now. I am surprised that if there was an ECC memory error that there was no notification system for that, either on the dashboard or email. Maybe not enough of us use server ECC memory to be worth the trouble. Does anyone know of a way to add a monitor for ECC memory errors? Thanks for your help! Ross

So does that imply bad memory? I have 16GB installed, which sounds like it should be ok, although I have thought of going to 32. I could shutdown and reseat current memory to see if that changes anything...

True, but what’s odd is that I’ve run parity checks weekly for the last year and they take 15 hours, speed 146 MB/sec This one currently reports: Elapsed time: 2 days, 23 hours, 20 minutes Current position: 1.47 TB (18.3 %) Estimated speed: 6.1 MB/sec Estimated finish: 12 days, 8 hours, 39 minutes Sync errors corrected: 0 Why would the speed be so low? Server not being used for much else. Thanks for any advice. Ross

Diagnostics attached. I was hoping to fix anything with Unraid and then move on to Plex. Storage and Plex are the primary uses of this server. The current issue started last week, Plex interface looked fine, but when I tried to play anything or use Live Tv DVR, the hour glass would not stop. As if there was a transcoding issue. Was working fine for the last year or so. Diagnostics attached. Thanks for any help. wserver1-diagnostics-20190727-0257.zip

I have had an Unraid system up for a while now, predominantly file storage and Plex (which is having issues I will post in another thread). Xeon E3 1245v3 16GB ram, 8TB x 3 disk (16TB and parity) and a 240GB SSD cache drive Unraid 7.6.2 - recently updated - not sure if that was the start of my issues I decided to just relook at my whole system. So with the Plex docker not running, my CPU is varying from 30-60% over all load. That seems high to me for a server that is just sitting there... Is that normal? The dashboard comes up and looks ok. But when I go to Plugins, the page loads but the "spring" just keeps moving and it never returns. I had some of the usual applications installed, and was going to list them for this thread, but ... Any ideas where to go from here? Thanks, Ross