Dewm Posts - Answer Overflow

Dewm

•Created by Dewm on 9/9/2024 in #🛟bazzite-help

Gparted "move left" breaks install, no way to regenerate Grub

Hello, I recently used a Gparted LiveCD to move my bazzite partition left to extended it further as I was running out of space; and no longer needed the NTFS partition on the drive. Upon rebooting, I was able to see bazzite ostree listings as per usual, but upon booting it up I was forced into recovery mode and had a "root user account locked" error, preventing me from using the terminal. I proceeded to follow this tutorial: https://docs.fedoraproject.org/en-US/quick-docs/root-account-locked/ Which requires me to follow the steps here: https://docs.fedoraproject.org/en-US/quick-docs/grub2-bootloader/#_restoring_the_bootloader_using_the_live_disk But upon trying to chroot into /mmt, I recieve the error:

chroot: failed to run the command '/bin/bash' No such file or directory

chroot: failed to run the command '/bin/bash' No such file or directory

I have tried this a few different times with a few different live CDs. I am currently using Fedora-KDE-Live though. I have also tried running boot-repair-livecd which runs boot-repair via the terminal; and it provided me with the information that GRUB is looking for the partition starting at a data point much higher than what the actual start point is for that partition. I assume I have to update the partition table somehow, but I have no idea where this is... Now for completion sake, I have sdh4 which is my /boot drive, that's formated with FAT32 which contains an "EFI" and "System Volume Information" folder at it's root. SDH5 is an EXT4 "extended data" partition that is 1GB in size that has a "boot" (link), "efi", "grub2", "loader" (link), "loader.1", "lost+found" and an "ostree folder SDH6 is my home folder / bazzite folder which hosts my "boot", "dev", "home", "ostree", "proc", "root", "run", "sys", "tmp" and "var" folders. When following the instructions, I only used folders from SDH6 and SDH4 as I do not understand wat the SDH5 folders are. The EFI folder it has is entirely empty, and I don't want to break anything from my lack of understanding.

32 replies

UBUniversal Blue

•Created by Dewm on 8/11/2024 in #🛟bazzite-help

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 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>

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

13 replies

Gaming

Programming