Update #1

I fixed my boot issue, but now I have to fix the issue with snapper not working right.

The boot issue: Something—I don’t know what—added a removable drive to fstab, and the error was that drive couldn’t be mounted at boot. I have two guesses:

  1. I formatted a microSD card using YaST Paritioner sometime before doing the distro upgrade.
  2. The drive might have been mounted during the distro upgrade, though I don’t think it was.

At any rate, I commented out that line in fstab and it booted right up.

Mullvad is working fine when I boot normally. I guess it was only broken when booting a snapshot from before I upgraded it.

Update #2

I also fixed /.snapshots by adding it to fstab. Now it gets mounted on every boot, and this version of fstab will be in all future snapshots. I just took a manual snapshot for good measure.

I don’t know which action caused the issue, so I’m going to list everything I did. I’m new to OpenSUSE Tumbleweed, and I haven’t used Linux since like Linux Mint 17.

  1. I disabled KWallet because I got tired of typing in a password every time my desktop launched just for wifi passwords. I decided to just let Linux store them in plain text since my whole system is encrypted with LUKS.
  2. I did a distro update. (zypper dup) After that succeeded, I logged off and back on.
  3. I noticed Mullvad had a new version. They don’t officially support OpenSUSE, so I downloaded the new RPM. I ran rpm -e mullvad-vpn to remove the old one. That might have been a mistake since my notes say I used zypper to install it the first time. I installed the new one with zypper. It launched and connected just fine.
  4. I had some trouble getting network settings to store/retrieve my wifi password, so I decided to reboot my system since I changed so much stuff.
  5. It wouldn’t boot. I see a few “BIOS” and “ACPI” errors.
  6. Time to try out Snapper! I reboot and choose the most recent snapshot from before tonight.
  7. It boots, but when I try snapper rollback I get IO error (.snapshots is not a btrfs subvolume)
  8. I get the same error trying to open the YaST snapshot viewer.
  9. I check btrfs, and I see @/.snapshots plus a bunch of numbered snapshots, of course.
  10. I check fstab, but I don’t see an entry mounting anything on /.snapshots.
  11. I do see a directory at /.snapshots, but it appears just be an empty directory.

Mullvad seems broken with this snapshot. I can’t connect to the internet. The mullvad-daemon won’t start, so I think the killswitch is active. I’ve had to type all this on my phone.

What can I do to fix this? I just want to rollback to this good snapshot, and then I can worry about fixing Mullvad when the filesystem isn’t read-only.

One month. That’s how long it took me to break my system. ☹️