I’m learning, but apparently not fast enough. Looks like I borked my system with a hasty reboot and now my root drive is not writable. Booting gives a ton of errors to that effect and my /home is missing.
I’ve spent the day so far googling different solutions but I’m slowly realizing that linux solutions are ephemeral as a fart in the wind. I’m TW 15. Any help would be appreciated.
Jim
Also, my root drive is btrfs.
What does that mean?
What errors does it throw?
Can you boot into a previous snapshot?
Apologies for the TW15, as I realize tumbleweed does not have versioning. What I meant to express is that I have not applied an update for the past few days (not since Leap went to 16).
My root drive is nvme01. Today I took sda1, which was already on my opensuse system, and repartitioned it with Yast. I cleared the partition, then made a new ext4 partition and an encrypted partition. This is relevant because earlier snapshots time out trying to load the previous configuration for sda1. I get dropped to the repair console with the earlier snapshots.
I used installation media to get to the recovery prompt. I mounted my nvme root partition and ran btrfs --repair. It found several errors, but on reboot the problem remains. Specifically, it will boot to a desktop (barren desktop) and throws constant windows stating that it cannot write to various config files. They take the form of: “Configuration file X not writable. Please contact your system administrator”. If I fight past those, there are no applications available.
I can see that the nvme0np2 (root partition) still shows 73% full, so I didn’t accidentally wipe that partition. Gparted shows it there as well.
This is fixed. I updated my BIOS then started diligently working through my snapshots. I found one that works. Thank you.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.