[BUG] still booting read only after roll back about snapper-rollback HOT 10 CLOSED

I fixed the issue. I did a fresh install and chnaged two things. I'm not sure which fixed the issue, but one of them did. Thank you and sorry about that.

david-cortes/snapper-in-debian-guide#2 (comment) if you're curious what I did.

from snapper-rollback.

Just to make sure I understand:

• you booted into a previous snapshot which itself is readonly
• you are running snapper-rollback from there
• when you reboot into the rootfs, the system is readonly as well?

Snapper was built by and for openSuse, then adapted by the archlinux community for arch and its subvariants. Debian support came later by a few volunteers and is quite new per my understanding.
I've never used or tested this script on Debian, and I'm unfamiliar with the guide you linked to so you're probably going to have to debug this on your own or with the guide author's help.

A few pointers:

• what is the partition layout? The subvolume layout? It should match the ArchWiki suggested volume layout
• what command-line was the kernel booted with?
• the way to solve this problem, like any other, is to isolate it. Will your system be rw if you're booted into your standard rootfs at the time you run the script? Will it be rw if you reboot into a different snapshot? What config do the problematic snapshots have? What happens if you boot into a non-rootfs read-write snapshot? And so on.

If all else fails, you might want to consider going with the Spiral Linux project, which apparently does all this setup for you out of the box. This isn't an endorsement as I haven't tested the script out on Spiral either, but it might help you isolate the issue a bit further.

In any case, I'll be interested to hear what your solution was - please let me know if I can help.

from snapper-rollback.

• you booted into a previous snapshot which itself is readonly

Yes.

• you are running snapper-rollback from there

Yes.

• when you reboot into the rootfs, the system is readonly as well?

Yes.

• what is the partition layout? The subvolume layout? It should match the ArchWiki suggested volume layout

Yup. Except it its @rootfs instead of @.

• what command-line was the kernel booted with?

Looks like it is booting ro.

BOOT_IMAGE=/vmlinuz-6.1.0-10-amd64 root=UID... ro rootflags=subvol=@snapshots/6/snapshot quite

Now I'm wondering why. When I first installed snapper, before I did any rollback, it booted fine -- not in read only mode.

It only started doing this after I did a rollback. Suspicious.

from snapper-rollback.

I am going to do another fresh install, and this time I'll boot into the snapshot but not do a snapper-rollback. Then I'll see if it'll let me boot back normally.

One of two things will happen:

1. It works -- means something is up with snapper-rollback
2. It does not work -- means the problem is with something else, not snapper-rollback.

from snapper-rollback.

The issue is definitely with the rollback per your description. My question is how is the rollback configured? I'm not sure I'd pin it on the script so fast - I see your kernel cmdline is booting into a snapshot. If that's after the reboot and you're selecting the default grub menuentry, why are you booting into a snapshot?.

Before pinning the problem you're facing on anything, it's important to prove beyond a doubt the origin of the issue. It sounds like this is a very custom setup, which is fine, but it means extra care needs to be taken to isolate the problem to one of the components.

from snapper-rollback.

My question is how is the rollback configured?

What exactly do you mean? Do you mean the /etc/snapper-rollback.conf file? It's left to defaults except for this line:

subvol_main = @rootfs

If that's after the reboot and you're selecting the default grub menuentry, why are you booting into a snapshot?

That is the question....

from snapper-rollback.

The script doesn't actually touch grub or its menuentries because too much complexity. I invite you to read through the script source once and use --dry-run flag, but it sounds like your grub menuentries are messed up for some reason. Which makes the script here a very unlikely culprit, though it's not impossible of course.

I'll be interested to know why the default grub menuentry are pointing to a snapshot

from snapper-rollback.

This be strange. I did a fresh install and installed all the tools: snapper, grub-btrfs and snapper-rollback.

I haven't done any rollbacks and am booting up the default grub menuentry.
Everything works as expected. The filesystem is not read only. I can do things.

But it still shows ro for how the kernel was booted:

BOOT_IMAGE=/vmlinuz-6.1.0-10-amd64 root=UID... ro rootflags=subvol=@rootfs quite

I am going to keep debuging this. Thanks!

from snapper-rollback.

I'll close this issue now, but I'd be curious to know what happened. Good luck debugging!

from snapper-rollback.

Thanks for circling back with the explanation!

from snapper-rollback.