On Mon, Mar 18, 2024 at 1:31 PM Darryl Gregorash <raven@accesscomm.ca> wrote:
On 2024-03-18 03:39, Roger Oberholtzer wrote:
Hmmm. I see.
So if I am happy with snapshot 1406, I would 'snapper rollback 1406' to make that the current content?
I ask because snapper seems very powerful to the point where I get suspicious. This is the computer version of "measure twice, cut once".
https://doc.opensuse.org/documentation/leap/archive/15.0/reference/html/book...
If you did not choose "Bootable snapshots" when you booted the system, then you booted from the wrong menu item in the boot menu. Try booting from that menu now, then run (as root) "snapper rollback" and reboot normally. Hopefully, with your system in its current state, that will still work. If not, I have no idea what you can do. Since the snapshot you are now using is now the default, I'm not overly confident that this will work. If it does work, you should be booting with the root system mounted r/w. But if it does not, then possibly the only thing you can do is re-install the system (install, NOT upgrade) from a USB stick. Make sure to bookmark that URL above, for future reference.
I booted from the main menu. I did not navigate anywhere like to Read-only snapshots. So I would have expected it to be writable as well. Odd that the system has gotten into a state where there are no writable options. snapper rollback just says: Ambit is transactional. Active snapshot is already default snapshot. Sigh. I don't want to do a reinstall. All the software is set exactly as I want. It's one of (not the only) systems on which I develop software. Oh well. Time to extract all the needed information from it! I still cannot believe that snapper cannot do whatever it does to allow changes. A new snapshot. Couldn't I make a snapshot via some other command than rollback? Or is it that since I'm in a snapshot, there is nothing to make a snapshot of and then allow new changes after that. If I wasn't booted into it perhaps? Like boot from a USB stick and then try the rollback on this filesystem? I suspect I'm just demonstrating my ignorance about that it the reason for the problem. -- Roger Oberholtzer