Bust

I'll keep an eye on it, recently it hasn't gone more than a few weeks without the issue happening. If nothing happens in that time, I'll consider this solved as a bad power or data cable. Thanks for your help and potentially saving me from buying a new drive :)

Yes, I had rebooted. I've not noticed there to be read errors a few at a time with the parity disk, the only time I see the read errors is when it's completely flooding the logs. An all or nothing situation if you will. I swapped my parity drive to a known good slot in my JBOD enclosure. Posting diags again. tempest-diagnostics-20250921-1318.zip

Apologies for not adding in the original post. I’ve attached the diagnostics. tempest-diagnostics-20250920-0947.zip

This has been going on for a few months, where the log filesystem will completely fill up and CPU is consistently at 100%. It happens randomly and is only temporarily fixed by performing a reboot. Sometimes it is fixed for a week, sometimes longer. The log is filled with the following errors: Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=10739486256 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=8943333208 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=8943333008 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=4962140440 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=10739486256 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=10739486256 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=8943333016 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=8943333216 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=4962140248 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=10739486256 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=4962140448 Sep 14 02:03:56 tempest kernel: md: disk0 read error, sector=10739486256 This would indicate to me that my parity disk is potentially failing? However, after doing an extended SMART self-test, nothing immediately jumped out at me so I am skeptical. Before I chalk this up to a bad drive and replace it, is there anything I'm missing or should test first? Appreciate any help. ST14000NM0288_E_ZHZ208XX0000G841014N_35000c500a7c0ca7f-20250919-2238 3.txt

I'm attempting to figure out which process is creating DNS queries for "none.lan", but am having no luck. From what I understand, this behavior typically happens when a field that should be populated with a domain name is not populated. I've turned off all VMs and Docker containers to narrow it down to unRAID. I also created a logging rule in iptables which verified the behavior is stemming from the root user. Does anyone have an idea of how to accomplish this task? I've seen auditd suggested, but that doesn't appear to be available for Slackware.

Hey there, I've done some research and believe one of my disks needs to be replaced. Before I purchase a new disk, I would really appreciate a once-over of the SMART report from someone more knowledgable than myself. Additionally, I was checking other disks and noticed all appear to have a very large number of "Total errors corrected". All, but the disk I am attaching the SMART report for, have 0 "Total uncorrected errors". Is this necessarily a bad thing? Edit: for context, the large very large numbers are "3479317663" errors corrected with "566140.855" Gigabytes processed [10^9 bytes] ST33000650SS_Z2959PXT_35000c50055abbc8b-20230707-2149.txt