Rock G

I understand and you are absolutely correct, always check compatibility between the 3 parts. The mobo and chipset supports the stock speed of my RAM however it's a bit outside of the official support of the CPU which I also noticed on the faq below. However, I've had this cpu+ram+mobo combo for roughly 3yrs+ running unraid with no major headaches or annoyances and I imagined if it was not compatible, it would've exhibited the same issues shortly after and not just now. Nevertheless, I will make note of this and if I'm unable to pinpoint the cause and it becomes unbearable, I will swap them out. Appreciate your feedback @JonathanM.

Thank you @JorgeB and yes my mistake, I meant I switched the docker from macvlan to ipvlan mainly because I initially noticed the hard locks whenever Plex is in use (which happens to be the docker always in use). I had the XMP profile enabled and set to 3200MT/s but I decided to disable it recently while trying to pinpoint the root of this issue. The stock speed is 3000MT/s. I'll monitor over the weekend to see how things go and then run memtest later if needed. Appreciate the suggestion.

Over the past few weeks I've been experiencing random hard freeze almost every couple of days. It doesn't seem to matter whether there's a high load/activity or if the system is idle (in terms of me accessing anything). Unfortunately it has gotten worse to a point that it happens practically everyday. I primarily use the server as a NAS and I only have a handful of dockers and VMs (which I haven't used for quite some time). Also, I only run dockers as needed and I don't leave them running constantly. My initial reaction was the docker ipvlan setting which I found on other threads, but changing it to macvlan didn't clear the issue. Next stop was the cache drive. I found some data corruption on my nvme cache drive which was set to btrfs so today I decided to rebuild cache drive and try XFS. I disabled docker, cleared/deleted partition/formatted to XFS which all went smoothly but before I can even rebuild any of my dockers, I ran into a couple more hard freeze. When this happens, the GUI becomes unresponsive and I have to manually shutdown. Ignoring the data corruption lines in the syslog, I noticed quite a few entries of rcu_sched self-detected stall on CPU which I'm not familiar with. Can someone pls review the attached logs, dumb it down for me pls and provide feedback? I only exported the sections before I had to shutdown but I can upload the entire syslog if needed. Thanks in advance and always very appreciative of the community. Edit: forgot extra details. XMP is disabled and also disabled C-states for kicks. CPU: Threadripper 2990WX Mobo: MSI MEG X399 Creation RAM: HyperX Predator 64GB (4x16) 3000MHz CL15 UnRaid v: 6.10.3 random1_06.22.2022.txt random2_06.24.2022.txt

Looking good on 6.9.0-rc2. Thanks for all your work and time!

Thanks for the feedback and tips @itimpi. Looks like you are correct, searching for "ata1" and "ata6" in the logs did point me to the parity drives. I'll swap out those cables and keep an eye on the syslog. Thanks again!

I randomly see this error in the logs "Tower1 kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen" and when I tried running the parity check earlier, it was crawling. I've read in past threads that this is usually due to a bad sata cable but need a little help figuring out which one to replace. I've attached the full diagnostics. Is it disk1 and disk6 or do I need to count the parity drives too? tower1-diagnostics-20191008-0422.zip

I am upgrading a couple of my hard drives and wanted to know if anyone would be interested in two 12TB IronWolf HDDs. I'm selling for $250 each + actual shipping cost within the US via USPS Priority Mail or Standard mail whichever the buyer prefers. I can also ship outside of the US if anyone is interested. I'm only taking Paypal at the moment. Pls PM if interested. ST12000VN0007-2GS116_ZJV0W3Q1-20190912-0027 parity2 (sdk).txt ST12000VN0007-2GS116_ZJV0VJAW-20190912-0027 parity (sdf).txt

Thanks @Squid

I noticed something unusual in the last 2 builds. I keep getting notifications that there's an update but when I update, it shows 0 B pulled and it still shows update available. It doesn't matter whether I use docker, latest or public in VERSION, it still thinks there's an update avail. I also tried a couple of commands from a terminal but it looks like its running on the latest build. Other than this, everything is running fine. Does anyone have any suggestions?

Thanks Squid, I would've never picked that plugin to have a lurking background process. Ah yes, thank you for reminding me of Nerdpack. I've been trying to figure out how to install iftop and nethogs and stumbling along the way. I did notice a constant ping to sync the time with google. Squid is probably right, there's nothing to worry about. It was something random that caught my attention and couldn't find a reason. If anyone else has any input, please feel free. I'll take it as in as good learning experience.

I suspected that as well but I never seemed to have noticed this activity in the graphs. I'm attaching the diagnostics and an updated screenshot that I just took. tower1-diagnostics-20190826-0123.zip

Hi guys, The past couple of days I noticed constant network traffic and cpu activity while no dockers or tasks are running. I have no VMs and I mainly use Plex but I constantly see CPU and network traffic, and when I say constant I mean non-stop as long as my machine is on. I am Linux novice so I'm hoping the community can teach me a few things and point me to the right direction. I am using version 6.7.2 and I took a screen shot of the system stats after a few minutes yesterday and as you can see, the cpu and network traffic is low but non-stop and I would like to understand where it's from. I tried looking at the processes and the sys log but obviously I have no idea what I am looking for. Any info that can help me figure out this activity will be greatly appreciated. I can attach the syslog and an updated system stats for a longer period if needed. Thanks in advance and looking forward to everyone's feedback.

Thanks johnnie.black, I suspected cache1 contributed to the errors so I moved shares from the cache drive to the array then ran another parity check. It came back clean with no errors but as a precaution I followed your suggestion as well. I ran multiple passes of memtest and all passed error free. I also went ahead and replaced the sata cable on cache1 for good measure.

Hello everyone, I have been using unRaid for a little over 6 months and ran into my first issue that I need assistance with. I regularly run a parity check once a month but ran into some errors 2 nights ago, about 200+ parity errors, and disk1 ended up being mounted read-only. I also noticed a ton of read errors and corrections on one of my cache drives. After some googling I started the array in Maintenance mode, ran a filesystem check followed by a filesysten check with repair on disk1. Also, and I believe this is where I went overboard cause I'm a maniac and potentially created more issues, I started messing around with my cache drives. First I moved my shares off the cache drive to the array (appdata, system, downloads & domain), stopped the array, unmounted both cache drives, deleted each partition, reformatted in XFS, remounted then again formatted the cache disks after restarting the array. I then moved the same shares back to cache, restored appdata from backup then had to rebalance the cache drives because of dual profiles. After all of this I then restarted the parity check which usually runs for about 15-16hrs due to the size of my array. Fast forward this afternoon, I received an email notification that the parity check completed but now there are more errors, 615 to be exact. I have not done anything since the parity check completed aside from doing another diagnostic dump which I also did prior to running this 2nd parity check. Can someone please review both diags and provide guidance? I have a 2nd unRaid box which is basically a clone of Tower1 so worse comes to worse, I have my stuff backed up. I also just bought 2 new 12TB Ironwolf drives, (thanks to prime day!), which I was planned to use as an upgrade to both parity drives on Tower1 before all of this happened. With that said, I am fine blowing everything on Tower1 to start over then restore from Tower2 but I also welcome the learning opportunity in terms of troubleshooting and learning more about the system. Any feedback and guidance will be greatly appreciated.