https://tsvinc.dev/tags/smart/ Recent content in Smart on tsvinc Hugo en-us Wed, 08 Jul 2026 00:00:00 +0000 https://tsvinc.dev/posts/alerts-you-understand-at-3am/ Wed, 08 Jul 2026 00:00:00 +0000 https://tsvinc.dev/posts/alerts-you-understand-at-3am/ <div class="tldr"> <span class="tldr-label">TL;DR</span> A digest that dumps raw SMART counters is complete and useless: <code>re=344</code> means nothing at 3am. Alert on <em>growth</em> — compare today's counters against yesterday's row for the same serial, and push urgently only when a number moved. Seed the first sighting of a drive silently, or every new disk pages you on day one. Two channels, two intents: a calm daily digest that reassures, and an urgent push that interrupts. </div> <p>Here is the notification my daily SMART logger pushed on day one. Four drives, one line each, everything the tool knew:</p> https://tsvinc.dev/posts/reallocated-sectors-dying-or-scarred/ Wed, 08 Jul 2026 00:00:00 +0000 https://tsvinc.dev/posts/reallocated-sectors-dying-or-scarred/ <div class="tldr"> <span class="tldr-label">TL;DR</span> A high <code>Reallocated_Sector_Ct</code> is history, not prognosis. The drive with 344 reallocations was healthy — scarred, but its firmware was still successfully remapping. The drive with <em>zero</em> reallocations was the dying one: <code>Current_Pending_Sector</code> climbing while the reallocated count stayed pinned at 0 means the firmware has stopped remapping, which is the failure. Judge by whether the counters <em>move</em> under a forced write pass, not by the raw number. </div> <p>Two drives on the same HBA, same evening, same test. Here are the SMART lines that matter, before I touched either of them:</p>