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*
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_`
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
dmesg
filtered for “btrfs” near the end of the same section. Filtering for “error” turned up nothing else relevant AFAIK. Looking atjournalctl -xb
now. From what I've read so farbtrfs check —repair
looks like a long shot to me as well{}
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.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 likesmartctl -a /dev/sdi | awk '$1 ~ /^(9|202)/ || /FAIL(ING|ED)/'
which works for my ancient Crucial MX300 drives.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.