Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

18
  • 1
    @horsey_guy just posted fstab near the end of the ‘what I've tried’ section. Thanks Commented Aug 2 at 0:23
  • 1
    I just added a photo of dmesg filtered for “btrfs” near the end of the same section. Filtering for “error” turned up nothing else relevant AFAIK. Looking at journalctl -xb now. From what I've read so far btrfs check —repair looks like a long shot to me as well Commented Aug 2 at 1:06
  • 5
    1. Please don't post images of text. Copy and paste the text itself into your question and format it as code by selecting it and pressing Ctrl-K or by using the editor's {} icon, or by adding a line containing three backticks before AND after the text. 2.You are almost certainly wrong about what you think is causing this. Changing the hostname etc will not cause disk errors. Commented Aug 2 at 3:00
  • 2
    3. The most likely cause can be found in your statement "The SSD and everything else in my computer is about 6 and a half years old, so maybe something is failing." - 6 1/2 years is beyond the life expectancy of almost any SSD, certainly beyond that of typical consumer-grade drives. Try running smartctl -a on the SSD's real device node (not the /dev/mapper entry), and keep an eye out for the drive's age and lifetime and any FAILED/FAILING entries. maybe something like smartctl -a /dev/sdi | awk '$1 ~ /^(9|202)/ || /FAIL(ING|ED)/' which works for my ancient Crucial MX300 drives. Commented Aug 2 at 3:06
  • 2
    smartctl -a doesn't show the attributes on an nvme like it does for a sata ssd - i assumed sata ssd was what you meant when you said "SSD" but didn't say "NVME" . I only realised you were talking about an nvme when I saw the smartctl output. And, yeah, the info seems inconsistent and contradictory. and the power on hours seems completely wrong for a 6.5 year old drive. BTW, "Power on Hours" is exactly what the name implies - the count of hours where the drive has had power. Commented Aug 3 at 3:49