grub-install requires a target: either a drive for legacy booting or a mounted efi folder for EFI booting.
-
Not explicitly for UEFI/EFI. It will use the (default) ESP that is always mounted for THAT particular operating system (at /boot/efi).grub-install requires a target
You would only explicitly write a target if you wanted to create a new GRUB boot NVRAM variable somewhere using the GRUB files of THAT OS.
Of course, you CAN write a target in the grub-install line, even the default target, it won't hurt (as long as you get it right!).An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles BukowskiComment
-
I ran update-grub, then rebooted, and KI still get the error message (also when I shut down). However, it disappears after a couple of seconds, and doesn't seem to affect the running of Kubuntu, so I'm just going to let it be until I start having problems. Thanks again for the help.Comment
-
Now, I wonder if that's a message (black screen, white letters?) about a firmware issue?
If so, it is probably not a problem.
There was a discussion of it here, maybe two posts about it here.
It occurs (and has for a long time, many months) on my system upon shutting down. I just ignore it.
You really should have grub-install and then update-grub.
But it seems that you don't really have a problem anyway.An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles BukowskiComment
-
Well, it hung up again, and after restarting it and getting it going again, I tried grub-install and update-grub, which went smoothly, then rebooted the computer and got the same error message. I don't know if this is related ot not, but I used to get a message after grub saying that all files systems were being checked, and now I don't get that, just the error message.Comment
-
What's the error message say?An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles BukowskiComment
-
'You are in emergency mode? followed by a couple of instructions which I was unable to copy down because it disappeared after less than two seconds. I'm going to assume it's a harmless glitch and do nothing unless it gets worse.Comment
-
You can Google "Emergency mode in Kubuntu/Ubuntu," to see what it is and possibilities.
Things I see:
Maybe check your /etc/fstab file to make sure it looks OK.
Is your boot disk OK? SMART is one way to check it (although it auto-checks disks, too, at startup).
People have used Boot Repair to troubleshoot.
Some users have simply run grub-install and update-grub to make the message go away.
Question whether a filesystem is corrupted.
You didn't specify your PC system. But what we did was pretty standard and safe installing K24.04.1. Nothing unusual about it per se.
You get that message, but you can continue to boot into Kubuntu 24.04, and you are able to access and use your root filesystem.
Your approach may be best. Do nothing for now.
There are diagnostics to run, which some of the guys here may know about, like checking system logs.
An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles BukowskiComment
-
I did take a look at the system logs today after getting stuck at the error message, but I have no idea what to look for. So maybe I'll just wait awhile to see if this is going to be a problem or not. If so, would re-installing the system be a solution? I originally wanted to go to 24.10 but when the upgrade deleted all my graphic drivers I became worried...Comment
-
Ah, my system is a rather standard one, a desktop with i5 processor, 16 gigas memory, Nvidia GeForce 730 graphics card, running on the Nvidia 470 driver and a 500 GB hard drive with just Kuvuntu and a btrfs file system.Comment
-
Maybe, but ...would re-installing the system be a solution?
as I read things, Emergency mode could be -- but not necessarily -- a signal that something's wrong with some file system.
And you already re-installed grub (a good thing).
That's the problem with reading the logs -- run the command, but then how to interpret results.
So, if you do see something suspicious, you could copy-post the log files here to see if anyone can diagnose things.
There's a couple common commands for checking filesystems, you probably know what they are, they are in my cheat sheets somewhere (I've never had to use them!) ...An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles BukowskiComment
-
Don't know if this works, haven't tried it, but the command is fsck.
How to use fsck to check and repair disk errors?
Reboot your Ubuntu system.
Press the Shift key to access the boot menu.
Select "Advanced options" and enter recovery mode.
Choose the fsck option from the menu.
Follow the prompts to run fsck on the desired disk partition.An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles BukowskiComment
-
I tried this, and discovered that when I go into recovery mode and get the menu, I can't use my cursor! So I can't cant scroll down to fsck to try it out. Weird; something is wrong, but what?Comment
-
The Down arrow on the keyboard?
You can, also, run fsck from Konsole, as a command. We'll have to look up the exact form, the arguments, to use.
Edit: of course, the partition you wish to check must be unmounted.Last edited by Qqmike; Nov 03, 2024, 08:27 PM.An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles BukowskiComment
-
I ran fsck tonight and it informed me that there were differences between my boot and its backup, and offered me 3 options: to write boot to its copy, to write the copy to boot, or do nothing. I chose the first option and rebooted, but the error message did not go away. I ran fsck again and was told that my file system did not unmount properly and that there were some dirty bits left. I chose to clean them, but have not rebooted yet. If this goes on, I will start a new thread as I think no one else is reading this now except you (QMike) so maybe someone else has an idea. Thanks again for all your help.Comment
Comment