I’m experiencing a weird issue with Silverblue 41 I didn’t have when I first installed, so I wanna test if /etc modifications could have anything to do with it.
Is there a way to temporarily boot the current image but without any /etc modifications?
Get a USB-to-SATA / NVME adapter and a second SSD at least the same size of your current one.
Use clonezilla and clone your current system to the different drive
Boot into that drive
Create a read-write subvolume mounted at /etcold (or is it /var/etcold?)
Copy /etc to /etcold
Use the experimental reset command which basically does an rsync from /usr/etc (which stores the current defaults) to /etc
Reboot
If it goes well, stay, if not you can still copy the contents of /etcold to /etc and it should work again
This is really experimental. In theory it is not thaat bad and /etc is normally not changed by the user. Only some things should be, and I think we got them all in the custom rsync command.
Thanks for that information. I assumed that since Silverblue overlays /etc modifications over the base image it had a straightforward way to temporarily boot the base image without modifications, but it looks like these are the available options.
Is there any reason you can’t manually revert the changes AFAIK etc is mutable.
I can make modifications to /etc but quite frankly I don’t know where to look. Perhaps the issue isn’t related to any /etc modifications whatsoever. So I was hoping that if I booted the image without the overlay I’d be able to see if that’s the right angle to investigate.
That’s unfortunate, thanks for flagging this. I might still be able to use the tip Hristo shared to figure out which files got changed and identify a likely culprit.