<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rasdaemon on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/rasdaemon/</link>
    <description>Recent content in Rasdaemon on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 24 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/rasdaemon/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Hardware Error Monitoring: mcelog vs rasdaemon vs EDAC-utils</title>
      <link>https://www.pistack.xyz/posts/2026-05-24-self-hosted-linux-hardware-error-monitoring-mcelog-vs-rasdaemon-vs-edac-utils-guide/</link>
      <pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-24-self-hosted-linux-hardware-error-monitoring-mcelog-vs-rasdaemon-vs-edac-utils-guide/</guid>
      <description>&lt;p&gt;Server hardware failures rarely happen without warning. ECC memory controllers, CPU caches, and motherboard chipsets continuously detect and log correctable errors — but unless you actively monitor these signals, a correctable error today becomes an uncorrectable crash tomorrow. Self-hosted Linux hardware error monitoring tools give administrators visibility into Reliability, Availability, and Serviceability (RAS) events before they escalate into outages.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
