Timeline for Btrfs read-only file system and corruption errors
Current License: CC BY-SA 4.0
31 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3 at 4:19 | comment | added | Growing My Roots | @cas I was having and still am having a lot of trouble using the stackexchange site in my browser on my phone. So probably because they dedicate most of their time to the app rather than the mobile site. Totally agree with avoiding apps. I tell everyone to do the same | |
| Aug 3 at 4:17 | comment | added | Growing My Roots | @cas thank you for clarifying the SMART Data output. Looks like I need to start looking at other drives soon. Not sure if it’s really worth investigating this issue any more. | |
| Aug 3 at 3:56 | comment | added | cas | BTW, I have no idea why you're talking about apps. I never use them either and would never recommend their use to anyone (IMO, the only reason companies make apps rather than web sites is so they can trick people into installing spyware...to me, "app" is almost synonymous with "spyware" and "malware"). | |
| Aug 3 at 3:49 | comment | added | cas |
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.
|
|
| Aug 3 at 2:45 | comment | added | Growing My Roots | @ also Percentage Used seems very low if this is the lifetime. There’s also contradicting info with the error information it appears. Will look into in a bit. | |
| Aug 3 at 2:43 | comment | added | Growing My Roots |
@cas I added the output of smartctl which is one of the programs I remember trying before. However, everything you suggested after the | didn’t output anything because there were no attributes with 9, 202, etc. In fact there were no attributes at all in the output. Maybe I need to look into how to get the attributes to print. The output of the SMART Data section doesn’t add up to me at first or now second take. The power on hours are very low for how old the SSD is or maybe I just don’t know what the definition of power on hours are.
|
|
| Aug 3 at 2:37 | history | edited | Growing My Roots | CC BY-SA 4.0 |
Added SMART Data section from the output of `sudo smartctl -a /dev/nvme0n1`
|
| Aug 2 at 16:59 | comment | added | Growing My Roots | Thanks for your suggestions. I’ll admit I could have done this better. But I was trying to create the post in one browser session (so people reading the post weren’t reading incomplete info) and text wasn’t copying from stackexchange to my notes program properly. Possibly because I am using a browser rather than the app (if there is one). I try to avoid apps so I’m not confined to their privacy environment. Similarly I try not to use a browser on a live disk unless I’ve adjusted many privacy and security settings which is cumbersome every time you start the disk up. Maybe I’m overthinking :) | |
| Aug 2 at 7:13 | comment | added | cas |
You shouldn't need to extract text from the images. it looks like you're booting from a Live CD or USB stick, so just save the text to either another (writable) partition on the same USB stick or to a second USB stick (e.g. lsblk -f > /path/to/writable/filesystem/lsblk.txt). Then you can just copy & paste it from the file into your question. Or use script to log everything that happens in that Live CD session to a file (but that's going to have a lot of control characters and escape codes which will need to be edited out).
|
|
| Aug 2 at 6:50 | history | became hot network question | |||
| Aug 2 at 4:47 | comment | added | Growing My Roots | @cas thank you for clarifying that changing the hostname likely wouldn’t cause disk errors. I am trying to learn from any mistakes I’m making | |
| Aug 2 at 4:45 | comment | added | Growing My Roots | @cas I will be more mindful about posting images. I certainly don’t mean to exclude or frustrate anybody. I copy and pasted some text from images when it was smaller amounts but was having a lot of issues with it so didn’t for lots of text especially because I’m not exactly sure what’s relevant and I have a disability so it was very tedious. I am doing almost everything on my phone because of the read only issue so this isn’t common for me to post images. I’m open to any programs for helping copy and paste text from images reliably and will keep your thoughts in mind :) | |
| Aug 2 at 3:25 | answer | added | cas | timeline score: 5 | |
| Aug 2 at 3:21 | comment | added | horsey_guy |
@GrowingMyRoots Maybe have a look at btrfs rescue options too.
|
|
| Aug 2 at 3:06 | comment | added | cas |
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.
|
|
| Aug 2 at 3:00 | comment | added | cas |
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.
|
|
| Aug 2 at 1:06 | comment | added | Growing My Roots |
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
|
|
| Aug 2 at 1:04 | answer | added | Hauke Laging | timeline score: 9 | |
| Aug 2 at 1:02 | history | edited | Growing My Roots | CC BY-SA 4.0 |
added 130 characters in body
|
| Aug 2 at 0:51 | comment | added | horsey_guy |
btrfs check --repair may work successfully with some praying beforehand in my experience. Create a backup before doing any major repairing though.
|
|
| Aug 2 at 0:44 | history | edited | Growing My Roots | CC BY-SA 4.0 |
added 162 characters in body
|
| Aug 2 at 0:28 | comment | added | horsey_guy |
How about showing the most interesting parts (such as filesystem error notices) in the commands, dmesg and journalctl -xb?
|
|
| Aug 2 at 0:23 | comment | added | Growing My Roots | @horsey_guy just posted fstab near the end of the ‘what I've tried’ section. Thanks | |
| S Aug 2 at 0:19 | history | edited | Growing My Roots | CC BY-SA 4.0 |
Fix punctuation, formatting, extraneous markdown, verb-agreement of `run`, and capitalization. Use sentence case instead of title case for headings.
|
| S Aug 2 at 0:19 | history | suggested | horsey_guy | CC BY-SA 4.0 |
Fix punctuation, formatting, extraneous markdown, verb-agreement of `run`, and capitalization. Use sentence case instead of title case for headings.
|
| Aug 2 at 0:01 | comment | added | horsey_guy |
Show /etc/fstab.
|
|
| Aug 2 at 0:00 | review | Suggested edits | |||
| S Aug 2 at 0:19 | |||||
| Aug 1 at 23:29 | history | edited | Growing My Roots | CC BY-SA 4.0 |
added 423 characters in body
|
| Aug 1 at 22:55 | history | edited | Growing My Roots | CC BY-SA 4.0 |
added 163 characters in body
|
| Aug 1 at 22:44 | history | edited | Growing My Roots | CC BY-SA 4.0 |
added 349 characters in body
|
| Aug 1 at 22:38 | history | asked | Growing My Roots | CC BY-SA 4.0 |