Repository navigation
docs(hardware): smaug's boot disk, read with smartctl (#413) - #477
Merged
Merged
Conversation
TrueNAS 25.10.7 is installed on the S3520 and the drive has been read properly for the first time. Serial PHDV706401TM240AGN, firmware N2010101, SATA 3.1 at 6.0 Gb/s, SMART self-assessment PASSED. That closes the last thing this entry listed as owed. It is a used drive and the entry now says so with numbers. Media_Wearout_ Indicator 088 on Intel's own falling counter, so roughly a tenth of the write endurance is spent — ample for a disk carrying an operating system and no data. 13,182 power-on hours, about eighteen months. Around 72 TiB written by whoever had it before. Zero pending, zero reported-uncorrectable, zero CRC, zero end-to-end, and 24 C in the bay with the fan running. 509 unsafe shutdowns out of 538 power cycles is the number that says what this drive did in its previous life: it was almost never shut down cleanly. It is also this entry's own argument, tested by someone else. The part was chosen because "a boot disk that survives a power cut is worth more here than one that is merely fast", and Power_Loss_Cap_Test still passes after 509 of them. The four reallocated sectors get the most words, because they have an operational consequence that is cheaper to write down now than to discover on the day. SmartDriveBadSectors fires on reallocated_sectors > 0, deliberately — a remapped sector never un-remaps, so the first one is the finding. This drive will therefore trip that alert the day SMART collection reaches smaug, exactly as oracle's 32 static sectors do. The answer is the one #351 already built and does not need inventing again: silence the static fact, let SmartDriveBadSectorsGrowing carry the trend, because a silence matches labels and no label carries the count. SmartDriveWearHigh will not fire; it wants 80 % of rated life and this is near a tenth. I checked both thresholds against the rules rather than asserting them. Nothing else moves. No pool exists, the Exos drives are still in transit, and the address is DHCP on 10.0.40.100 rather than the static ADR-0016 wants — all of which stay as they are until the drives land. Refs #413 #351 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TrueNAS 25.10.7 is installed on the S3520, and the drive has been read properly
for the first time. Serial
PHDV706401TM240AGN, firmwareN2010101, SATA 3.1at 6.0 Gb/s, SMART self-assessment PASSED. That closes the last item this
entry listed as owed.
It's a used drive, and the entry now says so with numbers
Media_Wearout_IndicatorPower_On_HoursAmple for a disk carrying an operating system and no data.
509 unsafe shutdowns out of 538 power cycles
That's the number that says what this drive did in its previous life: it was
almost never shut down cleanly.
It's also this entry's own argument, tested by somebody else at their expense.
The part was chosen because "a boot disk that survives a power cut is worth
more here than one that is merely fast" — and
Power_Loss_Cap_Teststillpasses after 509 of them.
The four reallocated sectors get the most words
Because they have an operational consequence that's cheaper to write down now
than to discover on the day:
SmartDriveBadSectorsfires onreallocated_sectors > 0, deliberately — aremapped sector never un-remaps, so the first one is the finding. This drive
will trip that alert the day SMART collection reaches
smaug, exactly asoracle's 32 static sectors do.The answer is the one #351 already built and doesn't need inventing again:
silence the static fact, let
SmartDriveBadSectorsGrowingcarry the trend,because a silence matches labels and no label carries the count.
SmartDriveWearHighwill not fire — it wants 80% of rated life and this isnear a tenth. I checked both thresholds against
host.rules.yamlrather thanasserting them.
Nothing else moves
No pool exists, the Exos drives are still in transit, and the address is DHCP on
10.0.40.100rather than the static ADR-0016 wants. All of that stays as it isuntil the drives land.
make validatepasses;check_docsgreen at 10 assertions.Refs #413 #351
🤖 Generated with Claude Code