hansolo77

Should I stop my current non-correcting scan then? It's still found 0 errors and I'm pretty confident it's passed the mark where the first error occured yesterday.

I don't think the controller has a fan on it, but I do have a fan blowing air across the entirety of my expansion cards. I also have all my fans set to be on full power rather than ramp up based on temps.

Thanks for the advice. I didn't know the UEFI version of memtest would cause a blank screen for so long. I just assumed it wasn't working. I never got an error messae or anything, so maybe it was working the whole time and I was just wrong. I'll try it again. That makes too much sense! I never thought about that. I will do that next. When I do that test, should I be doing it as a repair or just a scan? Also.. what if the problems don't crop up until like the last hour? Bummer lol. I hope it's not the controller. I mean yeah, anything is possible. I bought this one from eBay "The Art of Server". Highly recommended seller. Is there a way to test the controller directly? After I posted last night with the diagnostic logs, I started another non-correcting check. It is almost 12 hours in and has found 0 errors. [fingers crossed]

Completed another correcting parity check.. down to 20 errors. Still pretty concerned about it. Not sure what else to try. Is it possible my parity drives are just corrupted, and I could "rebuild" them by removing them and re-adding them? I've only been playing with Unraid about a year. Hard to believe I've got such a massive problem with my parity after all this. kyber-diagnostics-20210506-2242.zip

I saw the Memtest86 entry in the Unraid boot menu but when I select it, not thing happens. It might be that it's using the same version I was unable to load. But yeah, I think the memory is fine. I'm running another parity check, and it's still finding errors. I don't know what's causing it. I disabled all my dockers and vm, rebooted (perfectly) and started it. Nothing is running that could be accessing the array. Yet still it's finding errors after all these corrections.

It's been about 24 hours.. I've got 0 errors on the memtest with 2 passes and another 3/4 of a third pass. I believe the RAM is not the issue.

I'm actually trying to get the memtest started.. I have it written to a USB flash drive.. plugged it in, my BIOS reads it, but if I have it boot via UEFI it just sits at a blank screen. If I boot it via regular, I get an error that it's not bootable and to replace it or select a different device. So I'm going to try an older version. My motherboard should be compatible with the latest version (released around September 2019), so I don't know what I'm doing wrong. ==== EDIT ==== Got the latest v4 release, got a new option in my BIOS for "USB Floppy". Using that, I've now been able to get it to boot the memtest, and it's running. If I remember right, and the program hasn't changed, I can just leave it running overnight. The longer it runs the more accurate the test. I'll report back tomorrow unless somebody says otherwise. Also of note.. I was able to successfully shutdown Unraid without any delay issues again before loading Memtest. I truly feel I've resolved the original issue. It had to have been a combination of using UnBalance Scatter while the NZBGet docker was attempting to repair a massive download that was missing parts. It was something like 54gb. Mover was set to go every hour, so it was probably trying to move files onto the array while trying to repair the download, while trying to Scatter. Everything all at once. I didn't even realize it was doing that until I had rebooted (unsafely) and saw it trying to resume the recovery after the fact. I'll know better next time. If my RAM checks out, I might have a new problem to address. I just completed another self-correcting parity check and it found 24 errors. That's a LOT better than the 138k I was getting before. I'm just concerned because it IS still 24 errors. I wish I could verify integrity of the data, but it's all media and I don't have anything to compare it against. No way to know if anything is corrupted until I try to access it and have issues. Oh well. Thanks again for the help though everybody. Still learning!

Cool thanks. So I should let it run it's tests.. and if it finds faults I should replace the ram? Or is there something else to do? It's been over a decade since I've ran a memtest. Kinda interested to see how it does.

How do I go about running a memtest? I see there is an option in the pre-boot options of Unraid, but it doesn't do anything when I select it. Do I need to have a copy of it on a flash drive or something first? Also... I have reboot my server probably a dozen times in the last few days. Looks like I've fixed THAT problem. I ran another correcting parity check and it found 24 errors. I feel like I'm getting closer to a solved matter, but I still want to be sure. A memtest sounds like something I can do.

Thanks will do!

