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:
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.
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:
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.
Fedora Docs
Phenomenon Cannot open access to console, the root account is locked in emergency mode (dracut emergency shell) Reason This is a known problem. It happens Fedora releases 28 and newer,…
Fedora Docs
GRUB2 is the latest version of GNU GRUB, the GRand Unified Bootloader. A bootloader is the first software program that runs when a computer starts. It is responsible for loading…
