thepensivemonk

Members
  • Posts

    8
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Toronto, ON CANADA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

thepensivemonk's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I have noticed this with Plex as well. Originally looked to RAM as a potential issue, but managed to eventually rule that out. I do have an appdata backup running right before Plex does its media scan and the fault always seems to happen around the same time in the early morning and in the "ld-musl-x86.so.l" library. Did you find any more details on your issue? pm
  2. Final update, for those interested. Running Memtest on my original RAM (Kingston HyperX Fury 2666 MHz, 2 sets of dual channel 16 Gb kits for a total of 4 x 8 Gb DDR4 sticks). Original DIMM configuration as per the ASUS motherboard guide with all four sticks in one quad-channel bank, ran into Memtest errors on the second pass. Current config, 2 x 8 Gb dual pairs in the top two DIMM slots of each channel. In my motherboard this would occupy the closest four DIMM slots to the CPU. In both cases the motherboard had no problem identifying all 4 DIMM modules and that I had 32 Gb installed. In the first config, however, the auto detected frequency was 2133 MHz. In my second config the detected frequency is 2400 MHz. Keeping in mind I have not done any custom setup of RAM or CPU. Memtest on this config has been clear for the last 3 hours of testing (no errors). If it makes through 3 passes I will be satisfied for the time being and let Unraid boot and monitor for changes. I would also like to mention that the Corsair Vengeance DDR4 3000 MHz sets that I purchased yesterday also flagged with errors when I installed them all in one quad channel. Again, in hindsight, maybe not a surprise as I was using two identical dual channel kits, not one complete four channel kit. I assume that baring the fluke of finding an in stock quad channel ram kit that happens to be on the ASUS QVL for this motherboard, I am basically kissing the bottom two banks of each quad channel goodbye. Luckily the memory I have have is sufficient for my current needs and all this will be considered for any future builds. pm
  3. Hmmm... so a bit more research, and I may have found a possible reason for my RAM errors. My mb supports quad channel memory, but I bought two Kingston DDR4 dual channel kits thinking that would be fine. As I dig into it further, putting those two dual channel kits in a four channel arrangement could potentially lead to some oddness. I believe the mb is considering the RAM to be quad channel compatible (exactly the same speed and timing), but I am wondering out loud if due to the fact I didn't use an actual quad channel DDR4 kit, then minor differences in the two kits installed are causing issues, but only some of the time. It will require possibly more server down time to test than I am really keen on, but I think my short term solution is since I have 8 ram slots, I will install the two dual channel kits in the top two banks of each channel, giving me the same overall ram, but no quad channel confusion. The likelihood of finding a quad channel kit for my old motherboard is slim to none, so I guess I start planning for a new server... pm
  4. My unraid system is fairly modest, being the first one I built. It is based on an ASUS X99-A/USB 3.1 motherboard, with an Intel Core™ i7-5930K CPU @ 3.50GHz and right at the moment has some Kingston HyperV DDR4 ram modules in it that will be replaced today. My power supply is a Corsair RM 750x powering my 7 6Tb WD Red NAS drives and two SSD for cache. I do have a nice Cyberpower UPS connected (I have made that mistake before, and not willing to risk server damage on a power cut). I have done no tuning or overclocking on this system at all, only making the necessary bios changes to support what I needed in Unraid. That the memory started showing errors in a memtest with basically default settings, I am fairly confident that there is a lingering RAM issue. However, I also was being very budget focused when I bought the RAM and it is possible that it was never an ideal match for this motherboard. I picking up some Corsair Vengence DDR4 3000MHz modules today that are specifically listed in the mb compatibility list and will install and test and report back. I have been so impressed with Unraid in general, but still learning all the ropes.. pm
  5. Just to update, though I had to make a dedicated UEFI memtest key to get the test to run, it did start finding memory errors on the second test pass. Very disappointed in Kingston as this was new identical matched RAM for this server. Now I need to figure out getting replacement as, based on the report, the failures seem to be scattered through all four DIMMS. >: ( pm
  6. I ended up with the first parity errors of my system last week, my build being about four months old with no issues. I re-ran the party check (with auto correction on, not knowing that I should leave it un-correcting). The errors persisted, so I did a clean reboot of the server, having read that an improper shutdown might have contributed.. I do have my system on a UPS, and though we have had power outages recently, the system did not have a power cut. All that said, the manual party check I ran after boot (also still accidentally had auto-correcting on, had not found that information in my research at that time) also showed a couple of party errors. I am running another parity check, this time properly with no corrections, but my question is this: How do I trace down the source of the issues? All my drives appear to be ok and I see zero read/write errors. If there is a drive failing, I would obviously like to track that down asap, but I need a helpful hand to point me to where I would find the clues. My most recent diagnostic is attached. Any assistance would be most appreciated. denki-3k-diagnostics-20210916-1205.zip
  7. THANK YOU! I was doing a lot of head scratching wondering why my attempt to use VirtManager were failing. This did the trick!