OMG Somebody please help me! I went in and updated the BIOS. It finished 100% and rebooted. Now, the PC comes on, but there is no video display. I'm completely screwed now. I can't access anything. i can't go into the BIOS, and I can't get Unraid to load. It just sits there, with the fans spinning and the LED on. I've already tried using the reset CMOS button on the back of the case, with power plugged in and unplugged. Nothing works. I can't even access anything to try to reflash the BIOS again. It's just completely bricked except for power, fans, and LED. It's Sunday too, so their Live Chat support is not available. I don't know what to do. I'm breaking down mentally here, about to start crying. OMG WHY ME? ------------------------ Edit: I think I got it. I discovered I had downloaded the latest BIOS, and it was a BETA. So I grabbed instead the latest "stable" BIOS and used that. Now everything is back up. I noticed the settings were all reset, and a lot of the tweaks I set, like (dis)enabling things had changed where they were. I think I got it for the most part, but now it's displaying my HBA card discovering all the drives. It didn't do that before. Something else I set, I read in that Ryzen thread @JorgeB linked to set "Power Supply Idle Control" (or similar) to "typical current idle" (or similar)".. so I did that. I also found where the C-States setting is, but I left it at Auto. Should that be disabled? Thanks again guys, I really appreciate it!

The thing that bugged me about that 2600 vs 3200 is that the RAM is 3600 to begin with. Kinda like the old CPU days where you had a clock speed of 100mhz with a 4x multiplier to get 400mhz. My BIOS settings for the RAM overclock has all kinds of settings to tweak that stuff. I never mess with it, because I know overclocking leads to instability. I try to keep everything at their base levels. So when I installed this system, I knew the RAM was clocked at 3600mhz, and the motherboard supported it, so I set it to that speed. I didn't attempt to overclock it, just set it at the RAM's preset speed. I also didn't know the Ryzen processor had an upper safe limit of 3200mhz. So now I have the RAM clocked down to that. This is mostly a media/PLEX server, so I guess RAM speed isn't all too important, except for when I'm transcoding. I've still got the Docker and VM modules disabled. I've been able to complete another extended Fix Common Problems scan with no issues. I've also rebooted the server 3 times now and it was able to do so with no problem. I'm going to try slowly turning things back on and see if the reboots still work. I've had a few ideas as to what caused the problem in the first place. The first major thing I added to my server since the last time I was able to properlly shutdown was the "My Servers" addon. I wonder if that is causing some kind of background lockup with the network. The last time I had a force shutdown, the logs showed some networking issues. It also indicated it was unable to unmount the cache drive. With no array activity, and no dockers or vms, it makes me wonder what else could be holding the cache. --- The other thing I've done recently, was the UnBalance Scatter. The system has been fine for months. I actually reached something like 48 days uptime before rebooting to install new nVidia drivers. But when I noticed I had a drive 100% full and started to use the UnBalance plugin, that's when I started having trouble. I remember the system becoming unresponsive and needing a hardware power button reset to come back up...while it was running the scatter. I think that also explains why I had so many duplicated files (literally like complete TV shows, not just a few episodes, were duplicated on 2 drives). The process of moving was interrupted. And with the forced shutdown, the Parity WOULD be out of sync. I've gone back through and erased all the duplicates, and that last non-correcting parity check only came back with 10 errors. I think I probably need to just do one more correcting scan and that should be it. I think for the time being, I'm going to try enabling various dockers, one at a time, and reboot. See if they are stable. NZBGET in particular since that's the one that was logging segfaults. I think it might have been struggling because I remember it attempting to uncompress a really large file that was incomplete and it was rebuilding from parity files, all while the scatter was running, and then the lockup happened with a forced reboot. So I've gone in and removed all the files in the NZBGET download folder to eliminate any needed work. I might just uninstall that docker, and reinstall it to be safe. I am still interested in what I'm reading about the Ryzen c-states. After coming home; waiting for a reply, I've been reading about it. The forum was a buzz with posts back when 6.7 was coming out. We're now on 6.9, so I'd think some maturity in the code would have come by now. The same is true about my specific components; I need to see if there's a new BIOS update, since I believe I'm still running the initial release. All things to look into tomorrow. Good thing I'm off work. As for now, I'm really tired and my brain (and eyes) are starting to get foggy. I'll need to look at this from a fresh perspective in the morning. Still would like feedback and help if anybody has any further ideas or suggestions.

