search

Antynea / grub-btrfs

Include btrfs snapshots at boot options. (Grub menu)
GNU General Public License v3.0
688 stars 73 forks source link

system booting in read only mode after doing a rollback #294

Closed imthenachoman closed 1 year ago

imthenachoman commented 1 year ago

I installed snapper and grub-btrfs and everything was fine.

I rolled back to a snapshot and rebooted the default entry, but it is in read only mode. I can't figure out what I've done wrong?

If it matters/helps, this is the guide I am using to get all this working: https://github.com/david-cortes/snapper-in-debian-guide

Schievel1 commented 1 year ago

I haven't read the whole guide, but it says

Now you should have booted into a READ-ONLY snapshot of your system at the time before atop was installed.

So this is desired behavior, isn't it?

/ sorry, I thought you booted into a snapshot. Instead you rolled back and booted the default entry. Hm, I have to read how they make snapshot read only in their guide.

// in the meantime... I am quite sure grub-btrfs is not what is making your snapshots read only. It's snapper itself or snapper-rollback that is doing it. I guess it's the interface between snapper and snapper-rollback that changed and it now causing that.

https://wiki.archlinux.org/title/Snapper has instruction on how to rollback manually und 5.11.11. Maybe you can give that a try and report back if the snapshot at @ (or @rootfs for you I guess) is now rw

Also the Snapshot can be made Writeable using 'btrfs property set -ts /path/to/snapshot ro false'

imthenachoman commented 1 year ago

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
Schievel1 commented 1 year ago

Yes I have that too, regardless of btrfs or ext4. This is a wild guess, but could it be that this ro option is applied to the initramfs if there is one?

imthenachoman commented 1 year ago

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.

https://github.com/david-cortes/snapper-in-debian-guide/issues/2#issuecomment-1629926033 if you're curious what I did.