you need to add the grub/systemd-bootd back into the UEFI boot entries, from linux you can do it with efibootmgr but i think there is some tool for windows as well
I did this -> (from chatgpt) sudo mount /dev/nvme0n1p5 /mnt sudo mkfs.vfat -F32 /dev/nvme0n1p3 sudo mkdir -p /mnt/boot/efi sudo mount /dev/nvme0n1p3 /mnt/boot/efi sudo mount --bind /dev /mnt/dev sudo mount --bind /proc /mnt/proc sudo mount --bind /sys /mnt/sys sudo chroot /mnt grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB update-grub exit reboot which lists linux, and when I select linux to boot, it goes into emergency mode (You are in emergency mode, after logging in type journal -xb to view system logs...)
What files have you nuked in /dev/nvme0n1p3? Did you really want to remove them all?
nvme0n1p3 is 800mb,, I don't knwo what was there, I formatted this partition after booting into new windows,,
Well this was frankly stupid.... You had a working system but instead of adding only a boot entry you nuked part of your system because chatgpt told you so...
nvme0n1p4 (300mb) was listed as EFI partition,,, I tried to install to that partition and got to the emergency mode.. Then I formatted the n1p3 partition and tried there 😐
The command I posted (from gpt)
Обсуждают сегодня