Ross

My question is, should you uninstall the docker after a successful run and then reinstall if you need it again? Or just turn autostart off unless you think you need it? Ross

I changed the one line to my plex location, library folder was there. It is started and running, does it stop automatically? How long should I let it run? And where do I find the log file? The post making it clear that you only have to update one line was very helpful. That maybe should have been obvious, but it was not to me. A youtube video would be great, even though it is simple. Thanks for doing this! Ross

I figured out how to load an older drive, which I did and now I am back up. Ross

My Nvidia drive updated tonight and now is not working. The NVIDIA Quadro P2000 GPU installed in this system is May 4 20:15:26 wserver1 kernel: NVRM: supported through the NVIDIA 580.xx Legacy drivers. Please May 4 20:15:26 wserver1 kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more May 4 20:15:26 wserver1 kernel: NVRM: information. The 595.71.05 NVIDIA driver will ignore May 4 20:15:26 wserver1 kernel: NVRM: this GPU. Continuing probe... May 4 20:15:26 wserver1 kernel: NVRM: No NVIDIA GPU found. Is there a path to downgrade to the last working driver? Thanks for any help. (I need to rebuild this ancient system, but it was running fine)

It worked but I needed to re-add my plex docker. I am not sure if that is expected or not. The last question is the correct setup for the appdata, system, and domains shares. When I started they were setup as Array primary, Cache secondary and mover set to move to cache. Now they are cache primary, array secondary and mover set to move to cache. As long as mover is set to move to cache, does it matter what is primary or secondary? I also have an isos directory that is empty, no VMs so expected. Is that just a standard directory and if so is it supposed to be setup like the appdata, etc.? Thanks, Ross

That link is great, since it directly addresses the changes. So prior directions had me running appdata backup, etc. With using this technique and just letting mover do everything, I assume I can leave out ape-data backup step from prior videos...? Ross

I found great help and video for updating the cache drive in version 6. But the options are slightly different in version 7. Is there an easy way to move everything off the cache in v7 and then move to the larger drive? I have both cache SSDs installed, the larger one is not mounted or formatted yet. I think I have everything backed up using the latest appdata backup, but want to check in here before forging ahead. I have one docker (plex), I have no VMs. Thanks for any advice. Ross

That fixed the problem. Thanks!

Moved to a PC. So attached is the zip file! Thanks, Ross wserv-diagnostics-20250423-1452.zip

I have an old server, has been stable, used as a file share and has a Plex docker. Recently (weeks) updated to Unraid 7.01. While on vacation I got warnings of cache disk low on space. When I got home the plex docker was not running and the cache disk was full. I rebooted just to see if that helped, but it did not. My cache disk is a 256gb ssd, and has been adequate for years with the same docker and utilization. Plex is setup to record off of antenna, and it did not seem that anyone at home was using plex on a device that would need transcoding. With the cache drive full I assume I’ve lost those files, but how do I recover as gracefully as possible? I did order a larger cache drive and will set a minimum free space on the new one. The config was stable for years, but maybe the 7.01 update changed how things were working. Thanks for any advice! 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