So system unable to start properly
sysroot: Parsing deployment /ostree/boot.0/fedora/39734cb9927f5b4ebab3bfd3b475a0275276dcb970e62bcd690d9c444c2dd1a1/0 in stateroot 'fedora': readlinkat: No such file or directory
What happened? What changed recently? Does the rollback deployment work?
This started happening when the computer lost power during the shutdown process. Neither rpm-ostree nor ostree commands worked, and the system booted into emergency mode.
$ rpm-ostree rollback
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
Then we need the journal log from the system after you’ve run rpm-ostree status and it fails: journalctl -b > journal.log, especially the rpm-ostreed.service part.
...
Reading config file '/etc/rpm-ostreed.conf'
error: Couldn't start daemon: Error setting up sysroot: loading sysroot: Parsing deployment /ostree/boot.0/fedora/39734cb9927f5b4ebab3bfd3b475a0275276dcb970e62bcd690d9c444c2dd1a1/0 in stateroot 'fedora': readlinkat: Нет такого файла или каталога
...
The system use an incorrect bootversion link. Is there a way to fix this?
You will have to look at what versions are installed manually and figure out which one is broken. You need to look at /boot/loader/entries, /sysroot/ostree/deploy, etc. It’s really weird that this happened as this is what ostree should be preventing from happening.
If you can start by giving us the listing (ls -alh) and content of the BLS entries that would be good. Listing of /ostree/boot.0/fedora as well (ls -alhR).
This sounds a lot like Silverblue won't boot after forced shutdown, searching for ways to recover it.
This is likely fixed in ostree 2025.5 (deploy: call syncfs() for /ostree instead of / by champtar · Pull Request #3504 · ostreedev/ostree · GitHub)
1 Like