Quick little update. I decided to remove the 10gbe NIC hardware from the server. Since it's always giving me trouble with my other PC (drivers, Windows always "detects a problem" and disables it), it's just time to take it out. I got it to move the nearly 100tb of data between my old server and this one. Now that it's done, I put the NIC in my regular PC and had troubles since. Figured since I was inside the case reseating the RAM, I might as well. So logs might show it's missing now.

Seems like the "safe" shutdown didn't work. I had all Dockers off, and disabled them in the Settings tab. The only VM running was Windows 10, which I actually had "sleeping". Nothing was accessing anything on the array. When I did the shutdown, my web interface showed it was shutting down but the server computer never did. I attached a keyboard to the machine (the screen was blank) and hit enter a few times.. it indicated it was waiting 420 seconds for a graceful shutdown. I remembered I saw a thread on here, I think @Squid posted it, about increasing the timeout for various things to allow them more time to shutdown before hand. Well anyway, the time expired and the terminal screen indicated it was Forcing the shutdown. It saved a log: kyber-diagnostics-20210501-1615.zip After it fully shutdown, I rebooted and accessed the BIOS. It indicated that the RAM was running at 3600mhz. A feature called A-XMP was enabled, and the speed was set at 3600mhz. I think I must have done that when I first put the parts together. I changed the frequency to "AUTO" then disabled the A-XMP and rebooted. It rebooted up and the BIOS then showed it was at 2600mhz. That sounded really low, so I turned the A-XMP back on and set the frequency to 3200mhz and rebooted. Now the BIOS shows it's running at 3200mhz. UnRaid loaded up, but (as expected) it's now running another parity check. Awaiting further instructions...

Just got home. Looks like it's just the remote access that was having trouble... Dad said the power went out and the modem hadn't come back on yet. I had to power cycle the modem and router. The server is on a UPS so it was able to continue the non-correcting scan. Good news I guess.... it only found 10 errors. So I'm going to reboot the server, access the BIOS and drop the RAM speed down. Once back up, what should I do next? Also.. the last extended Fix Common Problems scan came back error free! Thanks again for all your help! kyber-diagnostics-20210501-1605.zip

Cool I’ll check that when I get home. I’m probably going to have to reboot anyway. just sucks because now I can't get a diagnostic zip after the non-correcting parity check. Ugh.

I’m pretty sure I’m not overclocking the ram but I can double check. If it’s true though that the problem is related to that, why would it only now be showing issues and not before? I’ve had this running for a long time without issues. Also, I’m at work right now and My Servers shows my server is offline. 😬 not a good sign...

No I haven't. I was going to wait and see how this non-correctings can goes first, and see if there's anything else to try.

OK.. it was pretty late I thought I had 2 in there. But I'm pretty sure I've not rebooted since that was posted.

I actually have another scan running now.

I think that might be the case. When I looked at the modification date for those files on the array, they were back in August of last year when I was building my server. I just used Krusader and erased them.

I ran a correcting check, rebooted, ran 2 more correcting checks and now a non-correcting check is in progress. The last diagnostic zip I posted should have the 2 correcting checks. I've not rebooted yet, so I'll post another zip after the non-correcting is over.

Sounds good to me, that's what I thought. I'm just trying to come up with an explanation to why I would have so many sync errors after 3 runs. Doing a non-correcting scan now and it's found 6 already in the 9 hours of running. Still got 22 hours to go. I looked at the extended scan log from FCP.. looks like I have a problem too where my `/system` path, that holds the docker and libvert folders is actually spread across multiple locations.. disk 1 and cache. That might be why I'm having issues with the nzbget docker... I wonder how that happened, as I never touch those things. The share is configured with 'Prefer Cache`. But I would think it's an either/or situation, where it would either be on the array or on the cache, not both. How would I fix that?

I don't do this. I always access files through the shares, never via /mnt/disk**. Unless when I did the Unbalance plugin/scatter. Maybe that screwed me all up.

Ok... so how do I do that? I'm still pretty noob. I don't know what it could be.