Ostree Tree 0 not booting anymore due to config errors, can't seem to deploy Tree 1 as default.

Hello, I seem to have messed up either my fstab (forgot to test with mount -a) or messed things up by installing overlayfs-tools.
Currently I am able to boot with no issue under Tree 1, but I can't seem to do anything under Tree 0. Though when trying to type

sudo ostree admin status -v

sudo ostree admin status -v

sudo ostree admin status -v

sudo ostree admin status -v I get the result:

OT: root_is_ostree_booted: 1
OT: using fuse: 0
OT: Target rootdev key backing-root-device-inode found
OT: Deployment 4bb1b0ddc688a77bfd70f39e90727a6c1b7a767490ff7ddcad0588e3f071ddbe.0 unlocked=0
OT: Target rootdev key backing-root-device-inode found
OT: Deployment 316379777b350ed9d999a247dbc27919f1c532ceede4aa1d333a8cf6d4317663.0 unlocked=0
  default 5ee1cc894971c3c6a7498ae783a51b7dd4876dbddb4c2a7a9b666eac488b12e0.0 (staged)
    origin: <unknown origin type>
  default 4bb1b0ddc688a77bfd70f39e90727a6c1b7a767490ff7ddcad0588e3f071ddbe.0
    origin: <unknown origin type>
* default 316379777b350ed9d999a247dbc27919f1c532ceede4aa1d333a8cf6d4317663.0
    origin: <unknown origin type>

OT: root_is_ostree_booted: 1
OT: using fuse: 0
OT: Target rootdev key backing-root-device-inode found
OT: Deployment 4bb1b0ddc688a77bfd70f39e90727a6c1b7a767490ff7ddcad0588e3f071ddbe.0 unlocked=0
OT: Target rootdev key backing-root-device-inode found
OT: Deployment 316379777b350ed9d999a247dbc27919f1c532ceede4aa1d333a8cf6d4317663.0 unlocked=0
  default 5ee1cc894971c3c6a7498ae783a51b7dd4876dbddb4c2a7a9b666eac488b12e0.0 (staged)
    origin: <unknown origin type>
  default 4bb1b0ddc688a77bfd70f39e90727a6c1b7a767490ff7ddcad0588e3f071ddbe.0
    origin: <unknown origin type>
* default 316379777b350ed9d999a247dbc27919f1c532ceede4aa1d333a8cf6d4317663.0
    origin: <unknown origin type>

OT: root_is_ostree_booted: 1
OT: using fuse: 0
OT: Target rootdev key backing-root-device-inode found
OT: Deployment 4bb1b0ddc688a77bfd70f39e90727a6c1b7a767490ff7ddcad0588e3f071ddbe.0 unlocked=0
OT: Target rootdev key backing-root-device-inode found
OT: Deployment 316379777b350ed9d999a247dbc27919f1c532ceede4aa1d333a8cf6d4317663.0 unlocked=0
  default 5ee1cc894971c3c6a7498ae783a51b7dd4876dbddb4c2a7a9b666eac488b12e0.0 (staged)
    origin: <unknown origin type>
  default 4bb1b0ddc688a77bfd70f39e90727a6c1b7a767490ff7ddcad0588e3f071ddbe.0
    origin: <unknown origin type>
* default 316379777b350ed9d999a247dbc27919f1c532ceede4aa1d333a8cf6d4317663.0
    origin: <unknown origin type>

OT: root_is_ostree_booted: 1
OT: using fuse: 0
OT: Target rootdev key backing-root-device-inode found
OT: Deployment 4bb1b0ddc688a77bfd70f39e90727a6c1b7a767490ff7ddcad0588e3f071ddbe.0 unlocked=0
OT: Target rootdev key backing-root-device-inode found
OT: Deployment 316379777b350ed9d999a247dbc27919f1c532ceede4aa1d333a8cf6d4317663.0 unlocked=0
  default 5ee1cc894971c3c6a7498ae783a51b7dd4876dbddb4c2a7a9b666eac488b12e0.0 (staged)
    origin: <unknown origin type>
  default 4bb1b0ddc688a77bfd70f39e90727a6c1b7a767490ff7ddcad0588e3f071ddbe.0
    origin: <unknown origin type>
* default 316379777b350ed9d999a247dbc27919f1c532ceede4aa1d333a8cf6d4317663.0
    origin: <unknown origin type>

I believe I need the origin to set ostree 1 as my current commit/deploy, though I'm not entirely sure. Here are the contents of /ostree if that helps.

tree -L 2
.
├── boot.0 -> boot.0.1
├── boot.0.1
│   └── default
├── deploy
│   └── default
└── repo
    ├── config
    ├── extensions
    ├── objects
    ├── refs
    ├── state
    └── tmp

tree -L 2
.
├── boot.0 -> boot.0.1
├── boot.0.1
│   └── default
├── deploy
│   └── default
└── repo
    ├── config
    ├── extensions
    ├── objects
    ├── refs
    ├── state
    └── tmp

tree -L 2
.
├── boot.0 -> boot.0.1
├── boot.0.1
│   └── default
├── deploy
│   └── default
└── repo
    ├── config
    ├── extensions
    ├── objects
    ├── refs
    ├── state
    └── tmp

tree -L 2
.
├── boot.0 -> boot.0.1
├── boot.0.1
│   └── default
├── deploy
│   └── default
└── repo
    ├── config
    ├── extensions
    ├── objects
    ├── refs
    ├── state
    └── tmp

DewmOP•8/12/24, 12:45 AM

I was able to use ostree admin pin 1ostree admin pin 1 to set it as my default boot currently, but says root_is_ostree_booted: 1root_is_ostree_booted: 1 now. Is this okay? Or would this be an issue down the line?

DewmOP•8/12/24, 1:25 AM

This also doesn't fix the "Unknown Origin Type"

SovietThunderChicken•8/12/24, 4:54 PM

I am having a very similar issue, FYI. I am using the bluefin-dx-nvidia variant though

DDewm I was able to use ``ostree admin pin 1`` to set it as my default boot currently,...

antheas•8/12/24, 6:32 PM

You should either be able to do rpmostree rollback

antheas•8/12/24, 6:32 PM

Which will swap the deployments

antheas•8/12/24, 6:32 PM

Or update

antheas•8/12/24, 6:33 PM

Which will replace the broken deployment

Aantheas You should either be able to do rpmostree rollback

DewmOP•8/12/24, 7:50 PM

Cheers! I'll give that a try!

DewmOP•8/12/24, 9:17 PM

That seems to have done the trick! I have unpinned my previous setup, thank you!

DewmOP•8/12/24, 9:18 PM

Marking as solved, would you like any help with this too @SovietThunderChicken ? Have you tried any of the steps taken here?

SovietThunderChicken•8/12/24, 10:27 PM

You can mark as solved, not applicable to me though. Mine was specific to blue build

Ostree Tree 0 not booting anymore due to config errors, can't seem to deploy Tree 1 as default.

Similar Threads

Similar Threads

Similar Threads