Add TRIM corruption sequel post + publish SATA cable post (en/zh, og+banner)

Browse Source

- New post: 'The Corruption Came Back on Different Drives — the Cause Was
  TRIM, Not the SSDs' — same 0x8941f998 zeros fingerprint on a second drive
  stack (IronWolf 110 SATA pair), root cause queued TRIM (FreeBSD gag 264139),
  fix diskAutotrim=off + nodiscard, scrub evidence, enterprise SATA buying
  guidance. en + zh, custom OG + banner.
- Publish formerly-draft SATA cable post (draft:false) with OG + banner.
- Correct drive identity in both: ZA960NM10001 is Seagate IronWolf 110, not
  'Samsung PM9A3' (PM9A3 is NVMe; FPDMA errors are SATA-only).
- Old RAID post (en+zh): cross-link to sequel, fix 'a Samsung' -> IronWolf 110.

...

This commit is contained in:

hoelee

2026-09-18 05:38:13 +08:00

parent fb66e17b50

commit 044ded45b3

12 changed files with 762 additions and 36 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

public/banners/that-dying-ssd-was-just-a-bad-sata-cable.png

BIN

Binary file not shown.

Side by Side After Width:  |  Height:  |  Size: 73 KiB

public/banners/the-cause-was-trim-not-the-ssds.png

BIN

Binary file not shown.

Side by Side After Width:  |  Height:  |  Size: 75 KiB