this post was submitted on 25 Feb 2024

32 points (86.4% liked)

Linux

48301 readers

667 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

removed my mint partition from my kde-neon system and now grub won't boot :-{ (lemmy.world)

submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]

23 comments fedilink hide all child comments

The title explains it well. But I installed Mint on a 2nd partition, then deleted it since I no longer used it, and now Grub dumps me to the command line on boot :/

How do I recover?

EDIT: gonna give up. Fuck grub lmao EDIT2: Just reinstalled mint and used the grub it gives to fix everything lmfao

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 9 months ago* (last edited 9 months ago) (1 children)

NB: So, just a heads up, that since I've been able to boot into my KDE-neon install via grub

$ set root=(hd0,gpt2)
$ linux /boot/vmlinuz root=/dev/nvme0n1p2
$ initrd /boot/initrd.img
$ boot

I've skipped the steps regarding booting into a live image and using chroot/mount to mount the main install to the live session. If it's definitely necessary that I go that route let me know and I'll try it that way.

EDIT: My bad, grub install works fine if i run it w/ sudo

However, even after doing grub-mkconfig I'm being spat out onto the grub console when i reboot :S

[–] [email protected] 1 points 9 months ago (1 children)

This is definitely strange, but the EFI system partition will have to be mounted to install grub to it, maybe the disk got mounted as read only, could you try explicitly mounting it as rw with this command

sudo mount /dev/nvme0n1p1 /boot/efi -o rw

and then see if you can make a file as root by doing

sudo touch /boot/efi/test

if it doesnt fail on a permissions error, try installing grub again with --removable incase this error has something to do with it trying to tell the firmware what disk to look in like this

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --removable

hopefully this will run without error and install grub, and if it does id run it again without the removable flag

[–] [email protected] 1 points 9 months ago (2 children)

It was just me not running the command with sudo, my bad!

But even then, doing install-grub and grub-mkconfig with sudo (completing w/o errors) I'm still getting spat out onto the grub console at boot. Should I try formatting the efi partition and reinstalling grub to it?

[–] [email protected] 1 points 9 months ago (1 children)

Oh its no worries, it sounds like you just need to regenerate the grub config, you can do this by running

sudo grub-mkconfig -o /boot/grub/grub.cfg

or if your distro has it, you can just run

sudo update-grub

then grub should see the config on boot and put you in the normal graphical menu

[–] [email protected] 1 points 9 months ago (1 children)

Seems to work fine, but same again, nothing :/

Is it worth me just wiping the partition and doing it from scratch?

[–] [email protected] 1 points 9 months ago (1 children)

I think anything that can be done with a fresh format can be done with the current one, when you ran grub-install after the issue with not running it as root, did you only do it with --removable? If so, the old grub is might be getting picked over the new grub installed at the removable fallback path, because it has a proper entry in the boot order. I dont know what key it is on your system, but if you can get into the boot order menu where it shows all the different boot devices, like where you can pick where you want to boot from, id look for one that just says something like "UEFI boot " or something like along those lines, it wont say like grub or your distro name, if there is such an option available, could you try booting from that option?

[–] [email protected] 1 points 9 months ago (1 children)

I ran it without the --removable flag :)

Spamming f12 for the uefi boot menu, I have 3 options (neon, ubuntu, and ubuntu) but all 3 spit me out onto the grub console

[–] [email protected] 1 points 9 months ago (1 children)

Alright, could you see what the root variable is in the grub console before manually setting it by running echo $root, and if it prints anything, could you run ls / in the grub console and see if you see like home dev etc, or the directories you would expect to see in / inside linux, and if you do see anything, could you run ls /boot/grub/ and see if you see grub.cfg. But if you are already inside linux, go ahead and install grub with --removable, it wont overwrite your current installation. I dont want you to format the efi partition, incase something goes wrong and you wont be able to boot into linux at all

[–] [email protected] 1 points 9 months ago (1 children)

So echo $root returns (hd0,gpt1). I have to set it to hd0,gpt2 to get the boot/linux dirs. I'll try --removable and get back to ya

[–] [email protected] 1 points 9 months ago

Eh, it gives me a grub-like menu but selecting any option just dumps me back into the console.

[–] [email protected] 1 points 9 months ago (2 children)

I had an issue like that in the past

Even after I run grub-mkconfig and put the efi files on the correct folder, it wasn't recognized by the UEFI

What I did was to open my BIOS and at the EFI configs, I choose manually which efi file I wanted it to open

Maybe it does the trick to you as well

[–] [email protected] 1 points 9 months ago (1 children)

Tried all the ones that my BIOS picks up but no dice :/

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago) (1 children)

Can't you select the path?

Maybe your BIOS is at the wrong EFI partition

Make sure your UEFI is retrieving the correct path where you're installing your grub

Edit:

https://www.reddit.com/r/archlinux/comments/y29whd/grub_doesnt_initilize_on_acer_laptop/

Look at my issue in the past and see if it create an insight to you. Note that some of the commands may be different because I run Arch, so adapt it to your distro

[–] [email protected] 1 points 9 months ago* (last edited 8 months ago)

Afraid I got nothin' from that. It's pretty much beyond my abilities.

Im gonna try installing mint again and letting that fix my grub. if it doesnt, im gonna wipe and redo my install.

Thanks for trying :)

EDIT: Yep just stuck mint on the smallest partition the installer would let me and it "fixed" itself lol. Ah well. Until I inevitably distro hop :')

[–] [email protected] 1 points 9 months ago

Tried the 3 options I had in the UEFI boot menu but no dice on either annoyingly.