I’m stuck with a broken dual-boot environment. I have Fedora 29 installed and working well. I had created an ostree and booted Silverblue on it with some success. At some point when cleaning up my system I deleted something in /ostree/deploy and it got all messed up. I ended up completely deleting my /ostree directory and doing again…
error: Parsing deployment 0 in stateroot ‘fedora’: readlinkat: No such file or directory
with the os-init command or status or whatever.
I’m guessing there is somewhere besides /ostree where something is stored. Maybe in /var. I haven’t found it. I’d very much like to create a new /ostree and take a look at this technology. Any insight as to how I can fix this would be greatly appreciated.
Try the command rpm-ostree status, it should display the deployments in the order they are presented at boot with the current one highlighted with a dot.
You may also want to take a read at this location>https://ostree.readthedocs.io/en/latest/manual/adapting-existing/ it seems to be relevant to your particular situation at this time.
I see,
Even so, that link is for ostree, which is the underlying technology of rpm-ostree, and there are other manuals there which may be more relevant to you in this case. But, that doesn’t answer the question you posted. IMHO, I would just blow it away and start over, unless there is a compelling reason to diagnose the problem.
That’s exactly what I tried to do and got into this predicament. I deleted the /ostree directory completely. That doesn’t seem to be enough, however. I guess something else is still hanging around. Maybe for podman or runc?
I don’t see anything for podman images as root.
I have a fully functional and necessary fedora-29 install on this system, so won’t be wiping that.
Certainly not! I was referring to the Silverblue install specifically, and just installing over it in it’s current location with automatic partitioning initially, then tweak it prior to install if/as needed.
But I see @jlebon has answered.