Forced reboot caused ostree deploy to be missing
Hey everyone!
So a month or so ago I had an issue where I forced a cold reboot and it seems that because of this the ostree deploy that I was using got corrupt or simply vanished.
Regardless, I did some workaround by moving the boot.1 to boot.0 so I could boot into to system and since I was in an hurry I ended using the system as it was till today (yep, no reboot or shutdown since then afraid it wasn't going to boot again).
So now I'm trying to figure out what's the issue because I want to keep the system up to date and
ujust update won't work since ostree seems to be borked.
What I mean by ostree being borked is that rpm-ostree service doesn't start because the deploy that is trying to find doesn't exists.
Attached to this message is the output for systemctl status rpm-ostreed.service
Here are the deploys that actually exists:
sudo ls -lha /ostree/deploy/default/deploy/ total 12K drwxr-xr-x. 1 root root 834 jun 19 12:58 . drwxr-xr-x. 1 root root 32 abr 25 13:04 .. dr-xr-xr-x. 1 root root 180 mai 31 14:09 2d8aae754e5a6a0b669a7f8a903732454b41a6288aebef10f264393b259e575c.0 -rw-r--r--. 1 root root 344 jun 1 19:01 2d8aae754e5a6a0b669a7f8a903732454b41a6288aebef10f264393b259e575c.0.origin dr-xr-xr-x. 1 root root 180 abr 28 08:08 92c3e22984b2ca3d47702689568c9f4516c3ff8ef3ea4e2403126bebea2d34af.0 -rw-r--r--. 1 root root 345 mai 28 17:12 92c3e22984b2ca3d47702689568c9f4516c3ff8ef3ea4e2403126bebea2d34af.0.origin dr-xr-xr-x. 1 root root 180 jun 19 12:58 b7c4e66d4dccb15396cad3f3181fa3ead49b59ac66c9f73fb27b95316ec90d3a.0 -rw-r--r--. 1 root root 344 jun 19 12:58 b7c4e66d4dccb15396cad3f3181fa3ead49b59ac66c9f73fb27b95316ec90d3a.0.originAnd attached to this message are the ostree-1.conf and ostree-2.conf. I think the solution might be to edit the ostree confs with an valid deploy, but this is way over my head already, so I figured I should ask for some assistance. I'm attaching files that I think could help understand this issue better.
1 Reply
Forgot to mention, this is a PC, not a handheld.
Spent 8 hours trying to solve this, no luck.
For anyone who also has this issue, cut your losses, backup using a live USB of your choice and reinstall.