One bit in RAM: fixing a Phison SSD controller in "SATAFIRM S11" state
Comments on “One bit in RAM: fixing a Phison SSD controller in "SATAFIRM S11" state”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
A blogger (stperin) recovered data from a Silicon Power 120 GB SSD with a Phison PS3111-S11 controller stuck reporting "SATAFIRM S11". Using trulycrisp's Psychite vendor-command tooling, the author traced the state to one RAM flag bit, set at boot because of a single crash-log page on the NAND. Erasing that block restored the drive and its NTFS volume, avoiding the data-wiping MPTool reflash. This is one drive and one fault, and the raw-dump reconstruction stayed incomplete. SMART data pointed to repeated power loss as the underlying cause.
Why it ranked
No. 13 of 59 with a score of 0.63. The panel rated it highest on technical depth (0.97) and new information (0.91), lowest on audience breadth (0.34). Placed No. 13, No. 21 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Deep, well-substantiated reverse-engineering writeup of a Phison SSD controller fault and recovery; highly technical and novel, but a niche hardware audience, so moderate breadth and significance.
- AI judgeJudge 3gpt-5.6-luna
- A deeply documented, reproducible SSD recovery and firmware reverse-engineering case, with code, measurements, safeguards, and transferable debugging lessons. It is highly useful to storage and hardware practitioners, though the exact fault is niche.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.63total under rubric v2.3
- Significance0.49
- Reader interest0.80
- Audience breadth0.34
- Practical relevance0.62
- Substantiated0.88
- Technical depth0.97
- New information0.91
- Counts against: Promotional0.03
- Counts against: Overclaim0.13
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.50 | 0.30 | 0.68 | 0.49 | 0.38 | +0.24 | +0.118 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.71 | 0.80 | 0.90 | 0.80 | 0.19 | +0.26 | +0.209 |
| Audience breadthHow many people who build technology does it concern? | 0.41 | 0.25 | 0.35 | 0.34 | 0.16 | +0.13 | +0.044 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.58 | 0.55 | 0.72 | 0.62 | 0.17 | +0.22 | +0.136 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.98 | 0.85 | 0.82 | 0.88 | 0.16 | +0.05 | +0.044 |
| Technical depthHow technically substantive is it? | 1.00 | 0.92 | 0.98 | 0.97 | 0.08 | +0.05 | +0.048 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.90 | 0.85 | 0.98 | 0.91 | 0.13 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.03 | 0.03 | 0.02 | 0.03 | 0.01 | −0.19 | −0.005 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.20 | 0.15 | 0.04 | 0.13 | 0.16 | −0.11 | −0.014 |
| Sum of contributions | +0.626 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.626 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-01/13/"><img src="https://rubric.hrih.si/badge/2026-11-01/13.svg" alt="Ranked #13 on Rubric, 1 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 7 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenCausal conclusion
On the Phison PS3111-S11, a non-zero byte at RAM address 0x5C0CB5F0 makes the firmware's IDENTIFY handler report SATAFIRM S11 instead of the real model.
The article gives no link or citation for it.
The article says “If that byte is non-zero, the firmware's IDENTIFY handler reports SATAFIRM S11 instead of the real model”
The source says No source to compare with.
No source givenCausal conclusion
Erasing the NAND block holding the bad system-area page permanently ended the SATAFIRM S11 condition, and the drive returned as SPCC M.2 SSD / SBFM21.1 with its NTFS volume mounting.
The article gives no link or citation for it.
The article says “Erasing the block that held that page ended the condition permanently. The drive came back as SPCC M.2 SSD / SBFM21.1, mounted its NTFS volume”
The source says No source to compare with.
Couldn’t checkCausal conclusion
Psychite by trulycrisp provides the vendor-unique command transport, command set and firmware container format for the Phison S11, enabling RAM read/write, raw NAND reads, block erase, soft reset and firmware decryption over SATA.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “That project worked out the genuinely hard part: the vendor-unique command (VUC) transport that gets you past the standard ATA command set and into the controller”
The source says No passage could be compared.
Source cited by the article: github.com/trulycrisp/psychite
No source givenCausal conclusion
Phison's MPTool reinitialisation fixes SATAFIRM S11 but wipes the flash translation layer and all data permanently.
The article gives no link or citation for it.
The article says “This works. It also wipes the flash translation layer and, with it, every byte of your data, permanently”
The source says No source to compare with.
No source givenNumber
The drive's SMART data showed 2358 unexpected power-loss retracts out of 2368 power cycles (99.6%), 74999 power-on hours, and 92% life left.
The article gives no link or citation for it.
The article says “2358 unclean shutdowns out of 2368 power cycles. 99.6% of this drive's life ended in sudden power loss. It had 92% of its write endurance left”
The source says No source to compare with.
No source givenNumber
The dump's apparent encryption was not a cipher; it was caused by partial frames (flagged by bit 0 of OOB byte 8) being read as full 4 KB frames, and the derived placement rule matched the repaired drive for 60 of 60 LBAs.
The article gives no link or citation for it.
The article says “Verified against the repaired drive by content hash: 60 of 60”
The source says No source to compare with.
No source givenGeneralization
The VUC read path on the PS3111-S11 returns plaintext, so there is no XOR key to extract on this path, contrary to data-recovery vendor claims of XOR scrambling.
The article gives no link or citation for it.
The article says “the VUC read path returns plaintext: here is 176 KB of known content, read back through that path, unscrambled. There is no XOR key to extract on this path”
The source says No source to compare with.
No source givenNumber
Sorting versions of the same LBA by (superblock sequence, physical page index) picks the correct one only 42% of the time among complete frames, and the dump held 77% of live clusters but only 50% in complete frames.
The article gives no link or citation for it.
The article says “picks the correct one 42% of the time among complete frames”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 1 Nov 2026, 05:47 UTC. It played no part in the ranking.