#can't boot after moving/resizing partitions

1 messages · Page 1 of 1 (latest)

edgy pike
#

Hello, I originally had Garuda Linux installated and wanted to move to rhel. First I split my nvme in half and installed fedora, but later reinstalled and wanted to try rocky. I installed rocky Linux 9 on the other partition(with lvm, I think separate boot location).
Now I wanted to move fully to rocky, so I booted a fedora live image, and with kde partition manager deleted old Linux btrfs partition, moved my rocky partitions left and resized the home lvm.
How nvme partitions looked Before:
|Garuda Boot| |Garuda| |RL Boot I think?| |Rocky LVM| |No clue|
Then I moved around everything to:
|RL boot?| |Rocky LVM| |idk|
Rocky LVM has 2 I think called volumes, root and home. Resized those too.
Now my pc won't boot. In bios I only see Fedora partition, which is the probably remnant boot, which is putting me into grub>.
I then in grub did

> ls
(Memdisk) (Proc) (Lvm/rl-root) (Lvm/rl-home) (Lvm/rl-swap) (Hd0) (Hd0,gpt6) (Hd0,gpt5) (Hd0,gpt4) (Hd0,gpt3)

//Prolly means separate boot part?
> ls (lvm/rl-root)/boot
./ ../

>Ls (Hd0,gpt3)/
Error: unknown file system

>Ls (Hd0,gpt4)/
Efi/ grub2/ loader/ vmlinuz...El9_4.x86_64 initramfs...el9_4 config-5... Symvers-5... 

>set root (Hd0,gpt4)
>linux /vmlinuz-5.14.0-427.33.1.el9_4.x86_64 root=/dev/nvme0p4
>Initrd /initramfs-5.14.0-427.33.1.el9_4.x86_64.img
>boot

Then I saw Linux penguins appear, some fly by text and then I end up in what I only can assume is that command that live watches IO changes, it just sits and tells me what usb devices are changing, not progressing.

I REAALLY don't want to reinstall, took me months gradually to install everything I need for my work.

How can I rescue this?
I feel like I'm close, I just don't know what I'm doing wrong.

#

Unsure if that's the right Linux params, so I tried
linux ...x86_64 root=/dev/nvme0p4
And
linux ...x86_64 root=/dev/nvme0p6
But both resulted in just that usb logging state.

When I tried without setting the root, I Got

FAILED] Failed to start Switch Root.

See 'systemctl status initrd-switch-root.service' for details.

Generating "/run/initramfs/rdsosreport.txt"

Entering emergency mode. Exit the shell to continue.

Type "journalctl" to view system logs.

and then again usb logging. What am I doing wrong :(

edgy pike
#

following https://0xcaffee.blog/posts/grub-booting-with-lvm/ I managed to get to rocky Linux emergency console I think. Unfortunately default.target doesn't work, and I can't enter my root password due to it requiring characters from non-en layout(not that I'd know what to type once I'm in anyways).
It failed with:

[DEPEND] Dependency failed for /boot/efi.
[DEPEND]Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Mark the need to relabel after reboot.
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uuid/E804-AFGE.