Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics.
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I wouldn't hibernate on an m2ssd qlc degradation killed my samsung 980 pro. it got corrupt sectors so bad that the samsung magician software just gives up after scanning
Wasn't that the drive that got insane write amplification due to a firmware bug?
Edit: yup, definitely wasn't cuz you were actually writing to it an unusual amount. Those drives would wear themselves out during normal use for seemingly no reason. I've been hibernating to a WD Black for years, and it's fine.
I've updated the firmware the same week it was reported in tech news, still bsods randomly. I use a new drive now
The firmware update couldn't fix damage that had already been done.
The bugged firmware was actually killing the drives by wearing them out prematurely.
The fixed firmware only stopped damaging the NAND storage, but there is no way for it to undo damage that had already occurred.
An ssd functioning normally can deal with years and years of daily hibernating.
That sucks but as another said that seemed to have been a firmware bug. I have hibernated thousands of times with 32GB RAM and had no SSD die on me yet.