`loading sysroot: Parsing deployment [...] in stateroot 'fedora': readlinkat: No such file [...]`
i have no idea if this is the right place to ask this type of question but after searching and seeing a lot of people asking the same thing on various different forums but all either have literally no solutions or are a different configuration and since i am using a bluebuild image, might as well ask here.
i think yesterday i may have physically mishandled my laptop while it was still shutting down and may have made it crash mid shutdown process, and i woke up to trying to turn it on and being greeted to emergency boot.
it took a whole morning and some bits of an afternoon to fix but i did manage to get booted again by directly modifying a grub entry from a live environment (the issue itself is that, i believe rpm-ostree or something was probably doing some background processing stuff while shutting down - i may have somehow managed to interrupt it in between that point, so the system got upgrade but none of the configurations did, so everything is trying to point and use directories such as
/ostree/boot.0/fedora/xxx when they don't exist while /ostree/boot.1/fedora/yyy do) which thankfully got me booted, but sadly all rpm-ostree commands don't work at all.
they all error out with error: Loading sysroot: Failed to invoke RegisterClient: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.projectatomic.rpmostree1': startup job failed, and poking at systemctl status rpm-ostreed reveals:
[cont.]Solution:Jump to solution
This might be what @fiftydinar ran into before. He made a detailed comment on this issue
https://github.com/ostreedev/ostree/issues/2283...
GitHub
OSTree boot links can get out of sync · Issue #2283 · ostreedev/o...
We've had one instance recently in RHCOS where a system failed to boot with: systemd[1]: Starting OSTree Prepare OS/... ostree-prepare-root[887]: ostree-prepare-root: Couldn't find specifie...
4 Replies
[...]
this is the same exact directory grub was trying to use to boot - it doesn't exist, while
/ostree/boot.1/fedora/c2f52ba9bf2d6609fba301c12159cf00b9e43fea4f7ff2920945464e08377933/0 does exist and is what i modified for grub to use to make it bootable. so, how could i make rpm-ostree point to this directory? at least, just for now, to run an upgrade or whatever and hope that it can fix itself.
(i am using a custom bluebuild image, it's not related to a failing build, this is just a random issue that happened to me)Solution
This might be what @fiftydinar ran into before. He made a detailed comment on this issue
https://github.com/ostreedev/ostree/issues/2283
GitHub
OSTree boot links can get out of sync · Issue #2283 · ostreedev/o...
We've had one instance recently in RHCOS where a system failed to boot with: systemd[1]: Starting OSTree Prepare OS/... ostree-prepare-root[887]: ostree-prepare-root: Couldn't find specifie...
Maybe this will help
In the end, he did end up having to completely reinstall
yeah, that's a trend i'm noticing with this issue in particular
either being "i just reinstalled" or "it fixed itself"
well siiigh. guess i'm reinstalling again then, thanks