888
systemdeez nuts (sh.itjust.works)
submitted 8 months ago by silverchase@sh.itjust.works to c/linuxmemes@lemmy.world
206 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[-] Deckweiss@lemmy.world 1 points 8 months ago* (last edited 8 months ago)

Honestly, I have no idea why it went wrong or why it let me do that. Also my memory is a bit fuzzy since it's been a while, but as best I can remember what I did step by step:

  1. fuck around with power management configs
  2. using btrfs-assistant gui app, rolled back to before that
  3. btrfs-assistant created an additional snapshot, called backup something, I didn't really pay attention
  4. reboot, all seemed good
  5. used btrfs-list to take a look, the subvolume that was the current root / was a child of the aformentioned backup subvolume
  6. started btrfs-assistant and deleted the backup subvolume
  7. system suddenly read only
  8. reboot, still read only
  9. btrfs check said broken refs and some other errors,
  10. i tried to let btrfs check fix the errors, which made it worse, now I couldn't even mount the drive anymore because btrfs was completely borked
  11. used btrfs rescue, which got all files out onto an external drive successfully
  12. installed arch again and rsync the rescued files over the new install, everything works as before, all files are there
[-] EinfachUnersetzlich@lemm.ee 2 points 8 months ago

btrfs check said broken refs and some other errors,

Gotcha. That must have been a kernel bug (or hardware error), none of the userspace utilities could cause it unless they were trying to manipulate the block device directly, which would be really dumb. It's possible it wasn't even related to the subvolume manipulation.

this post was submitted on 19 Apr 2024
888 points (98.7% liked)

linuxmemes

21280 readers
800 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world