Quote from: meikel on June 05, 2026, 06:31:57 PMIt's an SAMSUNG EVO 850 250gb - it's used but when this issue happens again I'm fine with downtime. I may move to a raid1 at some point but it's not worth the hustle right now as there is no dedicated space for another ssd.I have seen the Evo 830 or 840 being written to death way past what the specifications officially stated so I hope you never have to replace it ever again :)
Quote from: Nullman on June 05, 2026, 05:58:58 PMThese results are quite confusing. S.M.A.R.T parameters are clearly indicating that SSD is pretty much dead. Confusing part is the fact that machine still crashed running Debian live. This indicates another issue beside dead drive.IMO it's 100% to be expected and probably the cause of all the issues...
# dmesg | grep -i microcode
[1] CPU microcode: updated from 0x1d to 0x24000026
# sysctl -a | grep hw.model
hw.model: Intel(R) Celeron(R) N5105 @ 2.00GHz
QuoteThis affected a number of CPU families in the current release, including
Raptor Lake (06-bf-02/05/06/07, Core Gen13/Gen14), Sapphire Rapids
steppings E0-E3 (06-8f-04 through 06-8f-07), Arrow Lake-H (06-c5-02),
Panther Lake (06-cc-02/03), and others.